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.

BQ78350-R1: Data Flash Wearout error occurrence

Part Number: BQ78350-R1


Hello,

We are using the BQ78350-R1 chip in out BMS to monitor our battery pack status. However, we often encountered the Data Flash Wearout (DFW) permanent fail. The PF can be cancelled through a BMS reset, that is disconnect and reconnect the power lines. We suppose that this is due to excessive write on the data flash, probably triggered by some subroutine we still have to correctly identify. Do you have some infos on how to correctly handle the data flash and possibly avoiding too many write access to it?

If needed we can share parts of the proprietary source code which handle the TI chip.

Regards, 

Ferdinando Gasparini,

Battery Test Engineer

Stiga s.p.a.

  • Hi Ferdinando,

    It is very unusual to see this permanent fail. The data flash is rated for 20,000 writes - how many packs have you observed this on? This PF indicates that data written to flash could not be written successfully. Are you able to narrow down when this PF occurs (is it a specific section or register in Data Memory)? I think you are on the right track by checking if there is some code that is writing to flash excessively. Unfortunately I do not have any additional tips for debugging this type of failure since it is very rare. The last time someone reported this, it was on a single unit out of a large population which is likely a weak device that failed earlier than 20,000 writes.

    Update: I did find an older thread where the DFW PF was being induced by programming the srec incorrectly (by writing past the last address in data flash). You should avoid reading or writing to addresses beyond address 0x4612.

     https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/629964/bq78350-pf-data-flash-wearout-failure

    Best regards,

    Matt