Embedded OS
An embedded computer system runs nearly every electronic device available today. These tiny programs regulate everything from the apps on a cellphone to the heat in a toaster. This type of system centers on microcontroller chips. These chips function like a tiny computer, taking in information, processing it and then outputting information. Unlike a normal computer, a typical microcontroller chip is only able to do one thing. While all of these embedded systems have microcontroller chips, only the more complex ones have a full embedded operating system. Generally, in order for an embedded system to warrant an actual operating system it needs at least one of two things: complexity or interactivity. A complex system needs to take in information from multiple sources, perform multiple types of operations or output different information based on its situation. In essence, it needs to be able to do multiple tasks. The other common requirement for an actual operating system is interactivity. If a user has to interact with the operation, especially if the operation is time dependent, it will usually have an embedded operating system. Since a standard controller simply takes in and sends out data, any time a user needs to interact with that data a more complex system is needed. Many real-time operating systems are also embedded. This type of system requires immediate response to data input--latency and lag are not an option. Since an embedded system has no purpose outside its specific task, they operate well together. These systems typically run immediate response procedures, such as the anti-lock breaking processes on a car.
Are there any drawbacks to using embedded operating systems?