TPS8804EVM: Hardware not connected issue

Part Number: TPS8804EVM
Other Parts Discussed in Thread: USB2ANY, , TPS8804

Tool/software:

Hi TI Team,

Regarding TPSEVM board connection with USB2ANY adaptor and evaluate using TPS GUI (TPS880x-1.0.0.setup-win_7.3.0.), 

Summary: 

Shall we get solution for the issue "Hardware not connected" and "Device Disconnected"

Details:

Enclosed the steps(with snaps) we followed in the attachment.

We got issue at step 4 and step 6.(Expected and actual results placed)

Please have a look and guide us solution to get out from the issues at step 4 and 6.?

 

Advance Thanks for the reply

 TPS_GUI_Steps.docx

Regards

Selvam

  • Hi Selvam,

    It sounds like you might be attempting to interface between the Windows PC and the TPS8804EVM with USB2ANY, but using a procedure intended for the MSP430 LaunchPad?

    If you are using the USB2ANY, you want to follow the steps mentioned in the TPS8804EVM User's Guide.  This should result in the USB2ANY showing up as the "USB2ANY/One Demo device" under Window's Settings / Bluetooth & devices / Devices.

    The software mentioned in the Dual-Ray Smoke Detector with TPS8802 and MSPM0 MCUs is intended to be used with the LP-MSPM0L1306 LaunchPad.

    Thanks & Regards,

    Jesse

  • Good day Jesse,

    Thanks for the input.

    Yes, we are attempting to interface between windows PC and TPS8804EVM with USB2ANY and we followed procedure @ 

    Using the TPS8804EVM (Rev. A) 

    Once connected USB2ANY adaptor, we are getting below message (Enclosed snaps also - USB2ANY_Detection_Name.png)

    Windows Name                                                                                                 Message

    Under Window's Settings / Bluetooth & devices / Other Devices    --       MAP430-based HID Device"

    Under TPS GUI software TPS880x 1.0.0                                             --       MSP430-based HID Device waiting for data…

    In both Setting window as well as TPS GUI software, USB2ANY showed as "MSP430-based HID Device". 

    But not getting the name as "USB2ANY/One Demo device"

    Is any update happened regarding USB2ANY name? and

    Please guide as to resolve the issue of "Hardware not connected/Device disconnected" for TPS8804 EVM PC interface.

    Hope able to see the attached document about followed steps available in initial request form.

    Regards

    Selvam

     

     

  • Hi Selvam,

    Yes, I was able to see the attachments.  They were helpful in understanding the situation.

    I believe that I was able to reproduce your error, and I was able to fix it on my setup by updating the USB2ANY firmware.  I downloaded and ran the USB2ANY Explorer (slvc695) software.  When the USB2ANY Explorer software detects old firmware on your USB2ANY, it should provide on-screen instructions to update the firmware on your USB2ANY to version 2.8.2.0. 

    At some point, the firmware upload process will ask you to press the S1 button while plugging in the USB.  If you are like me and do not have 3 hands, you might find it easier to remove the screw from the back of the USB2ANY cover so that you can gain access to the switch without needing a paperclip for the tiny hole.  :-) 

    After completing the firmware upload, you can close the USB2ANY Explorer and re-open your TPS880x GUI.  It should be able to detect the USB2ANY at that point.  You will also notice that it will now be listed as the "USB2ANY/OneDemo device" in Window's Settings / Bluetooth & devices / Devices.

    Thanks & Regards,

    Jesse

  • Hi Jesse,

    Thanks for the solution.

    Great its working, able to connect and corresponding following success messages

    1. "USB2ANY/One Demo device" Under Window's Settings / Bluetooth & devices / Other Devices 

    as well as under TPS GUI software

    2. Hardware Connected 

    We will check and will revert back if any other challenge.

    BTW, I'm also having two hand like you, So I got third hand from my team member and access the tiny hole Slight smile

    Thanks

    Selvam

  • Hi Selvam,

    That is good to hear! :-)

    Thanks,

    Jesse