MSP-FET430UIF, IAR Kickstart: "Failed to initialize device"

In article <30YOh.1656$H_5.23@newssvr23.news.prodigy.net>, Joerg 
<notthisjoergsch@removethispacbell.net> writes
>Gunther Mannigel wrote:
>
>> Marius.Hancu@gmail.com schrieb:
>>
>>> On Mar 14, 11:46 am, Joerg <notthisjoerg...@removethispacbell.net>
>>> wrote:
>>>
>>>>> However, with the 3.42 version, we had the "Failed to load debugee"
>>>>> errors described in the above, i.e. couldn't really debug.
>>>
>>>
>>> Fixed after sending all our FETs (both USB and LPT) to TI support for
>>   LPT? How do they program a 'HC244?
>>
>
>In America that's done with a Smith&Wesson :-)

Apparently a British owned company...

It is fascinating to see who actually owns what. Often you find a 
company that is part of the history and heritage is owned by some one 
foreign.  It is the same in the UK .   The Business world is global with 
little soul.

The Ironic thing about Smith and Wesson being owned by a British company 
is of course that it is illegal to own any of their products in the UK 
:-(


-- 
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills  Staffs  England     /\/\/\/\/
/\/\/ chris@phaedsys.org      www.phaedsys.org \/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

>I am having the same failure to start problem.
>
>The devices worked fine last summer on this computer but now Windows
>reports "Cannot start this hardware" Code 10 and I get the yellow
>exclamation mark by the driver.

Thanks to those that offered suggestions.

The problem turned out to be a conflict with another driver that had been
installed months ago and wasn't being used any more, but it prevented the
TI driver from functioning apparently.

In my case it was the N8VB vCOM Virtual Serial Ports
Driver, which makes sense once the problem has been resolved. It never
bothered other serial devices, but I guess XP doesn't like 2 multiport
drivers at the same time. Disabled the N8VB driver and XP's wizard popped
up to re-install the MSP-430UIF that was failing to start.

Anyway, for those who google here in the future, don't give up hope. Look
for the driver conflicts, try the older and newer versions, and eventually
it will work on XP and W2K.

Peter

On Mar 29, 6:05 pm, "PeterJ" <pjenni...@gmail.com> wrote:
> I am having the same failure to start problem.

We were able to solve the problem only after the FET devices were sent
to TI in Texas and reprogrammed.

I strongly suggest contacting them.

It seems that there are many generations of devices out there. In our
case, we bought it recently, but it was still dated 2004.

Marius Hancu

On Apr 20, 6:33 pm, Marius.Ha...@gmail.com wrote:
> On Mar 29, 6:05 pm, "PeterJ" <pjenni...@gmail.com> wrote:
>
> > I am having the same failure to start problem.
>
> We were able to solve the problem only after the FET devices were sent
> to TI in Texas and reprogrammed.
>
> I strongly suggest contacting them.
>
> It seems that there are many generations of devices out there. In our
> case, we bought it recently, but it was still dated 2004.
>
> Marius Hancu

No nothing like that. Its a pure and simple Driver conflict and a very
common one for the TI USB device. Uninstall some other virtual serial
or USB drivers and look for driver conflict. It will be resolved

I ran into the same problem on a the same IAR version running on Vista.  It
turned out to be pretty simple.  The USB dongle - when plugged in creates a
vertual COM port (COM17: in my case).  Another program (Palm HotSynch) was
opening that port every time I rebooted - thinking it was a bluetooth
virtual COM port.  Once I corrected the other progra, all was well.

To help, after plugging in the USB device, open the project options in IAR
and look in the "FET Debugger" settings under "Debugger".  The Connection
field should say "Texas Instruments USB-IF". To the right of that is a
Field that says "Automatic".  Click on the "..." button to the right, and
it should list a COM port as well as "Automatic".  In my case with the USB
device plugged in,  It showed "COM17 (Aready in use)" - that's how I new
that something else hijacked it.  If it doesn't list a virtual com port,
you may have a driver issue.

Cheers,
Steve


>Hello:
>
>We have two MSP430 development setups using:
>
>- the IAR Kickstart 3.42 for TI MSP430
>- the USB Debugging Interface MSP-FET430UIF
>- the target: MSP430F1612
>
>One of them works fine, we're able to compile and debug.
>
>One the other, we can compile but we can't debug/execute. We're getting 
>these messages:
>
>Failed to initialize device
>Failed to load debugee
>
>What could it be?
>
>Permissions in installing the IAR Kickstart? Are they critical?
>
>Has any of you seen similar stuff?
>
>Thanks.
>Marius Hancu
>