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.

BQ 34z100 not responding to unseal key

Ok, still having some low volume production pains. I have a quantity of 60 or so batteries that after programming data flash and doing IT enable and sealing, FAS is set but SS is not set. attempting to use the FAS key to unseal does not create any response. of i use the 0x41 reset command SS will set, and it responds to the SS key to remove the SS flag, but FAS is still non responsive.

Any ideas, or other information you guys would need for this? I can provide a sample battery to a TI apps engineer if that is helpful.

  • Did you change the Full Access key from the default when programming the data flash into the ICs? Additionally, is this common to all ~60 batteries that you've programmed? If it's potentially caused by the Full Access key getting overwritten with an unexpected value, you could try programming a fresh chip and reading out the Full Access key to double-check that it's set properly.


    If you've changed the key for your application, you'll need to make sure that neither 16-bit word corresponds to another I2C command (so it can't be, say, 0x0021 since it's used for IT_ENABLE) otherwise the key would be unusable for unsealing the gauge.

  • FAS was not changed from the default of FFFF FFFF. this is only happening on about 60 units out of 500. all went thru the same test procedure.

  • Matt,

    You should be able to export a .rom file with the device in unseal mode. You can then load this file into a pack that is in full access mode and read the data flash. You should be able to read the full access keys. If you cannot get it to work, then send the .rom file to me and I will check the keys.


    Tom

  • Tom,

    I am able to do this and the full access keys are the default. The issue is I have 60 batteries out of a lot of 500 that are not responding to the FAS key. All 500 received the same programming which is why these few are showing this behavior and were set off to the side. without being able to clear the FAS off these packs there is nothing else i can really do with them. They seemed to be grouped around the same tray of battery packs, but I had them go thru 2 different programming stations with the same result. This leads me to believe its a problem with the IC and i'm wondering if someone at TI would be able to take a look at it.