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.

  • TI Thinks Resolved

CCS/BQ27510: Some problems with BQ27510

Intellectual 310 points

Replies: 21

Views: 800

Part Number: BQ27510

Tool/software: Code Composer Studio

Dear sir:

I have some questions about BQ27510

1.We burned our own bqfs file and found that it always failed to write. The failure information is as follows:

Written data:

Every time I fail in the same place, it's troublesome.

2.Can you provide us with an official and up-to-date available bqfs document?

3.Is I2C not working after the failure of Flash burning BQ27510 in the main control software?

4.Write failed chips with master control. Can you take them down and burn them with a burner?

Attachment is source code

bq27510-i2c.tar.gz

  • In reply to Onyx Ahiakwo:

    Hello Onyx,

    Thanks for your attachment. Sorry for writing you again. I had tried the bqfs file which was provided by you, but unfortunately, it still fail to upgrade.

    W: 16 64 D7 24
    X: 2
    C: 16 66 00

    Like usual, it fails to compare the value of reg 0x66 with 0x00.

    Do you have any advice? What's the root problem?
  • In reply to Kyson Lok:

    Kyson
    The file i provided you was the default. it is not broken down to less than 32bytes per command line.
    pls use ev2300 having firmware 3.1m or 3.1r or an ev2400 to program the gauge using bqstudio. Then use extract the a new bqfs, but before doing so click the options button next to the field when trying to create and extract break limit the no of bytes to less than 20 before extracting the bqfs file.
    then use that new file in your host to program.
    thanks
    Onyx
  • In reply to Onyx Ahiakwo:

    Hello Onyx,

    I use ev2400 to extract a new bqfs file and limit bytes to 18. But unfortunately, it still no success. I can program it via ev2400, but fail to program on host.
  • In reply to Kyson Lok:

    Hi Kyson

    Here are a few more things to try:

    -Can you increase the time delay in the bqfs files to 200.
    -Can you capture scope shots of your signals so we ensure your system is not violating any of the i2c specs.
    -Can you post your code so i can have one of our programming experts review it.

    thanks
    Onyx
  • In reply to Onyx Ahiakwo:

    Hello Onyx,

    Sure, please check the attachment. The source code in code folder, and the I2C capture file in I2C analysis folder. Note that the capture file is kvdat extension, you can download this software to analysis it. http://www.qdkingst.com/en/download

    bq27510-3G.zip

  • In reply to Kyson Lok:

    actually, it always fails at 434 line. The capture file I sent you in above was comment on the compare command in bqfs. I update the capture file now.

    Those commands above 434 line looks like:

    W: 16 00 02 2D 00 00 CB AF 0C FF 1B 0E 38 FA 36 D8 FF 00 D7 FF
    W: 16 12 00 D6 FF 00 D5 FF 00 CF A0 0E 7F A1 0E 02 AF 18 D8 BF
    W: 16 24 01 03 AF 18 D7 BF 01 00 AB 18 80 2B 0E 00 CB 02 D0 AF
    W: 16 36 04 4A FA 36 D0 AF 04 00 CF 02 D0 FF 00 FF A1 0E 61 A0
    W: 16 48 0E 02 AF 18 7F BF 0E 02 CF 02 6F A0 0E 7F A1 0E 01 AB
    W: 16 5A 18 10 2B 0E 01 CB 02 10 AF 0E
    W: 16 64 09 27
    X: 200


    C: 16 66 00 -- 434

    Even though I attempt to write the block separately, it always fails. 

    bq27510-3G fail at 434.zip

  • In reply to Kyson Lok:

    We would look and get back to you by tomorrow.
    thanks
    Onyx
  • In reply to Onyx Ahiakwo:

    I can't find anything obviously wrong in your code.

    For security considerations, I can't install the application to check the I2C log file data. A text based I2C file that shows what's actually written to the gauge could help. Also, the delay (X:200) is very important. The gauge will not return the expected data unless it had time to process the block.

  • In reply to Dominik Hartl11:

    Hello Hartl,

    Thanks for review the code. Actually, the code is based on 

    But I also try to change the delay value to 200, but it still fail. It is very weird. With your experienced, what do you think it will cause this issue? Will it caused by the hardware? 

  • In reply to Kyson Lok:

    Hi Kyson,

    To see if there are issues with the i2c signals, can you capture a scope shot of the signals when the NACK occurs?
    thanks
    Onyx

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.