• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 78 subscribers
  • Views 1199 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-EXP430FR5994: CCS/MSP-EXP430FR5994 bricked on MSP-FETs / eZ-FETs update

RIRO
Prodigy 150 points
Part Number: MSP-EXP430FR5994
Other Parts Discussed in Thread: MSP-FET, UNIFLASH, ENERGIA, MSP-EXP430F5529LP

Tool/software: Code Composer Studio

I just bricked two MSP-EXP430FR5994 using:

  • CCS  Version: 9.3.0.00012.
  • windows 10
  • system has only had 9.3.0 installed on it.

  1. Started a new project.
  2. went to debug
  3. Prompted to update firmware 

    MSP430: Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE.

  4. Ran the update with the following results "MSP430: Error: MSP-FET / eZ-FET core(communication layer) update failed"
  5. Tried debug and Identity with a new message: 

    MSP430Error 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.

  6. with the following result message:"MSP430Error: MSP-FET / eZ-FET recovery failed"

  • hunted through the E2E for similar issues, but did not find a solution.
  • Tried CCS cloud, but same result.

Is there a solution to this problem?

Thank you

  • 0
    TI__Mastermind 41040 points

    Hello,

    I found a few threads with similar issues. Some have advised that recovering the board from a different PC worked. I have not seen this issue before, but you may also try recovering with Uniflash or Energia if you do not have another PC available. Let me know if either of those work to recover the boards. When you have the board plugged in, does it show up under the COM ports in device manager?

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

    https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/483543

  • 0 in reply to Eddie LaCost
    Prodigy 150 points

    No alternate computer at this time. (thought I think a fix rather than a patch should be found)

    The enumeration shows up as an HID ( USB Input Device )

    Information from Properties (Device manager):

    Device USB\VID_2047&PID_0203\5&8725cca&0&2 was configured.

    Driver Name: input.inf
    Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}
    Driver Date: 06/21/2006
    Driver Version: 10.0.18362.175
    Driver Provider: Microsoft
    Driver Section: HID_Inst.NT
    Driver Rank: 0xFF3202
    Matching Device Id: USB\Class_03
    Outranked Drivers:
    Device Updated: false
    Parent Device: USB\ROOT_HUB30\4&7b9582d&0&0

    What other information do you wish to capture from my system that could help in the diagnosis?

    Additional brainstorming notes:

    • Other MSP EXP boards working correctly.
    • no recovery on different UBS ports
    • cold reboot no effect
    • Starting new CCS project no effect.

  • 0 in reply to RIRO
    Prodigy 150 points

    update.

    Used another PC and used MSP430FLasher.exe to bring the MSP-EXP430FR5994 back to life.

    went back to my development laptop, and CCS re-bricks it when performing firmware update.

    For right now, (this is effecting development) can i use MSP430FLasher.exe to download the firmware which the CCS is trying to download? where it it?

    Also, the update is now corrupting my newly purchased MSP-EXP430F5529LP in the same way.

    Since I have a reproducible process, is there any thing I can do to provide information so we can solve this?

    Added point: at the start of the update, the USB re-enumerates.

     

  • 0 in reply to RIRO
    Prodigy 150 points

    After multiple days lost in development, I finally got the system working again. But never found out why the dev-boards update failed.

    • Completely uninstalled CCS9
    • Uninstalled USB drivers.
    • Ran a scrub through all the USB history and removed all ID 2047 devices. (using usbdeview-x64) 
    • Search through all of windows for any MSP430 / msp usb files to purge.
    • Ran a couple of reboots for sanity check.
    • Installed CCS10 (which did have one error on running update:

      An internal error occurred during: "Computing size".
      Profile epp.package.cpp is not current. Expected timestamp 1589312186494 but was 1589311999679

    • reboot
    • all MSP dev boards now updating.

    I hope that someone at TI is investigating this issue for the long run, since it not an isolated incident.

**Attention** This is a public forum