Anonymous | Login | Signup for a new account | 2021-03-05 19:59 UTC | ![]() |
Main | My View | View Issues | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000013 | Firmware | Task Manager | public | 2008-10-29 17:18 | 2011-06-17 12:10 | ||||||
Reporter | Fred | ||||||||||
Assigned To | |||||||||||
Priority | normal | Severity | minor | Reproducibility | N/A | ||||||
Status | new | Resolution | open | ||||||||
Platform | OS | OS Version | |||||||||
Product Version | |||||||||||
Target Version | Future | Fixed in Version | |||||||||
Summary | 0000013: Non Time Critical Non Preemptive Task Scheduler | ||||||||||
Description | A task scheduler needs to be written for things like idle pwm updates etc. It would be nice if it had some intelligence to it. Features like priority, period, runtime, and a pointer to a function to handle it would all be nice to have. Note, this will not be a pre-emptive scheduler as there are no interrupts to trigger such behaviour and no time for context switching. The master plan is that the fuel calculation code runs first always and the scheduler runs some jobs after that and if that doesn't run it runs even more jobs instead of it. Some discussion has occurred on the forum here : http://www.diyefi.org/forum/viewtopic.php?f=8&t=77 [^] And the wikipedia page on RTOS scheduling is worth a read too : http://en.wikipedia.org/wiki/Real-time_operating_system#Scheduling [^] This task is free for any developer to pick up and run with. We don't need this particularly soon, but it will definitely be a requirement to keep fuel latency low once we pick up more than just a basic feature set. | ||||||||||
Tags | No tags attached. | ||||||||||
FirmwareVersion | |||||||||||
Issue Type | New Feature | ||||||||||
Risk of Breakage | high | ||||||||||
Attached Files | |||||||||||
Copyright © 2000 - 2011 MantisBT Group |