On Tue, Mar 18, 2003 at 02:14:10AM -0500, Konstantin Klitenik wrote:
> I think the problem is that FPP doesn't even recognize anything on Parallel
> port.  I checked everything again.  I made the cable less then 2 feet.

Good. That eliminates one variable.

>  The
> way the error comes up, it doesn't even try to program.  As soon as I press
> program it says "Failed to program code!"

This isn't a really useful error message unfortunately. About 12 different
items have to be perfect for the programmer to work.

>  All the settings are fine.

Are you sure? Have you actually used the test mode to wiggle each line and
verify that it's the correct pin on the programming socket. Any of a misconfig,
miswire, or wrong polarity on any of the programming lines will cause the
programmer to fail.

Trust me, it's worth taking the 30 minutes required to test each line from
config to socket. You won't be sorry.

> I set
> the pic to 16f84 which is what I have and chose parpic as the hardware.

That isn't sufficient for initial testing. You still need to verify that
each line is configured and wired properly. This can only be done by actual
testing in test mode.

This failure mode in FPP is one reason why I put chip autodetect in my latest
version of picprg. If it doesn't autodetect, then you don't even bother to
try to program.

Verify everything. I can almost promise you that you have a misconfig or
miswire somewhere in your setup.

BAJ

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads