• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 22 subscribers
  • Views 919 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

is this why the RTOS 'need' is so prevalent

²erik malund

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

Parents
  • 0 in reply to ²erik malund

    Shades of RTOS. A Co-operative, non-pre-emptive, round robin RTOS as defined by Erik.

    Unless you have very few states, I believe that RTX-Tiny would use less code and run faster than your home built state machines.

    RTX ran on the MIR in less than 600 bytes total program. The program controlled dynamic displays as a slave under control of a fantastic x386. Both display and communications ran under RTX if I remember correctly.

    I did not write the code but someone that you know personally Erik wrote the code.

    Oh! The MIR did fall eventually. May be a bad example, you think?

    Bradford

Reply
  • 0 in reply to ²erik malund

    Shades of RTOS. A Co-operative, non-pre-emptive, round robin RTOS as defined by Erik.

    Unless you have very few states, I believe that RTX-Tiny would use less code and run faster than your home built state machines.

    RTX ran on the MIR in less than 600 bytes total program. The program controlled dynamic displays as a slave under control of a fantastic x386. Both display and communications ran under RTX if I remember correctly.

    I did not write the code but someone that you know personally Erik wrote the code.

    Oh! The MIR did fall eventually. May be a bad example, you think?

    Bradford

Children
No data