<div>Lattice Radiant version 2022.1 and 2023.1: Why does the Radiant Timing Report indicate an unconstrained path for path with applied constraint such as <i>set_input_delay</i>?<br></div>

• Related Articles

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

• What would happen on the timing analysis if user set a negative value on the set_input_delay constraint?

  User can either set the negative value on the -max option or on the -min option: 1. Setting a negative value for the -max option of the set_input_delay: When user set a value of the set_input_delay for the -max option, this applies to the setup ...

• Radiant version 2023.1 or newer: Are there priority rules when multiple timing exception constraints are applied on a specific timing path?

  Kindly refer below to the exception priority: 1. set_false_path 2. set_max_delay or set_min_delay 3. set_multicycle_path A couple of notes: 1. set_max_skew applies to the timing path together with exception constraint that takes priority. 2. ...

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

• All Nexus / Radiant 2023.1 or earlier: How are the clock-to-out max and clock-to-out min values on the I/O Timing Analysis report calculated?<div><br></div>

  Clock-to-out max corresponds to the arrival time of the data of the external timing path when setup time is analyzed. Clock-to-out min corresponds to the arrival time of the data of the external timing path when hold time is analyzed. If there are ...