SBASAE4 December 2025 ADS125P08
PRODUCTION DATA
After the CS-FWD mode is enabled, the UDP communication is started by sending the CS Forward Header frame as shown in Table 7-42. The first byte on SDI includes the CS forward index or SPI index as 4 MSBs. This is the destination device selection, 0h00 to 0h0B where 0h00 is destination device 1, 0h01 is destination device 2 and so on. The first byte on SDI also includes the number of frames to be transferred as 4LSBs. The second byte on SDI includes the CRC for the preceding data, if CRC is enabled. The third byte (do not care) is always required: When in CS-FWD mode, three bytes per frame are always required for the header frame to communicate with the CS-FWD controller.
| SIGNAL | 1stBYTE | 2ndBYTE | 3rdBYTE |
|---|---|---|---|
| SDI |
SPI index (4 MSBs) and frame# bits (4 LSBs) |
CRC (if CRC enabled) |
Don’t care |
| SDO |
FFh |
1stbyte received on SDI |
CRC check result (if CRC enabled) |
The SPI index (4 MSBs) of the first byte in the header indicates which destination device is selected, Table 7-43 describes the exact mapping of these bits to a specific destination device.
| SPI INDEX | DESTINATION DEVICE SELECTED |
|---|---|
| 0000b | The device, ADS125P08 |
| 0001b | Destination device 1, connected to GPIO0 |
| 0010b | Destination device 2, connected to GPIO1 |
| 0011b | Destination device 3, connected to GPIO2 |
| 0100b | Destination device 4, connected to GPIO3 |
| 0101b | Destination device 5, connected to AGPIO0 |
| 0110b | Destination device 6, connected to AGPIO1 |
| 0111b | Destination device 7, connected to AGPIO2 |
| 1000b | Destination device 8, connected to AGPIO3 |
| 1001b | Destination device 9, connected to AGPIO4 |
| 1010b | Destination device 10, connected to AGPIO5 |
| 1011b | Destination device 11, connected to AGPIO6 |
| 1100b | Destination device 12, connected to AGPIO7 |
| all other codes | Reserved |
The frame number bits (4LSBs) of the first byte in the header in Table 7-42 sent from the host indicate the number of frames sent to the selected destination device as shown in Table 7-44. After the specified number of frames are sent to the selected destination device, the CS-FWD controller expects another header frame with new information regarding the next destination device selection and number of frames to be sent. The CS-FWD controller stays in CS-FWD mode until the user explicitly chooses to exit this mode, see the Disabling the CS-FWD mode section for details on exiting the mode.
| FRAME NUMBER LSBS | NUMBER OF CS-FWD FRAMES SENT |
|---|---|
| 0000b | 1 |
| 0001b | 2 |
| 0010b | 3 |
| 0011b | 4 |
| ... | ... |
| 1110b | 15 |
| 1111b | 16 |
During an UDP sequence, a header response frame is sent from the device on SDO as shown in Table 7-42, this response is denoted as Ack in the following, as shown in Figure 7-37. This consists of bits[23:16] = FFh to represent the device writing to the host, bits[15:8] repeat the data sent to initiate the UDP (first byte on SDI), and Bits[7:0] are a correct CRC for the preceding data using the polynomial x8 +x2 + x + 1. This byte of CRC is required only when CRC is enabled for the SPI, otherwise the byte is 0hFF.
The host can distinguish whether the host is communicating with the CS forward controller or any other destination device based on the SDO received. If talking to the controller, the host receives the SDO as FFh and the mirrored bytes received by the controller. So the host can check if the bytes received by the controller are correct or not and then decide how to respond: keep timeout and re-send the commands to the controller if the bytes are incorrect.
Figure 7-37 shows a timing diagram for a typical CS-FWD communication sequence. In the first header frame shown, the SPI index is set to target device M. Therefore, in the subsequent frames, the CS signal is only forwarded to device M (j is the number of frames for communication to device M as specified in the header frame). In the 2nd header frame, device N is specified and communication to device N is performed in subsequent frames (k is the number of frames for communication to device N).
Figure 7-37 also indicates the responses sent from the target device to SDO. Simultaneously with each header frame, the Ack frame of the target device is visible on SDO. Thereafter, the target device sends command or data bytes to SDO depending on the commands used, for simplicity those are indicated by Ack(M) for device M and Ack(N) for device N in Figure 7-37.
The condition for a qualified forward frame is to have a minimum of at least 8 SCLK cycles when CSn is low. However, the frames can be longer than 8 SCLK cycles, and subsequent frames can differ in length. There is no maximum limit on the frame length.
The following error handling is recommended to provide robustness of the communication with and without CRC enabled:
Figure 7-38 depicts the state diagram for the CS-FWD controller. As soon as the CS forward is enabled, the controller is expecting to receive a valid header frame. Once a valid header frame is received, the communication with the selected destination device is started, and continues until the pre-defined number of frames are completed, or a timeout occurs, or the CS forward mode is disabled in the SPI controller device.