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 provides connections in the design that may need to be constrained to increase timing coverage. Since these are connections, users may want to consider tracing the cells/registers these objects are connected to, to define the proper constraint since it is desired to define a constraint on a valid timing path (Reg to Reg, Reg to Port, Port to Reg, Port to Port).
Below is an example of the contents of the log file.
Related Articles
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 ...6945 - Radiant: How does the user set constraints for a MII interface?
1. First step is to check the specs of the MII PHY. As an example, see analysis of the specs MII PHY together with what constraint would used the spec. ...7480 - Lattice Radiant: Why are there missing timing paths analyzed on R3.0 when it was compared with R3.1 and later?
Description: When users try to compare timing analysis paths from R3.1 and later with R3.0, there are timing violations/timing paths found in R3.1 and later that cannot be found in R3.0. Solution: This is a known issue on Software version R3.0 The ...6282 - Diamond: ERROR - par: I/O initial placement is unsuccessful. Check the I/O placement constraints / user preferences (such as pin locking) carefully
Description: When compiling a design on Diamond with multiple unassigned output ports, the below error might occur. "ERROR - par: I/O initial placement is unsuccessful. Check the I/O placement constraints / user preferences (such as pin locking) ...7075 - Lattice Radiant/Diamond: Do I need to constrain internal paths found on Hard Blocks (Lattice primitives)?
Timing within hard blocks are already optimized. Paths utilized in the primitive are already consistent hence Ideally there is no need to have them (the paths inside) constrained separately. Users would just need to connect the input/output ports to ...