> I have a problem on my project that when I debug my
> code it is absolutely
> perfect, however, in the real world it seems that
> there are just much more
> things that I did not take into account. My problem
> is that as far as I know
> there is no way to track down what's going on even
> using a hardware debug
> station -- but I may wrong. So that the PIC needs to
> be run in the real
> clock speed while I would need to watch the input
> and output signals as a
> logic analyzer and see the code flow so that I can
> have a chance to detect
> why my code enters to the bad state.

What sort of I/O is giving you these problems?

I know that when I was debugging some I/O events I put specific breakpoint
labels in so I could step up to the breakpoint before the I/O happened, run
the code that handled the event and detected when it finished, and then had
another breakpoint immediately after that. This way the I/O went at normal
speed, but I could examine the states before and after.

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist