skywalker_lee

It's a long story to talk about embedded operating systems. I have been using embedded operating systems for 12 years. Now, except for special low-power environments, all my development projects are basically based on the system for architecture development. The people above seem to have come into contact with many types of systems, which shows that they have worked on many projects along the way, which is admirable.

The development of embedded systems can basically be summarized into two categories: embedded real-time systems (often called RTOS) and embedded modern systems.

Embedded real-time systems: FreeRTOS, ucOSII, ucOSIII, DSP/BIOS, RT-Thread...

Embedded modern systems: Linux, WINCE, IOS, Android...

These two categories have their own advantages and disadvantages, from the usage scenario, from the CPU platform, from the resource requirements, from the scheduling mechanism... and so on. I think no matter from which angle, a special topic can be opened to explain it clearly. O(∩_∩)O~

The moderator collects this kind of information and may want to open a section specifically for discussing operating systems.

I have done technical support in several communities before, so I have some experience in this area. Let me give you some personal advice.

If we talk about embedded programming alone, this question is too general, because this topic is too broad to be summarized. I suggest that the moderator start from these aspects, and set up sections for several popular operating systems. The focus of each section can be to highlight the key features, for example:

For example, the release and discussion of RTOS porting on different CPU platforms can solve many big problems for novices, because a stable and well-ported version is indeed very important for project development, and novices lack experience in this area.

There are also test codes for some system API functions and analysis of implementation principles to help novices quickly master the usage features of the interface.

You can even summarize and explain the configuration options of common systems, which is lacking in many systems, especially newer versions, because many Chinese instructions cannot keep up with the update speed of system versions, and the instructions of new versions are not detailed enough.

If there are more experts in the section, we can directly initiate the translation of the system data manual. This is a problem that most domestic developers will encounter. After all, there are many developers who have rich practical development experience but low English proficiency. This can definitely help them get started quickly.

In short, the section can start with simple and common problems. Because in the operating system, even the commonly used basic interface functions, if discussed from the perspective of the underlying implementation details, no matter how high or low the level of the participants is, they can gain new understanding and gains from various angles.

By the way, if the moderator needs technical support, I am also happy to provide my limited personal experience. ^_^

高进

skywalker_lee posted on 2019-11-22 16:57 Speaking of embedded operating systems, it's a long story. I have been using embedded operating systems for 12 years. Now, in addition to special low-power environments...

Great. I will write down your ID. Please support this version in the future.

liupk

I am currently preparing to learn rt-thread. I hope there will be more information on this topic on the forum.

kangkls

RT-Thread is a bit troublesome to use, it is just not very convenient. UCOS is open source but charges a fee, which is an extra cost for companies. FreeRTOS combined with CubeMX is trouble-free, convenient and simple. For me, it crashed after adding an SD card and file system, and the problem has not been found yet.

liyiui

The real-time operating system (RTOS) was the first system I used. I studied it for a while. At that time, the MCU RAM was small. I felt that it was still very useful at the time, but there were many calls, and it didn’t feel very convenient. Now the MCU RAM is large and the functions are very powerful, and there is no need for an operating system.

sblpp

FreeRTOS is good, and rt-thread is also good.

I have reservations about writing your own operating system. It is very difficult to promote it. . .

It is possible to make upgrades and improvements based on existing ones.

pingfan1969

From the application perspective, it can be divided into general-purpose embedded operating systems and special-purpose embedded operating systems. Common general-purpose embedded operating systems include Linux, VxWorks, Windows CE.net, etc. Common special-purpose embedded operating systems include Smart Phone, Pocket PC, Symbian, etc. According to real-time performance, it can be divided into two categories: Real-time embedded operating systems are mainly oriented to control, communication and other fields. Such as WindRiver's VxWorks, ISI's pSOS, QNX and Nucleus of QNX System Software. Non-real-time embedded operating systems are mainly oriented to consumer electronic products. Such products include PDAs, mobile phones, set-top boxes, e-books, WebPhones, etc. For example, Microsoft's Smart Phone operating system for mobile phone applications.

ICANUP

I am a newbie, I don't know much about this, I have only been exposed to Linux, I come here to learn from the experience of the masters, and I am ready to move in this direction in the future

wangjiantao918

I have relatively little contact with embedded systems. The one I have most contact with is DSP, mainly TI's products. I have done programming and debugging to meet my own requirements.

szjm-slm

So far, I have only come into contact with MQX and MQXLite

Currently learning RT-Thread

btty038

I know, but I can't. What should I do?

高进

btty038 posted on 2019-11-23 23:19 I know, but I don’t know how to do it. What should I do?

The purpose of this activity is to gather a group of people to discuss embedded systems together in the future. If the moderator is interested, you can also follow it. I think ordinary embedded systems are not much more difficult than using Windows, but most people think they are useless and are unwilling to learn about them.

Evans_li

I am currently learning ucos, it is very easy to use and the code is very neat

foxpro2005

When I first came into contact with OS, I started learning from uCOS, but later I mainly used FreeRTOS.

Later, I came across the famous domestic RT-Thread and was ready to give it a try, but I found it too difficult to get started. It might be because I had no Linux foundation (their style tends to be Linux). In short, I was still blocked from the door.

mh_y

I have always wanted to learn how to operate embedded systems, but I have hardly used the products I have developed since graduation. During my internship, I extracted a small operating system OSAL from the ziggbee protocol and ported it to STM32. Later, I also ported FreeRTOS, UCosII, etc. However, I was limited to porting and had no idea about the internal things. I was very depressed. Now I want to try Linux.

hjl2832

Embedded operating system (RTOS) operating system, I have been exposed to μClinux, the system on the fingerprint attendance machine of the previous company, and the application of S3C44B. At that time, the system was transplanted based on the design company's transplantation. My own application was just added, subtracted and modified, and I was not very familiar with it. Later, when I was working on a new energy project, I transplanted μC/OS-II myself. I followed the user manual to modify and transplant step by step. At that time, I felt that after using RTOS, the product functions were indeed stronger. The biggest feeling was that the multi-task real-time that was a headache before the system became very easy to use. Then in order to learn Vxworks and Linux, I bought 2440 and development board by myself. After running all the routines, I didn't go deeper. Until today, I haven't used it in the project. My current work is mainly based on embedded applications of ordinary single-chip microcomputers, so FreeRTOS and RT-Thread are the most used now. I personally think μC/OS-II is very good, but commercial applications require authorization.

Currently, RT-Thread may be the most discussed system in China.

qditz

Currently, the most commonly used embedded operating system is Linux, and other common ones include: VxWorks, Windows CE, Palm OS, C/OS, etc. In addition to the functions of task scheduling, synchronization mechanism, interrupt processing, file processing, etc., the overall characteristics also have some characteristics. Strong real-time performance; support for open and scalable architecture, with scalability; provide a unified device driver interface; provide easy-to-operate, simple, and friendly graphical GUI and graphical interface; support TCP/IP protocol and other protocols, provide TCP/UDP/IP/PPP protocol support and a unified MAC access layer interface, and provide powerful network functions; the user interface of the embedded operating system provides services to user programs through system call commands; once the embedded system starts running, it does not require excessive user intervention; the embedded operating system and application software are solidified in the ROM of the embedded system computer; it has good hardware adaptability (portability). For embedded system programming, first of all, you need to master basic debugging skills, which are key skills required to work on small embedded systems; secondly, you need to have a good understanding of interrupts and monitoring of internal and peripheral devices of the chip; determine whether there are real-time requirements and whether your operating system and application can meet these requirements; thirdly, implement task synchronization in the real-time operating system and embedded Linux; and finally optimize the size, running speed and energy consumption of embedded software. If you can master these points, you can do well in embedded programming.

fesns

I first learned freeRTOS and developed several projects

I also studied Linux for a while but didn't stick with it

Bingqi23

Since I am engaged in the research and development of in-vehicle navigation, I have been dealing with real-time operating systems. When I just graduated and joined the company, it happened to be the development of a derivative model of a mass-produced model, which used an OS developed by the company itself. It was small, fast, and very comfortable to use. As a result, I still use this environment on general platforms. After that, I came into contact with Japan's Itron the most, which is the best choice for MCU. After that, I came into contact with AutoSar and developed a model. Then there is Linux, and the kernel is configured in real-time mode. Now I am developing the Android platform, which has nothing to do with real-time...

bingdongshijian

Before, I had been running programs on bare-metal microcontrollers, which was enough for general projects. I had developed some cumulative thermostats, counters, and air disinfection equipment. I also worked on IoT terminals and communications. I got in touch with the Linux embedded operating system and transplanted the system by following the learning video. The chip was based on Samsung. The biggest feeling was multi-tasking, which was quite convenient and easy to use. It was also from that period that I gradually imitated the kernel program and started programming in object-oriented languages. Although the readability was poor, the portability was quite high.