7098 - MachXO2/MachXO3: When using SSPI to Wishbone RD (FPGA-RD-0219) for MachXO2 failure is experienced when trying to do "Background Erase, Program, and Verify". How to fix it?
Problem:
When using SSPI to Wishbone RD (FPGA-RD-0219) background programming fails. How to solve the issue?
Solution:
When using the SSPI to Wishbone RD for MachXO2, please make sure that GSR for synthesis and map design are turned off.
Related Articles
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 ...
7740 - How to enable SSPI programming in MachX03-9400 Development Board
Setup to enable SSPI in MachX03-9400 development board. Connect to JP2, MCLK, SI, SO, SS, 5V SPI, GND to USBN programming cable. Connect FTDI, do a JTAG chain scan, make sure JTAG can program. Connect USB programming cable. Set to Slave SPI ...
5494 - I2C: What is difference between option "I2C Erase,Program,Verify,Feature" and option "I2C Program Feature Row"?
Description: The I2C Erase, Program, Verify option requires that the Feature Row be programmed prior to the execution of the "I2C Erase, Program, Verify" operation. This operation checks for the Feature Row match between the device and the JED file, ...
7757 - Radiant Programmer: What is Erase, Program, Verify Quad 1 operation used for?
Description: Erase, Program, Verify Quad 1 enables that QE bit to '1'. In general, there are two (2) requirements/steps to enable booting from external SPI Flash through x4 (QUAD Mode) Step 1 - Convert the bitstream file into hex (Quad I/O read mode) ...
6460 - LatticeECP2/M: "ERROR - Failed in Function VERIFY_STATUS (see log file for more details)" - possible issue when trying to configure an FPGA using HW-USBN-2B?
Description:Error message: ERROR -Failed in Function VERIFY_STATUS (see log file for more details) Solution:It is possible that the issue came from a microcontroller connected to the FPGA's PROGRAMN pin. This pin is intended to hold off the FPGA ...