IAR Debugger Communication Error

Started by Robert October 12, 2006
I have the following setup and get random communication errors with
the IAR toolset with the TI USB debugger. IAR told me it's not their
problem as the debugger is not their driver even though I purchased
both the toolkit and debugger from them. Yep, another case of great
support, NOT!

IAR 3.41a
Softbaugh ESG439 demo board
TI Debugger MSPFET 430 UIF
Win2K
Direct USB connection - no hub.
The debugger at random times develops a communication error. The
error occurs with two different Softbaugh demo boards (ESG439,
ES169). Rebooting the PC does not always solve the issue. Sometimes
but not always I can get the debugger to work is by blowing away all
the debug drivers, reinstall the drivers, and then re-boot. I don't
have any other USB devices connected, just the debugger.

The following message appears at random times either during initial
debug loading or during debug runtime.
Error Message:

Emulator
Communication error.

Please connect to device and press retry to reconnect or press
cancel to abort.

Thanks for any suggestions!

Beginning Microcontrollers with the MSP430

I have two eZ430-F2013 thumbs. If I keep using the same one (either
one of the two) from session to session, IAR FET Debug always works.
But if I switch from one to the other, I occasionally got the same
error as you did. Just like Windows itself, it is beyond reasoning.

--- In m..., "Robert" wrote:
>
> I have the following setup and get random communication errors with
> the IAR toolset with the TI USB debugger. IAR told me it's not
their
> problem as the debugger is not their driver even though I purchased
> both the toolkit and debugger from them. Yep, another case of
great
> support, NOT!
>
> IAR 3.41a
> Softbaugh ESG439 demo board
> TI Debugger MSPFET 430 UIF
> Win2K
> Direct USB connection - no hub.
> The debugger at random times develops a communication error. The
> error occurs with two different Softbaugh demo boards (ESG439,
> ES169). Rebooting the PC does not always solve the issue.
Sometimes
> but not always I can get the debugger to work is by blowing away
all
> the debug drivers, reinstall the drivers, and then re-boot. I don't
> have any other USB devices connected, just the debugger.
>
> The following message appears at random times either during initial
> debug loading or during debug runtime.
> Error Message:
>
> Emulator
> Communication error.
>
> Please connect to device and press retry to reconnect or press
> cancel to abort.
>
> Thanks for any suggestions!
>
--- In m..., "old_cow_yellow"
wrote:
>
> I have two eZ430-F2013 thumbs. If I keep using the same one (either
> one of the two) from session to session, IAR FET Debug always works.
> But if I switch from one to the other, I occasionally got the same
> error as you did. Just like Windows itself, it is beyond reasoning.
>

So what's the deal does everyone just except the fact that the
development software / tools are junk and live with it? The tools are
junk if they do not work as one would expect them to do in normal
conditions. Having a debugger not even being recognized after a clean
boot is totally unacceptable especially after paying big dollars for
it.

Thanks for you reponse.