7239 - Diamond / FDP-Link Receiver IP version 1.4.0: How can user resolve the timing violations on paths within the FDP-Link Receiver IP related to the reset pin of clkdivg instance and the pll lock of the bw_align instance of the IP? 

• Related Articles

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

• 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)?

  These timing violations only occur if we use soft JTAG for Reveal. To handle this, user can use a set_false_path constraint between the clocks as these paths are invalid.

• 200 - Diamond: How do user get a reasonable I/O timing report when PLL phase shift is very large?

  When user change the PLL phase to improve the Tco, user caan program the PLL phase delay by more than 180 degree, e.g. 315 degree. Its equivalent effect is to advance 45 degree if one clock cycle latency is acceptable. But the Lattice software will ...

• 692 - Lattice Diamond:  Does the Lattice timing analysis tool only analyze 4096 timing paths at maximum?

  The timing analysis tool does analyze all timing paths in your design. For timing closure, the analyzer will address all failing timing paths even if they exceed 4096 paths. It is for MAP and Place & Route TRACE reporting purpose only that up to 4096 ...

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