6452 - ECP2/ECP2S: Does ECP2 and ECP2S devices bitstream compatible?

• Related Articles

• 3036 - Lattice EPC2/S: Why is the encrypted bitstream not working for Lattice ECP2/S device?

  For the encrypted bitstream to work in LatticeECP2/S device, ensure the following: For power-up, VCC must reach its valid minimum value before powering up VCCAUX (LatticeECP2/M “S” version devices only). Refer to LatticeECP2/M Family Data Sheet for ...

• Why FPGA Programming Failure When JTAG Chain Has 7 or More Devices?

  DESCRIPTION When programming Lattice FPGA devices via SPI Flash using a JTAG chain, the Erase-Program-Verify (EPV) operation fails deterministically starting from the 7th device in the chain. Chains of 6 devices or fewer complete SPI Flash EPV ...

• 5646 - ECP5/ECP5-5G/CrossLink: If the user wants to update the bitstream in the field and encrypt the bitstream so that it can only be used on my product, is there a solution available in the CrossLink device?  If yes, in what document is it stated?

  Encrypting the bitstream is only available with Lattice XP2, and ECP products. Crosslink, does not support a bitstream encryption solution on the other hand.

• 7149 - Nexus Devices: What is the maximum SPI Flash size that Nexus devices can boot?

  Nexus devices can boot up to 4 Gb as long as Control register 1 bit 14 (32-bit SPIm Commands) and bit 17(32-bit SPIm Address) is set to 1. See below: By default device boots at three byte address and three byte commands settings. By setting these ...

• 5501 - MachXO3: Can MACHXO3 devices be re-programmed over I2C in User Mode, in addition to access Embedded Function Block (EFB)'s Primary hardened User I2C, along with Primary Configuration I2C?

  Description: This article explores the possibility of MACHXO3 devices be re-programmed over I2C in "User Mode", in addition to access Embedded Function Block (EFB)'s Primary hardened User I2C, along with Primary Configuration I2C. Solution: Both ...