What operating systems does the Internet of Things have? Summary of IoT operating systems

In 2018, the in-depth transformation of the industry by the Internet of Things has begun. The quality and quantity of the Internet of Things industry chain companies will enter a full-blown period. As a full-cycle observer of the Internet of Things and a focus center for information services, IoT think tanks are promoted by the industry and will also feed back on industrial upgrading. Since 2016, the Internet of Things think tank has launched the "National Internet of Things Industry Panoramic Atlas" every year, providing practitioners with a full-perspective tracking and analysis of the Internet of Things, and implementing the symmetry of information in the Internet of Things industry.

However, with the rampant upgrade of the Internet of Things industry, the release of the annual panoramic map is far from satisfying the rapid development speed and corporate demands. Based on the above facts, the "Panorama Atlas of the National Internet of Things Industry" has decided to undergo a major revision and upgrade:

(1) The annual static will be condensed into a shorter period of "dynamic update";

(2) The large and comprehensive corporate collection method will be embedded in the selection criteria that meet the industry factual standards, which is three thousand weak, and only the best is selected;

(3) The collection of basic information of Internet of Things companies will be upgraded to richer and deeper information integration and processing;

(4) The focus on the entire section of the Internet of Things industry will be upgraded to focus on the weight distribution of key areas and potential tracks.

The key sectors that were flopped for the first time include: IoT chips (mainly computing chips and communication chips), authorized spectrum IoT networks, unlicensed spectrum IoT networks, IoT operating systems, IoT PaaS cloud platforms, utilities, and intelligence There are more than ten technology categories/vertical fields such as security cameras, smart homes, smart fire protection, smart logistics, smart door locks, and smart lighting.

The Internet of Things think tank will continue to publish a brief summary of corporate information in the above-mentioned fields. If, because of our omissions, you have missed which IoT industry is the best company, please contact us and feel free to give us your advice.

As the commanding heights of the strategy in the era of the Internet of Things, the IoT operating system has attracted the participation and deployment of many enterprises. The kernel of the RT operating system was born in 1980; the RT operating system was introduced in 1990; the open source Linux became popular after 2000; Android in 2010 dominated the mobile terminal market and radiated embedded applications; and now, the era of the Internet of Things operating system Coming as promised. The wind of change of the times, almost every ten years, has blown up many technology companies. While building the operating system ecosystem, they have also made great technology companies. Google, Apple, Microsoft, etc. are all like this. When personal computers are moving to millions of households, Microsoft has seized the opportunity to become the overlord of computer operating systems. When smart phones became a must-have item, Google and Apple seized the opportunity to become the duo of the mobile operating system market.

However, in the early days of the Internet of Things operating system, due to fragmented Internet of Things applications and diversified Internet of Things terminal devices, the Internet of Things operating system did not become like a PC or mobile phone operating system. It was quickly unified, forming one or two. The pattern of the dominance of the company. With the continuous development of the Internet of Things market, around 2014, a large number of Internet of Things operating system service providers began to emerge, including industry giants in the chip, Internet, and ICT fields, and of course a large wave of start-ups and some traditional embedded The operating system providers are following each other!

At present, there is no clear definition of the Internet of Things operating system, but in the context of the continuous increase of Internet of Things devices, it has ushered in a variety of paths of development.

One is tailored and customized based on Linux, Android, iOS and other operating systems to meet the needs of IoT access devices;

The other technical route is based on traditional embedded operating systems and real-time operating systems, and by adding functions such as device networking to meet the interconnection requirements of Internet of Things access devices, and form a new Internet of Things operating system;

The third technical route is a new operating system for the Internet of Things.

This article will sort out and introduce the IoT operating systems created by chip vendors, Internet service providers, software providers, ICT service providers, and innovative companies from different perspectives:

(Note: If there is no separate operating system logo in the above picture, use the corporate logo instead)

mbed OS

Owner: ARM

Name: mbed OS

URL:

The ARM®mbed™ operating system is an open source embedded operating system designed for "things" in the Internet of Things (IoT). The operating system contains all the functions necessary to develop connected products based on the ARM Cortex-M microcontroller, and is very suitable for applications involving smart cities, smart homes, and wearable devices. Simply put, Mbed is a development platform, a microcontroller development platform based on the ARM cortex M series.

Long before embedded devices are connected to the Internet, traditional embedded operating systems have been designed. Therefore, this type of operating system cannot address the new requirements for IoT devices. In contrast, the mbed operating system is specially built for IoT devices. The design revolves around the five core principles of IoT devices: security, connectivity, manageability, efficiency, and productivity.

Android things/Brillo, Fuchsia

Owner: Google

Name: Android things, Fuchsia

URL: https://developer.android.com/things/

Android Things is a new version of the system after Google changed its name for Google Brillo, which is an IoT operating system announced by Google in 2015. Although the core of Brillo is the Android system, its development and deployment are obviously different from regular Android development. Brillo takes C++++ as the main development environment, while Android Things is for all Java developers, regardless of whether they have mobile development experience or not.

Android Things platform architecture

Android Things integrates Weave, a communication platform for IoT devices, and Weave SDK will be embedded in the device for local and remote communication. Weave Server is a cloud service used to handle device registration, command transmission, state storage, and integration with Google services such as Google Assistant.

From the perspective of hardware resources, Android Things is a local tyrant-level system. The memory of hundreds of MB is obviously not suitable for single-chip microcomputers. This is normal, because its main competitor is actually Windows 10 IoT.

In August 2016, it was reported that Google was "quietly" developing a new operating system named "Fuchsia". Pink + Purple == Fuchsia (a new Operating System)", which means that pink plus purple equals Fuchsia, a brand new operating system, which is also dubbed the crimson goblin by netizens.

Unexpectedly, it is not based on the Linux kernel, but based on a kernel called Magenta. Magenta is a project based on'LittleKernel' (LK). LK is a lightweight kernel mainly for small systems and embedded applications. , Suitable for use when the hardware processing capability is weak, but Magenta is much more powerful than LK.

Although Android accounts for most of the mobile device side, Android still has many problems, such as serious fragmentation, poor performance on large-screen devices, and stuttering and experience problems criticized by many users. Although the essential reason for the lag is that the background of many unscrupulous applications wake up to each other, uncontrolled permissions, memory usage, etc., but this also reflects that the underlying architecture design of Android is flawed. So Google wanted to abandon Linux altogether and develop its own Fuchsia, while also avoiding the GPL.

The media speculated that Fuchsia's kernel is designed for IoT devices, so this may be a lightweight IoT operating system developed by Google.

Windows 10 IoT Core

Owner: Microsoft

Name: Windows 10 IoT Core

Website: developer.microsoft.com/en-us/windows/iot

Windows 10 IoT is a series of Windows 10 versions for various smart devices, covering a wide range of types from small industry gateways to large and more complex devices (such as point-of-sale terminals and ATMs). Combining the latest Microsoft development tools and Azure IoT services, partners can collect, store, and process data to create viable business intelligence and effective business results. After building a solution based on Windows 10 IoT, partners will find more opportunities when using a range of Microsoft technologies to provide end-to-end solutions.

Since Windows 10 for IoT is a brand new product, it clearly lags behind many other IoT operating systems in terms of user base and experienced developers. Having said that, this operating system has great potential, especially if you want to develop applications in-house. In the end, those who are accustomed to using Visual Studio and Azure IoT services, who are engaged in development work for Windows, will be attracted to the whole set of Windows 10 for IoT solutions.

Microsoft puts more emphasis on the Windows One strategy proposed in Windows 10, that is, hope that one Windows can adapt to all devices and screens. And provide a consistent experience for users and developers.

In this way, the system has powerful functions, but it will inevitably lead to its oversize. At present, Windows IoT Core provides two versions, respectively for two scenarios with display and without display (headed or headless mode). The headless mode requires 256MB of memory and 2GB of storage, and the headless mode requires 512MB of memory and 2GB of storage.

Tizen

Owner: Samsung

Name: Tizen

Website: developer.tizen.org/development/iot-preview/getting-started

Tizen is an open source standard software platform based on HTML5. It faces smart phones, tablets, in-vehicle information, smart TVs, and laptops. Customers can enjoy innovative operating systems, applications and user experiences between devices, and Tizen supports original device creators.

After Samsung tasted the sweetness of the Android system, it was a few years ago that it had to develop its own Tizen system, which also went through several twists and turns. Since Intel and the Linux Foundation announced their commitment to the development of Tizen in 2011 to January 17, 2012, the three provinces announced the integration of Bada into Tizen. From the launch of the Galaxy Gear smartwatch equipped with the Tizen system to Samsung’s announcement that its smart TVs will adopt the Tizen system in 2015 .

The Internet of Things operating system developed by Samsung Electronics is in fact a simplified version of the Tizen operating system, which is currently used in Samsung Electronics’ smartphones and TVs. According to Samsung Electronics' plan, home appliances such as refrigerators, electric ovens, washing machines and light bulbs, etc., will be likely to adopt this operating system.

AliOS-Things

Owner: Ali

Name: AliOS-Things

URL:

AliOS Things is a lightweight IoT embedded operating system for the IoT field. Committed to building cloud-integrated IoT infrastructure equipment. With extreme performance, minimalist development, cloud integration, rich components, security protection and other key capabilities, and support terminal devices to connect to Alibaba Cloud Link, it can be widely used in smart homes, smart cities, new travel and other fields.

Minimal development

Based on the Linux platform, it provides an MCU virtualization environment. Developers directly develop hardware-independent IoT applications and software libraries on the Linux platform, and use PC platform tools such as GDB/Valgrind/SystemTap to diagnose development problems;

Provide IDE, support system/kernel behavior Trace, Mesh networking graphical display;

Provide Shell interaction, support various detections such as memory trampling, leaking, and maximum stack depth;

Provide a component-oriented compilation system and Cube tools to support flexible combination of IoT product software stacks;

Provide various product-level components including storage (power failure protection, load balancing).

Plug and play connection and rich services

Support umesh plug-and-play network technology, the device will automatically connect to the network after power on;

Connect seamlessly with Alibaba Cloud Computing IoT services through Alink.

Fine-grained FOTA update

Support application code independent compilation image, IoT App independent minimal image upgrade;

Supports high image compression.

Thorough and comprehensive security protection

Provide system and chip level security protection;

Support trusted operating environment (support ARMV8-M Trust Zone);

Support preset ID2 root ID card and asymmetric key, as well as trusted connection and service based on ID2.

Highly optimized performance

The kernel supports Idle Task cost, Ram

Provides YLOOP event framework and core components based on this integration to avoid stack space consumption. The core architecture is well-supported for very small FootPrint devices.

Feature evolution to solve practical IoT problems

Better integration and optimization of cloud integration, simpler development experience, safer, better overall performance and algorithm support, and more feature evolution.

Lite OS

Owner: Huawei

Name: Lite OS

URL:

Huawei's IoT operating system Huawei LiteOS is a lightweight operating system based on a real-time kernel developed by Huawei for the IoT field. This project belongs to the basic kernel source code of Huawei LiteOS. The existing code supports common data structures such as task scheduling, memory management, interrupt mechanism, queue management, event management, IPC mechanism, time management, soft timer, and doubly linked list.

The code of Huawei LiteOS will be under the BSD 3-Clause License, unless Huawei chooses another license ("Applicable License").

Lite OS is currently the world's lightest IoT operating system. Its system size is as light as 10KB, with zero-configuration, self-organizing, and cross-platform capabilities. It can be widely used in smart home, wearable, industrial and other fields. Because LiteOS implements open source, partners can quickly build their own IoT products, which will make the development of smart hardware easier and accelerate the interconnection of everything. The Lite OS model is similar to the Contiki system invented by Oxford University researchers and the TinyOS invented by the University of California, Berkeley. It also has the characteristics of lightweight and open source.

The LiteOS operating system has the characteristics of the lowest energy consumption, the smallest size, and the fastest response. It has launched a fully open open source community, providing chips, modules and open source hardware boards, such as HiSilicon’s PLC chip HCT3911, media chip 3798M/C, and IPCamera chip Hi3516A , And LTE-M chips, etc. (Developers can also choose third-party chips, such as STM32, etc.).

LiteOS is mainly used in smart hardware in the IoT field such as smart home, wearable, car networking, smart meter reading, and industrial Internet. Data collection and real-time control are its typical use environments.

Oasis OS

Owner: New H3C

Name: Oasis OS

URL: Products___Technology/Technology/LvZhouOS/

Oasis OS is a unified IoT operating system and middleware platform independently developed by Xinhua 3 for the IoT field, free and open source. It has key capabilities such as security, lightweight, low power consumption, real-time and fast speed, openness, and interconnection. Developers provide a one-stop complete software platform, which effectively reduces the development threshold and greatly shortens the development cycle. Oasis OS can be used on smart hardware devices in smart cities, industry, agriculture, campuses, hospitals, wearables and other IoT fields to form a unified data format and upload to the Oasis cloud platform.

UHomeOS

Owner: Haier

Name: UHomeOS

URL:

UHomeOS framework diagram

The UHomeOS operating system is based on the integration of hardware modules, interconnection, big data, artificial intelligence and other technical achievements, gathers the ecological service resources of the smart home industry, provides a cross-scenario, fully compatible, multi-resource, and high-security basic operating environment, centered on home users, Connect three networks of people, home appliances, and services to empower home appliances, let home appliances understand user needs, and actively provide users with personalized ecological scene services to enhance user experience.

HelloX

Name: HelloX

URL: Not available

HelloX is a completely open source IoT operating system developed by domestic operating system enthusiasts. The HelloX operating system also conforms to the hierarchical structure of the IoT operating system.

HelloX layered architecture

At the bottom is the driver layer, which implements driver support for most common hardware, including USB, Ethernet, SPI/UART, and so on. Strictly speaking, the driver layer should be part of the kernel. In the implementation of HelloX, in order to highlight the characteristics of HelloX's rich driver support, the driver is taken out separately as a level display.

Above the driver layer is the kernel layer. Mechanisms such as memory management and task scheduling are all implemented in the kernel. Unlike other IoT operating systems based on Linux kernel customization, HelloX's kernel is completely newly developed based on the characteristics of the IoT. The modules in the kernel are loosely coupled, and any kernel modules can be flexibly tailored or added according to needs. This ensures the scalability of the kernel and can meet various fragmented hardware requirements. You can also replace the default module or algorithm in the kernel as needed. For example, you can use a custom task scheduling algorithm to replace the default priority polling-based scheduling algorithm in the kernel. You can also use a more real-time memory allocation algorithm (such as a fixed-size linked list method) to replace the default free linked list memory allocation algorithm in the kernel, and so on. For MMU support, HelloX is also implemented as an optional module, cutting out the MMU function will not have any functional impact on other modules in the system (but memory protection, virtual memory and other mechanisms cannot be used).

Above the core layer is the peripheral component layer. HelloX provides a variety of peripheral components including network, file system, system calls, etc., for IoT application development and call.

The current HelloX transplants the IoTivity IoT collaboration framework as its own collaboration framework. In the future, according to needs, HelloX will develop a more flexible IoT collaboration framework to be used in conjunction with HelloX.

Based on these basic components and functions, a wide range of IoT applications can be implemented based on the HelloX operating system, such as home gateways, smart cameras, home appliances in smart homes, meter reading, e-Health, etc. At present, HelloX has realized the docking and integration with multiple IoT cloud platforms.

SylixOS

Owner: Yihui Information

Name: SylixOS

URL:

SylixOS is an embedded hard real-time operating system, similar to its operating system, the world's more well-known are VxWorks (mainly used in aerospace, military and industrial automation), RTEMS (originated from the US Department of Defense missile and rocket control Real-time system), ThreadX (mainly used in aerospace and digital communications), etc.

From a global perspective, as a latecomer to a real-time operating system, SylixOS draws on the design ideas of many real-time operating systems, including RTEMS, VxWorks, ThreadX, etc., to achieve or exceed many real-time performance parameters. The level of the operating system has become one of the best representatives of domestic real-time operating systems.

μT/OS

Owner: Dalian Youlong Software

Name: μT/OS

Website: github.com/TenuxOS

Dalian Youlong Software Technology Co., Ltd. began to learn from Google’s successful business model on Android in 2008. Based on the μT-Kernel specification, at the end of 2009, it was the first in the world to develop real-time operations that support Cortex M3 and μT-Kernel specifications. The system kernel, later gradually added mature lightweight open source middleware on Linux, launched the Chinese own open source real-time operating system for the Internet of Things-μTenux. In μTenux, the kernel that follows the μT-Kernel specification is named μT/OS .

μTenux supports a variety of 32-bit core microcontrollers such as CortexM0/3/4, ARMV4T, ARMV5E, etc. In 2010 and 2011, μTenux has successively become a global operating system strategic partner of ATMEL and ARM.

uT/OS V3.0, supports the full range of ST Nucleo boards, supports the STM32 Cube library, supports dynamic downloading of programs, and adds security APIs.

Elastos

Owner: Elastos

Name: Elastos

URL:

The Elastos OS operating system is a smart terminal operating system based on C++ component technology (CAR), supporting multiple application types (C++, Android JAVA, HTML5/JS), and oriented to personal cloud storage and home cloud IoT and home cloud Internet. The system will be used in various devices such as smart TVs, personal cloud storage terminals and wireless network application terminals, in an effort to build a relatively complete smart home environment.

TreeOS

Owner: Guanglun Electronics

Name: TreeOS

URL: #TreeOS

TreeOS is a non-core, software component-based, real-time embedded operating system, and a new type of operating system.

The TreeOS real-time operating system is seen as composed of two parts: the first part: the method of designing software architecture, which is also a componentized method; the second part: the software component library.

The following summarizes some of the characteristics of TreeOS:

A real-time operating system suitable for various single-chip microcomputers;

A real-time operating system suitable for 51 single chip microcomputers;

A new operating system using software component technology

A real-time operating system with a driver library;

An operating system that can automatically help you complete 70-90% of software development tasks;

A very simple, general-purpose single-chip operating system.

TreeOS fills the gap in the market where there is no suitable operating system for low- and mid-range microcontrollers. Due to the use of software component technology, we can further develop a software robot that can help engineers program, this is AlphaMCU. With a click of the mouse, you can easily complete 70~90% of the entire project software code (customized operating system)! And these codes are all product-level. All you have to do is write the remaining user code.

TreeOS has been successfully applied to MCS51, STC, AVR, MSP430, STM8, STM32 and many other single-chip computers. Since the front-end and back-end systems are used in the scene, this approach is more suitable for single-chip use. But in fact, TreeOS does not specifically target a certain type of computer system (the component library may be different). Therefore, TreeOS can also be applied to any other computer system that meets its design requirements, such as ARM7 or PC.

The applications of TreeOS include: industrial control, instrumentation, automotive electronics, civil electrical appliances, medical equipment, communications and many other industries.

RT-Thread

Owner: Rui Saide

Name: RT-Thread

URL:

RT-Thread is an open source Internet of Things operating system from China, which provides very strong scalability: from a very small core that can run on the ARM Cortex-M0 chip, to the medium ARM Cortex-M3/4/ The 7 system, even running on MIPS32, ARM Cortex-A series processors, has rich system functions, and its project source code is hosted on the GitHub repo.

RT-Thread includes its own, traditional hard real-time kernel: preemptible multi-task real-time scheduler, semaphore, mutex, mailbox, message queue, signal, etc. Of course, there are three differences between it and the traditional real-time operating system:

Device driver framework;

Software components;

Application module

The device driver framework is more similar to a set of driver frameworks, involving UART, IIC, SPI, SDIO, USB slave/master, EMAC, NAND flash memory devices, etc. It abstracts/extracts the commonalities in these device drivers, and the driver engineer only needs to implement a small amount of low-level hardware operations and board-level configuration according to a fixed pattern. In this way, a hardware peripheral can be more easily connected to the RT-Thread system and obtain the complete software stack function on the RT-Thread platform.

Software components are software units located on the RT-Thread kernel, such as command line (finsh/msh shell), virtual file system (FAT, YAFFS, UFFS, ROM/RAM file system, etc.), TCP/IP network protocol stack (lwIP) , Libc/POSIX standard layer, etc. Generally, a software component is placed in a directory, such as a folder under the RT-Thread/components directory, and each software component is described by an SConscript file and added to the RT-Thread build system. When this software component is turned on in the system configuration, this component will be compiled and linked to the final RT-Thread firmware.

Note: With the opening of the package manager in RT-Thread 3.0, more and more software components will appear in the RT-Thread platform in the form of packages. The RT-Thread platform refers more to:

RT-Thread core;

shell command line;

Virtual file system;

TCP/IP network protocol stack;

Device driver framework;

Libc/POSIX standard layer.

More IoT software packages are added to the RT-Thread system as packages.

The application module, or User Application (UA) is a dynamically loadable module: it can be compiled independently of the RT-Thread firmware. Generally, each UA contains a main function entry; an object container of its own, which is used to manage kernel objects such as tasks/semaphores/message queues of the application, create, initialize, and destroy.

Ruff

Owner: Shanghai Nanchao

Name: Ruff

Website: ruff.io/zh-cn/

Ruff is an IoT operating system that supports JavaScript development and application. It provides software developers with an open, efficient and agile IoT application development platform, making IoT application development easier.

Ruff abstracts the hardware and uses an event-driven, asynchronous I/O-based model to make hardware development lightweight and efficient. In addition to using JavaScript as a development language, it also has its own software warehouse, from modules to drivers. Improve software compatibility and lower the threshold of hardware development.

The entire Ruff development system includes Ruff OS, Ruff SDK, Ruff software warehouse, and Ruff Kit development kit. As long as you have software development experience, you can use Ruff to develop hardware applications.

The characteristics of Ruff are:

JavaScript programming-the only full-stack language with many developers as the programming language

Hardware abstraction-the hardware can be operated by calling the library, reducing the entry barrier for development

Cross-platform-ignore the board card differences, the same application code can run on different boards

Efficient and convenient development-bid farewell to cross-compilation and programming of boards, complete testing on PC, and deploy with one click

MICO

Owner: Shanghai Qingke

Name: MICO

URL:

MiCO IoT OS was released in July 2014 by Shanghai Qingke and Alibaba Smart Cloud. It is the first true IoT operating system in China. Simply put, it is an MCU-based full real-time Internet of Things operating system, a highly portable operating system and middleware development platform designed for smart hardware and running on a microcontroller. It has been widely used in smart home appliances, lighting, Medical, security, entertainment and other IoT application markets.

The full name of MiCO is: Micro-controller based Internet Connectivity Operating system. It is an Internet access operating system based on a microcontroller. Developers can design innovative smart products connected to the Internet based on MiCO on various microcontroller platforms to realize the interconnection of people and things.

MiCO is a highly portable real-time operating system designed for intelligent hardware optimization and running on a microcontroller. It contains a variety of software middleware, thereby reducing the cost of intelligent hardware development and improving development efficiency. It is the first Internet of Things operating system in China. MiCO has a complete solution, including recommended wireless network configuration, initial setup of smart hardware, fast wireless network access, local device and service discovery, identity authentication and other components. All these can reduce the cost of R&D investment and maintenance, and shorten the R&D cycle.

Zephyr

Name: Zephyr

URL:

The Linux Foundation announced a microkernel project, Zephyr, led by Intel and provided by Wind River. The Zephyr microkernel will be used to develop a real-time operating system (RTOS) for IoT devices. The Zephyr project is supported by companies such as Intel, NXP Semiconductors, Synopsys, and UbiquiOS. Wind River, an Intel subsidiary, donated its Rocket RTOS kernel to the Zephyr project.

Wind River's Rocket RTOS will be transformed into a downstream commercial distribution based on the Zephyr kernel. The Zephyr microkernel can run on a 32-bit microcontroller with only 10KB of RAM. In contrast, the Linux-based microcontroller project uClinux requires 200KB of RAM.

The Zephyr project provides security features at the two levels of equipment and communication protocol stacks. In addition, the community also takes security issues seriously and plans to establish a special security working group and appoint a security maintainer.

μCLinux

Owner: Microsoft

Name: μCLinux

Website: Clinux/

μClinux is an embedded Linux version, its full name is micro-control Linux, which literally means micro-control Linux. It was originally a derivative product of the Linux 2.0 kernel. Compared with standard Linux, μClinux's kernel is very small, but it still inherits the main features of the Linux operating system, including good stability and portability, powerful network functions, and excellent File system support, standard rich API, and TCP/IP network protocol, etc.

Because there is no MMU memory management unit, the realization of its multitasking requires certain skills.

Like Linux, μClinux operating system divides interrupt processing into two parts: top half processing and bottom half processing. In the top half of processing, the interrupt operation must be turned off, and only necessary, very small, and fast processing is performed, and other processing is handed over to the bottom half of processing; the bottom half of processing executes those complex and time-consuming processing, and accepts interrupts. Because there are many interrupt processing in the bottom half of the system, it will cause the system interrupt processing delay.

The biggest feature of μClinux is that it is designed for non-MMU processors and can utilize powerful Linux resources. Therefore, it is suitable for the development of small-capacity, low-cost products that do not require high events, and is especially suitable for the development of embedded systems that are closely related to network applications. Device or PDA device.

QNX

Owner: BlackBerry

Name: QNX

URL:?returnaddress=%2Fdownload%2Fgroup.html%3Fprogramid%3D29178

QNX is a distributed, embedded, and scalable hard real-time operating system. It complies with POSâ…¨.1 (program interface) and POSâ…¨.2 (Shell and tools), and partly complies with POSâ…¨.1b (real-time extension). It was born in 1980 and has a history of 37 years.

Gordon Bell and Dan Dodge founded Quantum Software Systems in 1980. They wrote a system called QUNIX (Quick UNIX) that could run on an IBM PC based on some ideas from the college era. It was not until AT&T sent a letter from a lawyer. Change the name to QNX.

QNX is a micro-kernel real-time operating system. Its core only provides four services: process scheduling, inter-process communication, low-level network communication, and interrupt handling. Its processes run in independent address spaces. All other OS services are implemented as cooperative user processes, so the QNX core is very small (about 12Kb for QNX4.x) and runs extremely fast.

QNX is recognized by the industry as one of the best embedded real-time operating systems on the X86 platform. It has a unique micro-kernel real-time platform, based on micro-kernel and complete address space protection, real-time, stable, and reliable. It has been transplanted to PowerPC, MIPS, ARM and other cores, and has become an embedded real-time widely used in China operating system. Although QNX itself does not belong to UNIX, because it provides POSIX support, most traditional UNIX programs can be compiled and run on QNX with minor modifications (or even without modification).

On the basis of a high-reliability core, QNX's innovative design makes it also highly efficient. The most striking thing about QNX is that it is a sibling of UNâ…¨, which maintains a high degree of similarity with UNâ…¨. Most UNâ…¨ or LINUX applications can be directly compiled and generated under QNX. This means that a large number of stable and mature UNâ…¨ and LINUX applications can be directly transplanted to QNX, a more stable and efficient real-time embedded platform.

TRON

Name: TRON

URL: Not available

TRON is an open real-time operating system kernel design project, it is the abbreviation of "The Real-time Operating system Nucleus" (real-time operating system kernel). The project was initiated by Professor Ken Sakamura of the University of Tokyo in 1984 with the aim of developing an ideal computer structure and network for the needs of the whole society.

Sakamura, a professor at the University of Tokyo in Japan, has always been a thinker outside the framework, boldly speaking, and enthusiastically supporting the next generation of computing architecture; most of his academic life has been devoted to the development of TRON and the promotion of popularization in Japan. The concept of ubiquitous computing. Sakamura said that the "Intelligent Object Network" he envisioned—similar to the popular Internet of Things—can be traced back to one of the TRON goals he developed in 1987.

TRON is not well-known in the country, but in fact, its application is very wide. If you are interested, you can search for related articles to understand, such as "TRON's Another Operating System World with Life".

μCOS-II/μCOS-III

Name: μCOS-II/μCOS-III

URL:

Those who do embedded development in China should have heard of μCOS, and μCOS is also widely used in China. This is due to the good style and openness of the code, as well as the completeness of the supporting middleware and documentation. With the support of the company and some domestic embedded experts, many Chinese books about μCOS have been published.

The predecessor of μC/OS-II is μC/OS, which was originally published in 1992 by American embedded system expert Jean J. Labrosse in the May and June issue of Embedded System Programming. It also serialized μC/OS. The source code of the OS is published on the magazine's BBS. μC/OS-II is developed on the basis of μC-OS. It is a small, preemptive multi-task real-time kernel written in C language. μC/OS-II can manage 64 tasks, and provides tasks such as task scheduling and management, memory management, synchronization and communication between tasks, time management, and interrupt service. It has high execution efficiency, small footprint, excellent real-time performance and scalability Strong sex and other characteristics.

μC/OS-II interrupt processing is relatively simple. Only one interrupt service subroutine ISR can be linked to an interrupt vector, and the user code must be completed in the ISR. The more things the ISR needs to do, the longer the interrupt latency, and the maximum nesting depth that the kernel can support is 255.

Micrium announced the addition of μC/OS-MMU and μC/OS-MPU to its embedded products. These two products increase key memory functions in embedded systems. μC/OS-MMU provides a memory protection function for a central processing unit with a memory management unit (MMU) by providing time and space protection for multiple independent applications. μC/OS-MPU protects the memory of the task to prevent unauthorized access to the system memory, destroying the content of the memory, and provides a protection mechanism for the CPU with a memory protection unit.

Regarding the difference and performance comparison between μCOS-II and μCOS-III, you can search for related articles for understanding, such as "Performance Comparison between UCOS-II and UCOS-III".

2016年，为了强化自身嵌入式物联网设计方案，Silicon Labs宣布收购物联网（IoT）即时操作系统（RTOS）软件供应商Micrium，来增进物联网嵌入式解决方案的完整性。

FreeRTOS

名称：FreeRTOS

网址：

FreeRTOS是一个迷你的实时操作系统内核。作为一个轻量级的操作系统，功能包括：任务管理、时间管理、信号量、消息队列、内存管理、记录功能、软件定时器、协程等，可基本满足较小系统的需要。

FreeRTOS的特点包括：

用户可配置内核功能

多平台的支持

提供一个高层次的信任代码的完整性

目标代码小，简单易用

遵循MISRA-C标准的编程规范

强大的执行跟踪功能

堆栈溢出检测

没有限制的任务数量

没有限制的任务优先级

多个任务可以分配相同的优先权

队列，二进制信号量，计数信号灯和递归通信和同步的任务

优先级继承

免费开源的源代码

FreeRTOS的创始人是Richard Barry，他编写了大量的移植代码和配套文档。SafeRTOS便是基于FreeRTOS而来，前者是经过安全认证的RTOS，因此FreeRTOS的安全性也有了相对的保障。

Ubuntu Core 16

拥有者：Canonical

名称：Ubuntu Core 16

网址：

Ubuntu已经向外界透露了它们对于物联网的最新想法，那就是让Linux成为让物联网更智能和可扩展的核心。Snappy Ubuntu Core是面向智能设备的最新平台，其承诺可以运行存储在本地或依赖于云端的相同软件。显然，后者的最大好处就是可以让使用者避开频繁的定期升级。

Ubuntu Core团队意识到，“联网设备”的数量将会激增。虽然手机和计算机的定期维护和更新已深入人心，但是对于洗衣机、温控器、以及智能开关来说，大家却很容易忽略掉它们。

此外，在频发的黑客攻击面前，联网设备的安全性也需要慎重考虑。如果没有最新的安全补丁和固件修复，那么必将会给联网设备的使用者留下巨大的隐患。

更重要的是，Ubuntu Core既可以在设备上、也可以依赖云端而运行。并且无论他们运行于ARM或x86平台，开发者都会得到相同的API和安全更新。

截至目前，Ubuntu母公司Canonical已经拥有了21家合作伙伴，我们希望这一数字可以在今年迎来更高的增长。

Nucleus OS

拥有者：Mentor

名称：Nucleus OS

网址：

Nucleus是为实时嵌入式应用而设计的一个抢先式多任务操作系统内核，其95%的代码是用ANSIC写成的，因此非常便于移植并能够支持大多数类型的处理器。从实现角度来看，NucleusPLUS是一组C函数库，应用程序代码与核心函数库连接在一起，生成一个目标代码，下载到目标板的RAM中或直接烧录到目标板的ROM中执行。

Nucleus是Mentor Graphics公司开发的一种嵌入式操作系统。这家公司声称，其软件目前在30多亿个设备上运行，这是个相当庞大的安装群。该操作系统为众多嵌入式架构提供了有力的支持，在汽车、医疗、公用事业、工业和消费类电子产品等行业垂直领域大受欢迎。共享单车Bluegogo用的就是Nucleus OS。

Ostro

名称：Ostro

网址：ostroproject.org

Ostro操作系统是特别为物联网建造的操作系统，开发者可以马上用，节省了很多时间，功能也非常完善，包括覆盖全面的连接标准，支持包含蓝牙、WiFi和NFC等连接方式，并且支持多种如IoTivity的设备对设备互联互通标准;包含安全启动、强制访问控制、加密标准和软件安全更新协议等安全措施;先进的设备管理以及直观的开发工具。

Ostro是一套基于Linux并且为物联网智能设备特别量身订做的开源操作系统，它可以为任意数量的物联网使用案例特别定制功能，包含Linux参考设计、软件包安装和管理机制。除此之外，它的开发工具可以让设备上的连接潜力扩展到最大。Ostro项目不但提供管理众多设备的工具，最重要的是，它能保障物联网世界安全无虞。

Ostro操作系统的适应性非常强，既可直接用于受支持的设备，也可以按照需求进行定制，而且开发环境提供了多种语言选择（Native (C/C++)和Node.js），可以轻松找到新设备的驱动程序，并充分利用Linux社区的所有资源。最后，它还提供了从引导/内核到中间件和应用的自上而下的安全性选项。

Ostro操作系统包含易用的工具，让开发和原型制作都变得容易。它利用Yocto项目的工具组环境来进行操作系统和应用包的配置，开发者可以先创建出一个理想的配置再根据需求修改。当使用基于Linux的开发工具时，对于既有的Linux和安卓开发者，完全不需要额外的学习过程，开发者可以直接用交互编译工具来生成程序。

TinyOS

名称：Tiny OS

网址：暂缺

Tiny OS是UC Berkeley（加州大学伯克利分校）开发的开放源代码操作系统，专为嵌入式无线传感网络设计，操作系统基于构件（component-based）的架构使得快速的更新成为可能，而这又减小了受传感网络存储器限制的代码长度。Tiny OS是一个具备较高专业性，专门为低功耗无线设备设计的操作系统，主要应用于传感器网络、普适计算、个人局域网、智能家居和智能测量等领域。

Tiny OS的如下特性决定了其在传感器网络中的广泛应用，使其在物联网中占据了举足轻重的地位。

相对于主流操作系统成百上千MB的庞大体积来说，Tiny OS显得十分迷你，只需要几KB的内存空间和几十KB的编码空间就可以运行的起来，而且功耗较低，特别适合传感器这种受内存、功耗限制的设备。

Tiny OS本身提供了一系列的组件，包括：网络协议、分布式服务器、传感器驱动及数据识别工具等，使用者可以通过简单方便的编制程序将多个组件连接起来，用来获取和处理传感器的数据并通过无线电来传输信息。

Tiny OS在构建无线传感器网络时，通过一个基地控制台控制各个传感器子节点，聚集和处理各子节点采集到的信息。Tiny OS只要在控制台发出管理信息，然后由各个节点通过无线网络互相传递，最后达到协同一致的目的。

eCOS（GNU）

名称：eCOS（GNU）

网址：ecos.sourceware.org

eCos（embedded Configurable operating system），中文翻译为嵌入式可配置操作系统或嵌入式可配置实时操作系统。适合于深度嵌入式应用，主要应用对象包括消费电子、电信、车载设备、手持设备以及其他一些低成本和便携式应用。eCos是一种开放源代码软件，无需支付任何版税。

它是一个源代码开放的可配置、可移植、面向深度嵌入式应用的实时操作系统。最大特点是配置灵活，采用模块化设计，核心部分由小同的组件构成，包括内核、C语言库和底层运行包等。每个组件可提供大量的配置选项（实时内核也可作为可选配置），使用eCos提供的配置工具可以很方便地配置，并通过不同的配置使得eCos能够满足不同的嵌入式应用要求。

eCos使用了分层式中断处理机制，把中断处理分为传统的ISR和滞后中断服务程序DSR。类似于μClinux的处理机制，这种机制可以在中断允许时运行DSR，因此在处理较低优先级中断时允许高优先级的中断和处理。为了极大地缩短中断延时，ISR应当可以快速运行。如果中断引起的服务量少，则ISR可以单独处理中断；如果中断服务复杂，则ISR只屏蔽中断源，然后交由DSR处理。

Contiki

名称：Contiki

网址：

Contiki系统的名字来自于托尔·海尔达尔的康提基号，由牛津大学研究人员发明。

Contiki是一个适用于有内存的嵌入式系统的开源的、高可移植的、支持网络的多任务操作系统。包括一个多任务核心、TCP/IP堆栈、程序集以及低能耗的无线通讯堆栈。Contiki采用C语言开发的非常小型的嵌入式操作系统，运行只需要几K的内存。

Contiki拥有出色的TCP/IP网络支持，包括IPv4和IPv6，还有6Lowpan报文压缩、RPL路由、CoAP应用层，已经成为无线传感器网络和物联网感知层低功耗无线组网协议研发和实验的主要平台，其中6Lowpan已经成为IETF规范，也被zigbee SEP2.0标准以及ISA100.11a标准所采纳。

BTC Miner

Bitcoin mining is the process of creating new bitcoin by solving puzzles. It consists of computing systems equipped with specialized chips competing to solve mathematical puzzles. The first bitcoin miner (as these systems are called) to solve the puzzle is rewarded with bitcoin. The mining process also confirms transactions on the cryptocurrency's network and makes them trustworthy.

For a short time after Bitcoin was launched, it was mined on desktop computers with regular central processing units (CPUs). But the process was extremely slow. Now the cryptocurrency is generated using large mining pools spread across many geographies. Bitcoin miners aggregate mining systems that consume massive amounts of electricity to mine the cryptocurrency.
In regions where electricity is generated using fossil fuels, bitcoin mining is considered detrimental to the environment. As a result, many bitcoin miners have moved operations to places with renewable sources of energy to reduce Bitcoin's impact on climate change.

Btc Miner,Bitmain S19 Xp,Bitmain Antminer S19 Xp,Antminer Bitmain S19 Xp 140Th

Shenzhen YLHM Technology Co., Ltd. , https://www.hkcryptominer.com