• TI Thinks Resolved

BQ4050EVM-561: bqStudio does not communicate with bq4059EVM-561

Part Number: BQ4050EVM-561

I have the following problem with bq4050EVM-561


1.       The bqStudio has been download from bq4050 TI web site without problems to 2 PC (the same issues were noted on both PC).

2.       The evaluation module was connected to 4S1P Li-ion string with sequencing advised in User’s Guide SLUUBF9.

3.       The PC port was connected to EV2300 (EV2400 gives the same results) and EV2300 was connected to evaluation module through SMBus 4 wire cable.

4.       The bqStudio software has been started but it did not AutoDetect device (message: Autodetect device = NONE). Pressed WAKE push button on the module did not change the response.

5.       After selection of 9E34-0.01 bq4050.bqz from Gauge list, the following message popped up:

“The detected device is not compatible with this application! Some actions could cause to lose communication permanently and enter unrecoverable state. Proceed on your own risk!”

6.       Proceeded on my own risk I found that main bqStudio screen popped up with 2 than 3 green arrows in DashBoard  window for a few seconds and then they were lost. No SMBus communication was established.

7.       The oscilloscope probe was connected between SMBC and GND of the evaluation module. I wanted to monitor SMBus traffic after I already confirmed 3.3V present on the module.  As soon the probe touched the SMBC pin the SMB communication with bqStudio was established and data scanning proceeded with programmed speed. Changing of DF parameters was possible in bqStudio and the module was responsive.

8.       After described “successful” start, removing oscilloscope probe, disconnection and reconnection of EV2300 from PC, or disconnection and reconnection of SMBus cable did not affect proper operation of the bqStudio and the evaluation module.

  • Zoran,

    This might have to do with the fw on both the ev2300 and the ev2400. Please update ev2300 to 3.1r and the ev2400 to the latest code on ti.com. That should fix this.

    The only reason smbus might go down is if your gnd path is iffy. Connecting the oscope can provide a solid gnd or might drain a residual charge on the board. You may have also had a mild ESD hit which once a clear GND is established drains the chg.

    If you can successfully shut the gauge down and wake it up with a pack connection, we can confirm if it was the latter.