 | | sys_timer —Samuel Winchenbach
|
| | | I recently adopted legOS as my development environment and I have to say I tremendously impressed. Thanks to everyone who has worked so hard on it. It is really a first class, grade A product. Is sys_timer accurate to within 1 ms? unsigned long (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: sys_timer —Michael Ash
|
| | | | | (...) Yes. It is updated from an interrupt routine that fires every 1 ms (IIRC). However.... (...) wait_event is only accurate to 20ms or so, depending on what your other tasks do. So your timing is very accurate, but you're not timing what you (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| | | | | |
| | | | | Re: sys_timer —Michael Obenland
|
| | | | (...) Yes. (...) That is right. (...) It does, actually. The timer itself counts the millisec. But if you do a wait_event() call, your running program gives up its time slice, the OS waits for the event and then continues your task with the next (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Accurate msleep and timeslicing - was Re: sys_timer —Joseph Woolley
|
| | | | "Michael Obenland" <obenland@t-online.de> wrote in message news:GvJ5vD.7MC@lugnet.com... <snip> (...) switch. (...) I made some modifications to the tm_sleep_wakeup that allows high priority tasks to wake up at exactly the time specified for msleep (...) (23 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| | | | |
