Lesson finished
Up next: Embedded Software Architectures and Classification of Embedded Systems
Unlock all 17 lessons of Medical Embedded SystemsFull course ₹40,000 · paid
Embedded System Basics, Constraints, SoC and Multi-Processor Designs
A free lesson from Skill-Lync's Medical Embedded Systems course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Module 1 Session 1”
What will you learn in this free Medical Embedded Systems lesson?
The instructor defines a system and an embedded system, then contrasts embedded systems with general purpose computers on real-time behaviour, priorities, latency and limits on memory, speed and power. It goes on to system-on-chip versus chips on a board, single and distributed processors, and peripherals such as I2C, SPI and CAN.
- Embedded versus general purpose computing systems
- Constraints: memory, processor speed, power and heat
- System on chip versus chips on a board
- Peripherals, buses and debug interfaces
What comes after lesson 1?
The next free lesson is lesson 2, “Embedded Software Architectures and Classification of Embedded Systems” (19 min). Later in Skill-Lync's Medical Embedded Systems course (paid): lesson 4, Module 2 Session 1; lesson 5, Module 2 Session 1 Part 1; lesson 6, Module 2 Session 1 Part 2. The full course has 17 lessons (8 h 32 min of video); see the course overview or its price and syllabus.
Lesson transcript
Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.
Students, this course is on Medical Embedded System. In this course, in the module 1, we will be covering on Embedded Systems Design. So, the table of contents for this module 1 will be, we will be introducing what is Embedded System, what are the types of Embedded System, what are the characteristics of Embedded System, what are the processes embedded in a system, and what is the embedded hardware units and devices in a system, and what are the embedded software in a system. And we will also be covering on Embedded System Classification, Embedded System Architecture.
Also, we will be covering on what are the skills required for an Embedded System Designer, and what are the typical application scenarios for an Embedded System Designer. The learning objectives for this module 1 will be, in this module, we will learn about Embedded Systems and how a processor is embedded into a system, the embedded hardware and software units and the devices in a system, the embedded system architecture and their classifications we will be covering. And also, we will be touching upon what are the skills required if you have to be an Embedded Engineer, and also the applications of Embedded System in the current scenario, what are the applications where Embedded Systems are being used.
So, that is how we will be covering in this module 1, and these are the learning objectives. Now, let us take up the first topic, that is, Introduction to Embedded Systems. Before going into Embedded System, let us see what a system is about. So, what is a system? A system is defined in such a way that, in a way of its working, or organizing, or doing one or many of the tasks, which are performed in a system, according to a fixed plan, or a program, or a set of rules, that is, what a system is all about.
Now, a typical example of a system are, example, you can take your watch, or your mobile phone, or your computer, or your TV, or a microwave oven. All these all are a system, basically. So, now, let us see, what an Embedded System is about. So, what are these Embedded Systems? An Embedded System is a system, that has an embedded software in a computer. The system is dedicated for either an application, or multiple applications, or a specific part of an application, or it can be for a product, or a component of a larger system.
So, basically, an Embedded System is a system, that is embedded as a subsystem, in a larger system, which may be, or may not be, a computer system. So, basically, we can say, it is a combination of hardware, software, additional mechanical, or other parts, which are designed to perform a specific function. So, the Embedded System can also be a part of a larger system, also. So, typically, you can see here, a system, from the figure, we can see, there is a system. There is an input and output.
Within the system, you can see that, there are three subsystems in there. That is, S1, S2, and S3. So, these subsystems, S1, S2, and S3, are combined to form a larger system. And there is an input. This input is going to act within the system. It can interact with either one of these subsystems, or either two of the subsystems, or with all the three subsystems as well. And in combination, it produces an output. So, this is a typical system, what we are looking at. So, now, let us see, what an Embedded System is.
So, from the figure, we see that, these are the typical components of an Embedded System. So, basically, you can see that, the Embedded System has got three main components, which are embedded into it. So, you can see that, there is an input. There is an output parameter. There is an Embedded System here. And also, in the Embedded System, we have the application software and the firmware running. And there is a hardware. So, there is a hardware in the Embedded System that has got an application software or a firmware.
And there are input parameters or variables are there, which is going to act on this embedded system. And there are outputs going to be produced based on the input parameters. And then, that is going to be represented onto a display. Or it can be given as an input to other systems as well. And there is an user interface. This user interface is going to take in any kind of an inputs, which is required for interfacing to the Embedded System. And also, this system can have a link or interface to other systems or subsystems.
So, basically, we see here that, it embeds hardware similar to a computer. So, the processor may be embedded as a processor course. So, here we see that the hardware includes embedded memory, peripherals, input and output. There are devices like input devices and output devices are going to be there. Also, we see that it embeds a main application software. So, there is an application software. The application software may perform concurrently multiple tasks or a set of tasks it can perform. So, from the figure, we can show that the units and the hardware of an embedded system are typically the, as I mentioned earlier, hardware, software.
The software consists of either the application software or the firmware as well. So, the software usually embeds in the ROM, that is the read-only memory. And there is some requirement in some applications where a real-time operating system is required. So, in those cases, the R2S is going to supervise the application software and it is going to control and access to the system resources. Also, it enables finalizing the execution of the task of a program within specified time interval. So, if you have any time critical applications, real-time operating system is manitably required.
The embedded system also takes in input parameters or variables and as an output parameter and a variable. So, it has got various links and interfaces to the other systems as subsystem as well. So, by means of external interfaces, it is going to interact with other systems or subsystems as well also. Also, we can see that the embedded system will have an user interface. The user interface allows the users to interact with the embedded hardware and the software and it can have an interface. So, basically, you can see that the embedded system is going to have a microcontroller or a microprocessor.
So, here the processors may be a general purpose or a specialized processor as well. It can be meant for carrying out any certain class of computations. Also, it can be designed for any specific application in mind if it is going to be for some dedicated applications. Also, it can be used for carrying out any IAM digital signal processing or computational purposes as well. Also, it has got various types of memories for storing the program and the data as well as. Also, the embedded systems can be used to carry out dedicated or any specific kind of a task.
Also, embedded systems are also used to reduce the size and cost of the product because if it is going to be carried out using some kind of a dedicated hardware which can be used to control a particular product or a system or a subsystem where it can be mass manufactured, you can reduce the cost of the system. Also, these embedded systems can be used to increase the reliability and performance of a system. Now, in case you have to mass produce these embedded systems, the return on investment will be very good on you and you will see that your products will be able to sell at a much cheaper price and you will be able to mass produce them in larger quantity and you will be able to have a good return on investments.
Now, let us see some of the typical examples of an embedded systems. Typically, embedded systems have got very diversified applications. Major application areas are in the areas of telecommunications like your mobile phones or your telephone exchanges, smart cards, missile applications in the military, satellite communication devices, computer networking, digital consumer electronics and automotive electronics. These are some of the areas. Typically, you can see your mobile phones. Most of your mobile phones are loaded with very high-end embedded systems having a good processing capability interfacing to various applications.
Many of your digital watchers are having wide varieties of embedded systems running in with a good computational capability with multi-functions, even having a capability of phone applications as well, where you can even talk and you can even do recording of your voice communications and other many other things. Typically, washing machines at your home, microwave ovens, dishwashers, robots, traffic light controller and various medical devices what you see in the hospital or in the home environment which you use for monitoring your health parameters. These are some of the typical examples of an embedded system.
Now, you might have a doubt on what is the difference between a general purpose system and an embedded system. So, what is the basic difference between an embedded system and a general computing system? Now, a basic computer is an example of a general purpose computing system which is a normal computer such as your laptop or your desktop computers which you commonly use. So, basically, a computer is a system which has got components like microprocessor. It will have special purpose processors like your graphics card, input-output, network processor, etc.
Basically, they will have a good large amount of memory capacity available and also they have input-output functions like your touchscreen. It will have various interfaces to devices like your faxes, modems. It will also various input devices can be connected to them like your keyboard, mouse, digitizers, scanners and also it will have output devices like it can have a touchscreen or an LCD screen or it can have a normal CRT monitor or your TFT monitors. It can also even connect your printers and networking interfaces like your internet interface.
It can have bus drivers, wireless interface, Bluetooth, various types of connectivities are possible and it will have some kind of an operating system running like your Windows or your Linux such kind of an operating system. They will be running on them. So, typically, the characteristics of a general purpose computing systems are, now let us see what are the characteristics of a general purpose computing system. So, in a general purpose computing system, you can see that the program first loads itself into the RAM and then it runs the programs and then multiple programs are going to run and multiple tasks are going to be carried out and it is going to be running in a parallel processing method.
And here, a requirement of an operating system is going to be there and it is going to run very complex algorithms as well as and also it is going to provide some set of good graphics or touchscreen interfaces where you are going to have a GUI, you are going to interact with it. Also, the general purpose computing system has got little constraint of the memory and no time deadlines are going to be there for any task to be completed or executed from the programs. Whereas, if you take an embedded system, embedded system has got some specific characteristics.
So, the characteristics are the program is going to be preloaded or it is going to be embedded into the RAM, ROM or it is going to be loaded onto the flash memory. And here in the embedded system, we see that the functions are going to be carried out in real time. So, the system functions are going to be carried out in real time and the task is executed according to priorities. So, you are going to set some priorities for your task, which is a high priority, low priority and then according to the priority, the system is going to execute the task based on the priorities which have been assigned.
Also, the system is going to react to events and it interprets in the pre-determined time intervals and also the responses are going to be scheduled according to the priorities. Also, in the embedded system, you can see that the system controls the latencies of the task. So, there is each task is going to have some latencies and the events and then the interrupts and the response are accordingly controlled. So, what is the latency? Latency means the time interval between the instance of need to respond and the start of the actual execution of a task.
Also, the embedded systems, if you see, they have dedicated set of functions. They are not very generic. They will be dedicated set of functions and also they can be used to carry out complex, dedicated, some special purpose algorithms can be carried out. And it can be carried out in an efficient manner and then the task can be executed within the embedded system. Also, they have dedicated purpose, pre-programmed hardware and graphics and other user interfaces. But as such, the embedded systems also have some constraints. If you see, the embedded systems also will have some constraints.
What are the constraints? Basically, here the availability of memory is very limited and also the limited availability of the processor speed. So, here in an embedded system, you cannot expect that you will have a luxury of a very high computational processor because accordingly, the system cost goes up, the cooling requirements will go up and other factors we will have to look into when you are selecting your processor as well. And also, in the embedded system, there is a need for the system to run continuously. So, there is a need to have the system continuously on.
So, there is a need for the power to be consumed continuously. So, we need to see that the power consumption is going to be restricted or limited so that you conserve your battery or your power. And also, you need to see that there is going to be a lot of amount of heat is going to be generated. We need to see how we are going to dissipate the heat, how we are going to take care of the cooling mechanism. And also, the program has to be run by managing the power dissipation to a minimum level.
The system is designed for an embedded system have constraints for performance, power, size and the design and manufacturing costs. So, these are some of the constraints which we should look into when you are designing an embedded system. And then, you are going to design for a specific application. Now, let us move on to the next topic. Now, let us cover up on the types of embedded system. Now, let us see what are the different types of embedded systems. So, the embedded systems are classified based on the performance, the functional requirements are based on the performance of the microcontroller as well.
The performance or functional requirements are again classified into real-time systems, standard one systems or network systems. Now, the other classification of embedded system is based on the performance of the microcontroller. Again, based on the performance, there are three levels of classification. They are classified into small scale, medium scale or high scale microcontrollers or embedded system. Based on the performance of the microcontroller, we can classify them as either small scale, medium scale or high scale embedded system. Now, let us see the characteristics of embedded system. So, what are the characteristics of an embedded system?
So, the embedded systems are being designed to carry out some kind of a specific task. Embedded systems are designed to carry out some type of a specific task. Also, it is not necessary to have a general purpose computer to carry out multiple tasks. Also, the embedded system can be used for real-time applications and they can also be used for low or high performance requirements. Also, the embedded system can be designed in such a way that you can design a very simple embedded system or a very complex embedded system and also the complexity and the application of the embedded system will decide your cost also.
So, there are some important characteristics which you need to consider when you are designing an embedded system. Basically, the embedded system performs specific tasks. So, the embedded system is going to be designed to carry out some kind of a specific or a dedicated function. So, the cost of the embedded system should be kept at very, very low. It should not be expensive. Also, it should be time-specific in the sense that it should perform the task within a certain time frame. Also, it should consume very low power.
Embedded systems do not require much power to operate. So, we should always ensure that we are going to design an embedded system at a very low power consumption levels and also it should have high efficiency. The efficiency of an embedded system should be very, very high and also it should have minimal user interface. The user interface should be kept at very minimal and also it should be very easy to use and it should have less user or human intervention to the system. So, basically, the embedded system should require no humans to intervene or very less human intervention should be there to the embedded system.
Also, the embedded system should be highly stable. The embedded system should not frequently or should not require regular maintenance. So, it should be highly stable enough. Also, it should be highly reliable. The embedded system should be highly reliable and should perform the task in a very consistent manner. An embedded system can use a microprocessor or a microcontroller as well and also they can use memories based on their requirements. And also, if you have designed any embedded system, it should be easy to manufacture. So, majority of the embedded systems are manufactured, are designed to be very compact and also it should be affordable to manufacture.
And also, the size and the complexity should be very simple enough so that the manufacturer finds it easy to manufacture them and reproduce in larger quantities in a shorter time. The other characteristics of an embedded system are they do not have to be as standalone devices. Embedded system may be a smaller system in a larger system as well. Example, if you take your car navigation system, the car navigation system is a smaller embedded system into a bigger car as a major system and there are various other functionalities built into that.
The car navigation system is an embedded system built in into your car. So, the embedded systems are programmed with the firmware and the firmware is stored in a memory. It can be in a ROM or in a flash memory. Now, let us see the user interfaces for the embedded systems. So, the embedded system may or may not have a user interface at all. It can be a simple user interface or to a complex graphical user interface. They may also resemble some kind of a modern computer desktop like OS.
The embedded devices generally use buttons, LED, LCD or they can use a touchscreen or they can be menu-driven touchscreens available as a user interface. Yes, also the embedded systems have remote interfaces where you can try to interface or have access to your embedded system from a remote location by means of serial interfaces or it can be through USBs or Ethernet or it can be through wireless as well. Now, let us move on to the next topic. Now, what are the essential considerations in an embedded system?
So, embedded systems are always unique and they are basically being customized for the functions and services for which they have been tasked to perform. So, when you are going to design an embedded system and you are going to program the software for an embedded system, the development teams must be very careful to consider all the options before they ensure that the product is going to meet the exact specifications for the user as given as. Also, they need to comprehensively review the development options and also see the best possible method to implement them.
And also, they also need to look into how best they can optimize the embedded system to meet the functional objectives what have been given by the users. So, some of the functional objectives like what are the considerations you need to look into is the response time. So, in real-time systems, within what time a particular task is to be completed or whether a particular function has to complete its functionalities within that given time intervals you gotta start to get some confirmation answers or what is the size of it what is the area it is going to occupy what is the location it is going to Dean C2Q and that you need to come in regarding the design reason and what is the supply It is going to be located at what environment it is going to work. So, what is the size, weight which is going to be, when it is going to be defined and also the cost.
The cost of the embedded system should be as minimum as possible so that it does not add to the overall cost of the system and also the cost should be affordable. Also, the embedded system must be portable. It should not be a device which is very bulky. So, it should be a portable device and it should be easily carried and then interface to a subsystem or a larger system. Also, the embedded system should be designed in such a way that they consume low power. Especially, if you are going to use these devices in a remote locations and battery life has to be preserved, you should ensure that they consume as much as low power as possible, especially if they are going to use a battery at remote locations.
Also, these embedded systems should be fault-tolerant. In case there is a system which is going to perform some task and it is going to hang for a longer time, it should be in a position to recover itself back and also it should not give out any faulty readings or recordings. It should be in a position to give you some kind of an authenticated data only and also it should be an validated data. And also, the system should be functional in all aspects and it should be in a self-requiry mode in case it is going to go into some kind of an unknown conditions.
These are some of the considerations which you need to look into when you are designing an embedded system. Now, let us move on to the next topic that is the processes embedded into a system. So, the properties of a typical embedded system as we covered are low power consumption, small size, which should have a rugged operating ranges and low per unit cost. Now, you know that there are numerous number of microcontrollers being developed for embedded system use. Also, the general purpose microprocessors are also commonly used in the embedded system.
But if you are going to use a microprocessor, they require more support circuitry as compared to the microcontrollers, which you use in an embedded system. Basically, there are going to be two approaches for the design of embedded system. In the first approach, we are going to design the embedded system using the system on chip concepts. This approach is very commonly used and very extensively used for systems like mobile phones, camera and complex systems. The second approach is based on the design using the chips on a circuit board.
So, that approach is also a cheaper approach and then the processor is a little cheaper. In the second approach, the separate chips of the microprocessors or application-specific instruction set processor called ASIP, memory, single-purpose processor and peripherals are going to be interconnected on a board. So, basically, all chip interfaces with an appropriate circuitry. The chips are going to be interconnected on a board and the software is going to be embedded onto the memory. The software is going to be embedded into a memory, that is, which is running on a chip.
The system on chip can be used to design complex embedded systems. In an SOC, you can see that a complex embedded system is designed on a single silicon consisting of multiple processors, hardware units and the software. Here, the SOC is a design innovation in an embedded system where on a large VLSI chip, it has got multiple processors, software and all the needed digital as well as analog circuitries are going to be built onto a single chain. So, if you take an SOC, SOC will contain many other components like it can have an embedded general-purpose processor.
It can have an embedded application-specific instruction set processor like ASIP with the instruction set of a microcontroller or a digital signal processor or a graphical processor available on them. It can have single or multiple processors available on a single SOC and also it will have catch, RAM, RAM and flash memories available on them. Also, the circuits for the specific or special functions for a single-purpose application-specific integrated circuit, that is ASIC applications can be built in on a single SOC. Also, it will contain analog circuitries and other logical circuitries also can be built in on an SOC.
So, you can see that an SOC will have larger varieties of devices available on a single chip and you can easily interface them and it has got a numerous number of advantages if it is available on a single system on chip. In general, if you see that SOC needs very large design effort and the cost of the development is also going to be high. Here, the non-recurring engineering cost is going to be very high. But the advantage of SOC is that the system has got very high performance and functionalities are very high.
They have improved and there is going to be very low power distribution because all the components are built on to the single VLS in here. You will see that the interconnections are not going to be there. Cables are not going to be there. You will see that failures are going to be very, very less. And since it is going to be running on low voltages, you will see that the power consumption is going to be very less. And also, the SOCs are going to be used in embedded system which are extensively and commonly used.
And they are going to be small in size and performance is going to be very, very high. And you can see that on a single SOC, larger functionalities are available. And also, you need low power energy to run these devices. And power consumption is going to be very less. Hence, cooling requirements are going to be less. You can preserve your battery and power dissipation is going to be very, very low. And you can see that nowadays, most of your devices, whatever you have, like your mobile phones or your PCs, your digital TVs, digital cameras, networking devices, all wireless communication devices, set-off boxes, they all run on system objects.
That is, the SOCs are very commonly used there. I had mentioned that the embedded systems can be designed using a single processor or a multiple processor. And also, a single processor can run multiple processes within them. And then, you can carry out multiple tasks. So, the design of embedded system can be carried out using a single processor or a multiple processor. And each of the processor can have multiple processes running within them. They can carry out multiple tasks within them. So, the processor can be of different categories.
It can be a general-purpose processor, like your microprocessors, microcontrollers, or embedded processor, digital signal processor, or a media processor. Or it can be an application-specific processor. Or it can be an application-specific instruction processor. You can design them using these type of categories of processors. Again, based on the functionality, complexity, and the computational requirements, the number of processors which is going to be designed in an embedded system is going to be designed by the design team. And they take a decision whether a particular requirement can be met with a single processor or a multiple processor.
In a simple embedded system, basically, a single processor is used to carry out various functionalities. So, you can see in the figure that this is a simple embedded system where there is a single processor-based system. There is an input and output. There is an input and output. And you can see there is an input. In the processor, you can see that there are multiple processes which can go on based on the input which is there. And there is an embedded software which is going to run there.
And it can carry out the processing with different processes which are there in the system. And they can, based on that, the output of the process, then that is going to be given, displayed on an output device. Also, you can see that within the processor, multiple tasks can be carried out. So, that task can be in the form of various interrupts like, for example, interrupt 1 will happen. It will carry out a task in process 1 where the interrupt is going to happen. And the application takes to a various, into a separate subroutine where the subroutine is going to carry out a particular task.
And then the results are going to be returned or simultaneously in a process 2 as a task 2 can be carried out. And then it can return back to the process 2 or simultaneously a process 3 can happen where a task can be carried out and the results are going to be returned. It is not necessary that all the three processes are going to run. Based on the input, either one of them can also be done or two of them can be done in a different combination or all the three can also happen.
Based on that, the output is going to be represented in the output device. So, you can see in the processor, there is going to be an application which is going to start and it is going to carry out variation initialization. And it is going to wait for an interrupt to happen based on the input. Once the input is going to come into the processor and the embedded software is going to trigger various processors within them and then there is going to be an output which is going to be produced.
So, this is based on a single processor. So, now let us see what is a distributed or a multiple processor based application. In a distributed computing, basically we use multiple processors. So, multiple processors are going to be used. So, here in this example, what I had shown you, there are three processors, processor 1, 2 and 3. So, each processor is running a different process on them. So, there is an input and an output. You can see that processor 1 has got two process running and processor 2 also has got process 1 and process 2 running within them.
The processor 3 has got three process running within them. So, each algorithm or a CELTAF algorithm is going to be executed on each of the processor and the system may require a number of processors to implement the computational units based on the complexity. So, the implementations are going to be specific or it is going to be based on the need of the system. The multiple processor is going to integrate the system. Typically, you take an example of a video camera. Here, the video camera application, you can see that there is an image acquisition.
And that I want to wait to see that there is an image of the computer. Thank you. This is going to run in a processor and the processing of the bytes for the pixels after taking the image is going to have another processor unit running in and your camera is going to relieve for the next image to be captured. So you can see that each camera frame requires some kind of an compression before they are going to be stored into the camera memory. So you can see that the camera requires some kind of an algorithm to carry out like for example a DCT algorithm to do the compression of the images and then store them.
So the stored images are going to be then decompressed before you are going to display them or you are going to print them. So the decompression algorithm will require an inverse DCT functions to be carried out. So the compression and decompression itself is a very complicated algorithm which is going to require you a separate processing unit. So you can see that a camera reads, a camera is going to need multiple processor units. So that all the processing is going to complete before the camera is going to be ready to take a next image or a frame into your video recording.
Now let us take another example of your mobile phone which you can understand very easily because most of us have got a mobile phone with us. The smartphones have a number of applications running parallelly and they require very high computational requirements. So the mobile phones are going to need the communication processor, graphic processor, user interface processor, voice processor, touchscreen interfaces and also it will have some kind of a keyboard inputs or your touch inputs which are going to feed it. So this is a very complicated distributed system.
So you can have a single processor or a multiple processor based mobile phone based on your application needs. And then you can have various processors running in each of the processors. And then you can see that all the processors can run parallelly and they will make the system to feel as if they are running in real time. So these are the typical examples of a distributed computing. Now let us see what are the characteristics of a distributed computing. So in a distributed computing components may be physically distributed.
As we have seen in the previous example components like we have three processors which are being physically distributed. And there is going to be communication happening among all the multiple processors which are going to be there. And there is a dedicated hardware connecting through the communication channels. And also this is basically since it is going to be distributed and then you are going to carry out multiple computations in different process. Basically they are going to be very economical as well. For example, if you are going to have a embedded system which is going to be distributed with four numbers of 8 bit controllers.
You can see that the cost of the 8 bit controllers may be cheaper than a single 32 bit controller. So you can see that you can design an embedded system with four numbers of 8 bit controllers at a cheaper price rather than going for a single 32 bit controller based application. Also multiple processors can perform multiple time critical tasks. So that is the advantage what we will have. And also you will see that if you are going to use a distributed system we have better logistics.
That is the devices are going to be controlled may be well controlled and they are going to be physically distributed as well. So you will see that the devices are going to be better controlled. Now let us take up the next topic that is the embedded hardware units and the devices in an embedded system. So basically an embedded system hardware is similar to a computer. So the processor is an embedded processor core. Here the hardware unit consists of a number of building blocks in a circuit board or in an ASIC or on an SOC along with the processors.
The hardware units includes like embedded memory, peripherals, input and output devices. Also it embeds a main application software. So the application software may perform concurrently multiple tasks. So the various embedded hardware units and devices in an system are like the main units is the microcontroller or a microprocessor. or a digital signal processor or a digital signal processor. It will have sensors. It will have converters like analog to digital converters, digital to analog converters. It will have actuators, display, keypads. It will have memory both on-chip and off-chip memories.
And also they have communication path with the interfacing environments. Basically the bus protocols are going to be there. The hardware units also will additionally be present in the embedded system are the power supplies, the clock oscillators and clocking units. The system timers, real-time clocks, reset circuitries, power up resets, watchdog timers. These are some of the units which may be additionally present in an embedded system. Now let's see what are the peripherals which are going to be connected to an embedded system. Basically the embedded systems talks with the outside world via the peripherals.
Peripherals are like serial communication interfaces like RS-232, RS-422, RS-485 interfaces. Or it can be through the synchronous serial interfaces like your I2C, SPI, SSC and ESSI. Or it can be your USBs or it can be through the media cards like SD cards, Compact Trash and other devices. Also the embedded system talks with the outside world via other peripherals like your network interface cards, Ethernet like NIC cards, Wi-Fi, fiber optics. Or it can be through field buses like your CAN bus controllers or your LIN buses or like your PROFIBUS.
Or it can be through the timers like face lock loops, programmable interval timers. Or it can be through general purpose input-output GPIO devices. Or it can be through your analog to digital converters or digital to analog converters. And also for debugging we use the JTAG or the in-system programming or background debug mode interface port or like the BITP and the DB9 ports. Now let's go on to the next topic that is the embedded software in a embedded system. In the design of the embedded software architecture, here the software is simply going to have a loop which is going to monitor the input devices.
So these loops are called as subroutines. So each of which is going to manage a part of the hardware or the software. And these loops are going to be a simple control loop or they are going to be a program input-output loops. So a simple control loop can be a software which runs in repetition or in a loop. Or they can be in the form of subroutines which are going to be called repeatedly and they are going to handle some part of the software and the hardware.
Well, here the machine is a little bit more of a software. Well, we'll open the insert and there's a little bit more. If we can do it, we'll open it up and instead. And you can hear it.