'what to know before programming 12c671/JW'
<x-flowed>Is there anything important to know before I program a pic12c671/JW? I am
using it where a 16f84 is too large physically to fit, and because it works
with my picbasic compiler. I don't want to screw it up.
One example of one thing I didn't know to do was to record the osccal value
of my pic12c508/JW before I programmed it. Is there anything like this that
can go wrong when I program a pic12c671? Or can it be programmed and erased
like a 16f84 (only using uv, of course).
Get Your Private, Free Email at http://www.hotmail.com
Mister Happy <MITVMA.MIT.EDU> wrote: PICLIST
> Is there anything important to know before I program a
> pic12c671/JW? .... I don't want to screw it up.
> one thing I didn't know to do was to record the osccal value of my
> pic12c508/JW before I programmed it. Is there anything like this
> that can go wrong when I program a pic12c671?
Just as with the 12C508, you should record the 12C671's "osccal"
value before you erase it. If you don't, though, you won't
really "screw it up"; at worst, the thing's internal oscillator
will be a little off. If you're using an external crystal or RC
or whatever, it makes no difference.
=== Andrew Warren - ix.netcom.comfastfwd
=== Fast Forward Engineering - Vista, California
Can't remember if it's a problem with that one, but avoid programming
the code protect bits in the configuration word ... it appears hard to
erase them. ;-)
I once programmed a 12C509 OTP by accident using the 16F84 algorithm.
The result was apparent code protection.
James Cameron us.netrek.org quozlhttp://quozl.us.netrek.org/
At 01:48 27/12/99 GMT, you wrote:
Don't code protect it! You cannot erase the code protection bits.
MPLAB compatible PIC programmers.
More... (looser matching)
- Last day of these posts
- In 1999
, 2000 only
- New search...