Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Basically, the purpose of the RTOS is organisation of multitask operation of your software, and providing determenistic reaction to external events. This means that you always can say that if some event occured, then proper action will run in no more than certain time interval.
RTOS provide such mechanisms as preemptive or/and cooperative task switching, task priorities, semaphores, messages and so on.
RTOS saves the developer's time, freeing him from implementation of schedulers and making program structure more clear.
I'd recommend you to use RTOS if your projects has many separate tasks which have to run with different time intervals or event-driven actions. Otherwise, use of RTOS could make your software more difficult.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
