• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 200 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

BQ34Z100EVM: EVM setup SLUU904A issues

Mike Twieg1
Intellectual 390 points
Part Number: BQ34Z100EVM
Other Parts Discussed in Thread: BQSTUDIO, , EV2400, GASGAUGECHEM-SW, BQ34Z100

I'm trying to setup the BQ34Z100EVM for use with a 24V SLA string, but have run into several issues with the software. I'm using bqStudio version 1.3.101.1, which I believe is the latest stable build. I started with the quick start guide (SLUUBV2), and didn't have any issues there. Updated the EV2400 firmware to 0.28. Then I went on to follow SLUU904A, and problems start occurring at the Chemistry Screen section (section 3.4). 

I tried to update the chemistry version via the GASGAUGECHEM-SW. Initially I downloaded ChemicalUpdater-876-windows-installer.exe but got this error message

Couldn't get that message to go away, even by reinstalling bqstudio or running as admin. So I instead downloaded ChemUpdate876.zip, and installed that via Help > Update Chemistry. Now bqstudio indicates I have Chemistry version 876, which I assume is the latest. The chemistry ID most similar to my batteries (a similar looking pack from Sigmastek, 18Ah instead of 17Ah) is 0809, so I select that and click "Program Selected Chemistry," and get this window:

I've seen many other e2e threads about this message, but none explain what it actually means, and none of the replies have helped me much. But despite the message it seems to have at least changed the CHEM_ID. Here is what some of the various commands return in the log panel:

So next I try section 3.5, the programming screen. The first step is "Search for the .srec file using the Browse button," but does not say where to look for the file, and I'm unable to find any existing .srec files anywhere.

Eventually I tried creating output files via the Golden Image tab, and I successfully create .srec, .bq.fs, and .df.fs files. I go back to the programming tab, select the new .srec file, click Program, and it says "Operation executed successfully" in the bottom left. Next I click "Execute FW", but the bottom left message says "Failed to execute Firmware - No acknowledge from device." I follow the advice in this thread and can successfully read some bytes with I2C address xAA, which I suppose is good.

So at this point I've made several deviations and wanted to ask a few things before I proceed.

1. Are the "target bqz container is old" and "Failed to execute Firmware - No acknowledge from device" messages just bugs in bqstudio which should be ignored?

2. I'm concerned about the .srec file I created and uploaded; doesn't feel like a "Golden" image if I created it while deviating from the normal steps. I feel like there was supposed to be a real Golden .srec file that shipped with the bqstudio install, or would be downloaded from the BQ34Z100 webpage, but I still can't find one.

3. I've been doing this all with the EVM powered from a 4V DC supply. If my battery is not an exact match for an existing battery in the CHEM_ID list, what things should I do before trying this out with my actual battery? As far as I can tell, mine is similar to the YUASA NPH_18 I've selected, except my packs are specced at 18Ah, and I want to use two packs in series.

Regards,

Mike

  • 0
    TI__Genius 11535 points

    Hi Mike,

    1. I will need to look into the "target bqz container is old" message further. I've never seen this before but as you stated, there have been several reports of it in previous posts. I don't think it should impact performance. The "Failed to execute firmware" message is not a bug, it means that something went wrong and bqStudio is not able to communicate with your device. There can be several reasons this message appears, including the device not being sufficiently powered, not being connected to the EV2400, and trying to program a device when it is sealed.

    2. Section 3.5 is not necessary unless you are specifically trying to program new software onto your BQ34z100. For example if there was a new firmware release you could download the srec from ti.com and program it onto your device. I'm not sure if you actually programmed your device but even if you did it was probably the default.

    3. If you cannot find an exact match for your battery in the chemID list, you can go to https://www.ti.com/tool/GPCCHEM to find the closest match. 

    Best,

    Jessica

  • 0 in reply to Jessica H.
    Intellectual 390 points

    Hi Jessica, thanks for the reply,

    The "Failed to execute firmware" message is not a bug, it means that something went wrong and bqStudio is not able to communicate with your device. There can be several reasons this message appears, including the device not being sufficiently powered, not being connected to the EV2400, and trying to program a device when it is sealed.

    It seems bqstudio is able to communicate with the device, since I can read its registers and use the commands in the commands panel. But "Execute FW" always returns the same message.

    2. Section 3.5 is not necessary unless you are specifically trying to program new software onto your BQ34z100. For example if there was a new firmware release you could download the srec from ti.com and program it onto your device. I'm not sure if you actually programmed your device but even if you did it was probably the default.

    I'm still unclear on what the role of the different files is. I'm guessing I should only be dealing with the .df.fs file to update the various parameters and calibrations, and only touch the .srec or .bq.fs files if there's an update available to the device's firmware?

    I'll check out that link, thanks.

  • 0 in reply to Mike Twieg1
    TI__Guru** 102405 points

    Hello Mike,

    We looked at the issue and suspect that the firmware was run automatically after programming. Trying to send execute command when firmware is already executing will result in error.

    Sincerely,

    Wyatt Keller