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.

bq34z100 cannot program flash configuration

Other Parts Discussed in Thread: BQ34Z100

Hi All


I'm trying to program the data flash configuration on my bq34z100 eval kit. It's the first time I using the bq design kit and software. Following the Design Steps in SLUSAU1B beginning on page 28, I entered the new values into the fields in the configuration view of the Gas Gauge Evaluation Software. However, it does not seem to work properly. At first, when entering a value (e.g. Design Capacity = 15400) and closing with the Enter key or clicking somewhere else I get a message box saying "TIFlexGrid - Type mismatchtxtEdit_LostFocus". In spite of the message, the newly entered value remains in the field. But then, when I click on "Write All" or "Write All, Preserve" the writing process starts and the progress is displayed on the bottom right of the application window. After finishing, another read out is done and immediately the old default value of 1000mAh is displayed in the Design Capacity field.

I tried to start the application as Adminsitrator under Windows 7, but that didn't help either. I also thought about seal/unseal, however, the design steps do not say anything about this.


Here's some more data on my application:

Battery Pack: 4S6P Li-Ion, 15.4Ah, Unom 14.8V, Ucharge 16.8V

bq23z100EVM Design Kit configuration: J2: 16V

EV2300 Adapter with I2C communication to design kit

 

I hope, someone can give me some good advice on how to do this. Thanks in advance.

Cheers

Adrian

  • There are some comments on the Lost Focus error message on the forum. Here are a couple of them.

    http://e2e.ti.com/support/power_management/battery_management/f/180/t/214918.aspx

    http://e2e.ti.com/support/power_management/battery_management/f/180/t/247436.aspx

    Maybe one of these will help.

  • yep, the second link did it, even though it is a bit annoying that I have to adjust my regional settings for that... but thank you anyway.

    ==> It is a bug with regional settings. Set decimal separator to comma (",") at your regional settings to solve this.