• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 63 subscribers
  • Views 394 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

BQ78350-R1A: Differences between chip versions BQ78350-R1, BQ78350-R1A and BQ78350-R2.

BQ78350-R1A: BQ78350-R1 and BQ78350 comparison

Needhu Gunasegaran
Intellectual 2890 points
Part Number: BQ78350-R1A

Hello Team,

I have a followup question to the following e2e post.

https://e2e.ti.com/support/power-management/f/196/t/879900

Is there an exact description of what the problem with the robustness during shutdown is?

My customer has the following followup question.

Is it advisable to change the whole production to the bq78350R1A or is the firmware 01.04 available as download? With firmware 2 a lot of data in the bq has to be adapted, so we would like to do without it.

However, we currently have a problem that on some of our boards the bq is in an error state immediately after the first start-up, which immediately causes a PF and ensures that the communication to the microcontroller is disturbed. Do you know this phenomenon?

Looking forward for a feedback.

Thanks in advance,

 - Needhu

  • 0
    TI__Guru* 81034 points

    Hi Needhu,

    We recommend using the v1.04 firmware. The R1A comes pre-loaded with v1.04 firmware, but the firmware is also available for download from both the R1 and R1A product folders on ti.com. 

    The reason that v1.04 firmware was created was because we heard from a few customers that they observed flash corruption with frequent use of the Shutdown command in a small percentage of devices. If the instruction flash is corrupted, communication with the device is no longer possible even with a full power cycle. V1.04 firmware only modifies the Shutdown routine to make sure that no accidental access to the flash is possible. The new firmware resolved this issue in 100% of cases.

    I do not know if this is at all related to what you are observing after first startup. It sounds different from your description. What PF was observed?

    Best regards,

    Matt