3964 - SED: How to run Soft Error Detect (SED) block when the user logic is running in LatticeXP2 devices?
Description: This article describe the ideal way of using SED block in LatticeXP2 product.
Solution:
According to LatticeXP2 Product Change Notification (PCN)# 02B-12, the SED block cannot be run during normal active operation.
However, the SED function can still be run on a programmed device when the user logic is inactive.
We will not be able to run SED block when the user logic is running.
However, SED block can be active when there is no transition in the user logic (e.g. if the user logic is under reset condition).
Related Articles
5304 - All Devices: Can we access any NON-JTAG port (Wishbone, I2C, SPI or CPU) while SED is running in user mode?
No. While the SED is running if the user tries to access the device using any non-jtag port (like WB, I2C, SPI or CPU) the SED will be terminated.
2123 - MachXO2: Can the user use MachXO2's Embedded Functional Block (EFB) I2C pins (SCL and SDA) to work with soft (NOT EFB) I2C logic?
Definition: The MachXO2's EFB Primary I2C have dedicated pins. User can't use them for general purpose when enabled for EFB I2C usage, by enabling the Primary I2C Port. However, if the I2C Primary port is not enabled, then the I2C IOs become User ...
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 ...
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 ...
7110 - SEDC: Why does errcrc_o asserts when a correctable error is detected?
The sedc_errcrc_o normally asserts when there is a soft-error detected. It will transition from high to low in the second run if the single-bit soft-error is correctable. To support this, the user has to monitor the 2 clock cycle low pulse of BUSY ...