RTOS
Brought to you by:
inspirati
Originally created by: uavflightdirector
Change to an RTOS to provide better data control and better task handling.
This will be of greater benefit as a wider variety of sensors is added.
What still needs to be decided?
What we want from an RTOS
What our critical specifications are
What still needs to be done?
Lots
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: robert.dickenson (code.google.com)
there is a branch with FreeRTOS implemented. the RTOS currently does nothing other than run a demonstration task. in order to go the RTOS route a number of rather significant restructurings of the code is required. these could easily be done incrementally (aka, the low priority interrupt can be a task, navigation can be a task etc). however in order to do this some serious analysis of stack allocation and use will need to be done.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: uavflightdirector
(No comment was entered for this change.)
Labels: -Priority-Medium Priority-Low
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: robert.dickenson (code.google.com)
The FreeRTOS branch now runs MatrixPilot under SILSIM. Work is still required with HILSIM testing.