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.

bq27510-G3 downgrade to G2 firmware

Other Parts Discussed in Thread: BQ27510-G2, BQ27510-G3

All,

We are proceeding with the manufacturing of our product and initially, we had bq27510-G2 however, due to the time schedule and the availability of G2(out of stock) from our supplier, we had decided to procure G3 to avoid any delay. Our DFI file is based on G2.

In addition, we had created our own FG programming software using bqfs. However, the client would want to program using dffs if the firmware version is already correct in order to reduce tack time.

These are my main concerns:

1. How will we be able to check the firmware of the FG? Can we check the FG firmware without EV2300 and not using the bq evsw? Can we check the firmware by Write-Read-Compare (USB to I2C) to specific registers? If so, can anyone please provide us as to what App note we need to refer to or if anyone could give us direct assistance?

2. Can bq27510-G3 be downgraded to bq27510-G2 firmware? we had encountered issues before using G1 hardware upgraded to G2.. If G3 could be downgraded to G2, can we use bqfs file? what are the other parameters/checksums that we need to check? 

Thanks,

Kat

  • If you use the -checkversion:10050004 command-line option when creating the Flashstream files, the dffs file will include lines with the FW_VERSION subcommand.  You will see lines where it sends (0x0002) to the Control( ) register, then reads back the result expecting 0x0400 to be returned for 510-G3.  See the table in the datasheet which lists the Control( ) subcommands.

    Yes, you can use the bqfs file to downgrade or upgrade between G2 and G3.  The bqfs file includes the checksums automatically.  If any C: (compare) line in the flashstream file fails, then you should not continue parsing the file but go back to the beginning and erase again (starting at the first line that tries to talk to I2C device address 0x16, which is the address of the gauge when in ROM mode).

  • I would appreciate confirmation of your statement about the using CNTL_FUNCTION with the FW_VERSION subcommand.  You stated that the value retrieved be 0x0400 for 510-G3.  I am currently reading 0x0123 for 510-G2 which I took to mean v1.23 listed in the EVSW.  What will the value be for 510-G4?

    While I'm asking a question on this topic, what are the expected values for the HW_VERSION subcommand on 510-G2, 510-G3 and 510-G4?