From: Marius.Hancu on
On Mar 4, 11:43 am, Gene S. Berkowitz <first.l...(a)comcast.net> wrote:

> I recently ran into this with the full version of IAR at work.

Are you talking about the IAR Workbench or what?

Thanks.
Marius Hancu

From: Marius.Hancu on
On Mar 4, 11:43 am, Gene S. Berkowitz <first.l...(a)comcast.net> wrote:

> I recently ran into this with the full version of IAR at work.
> My FET then started working correctly.
> NOTE: On my home system, where I have QuickStart, there was no such
> file.

Didn't you have the same problem on your home system?
If you did, how did you solve it?

What was your target processor? Was it MSP430F1612?

Marius Hancu

From: Gene S. Berkowitz on
In article <1173130124.885459.244060(a)n33g2000cwc.googlegroups.com>,
Marius.Hancu(a)gmail.com says...
> On Mar 4, 11:43 am, Gene S. Berkowitz <first.l...(a)comcast.net> wrote:
>
> > I recently ran into this with the full version of IAR at work.
> > My FET then started working correctly.
> > NOTE: On my home system, where I have QuickStart, there was no such
> > file.
>
> Didn't you have the same problem on your home system?
> If you did, how did you solve it?
>
> What was your target processor? Was it MSP430F1612?
>
> Marius Hancu

At work, I use the purchased, licensed, full version of Embedded
Workbench, 3.4.something.

At home, I use the Kickstart version that came with the TI USB-key
thingy. Since that's SPY-by-wire, the parallel port was not an issue.
The kickstart installation did not have the HIL file, only my work
installation did.

Did you check the PnP setting for the parallel port as I suggested
previously? I think that is the most likely factor.

It almost should not matter which MSP device you use, as long as the FET
is working properly. The toolchain should still be able to read the
device ID, and report an "incorrect device" error, not a communications
failure.

--Gene


From: mmihai on

Using a scope should answer the question about the parallel port or
the software ID problems.
I agree wuth the OP, if the device was not supported the program
should complain about unknown ID, not about not being able getting it.

The JTAG interface (except 2 wire SPY-by-wire) is pretty standard so /
in programming mode/ besides memory size[s] the exact part number
shoudn't really matter[?].

--
mmihai