Section three free articles on the ESP 32. In this section, we will learn the following topics, what is the real time operating system? Free Otto's implementation in the ESP 32 What are tasks queues and semaphores implementing dual core multitasking and synchronization in the sparkfun ESP 32 thing. inter task communication in the sparkfun ESP 32 thing with free arctos performance benchmarking with free Otto's implementation in the sparkfun ESP 32 thing. video What is a real time operating system. In this video, we will look at the difference between an operating system and a real time operating system.
And then we will look at the need for our tools in IoT And finally, some basic advantages or features of Otto's. Take any modern computer as an example, and we quickly see that it has an operating system of some sort. We are talking about platforms like Linux, Windows, Mac OS, and so on. An essential component of any mobile device server or computer system is a general purpose operating system, which is responsible for running all the applications in an installation. They handle memory management, hardware input output, like reading from keyboards, mice, driving graphics cards, task management, disk and file system interactions, and much more. That's the purpose of an operating system is to provide an interface between software applications and the underlying hardware infrastructure.
If it were involved An operating system, each application would likely have to perform its own similar implementation of such functions, which would be a waste while earlier GPOs provided basic functions, today's GP OSS have become much richer and richer with features that it can no longer be considered just as an operating system. So then what is it Otto's It stands for real time operating system. It retains the core functions of a GPOs like memory management, task management, and API synchronization, while being flexible to be ported across different hardware platforms. It is designed in applications where time is of the essence. For example, in autonomous cars or nuclear power plants. Generally they are run on smaller most lightweight hardware then GPO versus as larger hardware configurations.
Tend to have issues with agility. What does real time in arpeggios really mean? Doesn't mean that it is faster? Not necessarily. The problem lies with the word real time. It's used all over the place in different scenarios, like real time delivery updates, real time video in real time support in this creates ambiguity.
No wonder many people misunderstand autos and think that as soon as they implement arctos in their project, it becomes faster. The key concept around which Otto's was built is determinism. Let me elaborate and artosis execution pattern must be repeatable, it should produce reliable outputs and nothing unexpected should happen. All the worst case scenarios must be known and handled. Furthermore, the reaction times to different evens should also be known. Basically, there must be zero outlier cases.
Is happening in such a system. This kind of an operating system is called a heart arctos. This implementation is done on satellites, nuclear power plants, airplanes, etc. In less critical situations like video streaming and gaming, soft arctos is implemented, where outlier cases are allowed, but managed under a threshold as long as it doesn't affect the user experience. real time operating systems do this by providing programmers with a high degree of control over how tasks are prioritized and allow checking to make sure that important deadlines are met. To fully grasp these concepts, it is helpful to consider an example.
Imagine that you are designing an airbag system for a new model of car. In this case, a small error in timing, causing the airbag to deploy too early or too late. Late could be catastrophic and cause injury. Therefore, a hard real time system is needed. You need assurance as a system designer that no single operation will exceed certain timing constraints. On the other hand, if you were to design a mobile phone that receives streaming video, it may be okay to lose a small amount of data.
Occasionally, even though on average, it is important to keep up with the video stream. For this application, a flexible real time operating system may suffers coming to think of it should have been named deterministic operating system or das initially itself to avoid all the confusion, but wait, dos was already taken by Microsoft dos. So no luck. Anyway, let's move on to why we need Otto's now more than ever. the demands of an increasingly data driven world mean that your IoT device will require robust and reliable software and Atos will be the engine powering the Internet of Things. Some of the benefits of arctos in IoT is as follows.
Priority based scheduling in autos is a powerful tool to separate critical processing from non critical, task based API in Otto's make modular development a breeze. This also allows for easier testing cycles during product development. The task based system also allows separate designers to work independently on their parts of the project. Code reusability is also an added advantage of the task based system. And Otto's can be entirely event based, and so no processing time is wasted pulling for events that have not occurred. a high degree of control is given for tuning the timing of tasks.
This allows for a cleaner and smaller application code. A separate task is allocated for background processing called idle task that ensure that things like CPU load measurement, background error checking, etc, won't affect the main processing. There are well established techniques for writing good embedded software without the use of an arctos. In some cases, these techniques may provide the most appropriate solution. However, as the solution becomes more complex, like in the field of Internet of Things, the benefits of an arctos becomes more and more apparent summary. In this video, we have covered the following topics difference between an odious and arctos What is the need for arctos in IoT advantages of using arctos in projects?
In the next video, we will look at the free Otto's implementation in the ESP 32