On Tue, Mar 18, 2003 at 10:52:01AM -0500, Konstantin Klitenik wrote:
> I've used define/test and all the pins are configured correctly.  I have
> also tried to use picprg and it doesn't detect the programmer.  I've been
> trying to figure out what's wrong for hours and I'm getting frustrated.  I
> tried building a QandD and there isn't much you can get wrong there, but it
> still doesn't work.

OK. Here's the next phase. You need a voltmeter for it.

Redo your define/text mode. But this time record the actual low and high
voltages for each pin on the socket.

Here's the theory (sight unseen): Your parallel port outputs a 3.3V high
signal. High enough for TTL printers, not high enough for programming PICs.

Further details about the situation on the TLVP page:

http://www.finitesite.com/d3jsys

BAJ
>
>
>
> >From: Byron A Jeff <byron@CC.GATECH.EDU>
> >Reply-To: pic microcontroller discussion list <PICLIST@MITVMA.MIT.EDU>
> >To: PICLIST@MITVMA.MIT.EDU
> >Subject: Re: [PIC]: PARPIC AND TAIT's FPP programmer
> >Date: Tue, 18 Mar 2003 10:25:43 -0500
> >
> >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
>
>
> _________________________________________________________________
> Tired of spam? Get advanced junk mail protection with MSN 8.
> http://join.msn.com/?page=features/junkmail
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

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