Can the bitstream file generated from the 80-pin Crosslink Packages selection be programmed across any of the Crosslink packages, i.e LIF-MD6000-6JMG80I, LIA-MD6000-6JMG80E, LIA-MD6000-6KM80E?

• Related Articles

• Lattice Diamond: What is the behavior of my generated bitstream if i do not have any LSC_SW_XO3D_SECURITY_ENCRYPT feature line in the license file when signing a bitstream?

  The bitstream gets generated without any error or warning. If the license feature of LSC_SW_XO3D_SECURITY_ENCRYPT is removed, Bitgen will generate plain a bitstream file, it will ignore the Security setting that is added in the bitstream.

• 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: Why is the bitstream file size fixed (ex. Always 1.8Mb) even in small designs for Certus-Pro NX?

  Certus Pro-NX, the BIT file size on simplest design is 1.8MB, while for Crosslink-NX it generates 790KB. Whenever design becomes more condensed (especially more usage of EBRs and LRAMs) bitstream size will increase from that 1.8MB. The bitstream size ...

• 7040 - Programmer version 3.12: Why is the checksum value different between bitstream generated with Diamond 3.12 and 3.10.

  Starting from Diamond version 3.12, bitstream checksum value is changed from 4 bytes to 2 bytes checksum output when perform operation “SPI Flash Calculate File Size Checksum” in programmer.

• 2372 - LatticeECP3:  Can the bitstream used for the regular device be programmed in the low power device of LatticeECP3?  

  Yes. The bit stream formats are the same for the regular LatticeECP3 and the low power LatticeECP3 devices. For example, LFE3-70EA-8TN1156C and the low power version "LFE3-70EA-8LTN1156C" can use the same bitstream file. There is no need to generate ...