DLPU048E August 2016 – July 2024
Table 3-6, Table 3-7, and Figure 3-3 describe the SPI bulk write protocol.
MOSI Controller Output, Peripheral input (e.g. Host Output, DLPC230 input):
| DATA BYTE | DESCRIPTION |
|---|---|
| CMD | 1-byte write command op-code |
| Tag | 1-byte identifier used to uniquely mark each command sent by host. |
| Length | Length of the bulk header data (Data 1a, Data 1b). This is always 2 for a bulk write. |
| Data1(a:b) | Bulk header data. The value specifies the length of the bulk payload (1-256 bytes). LSByte = "a". |
| CRC1 | CRC or checksum for the write header. Includes op-code, tag, length, and header data bytes. |
| Data2(a:n) | Bulk write payload data. The number of bytes will vary, and should match the value stored in Data1(a:b). |
| CRC2 | CRC or checksum for the bulk payload. This only includes the bulk payload (Data2). |
MISO Controller input, Peripheral output (e.g. Host input, DLPC230 output):
| DATA BYTE | DESCRIPTION |
|---|---|
| CMD (ACK) | Echo of the received command op-code from the host controller. |
| Tag (ACK) | Echo of the received tag from the host controller. |
| LengthR | Length of the return data. This is always zero for a bulk write. |
| CRC-R | CRC or checksum for the response bytes. This value covers op-code, tag, and length. |
Figure 3-3 SPI Bulk Write