Spaces:
Runtime error
Runtime error
File size: 2,031 Bytes
b24351f |
1 2 3 4 5 6 7 8 9 |
BQ76930EVM: Evaluation software fails to detect connected device
Part Number: BQ76930EVM Just realised the image I posted shows the cable connected to SMBus... I posted the wrong image, the correct one should show it connected to I2C. Hi I'm hitting a problem when I try to open the evaluation software. It throws up an error message which reads 'Unable to read ADC Gain and Offset from connected device. Please ensure a powered bq789X0 is connected to the I2C communications lines on the communication adapter...etc, etc'. What is particularly frustrating is that I have had this working cleanly in the past - I have just resurrected this project and have now hit this problem so it's quite likely it's caused by something I've got configured wrong. I'm powering the board using an external power supply, providing around 30V and the board is connected (via I2C) to an EV2400. I've attached a picture of the board showing its configuration - ignore the cable in the shot, it's for connecting my battery but is currently disconnected. Any ideas on what might be wrong here? Cheers, Mike
Hi Mike, The LED is lit so the board has power, You are using an EV2400 so you don't want the pull up shunts, they are removed. As you note, in the picture the SMBus connector is used, move to the I2C. Also be sure to move the EV2400 end to the I2C connector. Be sure to boot the board with the pushbutton left of the PACK- terminal in the picture. Check that REGOUT has gone high, then you may need to check continuity on the I2C lines from the EV2400, The connector pins or the cable are the most likely to open, Inspect at various points with a scope while trying the read. You might unplug the EV2400 & restart the software also. Be sure there is no another instance of the software or a BQStudio running which has claimed the interface.
Hi WM5295 Thanks for providing your checklist. I worked through it and it is now working once again. I had mistakenly been pressing the button labelled Display and not the Boot button. Cheers, Mike
|