I have observed the fuel gauge firmware become corrupted in the following situations:
- Flashing new Firmware
- Updating data memory
- communication with battery charge
I am using the R3 firmware.
It is clear the memory is being corrupted by the fact that the devices will still respond to SMBus commands, but with incorrect data. (All 0s for measured values, and garbage information for programmed values like manufacturer name).
Once the device gets in this state, it is impossible to access it with BQ Studio to reflash the firmware. Triggering a soft reset via the manufactureAccess() Reset command has also proved to be ineffective.
Is there any way to reset these bricked devices so they can be correctly programmed, or otherwise restore the device to correct functionality?
If I switch to using the R5 firmware (which has improved code for watchdog recovery among other improvements), would I see a decrease in the number of these issues or better results in recovering these devices?
