• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 64 subscribers
  • Views 870 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

EV2300 Connection Issues

MARK BREMER
Prodigy 10 points
Other Parts Discussed in Thread: BQ27500, EV2400, BQEVSW

Hi,

I'm working with the bq27500 gas gauge and am trying to use the EV2300 to interface with it.  At first we had some driver issues, but eventually got it working with a VM with WinXP.  For a while we could communicate with the gas gauge but all of a sudden it stopped working and is not able to connect anymore.  It fails to auto-detect the gas gauge anymore and cannot communicate.  I sniffed the I2C line and there's nothing coming out of the EV2300, so I assume the issue lies in the EV2300 itself?  

Sounds like it is a driver issue, but after reinstalling all the drivers it still doesn't work, plus it doesn't explain how we were able to connect the first time.

The other possibility seems to be that the EV2300 is no longer working properly.  The LEDs on the board are all working though, meaning it's powered so I'm not sure this is it.

Has anyone run into a issue like this before?

Also, I've read that the EV2400 is backward compatible.  Will it work for the bq27500?  If so, why is the EV2300 still suggested to be used with the bq27500?

  • 0
    Intellectual 300 points

    FWIW, we ran into something similar with an EV2400 - we were using bqEVSW on Windows XP to drive a suspect board (something wrong with the I2C) and the EV2400 stopped working altogether. The LEDs were still on, so I spent some time checking cables. We noticed that the errors displayed in bqEVSW changed from timeouts to USB errors at that time. We switched from our suspect board to the EVM and restarted bqEVSW, but still could not get the EV2400 to send I2C signals.

    Tried the EV2400 again later on a different PC, and saw no problems. Tried a couple days later on the original PC, and saw no problems. I suspect the EV2400 reset itself (the I2C levels were bad, so it might have been protecting itself), and perhaps confused the USB driver on the original PC.

  • 0
    Genius 3970 points

    This may seem like a silly question, but are the I2C lines are pulled high when you're probing the signals? The EV2300 doesn't have built-in pull-up resistors on the I2C lines.

    I myself don't have an EV2300 (I have the EV2400) but a firmware update might help in your case. Try this updater: http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/180/3225.EV2300FWUpdaterUnprogDev.zip

    The EV2300 is the 'predecessor' of the EV2400, but the EV2400 will work just fine with the bqEVSW (some older versions will prevent the EV2400 from working and you may need to use SLUC291 to re-install the EV2400 support components). I've had issues where the EV2400 support components block me from using certain bqEVSW profiles for certain gauges, but haven't tested this on the bq27500 or EV2300.