??? 01/20/11 17:32 Read: times |
#180722 - Not The only reason Responding to: ???'s previous message |
With and RTOS you do not have to slicing up large tasks into smaller chunks to avoid stilling the system.
It is still in the same catagory,. How to get the CPU to complete all tasks in the allotted time(s). You also get the rest of the widgets mailboxes and semaphores that help avoid a bunch of unsupervised globals. Have you also noticed that there is a all 8 bit CPUs should be replaced with ARMs The reasons not to use a RTOS are fewer when you are using an 32bit CPU. |
Topic | Author | Date |
it just struck me, is this why RTOS 'need' is so prevalent? | 01/01/70 00:00 | |
Two Camps Here | 01/01/70 00:00 | |
Best Practice | 01/01/70 00:00 | |
a similar discussion... | 01/01/70 00:00 | |
I have always maintained the belief... | 01/01/70 00:00 | |
"non-arbitrary" ? | 01/01/70 00:00 | |
"Real" Processing exposed | 01/01/70 00:00 | |
Too Specific | 01/01/70 00:00 | |
sweeping generalisation | 01/01/70 00:00 | |
RTOS are very useful | 01/01/70 00:00 | |
I think this got away ... | 01/01/70 00:00 | |
Blocking/nonblocking I/O | 01/01/70 00:00 | |
Not The only reason | 01/01/70 00:00 | |
I considered developer effort | 01/01/70 00:00 | |
code generator | 01/01/70 00:00 | |
Another neat feature | 01/01/70 00:00 | |
there is such an attachment ... | 01/01/70 00:00 | |
Lots of tools available | 01/01/70 00:00 | |
not really | 01/01/70 00:00 | |
Lots of C tools | 01/01/70 00:00 | |
widespread | 01/01/70 00:00 | |
Missed the point! | 01/01/70 00:00 | |
Ecosystem | 01/01/70 00:00 |