godzich
11-10-2010, 11:46 AM
Pardon me if this has been discussed before (in that case - please someone redirect me into the right thread)...
For very precise fine tuned timing I cannot find enough info in the Prop data sheet. Assume a prop running at the standard 5MHz x 16 = 80 MHz internal clock. One instruction executes in 4 clocks = 50ns.
Consider the following PASM code:
WAITPEQ state, mask
MOV temp, ina
Execution continues immediately when the WAIPEQ condition is met. What I want to know is:
What is the delay time from when the condition is met (pins change) - to the sampling of the input pins in the next instruction? Is it 12.5ns, 25ns, 37.5ns, 50ns or more?
And is this delay constant? In other words: Is the waitpeq instruction sitting and waiting for the execution to continue based on 50ns or a smaller 12.5ns granularity? And when the execution continues, at which micro-state (50ns/4=12.5ns) is the actual sample taken to be written into temp?
Appreciate any input here, but prefer hard facts. Is this such information Parallax is sitting on?
Cheers,
Christian
For very precise fine tuned timing I cannot find enough info in the Prop data sheet. Assume a prop running at the standard 5MHz x 16 = 80 MHz internal clock. One instruction executes in 4 clocks = 50ns.
Consider the following PASM code:
WAITPEQ state, mask
MOV temp, ina
Execution continues immediately when the WAIPEQ condition is met. What I want to know is:
What is the delay time from when the condition is met (pins change) - to the sampling of the input pins in the next instruction? Is it 12.5ns, 25ns, 37.5ns, 50ns or more?
And is this delay constant? In other words: Is the waitpeq instruction sitting and waiting for the execution to continue based on 50ns or a smaller 12.5ns granularity? And when the execution continues, at which micro-state (50ns/4=12.5ns) is the actual sample taken to be written into temp?
Appreciate any input here, but prefer hard facts. Is this such information Parallax is sitting on?
Cheers,
Christian