• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 63 subscribers
  • Views 3579 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.

EV2400 communication errors with bqEVSW SLUC157A v00.09.64 and bq20z45-r1 v1.05 build 0005, windows 7 64 bit

c2011
Prodigy 140 points
Other Parts Discussed in Thread: BQEVSW, BQ20Z45-R1, EV2400I have installed the EV2400 support components SLUC291: http://www.ti.com/litv/zip/sluc291 On top of bqEVSW SLUC157A, and on two different PCs running Windows 7 professional 64 bit edition. When I connect to a battery pack using for example a bq20z45-r1 and go to the "DATA FLASH" window of EVSW and click the "Read All" button I get an error message concerning the read I/O operation (see attached screen shot of error dialog). Is this expected? I believe I have seen similar consistent errors with EV2400 when connected to the bq20z75-v181 and using bqEVSW v00.09.79 for the z75. Do the EV2400 support components work correctly with Windows 7 64 bit OS? They install with no contraindication of use concerning my OS and version of bqEVSW, but yet I always seem to get errors reading data flash only using the EV2400. An EV2300, when substituted into the same system works fine for this operation, although I had had to install the unofficial 64 bit OS support software for the EV2300 to get it working. If the EV2400 SW is not supported for 64 bit OSs, is there an unofficial support driver/software package for EV2400 as there is for EV2300? Other engineers here also seem to have been unable to get the EV2400 working though the reason hasn't been identified, so I thought I'd ask if it was a 64 bit OS issue or something possibly else. Thanks!
  • 0
    TI__Guru 57697 points

    EV2400 supports Windows XP, Vista and 7 running 32 or 64 bit OS. It does not require driver installation.

    The EVSW was originally written to support only EV2300. EV2400 support components need to be installed to allow EVSW to recognize and use EV2400.

    There are 2 effective questions in the post and i will attempt to answer both

    1. What causes Error code 6?

    Error code 6 means that the SMB transaction had a timing or start/stop problem. There are a few differences between EV2300 and EV2400. The EV2300 does not run at true 100KHz SMbus, it is ~66KHz. EV2400 runs at true 100KHz. This could cause some differences in target response. Especially if the target is busy running an algorithm during charge/discharge. I was unable to duplicate the issue. We will need to look at waveform to determine root cause and whether this is normal and compliant to SBS or if it is something that we can fix on EV2400. If we can have details of how to reproduce, we can debug and provide additional  details.

    2. Other engineers are unable to get EV2400 working

    Cause is that EV2400 support components are not installed. Make sure that the support components are installed last. There are some EVSW installers releases that overwrite the EV2400 support files. Typical error if the support components are missing is "EV2300 not found/connected".

  • 0 in reply to Shirish
    Prodigy 140 points
    Thank you very much for your informative answer. When I learned of the higher EV2400 operational speed from your response, I investigated the EV2400 schematics / user manual and I see that it has an active pull up circuit and other differences from the EV2300 as well. I looked at the waveforms on an oscilloscope and did some SMBUS protocol analyzer captures and reviewed the battery schematic. I determined that there was too much of a capacitive load on the SMBUS lines from over-sized TVS diodes on SMBC and SMBD, and that these were causing some unusual but consistent problems even with the EV2300's slower speeds in one pack design. That extra diode capacitance factor also worsened the function with the EV2400. EV2300 seems to work fine now without the too large TVS capacitance and seems to have improved at least somewhat with the EV2400 as well. I will have to do some retesting with the EV2400 and bus analysis to determine if there are further problems with the EV2400's higher speed operation with the particular pack design, and if further design changes are required. It is good to learn that the EV2400 is supported with 64 bit OS platforms, thank you also for that information. If I find that I have no follow up questions about the EV2400's bus performance after doing more testing with the relevant pack designs, I will mark the answer above as conclusive. PS Is there an EV2400 "customer kit" with an API to do I/O from a programming language similar to what the EV2300 has? Perhaps the EV2300 customer kit already works with EV2400 provided the EV2400 support software is installed? Thank you very much!
  • 0 in reply to c2011
    TI__Guru 57697 points

    Thanks for the analysis. The EV2400 has a weak pullup with active acceleration, so a large capacitance will affect SMB more than EV2300.

    You are right about the API. EV2300 customer kit works with EV2400 provided the EV2400 support software is installed.