Lattice Radiant: Why is the bitstream file size fixed (ex. Always 1.8Mb) even in small designs for Certus-Pro NX?

• Related Articles

• 3514 - Diamond: Why is there a difference in the bitstream file size with a small logic modification in LatticeECP3?

  The bitstream file size increases even with a small modification. The bitstream comprises both fuse data frames (SRAM configuration bits) and EBR initialization information. Fuse data frame size is fixed for the given device irrespective of how huge ...

• 296 - Lattice Diamond: Does the configuration file (such as an ECP3 bitstream) for SPI flash remain at fixed size regardless the size of  the FPGA design?

  The configuration file that is used for an SPI flash(or for JTAG download), remains the same size regardless the resource (such as logic cell) percentage utilization in the FPGA design.

• Lattice Radiant 2.1: How do I generate the bitstream for crosslink-nx with Radiant v2.1? 

  If the selected device on Radiant is an ES1 device, the bitstream can only be generated on R2.0. R2.1 can only allow bitstream generation for ES2 devices.

• Lattice Radiant 3.1.0 : Does SEI editor tool supports CertusPro-NX?

  Radiant 3.1.0.43.2 version has disabled SEI editor tool for CertusPro-NX. The later version of Radiant supports the SEI editor tool. (Ex: Radiant 3.1.1.249.0) For any other concern, file TechSupport ticket to assist you. ...

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