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.

TPS25751: Can't write to BQ25792 after migrating from TPS25750

Part Number: TPS25751
Other Parts Discussed in Thread: BQ25792, TPS25750,

Tool/software:

Hi,

We tried the TPS25751 with the same I2C APIs which work on TPS25750, and found that we can read from BQ25792, but can't write to it.

  • Hi Diverger,

    Could you elaborate on what you mean by this? Are you referencing the 4CC "I2Cw" and "I2Cr"?

    1. After moving between device, have you generated a new binary using the latest version of the gui? (v1.1.0)

    2. Can you confirm the device boots up and enters APP mode properly?

    3. Can you capture I2C on the I2Ct and I2Cc ports for both the I2C reading and writing cases and share the logs?

    I would not expect their to be any difficulties using these commands, so am interested to see what you are doing. There should not be any differences between the I2Cw commands between the TPS25750 and TPS25751.

    Thanks and Regards,

    Chris

  • 1. Yes, we use the GUI tool generate the new binary for 251.

    2. Yes, it boot into app mode, the evidence is we can read back registers of bq chip

    If you confirm that the communication method is the same with 250, we will do more checks on our side

    Thanks

  • Hi Diverger,

    Yes, the boot up and communication method between the two devices are the same. I would recommend reading the TPS25751 MODE(0x03) register to confirm it reads back "APP " mode.

    There is a known typo in the TPS25751TRM regarding the I2Cw. see the image below for the correct I2Cw table. The TPS25751TRM incorrectly says the 3rd byte is reserved.

    Thanks and Regards,

    Chris