• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 79 subscribers
  • Views 642 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430f5529 CC Error Messsage: Error Initializing Emulator

Michael Choi
Expert 1345 points
Other Parts Discussed in Thread: MSP430F5529, MSP-EXP430F5529LP

Dear Sir:

     I am new to the MSP430f5529 product line.  I purchased the Launchpad Evaluation Kit. 

     This is the problem.   I followed Lab 1 of the TI RTOS Workshop.   This lab verifies that the Code Composer (CC) 5.3 software has been installed correctly.   The lab only seeks for the operator to import a user defined target configuration and launch the target configuration.

      When I launch the target configuration this error message is returned:

MSP430: Error initializing emulator: No USB FET was found

      I know that for some unknown reason the TI software install failed.  

      I am enclosing a copy of a document that may tell you where the source of the error lies.

Fullscreen 7331.ti_msp430driver_setup_1.0.0.1_install.log Download 
Log started 05/31/2014 at 20:26:35
Preferred installation mode : win32
Trying to init installer in mode win32
Mode win32 successfully initialized
Preparing to Install
[20:26:54] eclipsedir = 
Preparing to Install
Creating directory C:\ti\fetdrivers\emulation
Creating directory C:\ti\fetdrivers\emulation\drivers
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\DPInst
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPInst64.exe
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPInst.exe
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC\msp430tools.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC\msp430tools.cat
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF\430CDC.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF\430cdc.cat
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_32
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_32\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_32\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_32\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_32\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_32\WdfCoInstaller01009.dll
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_32\difxapi.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_64
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_64\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_64\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_64\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_64\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_64\difxapi.dll
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_64\WdfCoInstaller01009.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_32
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_32\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_32\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_32\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_32\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_32\WdfCoInstaller01009.dll
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Win7_32\difxapi.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_32
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_32\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_32\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_32\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_32\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_32\WdfCoInstaller01009.dll
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_32\difxapi.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_64
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_64\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_64\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_64\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_64\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_64\WdfCoInstaller01009.dll
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_XP_64\difxapi.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_32
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_32\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_32\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_32\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_32\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_32\WdfCoInstaller01009.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_64
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_64\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_64\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_64\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_64\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_64\WdfCoInstaller01009.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_32
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_32\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_32\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_32\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_32\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_32\WdfCoInstaller01009.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_64
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_64\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_64\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_64\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_64\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Win7_64\WdfCoInstaller01009.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_32
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_32\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_32\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_32\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_32\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_32\WdfCoInstaller01009.dll
Creating directory C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_64
Unpacking files
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_64\umpusbvista.sys
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_64\ump3410.cat
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_64\umpf3410.i51
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_64\usbuart3410.inf
Unpacking C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_XP_64\WdfCoInstaller01009.dll
Directory already exists: C:\ti\fetdrivers
Unpacking files
Unpacking C:\ti\fetdrivers\MSP430_USB_Drivers_Software Manifest_WIN.pdf
Executing C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst.exe  /q /se /sa /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF"
Script exit code: 256

Script output:
 

Script stderr:
 Program ended with an error exit code

Error running C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst.exe  /q /se /sa /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_eZ-RF" : Program ended with an error exit code
Executing C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst.exe /q /se /sa /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_32"
Script exit code: 256

Script output:
 

Script stderr:
 Program ended with an error exit code

Error running C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst.exe /q /se /sa /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_FET_Vista_32" : Program ended with an error exit code
Executing C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst.exe /q /se /sa /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC"
Script exit code: 256

Script output:
 

Script stderr:
 Program ended with an error exit code

Error running C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst.exe /q /se /sa /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_CDC" : Program ended with an error exit code
Executing C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst.exe /q /se /sa /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_32"
Script exit code: 256

Script output:
 

Script stderr:
 Program ended with an error exit code

Error running C:\ti\fetdrivers\emulation\drivers\msp430\DPInst\DPinst.exe /q /se /sa /path "C:\ti\fetdrivers\emulation\drivers\msp430\USB_VCP_Vista_32" : Program ended with an error exit code
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 05/31/2014 at 20:27:07

        I hope you will be able to click on this document and read the installation error messages.

        This error document is my best guess as to the source of the error message that I saw in the screenshot.   

        I am using the Vista O/S and I do not know why the installation failed (if this is the source of the problem).  

        I was hoping that you could reply with some feedback and what I should do to remedy my problem.  I believe that it is possible that  a correct sequence of software installation may have to be followed.   If  this is the case, I need to know the correct uninstallation method and the correct software installation sequence to follow.

        Thank you for your time. 

 

 

     

  • 0
    TI__Guru* 79301 points

    Hi Michael,

    CCSv5.3 was released long before the MSP-EXP430F5529LP Launchpad, so I suspect there may not be support for the emulator on the F5529 launchpad in that version. Could you please try downloading the latest version of CCS (6.0) and see if you are able to program the device? If you are reluctant to move to CCSv6, CCSv5.5 should at least support the 5529 launchpad.

    Regards,

    Katie

  • 0 in reply to Katie Pier
    Expert 1345 points

    Dear Ms. Pier;

         Thank you for your reply.   I purchased another TI kit and I went through a lot of trouble getting that kit configured, therefore, I would prefer not to uninstall the CCv5.3.   Can I download CCSv6 and have it run side by side with CCv5.3?

          In my initial letter, I stated that there was an issue with a driver download which was most likely the source of the error message that I posted.  

           Anticipating that I may have to uninstall and reinstall software, I made reference to a sequence of operations. 

           1) Uninstall existing software (which I would prefer not to) and also

            2) Delete any files or folders that may have been left from the first install (I am referring to the driver install that failed) that may affect a new install.

            Can you please answer my first question with regard to running the two CC programs side by side?

             Then can you go into detail about deleting any files that may have been left over from the failed first attempted driver installation.    I did a typical install, therefore, in your reply, you can direct me to the address of the folder(s)where I would look to see if any existing files need to be deleted (so that if another installation needs to be conducted the second installation will proceed without any unnecessary complications).

            3) Last request, I am using Windows Vista and to be certain that my second driver installation will be successful, can you please point me to the drivers that you believe will remedy my error message (drivers compatible with the CC6 install).   If you can't point me to the drivers directly, then can you please name the drivers so that when I look on the webpage that you point me to, there will be room for confusion.

             Again, I would like to thank you for your reply and I look forward  to reading your next reply.

  • 0 in reply to Michael Choi
    TI__Guru* 79301 points

    Hi Michael,

    Where did the log file come from - was this a log generated simply when you installed CCSv5.3? Or had you tried to install something else in addition? When you install CCS you shouldn't have to run anything additional in order to have the drivers installed - ccs should already have installed them.

    You can certainly have two CCS installations that can run side-by-side - this is actually the setup that I use because I maintain a few different CCS versions on my computer to help support customers. Here is the method I use to install CCSv6 without interfering with my CCSv5.5 install for example:

    Normally, CCS will default to installing in C:\ti directory. To maintain independent versions of CCS, I instead tell the installer to install in a different directory. I usually name mine based on the CCS version - for example, I made a folder C:\ti_6_0 for my CCSv6.0 install. Then in the CCS installer, when it asked about an installation directory, I pointed it to this folder instead of C:\ti. If you do this, you can have completely separate installations of CCS in your different folders. The important thing to remember when doing this is that if you add components later, you need to remember to tell them the correct install path so they don't go in the default C:\ti but rather in the directory for the CCS version that you intend to use.

    Regards,

    Katie

  • 0 in reply to Katie Pier
    Expert 1345 points

    Dear Katie;

    To answer your question:

    Where did the log file come from - was this a log generated simply when you installed CCSv5.3?

    I found the log file in this TI software created directory:

    C:\ti\fetdrivers\install_logs

    I can't tell you much more than this because the user "start up software" directions for these kits leave it up to the user to find most of the appropriate software and educational materials.   When we open the box that contains the kit the flyers lead us to a webpage and after that the trail goes cold because the webpage does not explicitly point the reader to a complete download list of software that is matched to the specific hardware.   

    I hope you find this information helpful.   I am going to download and install CC6 and tell you the outcome.

     

  • 0 in reply to Michael Choi
    Expert 1345 points

    Dear Katie;

         Thank you for your feedback.  

          I installed CC6 and there was no error message.   Problem solved.

          Again, I would like to thank you for your help.   Good Call.

**Attention** This is a public forum