gnupic: Which programmer for 16F87X?
Subject:
RE: Which programmer for 16F87X?
From:
"SU,MENGJIN (A-Oregon,ex1)" ####@####.####
Date:
12 Sep 2001 15:47:51 -0000
Message-Id: <9F8400020EC5D311AF62009027C3961603226B01@axcs09.cos.agilent.com>
Hi, any body can tell me what picprog2.3 is. It sounds like a
software that drives a PIC programmer (which is made of a few
parts).
Thanks!
- Mengjin Su -
-----Original Message-----
From: Antti T Tuominen ####@####.####
Sent: Wednesday, September 12, 2001 3:54 AM
To: ####@####.####
Subject: Re: Which programmer for 16F87X?
On Tue, 11 Sep 2001 ####@####.#### wrote:
> Can you tell me which programmer would be the best/simplest
> for programming 16F87X under linux?
> I made one (picprog2.3) with 74hct573, it seems working,
> but for two days I can't burn PIC (it reads 0x3fff)
Now there's two of us. Except that I use 16F628 and 74hct241, my problem
is exactly the same. My parallel puts out 3.6V, I get correct voltages "on
the other end of the cable" when I test with picprg. I get 5.17V out
correctly through the HCT, and, IMHO, into correct pins on the PIC.
(There's a RB3/RB4 difference between 628 and 87x, if I remember
correctly) I've noticed that (at least to an unorganized mind like me) it
is next to impossible to really get the circuit correct on breadboard, on
the first try. But then, after double, triple, quadruple checking and the
thing converged into the correct circuit.
Hmm... I take +5V from a HD power connector and I've joined the GND (0V)
and parallel GND together. Is this asking for trouble? I remember testing
that when separated, they had 0V difference between them so I thought it's
OK.
In a week or so, I too get to test the setup on another machine. Lets see
what happens.
--
char*s="O@DDDQ@DD@QM__D_SDDDQQDDDQQLLL",O=1;main(m){for(;*s;(m*=2)>32&&
++O%6?s++, " attuomin(a)cc<.>helsinki<.>fi " ,m=1:2)putchar
(*s&m?"\n" "Antti Tuominen, www.helsinki.fi/~attuomin" [O%6]:32);}
---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####
