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-G1 EVM not acknowledging after flashing

Other Parts Discussed in Thread: BQ34Z100-G1, BQSTUDIO, BQ34Z100, EV2400

Dear e2e team,

I have been working with BQ34Z100-G1. We have a .srec file of already working BQ34Z100-G1. In that chip all the procedures and learning cycle is done

successfully.

We exported that .srec through Golden Image option of BQstudio tool and it created the Golden file successfully,

We then flashed the .srec file again in our new BQ34Z100-G1 chip. It flashed successfullym but once after 3 seconds the chip detection is stopped

and it didnt detect nor I can able to flash the original Bq34Z100-G1 firmware to the IC.

It always says no acknowledge from the device.

Seems like something got corrupted in the IC. IC deosnt seem like it gone bad, but still cant figure out the issue.

Does this issue have anything to do with the way we created the Golden Image.

I opened the exported files ".gg.csv" I found that Uddate status Register has been set as 06. Whether that is caused this issue.

do I have to set different value before creating the Golden Image file ?

Please clarify.

Thanks & Regards

Sarjoon

  • Sarjoon
    Did you press the Execute button after loading the srec? This should return the gauge to normal mode. If you did this and the gauge still will not respond, check the thermistor. It will pulse at a 1s rate, if the firmware is running. If it is not pulsing, then you can try to see whether you can program the default srec to the device and recover it. You can send the faulty srec to me and I can try it as well.

    Did you edit the gg file with a text editor. It can get corrupted, if you edit it with Excel.

    Tom
  • Hi Tom,

    I pressed Execute FW button at once after programming is done. But the Execute FW is not happening. It always says as "No acknowledgement from device". This issue used to come in working time also.. I already have reported this in my last post also, you suspected it may be in Sealed state but its in Unsealed state only. Still couldnt able to get Execute FW successful. So I always program the .srec and I will restart the tool since "Execute FW"never worked for me.

    Attached the srec files.

    working_srec.zip

    Never edited it. Used the created Golden Image(.srec) directly without doing Execute FW.

    Regards

    Sarjoon

  • Sarjoon
    I have had the same problem as you so that I can not re-program with a different .srec golden image since there is no communication with bq34z100 through bqStudio. Did you find the solution?
    Thank you.
  • I programmed Sarjoon's srec into a pack and experienced the same problem with the device not communicating and not recovering. It appears that the srec is corrupted. Which version of bqStudio are you using to export the srec file? Did the program report any errors during the process?
  • Dear Thomas,

    I mentioned in my previous reply that I receive the "No acknowledgement from device" error continuously when I was exporting the Golden Image file files, yet it finished exporting successfully and created the Golden Image files. Whether that plays any part in this flashing issue ?

    Also my question is why I keep on getting the "No acknowledgement from device" error. The tool used it bqStudio(the latest one downloaded from TI) you have any Studio tool exe fully working one without any issues. If you have anything like that please share this sir, it will be helpful.

    Thanks in advance
    Sarjoon.
  • Hi

    I have a same problem as yours.

    When I generate golden file, the bqstudio message is "No acknowledge from device", but finish export serc file and shown "successfully".

    After I program the serc file to another chip, It out of work and can't communication.

    I can't recover to original serc file, because it doesn't work at all.

    What is this problem? and how to avoid this again?

    The Tool I used is bqstudio V1.3.52 and EV2300 V3.1C.

    Cheers

    Xue 

  • I am having the same issue.  It sounds like a firmware or software bug somewhere in the chain. My versions of code are:

    bq34z100-g1 Rev 0100-0-16

    EV2300 Version 3.1c

    bqStudio Version 1.3.52.

    Maybe some more clues from my tale of woe:

    After programming my first board with the .srec file, I did an "Execute FW", then did a restart.  bqStudio could no longer find the chip.

    Thinking perhaps communications errors had corrupted the code and bricked the part, I took my second board and only programmed the data (.df.fs file). After executing and restarting, I could read battery status.  I couldn't unseal the chip however, so I couldn't run a calibration.

    I removed the programmer and cycled battery power.  After reconnecting the programmer, bqStudio could no longer connect to the chip.  I haven't had time to look at the I2C communications,  to see if the chip tries to respond.

    ----

    This is a serious problem, and needs to be fixed before we go into production.

  • Hello,

    I would recommend updating your EV2300 to 3.1m or 3.1r (preferred), or use EV2400.

    Here's the EV2300 updater. Follow the instructions in the wizard. It may require installing bqEV as well, if you run into a missing file issue when running the updater.

    EV2300FW Updater.zip 

  • I did verify that bqStudio v52 works without corrupting the srec file and I also verified that exporting the srec using the EV2300 v3.1c will corrupt the srec and brick the device if the srec is imported. We are adding a note to the product websites.

  • Hi,Mark

    I use the same tools as you. And Mr  ThomasCosby has verify the EV2300 v3.1c will cause the problem.

    I will change or update my EV2300.

    Cheers

    Xue

  • I'll update my EV2300, but I've also ordered an EV2400.  I think I'll wait for the latter to arrive and save risking another bricked chip.

  • The bq34z100-g1 has been programmed successfully using the EV2400.  Earlier in this thread, it was suggested I update my EV2300 firmware.  Any idea if this will also work?  I'd try it, but I don't wish to brick another chip finding out...

  • The EV2400 with v0.18 FW should not cause any problems with using the bq34z100-G1 device or EVM. The updater can be downloaded from the EV2400 website.