• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 62 subscribers
  • Views 244 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.

BQ79616-Q1: Risk evaluation when read non-existed registers of BQ79616 and BQ79600

Songzhen Guo
Intellectual 2770 points
Part Number: BQ79616-Q1 
Hi Team,
Customer is using BQ79616 and BQ79600 for BMS of vehicle.
Is there be any impact if customer read non-existent registers (not written in the datasheet)? What are the risks?

For example, there are registers A, B, C showed in Datasheet, but there is no register D.
When customer using MCU to read data, customer read data directly from register A to register D. 
When processing data, customer filter out the data corresponding to D , What is the impact of this?

What are the risks in actual use?



Best Regards
Songzhen Guo
  • +1
    TI__Genius 14890 points

    Hello Songzhen,

    There is no risk in just reading these registers. Please see the register summary notes below for the expected behavior of the different types of registers.

    The register summary tables use the following key:

    • Addr = Register address

    • Hex = Hexidecimal value

    • NVM = Non-volatile memory (OTP) shadow registers

    • RSVD = Reserved. Reserved register addresses or bits are not implemented in the device. Any write to these bits is ignored. Reads to these bits always return 0.

    • OTP_SPARE: These are spare OTP and shadow register bits that are implemented in the device. These spare bits are included as part of the CRC calculation. These bits are read/write as normal, but do not perform any function or influence any device behaviors.

    • OTP_RSVDn = OTP and shadowed registers that are implemented but are reserved for device internal usage, where n refers to the register address. MCU must keep these registers in their default value

    • HW Reset default is the value loaded when digital resets (POR like event) whereas Factory Configuration Default is the default value loaded into the OTP cell if customer doesn't program it themselves. Customer cannot read the HW Reset value.

    -Alex Scheuermann