Advantages of embedded software development:

The benefits of developing embedded software are:

(1) people at home and abroad are scarce. On the one hand, it is because this field has a high entry threshold, not only need to understand the underlying software (such as operating system-level and driver-level software ), high requirements on software expertise (embedded systems have high requirements on the time and space efficiency of software design) and must understand the working principles of hardware, therefore, it is difficult for non-professional IT personnel to break into this field. On the other hand, this field is relatively new and is developing too fast, many software and hardware technologies have been around for a short time or are emerging (such as arm processors, embedded operating systems, MPEG technology, and wireless communication protocols). Of course, those who master these new technologies are looking for them. Embedded talents are scarce, and the value is naturally high. The more experienced, the higher the price. In fact, there are few embedded talents. The root cause may be the unconditional contact of most people. This requires embedded development boards and software, and experienced people to guide the development process.

(2) Unlike enterprise computing and other application software, the work intensity of talents in the embedded field is usually lower (but the income is not low ). An IT enterprise engaged in enterprise application software. Once the user's system is finished, the next user has to be created. In addition, the requirements and completion time of each user have to be changed according to the customer's requirements, and they are often exhausted, repeat. In comparison, companies engaged in embedded systems all have their own product plans and act at their own pace. The products developed are generally generic and will not be modified by customers. After a product model is developed, it usually takes a relatively long period of free time (or just a small patching of the software), and it takes time to charge and take off. In addition, the scope of work for each person engaged in embedded software is relatively narrow, and the scope of professional technologies involved is those (ARM, RTOS, MPEG, 802.11, etc ), after a long time, these things will become more experienced, sell old books, and provide some guidance to those who are new to the market for half a year. If you are engaged in application software, it may be hard for the next customer to switch to a completely different software development platform.

(3) If you want to start a business and develop your own products on that day, embedded is a good idea, which is not as easy to be pirated as application software. A company named Qi Xingxing in the Civil Engineering Institute developed a handheld PDA, which seemed to be "engineering e" (there was an advertisement at the entrance of the south campus ), with this PDA, construction technicians can carry out on-site civil budget estimates and other civil engineering calculations. It is said that the sales are very good. A university teacher I know, his restaurant's ordering PDA developed by him (WinCE platform, wireless connection and Internet access). According to him, the sales volume is good. The restaurant's PDAs let customers order food, multi-explicit assignment class. I remember a group of students in class 00, Class 2 and class 2 designed a functional ordering system with VC ++ for the Windows Programming Course, at that time, I really wanted to advise them to make the software into a PDA, and it was estimated that there would be some sales (Macdonald at the South Square of Shanghai Railway Station used a very beautiful PDA to order food for users, as if they were decent ). The hardware design of these PDAs is generally customized by other companies (this is called "OEM": OEM). They are all general-purpose hardware. We just need to design the software and turn it into our own product.

Disadvantages of developing embedded software are:

(1) The entry point is relatively high, and the technologies used are often difficult. If the hardware and software foundation is poor, especially the operating system software skills are not deep, it may not be suitable for this trip.

(2) The number of enterprises in this field is much smaller than that in enterprise computing. In particular, there are a large number of embedded small enterprises (small enterprises need to start their own products ), few well-known large companies (mainly engaged in Embedded companies include Intel, Motorola, TI, Philip, Samsung, Sony, Futjtum, Bell-Alcatel, Italian FA semiconductor, Microtek, inhua, Huawei, ZTE, radio and television, and other manufacturing enterprises ). These enterprises are used to finding people in hard fields such as electronics and communication. Since our college graduates are mainly engaged in enterprise computing, our college has less contact with these enterprises. Our hospital is actively working hard and has established contact with its central branch office to seek internships or employment in these enterprises.

(3) There are a few companies that often require masters or above to engage in embedded systems, mainly based on the difficulty of embedded systems. But most companies do not have this requirement, as long as they have experience.

If we study embedded systems, we should focus on embedded software, especially embedded operating systems. For people engaged in embedded software, the most important technology is obviously (in fact, many companies write such advertisements ):

(1) master the structure and principle of mainstream embedded microprocessor

(2) An embedded operating system must be mastered.

(3) be familiar with the embedded software development process and have worked on at least one embedded software project.