• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 78 subscribers
  • Views 3510 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.

CCS/MSP-EXP430FR2433: "MSP430: Error: MSP-FET / eZ-FET recovery failed" firmware bricked?

M Spit
Prodigy 70 points
Part Number: MSP-EXP430FR2433
Other Parts Discussed in Thread: MSP430FR2433, MSP-FET, ENERGIA

Tool/software: Code Composer Studio

Hi,

I just received the TI launchpad for the MSP430FR2433 and wanted to try an example program. So I booted up CCS and loaded the 'Hello World' program for the proper MCU, which should print Hello World on a preferred output. I assumed this was over the USB UART so I opened Docklight (prefered console program), found the MSP UART Application port, opened a connection, and flashed the hello world program.

Here's where the problem started:
CCS asked me to update the firmware of the launchpad before flashing by pressing OK or Continue in a dialogue box.
The firmware flash failed and the USB devices (1 for UART application and 1 other standard device of the launchpad) in Windows device manager are gone.

Afterwards CCS said :
"MSP430: Error initializing emulator: One of the connected MSP-FETs / eZ-FETs debuggers needs recovery. Select 'Recover' to start the recovery process.  Note: Only one MSP-FET / eZ-FET debugger can be connected to your system during recovery."
So I did, but it gave the error
"MSP430: Error: MSP-FET / eZ-FET recovery failed".

I updated CCS to the most recent version through CCS itself and tried recovering, to no avail.

I think the brick happened because I had an open connection with the USB UART with 3rd party software while the firmware update was running.

I found some issues like this on the forums but they're all closed because the user didn't respond on the forum thread anymore. Is there a way to solve this issue?

With kind regards,

Merijn

  • 0
    TI__Expert 6635 points

    Hi Merijn,

    Did you come across the thread linked below?

    https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/562986?CCS-MSP-FET-eZ-FET-legacy-module-update-failed 

    There are several suggestions that I would recommend trying. Please take a look and let me know if you continue to have issues.

    Thanks!

    -Mitch

  • 0 in reply to Mitch Ridgeway
    Prodigy 70 points

    Hi,

    Navigating through all those referenced threads is kind of a mess, but here's what I've tried in those solutions:

    * Used Energia, still the same issue:

    error: MSP430: Error: MSP-FET / eZ-FET recovery failed
Failed: MSP430: Error initializing emulator: MSP-FET / eZ-FET recovery failed

the selected serial port
 does not exist or your board is not connected

    * Your linked thread didn't have the same issue; they still detected “MSP Application UART1”, which I do not.

    * other threads use the MSP-FET while I have a Launchpad with onboard debugger (eZ-FET). Maybe i can check if uploading firmware with the MSP-FET works (I do have one laying around) but i think it would still have issues with the USB interface, which I want to use for my project.

    * the same other threads have driver issues regarding the MSP-FET, while I think the update broke the communication interface on my launchpad. I do not see any devices that might be the Launchpad or its debug interface in device manager.

    * used a different USB cable, didn't work

    *grabbed a different launchpad, (MSP430-FR5994), still works and shows up in windows device manager

    I could try to hook the Launchpad on to a different windows machine in the hope it will magically work, but I doubt it.. Ill get back to you on that.

    Update:

    Apparently, using a different windows machine with an older CCS version (9.1), recovery magically worked.

  • 0 in reply to M Spit
    TI__Expert 6635 points

    Hi Merijn,

    That's great news! It sounds like the enumeration might have gotten corrupted on the original machine somehow. Thanks for digging into the solutions from the linked post - I know there was a good bit of information to sift through. 

    Glad you got things working :)

    -Mitch

  • 0 in reply to Mitch Ridgeway
    Prodigy 70 points

    Great news indeed, but how could this happen and how can I avoid this issue in the future?

    Next time i might not have access to another machine to try the same fix. I'd like to have a more reliable solution.

**Attention** This is a public forum