6771 - Radiant 2023.2 SP1 or earlier: How can user handle clock-domain-crossing (CDC) paths timing violations between rvlclk and another clock of the design (clk)?

• Related Articles

• 134 - Diamond: How can user block clock domain transfers where there is already synchronizer circuits in place?

  The Lattice Static Timing Analyzer Trace analyzes all clock domain transfers in which it can relate the source and destination clock domains. This may not always be desired. User may utilize their own synchronizer to handle the transfer between the ...

• 1964 - Diamond: How can users disable irrelevant clock domain crossings during the device implementation?

  Timing paths that contain clock domain crossings are paths between two registers that are clocked with two clocks. After performing timing analysis using Place and Route TRACE, such timing paths usually have the following source and destination ...

• 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 ...

• 7134 - Diamond: Is there a section or a tool where user can find the metastable CDC paths and if they are properly handled or not with FIFO or synchronizer FFs?

  In the timing report, there is a Clock Domains Analysis (CDC) section. It doesn't report if the CDC is handled properly through synchronizers or FIFOs. This should be the designer's responsibility, as we currently do not have a DRC that checks for ...

• Radiant: How does the user interpret the Single Clock Domain table entries on the Clock Summary section of the Place & Route Timing Analysis Report?

  The Single Clock Domain table of the Clock Summary Section of the Place & Route Timing Analysis report: There are three values on this table: 1. The Target is the frequency or period based on the clock constraint. This should always be the lowest of ...