bq34z100 senc file download

Thanks for the prompt reply.

I was able to load the .senc file.

Rob

What is the latest SENC file for the BQ34Z100?  We have an older EVM and we would like to make sure we are using the latest firmware.'

Thank You,

George

The v0.6 senc file attached to a previous post on this message string is the latest firmware release.

Regards
Tom

I seem to have a problem with my bq34z100 fuel gauge. I can talk to the gauge, but when I launch the GUI it does not recognize the device. Normally the GUI knows what TI chip is there. I have options to select the bq34z100 or the bq34z100R1 but regardless of which I choose I get a message that state “The detected device is not compatible with this application! Proceed at your own risk.”

 The auto device detected says 0_0_00 which may be the problem.  The detected device should match the encr. The thing is the chips come from TI with a .senc file (firmware image) that’s not loaded by us. I don’t know why this would not recognize this. I get this on every board.  I checked the rev of the IC it says bq34z100; it does not say R1

Normally this is the result of the ENCR file in the bqeval not watching the rev of the chip. If the correct ENCR file is available then bqeval just launches without issue, but since its not doing this, I assume there must be a mismatch. The thing is , as far as I know, there are only 2 options, and I have both; bq34z100 and bq34z100R1. Neither of these work. I do get communication but there could be problems programming the chip if using the wrong encr. I imagine this is all because the detected version is 0_0_00

The encr files I have are

bq34z100_0_01.encr

bq34z100_0_02.encr

bq34z100_0_03.encr

bq34z100_0_04.encr

bq34z100_0_05.encr

bq34z100_0_06.encr

bq34z100_0_07.encr

I had installed the bq34z100 EVM software  with sluc366a . Is there something newer. When the application launches, if I select bq34z100r1 the SBS screen indicates Texas Instruments bq Gas Gauge Evaluation Software – bq34z100R1 v0.07 – [SBS Data]

At this point I'm considdering loading a .senc file. I have the 0.06 fom this thread but it looks like there is a 0.07 since there is an encr at that rev.

Robert,

Version 0.06 is the latest release. The v0.07 is an experimental release and bq34z100-R1 has not been released yet. They must have been picked up with the latest bqEVSW build that added ROM file export / import capability.

Regards

Tom

Thanks Tom. Any idea why my device is being detected as 0_0_00. If I use the rev 6 encr I get issues. I could try to reprogram the senc, but I think its risky. Any other suggestions? I have 8 boards and they all behave the same

Robert,

Where did you get the devices? Maybe they were prototypes or are in ROM mode. I would try reloading the .senc file into one of them to see if will auto-detect when the bqEVSW is reopened. You can export the .senc file from one of the packs and I can check to see if there is something corrupted in it.

Tom

The devices I got were samples from Arrow. I completely removed power so I would not think they would stay in ROM mode. I think to exit ROM mode you send 08 but are the bits in te GUI reverse like they are in the 27541?If I want to get out of ROM mode do I send 00 then 08? If I want to enter ROM mode, is it 00 then F0 or reversed

The bq34z100 works a little differently than the bq20z devices. To enter ROM mode, you use I2C Command 00, Data Block 000F. To exit ROM mode you write this sequence to I2C address 16.

Finish the programming process by exiting ROM mode and sending the following commands:
(a) I2C Command 0x00: Data Byte 0x0F
(b) I2C Command 0x64: Data Byte 0x0F
(c) I2C Command 0x65: Data Byte 0x00

Regards
Tom

Hi Tom,

I'm not able to get the bq34z100 into Rom mode. I followed your instructions and it's not going into ROM mode.

For the Write I2C data Block, I tried:

000f

 Then 00 followed by 0F

Then  0f followed by 00

It looks like that is design for 1 byte at a time

I also tried Read/Write I2C byte  and the same sequences as above with no luck. The i2C address is AA and I am able to communicate with it properly

Thanks,

Rob

Am doing a firmware update check:  is Version 0.06 still the latest firmware for the bq34z100 or is a newer release now (or soon to be) available?

Carl, 

Version 0.06 is the latest release of the bq34z100 firmware. 

Tom

Hello,

I have a similar problem but I think you could help me.

To write a .senc file I use the I2C command 00 and Data Block 000f. The the bqEVWS shows me "communication error. Then I program the .senc file. And it shows "Programming completed succesfully!". After this I want to exit the ROM mode with the I2C command but it always shows "communication error". What could be the problem?

Christopher,

Did you press the Execute button after the download completed? This will return the gauge to normal mode. If you are trying to use I2C commands to exit ROM mode, then here are the commands and they must be written to I2C address 16.

Finish the programming process by exiting ROM mode and sending the following commands:
(a) I2C Command 0x00: Data Byte 0x0F
(b) I2C Command 0x64: Data Byte 0x0F
(c) I2C Command 0x65: Data Byte 0x00

Tom