MSP430FR6047: No signal detected in up or downstream channel - HID Bridge connected, waiting for device

fnails

Part Number: MSP430FR6047
Other Parts Discussed in Thread: UNIFLASH

Hello,

I am working with the evaluation board EVM430FR6047.

First day working with it, I installed drivers and USS Design Center SW and all worked proprerly.

Suddently at one moment all stop to work, and I got Error Code 255 "Unknown error". I tried to reinstall, connect and disconnet, install MSPWare and so on. Nothing worked

So I decided to re-flash the Firmware by installing uniflash 8.1.1 and reload the Demo Image "MSP430FR6047EVM_USS_Water_Demo_LPM_02_20_00_04.txt". Flashing gone well.

Now I get a different error code 126 "No signal detected in up or downstream channel", and the connection status gives "HID Bridge connected - waiting for device". The LED3 in blinking red.

Strangely if I try to capture the signal through "ADC Capture" I have some proper signal but I cannot changed any parameter because the "Request Update" button is greyed.

I am working with Windows 10 Enterprise (20H2), the EVM430FR6047 board and a connected pipe where transducers are properly connected to the board.

over 2 years ago

0 fnails over 2 years ago

Prodigy 10 points

0 Cash Hao11 over 2 years ago

TI__Mastermind 46765 points

Hi,

Okay, you can still program the chip. Could you use the CCS and run in debug mode and check the ADC data in the MCU? You can find the "gUSSLEATempMemBlock" which stores the UPS and DNS ADC data.

Best regards,

Cash Hao

0 Dennis Lehman over 2 years ago in reply to Cash Hao11

TI__Guru 71216 points

Hi fnails,

This error typically indicates that one or both transducers are not connected, OR, there is not a complete fluid path between them. Can you confirm you have transducers connected and fluid completely fills the pipe?

You indicated you can capture the ADC waveform. Can you share so I can see how it looks? Can you also provide a screen shot of the "Advanced Parameters" tab?

0 Dennis Lehman over 2 years ago in reply to Dennis Lehman

TI__Guru 71216 points

I did some digging and apparently there there is a possibility an incorrect parameter set in Pulse generator may cause the MCU to not communicate with the GUI, hence the "waiting for device...".

Interestingly, I used the same image file as you and programmed my target using UNIFLASH and see error #14, which is "Pulse Generate parameters are invalid."

And when I build the example project in CCS and program the device, then push the reset button - same issue. But if I program and run in debug mode, all is well. Let me continue to investigate. What happens if you run the EVM in debug mode?

0 fnails over 2 years ago in reply to Dennis Lehman

Prodigy 10 points

Hello Dennis,

Thank for your reply.

Here in attachment the tab of "advanced parameters". I set the clock to 8MHz as suggested in TI documentation.

This morning I could not reproduce the ADC Capture again. I wish I could change some parameters but again the "request update" is not active (greyed).

Do you suggest to run it in debug mode? I need to check how to made it and try. I'll keep you update,

Filippo

0 fnails over 2 years ago in reply to fnails

Prodigy 10 points

0 Cash Hao11 over 2 years ago in reply to fnails

TI__Mastermind 46765 points

Hi,

Any luck on the debug mode?

Best regards,

Cash Hao

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP430FR6047: No signal detected in up or downstream channel - HID Bridge connected, waiting for device