??? 01/04/08 14:40 Read: times |
#149040 - Sure Responding to: ???'s previous message |
Russ Cooper said:
You could think of it that way. It all boils down to exactly what points in the code you want to define as the official "start" and "end" of the delay. Sure - but the OP seems to be new to this, so I wanted to be sure that he understands precisely what's going on. Undoubtedly, the OP is trying to create a delay routin for the bit timing in a bit-banged 1-Wire driver - see: http://www.8052.com/forum/read.phtml?id=149001 In that case, what he needs is the overall delay from the start of the call to the end of the return; eg, <pre> // generate a 123us low pulse set pin low; delay 123us; set pin high; <pre> |
Topic | Author | Date |
Number of CPU cycle for 8051 function call | 01/01/70 00:00 | |
Do it in assembler | 01/01/70 00:00 | |
Delay functions | 01/01/70 00:00 | |
A related trick | 01/01/70 00:00 | |
Offset | 01/01/70 00:00 | |
Offset | 01/01/70 00:00 | |
Sure | 01/01/70 00:00 | |
Over Drive? | 01/01/70 00:00 | |
a refinement | 01/01/70 00:00 | |
NOPs are so bad waste of space... | 01/01/70 00:00 | |
waste of space... waste of time | 01/01/70 00:00 | |
fixed delay | 01/01/70 00:00 | |
Variable delay | 01/01/70 00:00 | |
determinism of the cache | 01/01/70 00:00 | |
there are no cache misses in 'linear code' | 01/01/70 00:00 | |
I got only ONE cache miss... | 01/01/70 00:00 | |
Old Keil Thread | 01/01/70 00:00 | |
What about a Delay like this. | 01/01/70 00:00 | |
No, it won't. | 01/01/70 00:00 | |
Ok. | 01/01/70 00:00 | |
also | 01/01/70 00:00 | |
Also ... | 01/01/70 00:00 | |
Actually... | 01/01/70 00:00 | |
will. | 01/01/70 00:00 | |
ANSI C | 01/01/70 00:00 | |
Keil option: Disable ANSI casts | 01/01/70 00:00 | |
typo. | 01/01/70 00:00 |