Step 1 -- establish the wince Development Environment

Starting from today, we have developed some wince programs and some DirectShow programming under wince. After studying for a whole day, we finally established the compiling and development environment.

 

1. Unlike LINUX embedded development, WinCE development requires several support platforms. The first is platform builder, which is an online debugging tool specially developed by Microsoft for developing wince. Using Platform builder, We can customize the wince Kernel on our product and support kernel-level debugging, just like Linux's munuconfig during kernel compilation. At the same time, developers can also develop the driver under wince here. Well, driver development has always been an embedded advanced technology, and it seems that only Daniel can complete it. It is said that it is very profitable. Haha. Back to the question, we can use platform builder to create our own development kit and install it in the PC. During each software development, we directly select this BSP, saving a lot of configuration work. Linux should be learned at this point.

 

Platform builder is updated to pb6, and many development boards are built by pb5. In order to ensure no compatibility errors, I have to select pb5.0. However, you can only download pb6 from the official Microsoft website. Now, you can only download pb6 from the donkey.

 

2. There is a prepared development kit in the CD of the Development Board. For the application software development of wince, as long as there is a BSP development kit, you can directly use another software EVC for application development. The EVC style is very similar to that of vc6. In MFC development, most vc6 methods can be used. The process of installing EVC is very simple. You just need to "Next. In the middle, you can select full installation.

 

After installing EVC, install the corresponding patch, and then install the development kit developed by pb5. We will discuss how to create the pb5 Development Kit and how to customize the system. During installation, there is an option in the middle to select the arm version corresponding to your own development board CPU, and my version is Samsung smdk2440: armv4l. After installing BSP, you can try to build a project for compilation. The compilation is successful.

 

3. Set the synchronous communication between the Development Board and the PC. The program compiled on the PC is directly downloaded to the Development Board through the network port. In Linux development, you can write a copy program to an NFS file in the PC makefile, but you must use the command line of the Development Board to run and debug the program. Install the synchronization software ActiveSync under XP, and then install the USB driver for wince synchronization. the USB port of the Development Board is connected to the PC, and the network cable is connected to the PC, at the same time, set the IP address of the Development Board and PC to a LAN. Now the PC communication work is ready.

 

Configure EVC communication, Click Tools> configue platform manager, select bsp of the development board, click property on the right, and set in the pop-up dialog box. Under transport, select TCP/IP transport and click configuration on the right side. You do not need to set it. Press OK. Under startup, select Microsoft ActiveSync and press test. If everything is correct, the connection is successful.

After the configuration is complete, click Run at each debugging, And the compiled program is automatically transferred to the Development Board for running.

 

I have always had a question: Serial Port + network cable + USB is required for Linux, WinCE, or VxWorks development. Generally, at least two interfaces are required, but why can't I write a program on the PC host, write another program on the Development Board, and communicate with the two programs? Only one interface can be used to download and debug the program and control the command line. After all, many computer serial ports are inconvenient, and there is only one network port, and developers often have to query problems online at any time. If there is such a method that only the USB port is used, it is much more convenient.

 

You cannot use ActiveSync in Windows 7, but you can use the Windows Mobile Device Center tool with the same functions.

 

Now you can use vs2005 or vs2008 to replace EVC. In vs2008, when creating a project, there is an option that is smart device. This is the project used to develop the wince project and Windows Mobile. In this case, select the BSP package for your Development Board.