Windows Embedded ce 6.0 initial development experience (7) Compilation and debugging platform favorites

Previous "customized platform" in Windows Embedded ce 6.0 initial development experience"

Http://blog.csdn.net/aawolf/archive/2008/01/12/2039866.aspx

After selecting catalog, the customization of the platform has come to an end. Next, we will go to the "Compilation and debugging" platform, the most variable. Compilation is simple, but there are many variables to compile.

The first step in compiling the Platform is to select the debug or release version. Select Configuration Manager from the build menu. In the displayed dialog box, select debug or release. As shown in red circles:

 

Select "build solution" in the build menu to start platform compilation. The compilation time varies depending on the performance of the Development machine, from several minutes to several hours. If the compilation fails several times, it is indeed a crazy thing ......

Until we see the output below in the output window, it means that you have completed the compilation and debugging of the image file.

 

After compilation, we can download the image file to the Development Board and start debugging. This process is also complicated. Before the first download, you must create a device for download in Visual Studio. The specific process is as follows:

Step 1: Select connectivity options from the target menu to open the connection Options dialog box:

 

Step 2: Select "add device" in the dialog box and create a new device named "mytarget_debug". This name has no restrictions and can be named by any name. In the "associated OS design/SDK" option, set it to "NONE ".

 

On the target device setting page, make sure that "downlaod" is set to "Ethernet", that is, Ethernet. Click the "Settings" button.

 

When developing on Vista or XP, a security warning will appear. Click "unlock" to select. Otherwise, the call will fail.

 

The "Ethernet download Settings" dialog box appears, for example:

 

At this time, we need to set the Development Board through the Super Terminal: power off the Development Board, confirm the serial port connection, and the Super Terminal is connected, turn on the power. When the Super Terminal prompts "hit any key to stop autoboot", Press any key to stop the automatic loading process. Then input the following in the command line:

Dboot eboot flash

Dboot is a boot-loader developed by digi. This command enables eboot in Flash ROM. We know that eboot allows ce image to be downloaded to the development board over Ethernet. After starting eboot, the NIC driver will be initialized first to ensure that the NIC is available, and then the bootme message will be broadcast to this segment. Therefore, when setting IP addresses for the development machine and the Development Board, you must note that the two must be set as IP addresses within the same network segment.

If the eboot starts successfully, a new device is displayed in the "Ethernet download Settings" dialog box in Visual Studio of the development machine. Select this device, the device name is displayed in the drop-down menu above.

Return to the previous dialog box, click "Apply", and then click "close ". Close the dialog box. In this case, our development board is mapped to the target device named "mytarget_debug.

Note that the above operations only need to be performed once for each Development Board. The device does not need to be added again when debugging is required for the second time.

Return to the main interface of Visual Studio. You can select the "Attach device" command in the "target" menu, or select the icon on the menu bar to perform the same operation. Example:

 

Next, the following dialog box is displayed, which downloads the built image file to the Development Board. Note: First, if the server IP address (that is, the IP address of the development machine) on the Development Board is not set correctly, the dialog box will appear, but the download will not start for a long time, always waiting for response;

Second, the downloaded image file will be stored in the memory of the Development Board. Therefore, if the development board loses power, the downloaded image will be lost. Therefore, this process is only for debugging. If you want to burn the image file to the Development Board, You Need To perform other operations.

The entire download process may take several minutes:

 

After the download is complete, the real debug process starts. Due to debug, the operating system of the entire development board runs slowly. Therefore, do not mistakenly think that this speed is the normal running speed of the Windows CE platform.

During system startup, execution may be interrupted in several places, which is caused by the macro of debugcheck, probably because a driver in the Windows CE system calls the BSPProgramBut it does not affect the normal operation of the system. So we can directly press F5 to continue running.

Conclusion
Here, we have fully explained the development process of Windows Embedded ce 6 and 0. If you do not have a development board, you can use the device emulator method to develop the CE 6.0 platform.

Call, and finally fill out this pitfall before the New Year. Wish you a happy New Year and fill in another trap in the future:

XP embedded development experience

Http://blog.csdn.net/aawolf/archive/2007/11/11/1879406.aspx

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/aawolf/archive/2008/02/03/2079664.aspx