The "embedded development process" in the previous article "Windows Embedded ce 6.0 initial development experience ":
Http://blog.csdn.net/aawolf/archive/2007/10/10/1818866.aspx
Ce Development Environment
Next we will make the main character debut today-digi CC 9p Development Board. To thank digi for providing the Development Board, let's make an advertisement for them: This is a company that focuses on WiFi-related products and also produces the cpu Of the ARM architecture, so the Development Board is also part of their company. The general feeling is pretty good. If you are interested, you can visit http://www.digiembedded.com/to learn more about digidashboard.
This is the real-time photo of the digi Development Board. Thanks to my et900, the effect is not bad:
DiGi CC 9 p Development Board
We can see from the figure that the LCD screen is not attached to this development board, so we need to connect to a monitor through VGA output, the blue interface above the figure is VGA output; the left interface is from top to bottom, they are: DC power supply, RJ45 Ethernet interface, RS232 serial port, and the right side is also connected to my tested mouse :)
Because the device environment variables and commands such as starting eboot need to be sent to the Development Board through serial port, we need to connect the connection development board to the PC serial port through serial lines. Because my notebook does not have a serial port, I use a USB to serial port converter, and everything works properly.
After compiling the platform, the image file (NK. Bin) needs to be downloaded to the ram of the Development Board through a network cable. The advantage of using a network cable is that the speed is faster. There are two ways to connect a network cable: directly connect the PC to the Ethernet port of the Development Board, which is also the lowest cost, is to use a router with DHCP function, the PC and the development board network cable to connect to the router. In actual development, I chose the latter method because the router is better than the direct connection network cable ......
After the hardware connection is complete, we will discuss the installation of the development environment. The entire process may take several hours, but this depends on the specific machine.
The digi CC 9p development kit contains the 2005-day verification version of Visual Studio 6.0 and platform builder 180. During the installation of Pb, enter the key. This key can be obtained through registration on the Microsoft website, the registration address is as follows: http://www.microsoft.com/windows/embedded/eval/getregistration.mspx
After Visual Studio 2005 is installed, we should first install VS 2005 SP1 and then install Pb 6.0. After all, PB is used as a plugin in VS 2005. Next, you also need to install Pb 6.0 SP1, which can be downloaded on the Microsoft website, as follows:
Http://www.microsoft.com/downloads/details.aspx? Familyid = BF0DC0E3-8575-4860-A8E3-290ADF242678 & displaylang = en
After VS 2005 and Pb 6.0 are installed, we should also install the digi resource CD.
We should first install the digi 9p BSP, which contains the boot-loader and driver related to the Development Board.Program. That is to say, digi has already helped us in the "driver development" section we mentioned earlier. We need to focus on "platform Customization" and "Application Development ". Of course, if you need to customize boot-loader, you can also choose to Install Boot-loaderSource codeAnd the GNU x compiling environment. There is no uniform development environment for boot-loader development. hardware vendors often choose different development tools for development based on their own needs, such as arm SDT and other development environments. DiGi uses gnu x, probably for compatibility with embedded Linux?
After the software and hardware are installed, We can customize the CE platform. How is it? It does not seem very difficult.
In the next article "Windows Embedded ce 6.0 initial development experience", "set boot-loader ":
Http://blog.csdn.net/aawolf/archive/2007/10/15/1825702.aspx
This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/aawolf/archive/2007/10/11/1820278.aspx
This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/aawolf/archive/2007/10/11/1820278.aspx