I do not want to learn RTOS? Learn RTOS What are the benefits? Shall I run my project RTOS?
?????? questions about RTOS and so on, in fact, the final analysis is not enough for you to know RTOS, lack of experience in project development, etc. also.
For this part of the friends, share a few related content today:
embedded systems, there are many ways to achieve the task scheduling. Small systems with limited functionality, an infinite loop is sufficient for system functions. When the software design becomes large and complex, the designer should consider the use of real-time operating system.
Here to share the use of RTOS eight reasons:
1. Hard real-time response
Priority-based preemptive RTOS, based on real-time demand task execution priority scheduling. There are strict timing constraints of task execution priority, improve application response to time-critical events.
2. The maximum system performance
For large, complex embedded applications, using an event-driven RTOS, instead of poll-based super-cycle structure, it may generate a more efficient design, smaller memory footprint, applications get more processor time .
3. Reduce complexity
RTOS allows applications to be divided into small autonomous operation of a task. Their task execution context, or other tasks not dependent scheduler.
4. Peak load management
RTOS provides provides an effective method for managing system peak activity. Higher priority assigned to perform tasks peak load activities to ensure that they are accessible to the processor within a critical time, during this period, lower priority task is delayed.
The tight integration middleware
RTOS modular design makes it possible to easily add middleware. Middleware components and increase task-driven manner. They use communication resources and other tasks RTOS provides. The RTOS scheduling based on the corresponding event.
6. bigger development team
Each task can be considered a project. Resources (queues, semaphores, etc.) provided by the RTOS to define the input and output. The system is defined as one task can more easily deploy more developers to a project.
7. easy to debug and verification
The system is divided into functional clear mandate, it does not depend on other tasks. Before the entire system integration, you can easily debug and verify each task.
8. code reuse
RTOS系统中的模块化设计，鼓励将软件功能创建为独立的、验证过的任务。其独立性使得在其它设计中重用这些模块变得很简单。
当然，以上理由针对的大众需求，如你项目有特殊需求另当别论。
================================================================================================
之前，我就是收到一个项目中，就不要我使用rtos，但是发现其实这个是可以使用rtos来完成的。
其实有的项目可以用两种方式分别实现，但是rtos有任务切换，可能会带来不确定因素，但是我个人认为，rtos只要会用，一般是没有问题的，因为主流的rtos基本上已经比较稳定的。
裸机系统将是不用考虑任务切换，全局变量随便用，不存在可重入等问题，一个while大循环+定时器就基本解决了。但是函数之间耦合强，阅读性就不那么强。