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.

BQ40Z50-R2: Inquiry About Configuring COCP / DOCP / SCP Release Conditions to Latch Function on BQ40Z50

Part Number: BQ40Z50-R2
Other Parts Discussed in Thread: BQ40Z50

Tool/software:

Dear TI Support Team,

We are currently using the BQ40Z50 and would like to understand if the release conditions for COCP , DOCP , and SCP  can be configured as a latch function.

Specifically:

  1. Is it possible to configure these protections such that they remain latched (i.e., do not auto-recover) until a reset or specific command is issued?
  2. If this functionality is not directly supported, is there any workaround to achieve a similar behavior through firmware or configuration?
  3. Could you provide guidance on any relevant registers or documentation sections to help us implement or debug this functionality?

We would greatly appreciate your assistance. Please let us know if additional information is needed.

Thank you!

  • Hi Tom,

    I am confused on your descriptions of COCP, DOCP, and SCP. Can you please confirm what protections are being discussed from the list below?

    Regards,

    Anthony

  • Hi Anthony,

    From the TRM, the register settings for those current protection, it only mentions "Recovery."

    Is it possible can be configured as a latch function(i.e., do not auto-recover) ?

    Thanks!

  • Hi Tom,

    It is not possible to configure firmware protections to have the same latch functionalities that hardware protections do. However, can you please go more into depth about what is meant by auto-recover? If you do not want the protection to recover at all, the recovery parameters can be put out of the application range.

    Regards,

    Anthony