1591 - Diamond / LatticeECP3: What is the guideline to use a general routing based clock for the LatticeECP3 device?<br>
For the LatticeECP3 device, general routing can be used route as the clock resource rather than using dedicated clock resources. This should only be considered for non-critical clock paths and for small areas of the design. Clocks routed using the general data routing paths will not have the same performance as the dedicated routing resources. Due to the large amount of connectivity, this resource will not have a tight skew as the dedicated clocking resources. For this reason, it is best to limit the distance of clocks using general routing, as well as the number of loads. This can be done by grouping the logic in the clock domain with a UGROUP preference. As a result, it will improve both the setup time and the hold time for the general routing based clock.
If possible, user should always use a primary clock instead of the general routing based clock when routing a critical path clock for your design.
Related Articles
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. ...
908 - Diamond: ECP2: How many generic routing signals can be used as primary clocks in a LatticeECP2/M device? <br>
Diamond: ECP2: In a LatticeECP2/M, the primary clocks, whether they're global or quadrant, get their sources through a center MUX. The number of generic routing signals that can get onto the center MUX is 10. These 10 signals come from FPGA routing ...
217 - Diamond: Why does the design trigger warning messages stating Edge or Primary clock is un-routable, occupied and uses general routing, or are not placed on sweet site?
Occasionally in congested designs a conflict occurs resulting in an unroutable condition during the Place and Route (PAR) phase of a design. The conflict can be due to components that have been placed by user constraints, or by the decisions made by ...
2831 - Lattice Diamond / ECP3: Why is software unable to complete PAR on the LVDS clock when utilizing general routing?
Description:An error message is received when routing with general routingERROR - par: netsanitycheck: the clock clk_lvds_rx_p_c on comp adcif_inst/Inst3_EHXPLLF port CLKI is driven by general routing through comp clk_lvds_rx_p. Please consult ...
2165 - Simulation: Steps to compile/elaborate a SERDES based design in NC-Verilog?<br>
Simulation: Compiling/elaborating a SERDES based design requires pre-compiling the SERDES model. Follow the steps below to compile the Lattice SERDES model, revise your library definition file, and compile and elaborate your design. Unzip the ...