MSP430 Flash Emulation Tool: problems with connection via parallel port

Hello:

Re: MSP430 Flash Emulation Tool (P/N: MSP-FET430P140)
Target: MSP430F1612

We have 1 USB FET (Flash Emulation Tool), which works fine, and 2
LPT FETs, which should work via the parallel port, but aren't.

We're using the latest version (M) of the IAR Quickstart available from
the TI site, however aren't able to use the LPT FETs.

When trying to connect we get "Initializing hardware" and after 4-5
seconds we get:

"Failed to get target information"

We're in Windows.

BTW, our target MCU (MSP430F1612) doesn't show up in the device list, 
but we thought that MSP-FET430P140 is generic enough.

We also tried to access it from mspgcc, similar message.

Any ideas?

Thanks for any pointers.
Marius Hancu

V. strange, but this might be the problem:

MSP430F13x/14x/15x/16x Flash Emulation Tool MSP-FET430P140
http://focus.ti.com/docs/toolsw/folders/print/msp-fet430p140.html

it seems that our target processor:
MSP430F1612
**is NOT** listed under Related Products

which is very strange,  I'd have thought MSP-FET430P140 would cover
it.

Marius Hancu

On Mar 3, 10:34 am, Marius.Ha...@gmail.com wrote:
> V. strange, but this might be the problem:
>
> MSP430F13x/14x/15x/16x Flash Emulation Tool MSP-FET430P140http://focus.ti.com/docs/toolsw/folders/print/msp-fet430p140.html
>
> it seems that our target processor:
> MSP430F1612
> **is NOT** listed under Related Products
>
> which is very strange,  I'd have thought MSP-FET430P140 would cover
> it.

On the other side, on MSP430F1612's page:

http://focus.ti.com/docs/prod/folders/print/msp430f1612.html

The MSP430F13x/14x/15x/16x Flash Emulation Tool	MSP-FET430P140

is listed at Tools and Sofware

So I don't know what to believe.

Marius Hancu

I recently ran into this with the full version of IAR at work.
I made two changes at once, so I'm not sure which actually fixed the 
problem:

1. Open the Device Manager, Select "Ports (COM & LPT), select "Printer 
Port (LPT1)", and double click to view the properties.
Choose the "Port Settings" tab, and verify that  "Enable legacy Plug and 
Play detection" is checked.

2. In Explorer, open folder drive:\Program Files\IAR Systems\Embedded 
Workbench 4.0\430\bin.
See if you have a file named HIL.INF.  If so, open it.  Mine had "278", 
which is the typical port address for LPT2.  I changed it to "378", the 
typical port address for LPT1.

My FET then started working correctly.
NOTE: On my home system, where I have QuickStart, there was no such 
file.

I believe step #1 is the critical one.

--Gene



In article <WAdGh.31555$11.173981@wagner.videotron.net>, 
NOSPAM@videotron.ca says...
> Hello:
> 
> Re: MSP430 Flash Emulation Tool (P/N: MSP-FET430P140)
> Target: MSP430F1612
> 
> We have 1 USB FET (Flash Emulation Tool), which works fine, and 2
> LPT FETs, which should work via the parallel port, but aren't.
> 
> We're using the latest version (M) of the IAR Quickstart available from
> the TI site, however aren't able to use the LPT FETs.
> 
> When trying to connect we get "Initializing hardware" and after 4-5
> seconds we get:
> 
> "Failed to get target information"
> 
> We're in Windows.
> 
> BTW, our target MCU (MSP430F1612) doesn't show up in the device list, 
> but we thought that MSP-FET430P140 is generic enough.
> 
> We also tried to access it from mspgcc, similar message.
> 
> Any ideas?
> 
> Thanks for any pointers.
> Marius Hancu
> 

Hello,

Marius Hancu <NOS...@videotron.ca> wrote:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
> We have 1 USB FET (Flash Emulation Tool), which works fine, and 2
> LPT FETs, which should work via the parallel port, but aren't.

Comment:
=3D=3D=3D=3D=3D=3D=3D
In the ....\430\doc\EW430_UserGuide.pdf....
  Part 6. IAR C-SPY=AE FET debugger
    C-SPY=AE FET-specific debugging
      C-SPY FET communication
        PARALLEL PORT DESIGNATORS
.=2E.are the details on the usage of PP-FET.

The F1612 may be a device with spy-bi-wire, and that needs the USB-
FET.



Marius Hancu <NOS...@videotron.ca> wrote:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
> BTW, our target MCU (MSP430F1612) doesn't show up in the device list,
> but we thought that MSP-FET430P140 is generic enough.

Comment:
=3D=3D=3D=3D=3D=3D=3D
If you have a devie not covered by the latest version 3.42A, then is
TI and
IAR in the process of making the device files. If you have pre-
production
samples of the F1612, then you should get in touch with your TI
contact.
It is TI that hands out the files in that case.




// Best Regards
// Mats Mariedahl
__________________________
IAR Systems Technical Support
www.iar.com, support@iar.se
__________________________
The information contained in this message is confidential and may be
legally privileged.  It is intended solely for the addressee.  Access
to this message by anyone else is unauthorized.  If you are not the
intended recipient, any disclosure, copying or distribution of this
message, or any action or omission taken by you in reliance on it, is
prohibited and may be unlawful.  Please immediately contact the sender
if you have received this message in error.
__________________________

On Mar 4, 11:43 am, Gene S. Berkowitz <first.l...@comcast.net> wrote:

> 2. In Explorer, open folder drive:\Program Files\IAR Systems\Embedded
> Workbench 4.0\430\bin.
> See if you have a file named HIL.INF.  If so, open it.  Mine had "278",
> which is the typical port address for LPT2.  I changed it to "378", the
> typical port address for LPT1.
>
> My FET then started working correctly.
> NOTE: On my home system, where I have QuickStart, there was no such
> file.

We didn't find the file either (using the QuickStart).

Thanks anyway.

Marius Hancu

On Mar 4, 11:43 am, Gene S. Berkowitz <first.l...@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

On Mar 4, 11:43 am, Gene S. Berkowitz <first.l...@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

In article <1173130124.885459.244060@n33g2000cwc.googlegroups.com>, 
Marius.Hancu@gmail.com says...
> On Mar 4, 11:43 am, Gene S. Berkowitz <first.l...@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

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