Error initializing emulator: Could not initialize device interface

You may want to try CCSv4.  There is a code size limited version that is the equivalent of the old CCE Core Edition.  This will include a newer version of the msp430.dll

http://tiexpressdsp.com/index.php/Download_CCS

John

how do you actually overwrite the msp430.dll? im using windows vista business and ccs v4. and i got the same problem and im not sure how to troubleshoot it

Basically you have to get your hands on an old copy of IAR. I have the ez430-rf2500, which came with a cd with IAR workbench kickstart edition v4.21. I then went into C:\Program Files\IAR Systems\Embedded Workbench 4.21 Kickstart\430\bin, found msp430.dll and copied it over the corresponding file in the CC directory. If you are having trouble, lemme know your email and I can send you the .dll I am using.

The problem is that I don't have the IAR System for my notebook. And I installed the CCSv4, I can debug it without the emulator connected, however when i debug it with the emulator connected, I got an error of "Error initializing emulator: Could not initialize device interface" is it a hardware problem or a software problem? my email is westlife_a1_boyband@hotmail.com

hi! I currently running on Windows Vista Service Pack 2, and using the eZ430-Chronos Development Tool as well as the CCSv4 included in the CD installation which came with the kit. Using my pc i was able to debug the source codes for the watch however, when I use it on my laptop which is runing on Vista, i keep getting errors whenever i connect it with the emulator "Error initializing emulator: Could not initialize device", all installation of the emulator seems alright and even check the device manager on my laptop, nothing seems amiss with the whole installation. So what is the main problem now? My laptop or installation had gone wrong somewhere? I need help ASAP! Thank you!!!!!!

Hi, can I have a copy of the msp430.dll as well? My email is infinitus.internal@gmail.com

Thanks.

hi, can you send me the.dll file? my email is jingjie@nus.edu.sg .. thanks a lot.

Hi, I have the same problem. Can you send the file to: mar.tas(---at---)seznam[dot]cz

thanks a lot

Martin

Hi, can I have a copy of the msp430.dll as well? My email is  anubhav@sumonaconsulting.com

as i am using code composer ver 4.0 and do not access to IAR

and I am using msp430 Lanch pad as emulator

Thanks.

Hi!

I have the same problem with CCSv4.0.

Could you send me the msp430.dll file?

My email is mickeygu@libero.it

Thanks

Michele

will u tell me what os is in your PC?

Windows 7

I believe it would be Windows 7 Home basic or Premium and I too had the same. There are two options to solve this issue:

1. Either upgrade your os to Windows 7 professional or Ultimate whcih has windows XP mode through which your setup can work well

2. Downgrade to Windows XP and again your issues shall get resolved.

Regards

Anubhav

While both of these options would likely work they really should not be necessary.  I run CCSv4 with MSP430 on Win7 64bit and there is no need to run it in virtual XP mode.

Have you tried the latest CCSv4 release to see if it helps?

John

its happening because you have old version of CCS, I resolved my problem with instaling newer release.

I installed the latest IDE (v4.2.0) and I'm running Win7 ultimate X64. I too get the error:

Error initializing emulator:
Could not initialize device interface

How do I check the devices and see if the launchpad is connected anyway?

arjan wiegel said:

I installed the latest IDE (v4.2.0) and I'm running Win7 ultimate X64. I too get the error:

Error initializing emulator:
Could not initialize device interface

How do I check the devices and see if the launchpad is connected anyway?

Get another msp430.dll from IAR Kickstart and copy it to CCE installation directory (C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\drivers)

I have the same problem with Windows 7:

Error initializing emulator:
Could not initialize device interface

I got to device manager and see the USB FET on COM1. I copied the msp430.dll from IAR 6.0 into CCE but got the same error

I also upgrade CCE to  Version: 4.2.4.00032 

Can a TI employee address this issue for WIndows 7 we seem to all be having and post the solution or msp430.dll as required?

It works fine on Windows XP.

Hi,

I have the same problem.  It works on XP 32 bits (old computer) but not on Windows 7 64bits (laptop).  I updated CCS4 to the most current version available and it still doesn't work.

Any real solution for this problem?

All,

Please don't copy dlls from different IDE version - this will most likely lead to issues.

Could you check whether your interface shows up in the device manager? Our grey USB debugger (MSP-FET430UIF) shows up under "Ports (COM & LPT)" --> MSP-FET430UIF - VCP (COMxx). If this is not the case then the driver wasn't installed properly. eZ430 emulators and LaunchPads are HID based and will be listed as an HID device in the corresponding section.

Have you installed CCS 4.2.4.00033 using the installer or did you ran the patch update?

Regards,

Markus

This is a fresh installation from the most recent version available.  I can see the MSP-FET430UIF-VCP (COM 5) in the device manager.

Tomorrow, I will uninstall everything and start back from scratch just to make sure i have everything up to date.

I removed everything I could see from Texas Instruments in the Control Panel - Programs and Features.

I rebooted my computer and then downloaded the most recent code composer for MSP430 and installed it.  The driver for Win 7, 64bits is also installed.

When I connect the MSP-FETU430IF, it shows in the Device manager as MSP-FET430UIF - VCP (COM5).

When I try to debug, I'm still getting the message: "Error initializing emulator: Could not initialize device interface".

It seems to see the MSP-FET430 but it stops when it tries to communicate with the microcontroller.

Any other suggestions?

I just turned off my computer and then turned it on.  After reboot, I plugged back everything and started CCS 4.  Now everything seems to work fine.

Well, I guess I posted too soon. I was able to run the code with the debugger on my PCB but soon I started to get some access errors in the console and then it wouldn't work.  I tried to reload and it locked up. 

I had to stop it with Window task manager, reboot, delete the .lock file and then tried again.  Then, my original problem is back.  I tried 3 or 4 times and it still doesn't work.

I'm suspecting the driver because with the same installation (except for the driver) it works fine on another computer with XP 32bits.  I'm running Win 7, 64bits. 

Any special installation procedure I should watch for when installing the driver?

Hello,

I also have the same problem, I get the error:

"Error initializing emulator: Could not initialize device interface" 

I have Windows Home Premium 64bits and  CCS Version: 4.2.4.00033

I am currently developing code for tms320f28069 and I would like to test the LaunchPad boards I have.

Can anyone from TI explain why does it seem to be an error on the setups from several people?

I would prefer not to install everything again since, I am working with the tms320 and don't want to mess that setup...

Any response will be welcome.

Best regards,

Filipe Teixeira

All,

Please note that this thread is very old and relates to different CCS versions and even different microcontroller platforms.

Also, please do not copy any DLLs from one to another IDE version, this is likely to cause issues. I strongly recommend using the latest version of CCS (CCSv5.1.1 + the MSP430 update 5.1.4.2, which you get when you seach for updates in CCS).

Please also visit www.ti.com/mspds for known limiations and in case of questions. Please let me know in case you should still experience any issues.

Regards,
Markus

I did what you sad, downloaded the latest version and after that did the uptade.

It worked fine.

But in the day after that it started to shows up the same message (could not find the driver emulator in the specific COM port).

What I know now is that CCS v5 is able to work, but for sure it needs some configuration on it after the instalation.

May be some procedure on the Device Manager of Win 7 or some procedure on the LaunchPad. Some extra explanation is

missing....