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.

Writing the DFI of BQ27520-G4 via I2C Port

Other Parts Discussed in Thread: BQEVSW

Hi Everyone,
I'm having some confusions about loading .dfi file via I2C port.

1. slua449f and slua541a both describe the programming process. I assume they are two different methods.
I prefer slua541a. It references a program called "flashstream.exe"( I have found the link in dMax's profiles).
Do .bqfs and .dffs files have included the commands, which are described in the flowchart 8, 9 and 10 of slua449f?

2. So, my next steps will be:
a) Get the .dfi file and .senc file.
b) Use flashstream.exe to generate .bqfs and .dffs.
c) Parse one of these files in my system, and transmit the parsed data via I2C port.
Please confirm if is correct.

3. My gauge chip's firmware version is 0x0302. I didn't upgrade the firmware and got a .dfi file(.dfi of v3.02).
The firmware(.senc) provided in the website is v3.29. I think it is different with the chip's.
I used .dfi of v3.02 and .senc of v3.29 to create a .dffs file.
Can the chip work normally if I write this .dffs file to my chip?
If the chip works abnormally, how to handle this problem?

4. .bqfs file contains both data flash and instruction flash data. I think writing .bqfs file will lead to upgrade the gauge chip's firmware.
But, .bqfs file is much larger than .dffs file. It's about 3000 lines. If some errors happen when downloading this file, will the chip be brick?

Any help is much appreciated.

  • Hello Jerry,

    Please see responses below.

    1. We would recommend you go down the *.bqfs/*.dffs route.  As you mentioned, the *.xxfs file formats have commands built in that essentially allow a host to "walk through" the update process by parsing the *.xxfs file.  The commands in in the application note figures are similar to what the *.dffs file will do, but are not the exact same.
    2. Yes, your steps look correct.  You want to use the *.dfi from the firmware (FW) version you are going to use in production (so if using '520-G4 then the *.dfi should be v3.29).  You could also just read out the *.senc file after you have configured the gauge properly for your system (i.e. loaded proper chemistry, calibrated, set data flash parameters, completed learning cycle, etc.) and use just the *.senc with FlashStream.
    3. No, do not try and load a *.dfi or *.dffs that comes from a different FW version.  I would load the *.senc containing the FW version you are wanting to use onto a device (or EVM) using our tools.  Then you can extract the configured *.dfi or just the configured *.senc and use FlashStream to generate the *.dffs and *.bqfs
    4. You are correct, the *.bqfs is used to upgrade both the FW and the DF.  The *.dffs will only upgrade DF and should only be used if the FW version is the same as the FW version the *.dffs was created with (Flashstream has an option to include this check in the *.xxfs files).  If the update does not complete, the gauge should not brick, you should be able to start at the beginning of parsing the *.bqfs file and retry the update.

    I hope this helps.

  • Hi Jared,

    Thanks a lot.

    You mentioned reading out the *.senc file. Does the bqEVSW have this feature?
    I noticed there is a dialog box "Programming" under "I2C pro". I clicked "Read to *.senc file" and got a error code 772. My chip is in the full access mode.

    BR

  • Hello Jerry,

    Please see attached *.pdf that provides steps to reading out a *.senc file.

    I hope this helps.

    readoutDFI_senc_EVSW.pdf

  • Hi Jared,

    Thanks again.