6811 - Lattice iCECube2: Why does my Constraints for the output of Oscillators in iCECube2 is ignored by the tool?

Description: iCEcube2 only allows an inferred constraint on the internal OSC at its nominal value and Timing Analysis can't be set to a different frequency for the OSC as the user constraint will be ignored. Solution: This can work be around by feeding the output of the oscillator to a PLL (where the PLL is in 1:1 mode, i.e., 48 MHz input and 48 MHz output), then adding a constraint to overconstrain the output of the PLL to 52.8 MHz to cover the 10% tolerance of the OSC.

Related Articles
6536 - Lattice Radiant: How to resolve the issue in generating output bitstream on Radiant's Deployment Tool?
Description: The user encounters an error on the Deployment tool when trying to convert their generated bitstream from Radiant. Solution: The issue on the generation of output bitstream is due to the encrypted bit file generated by the Radiant's ...
3795 - Diamond Deployment Tool: Does the PCF(Pattern Control Format) format supported in the Lattice Diamond Deployment Tool?
The Lattice Deployment Tool already support's PCF format. To generate the PCF file, invoke Lattice Diamond Deployment Tool, Select Tester function type and ATE Output File Format. Both the Agilent HP3070 and HP3065 Tester Types are supported for PCF ...
6785 - 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 ...
2997 - Lattice Diamond: How does the synthesis tool treat the unused input and output ports declared in the RTL code and not used(logic is not being assigned to the IO Ports)?
The synthesis tool will remove the unused Input ports declared in the design. For unused Output ports, the tool can either tie them to the GND or leave them tri-stated. You can check this in the RTL view of the Synthesis tool. It is recommended to ...
6329 - Lattice Radiant: Why do Radiant constraint editors remove customer variables and equations in PDC (constraints) file?
TCL commands and Constraint Commands cannot be joint on to the same constraint file. The Timing and Physical constraints found in constraint file (.pdc) are the only object accepted and read by the tool. The TCL commands for setting certain variables ...

6811 - Lattice iCECube2: Why does my Constraints for the output of Oscillators in iCECube2 is ignored by the tool?

6811 - Lattice iCECube2: Why does my Constraints for the output of Oscillators in iCECube2 is ignored by the tool?

Related Articles

6536 - Lattice Radiant: How to resolve the issue in generating output bitstream on Radiant's Deployment Tool?

3795 - Diamond Deployment Tool: Does the PCF(Pattern Control Format) format supported in the Lattice Diamond Deployment Tool?

6785 - 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?

2997 - Lattice Diamond: How does the&nbsp;synthesis tool treat the unused&nbsp;input and output&nbsp;ports declared in the RTL code and not used(logic is not being assigned to the IO Ports)?

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

2997 - Lattice Diamond: How does the synthesis tool treat the unused input and output ports declared in the RTL code and not used(logic is not being assigned to the IO Ports)?