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/MSP430FR4133: eZ-FET won't update

Part Number: MSP430FR4133
Other Parts Discussed in Thread: MSP-FET, MSP-FLASHER

Tool/software: Code Composer Studio

New, just out of the box MSP430FR4133.  I tried to test example TI code but when I went to Debug I got message saying eZ-FET needs updating so I selected update.  Update failed so I tried Recover.  Recover failed so what should I try next?

  • I should add that the error message I receive when trying to recover the ez-FET is:

    Starting Debug Server ...
    MSP430: Error initializing emulator: MSP-FET / eZ-FET recovery failed

    I've found a few other instances of this problem on the forum but no definitive solution.

    Any help would be greatly appreciated!

  • Hello,

    Are you able to see the connected eZ-FET in device manager? It should look something like this.

    Can you post a screenshot of your device manager showing UART1 and Debug Interface? You might also want to try swapping USB cables and ports on your computer.

    Regards,

    Ryan

  • Hello Ryan,
    I don't see the eZ-FET connected in Windows Device Manager. 
    Interestingly, I was able to Recover the eZ-FET by going back to CCS Version: 6.0.1.00040.  I attempted to debug code to blink LED; V6 identified that the eZ-FET needed recovery and it reprogrammed successfully.  I was then able to download and run code on MSP430FR4133.  But then when I went back to CCS Version 7 and went to debug code, it failed and said needed recovery but recovery did not work in Version 7.  However, I was able to go back to 6 and recovery worked again.
    My goal was to compile the OutOfBox example so I tried but CCS Version 6.0.1.00040 gave some errors because of missing #DEFs.  So then I tried Version 6.2.  I was able to compile the example but when I went to debug the eZ-FET failed again.  So I went back to 6.0.1.00040 and recovered eZ-FET.  But I'm still struggling trying to run the example in CCS Version 6.0.
    I guess I could try to install CCS Version 7 on a different PC?
    Thank-you,
    David Wilhide
    719-425-1918
  • Hello Dave,

    Can you test and see if the issue also happens when using the latest MSP-Flasher and if you can recover the LP using the MSP-Flasher?
    I want to deduce if this issue is IDE or debug stack related.
    Could you also copy the MSP430.dll from the CCSv7 installation to the CCSv6 installation (please make sure you make a backup first) and check if he can still update/recover the LP using CCSv6?
  • Hello Jace,

    I've downloaded v1.3.16 of the MSP-Flasher and tested it with my MSP430FR4133 Launchpad.  Here is the error I received:

    MSPFlasher 1.3.16
    Evaluating triggers...done
    Checking for available FET debuggers:
    Found USB FET @ COM11 <- Selected
    Initializing interface @ COM11...done
    Checking firmware compatibility:
    The firmware of your FET is outdated.
    Would you like to update it? <Y/N>: y
    ********************************
    Initializing Upate Bootloader.
    Programming new firmware:
    ||||||| 100% Update Failed.  <R>etry/<C>ancel? c
    Exit: 49
    ERROR: MSP-FET / eZ-FET core<communication layer> update failed

    I will copy MSP430.dll from CCSV7 to CCSv6 and test next (after making backup of .dll!)

    thank you,

    Dave

  • Hello Jace,
    I copied MSP430.dll to the Version: 6.0.1.00040 drivers folder. I then started V6.0.1.00040, clicked on Debug for my default project and received the following
    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.

    I selected Recover and got the following:
    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.
    MSP430: Error: MSP-FET / eZ-FET recovery failed

    I then exited V6.0.1.00040, copied back the original V6 MSP430.dll, started V6.0.1.00040, clicked on Debug :
    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.

    I selected Recover and got:
    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.
    I selected “Update” (note this option did not appear when I was using V7 MSP430.dll in V6). Update was successful and project ran.

    Please let me know if there is anything else you would like me to try.
    Regards,
    Dave
  • Dave,

    thanks for the additional information. let me get back to you on this.
  • Hello Dave,

    Can you provide the DLL version numbers for both of your installations? Can you also give copies of these DLLs?  We are trying to reproduce the issue on our side.

  • Hello Jace,

    Here are the .dll versions:

    Version 6 .dll 3.4.1.0

    Version 7 .dll 3.10.1.000

    Do I attach the files using the "Insert File" button in the Forum editor?

    Thanks - Dave

  • V6MSP430.dll.txtV7MSP430.dll.txtHello Jace,

    The first file is V6 DLL and second file is V7 DLL.  I had to add the .txt extension since uploader won't allow .dll

    Dave

  • Dave,

    Our Tools team is still looking into this. Will update this thread once we know more.
  • Hello Dave,

    We have not been able to reproduce your issue. The V7 DLL works fine for our boards. Interestingly enough, we where unable to use the V6 DLL with CCS7. Can you try updating CCS7 to make sure you have the latest versions?

  • Hello Dave,

    Where you able to update your CCS and MSP-FETs tot he latest version?
  • Hello Jace - I've uninstalled CCS V7.3 using the uninstall program in the TI program group (not from Control Panel).  Then downloaded 7.4.0.00015 and installed.  I then tried to program MSP430FR4133 with OutOfBox demo.  I received the same sequence of messages:

    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.

    I select Update and receive:

    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.

    I select Recover, there is a several second lag then I receive the message:

    MSP430: Error: MSP-FET / eZ-FET recovery failed

    So then I plugged in my 3rd MSP430FR4133 which I had ordered as a backup and get the same behavior.

    Should the MSP430FR4133 as received require an update to the Debug interface?  If so, should the update always fail and require Recovery?

    It seems in my case that the Recovery option is not communication with my MSP430FR4133.

    Regards,

    David

  • Hello Jace,
    Following up on my previous post, I tested CCS V7 and my MSP430FR4133 on a different computer and did not experience these problems.  So the problem must be in my primary computer hardware or setup.  I doubt the hardware since I am able to use CCS V6 with the same USB port to program the MSP430FR4133.  Perhaps there is a driver issue with my primary computer (Dell 620S desktop).   Regardless, it is clearly my issue and I apologize for not trying this sooner.
    Thank-you,
    David

  • Hello Dave,

    Glad you were able to solve your issue. Thank you also for providing some detail on your PC setup that is not working.