John,

I always got better result by adding extra LEDs
1. one of pic pin I always used it as power led and thru
   any available timer I turn it on and off (fast enough that
   you can see it) the purpose of this is:
   if the pic crashed for any reason remotely you can tell if the
   pic is alive or dead.
2. if I want to check any subroutine to see if it is getting
   there or not beginning of subroutine I turn it on and of it
   I turn it off.
3. some times in the design there are lcd, sound, rs232 etc
   all you have to do is add more code for your debugging and
   once it is done just disable them.

I always used leds to debug and plus it is fun too

Andre Abelian



-----Original Message-----

I am curious about how people debug their code once they have burned it
into the chip and it does not work correctly.  Would appreciate any
feedback I can get.

I'm not talking about the commercial guys, now, with their
zillion-dollar
systems, but the poor hobbyists (like me) who have a breadboard, a chip,
a
few components, and a simulator.

Simulators are wonderful, but at some point you have gone through the
code,
and it all looks correct; you have run it through the simulator and it
works perfectly, you burn it into the chip, and BAM! it does not work.
:-(

So how do people debug it at that point?  (I have some ideas, but I am
sure
there are a whole raft of things I have not thought of).

John

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body