 | | Re: Interesting BrickOS Timing Results
|
| (...) 250msec? Not blocked entirely, but delayed. That's what I meant by "stutter". I've measured the general interrupt handler to take anywhere from 70-150us. So, the higher the sample rate the more significant the disruption. Anything faster than (...) (21 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
| | | | | Re: Interesting BrickOS Timing Results
|
| (...) I forgot to mention... This is *almost* the same as moving some of the subsystem code into a seperate high priority task. For example, LCD refresh code is executed in the 1ms timer ISR. It really doesn't need to be in the ISR. It can do it's (...) (21 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
| |
