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.
Part Number: BQ27510
Tool/software: Code Composer Studio
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:
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
In reply to Onyx Ahiakwo:
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Kyson Lok:
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
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 FFW: 16 12 00 D6 FF 00 D5 FF 00 CF A0 0E 7F A1 0E 02 AF 18 D8 BFW: 16 24 01 03 AF 18 D7 BF 01 00 AB 18 80 2B 0E 00 CB 02 D0 AFW: 16 36 04 4A FA 36 D0 AF 04 00 CF 02 D0 FF 00 FF A1 0E 61 A0W: 16 48 0E 02 AF 18 7F BF 0E 02 CF 02 6F A0 0E 7F A1 0E 01 ABW: 16 5A 18 10 2B 0E 01 CB 02 10 AF 0EW: 16 64 09 27X: 200
C: 16 66 00 -- 434
Even though I attempt to write the block separately, it always fails.
bq27510-3G fail at 434.zip
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:
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?
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.