Nexus devices with Reveal: boot issue

• Related Articles

• Lattice Nexus devices using Reveal: no output from LVDS IP

  Description: While debugging your Radiant design using Reveal, users may observe that there is no output from their LVDS IP. Solution: When Reveal is inserted in Nexus devices, on certain designs, the GSR net gets assigned to a reset signal that may ...

• 380 - ispLEVER Classic/Diamond Reveal Analyzer: using a JTAG chain with multiple devices

  Reveal Logic Analyzer can be used for On-Chip Debug even if the targeted device is a JTAG chain with multiple devices. Use ispVM to define the JTAG chain and the position of the targeted device in the chain. Then, save the chain (.xcf) file and ...

• Radiant 2023.2 and below: How to create a design-specific BSDL for Nexus devices?

  You can create an application-specific BSDL file using Radiant Deployment Tool. However, the tool only supports specific BSDL files that target non-volatile memory (using *.jed file), which is inapplicable for Nexus devices that target SRAM (*.bit).

• 6694 - Nexus: Why the JTAG_PORT/SLAVE_SPI_PORT pins are not usable as GPIO in USERMODE in Nexus Device Family?

  This is a known issue for Nexus Devices and will be fixed as soon as possible for the meantime to use JTAG_PORT/SLAVE_SPI_PORT ports in user mode as GPIO please enable SLAVE_I2C/I3C_PORT to proceed; the downside we are preserving the IOs as SDA and ...

• <div>All Nexus / Radiant version 2023.1 or earlier: Is it correct to think that STA is performed under worst-case conditions for both setup/hold for Nexus Devices?<br></div>

  Radiant timing analysis is performed under worst-case conditions for both setup/hold. As an example, consider the Nexus devices. By default, hold analysis is performed using the ‘m’ speed grade which represents the highest performance grade using the ...