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.

bq20z80v102 DFF flag failure on several devices after loading dfi file from bqEASY

Other Parts Discussed in Thread: BQ20Z80

I just built a 4cell LiPo battery pack around a bq20z80v102 chip. I connected to it using the EVM2300, software 0.9.79.  It all seemed to work until I started the bqEasy process. I chose the 1.02 version (default) dfi file and loaded it.  Everything continued until it tried to write to flash and then it complained that permanent flags were set so it could not continue.

I went back to the SBS screen and the DFF flag was set (it was not previously).  I tried the PF reset command (which worked previously) and it has no effect.  The device still responds to some commands and lights the gauge LEDs but it will not turn on the CHG or DSG fets and is basically useless.  I looked through these forums and found no good answer to the DFF flag except that it indicates an incorrect dfi file, but I used the only dfi file there is for v1.02

So I wired my battery cells to the eval board and tried to use it.  It went through the bqEASY process all the way to the cycles.  I got it to turn on the CHG fets and let the battery charge, but then I noticed that it has a bq20z80A chip which I believe means it is v110. 

Since I already have v102 parts I wanted to make sure that my the problem was not on my board so I replaced the v110 on the eval board with a v102.  It did the same thing as my board. It worked, I could read and write from the program.  but then I started the bqEASY process and as soon as I loaded the dfi file, the same thing happened and now it has a DFF flag set that I cannot clear and I can't charge or discharge it.

I ordered new bq20z80A parts and will try replacing them on my board to see if it will work, but it seems that there is a problem with your software or your bq20z80_1_02.dfi file.

Thanks,

Jonathan