How do I practice writing drivers and developing BSP after I buy a development board? (Author: wogoyixikexie @ gliet)

How do I practice writing drivers and developing BSP after I buy a development board? (Author: wogoyixikexie @ gliet)

How do I practice writing drivers and developing BSP after I buy a development board? (Author: wogoyixikexie @ gliet)

---------- A newcomer asked questions at the csdn Forum

Recently I want to buy a 2440 Development Board. To learn about embedded development of wince, I still have a few questions about whether the driver included in the Development Board can be used directly, can I directly allow the hardware to run smoothly under wince? If yes, I want to learn about wince driver development. What can I learn when I buy a development board? How does the code run? If not, do you need to make some modifications to the drivers that come with them to run under wince? What kind of changes are generally required?
What can I do with the Development Board to improve my development-driven capabilities? Let's talk about your opinions !!!

------------------------------------------------------

Is the moderator there? Stick this to the top and refine it. This question seems to have been asked by many people. Let's work together and express our own opinions. Let's get a post for the benefit of new people.
Too many new people are confused .........
---------------------------- My suggestions
The purchased BSP driver can be used directly, and only a few exist in the form of DLL.
I think C, C ++ and Assembly knowledge should be prepared before learning this thing.
Step 1: Look at the bootloader code: the bootloader code includes assembly and C, some of which are a little c ++; the bootloader contains many register setting methods on the platform;
I can't understand the information, read the manual, and I will gradually consolidate the compilation, C, and C ++. Bootloader is still streaking, and it is easy to learn. This is the reason from here.
Step 2: start to write drivers, petabytes of help documents, visit forums, and other people's blogs. Learn about some configuration files of wince, such as BAT, environment variables, sources, and Def files.
Familiar with the development-driven process of wince, single-layer -- Multi-layer PDD/MDD
Step 3: Understand the wince architecture, bootloader --, oal --, kernel --, filesys --, and so on.
The most important thing is that it is fun to help others in the forum. You can also meet more people (teachers and friends) and broaden your horizons.
I am a beginner. I don't know if it is correct. I hope it will help you. A wrong message is reported. Haha.

------------------------------------------------------

Reference the reply from shuiyan on the 4th floor:

If you buy a Development Board, you will certainly be able to directly run the system. Otherwise, you will be embarrassed to sell it.

If you want to learn BSP, you can see if anyone else can help. No one wants to learn by themselves, so they have to start from 0 on the first floor. There are many things. Take a look and be patient.

For help, you can skip the following steps: directly write a stream driver, load it as a DLL, and then write a small application in the system to open and operate. In this way, the progress is very fast. It takes about half a day to see the results in at most one day.
With the jump, we will gradually expand to learn how drivers are integrated into system images, how to start and load the system, and how to understand the processes...

Shuiyan's method is fast and recommended. You just need to find someone you are familiar.
(:-...... I did what I wrote, because I didn't teach anyone, I didn't have a document, and I kept reading books and visiting forums.
I have been aware of it for half a year.

Reprinted please indicate: Author wogoyixikexie @ gliet. guilin University of electronic science and technology, a Department of Science Association, the original address: http://www.cnblogs.com/wogoyixikexie/ (or my blog in csdn: http://blog.csdn.net/gooogleman) -- if there is a mistake, hope to leave a message to point out; if you have a better way, please leave a message after your blog. I will be grateful for your criticism and sharing.