• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 63 subscribers
  • Views 112 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

BQ25600: Questions on BQ25600 fault monitoring

Christina Lim
Expert 5085 points
Part Number: BQ25600

Hi,

My customer is unfamiliar with BQ25600 and have the following questions :

Questions:

  • For status registers REG08 ~ REG0A, since REG09 not support multi read, does user need to read these registers one by one?

  • What’s the suggestion for safety check? What action firmware should take to ensure battery safety in charging and discharging? for example what is the difference between CHRG_FAULT = 10 & THERM_STAT =1? Is there a recommended fault monitoring flow where customer can make reference to?

  • How does firmware can detect if charge IC in ship mode? How should firmware judge if keep in ship mode or exist ship mode?

 

Thanks

Christina

  • 0
    TI__Mastermind 46671 points

    Hi,

    1. Please single read REG09. REG09 keeps all the fault information from last read until the host issues a new read. In order to get the fault information at present, the host has to read REG09 for the second time. The only exception is NTC_FAULT which always reports the actual condition on the TS pin.

    2. Please refer to Table 16. REG09 Field Descriptions for the details. THERM_STAT refers to Thermal Protection (8.3.10.3.1 Thermal Protection in Buck Mode). The host should monitor REG07, REG08, REG09, REG0A regularly.

    3. When REG07[5]=1, the device should be in ship mode. But REG07[5]=0 does not indicate the device is not in ship mode. There's no dedicated bit indicating ship mode.

    Thanks,

    Ning.