ev2300 with 9.59 bqEasy software won't detect

Just an addendum,

If it helps at all, the numbers on the chip are as follows:

bq20z90

86KG4

FRLN

That is all that is written on the chip. 

Thanks,

Allen

I have attached document that describes the correct installation procedure and process for connecting to the gauge to communicate. See if you can get the EVSW to work with this guide. If not, there may be an issue with the chip, the EV2300, or any of the cables.

Hello,

I have managed to get complete functionality with the demo board that came with the EV2300, but when I try to use it with an actual chip from a battery pack, it doesn't work at all. I have probed the SMData and SMClock pins on the chip with a logic analyzer, and have verified that the signals are in fact getting to the chip and look identical to the waveforms coming straight out of the device. 

Any ideas would be greatly appreciated.  I am also following this thread ( http://e2e.ti.com/support/power_management/battery_management/f/180/p/65423/236142.aspx#236142 ) because it looks like he might be having the same problem as I am.

Thanks,

Allen Vandiver

I'm going to need some more information. If you are sure you are getting the correct signals from the gauge (not the EV2300), then there should be no reason that you shouldn't be able to see the chip working with the EVSW. It's possible that the signals you see are coming from the EV2300 and the chip just isn't responding. Do you have a schematic of your design I can review?

Hello,

Unfortunately, I do not have a schematic for the circuit, it was taken directly out of a working battery.  It was a Mayday 9-cell battery (since I don't believe Dell batteries cooperate with anything.  In addition , I can tell you that the resistance between the battery terminal and the clock pin was 100 ohms, and the resistance between the data pin and the terminal was 200ohm.  I think I might just try designing the circuitry or at least grabbing it from another not so cheap battery. 

Thanks for your help,

Allen Vandiver

Allen,

I don't understand what you mean by "the signals are in fact getting to the chip and look identical to the waveforms coming straight out of the device" - the host and the slave should be sending out different data.

You should look at the waveform on a scope. Look at the shape of the signal, the timing of the signal. Did you device ACK/NACK?

Attached is an unofficial SMBus application note for your reference.

Hello,

I ended up cooking that chip on accident (I let out the magic smoke), and decided to go with a battery using a bq20z95dbt.  This actually works much better.  the chip talks to the software just fine except that it appears to be sealed, and in such a way that the software can't unseal it.  Is there any possible way I could get the unseal/full access codes for the chip?  I am pretty sure it is revision 1.5 (that is what it says in the title bar anyways).  I think the 20z90 was just a faulty chip.

If you need an email to send it to, you can send it to allenvandiver@gmail.com, or my work address avandiver@caci.com

Thanks in advance,

Allen

Please contact with your local TI rep.

Hello,

I didn't see anywhere on your website how to find contact information for your local rep.  Any chance you could tell me who it is?  I am located in Rome, NY (central NY, near Syracuse).  

Thanks,

Allen