Forums

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

Started by Marius Hancu March 12, 2007
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
Marius Hancu wrote:

> 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? >
Yes but a long time ago, around two years or so. I loaded an older IAR version which fixed the problem. So instead of the latest one from TI's web site I used the one that came with the CD in the FET430UIF shipment carton. Then it worked. -- Regards, Joerg http://www.analogconsultants.com
> 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
Is IAR KickStart sensitive to the Windows version? The one setup which works is on Windows XP, the one which doesn't is Windows 2000. Marius Hancu
> 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
Is IAR KickStart sensitive to the Windows version? The one setup which works is on Windows XP, the one which doesn't is Windows 2000. Marius Hancu
> 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
Is IAR KickStart sensitive to the Windows version? The one setup which works is on Windows XP, the one which doesn't is Windows 2000. Marius Hancu
Hello,

I need to know if you have SP4 installed on the Win2000 PC.
The EW430 is tested with Win2000 + SP4.

Do you have any problem if using a FET-PP ?

Do you have any problem using another device, for example MSP430F449?

// Best Regards
// Mats Mariedahl
__________________________
IAR Systems Technical Support
www.iar.com, support@iar.se
__________________________

On Mar 13, 3:58 am, mat...@iar.se wrote:

> I need to know if you have SP4 installed on the Win2000 PC. > The EW430 is tested with Win2000 + SP4.
SP4 is installed.
> Do you have any problem if using a FET-PP ?
Not sure, we haven't tested yet, but we'll try.
> Do you have any problem using another device, for example > MSP430F449?
We'll try, see in above. Thank you for your help. Marius Hancu
On Mar 12, 8:53 pm, Marius.Ha...@gmail.com wrote:
> > 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 > > Is IAR KickStart sensitive to the Windows version? The one setup which > works is on Windows XP, the one which doesn't is Windows 2000. > > Marius Hancu
I believe so. The USB driver is XP only. Won't work on my 2000 either.
Hello Mats,

> > I need to know if you have SP4 installed on the Win2000 PC. > The EW430 is tested with Win2000 + SP4. > > Do you have any problem if using a FET-PP ? > > Do you have any problem using another device, for example MSP430F449? >
In my case (about 2 years ago) I used an XP machine. Got the errors every time, when trying to program several MSP430F1232. None of them could be programmed until I loaded the (older) Kickstart version from the CD that came with the USB programmer from TI. No need to investigate, I just mentioned it in case it helps you. By the way I find it is great that an engineer from a manufacturer participates in a newsgroup like this. Way to go! -- Regards, Joerg http://www.analogconsultants.com
On Mar 13, 3:47 pm, Joerg <notthisjoerg...@removethispacbell.net>
wrote:

> In my case (about 2 years ago) I used an XP machine. Got the errors > every time, when trying to program several MSP430F1232. None of them > could be programmed until I loaded the (older) Kickstart version from > the CD that came with the USB programmer from TI.
Well, to open some of the environments (.eww) we had required the new IAR 3.42 Kickstart. The old one (3.21) which came with the MSP- FET430UIF, couldn't do that. So, we installed 3.42. However, with the 3.42 version, we had the "Failed to load debugee" errors described in the above, i.e. couldn't really debug. Then we decided to go back to the old drivers, by uninstalling 3.42 and trying to install 3.21, however the old IAR (3.21) hanged when trying to initialize devices. We would be curious to know what is experience of others re going back to old drivers or IAR versions from the new ones? With the MSP-FET430UIFs we have (2004, but recently bought), we really couldn't do that, backtracking wasn't an option. Not too good, in our view. Marius Hancu