1046 - Lattice Diamond: What is the "BLOCK INTERCLOCKDOMAIN PATH" preference used for? <br>

• Related Articles

• 939 - Lattice Diamond: How can I block clock transfers in the timing analysis tool? <br>

  A clock domain transfer or crossing occurs when one register in a data path is clocked by CLKA and one register by CLKB. To block this transfer from the timing analysis use the preference: BLOCK INTERCLOCKDOMAIN If you are looking to relax or analyze ...

• 134 - Diamond: How can user block clock domain transfers where there is already synchronizer circuits in place?

  The Lattice Static Timing Analyzer Trace analyzes all clock domain transfers in which it can relate the source and destination clock domains. This may not always be desired. User may utilize their own synchronizer to handle the transfer between the ...

• 2389 - Do BLOCK constraints limit the maximum coverage % reported in the timing report that can be achieved (&lt;100%)?

  The timing report generated by the Lattice Diamond Place and Route Tools report a timing coverage %. This number tells the user how complete their timing report is. Some customers require 100% timing coverage to ensure their designs are fully timed. ...

• 3837 - Lattice Diamond: Is the USE EDGE preference available in the tool for MachXO2 devices?<br>

  Solution: The USE EDGE preference is not available for MachXO2 devices in Lattice Diamond software. The only way to support the edge is through the design - ECLKSYNC and DDR modules only.

• 2724 - Lattice Diamond: Where can I see the results of changes made in the Input Delay block?<br><br>

  The Place and Route TRACE report will only show the delays through the Input Data DELAY block if the delay values are static. The changes can be seen in the parameters under the INPUT_SETUP preference section of the TRACE report.