On 12/27/06, Herbert Graf wrote: > On Wed, 2006-12-27 at 10:05 +0100, Wouter van Ooijen wrote: > > jtag won't help much if your problem is timing-dependant. (printf > > will also interfere, but it is more 'under your control'). > > Very true, which is something I mentioned. That said, timing dependent > problems don't give many options for debugging. About the only one I can > think of that guaranteed not to interfere would be live stack trace > emulation. I don't have the equipment for that. Fortunately I haven't > encountered many of those types of bugs. It seems to me that most of you guys are writing bigger and more complicated firmwares (but maybe not that Time Critical). Most of my previous projects are rather simple (never exceeded 2kB with 16C72A/16F872/12F675) but rather time critical. With the first two, ICE2000 proved to be an invaluable tool. With 12F675 project, I did not have the processor module for ICE2000 so I used ICD2 a bit but it is too troublesome. So I mainly used a debug LED (pulse at different rate) -- kind of rudimentary printf. None of the project can have the luxury of serial debugging with printf. For the 12F675, I am actually counting every instruction because of the response time requirement. I still believe JTAG/ICD is essential and ICE is the best tool if it is available. Of course, a good/expensive oscilloscope with deep memory/zoom function is essential. But I must say I am not experienced when it comes to firmware (I am more a hardware guy) so I am still learning. Regards, Xiaofan -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist