Quote:
|
Originally Posted by KenWittlief
measureing timeing on the simulator wont tell you what you want to know, because the SW will be running on your PC, not on the target system (the RC) which is what really matters.
|
I don't know squat about the Simulator, but I think Mr. Lundy may have been saying that the Simulator is "clock speed-aware". It may know, or can be told, what the processor's clock rate is. I guess if the code doesn't use interrupts, that would be enough to determine the number of processor clock cycles between two points in the code.
realExecutionTime = simulatedClockCycles * realClockPeriod
I'll have to have a closer look at the simulator. At this point I feel like I don't have time to go up another learning curve. But I should probably do it anyway...