Welcome @aneeshvnair, to the community!
let me repeat the description of the I2C mode from the data sheet, section 6.7.3:
In the I2C mode the D+ and D- lines act respectively as I2C SDA and SCL signals when the OE_TP_INT/ signal is low. The transceiver automatically enables the pull-up resistor on the SDA line in this mode. The internal I2C slave interface of the transceiver does not react to commands from the master.
Communication addressed to the STOTG04 device is mirrored to the D+ pin and responses from this pin are mirrored back to the SDA pin. The D– pin mirrors the SCL clock.
You have probably misunderstood this description, but it means the following:
In I2C mode, the I2C interface of the STOTG04E no longer accepts control commands, instead the pins SDA (pin 2) and SCL (pin 3) are converted to D+ (pin 16, now bidirectional SDA) and D- (pin 15, now SCL output). The I2C interface shown in the data sheet, fig. 11, is therefore no longer used to control the STOTG04E, but routes the I2C communication from the external master transparently to pins D- and D+.
If you mean a bridge that converts USB to I2C in order to control I2C devices from a PC, you can find plenty of suggestions with your favourite search engine, even a Github project that uses one of the cheap NUCLEO-32 or NUCLEO-64.
Does this answer your question?
Regards
/Peter
In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
