I just realized that when wait I/O is all over the place using a RTOS is a feasible workaround. Even the 'C' library is wait I/O ARGH. Is it the average coders inability to make no_wait_I/O that is the reason that so many state "I need a RTOS" ?
Erik
Cross-posted at 8052.com
You are going to apps get so simple and RTOS with one task is silly. To so many tasks you should have used and RTOS.
In the middle Your state machine becomes straight code easy to write and easy to read. And easy to add more tasks to.
For many apps it is a preference like ASM vs C. The one you are most familiar with is quicker.
Personally I have never need a RTOS with an 8 bit CPU, but that is just me.
I just re-read my last post.
RTX ran on the MIR in less than 600 bytes total program.
That's plainly false. Not intentional, just dumb on my part. I meant to say the RTOS and communications ran in less than 600 bytes. The actual display code in several threads was a bit larger. Sorry about my mistake. Bradford