Where does the Wait_api call to? I've been looking through the files, and can't seem to find the function anywhere. I just wanted to have a look at how it's been set up, what registers it pokes.
The wait functions (wait, wait_ms, wait_us) all just read TIMER3, which is constantly running at a 1us tick. So they read the time on entry, and wait for the time to elapse. That's about it!
Simon
Hi Christian,
The wait functions (wait, wait_ms, wait_us) all just read TIMER3, which is constantly running at a 1us tick. So they read the time on entry, and wait for the time to elapse. That's about it!
Simon
Hmm, if the CLK is running fast enough for the Timer, then it should (theoretically), be possible. I don't know where the CLK comes from, but at 1uS per CLK, it should be 1 MHz.
The TIMER3 is setup as a fixed 1us tick so it can be relied upon, so you can't change the range. However, if you are willing to poke one of the other LPC1768 timers yourself (TIMER0-2), they are fairly flexible and have a prescaler, so you should be able to setup the sort of speeds you need.
Simon
Hi Evaristo,
The TIMER3 is setup as a fixed 1us tick so it can be relied upon, so you can't change the range. However, if you are willing to poke one of the other LPC1768 timers yourself (TIMER0-2), they are fairly flexible and have a prescaler, so you should be able to setup the sort of speeds you need.
Simon
Important Information for this Arm website
This site uses cookies to store information on your computer.
By continuing to use our site, you consent to our cookies.
If you are not happy with the use of these cookies, please review our
Cookie Policy
to learn how they can be disabled.
By disabling cookies, some features of the site will not work.
Access Warning
You do not have the correct permissions to perform this operation.
Hi folks
Where does the Wait_api call to?
I've been looking through the files, and can't seem to find the function anywhere.
I just wanted to have a look at how it's been set up, what registers it pokes.
Lerche