Timeline for Benefits of RTOS vs Bare Metal for MCU Programming?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 17, 2015 at 19:38 | history | tweeted | twitter.com/#!/StackProgrammer/status/600022600996233216 | ||
| May 11, 2015 at 8:21 | vote | accept | smeeb | ||
| May 9, 2015 at 3:04 | answer | added | Atsby | timeline score: 7 | |
| May 8, 2015 at 20:40 | answer | added | Karl Bielefeldt | timeline score: 12 | |
| May 8, 2015 at 19:18 | comment | added | smeeb | Thank you @whatsisname (+1) - that is sound advice and I will likely take you up on it. I don't think its a faux pas however, to still be interested in what the RTOSes offer, even if I'm months/years out from needing them. I guess I'd like to see the whole picture up front, at the 30,000 ft view. Thanks again! | |
| May 8, 2015 at 19:13 | comment | added | whatsisname | If it's not even clear to you what an RTOS offers, then why are you interested in writing applications for them? Whether an RTOS will benefit you or not depends entirely on what you are trying to accomplish. With that said, you must learn to walk before you can run. Program for the bare metal, and as you run into problems and solve them, you will truly learn what the benefits and drawbacks are. | |
| May 8, 2015 at 19:07 | history | edited | smeeb | CC BY-SA 3.0 |
edited body
|
| May 8, 2015 at 19:00 | history | asked | smeeb | CC BY-SA 3.0 |