5873 - ispMACH 4384 176 TQFP: Bank number for Pin 142 (GX0) is "N/A" instead of "1" on the Constraint Editor

• Related Articles

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

• 7161 - Radiant: How are multiple lines of constraints handled in the device constraint editor?

  Description: When handling multiple constraint commands in a constraint files, there might be confusion in which settings are applied. This FAQ will give examples on how device constraint editor handles it. See examples below for ldc_set_sysconfig ...

• 2378 - Diamond:  In Lattice Diamond, what is the difference between a Pin Layout File and a Pin Out file?

  A Pin Layout File is a report of pin information and assignments in your design. It is created from within the Lattice Diamond Spreadsheet View using File>Export Pin Layout File The Pin Layout File can be a list of available pins, pad names, ...

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

• 7060 - Radiant: When to use a create_clock or create_generated_clock constraint? What are the consequences if a create_clock constraint is used instead of a create_generated_clock constraint?

  Use create_clock constraints when the clock is coming from an input port. Use create_generated_clock constraints when the clock is generated from a module or circuit inside the FPGA design through multiplication or division of a base clock. The ...