1726 - ERROR - par: netsanitycheck: the clock buf_clk on comp Inst4_DLLDELB port CLKI is driven by general routing through comp clk. Please use the appropriate constraints when using general routing for clocks
User will encounter this error when running LatticeECP3 DDR design through software PAR. When using the DDR IO register (Double Date Rate) in a LatticeECP3 design, a user must implement a dedicated clock route for the clock being used at the DDR registers.
For an aligned interface using a DLL/PLL (Delay Locked Loop/ Phase Locked Loop) to shift the input clock, the clock input must be assigned to a dedicated DLL/PLL input pin. If using a PCLK pin instead, then the user must implement a "USE PRIMARY" preference so that the clock is routed to a primary clock tree.
For a centered interface that is not using a PLL/DLL instead the clock is directly routed to primary/edge clock tree going to DDR registers, then the clock must be assigned to a PCLK pin.
You can refer to section "High Speed DDR Interface Details" in TN1180 - LatticeECP3 High Speed I/O Interface for more details on each type of DDR interface.
Related Articles
6946 - What is the spec of 'sync_clk_i' of MIPI D-PHY Rx IP? Does the signal require to be in synced with any other clocks?
Description: Spec is given that 'sync_clk_i', or the 'Sync clock frequency', can support 24-200Mhz, and it is defaulted to 60Mhz, based on CSI-2/DSI D-PHY Rx IP Core IPUG 02081 document. 'syn_clk_i' does not need to synchronize with any clocks, and ...
2324 - [LatticeECP3]: Can I use a different rate of the input reference clock other than 100MHz when a 400MHz/800Mbps DDR3 interface is implemented?
If the user is using a Lattice DDR3 memory controller IP core version 1.2 or later, the user can use a different rate of input reference clock. The original clock synchronization module (CSM) in the earlier version DDR3 IP cores require the fixed ...
6321 - CrossLink-NX: Why are there no exception constraints between the byte clock and pixel clock, e.g. set_clock_groups constraints for each clock in the IP LDC file?
The set_clock_groups or any exception constraints were not defined in the IP LDC file as it would be difficult if the IP is used in a system design and the customer wants to analyze the paths between the clocks or does not want the clock domain ...
6396 - Byte-to-Pixel IP v1.4.0: Why are there no exception constraints between the byte clock and pixel clock, e.g. set_clock_groups constraints for each clock in the IP LDC file?
The set_clock_groups or any exception constraints were not defined in the IP LDC file as it would be difficult if the IP is used in a system design and the customer wants to analyze the paths between the clocks or does not want the clock domain ...
1748 - Common Public Radio Interface - IP Core: Do I need to use a clock cleaner when using CPRI IP core (Common Public Radio Interface) with Lattice SERDES based FPGA?
Lattice CPRI IP core (Common Public Radio Interface) supports LatticeECP2/M, LatticeECP3 and LatticeSC. When using the CPRI IP core in REC(Radio Equipment Control,master) mode, it's not necessary to use a clock cleaner since the system provides the ...