SWRS350B December 2025 – September 2026 IWRL6432WMOD
PRODUCTION DATA
The SPI packet format consists of the SPI header and SPI command/ response data.
Figure 5-9 SPI Data FormatThe SPI header of 16 bytes is further divided with CRC-32 for message authentication , command or response Identifier, long and short message size with few reserved bytes.
| Byte Offset | Field Name | Size (bytes) | Description |
|---|---|---|---|
| 0-3 | CRC-32 | 4 | CRC-32 computed over bytes 4–15 of the header and the full payload. Used for message authentication. |
| 4-5 | Message ID | 2 | Identifies the command (host-to-module) or response (module-to-host). See API command table. |
| 6-7 | Short Message Length | 2 | Length of the payload when payload is 255 bytes or less. Set to 0xFFFF if long length is used. |
| 8-11 | Long Message Length | 4 | Length of the payload when payload exceeds 255 bytes. Set to 0x00000000 if short length is used. |
| 12-15 | Reserved | 4 | Set to 0x00000000. Must not be modified. |
Figure 5-10 SPI Header FormatThe SPI command/response is further divided to command header and variable length command/response. The max variable length can be 106bytes.
Figure 5-11 SPI Command Format| Byte Offset | Field Name | Size (bytes) | Description |
|---|---|---|---|
| 0-1 | Command/Response Code | 2 | Opcode identifying the specific API command or response type. |
| 2-3 | Payload Sub-length | 2 | Length of the variable data field that follows. |
| 4-N | Variable Data | 0-102 | Command arguments or response data. Format is command-specific. Maximum 102 bytes. |