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.

CCS/BQ27510-G3: BQ27510-G3

Part Number: BQ27510-G3

Tool/software: Code Composer Studio

Thanks for your answer about timing of erasing data!

However, do you know answers of other questions about reason of I2C hang ?

1,In order to solve gost current problem, I increased cc deadband from 17 to 68(The cc deadband of V04 was changed to 68.) according to your advice. Is cc deadband change stored in 'Instruction flash' or 'Data flash'? In fact, I had been told that dffs file can cover cc deadband change during time of solving this issue? Could you confirm? 

2,Our factory will buy BQ27510-G3 from TI and update it via V04 dffs file(it is attached). Could I update FG using V04 dffs file without  any our configuration data loss because dffs file doesn't include IF section without  any our configuration data loss? Is IF part of V04 bqfs file same with default IF part of G3 bought from TI? Would you help confirm it is ok to use V04 dffs file?

3,What steps are needed to update FG via dffs file and bqfs files? Is this process same?

4442.V04 dffs and bqfs files.zip

 

  • Hi Emma
    1.cc dead band is stored in dF. Any configurable parameter by the customer is DF.
    2. Your dffs still contains more than 32 bytes in one write command. I had recommened breaking this up into smaller chuncks of less than 20 bytes per command. Note that dffs contains the entire data flash. if you use df that programs and overwrites the total dataa flash. If you use bqfs, that contains both the IF and DF, so you are effectively wiping the chip clean and programming the IF and DF.

    3. Yes The process is the same. Both are programmed in ROM mode.

    thanks
    Onyx
  • Appreciate your wonderful support for this problem!