Part Number:BQ34110EVM-796
Hi,
We are trying to make a new .fs file for an upto date calibration with an official battery pack that will be used for the production unit.
Hi,
I programmed the BQ34110EVM-796 using BQStudio (1.3.54.1) with .fs file (see attached) and EV2300 (version 3.1m). The programming failed at some point, not sure what happened and the BQ34110 got stuck in ROM mode. Before programming with BQStudio, the pins of the BQ34110 chip were:
REGIN = 2.6V
REG25 = 2.5V
BAT = 400 mV
CE = High
VEN = High
The file I sent is the same we used on lots of units before without any problem. However, REGIN was below 2.7V, so it might be why the programming failed. On our units, the design insures REGIN is above 2.7V.
After that, I was able to communicate with the BQ34110 on the ROM mode address using the Advanced Comm tab (ex: read at 0x16 00 without error). Since the device was already in ROM mode, I modified the .fs file to remove the “Unseal device” and “Go to ROM mode” steps. I tried to send the .fs again, however the EV2300 did not send any command on I2C when programming the .fs file (checked with sniffer on i2c lines). I closed and reopened BQStudio and selected “0110_0_02-bq34110.bqz”.
To make sure REGIN > 2.7V, the J2 jumpers were modified to have:
REGIN = 4.6V
REG25 = 2.57V
BAT = 400 mV
CE = High
VEN = Low
Then, the programming worked until line 42 of the attached file, which is a compare flashstream command:
C: 16 04 3B 8C FE FB
With the sniffer, I saw that the data read on BQ34110 was not 3B 8C FE FB, that’s why it stopped. Unfortunately, I did not keep the sniffer data…
I was not able to get out of the ROM mode (tried sending W: 16 00 0F and W: 16 64 0F 00 and reset the BQ34110). I removed 4 compare commands that began with C: 16 04 <data> and programmed the .fs again. BQStudio was able to send the whole file, but now the BQ34110 nacks at both addresses (0x16 and 0xAA) even after a reset, so it seems I bricked it.
The pins states are still:
REGIN = 4.6V
REG25 = 2.57V
BAT = 400 mV
CE = High
VEN = Low
My questions are:
- Why would the programming with BQStudio fail in the first place? The file seems fine, since we used it on many units without failure. Is it possible that a REGIN below 2.7V corrupts the firmware while in ROM mode? It did not seem possible to recover from ROM mode after the failure, which is worrying.
- Is there any BQStudio error log file? I did not find any…
- I noticed after the programming failure that VEN was low (it was high before). Is that a normal behavior in ROM mode?
- Now that the BQ34110 seems to be bricked, is there any other procedure we can try on the EVM to restore communication with the BQ34110?
Thank you,