MachXO2: How to account for frequency tolerance when using the internal OSC?

Workaround 1: Thus, if you would like to check the oscillator tolerance, you will change the nominal value in your RTL, let MAP and PAR automatically constrain the frequency, and check the PAR Trace. If the design is passing, then it is guaranteed to work between the frequencies. Workaround 2: The user can also retain the required frequency in RTL and constrain the frequency to the next highest in Spreadsheet View. Timing Analysis will be done based on the frequency in the constraint.

Related Articles
4072 - Diamond 3.3 / MachXO2: How can a user constraint Place & Route (PAR) for the MachXO2 built in oscillator to cover the 5% frequency tolerance variation?
Description: In Lattice Diamond 3.3 and later, PAR will accept a frequency constraint up to 5.5% above the nominal frequency setting to cover the timing variation in the oscillator over PVT. This can be done by adding a constraint in the Lattice ...
1713 - Diamond: When using the FREQUENCY preference, when would I want to use the HOLD_MARGIN keyword?
The HOLD_MARGIN preference is used to indicate the extra hold margins user can apply to the frequency preferences. If HOLD_MARGIN is not specified The 'min' path is optimized using the default timing numbers for each components, this could result in ...
6125 - ispLEVER Classic: OCSTIMER (On Chip OSC) sample Verilog code has an issue with the RTL simulation using ModelSim
Description: There is a typo error on the ispLEVER Classic OSCTIMER sample Verilog code. Solution: Please change the small letter to an upper case. Please note that Verilog is a case-sensitive language and differences in incorrect cases will affect ...
6894 - Diamond / Synplify Pro: Why is the Frequency for Synplify Pro Strategy Setting is set to 1 MHz when using the Area preset strategy?
When selecting Area preset strategy, the Frequency setting on the Synplify Pro will change to 1 MHz. If the user changes Frequency setting this to a mid or higher value, the optimization will try to meet that higher frequency and therefore the area ...
7739 - Radiant 2024.2 SP1: How can I resolve the PAR internal fatal error that only occurs on my design using Radiant 2024.2 SP1?
Description: In Radiant 2024.2 SP1, there is PAR internal fatal error occurs due to a crash on the STA. This error is not limited to a specific device. A symptom that the design is affected by this issue is if this design is passing PAR on older ...

MachXO2: How to account for frequency tolerance when using the internal OSC?

MachXO2: How to account for frequency tolerance when using the internal OSC?

Related Articles

4072 - Diamond 3.3 / MachXO2: How can a user constraint Place &amp; Route (PAR) for the MachXO2 built in oscillator to cover the 5% frequency tolerance variation?

1713 - Diamond: When using the FREQUENCY preference, when would I want to use the HOLD_MARGIN keyword?

6125 - ispLEVER Classic: OCSTIMER (On Chip OSC) sample Verilog code has an issue with the RTL simulation using ModelSim

6894 - Diamond / Synplify Pro: Why is the Frequency for Synplify Pro Strategy Setting is set to 1 MHz when using the Area preset strategy?

7739 - Radiant 2024.2 SP1: How can I resolve the PAR internal fatal error that only occurs on my design using Radiant 2024.2 SP1?

4072 - Diamond 3.3 / MachXO2: How can a user constraint Place & Route (PAR) for the MachXO2 built in oscillator to cover the 5% frequency tolerance variation?