JAJSJM2B July 2022 – April 2024 TPS929240-Q1
PRODUCTION DATA
デバイスごとのパッケージ図は、PDF版データシートをご参照ください。
The FlexWire is a UART-based protocol supported by most microcontroller units (MCU). Each frame contains multiple bytes started with a synchronization byte. The synchronization byte allows LED drivers to synchronize with master MCU frequency, therefore saving the extra cost on high precision oscillators that are commonly used in UART / CAN interfaces. Each byte has 1 start bit, 8 data bits, 1 stop bit, no parity check. The LSB data follows the start bit as the below figure describes. The FlexWire supports adaptive communication frequency ranging from 10kHz to 1MHz. The protocol supports master-slave with star-connected topology.
The FlexWire is designed robust for automotive environment. After the slave device receives a communication frame, it firstly verifies its CRC byte. When CRC is verified, the slave device sends out response frame and clears the watchdog timer. In addition, if one communication frame is interrupted in the middle without any bus toggling for a period longer than timeout timer t(DBWTIMER), the TPS929240-Q1 resets the communication and waits for next communication starting from synchronization byte. It is also required for idle period between bytes within t(DBWTIMER). The timeout timer t(DBWTIMER) is programmable by configuration register DBWTIMER. TI recommends using a longer timeout setting for low baud rate communication to avoid unintended timeout and using a shorter timeout setting for high baud rate communication.
If communication CRC check fails, the TPS929240-Q1 ignores the message without sending the feedback. The master does not receive any feedback if the communication is unsuccessful. In this case, the communication can be reset by keeping communication bus idle for t(DBWTIMER), which forces the TPS929240-Q1 to clear its cache and be ready for new communication.
FlexWire supports both write and readback. Both write or readback communication supports burst mode for high throughput and single-byte mode. Figure 6-11 describes the frame structure of a typical single-byte write action. The master frame consists of SYNC, DEV_ADDR, REG_ADDR, DATA and CRC bytes. After CRC is verified, the slave immediately feeds back ACK byte. Figure 6-12 describes the frame structure of a typical single-byte readback action. The master frame consists of SYNC, DEV_ADDR, REG_ADDR, and CRC bytes. After CRC is verified, the slave immediately feeds back DATA and ACK bytes.
BYTE NAME | LENGTH (byte) | DESCRIPTION |
---|---|---|
SYNC | 1 | Synchronization byte from master |
DEV_ADDR | 1 | Device address bit, r/w, broadcast, burst mode |
REG_ADDR | 1 | Register address |
DATA_N | Variable (1, 4, 16, 24) | N-th byte data content |
CRC | 1 | Cyclic redundancy check (CRC) for DEV_ADDR, REG_ADDR and all DATA bytes |
STATUS | 1 | Acknowledgment (Return FLAG_ERR register value) |