• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Subscribers 80 subscribers
  • Views 590 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.

MSP-FET: MSP-FET Rev 2.0.6 - Unable to perform Corrupted Firmware Recovery (Exit Code: 49)

Sam Selyutin
Prodigy 120 points
Part Number: MSP-FET
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hello,

I was attempting to use my brand new MSP-FET to program an existing EVM board I had ordered from TI.

When I first plugged in the board, all was showing correct under my COM section in Device Manager. Windows seemed to recognize it no problem.

However, I tried to debug and upload the program and was met with an enforced "Firmware update". After attempting the update, it failed and now my PC no longer recognizes my MSP-FET.

I have tried:

1) CCS 9.1 Recovery, did not work

2) CCS 12.8 Recovery, did not work

3) Tried both using the cold boot method by shorting the J2 header - which came unpopulated on my board, massive pain to deal with.

4) UniFlash recovery, did not work

5) MSP430 Flasher recovery, did not work

I feel like I am out of options at this point aside from sending this back to TI and getting another one. Also, why did I receive such an old revision of the MSP-FET (Rev 2.0.6)?

Please advise, thanks.

  • 0
    TI__Prodigy 520 points

    Hi! can you try the CCS12.8.1 It should have the fix -> https://www.ti.com/tool/download/CCSTUDIO/12.8.1 

  • 0 in reply to Shailesh Thakurdesai
    Prodigy 120 points

    Hi, what specifically would you like me to try in CCS12.8.1? I attempted recovery upon Identify Connection and it still is failing to recover.

  • 0 in reply to Sam Selyutin
    TI__Guru 67941 points

    Hi Sam,

    With the programmer connected, can you grab a screen shot of your Windows device manager showing the PORTS (COM and LPT).

    While you are there, right-click and try uninstalling the driver, then reboot your PC and see if this works.

  • 0 in reply to Dennis Lehman
    Prodigy 120 points

    Hi Dennis,

    Since the firmware became corrupted, the device does not show up under Ports, but only as an HID.

  • 0 in reply to Sam Selyutin
    TI__Guru 67941 points

    Hi Sam,

    I apologize for the delay in my response. Please send me a photo of the label on the bottom of the MSPFET.  Next, I will send you a friendship request.  I will ask for your complete mailing address in the message (I assume you are in U.S.) (this way it stays private).  I'll see if I can get one of our FAE's can get you another or I will send you one.

  • 0 in reply to Dennis Lehman
    Prodigy 40 points

    Hi Dennis,

    I am having the exact same issue, but I am UK based. What can I do? We ordered in next day guarantee as we need for an urgent project and now cannot progress.

  • 0 in reply to Andrew Norwood
    Prodigy 120 points

    Just adding this here for documentation purposes and additional tests.

    Andrew - try CCS6.0 - CCS6.1.0. I was able to get my MSP-FET to "almost" reprogram the firmware using that version of CCS. The red LED would flash and it would reach approx. 67% complete before ultimately failing and returning the same recovery failed message.

    Just wondering if yours exhibits the same behavior.

  • 0 in reply to Sam Selyutin
    TI__Guru 67941 points

    Sam - BTW, I checked the latest PCB files and rev 2.0.6 is the latest.  I sent you instructions in private chat to try something, and thought I would repeat here for the sake of others who find themselves in this situation.

    When attempting to use the recovery procedure, do you recall when you re-connected the USB cable your PC (windows) indicate a USB device is connected and if you look at your device manager it appears as a HID-compliant device?

    Try the recovery again by installing J2 jumper, the re-connect USB cable.  Do you know how to use PowerShell?  If yes, open a powershell command line interface and type the following:

    Get-PnpDevice -class HIDClass -PresentOnly | Where-Object{$_.PNPDeviceID -like 'HID\VID_2047*'} | ft InstanceId, Status, FriendlyName

    Do you see something like this with VID_2047 and PID_0204?

  • 0 in reply to Dennis Lehman
    TI__Guru 67941 points

    Hi Andrew,

    I'm working with Sam on this issue and we may have narrowed the issue down to Win 11 vs Win 10.  Sam has tried on 3 different Win 11 PCs with same result.  Sam is seeing if can find a Win 10 PC to try.  So question for you, what version are you running?

  • +1 in reply to Dennis Lehman
    TI__Guru 67941 points

    Looks like we found a solution. Sam installed a VM win10 on one of his PCs and using MSPFLASHER he was able to successfully recover and update both of his MSPFET programmers.  I'll work with the SW tools group to try to determine the specific cause and hopefully get this issue addressed once and for all.

  • 0 in reply to Dennis Lehman
    Prodigy 40 points

    Hi Dennis - Yes I am using Windows 11 Ver 10.0.22631 Build 22631. 

    Due to IT policy, I am unlikely to be able to install a VM on my machine. Is there any alternative solutions for us to try?

  • 0 in reply to Andrew Norwood
    Prodigy 120 points

    Use any Windows 10 machine. It does not have to be a VM.

  • 0 in reply to Sam Selyutin
    Prodigy 40 points

    Hi - yeah we don't have any Windows 10 machines on site, as IT policy say we have to keep updated to latest versions of everything. 
    I managed to take the programmer home and sort out on my personal PC and appears to behave.

    Would be beneficial if there was a Windows 11 workaround for other companies who have similar IT policies.

    Regards,

    Andrew

**Attention** This is a public forum