This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[FAQ] DRV2625: Using DRV260x or DRV262x with single I2C Master

Part Number: DRV2625
Other Parts Discussed in Thread: TCA9548A, TCA9554

The DRV262x and DRV260x devices has a TI haptic broadcast mode where it will make the device respond to the slave address 0x58 (7-bit) or 1011000 in binary. This mode is useful in the event that multiple haptic drivers implementing the TI haptic broadcast mode as installed in the system. In such a scenario, writing the GO bit to the 0x58 slave address will cause all haptic drivers to trigger the process at the same time.

Due to unchangeable slave address you would need to use the EN pins connected to I/O pins individually for the DRV260X or in the case of DRV262x would need to use a chip like the TCA9548A to separate the I2C lines in order communicate with each chip individually instead of it being broadcast

The block design below shows the TCA9548A acting as a switch for SDA and SCL communication as well as in the use case for the DRV260x the TCA9554 being used as a GPIO expander to switch on/off the EN pins of each device individually, using GPIO on the DRV262x series would cause issues as it has NRST instead of an EN pin and so would reset all registers if switched off and on.