• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 157 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.

BQ34Z100-G1: Issue when writing configuration file

franziskus
Expert 8309 points
Part Number: BQ34Z100-G1

Team,

my customer encounters issues when writing the configuration file onto the device during production. Some of the devices (60 out of 1000) act like there is no firmware present and thus the configuration cannot be applied.
The boards are produced in batches of 10 boards per batch. It seems like, if the issue occurs, the entire batch is affected.

Is there any sequence that erases the firmware from the devices that might happen during production?

Thanks for your help!

  • 0
    TI__Genius 10830 points

    Hi Franziskus,

    I wanted to let you know that your post has been assigned to one of our applications engineers. This week takes place our annual Battery Management Deep Dive event for which all our engineers are all hands on deck. He will be able to your post early next week, once this event is over.

    You can check out recordings of much of the material we present at www.ti.com/deepdive

    Thank you for your understanding!

  • 0 in reply to David Hien
    TI__Mastermind 25955 points
    Hi Franziskus,

    During programming in ROM mode, if a data comparison fails, production code should error out. A data comparison failure can be due to a communication error/noise or loss of power in the fixture during programming.

    An example of code is given here:

    www.ti.com/.../slua801.pdf

    If the device errors out during programming, please power cycle the device and program again.

    Check the test fixture for loose wires or a noise source that could cause corruption to data on the i2c bus.

    Sincerely,
    Bryan Kahler