2084 - Diamond: How to check the un-constrained connections in Lattice Diamond?
In Lattice Diamond, when user set up the strategies for either "MAP TRACE" or "Place & Route TRACE", select "Check unconstrained Path" to "True". TRACE will list out all the connections that are not covered by preferences. To make better use of this information to correlate back to RTL, user may also select "Full Name" to "True", since it will list the full name of the related instances in the design.
Related Articles
7175 - Diamond 3.13 and below: How to use Git with Lattice Diamond?
There is no direct way of integrating Git to Lattice Diamond. Users can only archive the project in Lattice Diamond and use Git to store the project inside a repository. Note: If users want to store the necessary files of the Diamond project only, ...
7403 - Radiant: How to further check the paths/connections in the design that are not covered by constraints?
To look into unconstrained connections from the design, use -dump_uncovered on the Place & Route Timing Analysis Strategy Settings, As shown below: The -dump_uncovered command creates a log file in the design directory named UncoveredConn.log this ...
7279 - Lattice Diamond: Does the MAXDELAY preference/constraint, and its option MIN, affect PAR? Or is it only used to check against TRACE timing?
Based on the MAXDELAY preference documentation found in Lattice Diamond Help, we see that MAXDELAY preference is only checked with TRACE timing analysis, but it is not factored in with PAR. Thus, PAR is unaffected by any MAXDELAY preference including ...
7733 - ECP5 / Diamond 3.14: Why does my design get a Map device oversize error related to PLL for LFE5U-12F in with Diamond 3.14, but completes map successfully in earlier releases of Diamond software?
In Diamond version 3.14, there is a bug where it incorrectly limits the number of PLLs in the device to 0 for LFE5U-12F. Example error message: ERROR - (device oversize error). The number of PLL components needed (1) exceeds the number available. ...
6271 - Reveal Analyzer core0 error: How to check the JTAG cable connections?
When the user connects the 2B programming cable with color-coded flywires to the board, Reveal only uses 4 wires + VCC and GND: * white = TCK * purple = TMS * orange = TDI * brown = TDO * red = VCC * black = GND If the user has connected a yellow ...