I am dedicated to embedded beginners who are dedicated to knowledge

We are dedicated to embedded beginners who are dedicated to knowledge. Master Additional discussions.
Practice is of course the best way to train students, but I think there are very few opportunities for students. Not to mention undergraduates and masters are not necessarily qualified. Therefore, I want to learn embedded systems based on my personal knowledge background and actual conditions. Set an appropriate stage goal and start thinking more with the conditions allowed.
In general, there is a shortage of hardware devices. However, we can work hard on software and embedded system development models to remind everyone that there is a lot of knowledge about embedded system development and design, so don't mess up, after learning about the architecture of embedded system development, the easiest way to get started is Linux C, such as UCOS (with open source code ), although it may not be possible to simulate on the hardware, do not worry. Wince and palmos are easy to use. For beginners and self-righteous masters, the programming level (which is not limited by hardware conditions) is absolutely endless, with a high level of programming (embedded mainly C, of course, the OO language C ++ and Java are the development trend). When you have the opportunity to supplement hardware knowledge in time, you will soon become a master.
Also, remember to learn embedded systems. "Find a solution and don't look for reasons." When TC programming was used in DOS, the building is a miracle.
I recommend a development path for your reference only,
1. c development experience
Condition: Linux (this is all available)
Method: casually, mainly to understand ansic programming (excluding GTK, QT, and other graphical Visual Development)
2. Network, Operating System , Architecture
Condition: Linux, various books, algorithms, and routines.
Method: C programming is used to implement knowledge algorithms and processes such as simple networks.
3. Embedded System Concepts
Conditions: various embedded websites, discussion groups, books
Method: Do not ask questions (especially when the sky is falling, this is mainly to prevent growth of inertia, but also cannot solve the actual problem) and think more.
4. embedded development practices
Condition: the demo version (or dversion, if any) of various embedded system development tools, including compilers and simulators. You can search for them or download them.
Method: There are two branches: one is the development of embedded systems based on MCU/DSP, and the other is the development of application software under RTOS such as palmos, WinCE and UCOS. If you are interested in hardware and want to become a real master, you can start with the first branch and enter the second branch later. If you are bored with hardware, you just want to stay on software development, you can start with the second branch, and there will be no essential difference between it and PC development in the future. It is no problem to find a good job. You don't need to take the following steps, for more information, see section 6th.
5. hardware development
Conditions: various embedded chips, memory and other circuit devices, protel99 and other Circuit Design Software, Board making .
Method: At this time, there should be development conditions, at least 51 series, which is more convenient. The design of the circuit is much more, but it seems scary. In fact, it is much simpler than the software. As long as you work hard, practice will tell you everything.
6. hardware engineering/software engineering/project management
Requirements: detailed information and use experience of each chip, software engineering knowledge, project management knowledge, training, and experience in large-scale project participation
Method: it is already a master, but there is no end to learning. It is fatal to be complacent about the existing knowledge. The next step... you should be the manager.
 
From my experience, you are welcome to ask questions from beginners.
For the sake of technology, all the way crazy...
 
Let me add a few points.
To become a master, you 'd better study the following fields:
1. Analyze the source code of a RTOS-UCOS is the easiest;
2. Analyze the implementation method of a communication protocol stack-TCP/IP is the most practical;
3. proficient in a DSP Development and Integration Environment-Ti ccs2.1 is the best, with the essence of RTOs in it;
4. proficient in one type Single Chip Microcomputer Development Integration Environment -- Keil C is the most classic;
5. proficient in a development and integration environment of MCU-ADS 1.2 is the most popular;
If you want to become a master, you can start practicing in the following fields:
1. proficient in a System Modeling Language and tool-telelogic Tau SDL/UML suit is the most classic;
2. proficient in an algorithm simulation tool-Matlab Simulink is the cheapest;
To check whether you have reached the premium level, you can do the following:
Build a prototype system for infrared or Bluetooth communication, and use the ready-made analog front-end, baseband DSP, and 32 bmcu as the main control, and DSP and protocol software. Of course, it cannot be complete. Just make a subset.
If you can reach this point, stop it. It's time to switch to the market. It is a waste of time to create a market for one or two years.