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

Original question:

CCS/BQ27510-G3: BQ27510-G3

CCS/BQ27510-G3: BQ27510-G3

Emma Wang(DELL EMC)
Intellectual 350 points
Part Number: BQ27510-G3
Other Parts Discussed in Thread: EV2400

Tool/software: Code Composer Studio

1,Is there any reason that brick FG results in I2C hang and continue to reset? My big concern is why fail FG hang I2C.

2,Why reducing to 50K? Standard clock is 100k is it right?

3,I have reviewed document, however could you help to confirm whether our updating steps with system?4212.update process with system.docx

4,How can I modify it manually? Change FW code using C?

  • 0
    TI__Mastermind 24870 points
    1. Please clarify I2C hang. NACK or one of the lines is held low. If both lines are floating, it is not a bricked FG. Measure TS pin as well. If you see a pulse, then gauge firmware is running.

    2. 100 kHz is the standard speed.

    3. Where did you get this document? Looks like screen shots of an old tool.

    4. Refer to gauge communications app note. Just send I2C commands.
  • 0 in reply to Kang Kang
    Intellectual 350 points

    8750.update process with system.docx3312.V01 and V03.zip1373.V04.zipBackground:

    Using system update method to update firmware of FG from V01 to V03. It failed and I2C handed, board continued to reset. I also tried to connect it by EV2400, which is also fail. When replace this FG using a  good FG, I2C became good and board didn't reset. When put this fail FG to a good board, I2C was good.

     I did a test that updated  FG at the same time communicated with other device on same I2C bus, which resulted in FG brick. This FG was not connected by EV2400. TS pin of this FG didn't have pulse.

    My big concern is why brick FG hang I2C?  FG may become brick because of some reason, but why it impact I2C bus?

    1,Is there any reason that brick FG results in I2C hang?

    2,Attchment is update program of system update we use. Picture shows command sent to FG by system, we use I2C analyser  to monitor command during this period and I capture some picture to let you review. Please help check and tell me whether there is mistake on it？

    3，Attchment is new version V04 of FG we use. According to before communication with TI FAE, he recommended to reduce delay time to 200 (original is X:2) after he reviewed this V04. Could you tell me how to modify it? Via prameters in V04? Or change code during update?

    4,He also recommended to reduce clock to 50kHz, after he reviewed clock(it is 100kHz) picture. Why? Standard I2C is 100kHz.