2663 - Programmer: Why do I observe the JTAG ID Code of the device in bit reversed format when I transmit read ID instruction in Slave SPI Mode?

This is the usual way of sending the device JTAG ID of the device. In order to be compliant with the IEEE Std.1149.1 Test Access Port and Boundary-Scan Architecture, bit 0 (LSB) of the device ID must be the first bit to be sent out of the device. The last bit is bit 31 (MSB).

Users who write their own Slave SPI interface controller must be aware of this before hand. If using Lattice Slave SPI embedded flow, you need not care about this reversal as Lattice's SSPI embedded files handle these issues.

Related Articles
Radiant versions 2023.1 and 2023.2 "Error 71241007 Map ERROR <71241007> - When JTAG_PORT and SLAVE_SPI_PORT are both set to user mode (disabled), at least one of SLAVE_I2C_PORT or SLAVE_I3C_PORT must be enabled"
Description: In Radiant versions 2023.1 and 2023.2, when the user sets all of the configurations ports as DISABLED on the Device Constraints Editor - Global Tab, the user will experience the following error: "Error 71241007 Map ERROR <71241007> - ...
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 ...
ECP5 / Diamond 3.14: Why does my design get a Map device oversize error related to PLL for LFE5U-12F in with Diamond 3.14, but completes map successfully in earlier releases of Diamond software?
In Diamond version 3.14, there is a bug where it incorrectly limits the number of PLLs in the device to 0 for LFE5U-12F. Example error message: ERROR - (device oversize error). The number of PLL components needed (1) exceeds the number available. ...
641 - Lattice ispVM: How to create a single bit file to program two FPGA's from one SPI Flash?
As shown in Figure 15-2 of TN1108 (LatticeECP2/M sysCONFIG Usage Guide), users can configure two Lattice FPGA's from one SPI flash. The first device is programmed in SPI mode, whereas the second device is programmed in Slave Serial mode. To use this ...
2531 - Deployment Tool: Why is the bit count for a Serial Vector Format Verify operation greater than my BIT file?
Solution: The number of bits shifted for a Verify operation can be larger than the bit count of the base BIT file for the FPGA. How many extra bits typically depends on the communication interface used. When using the JTAG port the bit counts will be ...

2663 - Programmer: Why do I observe the JTAG ID Code of the device in bit reversed format when I transmit read ID instruction in Slave SPI Mode?

2663 - Programmer: Why do I observe the JTAG ID Code of the device in bit reversed format when I transmit read ID instruction in Slave SPI Mode?

Related Articles

Radiant versions 2023.1 and 2023.2 "Error 71241007 Map ERROR &lt;71241007&gt; - When JTAG_PORT and SLAVE_SPI_PORT are both set to user mode (disabled), at least one of SLAVE_I2C_PORT or SLAVE_I3C_PORT must be enabled"

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

ECP5 / Diamond 3.14: Why does my design get a Map device oversize error related to PLL for LFE5U-12F in with Diamond 3.14, but completes map successfully in earlier releases of Diamond software?

641 - Lattice ispVM: How to create a single bit file to program two FPGA's from one SPI Flash?

2531 - Deployment Tool: Why is the bit count for a Serial Vector Format Verify operation greater than my BIT file?

Radiant versions 2023.1 and 2023.2 "Error 71241007 Map ERROR <71241007> - When JTAG_PORT and SLAVE_SPI_PORT are both set to user mode (disabled), at least one of SLAVE_I2C_PORT or SLAVE_I3C_PORT must be enabled"