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 behave incorrectly. Hence causing Reveal and possibly other circuits not to function properly.
To resolve this, please disable the GSR option in the Strategy Settings:
Related Articles
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: IP signals are grayed out in Reveal Inserter
Description: In Radiant, users may see that they are unable to trace some IP signals in Reveal Inserter. It will appear grayed out like the following: Solution: Please check if the IP you are using has an option to remove Tristate Buffers. If so, ...
5075 - How to use Reveal with Soft JTAG for debugging the design?
See the following example from the CrossLink/LIFMD device family, which does not provide a hard JTAG block. Therefore, Reveal JTAG support is implemented using Soft JTAG debugger logic and GPIO pins will be used for four JTAG pins (JTAG_TCK, ...
7469 - Lattice Reveal: What should be checked if a Reveal Error <i>Core0 incorrect pattern readout</i> is encountered?
First, try to adjust the TCK Low pulse width delay to a certain value (usually between 5 and 10). This can be done in the �Design > Cable Connection Manager� settings. If above suggestion does not solve the error, verify the following items: (1) ...
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).