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.

BQ76942: BQ76942 burn in process question

Part Number: BQ76942
Other Parts Discussed in Thread: BQSTUDIO

Hi team,

Our customer want to check the burn in process of BQ76942,

they used TI program "Battery Management Studio" to burn in,

but it seemed that it is not able to output bq.fs or df.fs files, only gg.csv files.

Is there a way to use the program to output files other than gg.csv to support BQ76942?

Thanks


  • Hi Roy,

    The Data Memory page in BQStudio will import the gg.csv. files.  It will export gg.csv or flash stream files.  The flash stream export includes a gm file which is commands and an OT which includes a command to write the OTP.  Since OTP is limited, use that carefully.

    The BQ769x2 Command Sequence page will load and run fs files, In a simple test it loaded a few settings.

    The user should validate that it does what is desired.

  • HI Team,

    Thanks for your help, it will export and import .fs file now.

    BTW, our customer found out that the ot.fs file has OTP Programming command, what is the purpose?

  • Hi Roy,

    The ot.fs file has a section to program the OTP at the end.  Use that carefully since it is permanent.  Be sure the voltage for the board is set properly before loading the ot.fs file.

  • Customer have these problems when they program.

    Do they have to execute OTP to program successfully?

    If OTP is not executed, will the data disappear when rebooting?

    Do they need to connect 10volts to VBAT when they execute OTP command?

  • Hi Roy,

    If not using OTP the settings may be loaded each time the part is powered on.

    Yes, the settings are lost when the power is turned off if the settings have not been programmed to OTP.   

    For successful programming the supply voltage should be between 10 and 12V, and the part should remain on for at least 100 ms after the command is sent.