• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 79 subscribers
  • Views 3479 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

MSP-FET: No debug probes/devices detected

MSP-FET: Uniflash shows "No debug probes/devices detected" when connected to a customized board(with MSP430FR6989 chip) through a MSP-FETFlash Emulation Tool.

Dongmeng Li
Prodigy 20 points
Part Number: MSP-FET
Other Parts Discussed in Thread: UNIFLASH, MSP430FR6989,

Hi All,

I'm trying to program the MSP430FR6989 chip on a customized board through the MSP-FETFlash Emulation Tool. When I tried to flash my .out file in Uniflash, it shows me "No debug probes/devices detected".

The drivers have been installed, and I can also see 'MSP Application UART1' and "MSP Debug Interface" device in device manager. Whenever I plugged in my MSP430 programmer, Uniflash could sense it and did an auto-detect, but still no devices been detected. 

I tried the "New Configuration" and manually chose my device and port. At the first start, the MSP-FET has been updated its own firmware, but when I continued flashing the .out file, it showed me that no devices detected error again. (so I believe it can recognize the MSP-FET but couldn't talk to the MSP430 chip)

My board was powered externally by a power supply. My operating system is Windows 10. JTAG is not likely to have a connection error. 

Is it likely to have something wrong between the MSP-FET and the target MSP430 MCU? Any idea on how to debug this?

Thank you,

DL

  • 0
    TI__Mastermind 28745 points
    Hello DL,

    If Uniflash is showing "No Debug probes/Devices detected" can be either it doesn't see the FET or that it sees the FET fine and can't detect the device. If the MSP-FET is showing up device manager and causing Uniflash to re-attempt an auto-connect then it's probably an issue between the programmer and your device.

    Figures 2-1 and 2-2 of the hardware tools user guide show the exact connections and components required for programming. I would double check to be sure you are following them exactly. www.ti.com/.../slau278ae.pdf

    The most common issue is the power connections or the pull-up and filter cap values on the RST line.

    Please double check these and let me know what you find.

    Thanks,
    JD
  • 0 in reply to JD Crutchfield
    Intellectual 260 points

    Hi,
    Here’s what we have.  A 22uF cap not shown is next to the MSP4306986.  The symptom is actually intermittent.  Sometimes we’re able to detect the MSP-FET sometimes we can’t.  We tried 1n and 2.2n on C2, but no difference.
     Thanks.

  • 0 in reply to Shang Wu18
    Intellectual 260 points

    Also the resistor and capacitors are next to JT1, which is about 2 inches from the MSP430.

  • 0 in reply to Shang Wu18
    TI__Mastermind 28745 points

    Hello Shang,

    Schematic looks okay to me.  Do you have an EVM you can test with?  That way you can figure out if it's a hardware issue or not.  

    Also, I'm going to be traveling for the next week so my responses will be very delayed.  Someone else from the community may be able to assist.    

    Thanks,

    JD  

  • 0 in reply to JD Crutchfield
    Prodigy 20 points

    Hi JD,

    Thank you very much for the replies. We found out the problem was due to a damaged HDMI cable. It causes the system sometimes works and sometimes doesn't. We were able to flash the firmware successfully with another HDMI cable. 

    Thanks,

    Dongmeng 

**Attention** This is a public forum