I'm tonight, yet again, troubleshooting some weird bizzare, probably=20
critical timing-related bug.

The frustration?

The code works perfectly, reliably, 100% of the time when ran with the=20
PicKit2 in debugging mode.

And doesn't work reliably at all in 'normal' mode...  (@#*.  And I=20
should clarify, this is with no tracing or breakpoints enabled... just=20
enable the debugger, then click on 'run'....  starts and runs just=20
fine... or hangs.

I'm a bit tired of dealing with 'debugging tool artifacts', either=20
positive or negative.   At some point in the past, I figured I'd just=20
buy the right tool for the job, but then was dissuaded by the=20
description of the REAL-ICE hardware -  I think the problem back then=20
was the apparently slightly different 'memory map' with the debugger=20
enabled....

Is there any meaningful difference between say a REAL-ICE and a PicKit2=20
(especially if the programming pins are dedicated)?  Reading the=20
documentation just sort of leads me to the same conclusion - not really=20
any difference other than speed for certain things, and a few additional=20
features...  Am I missing something?

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