Production difficulty bq20z45 with Advanced bqMTester and version 1.0.6 of PC software

We have replaced a failed Q1 in HPA495, but that does not change the failed behavior of this setup. 

We do find on the Global Configuration screen under Select Device Version that the bq20z45-R1 is nowhere to be found as a possible Target Device.

Only 'z80, 'z90, 'z70, etc.... older parts.    Please help.

Ken

Hello Ken,
The Q5 you replaced really should not have failed.
One possibility is the cells were not connected in the proper sequence.
This is described in SLUA404 page 205.
1. connect the most negative terminal Cell1
2. connect the + of cell 1 (1N)
3. connect the + of Cell1 (1P)
4. connect the + of Cell2 (2P)
5. connect the + of Cell3 (3P)
6. connect the + of Cell4 (4P), if you only have 3 cells then 3P should also connect to 4P

For the Target Device you will need to add it manually.
There is a post that describes it.
http://e2e.ti.com/support/power_management/battery_management/f/180/t/23522.aspx
For bq20Z45 V1.05
I believe the 'target' you should add is:  "bq20z45 v1.05","450.1.05"

The bqMtester is a rather advanced setup and requires a great familiarity with the devices.

I believe this may be related to the fact that the bq20z45 V1.05 was not added at this point.
See my post further down on how to add the device.
See if adding the correct target remedies this.

It was not Q5 but Q1 that I said had failed and I replaced it already.

No cells are being hooked up at this point of failure.  The tester board has 0v on it when connections are made.

I will look at the post.

Sluu397A says “Using this option is sometimes tricky. It is recommended that TI be contacted

before using this option to ensure that the bqMTester has been tested with the requested device.

“

The 23 Aug 2011 post from Jackie also has changes to a config.ini file.

What do we edit in the config.ini file for the 20z45 part?

The information tell us to ask, so, has our target device been tested with this software? 

Should we be surprised that the 20z45 is considered a “custom device”?

Thanks.

 Ken

Yes my mistake, but Q1 should not have failed either.
It is under virtually no stress.

At the time bqMtester was written there were many "custom" parts being sold to customers.
Custom, at that point, would include any device not in the original release of the software.
As such the bq20z45 would fall under the custom category when this program was released.
It has been tested with the bq20z45, and there is no reason it would not work.

Include a link to the Aug 23 post because I can not find it.

The post I refer to is listed in your 9/15 post in this thread.

http://e2e.ti.com/support/power_management/battery_management/f/180/t/23522.aspx

The communication error is caused by v1.06 is not compatible with the the newer hardware (HPA495).

The newer hardware is account for cell-based voltage calibration. It is not required to calibrate bq20z45. Please use HPA169 bqMTester board with the current released bqMTester software.

To add bq20z45 v1.05 to the device list:

Add the following line to the <Targets> file:

"bq20z45 v1.04","450.1.05"

Add the following section to the <config.ini> file

[D450]
Platform=32816
CalWr=60
DateOffset=12
PkLotValid=0
ITOff_DFOff=18
ET1Off_DFOff=19
ET2Off_DFOff=20

Is there any software to run the HPA495?  We have been unable to find v2.0 that is in the documentation.

We do not have the HPA169 as it is not available.  We have the HPA495 which were told was the current design.

Please help.

Ken.

We now have tried the HPA169 and get through the bq tester setup fine. 

v 1.06 of bqMtester fails to find the board and terminates with no work done.

It appears the voltage is never enabled by the I2C interface to allow the target board to run.

Device Manager shows the TI USB bq80xx Driver as active.  The TI USB Firmware Updater is installed and hidden by Device Manager.

Ken

Ken,

Did you try adding the z45 to the config.ini file as Jackie suggested above? The HPA169 won't work with the z45 until it is added to the Config file.

Yes the edits were made to the target and config.ini files 

But I used v1.05 not v1.04 as was shown.  Typo I think.

Also I did not have the PkLotValid=0.  None of the other devices in bq tester list that.   It is only found in the bq eval software'sed config.ini

Today I tried uninstalling both the updater and bq80xx drivers before starting the bqMTester.

Now I get this error message:

Single site InitCacheFromSetup() failed for board 1.Error code=65557

All,

I have made the config file changes as shown.  The bq tester setup runs once as before.  When we run the Multistation test v1.06 we still get "zero boards found".  Then if we try the setup again, it fails with communication errors, again as previously documented.  We are no closer to a production solution.

I have hard wired some switches across the outputs of the optical couplers on the HPA169 and it works manually with bqEASY, but this is not a Production solution.

Ken

1. Can you try just connecting EV2300 and a TI EVM. Run the EVSW. It should auto detect the device and communicate without error. This is to make sure there is no conflict of the computer/OS/driver. 

2. How about the 「Single site InitCacheFromSetup() failed for board 1.Error code=65557」 error? Did you un-install and re-install the bqMTester v1.06 software? If not, please re-install the software. We have not seen that error message before. Something might be wrong during you initial installation, it is better to re-install the software.

3. Can you take a picture of what you did on the HPA169 board? I'm not sure what you mean by "hard wired some switches across the outputs of the optical couplers". I'm not sure how you can run HPA169 with bqEASY or EVSW. The board will not be powered up by neither of these software. Can you send us a picture of your set up?

Jackie,

    Thank you again for your help with this during the Deep Dive conference.  We are almost done, but still have an issue.  All the calibrations run but when we turn on the station setup checkbox to update the .ROM file, we are still getting Error code=65557 when bqMTester is starting up.  Remember we got the Tester to start by unchecking the update in setup.

Can we field update our EV2300 to make it USB TESTER READY ?

After we marry the cells to the GG board, we will need a simple program (one button) to enable the IT and maybe to put the part into ship mode after some simple operational tests.  Is there an API for the EV2300 that would let us create these programs or are these programs something that can be supplied?

Ken.

Ken,

That error code means the .ROM file header information or the .ROM format is bad. Did you update the <Config.ini> file with the following information?

[D450]
Platform=32816
CalWr=60
DateOffset=12
PkLotValid=0
ITOff_DFOff=18
ET1Off_DFOff=19
ET2Off_DFOff=20

The <config.ini> file needs to be updated before creating the .ROM file, otherwise, the .ROM file header information may be incorrect.

Attached here is a default bq20z45v1.05 default ROM file that I created. It works fine on my computer, so try that to see if you still get that error message.

http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/180/6404.bq20z45v105_5F00_default.rom

Please refer to the following post regarding EV2300 libraries.

http://e2e.ti.com/support/power_management/battery_management/f/180/t/49259.aspx

I thought it was corrected to Platform=32832.

My configuration is with "Platform=32816".

In your <config.ini> file, did you see a [P8040] entry section? If not, you should definitely use "Platform=32816"

On 10-06-11 I was told to use Platform=32832 by Chase.  That is the same value that is in the bqEVSW config.ini file.

There is no [P8040] in any file I find.  I am sorry, but there is some confusion growing. 

Is the config section for the bq20z45 not [D450]?

Changed the platform to 32816 for bqMtester.      (This number is 32832 in the bqEVSW config.ini)

It now appears we can use bqMTester to  EITHER do a calibration OR update the flash from a .rom file.

If we select in the StationSetup program to do calibrations and update the flash together within bqMTester, then we get an Error code = 65570 and in the lower window a Pass/Fail Error code 65544.

Ken.

Hi!

I experience identical results. Has anyone succeeded in doing both calibration AND rom update to a bq20z45-R1?

/Ragnar