SPRUI33H November 2015 – June 2024 TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1
The FSI supports a SPI compatibility mode. While the FSI can communicate with a standard SPI module, the FSI supports a limited configuration. The features of this compatibility mode are:
Table 28-11 lists the frame structure of the FSI-SPI compatibility mode. Each frame phase is present in this mode. If the FSI is transmitting to a standard SPI module, the SPI must decode the frame structure. Similarly, if the FSI is configured as a SPI slave, the standard SPI must encode the transmission to be sent.
Idle State | Start of Frame | Frame Type | User Data | Data Words | CRC byte(1) | Frame Tag | End of Frame | Idle State |
---|---|---|---|---|---|---|---|---|
1001 | 4 bits | 8 bits | 1-16 words | 8 bits | 4 bits | 0110 |
Because of the requirement that the standard SPI module encodes the various frame data, this limits the type of modules that can be connected to the FSI in SPI mode. The paired SPI module must have enough functionality to encode and decode the frames.
If the FSI is transmitted to a standard 16-bit SPI, the data is arranged in the following manner. The example provided in Table 28-12 assumes a DATA_2_WORD frame has been sent.
SPI Data | Data Contents |
---|---|
SPI word 0 | 1001, 0100, 8-bit User Data |
SPI word 1 | Data word 1 |
SPI word 2 | Data word 2 |
SPI word 3 | 8-bit CRC, 4-bit Frame Tag, 0110 |