6260 - Radiant version 3.0 or earlier: How to solve Nexus Platform SRAM programming issue?

Description:

In Radiant 3.0 or earlier version, the sysConfig has default setting for the JTAG_PORT as DISABLED. So it could lead to JTAG access issue on the device after loading the generated bitstream into the SPI Flash.

Solution:
As a workaround, user may follow the steps below:
A: Remove the bitstream (with JTAG_PORT = Disable) into the SPI Flash memory.
(1) Hold PROGRAMN to low then perform "Erase All" on the Flash content.
Note: Set-up the programmer based on the SPI Serial Flash vendor, and device name.

(2) Release the PROGRAMN once the operation is done.

B: Accessing the SRAM.
(3) After removing bitstream from the SPI Flash with disabled JTAG_PORT, perform JTAG scan to read the device and the board.
(4) Then, perform SRAM Erase, Program and Verify.

If new bitstream will be loaded to the SPI flash, ensure that JTAG_PORT/MASTER_SPI_PORT is enabled this time.
This can be set under "Device Constraint Editor".

• Related Articles

• 6297 - All Nexus: How to solve the issue regarding SRAM erase? Error: "Failed to erase the SRAM..."

  Description: One of the possible causes is that the flash is configuring the SRAM and thus causing access issue with FPGA's SRAM. Solution: To workaround this issue, user may try the following: (1) Hold the PROGRAMN port to 0 (active state/asserted) ...

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

• 7159 - When failing in programming/booting, which information is helpful for tech support to analyze the issue?

  Problem: Programming and booting from both internal flash and external flash are failing. Which information is helpful to tech support? Solution: When failing programming and booting, technical support can help in analyzing the issue by sharing the ...

• 5553 - Why in LCMXO2 part I got the following error message: ERROR - Failed in Function VERIFY_SRAM_DONE_BIT ?

  The "Failed in Function VERIFY_SRAM_DONE_BIT" means that, the Diamond Programmer is unable to determine the statue of the DONE bit in the device's Status Register. This could have happened due to following reasons: The DONE bit is NOT SET due to the ...

• 7152 - EIO for Nexus FPGAs: What does EIO function mean in the pinout file and the purpose of the pins?

  'EIO' function mentioned in the pinout file refers to 'Early I/O Release' enhanced configuration function. Our Nexus device supports this feature to allow the I/O that reside in the I/O Banks on the left and right of the device to release earlier so ...