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: Can't get BQ27441EVM-G1A to work with BQStudio

Part Number: EV2400
Other Parts Discussed in Thread: BQSTUDIO, BQ27441EVM-G1A,

Hi there!

I just received my EV2400 and BQ27441EVM-G1A in the mail. All up this costed me $500 AUD from Digi-Key - a lot of money to spend, but I was keen to get my hands on using BQStudio as this seems like such a powerful tool. Unfortunately I've been having some serious issues. You can see my setup below. The battery has 3.8V at present, and the resistive load is definitely being powered - so therefore, the BQ27441 would have power.

My EV2400 is recognised fine, and I have updated the firmware as appropriate as you can see (see the version is already 0.28 since I have done the update). All 3 LEDs are on, and everything is fine :)

However, when  move to using BQStudio I am running into some major issues. The first one is shown below - it says the BQ27441 is "not compatible with this application". This is clearly wrong, as the page for the BQStudio has this device on it's list of Supported Devices - which is the whole reason I bought the $100 development board in the first place.

I thought this message may just be a disclaimer, so I moved on. I then noticed on the left hand side the USB symbol is present, and it seems it has detected the EV2400. However, the IC symbol, and battery symbol were all greyed out.

Lastly, I tried to create a new project and setup with the Q&A session. But I just get errors :(

Please help me. I love TI and I love these new tools I have purchased, but for paying so much money it is giving me a lot of trouble. We have used the BQ27441 on a wearable device that is going to mass-manufacture soon, which benefits TI significantly for your sales - but I can't push forward without being able to program and calibrate production boards with this device!

If it was a custom PCB I was doing this on, I would think maybe it was my fault. But this is using TI software, with a TI firmware board interface, communicating to a piece of TI hardware evaluation - so it can't be my fault sadly.

Thank you. I look forward to hearing any help.