SLOSE79B August 2022 – October 2023 DRV8462
PRODUCTION DATA
Multiple devices can be connected to the controller with and without the daisy chain. For connecting 'n' number of devices to a controller without using a daisy chain, 'n' number of GPIO resources from controller have to be utilized for nSCS pins. Whereas, if the daisy chain configuration is used, a single nSCS line can be used for connecting multiple devices.
Figure 7-50 shows the topology when three devices are connected in daisy chain. This configuration saves GPIO ports when multiple devices are communicating to the same controller.
The first device in the chain receives data from the MCU as shown in Figure 7-51 for 3-device configuration: 2 bytes of header (HDRx) followed by 3 bytes of address (Ax) followed by 3 bytes of data (Dx).
After the data has been transmitted through the chain, the MCU receives the data string in the format shown in Figure 7-52 for 3-device configuration: 3 bytes of status (Sx) followed by 2 bytes of header followed by 3 bytes of report (Rx).
The header bytes contain information of the number of devices connected in the chain, and a global clear fault command that will clear the fault registers of all the devices on the rising edge of the chip select (nSCS) signal. Header values N5 through N0 are 6 bits dedicated to show the number of devices in the chain. Up to 63 devices can be connected in series for each daisy chain connection.
The 5 LSBs of the HDR2 register are don’t care bits that can be used by the MCU to determine integrity of the daisy chain connection. Header bytes must start with 1 and 0 for the two MSBs.
The status byte provides information about the fault status register for each device in the daisy chain so that the MCU does not have to initiate a read command to read the fault status from any particular device. This keeps additional read commands for the MCU and makes the system more efficient to determine fault conditions flagged in a device. Status bytes must start with 1 and 1 for the two MSBs.
When data passes through a device, it determines the position of itself in the chain by counting the number of status bytes it receives followed by the first header byte. For example, in this 3-device configuration, device 2 in the chain receives two status bytes before receiving the HDR1 byte which is then followed by the HDR2 byte.
From the two status bytes, the data can determine that its position is second in the chain. From the HDR2 byte, the data can determine how many devices are connected in the chain. In this way, the data only loads the relevant address and data byte in its buffer and bypasses the other bits. This protocol allows for faster communication without adding latency to the system for up to 63 devices in the chain.
The address and data bytes remain the same with respect to a 1-device connection. The report bytes (R1 through R3), as shown in Figure 7-52, are the content of the register being accessed.