Windows CE Learning Process

Process, windows, learning
Learning plan:
1. Application Design:
This part is necessary for understanding. After all, you need to write the driver test program yourself.
Because it is mainly to learn the underlying development, this part does not take too much time to understand the Win32 architecture.

Time: Two weeks! The time may be a little short, but it may take a little longer to get started with wince. After all, most of them are familiar with this part.
Reference books: Windows CE 6.0 developer reference

2. Arm architecture, ADS usage:
As a basic knowledge, it is necessary to understand the ARM architecture. Since you are engaged in embedded development, at least you need to be familiar with these things. The use of ADS is of great significance for familiarity with the underlying software. You can directly operate the hardware here! This part serves as a key basic knowledge!

Time: one month! This is not a long time. I hope you can go back and study this part when you encounter any difficulties. I think it will have better results.
Reference books: 1. Arm Architecture Reference Manual
2. Arm system developer's Guide

3. bootloader Startup Process and wince Startup Process Analysis:
This part is a key learning plan, especially the boot process of bootloader, which helps us to understand the startup process of the entire system. This part is difficult, so it may take a long time.

Time: about 2-3 months!
Reference Book: Windows CE embedded system he Zong key

4. bootloader transplantation and kernel transplantation:
This Department is required if you want to build your own operating system. There are many components in wince. in this department, we also need to be familiar with the usage of these components. This part is a very hands-on part, and may encounter many difficulties in debugging.

Time: 1 month!
Reference books: There are a lot of online materials. You can check them yourself.

5. Driver architecture and stream Driver Design:
Here we need to learn about the entire driver architecture and Driver Design. If the stream driver program is used, we can try to write some simple drivers, such as the serial driver.
Time: 1 month!
Reference Book: Windows CE embedded system he Zong key
Windows CE driver and BSP development guide

6. Layered-driven Learning:
Layered driver. This part shows a detailed example. The display driver may be used as a learning process. This part is a little complicated.

Time: 2 months!
Reference Book: Windows CE embedded system he Zong key
Windows CE driver and BSP development guide

7. Challenges:
TBD! You can also make any good suggestions!

Advanced topics:
1. operating system principle, Windows CE operating system principle:
This part requires you to master a lot during your work and I think it is essential to become a master. Linux has a lot to explain in this regard, but there is little information on wince. We need to learn by ourselves.
Time: unlimited!

2. Computer composition principle and Hardware working principle.
Embedded Software Development can't avoid looking at the circuit diagram, so this part has the best understanding. If you want to become a master of both hardware and software, this part is even more necessary.

The entire process is less than a year old. I hope everyone will stick to it. In fact, this process does not have to be done in this way. You may be exposed to these things earlier in your work. But I also hope that you can share with us what you learned at work. Help everyone, day up! I also hope that experienced people can share your learning experience with you.