Still, you can't beat developing on a 12C671 (as in, OTP) for
entertainment.  Not only can't you debug it, but you have to unsolder it an=
d
throw it away after each cycle.  I did that once. (ONCE).

I think that what I got out of that adventure was much like what Steve Smit=
h
said above.  Work out all the hardware mysteries on a more capable chip,
like the 877, and then port back to the little guy.  This may not eliminate
differences between the chips, but I haven't found many of those.  Most
problems are due to...the way Microchip designs
peripherals...misinterpreting the data sheet...misunderstanding compiler
behavior...making assumptions about "obvious" things that turn out to be
wrong...and, (I have to say it), debug code with bugs in it :)

Like you, I use the simulator to debug pure code, but I like to see it run
on hardware when I'm testing hardware.  I suspect it's how I think, and
there are probably quite a few of us in that group.

Barry

If I were as smart as some of the people here, having read and completely
understood everything, I wouldn't bother testing my code.  And I'd never
need to ask a question.
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.