<div>Radiant: What type of clocks do the Clock Port column of the I/O Timing Analysis Report refer to?</div>

For I/O timing analysis, the "Clock Port" column/field could refer to the following depending on the destination clock:

1. Internal oscillator clock: If the destination clock is directly from the internal oscillator, or if the destination clock is from a PLL clock output sourced from the internal oscillator.

2. External clock port: If the destination clock is directly from an external clock port or if the destination clock is from a PLL clock output source from an external clock port.

In this example case, since the destination clock of the path (based on the set_false_path constraint) is from a PLL clock output source from an external clock port, then the external clock port (CLK_25MHz) will be on the "Clock Port" column of the I/O timing analysis report.

See timing report section for the timing path:

Related Articles
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 ...
740 - Lattice ispLEVER: Timing Analysis: What is the I/O Timing Report?
Lattice ispLEVER: Timing Analysis: The I/O Timing Report (.ior) is a used to report the IO timing analysis of your design. Input Setup and Hold times (Tsu, Th) and Clock-to-Output times (Tco) are reported. The IO Timing Report sweeps across all the ...
All Nexus / Radiant 2023.1 and older: How can the user calculate the Clock-To-Out (min and max) values and Input setup/hold values of the I/O Timing Analysis report?
The Clock-to-Out max value is the setup analysis' arrival time of data with the output port's external timing path. The Clock-To-Out min value is the hold analysis' arrival time of data with the output port's external timing path. By default, timing ...
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 ...
Radiant: Why is the result of my timing different on the PAR report compared with the TWR report?
The result from .PAR and from .TWR is expected to be different. For Radiant 2023.2, multi-corner timing analysis is implemented, the idea is for: A. 2023.2 1) PAR Timing Analysis (.PAR) - The Timing model used is the model with "WORST" case at ...

<div>Radiant: What type of clocks do the Clock Port column of the I/O Timing Analysis Report refer to?</div>

<div>Radiant: What type of clocks do the Clock Port column of the I/O Timing Analysis Report refer to?</div>

Related Articles

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>

740 - Lattice ispLEVER: Timing Analysis: What is the I/O Timing Report?

All Nexus / Radiant 2023.1 and older: How can the user calculate the Clock-To-Out (min and max) values and Input setup/hold values of the I/O Timing Analysis report?

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

Radiant: Why is the result of my timing different on the PAR report compared with the TWR report?

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