Harold wrote:

>>
>> And I'll bet you always know "exactly" how long all your
>> "critical" routines take to execute too.
>>
.....
>        Yes... Too Long!  Anyone have any sort of histogram program to tell me
>where the processor is spending all its time?
>


Funny, I would have thought this to be fairly obvious to do by looking
at the assembler code [dare I say it - as opposed to looking at C code].

Short of trying to do this using a simulator [and counting cycles
- gakkk!], I have done this sort of thing in the past by setting/clearing
a port pin, and checking timing on a scope. Kinda primitive, but easy to
implement - and easier still [to change] with the new 'F parts. Finally
got hold of an '874 - love it to death.

Good idea for a new product from the s.w. types - PIC Profiler.

best regards,
- danM

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu