Hi all,
A couple of people have reported that rproxy works with some of their
machines and not others. They suspect it is a problem with fast
machines, due to the timing of the signals produced by rproxy. I suspect
it is a hardware issue related to the FET tool.
If you look in the user's guide that comes on CD-ROM with the FET tool,
there is a note about a modification which should be performed. I think
the latest FET tools should be shipped with this modification already
implemented. However, a large proportion of the FET tools shipped to
date need to be modified by the user. The modification improves the FET
tool's noise tolerance. Without it most slow machines never give an
error, but fast machines don't even reach the point where the host can
detect the device attached to the FET tool.
Even if the IAR or Quadravox tools work and rproxy doesn't, don't assume
this means rproxy is at fault [of course it could be - just don't assume
it :-)]. I suspect rproxy drives the interface a bit faster than at
least the older versions of the IAR software. This may just push things
over the edge. I use a 1.8GHz P4M notebook when testing the Windows
software, and have no trouble.
If you have a Thinkpad you should also note a modification required to
the FET tool when used with those. Most models of Thinkpad need a
resistor change to compensate for their unusually low drive on the
parallel port. The MSP430 FAQ on the TI web site gives details of this.
Regards,
Steve
- [Mspgcc-users] FET tool problems Steve Underwood
-
