Windows Embedded ce 6.0 initial development experience (3) set boot-loader favorites

In the previous article "Windows Embedded ce 6.0 initial development experience", "ce Development Environment ":

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

 

Boot-loader and a CE 6.0 system have been preset in the digi CC 9p Development Board. Therefore, we can directly start the development board to run an ce 6.0 operating system. However, our ultimate goal is to develop a CE 6.0 platform, so we need to set some system variables in boot-loader.

 

Boot-loader is equivalent to the BIOS in the PC. After the hardware is reset, the first command is boot-loader. Boot-loader first initializes the hardware and then guides the operating system to run. Boot-loader is very important in embedded development.ProgramBecause it is closely related to hardware devices, the development of boot-loader is completed by hardware vendors, and it is also part of BSP. This also determines that different hardware vendors have different implementations for boot-loader. Here we take digi as an example. The settings for boot-loader are only valid for the digi Development Board. If you use development boards from other vendors, refer to the relevant instructions.

The digi Development Board supports outputting a command line from the serial port to control the boot-loader behavior and set some environment variables. Therefore, we need to use the "Super Terminal" to set it.

 

Connect the serial port of the Development Board to the serial port of the development machine. If there is no serial port, a USB to serial port converter is required. The main idea is that hypertrm.exe and hypertrm. dll can be copied to Vista from Windows XP.

After creating a new connection, enter the connection name and select the COM port.

 

Set the serial port baud rate to 38400, data bit 8, no parity check, stop bit 1, data flow control none. Click OK to go to the main interface of the Super Terminal.

 

Make sure that the power supply of the Development Board is correct and the connection to the PC serial port is correct. Enable the power supply of the Development Board. Boot-loader outputs command lines from the Super Terminal. If we do not intervene, boot-loader will start the CE 6.0 System in Flash ROM. To set environment variables, We need to interrupt the startup process. When the command line prompts "hit any key to stop autoboot", we press any key and a command line prompt will appear.

In the command line, enter:

Setenv ipaddr 192.168.0.150

Setenv netmark 255.255.255.0

Setenv serverip 192.168.0.198

Saveenv

The first sentence is to set the IP address of the Development Board, the second sentence is to set the subnet mask of the Development Board, and the third sentence is to tell the Development Board that the IP address of the development PC. If you do not know the IP address of the development PC, you can enter ipconfig in the command line. Because we connect the development PC to the Development Board with a router with DHCP, the router automatically sets an IP address for the development PC. Finally, call saveenv to write the system settings to flash.

To restart the Development Board, enter reset in the command line. When the "hit any key to stop autoboot" prompt is displayed again on the Super Terminal, do not press any key to start the CE operating system built in the Development Board.

After the CE 6.0 operating system is running, the display displays the following screen:

 

To determine whether the network connection between the Development Board and the PC is correct, enter "http: // 192.168.0.150" in pc ie, that is, the IP address of the Development Board. The IE browser will access the web server in the Development Board. If the following figure is displayed, the network connection is correct.

 

After the Development Board is set up, we can perform our own development work.

Next article "Windows Embedded ce 6.0 initial development experience": "run an application first ":

Http://blog.csdn.net/aawolf/archive/2007/10/19/1833230.aspx

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/aawolf/archive/2007/10/15/1825702.aspx