RTOS

[GoogleCodeExporter]

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

Original issue reported on code.google.com by uavflightdirector on 3 Aug 2013 at 3:06

[GoogleCodeExporter]

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.

Original comment by robert.dickenson on 4 Aug 2013 at 11:55

[GoogleCodeExporter]

Original comment by uavflightdirector on 16 Sep 2013 at 7:25

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

The FreeRTOS branch now runs MatrixPilot under SILSIM. Work is still required 
with HILSIM testing.

Original comment by robert.dickenson on 3 May 2014 at 10:31