EVM430-FR6047: HID Bridge connected -- waiting for device

yue cao

Part Number: EVM430-FR6047
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

I just received my EVM430-FR6047 board and followed the User's Guide to set up the device and GUI, but it doesn’t work.

First, I flashed the "MSP430FR6047EVM_USS_Water_Demo_LPM_02_40_00_00.txt" image onto the board using UniFlash 8.8.1. However, when I tried to connect the board through the GUI (USS-02_40_00_00) on my Windows 11, it displayed: "HID device connected, but could not connect to it." I also attempted to connect it in a Ubuntu environment, but the error changed to: "HID Bridge connected -- waiting for device."

I also tried connecting/disconnecting my ultrasound transducer from the board, and nothing changed. Now the LEDs look OK: D101 and D201 are illuminated and D202 blinks.

I have reviewed other related questions on the forum, but none of the solutions resolved the issue.

Does anyone have an idea of how I can fix this issue?

Thank you very much!

Andy

1 month ago

0 Helic Chi 1 month ago

TI__Genius 9122 points

Hi, yue cao

On your EVM, there is no connection for RXD and TXD, but for using I2C, can you try to connect to MSP430 using I2C.

Also, if this is not work too, please go through the guide file in this page:

https://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/USSSWLib/USSSWLibWater/latest/

Regards,

Helic

0 yue cao 1 month ago in reply to Helic Chi

Prodigy 10 points

Hi Helic,

Thank you so much for your reply!

I am completely new to hardware, so I may not fully understand your suggestion. I tried connecting the RXD and TXD using jumpers, but it still doesn't work. Do I need to make any software configurations to connect the MSP430 using I2C?

On my Windows system, I still encounter the following error: "HID device connected, but could not connect to it."

I also tested it on my Ubuntu system and noticed that the error "HID Bridge connected -- waiting for device" still persists. However, when I click on ADC Capture, it captures some random signals. Additionally, an error message appears stating: "No signal detected in the up and downstream channels."