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.

How to ascertain the present firmware support the chemistry or not

Other Parts Discussed in Thread: BQEVSW, BQ20Z80, BQ20Z90, BQ20Z40, BQ20Z70

Dear ALL,

   As the file slua372r description:

 So, how  to ascertain the present firmware support the Chemistry ID which learned from the cycle?

(the fuel gauge is bq20z75 v1.15 ,and the Chemistry ID learned from the cycle is 0107,eg.So if I need update the firmware

?If  So,which version of the .senc file  I need and how I know the imformation about the firmware supported the chemistry ID or not?

  • You don't need a separate SENC file anymore. You can download a chemistry updater. You must have bqEVSW with bqEasy installed before installing the chemistry updater.  The updater is located here:

    http://www.ti.com/litv/zip/sluc066z

    Open EVSW, go to bqEasy, and then skip to step 4. Click 'Yes, Enable Chemistry Selection', select your ID from the list, and then click 'OK-Update Fuel Gauge Data Flash.

  • Chase,Thanks very much for your reply.

    I'm confused by the description of the slua372r and the update firmware step in the flow chart of  the  slua352A.

    Could I consider like this:after I update the Chemistry ID table by instal the chemistry updater which you relate to,then implement the chemistry select cycling,the Chemistry ID which learned from that step is be supported by the firmware of present device?

     

  • The Chemistry Updater will update your list of chemistry IDs in bqEasy. After you run the chemistry select cycling on your cell, the Mathcad tool will give you a closest ID match. You can then go to bqEasy, navigate to the Chemistry tab, and download the ID that your cell matched into your gauge. All Impedance Track devices (bq20z80, bq20z90/95, bq20z70/75, bq20z40/45, and bq20z60/65) are compatible with the chemistry IDs.

    The SLUA352a document is related to bqTester. This device is used in production, not in development. The chemistry ID step you are asking about is much earlier in the process than the bqTester, so they are unrelated. That might be why you are getting confused.