7113 - Lattice Radiant: What is a possible reason for an LPDDR4 Memory Controller timing violation for Nexus Devices?
The timing issue can be due to the CPU.
The LPDDR4 MC instantiates a small Risc-V CPU which implements the LPDDR4 training routes. This CPU runs on pclk_i which can be at a different frequency with aclk_i.
The maximum frequency for pclk_i, when the device performance grade is 7 is around 80MHz with +/-10 tolerance.
Related Articles
7010 - Radiant 2023.2 and below: How to create a design-specific BSDL for Nexus devices?
You can create an application-specific BSDL file using Radiant Deployment Tool. However, the tool only supports specific BSDL files that target non-volatile memory (using *.jed file), which is inapplicable for Nexus devices that target SRAM (*.bit).
6575 - Lattice Nexus devices using Reveal: no output from LVDS IP
Description: While debugging your Radiant design using Reveal, users may observe that there is no output from their LVDS IP. Solution: When Reveal is inserted in Nexus devices, on certain designs, the GSR net gets assigned to a reset signal that may ...
6470 - All Nexus / Radiant version 2023.1 or earlier: Is it correct to think that STA is performed under worst-case conditions for both setup/hold for Nexus Devices?
Radiant timing analysis is performed under worst-case conditions for both setup/hold. As an example, consider the Nexus devices. By default, hold analysis is performed using the ‘m’ speed grade which represents the highest performance grade using the ...
6103 - Lattice Radiant/Timing Analyzer: Is there a document describing how to use Radiant Timing Analyzer?
URL below is the Lattice Radiant Tutorial document. Navigate to page 38 for simple steps on how to use Radiant Timing Analyzer. https://www.latticesemi.com/view_document?document_id=53231
7766 - iCEcube2 Modelsim: How do I run Timing simulation for iCECube2 Devices?
In order to ran through Timing simulation for iCECube2 Devices, You would need the following Libraries: 1) sb_ice_ipenc_modelsim.v [Optional: Add this if Hardened IPs are present in your design, Example: SPI, i2C] 2) sb_ice_lc.v 3) sb_ice_syn.v 4) ...