John Nall wrote:

> 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.
> :-(

which simulator do you use?

> 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).

- use a better simulator ;-)
- checking code in blocks
- dump variables to the serial port
- blink some LEDs
- FM receiver to see if oscillator is running
- use a good compiler
- ask in newsgroups


Stef Mientki

>
>
> 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