Cannot start MSP430 debugging session

You could install KickStart and try your luck there. You may not want to use KickStart, but it does not hurt to try if that works.

Installed IAR KickStart and opened the flashing LED example.  This compiles OK but when I try Project->Download and Debug I get the following error:

Fatal error: Failed to initialize.
Check if hardware is connected.
Check if drivers are installed.
Try to restart the computer.
Tools using the parallel port are not supported on Windows Vista
Session aborted!

I have restarted the computer and I still get the same message.

Regards,
Mark

In that case, read: http://processors.wiki.ti.com/index.php/MSP430.dll_v3

Both CCS and IAR automatically install supposedly the same set of released dll's automatically. The above wiki offers Beta 2 of these dll's.

Thanks for the information.  I have run the installer and still no luck.  I have follwed the install instructions and those in the step MSP430.DLLv3 in IDEs and UIF Interface Up-/Downgrade Process.  This last step generates an error telling me that there is an error:

Could not find MSP-FET430UIF on specified COM port

When I run IAR I get the same error as above.  When I run CCS I get the following error:

Error initializing emulator:
Could not find MSP-FET430UIF on specified COM port

This looks like a reworded version of the original error.

Regards,
Mark

I have been wrestling with this problem for over 2 months.

Here is my scenario and experiences.

Hardware:  ez430-RF2500 kit.

Software:   IDE :  CCS V4.2.4.00033  on a Win XP SP3 machine.

So far, I have found no definitive solution, but I do always eventually  manage to get my ez430 board recognized 

without the above errors. What 'usually' seems to work for me are the following steps :

1. Close CCS and any terminal app I may have been using to view COM port output (usually Hyperterminal)

2. Uninstall the MSP430 Application UART (COMx) in device manager.

3. Run the app MSP430_DLLv3_CCS_Setup.exe, which I believe simply places the new MSP430.dll

    where it needs to go. Allow default folder settings.

4. When finished, I then proceed to insert the ez430 USB stick into my USB port.  Also, I am using a powered

    USB 4 port hub in case there are power issues, (which should not be the case).

    I usually do not get recognition on the first try, and I can immediately determine success/failure by my 

            hub's port activity green LED indicator. If the LED comes on and stays on, I'm in luck. If not,

    I keep re-inserting. Success can happen on the 4th or 5th try, but sometimes taking many more tries.

   Once, I walked away for a few hours, came back, re-inserted, and got recognition the first time.

So far, I have not been able to predict when the problem will recur, and what it specifically takes to resolve it.

TI people:

Is this problem isolated to the ez430 USB interface board ?

Do other MSP430 programmers have similar issues ?

I've been following many old and recent threads on this and it has been plaguing many a

developer for an unacceptable length of time. Is TI working on a solid fix ?

Thanks,

Joe Pepe

Joe,

Thanks for taking the time to reply.  I have followed your suggestions and so far I am having no luck  I still get the same problem as discussed.

I'm with you in that this is infuriating.

Regards,
Mark

I am in the same boat as you Mark, this is indeed infuriating. I find it curious that the ez430 demo program runs flawlessly (im using the RF256x) and information is sent between the boards wirelessly and the incoming data is understood by the PC application. However connecting with ANY program (fet-pro430, IAR,CCS) bounces back an error that the fet devices cannot be found on the specified COM port. 

I've tried everything from different drivers to uninstalling all USB drivers on the system and starting from scratch, I even did a fresh install of Win7 to wipe out any programs I forgot about that might be causing a conflict. No progress. I've been doing this for about 3 weeks now and I'm at my wit's end. 

Some other users suggested looking for any cell phone syncing software or certain mouse drivers may cause a conflict, neither of which are a problem I have. I'm going to go out on a limb and say that its the drivers supplied by TI causing the error because this is the ONLY usb device I have ever owned that causes this much of a problem.