• State
  • Replies 2 replies
  • Subscribers 63 subscribers
  • Views 52 views
  • Users 0 members are here
Support feedback
Options
Options
Related

BQ76952: An exception occurred when exiting the configuration mode

hengfa xu
Prodigy 20 points
Part Number: BQ76952

Tool/software:

Hi TI team,

I sent commands via I2C to configure the BQ76952. I was able to successfully enter the configuration mode. However, I found that sometimes I couldn't exit the configuration mode and it returned 0XFFFF. I would like to know what caused the configuration failure.

  • 0
    TI__Prodigy 740 points

    Another customer ran into an issue where they were getting a watchdog reset when trying to read PF_STATUS (0x0053) after exiting CONFIG_UPDATE mode. This only started happening when he changed the number of parameters being written. The issue is resolved by adding more wait time after exiting before sending any subcommands (direct commands are no problem probably due to clock stretching). So the wait time needed is dependent on the number of parameters in order to avoid the watchdog.

    This customer issue seems to resolve when waiting 50ms * # of parameters written before exiting config mode.

    e2e.ti.com/.../bq76942-por-reset-by-internal-watchdog-after-exit-of-config-mode

  • 0 in reply to Gavin Long
    Prodigy 20 points

    Hi Gavin!

    Thanks for your support!

    I have a new problem:

    After my device was shut down and then awakened by TS2(Awakening time: 600 ms), it would read the 0x9234 Power Config. Sometimes it would be the default value of 0x2982, sometimes it would be 0x3535 or 0x0000. When these latter two sets of data appeared, it sometimes caused the device to return 0XFFFF when entering the configuration mode.