Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: m-labs/migen
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 408a85f0226e
Choose a base ref
...
head repository: m-labs/migen
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: ccf63038cc40
Choose a head ref
  • 4 commits
  • 6 files changed
  • 2 contributors

Commits on Apr 2, 2016

  1. migen/build/platforms: adding apf6sp Armadeus Platform

    Signed-off-by: Fabien Marteau <fabien.marteau@armadeus.com>
    Martoni authored and sbourdeauducq committed Apr 2, 2016
    Copy the full SHA
    7cb3634 View commit details
  2. migen/genlib: little module documentation

    Signed-off-by: Fabien Marteau <fabien.marteau@armadeus.com>
    Martoni authored and sbourdeauducq committed Apr 2, 2016
    Copy the full SHA
    dc724f9 View commit details
  3. migen/fhdl: better error messages

    Signed-off-by: Fabien Marteau <fabien.marteau@armadeus.com>
    Martoni authored and sbourdeauducq committed Apr 2, 2016
    Copy the full SHA
    1acfa57 View commit details
  4. build/xilinx/ise: Use separate TNM_NET for period and TIG constraints.

    Because ISE is retarded, if you have anything other than period constraints on
    a TNM_NET (such as a TIG), then it is unable to trace the constraints through
    any of the clock elements like PLLs and DCMs. It will generate the following
    warning instead;
    
    > ConstraintSystem - TNM : *** was distributed to a DCM but new TNM constraints
    > were not derived. The requirement for derived TNM constraints is that the
    > distributed TNM is referenced by no more than a single PERIOD constraint.
    > Non-PERIOD referencers are also not allowed.
    
    The requirements for the TNM to be derived is described at
    [Timing Constraints User Guide - UG612 (v 11.1.1) April 29, 2009](http://www.xilinx.com/support/documentation/sw_manuals/xilinx11/ug612.pdf):
    
     * The TNM group is used in exactly one PERIOD specification.
     * The TNM group is not used in any FROM-TO or OFFSET specifications.
     * The TNM group is not referenced in any user group definition.
    
    The fix is described in http://www.xilinx.com/support/answers/40007.html ||
    http://www.xilinx.com/support/answers/37782.html
    
    Create two TNM Groups for your input clock. One used for the FROM-TO
    constraints and the other for the PERIOD propagation.
    
    Fixes #43
    mithro authored and sbourdeauducq committed Apr 2, 2016
    2
    Copy the full SHA
    ccf6303 View commit details
Loading