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

BQ40Z50-R2: SMBUS communication fail after FW (SREC) update

Jason Change
Intellectual 380 points
Part Number: BQ40Z50-R2
Other Parts Discussed in Thread: EV2400, BQSTUDIO

Hi team,

When I was performing SREC programming, the system interrupted the programming process halfway (so the programming was likely not completed). After that, the EV2400 was no longer able to connect to the device. 

After reopening BQStudio, the system asks me to select the Gas Gauge part number being used, and then displays the following screen for about 2 seconds as below picture. 

image.png

After 2 seconds, the EV2400 is unable to connect to the device, as shown in the image below. After that, the device can no longer be programmed with the SREC file. 

image.png

I try to read gauge, it show "9002" as below. 

May I know how to solve this issue?

image.png

  • 0
    TI__Mastermind 33610 points

    Hello,

    This question has been assigned and will be reviewed by someone on the team when possible. In the meantime please attach .gg/.log/ data files associated with the project to help the engineer assigned to this e2e.

    Thank you,
    Alan

  • 0 in reply to Alan Frias
    Intellectual 380 points

    Hi Alan,

    Thanks for your feedback.

    I already solve this issue.

    Step as below:

       1. Remove the battery cell

       2. Discharge all capacitors related to the gas gauge

       3. Assembly battery cell

       4. Wake up gas gauge (Pack pin voltage > Vshutdown+)

       5. Turn on Bqstudio and select part number

       6. Programming the SERC file as quickly as possible when the BQ software is opened

       7. If programming still failed, repeat steps 1 to 6.

    Best regards, 

    Jason