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.

BQ25790EVM: Testing via USB2ANY

Part Number: BQ25790EVM
Other Parts Discussed in Thread: USB2ANY, , BQSTUDIO, EV2400, BQ25790

As per this forum post I'm trying to test the BQ25790EVM via the USB2ANY debugger. That forum is not seeing much official attention so I thought I'd ask a different question. Can I modify the registers of the BQ25790EVM via something other than GUIComposer, say for example CCS? Is there any guide for how to start this process via CCS or something with better documentation?

I'm at a standstill with lacking documentation on how to evaluate the BQ25790EVM because I can't even get it to connect via GUIComposer due to errors that just say "error" without any further help. Does TI have a more well documented tool to evaluate this BQ25790EVM using the USB2ANY or similar chips such that I can see what I am supposed to be doing to get things connected and working?

Best regards,
Christopher

  • Hi Christopher,

    You write directly to the I2C registers via SDA and SCL lines using any I2C engine.  You could also purchase an EV2400 and use BQSTUDIO software.  But I think your issue is firmware problem with USB2ANY box.  Try updating that first.  

    Regards,

    Jeff

  • Hi Jeff, yes, at long last after updating the firmware via the USB2ANY Explorer Software here:

    https://www.ti.com/technical-documents/mytilit/export-control?litId=SLVC695&fileType=zip&&ts=1648531195803

    I was able to make the connection successfully. Thank you for pointing that out. Please note that the remainder of this post is not aimed at you Jeff, as I appreciate your attempts to help.

    I would like to take the opportunity to urge the TI team to update the BQ25790EVM guide or take the product off the market. I must have spent a total of 30+ hours trying to debug the thing over the course of several weeks on here. Meanwhile I'm using eval boards from Microchip that are up an running in minutes. For the price tag on this eval board and the USB2ANY I expect a polished and finished working product. I may not be a huge or meaningful customer, but this experience has definitely pointed me away from using TI products for fear of wasting this much time in the future.

    On a more productive note, for a basic expected customer experience, the specific things that I recommend updating are:

    1. If the USB2ANY is in fact the way of the future for TI eval boards, then moving away from the EV2400 and BQSTUDIO references would be ideal and replacing them with USB2ANY and GUIComposer instructions within the eval board guide. If you have no guide, don't advertise it as a possibility.
    2. Add a troubleshooting section to the BQ25790EVM guide and make it very clear to check the firmware matches that used in the guide via the USB2ANY Explorer Software before proceeding. Be sure to include the firmware and any other dependencies (GUI Composer version, etc.) in any guide.
    3. Make it very clear on the USB2ANY webpage that updating the drivers (and therefore using the device) requires a Windows PC (every other reference to using it makes it sound like I should have been able to do all this from Ubuntu).
    4. Add error or debugging to the connection of the TI Cloud Agent that actually gives helpful info other than "Error". If there are connection issues, make a default error message to check the USB2ANY firmware and links on how to do so.
    5. Include a link to the GUI Composer demo (https://dev.ti.com/gallery/view/BatteryChargers/ticharger_gui) in the product page.

    A very disappointed customer,
    Christopher

  • Hi Christopher,

    I apologize for the confusion.  BQ25790 was our first device to use USB2ANY and GUI composer.  Thanks for helping us debug. I will communicate your recommendations to my management.

    Regards,

    Jeff

  • Thanks Jeff. I also wanted to follow up and mention that I am still unable to get the connection to work after the firmware update on Ubuntu 20.04. Not really interested in jumping back into the rabbit hole of debugging it, so I'll just evaluate this one on Windows. You may also want to explicitly state that this whole setup is only tested and working on Windows for the time being.

  • Noted.  Will update in the user's guide.

    Thanks.

    Jeff