• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 64 subscribers
  • Views 253 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.

bq20z90 Programming Checksum

George Mortimer
Expert 1205 points
Other Parts Discussed in Thread: BQ20Z90

Is it possible for the bq20z90 ROM image to provide a checksum to verify that the program installed in the battery pack is correct? This would obviously have to be done before the serialization and calibration of the board by the Multi-Tester.  Our customer is asking for this as we have had some difficulty in verifying the correct firmware version due to multiple updates in the firmware during the development of the product.

  • 0
    TI__Genius 10235 points

    Sending 0x0002 to command 0x00 will return the firmware version of the device. This will allow you to verify that the correct firmware version is on the part.

    There is a checksum command (0x0004 to command 0x00), but it only computes the checksum of the data flash.

  • 0 in reply to Chase7071949597
    Expert 1205 points

    I don't think this is what I am looking for.  I tried to issue the 0x0002 command to the pack and I got back 0x0150 (generic firmware version 1.50).  I have been using the Firmware Version data bytes to keep track of updates in my .gg file, i.e. writing the revision level into the .gg file when I make a major programming change.  The Manufacturer Access code does not seem to help here.  I don't think a checksum on the data flash would be helpful, as the data flash includes such things as calibration values and board s/n which would change from board to board.  Is there a better way to track revisions to the programming .rom file?