1. Background With the rapid development of computer technology and the continuous advancement of chip manufacturing processes, embedded systems are increasingly widely used: from civilian devices such as televisions and mobile phones to military weapon systems such as aircraft and tanks, embedded systems are ubiquitous. In the application development of embedded systems, the adoption of embedded real-time operating systems (RTOS) enables multitasking, making program development easier, maintenance more convenient, and improving system stability and reliability. This has gradually become a development direction for embedded systems. 2. Overview of Embedded Operating Systems An embedded operating system is operating system software that supports embedded system applications. It is a crucial component of embedded systems (including hardware and software systems), typically including hardware-related low-level driver software, system kernel, device driver interfaces, communication protocols, graphical interfaces, and standardized browsers. Embedded operating systems possess the basic characteristics of general-purpose operating systems, such as the ability to effectively manage increasingly complex system resources; the ability to virtualize hardware, freeing developers from the burden of busy driver porting and maintenance; and the provision of library functions, standard device drivers, and toolsets. Compared with general-purpose operating systems, embedded operating systems have more prominent features in terms of real-time efficiency, hardware dependence, software solidification, and application specialization. Embedded systems have existed for more than 30 years. Looking at the development process of embedded technology, it has roughly gone through four stages. (1) Embedded algorithm stage without operating system. The embedded system in this stage is a single chip-based system with functions that work with some monitoring, servo, and indicator devices. Generally, there is no obvious operating system support, but the system is directly controlled by programming in assembly language. The main features are that the system structure and functions are relatively simple, highly targeted, without operating system support, and almost no user interface. (2) Simple monitoring real-time operating system stage. The embedded system in this stage is mainly based on embedded processors and uses a simple monitoring operating system as the core. The system features are: a wide variety of processors with relatively weak versatility; low overhead and high efficiency; generally equipped with a system emulator, with certain compatibility and scalability; the user interface is not user-friendly and is mainly used to control system load and monitor application operation. (3) The stage of general-purpose embedded real-time operating systems: Embedded systems marked by general-purpose embedded real-time operating systems, such as VxWorks, pSos, and Windows CE, are typical representatives of this stage. The characteristics of embedded systems in this stage are: they can run on various microprocessors; they have powerful and usable operating system functions, such as file and directory management, multitasking, device driver support, network support, graphical windows, and user interfaces; and they have rich APIs and embedded application software. (4) Embedded systems marked by the Internet: With the development of general-purpose embedded real-time operating systems, embedded operating systems for Internet networks and specific applications are increasingly attracting attention and becoming an important development direction. The true integration of embedded systems with the Internet and the seamless integration of embedded operating systems with application devices represent the future of embedded operating system development. 3 There are many open-source RTOS embedded real-time operating systems, such as VxWorks, PalmOS, and Windows CE. These operating systems are all commercial products, expensive, and their closed source code leads to a series of problems such as device support and application porting. Open-source RTOS, on the other hand, has unique advantages in cost and technology, and occupies an increasingly important position in the RTOS field. This article will introduce two excellent open-source real-time operating systems, μC/OS-II and eCos, analyzing and comparing their respective characteristics and performance, providing relevant data to offer a reference for selecting a suitable RTOS. 3.1 μC/OS-II μC/OS-II's predecessor is μC/OS, which first appeared in a series of articles published in the May and June 1992 issues of the magazine *Embedded Systems Programming* by American embedded systems expert Jean J. Labrosse, who also released the μC/OS source code on the magazine's BBS. At that time, more than 500 people downloaded the source code. Thousands of engineers worldwide have applied μC/OS to various fields, such as the camera industry, engine control, network access equipment, highway telephone systems, ATMs, and industrial robots. Many universities use μC/OS as a textbook for teaching real-time systems. In 1998, the author decided to publish a second book on μC/OS, *μC/OS-II: The Real-Time Kernel*, and established an official website: www.μC/OS-II.com. This book added new features to μC/OS-II and approximately 200 pages of explanations. μC/OS and μC/OS-II are specifically designed for embedded computer applications, with the vast majority of the code written in C. The CPU hardware-related parts are written in assembly language, with approximately 200 lines of assembly language compressed to a minimum for easy portability to any other CPU. Many porting examples are available on the website. Users only need a standard ANSI C cross-compiler, assembler, linker, and other software tools to embed μC/OS into their products. μC/OS features high execution efficiency, small footprint, excellent real-time performance, and scalability; the smallest kernel can be compiled to 2KB. μC/OS-II has been ported to almost all well-known CPUs. 3.2 eCos eCos (embedded Configurable operating system) originated from Cygnus Solutions in the United States. Cygnus released the first version of eCos, eCos 1.1, in November 1998, which initially supported only a limited number of processor architectures. In November 1999, Red Hat acquired Cygnus for $674 million. In the following years, eCos became a key product in Red Hat's embedded systems field and experienced rapid development. In 2002, due to financial reasons, Red Hat reduced the eCos development team, but did not stop eCos development. Red Hat subsequently announced that it would continue to support eCos development, and the original main eCos developers formed eCos Centric, which officially released eCos 2.0 in May 2003. Although eCos is a Red Hat product, eCos is not Linux or a derivative of Linux; eCos fills the gaps in Linux's capabilities in embedded applications. Currently, a minimal Linux kernel is approximately 500KB and requires 1.5MB of memory, not including applications and other necessary services. eCOS can provide the basic runtime components required for real-time embedded applications while only occupying tens or hundreds of KB of memory. eCOS is an open-source, configurable, portable, royalty-free real-time operating system designed for deeply embedded applications. As its name suggests, eCOS's greatest feature is its flexible configuration. The core of eCOS consists of different components, including the kernel, C libraries, and low-level runtime packages. Each component offers numerous configurable options, which can be easily configured using eCOS's configuration tools. Different configurations allow eCOS to meet the needs of various embedded applications. 4 Comparison of μC/OS-II and eCOS For these two open-source real-time operating systems, we mainly compare them from the following aspects. This comparison can provide a reference for choosing the right RTOS for your system. 4.1 Kernel Scheduling Mechanism The core of the RTOS kernel is the scheduler. When a system contains multiple tasks or threads, a scheduler must be used to determine which task or thread is currently being executed. The scheduler controls the execution of threads and provides a synchronization mechanism for them. Table 1 compares the two RTOS schedulers (scheduling mechanisms). [align=center] Table 1 Scheduler Comparison[/align] μC/OS only supports fixed-priority preemptive scheduling and does not support time-slice round-robin scheduling. Its scheduling method is simple, has good real-time performance, and is easy to use. eCOS has rich scheduling methods and good adaptability. Of course, the current eCOS only allows the use of a single scheduler in its target system. Future versions will allow multiple schedulers to work together. 4.2 Inter-task Synchronization and Communication Mechanisms The functions of an RTOS are generally accomplished by several tasks and interrupt service routines. Tasks and interrupt service routines must coordinate their actions and cooperate with each other, which involves the problem of inter-task synchronization and communication. Table 2 compares the synchronization and communication mechanisms of the two operating systems. [align=center]Table 2 Comparison of Synchronization and Communication Mechanisms[/align] 4.3 Task Switching Time and Interrupt Latency Time Task switching time and interrupt latency time are two important indicators for evaluating RTOS performance. Task switching time reflects the speed at which the RTOS executes tasks, while interrupt latency time reflects the speed at which the RTOS responds to external changes. Table 3 compares the task switching time and interrupt latency time of these two operating systems. [align=center]Table 3 Comparison of Task Switching Time and Interrupt Latency Time[/align] 4.4 Hardware Support μC/OS-II and eCOS support most currently popular embedded CPUs and have excellent portability. μC/OS-II supports CPUs from 8-bit to 32-bit; while eCOS can be ported between different architectures such as 16-bit, 32-bit, and 64-bit. Because the kernels of μC/OS-II and eCOS are very small, the minimum code size after trimming can be less than 2KB and 10KB respectively, and the minimum required data RAM space can be 4KB and 10KB. Therefore, they have very low hardware requirements and are highly economical. Conclusion The comparison shows that μC/OS-II has a much smaller source code than eCOS, making it particularly suitable for learning and research. Its biggest advantage is its compact size, making it suitable for small embedded systems with limited RAM and ROM, such as microcontroller systems. eCOS's biggest advantage is its flexible configuration, making it suitable for commercial or industrial embedded systems, such as consumer electronics and automotive applications. In short, the choice of operating system depends on the hardware requirements of the target system and the complexity of the user application.