Lattice Radiant: Why do Radiant constraint editors remove customer variables and equations in PDC (constraints) file?

• Related Articles

• Radiant and Diamond: HDL pin constraints not seen in Spreadsheet View/Device Constraint Editor

  Description: In Lattice Radiant and Diamond, while using the Spreadsheet View/Device Constraint Editor, it is possible to not see the HDL pin constraints reflected in GUI. Solution: This may be because the pins mentioned in the lines of code have ...

• Radiant / Synplify Pro: Why does Postsyn reject the user's pre-synthesis constraints on an FDC file when Reveal Inserter is included in the project?

  Description: The issue is caused by some differences in the behavior of the Verific and Synplify language parsers related to the handling of the escape characters in the instance name. Solution: This is not yet fixed by Synplify Pro and no timeline ...

• Lattice Radiant: How do i constraint a path with false path at Pre-Synthesis?

  It is not recommended to constraint from pin to pin in pre-synthesis path thus set_false_path may not be applicable. Instead, use post-synthesis path to do the set_false_path constraint. (use PDC)

• 711 - Lattice ispVM system: What are the constraint files used by ispLEVER Classic?

  The ispLEVER Classic software employs three types of constraint files: Lattice constraint input file (.lci), Lattice constraint temporary file (.lct), and Lattice constraint output file (.lco). The .lci file consists of two types: the parent .lci ...

• Lattice Radiant: Why does the constraint coverage did not improve after using set_false_path constraint?

  By Default, set_false_paths does not improve constraint coverage, however For Radiant 2023.1 or later, the user can use the Timing Command Line Option "-false_covers" to add in the false paths to the timing coverage. This can be applied on the ...