Windows Embedded compact 7 initial experience

Source: Internet
Author: User

Windows Embedded compact 7 has been out for more than half a year and has no time for it. Recently, it has a refresh version, and the computer has another 1 TB hard disk, So download it and try it out.

Let's talk about how to build the development environment. Platform Builder 7.0 is used as a plug-in for vs2008 and is not compatible with all previous versions of the wince development environment. It must be installed independently. Therefore, follow these steps to build a wince7.0 development environment:

    • Install vmware workstation 7
    • Install Windows 7 on a virtual machine
    • Install vs2008 and SP1
    • Install Windows Embedded compact 7

I used to learnWhen learning the new version of winceIt is based on the simulator to create a system, but wince7.0 currently does not support device emulator, probably because it only supports armv5 and later processors, while device emulator is still armv4. Currently, the project uses the arm11 processor, which belongs to armv6, So we plan to transplant it directly to this platform.

New Features and porting instructions for wince7.0 are provided in the installation directory in PDF. According to the documentation provided by wince6.0, porting from wince6.0 to wince7.0 is relatively simple. Wince5.0 to wince7.0 may be difficult to transplant. We recommend that you first port wince5.0 to wince6.0, and then from wince6.0 to wince7.0.

Currently, the project uses wince6.0, so we can use 6.0 BSP as the template for porting. The porting method is similar to the introduction of S3C2410-WinCE6.0-OAL quick debugging. Copy the BSP of 6.0 to the platform directory, then clone a new BSP through platform Builder 7.0, modify the corresponding item attribute in the catalog file, and change armv4 to armv6. In addition, modify the platform. bib and platform. Reg files under the files directory to clear the contents of these two files. Modify the dirs file in the src directory to remove the directory corresponding to boot and drivers. The purpose of this operation is to quickly port the oal of wince7.0, first run the kernel of wince7.0, and then slowly transplant various drivers.

The method for creating a project in wince7.0 is similar to that in wince6.0. Create a project based on the custom device template and set platform properties. Because the BSP kitl has never been verified on 6.0, kitl is disabled first. Use clean sysgen to compile the system after setting platform properties. If you are lucky, no compilation problem occurs and you can directly generate NK. Burn it to the device and get up. The printed information after the system is started is as follows.

Windows CE Kernel For Arm (thumb enabled) built on Dec 15   2010 At 16 : 44 : 21
Processortype = 0b76 Revision = 6 Cpuid = 0x0000fb766
Oemaddresstable = 80203b80
[Kernel] + Oeminit ()
[Kernel] dcache: 128 Sets, 4 Ways, 32 Line size, 16384 Size
[Kernel] icache: 128 Sets, 4 Ways, 32 Line size, 16384 Size
[Kernel] chipid [ 156 ] [Acda17d0]
[Kernel] - Oeminit ()
Nkstartup done, starting up kernel. ncpus =   1
Windows CE kernelinit
Error Reporting memory reserved, dump size =   00020000
Booting Windows CE version 7.00   For (ARM)
Memory ing: Total pages: 36278 , Filesystem pages =   4534
Booting kernel with clean memory Configuration:
Total memory sections: 1
[ 0 ] ( Static ): Start: 83a26000, extension / Attributes: 00024000 , Length: 08db6000
Scheduling the first thread.
PID: 00400002 TID: 00410002 Pgpool: Reserved 768 Pages For Loader pool
PID: 00400002 TID: 00410002 Pgpool: Reserved 256 Pages For File pool
PID: 00400002 TID: 00410002 Error: oalioctlhalgetdeviceinfo: Invalid request
PID: 00400002 TID: 00410002 Export xst0: Platform name = Wince6. 0 R3
PID: 00400002 TID: 00410002 Warn: oalioctlhalgetdeviceinfo: spi_getprojectname: bu
Ffer too small
PID: 00400002 TID: 00410002 Optional xst1: >>> Loading Module ' KD. dll ' ( 0xc0401db0 ) At
Ddress 0xeffe0000 - 0xefffe000   In Process ' NK. exe ' ( 0x83a09ad0 )
PID: 00400002 TID: 00410002 KD: Starting kernel debugger software probe (kdstub) -
Kd api version 27
PID: 00400002 TID: 00410002 Optional xst1: >>> Loading Module ' NK. exe ' ( 0x83a09ad0 ) At
Ddress Zero X 80200000 - Zero X 80217000   In Process ' NK. exe ' ( 0x83a09ad0 )
PID: 00400002 TID: 00500002 Filesys doesn ' T exist, no app started

So far, the migration of wince7.0 oal has been preliminarily completed. Although we haven't seen the wince7.0 interface yet, we have finally learned about platform Builder 7.0. Next, we can transplant the display and touch drivers to further unveil wince7.0.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.