is this why the RTOS 'need' is so prevalent

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
  • I wouldn't call it a workaround but yes, partitioning your code around I/O tasks is a reasonably efficient way to organize your code. If all your I/O is non-blocking you'll have write big chunks of RTOS-like functionality to manage properly sequenced completion of all that pending I/O. Doing it once for one project you may be able to do better but from project 2..n you might be better off with a RTOS.

    Of course there are reasons other than I/O to use or not to use an RTOS as well.

    Andrew

Reply
  • I wouldn't call it a workaround but yes, partitioning your code around I/O tasks is a reasonably efficient way to organize your code. If all your I/O is non-blocking you'll have write big chunks of RTOS-like functionality to manage properly sequenced completion of all that pending I/O. Doing it once for one project you may be able to do better but from project 2..n you might be better off with a RTOS.

    Of course there are reasons other than I/O to use or not to use an RTOS as well.

    Andrew

Children
More questions in this forum