Write it to a beginner like me-Write the wince single-layer driver process (Author: wogoyixikexie @ gliet)
To be honest, I have been using wince for half a year. I have never written a driver from start to end (I blushing) because I just got started, and this Samsung BSP is also quite complete, we usually just fill in the blanks under the original function (I guess many people do ). However, a good learner usually wants to learn from each other. In order to make up for my mistakes, I am now studying this important course on the occasion of Wince for six months. I hope more people can see it and learn it together.
I cut a lot of images and made comments during the process. Haha, just upload the film now.
Step 1: Create the simpledriver folder under the driver folder of BSP
----------------------------------------
The following describes how to add files such as dirs, sources, and source code. For details, refer to the online method. I will not go into details here.
________________________________________________________________________
_________________________________________________________________
Then, the simpledriver folder will appear in the FileView tag, and the code will be displayed. Use the mouse to quickly compile the driver.
Please refer to this post for detailed operation method http://blog.csdn.net/gooogleman/archive/2008/12/26/3613752.aspx
__________________________________________
After compilation, the corresponding DLL is generated under BSP, for example.
______________________________________________________________
Execute the copy operation and copy the corresponding DLL to the following folder. You just need to package and download it.
_______________________________________________________________
[HKEY_LOCAL_MACHINE/Drivers/builtin/simpledriver]
"Index" = DWORD: 0
"Prefix" = "SPL"
"DLL" = "// simpledriver. dll"
"Order" = DWORD: 0
_______________________________________ Is not finished yet, to be continued. I'm off duty. I'll try again tomorrow.
I was going to write a common driver writing method, but I think it is more worth learning to use the driver debugging assistant to dynamically load the driver, saving you the trouble of downloading the kernel all day, making the USB unstable and returning the blue screen, I really want to thank the author of the driver debugging assistant. Let's do it as follows:
Tutorial: http://www.cnblogs.com/we-hjb/archive/2009/01/19/1250838.html#1435015
The driver is the EXE file of the assistant. I have verified that it is feasible. Dnw output information after the driver is activated.
The driver debugging assistant is very convenient. Currently, it can only be used to debug the stream driver. What should I do if I debug the local driver? I want to find a solution. I will study it again later.
Complete!
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.