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.

BQ20Z655-R1: BQ20z655-R1: resetdata & WDreset data

Part Number: BQ20Z655-R1

Hi,

I have extracted 2 *.senc files from the same BQ20z655-R1 battery, days apart.

the initial *.senc what I had classed as my golden image contained these values:

resetdata (0x57): F209

WDresetdata (0x58): 00E3

After a number of tests these counters increased to:

resetdata (0x57): FA0E

WDresetdata (0x58): 00E5

The increase to these values may well be justified. However my observation has been if I then reflash my golden image *.senc file the counter values change. Reflashing the golden image returned the values to:

resetdata (0x57): F209

WDresetdata (0x58): 00E3

Elsewhere in the forum it was described that if a BQ device was reflashed 'resetdata' & 'WDresetdata' would retain there values. This is not what I am seeing.

It appears these values can be modified although the Technical Reference does describe these locations as ReadOnly.

Is there a way to clear these values, to zero, for the creation of a golden image file?

  • Hi,
    Most likely the issue is that the golden senc file already has the high reset counts.
    There are a couple of ways to rectify this:
    New golden Senc:
    1. Extract your golden gg file
    2. Flash the gauge with the default senc
    3. The default senc should zero out the reset counters. Verify that they are zero.
    4. Import your chemID
    5. Download your golden gg file from step 1.
    6. Upload your new golden senc file

    Write the values to 0 in data flash:
    On an unsealed gauge you can write the reset values to zero.
    SubclassID is decimal 57, hex 0x0039.
    Reset Counter Partial, Offset is 0
    Reset Counter Full , Offset is 1
    Reset Counter Watchdog, Offset is 2
    Upload the new golden senc after writing the values to zero.
    Regards,
    Swami
  • Swami,

    modified via the Subclass route

    Subclass not mentioned in 'Technical Reference'

    big thumbs up, it worked

    thanks