• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 78 subscribers
  • Views 1435 views
  • Users 0 members are here
Support feedback
Options
Options

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.

MSP-FET: MSP-FET Cannot Detect Device

Jon Vogel
Prodigy 100 points
Part Number: MSP-FET
Other Parts Discussed in Thread: MSP430F5438A, UNIFLASH, , SEGGER

Hi,

I'm new to the MSP430 family.  I just got a MSP-FET programmer/emulator for development with an existing product which uses the MSP430F5438A.  When I attempt to connect to the device, the MSP-FET reports that it "Could not find the device (or the device is not supported)."   I created test projects in both CCS and IAR, making sure to set the micro as the MSP430F5438A.  Then, I selected the debugging tool as the MSP-FET.  Both IAR and CCS report the same issue.  When I attempt to program from the command line tool, MSP Flasher, it fails, while creating the attached log.  The Uniflash tool also fails.

When I run MSP Flasher in DETECT mode, it locates the debugger and opens a debug session with it.  Also, the green light on the MSP-FET is on and the red light blinks with activity when it is being accessed.  I have both a "MSP Application UAT1" on COM7 and "MSP Debug Interface" on COM8.

The control I am attempting to program is definitely powered-up.  The original software is still running on it and responds to user interaction.

I'm used to using Segger J-link-Plus with ARM processors, so this situation has me a bit befuddled.  Can anyone offer any advice?

Thanks,

Jon

Log from MSPFlasher:

Tue Sep 24 15:23:06 2019:    * -----/|-------------------------------------------------------------------- *
Tue Sep 24 15:23:06 2019:    *     / |__                                                                   *
Tue Sep 24 15:23:06 2019:    *    /_   /   MSP Flasher v1.3.20                                             *
Tue Sep 24 15:23:06 2019:    *      | /                                                                    *
Tue Sep 24 15:23:06 2019:    * -----|/-------------------------------------------------------------------- *
Tue Sep 24 15:23:06 2019:    *
Tue Sep 24 15:23:06 2019:    * Evaluating triggers...
Tue Sep 24 15:23:06 2019:    * Invalid argument for -i trigger. Default used (USB).
Tue Sep 24 15:23:06 2019:    * Checking for available FET debuggers:
Tue Sep 24 15:23:06 2019:    * Found USB FET @ COM8 <- Selected
Tue Sep 24 15:23:06 2019:    * Initializing interface @ COM8...done
Tue Sep 24 15:23:06 2019:    * Checking firmware compatibility:
Tue Sep 24 15:23:06 2019:    * FET firmware is up to date.
Tue Sep 24 15:23:06 2019:    * Reading FW version...done
Tue Sep 24 15:23:06 2019:    * Setting VCC to 3000 mV...done
Tue Sep 24 15:23:11 2019:    * Accessing device...
Tue Sep 24 15:23:16 2019:    # Exit: 16
Tue Sep 24 15:23:16 2019:    # ERROR: Unknown device
Tue Sep 24 15:23:16 2019:    * Powering down...done
Tue Sep 24 15:23:16 2019:    * Disconnecting from device...done
Tue Sep 24 15:23:16 2019:    *
Tue Sep 24 15:23:16 2019:    * ----------------------------------------------------------------------------
Tue Sep 24 15:23:16 2019:    * Driver      : closed (Internal error)
Tue Sep 24 15:23:16 2019:    * ----------------------------------------------------------------------------
Tue Sep 24 15:23:16 2019:    */

  • 0
    TI__Mastermind 28516 points

    Hi Jon,

    Are you using our Lanuchpad or your own board? Can you provide a connection diagram between the board and the MSP-FET?

    Best Regards

    Johnson

  • 0 in reply to Johnson He
    Prodigy 100 points

    It's our own board.  The connection is the 14-pin MSP-FET JTAG connector.  I inherited this project from an outside company, but I know that the connector works because it's how they have been programming the board.  I just don't know what I am doing wrong that I can't program the board.

    Thanks,

    Jon

  • 0 in reply to Jon Vogel
    Prodigy 100 points

    I've learned, from googling around, that the device not recognized error comes from the probe not being connected to the device properly.  When I soldered a header directly to the 14-pin header pad on the board, I was able to program it.  When going through the outside supplied factory test fixture with pogo pins, it didn't detect the device.  So, apparently something is wrong with the test fixture I was provided.

**Attention** This is a public forum