Quote:
Originally Posted by Astronouth7303
The current generation of controllers just don't have a prayer of running an RTOS. Period. No easy multi-threading, inefficient indirect referencing, and a collection of other architecture issues make it pretty much impossible.
|
We aren't discussing the current controller.
Quote:
Originally Posted by Astronouth7303
One of the issues of using any RTOS is the complexity of developing code for a new device. While I have no experience with any RTOS, I know that if you miscode a kernel module (or w/e the term is for the RTOS of your choice), the debugging could be a real hassle.
|
No one is expecting teams to code at the kernel level.
Quote:
Originally Posted by Astronouth7303
Even if you don't write code at a kernel level, you can still have issues with threading that just don't appear in current code.
|
Who said teams will be forced to write multi-threaded apps, or even know what a thread is?
Quote:
Originally Posted by Astronouth7303
At this time, FIRST robots do not (generally) meet complexity requirements to justify an RTOS.
|
*sigh* I could write volumes about this one sentence, but I have other things to do...
-Kevin