ICOP VDX-6318 Getting Started Manual
Samuel Phung
Windows Embedded MVP
ICOP Technology Inc.
Screen captured with Snagit
VDX-6318
Windows Embedded Compact 7
Getting Started Guide
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Table of Contents
Introduction .................................................................................................................................................. 6
Part 1 – Development Environment Overview ............................................................................................. 7
Windows Embedded Compact 7 .............................................................................................................. 7
Windows Embedded Compact 7 – Platform Builder ................................................................................ 7
Windows Embedded Compact 7 Remote Tools ....................................................................................... 7
Visual Studio 2008 Integrated Development Environment ...................................................................... 8
Develop Compact 7 Devices: Typical Development Steps ....................................................................... 8
Develop Compact 7 Applications with VS2008......................................................................................... 9
Silverlight for Windows Embedded .......................................................................................................... 9
The Target Device ..................................................................................................................................... 9
Common Terminology ............................................................................................................................ 11
Compact 7 Environment and Directory Variables .................................................................................. 12
OEM Environment Variables .................................................................................................................. 12
Part 2 – Development Environment Connectivity ...................................................................................... 13
Ethernet Connectivity ............................................................................................................................. 13
Develop Compact 7 OS Run-time Image – OS Design .................................................................... 13
Develop Compact 7 Applications with Visual Studio ..................................................................... 13
Serial Debug Connectivity ....................................................................................................................... 13
Development Environment Setup with DHCP ........................................................................................ 14
Using Wireless Access Point Router ....................................................................................................... 14
Development Environment Setup with Static IP .................................................................................... 15
Local Area Network without DHCP Service .................................................................................... 15
Direct Connection using Cross-Over RJ-45 Ethernet Cable............................................................ 15
Static IP Addresses ......................................................................................................................... 15
Part 3 – Required Software & Installation .................................................................................................. 16
Recommended Software Installation Sequence .................................................................................... 16
Windows Embedded Compact 7 Installation ......................................................................................... 16
Board-Support-Package Installation ....................................................................................................... 17
SDK Installation ....................................................................................................................................... 18
AutoLaunch Component Installation ...................................................................................................... 18
CoreCon Connectivity Component ................................................................................................... 18
Part 4 – OS Design (Platform Builder Project) ............................................................................................ 19
Visual Studio 2008 .................................................................................................................................. 19
Windows Embedded Compact 7 OS Design Wizard ............................................................................... 19
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 2
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
OS Design Wizard – Board Support Package (BSP) ................................................................................. 20
OS Design Wizard – Design Templates ................................................................................................... 21
OS Design Wizard – Applications & Media ............................................................................................. 21
OS Design Wizard – Networking & Communications ............................................................................. 22
Security Warning - Catalog Item Notification ......................................................................................... 23
Part 5 – Configure and Customize Compact 7 OS Design ........................................................................... 24
Customize the OS Design – Add Additional Components ...................................................................... 24
Customize the OS Design – Locate Component by Search ..................................................................... 29
Customize the OS Design – Configuration Manager .............................................................................. 30
Customize the OS Design – Build Options .............................................................................................. 31
Customize the OS Design – The Registry ................................................................................................ 32
Registry Entries for FTP Server Component ................................................................................... 32
Registry Entries for the Telnet Server Component ........................................................................ 32
Registry Entries for the AutoLaunch Component .......................................................................... 32
Adding Registry Entries to OS Design ............................................................................................ 33
Static IP Address ..................................................................................................................................... 33
Other Compact 7 Components ............................................................................................................... 34
Part 6 – Build and Generate Compact 7 OS Run-time Image ..................................................................... 35
The Build Process – Starting ................................................................................................................... 35
The Build Process – Completed .............................................................................................................. 35
Part 7 – Download Compact 7 OS Run-time to Target Device .................................................................... 37
Target Device Preparation ...................................................................................................................... 37
Create Connectivity Profile for a Target Device ..................................................................................... 38
Associate VDX-6318 to MyTargetDevice Connectivity Profile ............................................................... 39
Download Compact 7 OS Run-time Image to VDX-6318 ........................................................................ 42
Deploy Compact 7 OS Run-time Image to Target Device ....................................................................... 43
Part 8 – Software Development Kit (SDK) ................................................................................................... 45
Create and Configure Compact 7 SDK .................................................................................................... 45
Build and Generate Compact 7 SDK ....................................................................................................... 47
Part 9 – Develop Native Code App with VS2008......................................................................................... 48
Create a New Native Code Application Project ...................................................................................... 48
Add Codes and Build the Application Project ......................................................................................... 51
Preparing Target Device to Connect to VS2008 IDE ............................................................................... 52
Configure VS2008 Device Connectivity Settings ..................................................................................... 54
Establish Connectivity to Compact 7 Target Device ............................................................................... 56
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 3
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Download Application to Target Device ................................................................................................. 57
Part 10 – Develop Managed Code App with VS2008 .................................................................................. 58
Create a New Managed Code Application Project ................................................................................. 58
Add Codes and Build the Application Project ......................................................................................... 60
Preparing Target Device to Connect to VS2008 IDE ............................................................................... 61
Establish Connectivity to Compact 7 Target Device ............................................................................... 61
Download Application to Target Device ................................................................................................. 62
Debug Application Running on Target Device ........................................................................................ 64
Part 11 – Debug and Remote Tools ............................................................................................................ 67
Download KITL Enabled Compact 7 OS Image to Target Device ............................................................ 68
Remote Tool: Process Viewer ................................................................................................................ 68
Remote Tool: Registry Editor ................................................................................................................. 70
Remote Tool: System Information ......................................................................................................... 71
Part 12 – Silverlight for Windows Embedded ............................................................................................. 73
Congratulations! – You’ve completed all the steps .................................................................................... 74
Appendix A – Development station Setup with DHCP ................................................................................ 75
Connecting to Local Area Network with DHCP ....................................................................................... 75
Using Wireless Access Point Router ....................................................................................................... 75
Capturing Serial Debug Messages .......................................................................................................... 76
Appendix B – Development station Setup with Static IP ............................................................................ 77
Connecting to Ethernet Hub or Switch without DHCP ........................................................................... 77
Direct Connection with Cross-Over RJ-45 Ethernet Cable ...................................................................... 77
Static IP Address ..................................................................................................................................... 77
Capturing Serial Debug Messages .......................................................................................................... 78
Appendix C – Windows Embedded Compact Resources ............................................................................ 79
Appendix D – VDX-6318-MSJK Technical Information ................................................................................ 82
Appendix E – Startup Options ..................................................................................................................... 91
Configure the SBC to boot from USB Flash Storage ............................................................................... 91
Appendix F – BIOSLoader ............................................................................................................................ 92
Primary BIN File .................................................................................................................................. 92
Alternative BIN File ............................................................................................................................ 92
BIOSLoader Configuration File for VDX-6318 ............................................................................... 93
Appendix G – Using Static IP Address ......................................................................................................... 95
Configure Static IP for Prebuilt Compact 7 OS Run-time ........................................................................ 95
Configure OS Design with Static IP Address ........................................................................................... 96
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 4
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Appendix H – Deploy OS Run-time with DiskPrep ...................................................................................... 97
Appendix I – CoreCon Connectivity .......................................................................................................... 100
Appendix J – Recover Jump Start Kit’s Original Files ................................................................................ 102
VDX-6318-MSJK Preconfigured Files .................................................................................................... 102
Recover Files with DiskPrep .................................................................................................................. 102
Appendix K – VDX-6318 System BIOS ....................................................................................................... 104
Appendix L – Using Watchdog Timer ........................................................................................................ 106
Using WDT0 .......................................................................................................................................... 106
Using WDT1 .......................................................................................................................................... 108
Watchdog Timer DLL: WDT.dll ............................................................................................................. 109
Appendix M – Using GPIO ......................................................................................................................... 110
Using the GPIO ...................................................................................................................................... 110
Windows Embedded CE Sample Codes ....................................................................................... 110
Configure GPIO to Output Mode ................................................................................................. 111
Configure GPIO to Input Mode .................................................................................................... 112
GPIO.DLL ...................................................................................................................................... 113
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 5
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Introduction
This Windows Embedded Compact 7 (Compact 7) getting started guide, with hands-on exercises, is
written in step-by-step format to show how to create a Compact 7 OS design, build customized OS runtime image from the OS design, configure the development environment to download the OS run-time
image to a target device, develop Compact 7 applications using the Visual Studio 2008 (VS2008)
Integrated Development Environment (IDE).
The following subjects are covered in this guide:
Development environment overview
Required software and recommended installation sequences
Develop and configure Compact 7 OS design project
Build customized Compact 7 OS run-time image
Establish connectivity and download OS run-time image to target device
Develop VS2008 managed and native code application for Compact 7 device
Develop managed and native code applications for Compact 7 using Visual Studio 2008,
establish connectivity and download the application to target device for testing and debugging
Using Kernel Independent Transport Layer (KITL) and Remote Tools to debug Compact 7 OS run-
time on a target device
While it’s possible to use a Virtual PC as the target device and work through similar exercises, using a
real hardware provides a practical environment, and helps improve the learning process. The VDX-6318
Single-Board-Computer (SBC), configured with the necessary software components, is used as the target
device for the exercises in this guide.
To minimize unnecessary problem caused by missing software components and improper development
environment setup, follow the recommended software installation sequences and setup provided as
part of this getting started guide to install the necessary software.
The primary objective for this guide is to show how to use Compact 7 development tools. It’s not within
this guide’s objective to talk about programming language and concept. Short and simple exercises are
used in this guide to keep the subject matter simple and easy to understand.
Update to this getting started guide and other Compact 7 resources are available from the following
URLs:
http://www.embeddedpc.net/VDX6318MSJK/
http://www.embeddedpc.net/download/VDX6318.htm
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 6
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Note:
The previous version, Windows Embedded CE 6.0 Platform Builder, is a plug-in to the Visual Studio
2005 IDE.
For Windows CE 5.0 and earlier versions, Platform Builder was a standalone development tool.
Part 1 – Development Environment Overview
The Windows Embedded Compact 7 Platform Builder (Platform Builder) development tool is a plug-in to
the Visual Studio 2008 integrated development environment (VS2008 IDE). All Compact 7 development
tasks are supported within the VS2008 IDE, a developer friendly, efficient and intuitive development
environment with templates and wizard to help simplify complicate development tasks.
Windows Embedded Compact 7
Windows Embedded Compact 7 is a hard Real-time operating system with ability to handle 32,000
concurrent processes and 2GB memory footprint for each process. Compact 7 delivers reliable,
secure performance in a small footprint package along with the latest networking, multimedia and
communications technologies. Compact 7 provides broad range of device support with enhanced
features, including robust file system, Web services for device, Silverlight for Windows Embedded,
voice over IP, network gateway configurations, platform development tool enhancements, greater
application compatibility with other Windows Embedded Compact based devices, Internet Explorer,
Windows Media CODECs, Microsoft .NET Compact Framework, and a number of other newly
supported protocols and services.
Combining large pool of production quality BSPs, device drivers, programming libraries and effective
development tools, Compact 7 provides an ideal rapid application development environment to help
create the next generation of smart, media rich, connected and service oriented devices. For more
information about Compact 7, visit:
http://www.microsoft.com/windowsembedded/en-us/products/windowsce/compact7.mspx
Windows Embedded Compact 7 – Platform Builder
Platform Builder is the development tool used to create Compact 7 OS design projects, build custom
Compact 7 OS run-time images and develop Compact 7 device drivers. It also provides the remote
tools to debug Compact 7 OS run-time image, device drivers and software components on a target
device.
Platform Builder for Compact 7 is a plug-in to the VS2008 IDE, and requires the VS2008 IDE to
function.
Windows Embedded Compact 7 Remote Tools
Using remote tools provided as part of the Compact 7 development environment, you are able to
remotely debug Compact 7 OS run-time image running on a target device, built with KITL enabled.
The following remote tools are provided as part of the Compact 7 development environment:
File Viewer
Kernel Tracker
Performance Monitor
Power Monitor
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 7
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Process Viewer
Profiler
Registry Editor
Resource Consumer
Resource Leak Detector
System Information
Timeline Viewer
Zoom
Visual Studio 2008 Integrated Development Environment
Visual Studio 2008 is a popular developer friendly development tool to develop broad range of
applications for different version of the Windows operating system. From the VS2008 IDE, you can
develop applications for the following Windows operating system:
Windows 7 and Windows Embedded Standard 7
Windows Vista, Windows XP and Windows XP Embedded
Windows 2003 and 2008 Server
Windows Phone 7, Windows Mobile Smartphones and Windows Embedded Handheld
devices
Windows Embedded CE 6.0 and Windows Embedded Compact 7 devices
More…
The VS2008 IDE provides a centralized development environment to develop broad range of
applications, such as:
Windows Form application
Win32, ATL and MFC project
DLL, ActiveX control, ASP.NET Web service, Windows service
SQL Server project, Console application, Class libraries
Windows Embedded Compact and Mobile Smart Device application
Windows Embedded Compact OS design
More…
Develop Compact 7 Devices: Typical Development Steps
After the hardware platform is selected, a typical Compact 7 device development project goes
through the following development phases:
Develop Compact 7 bootloader, device drivers and BSP for the selected hardware (some
hardware vendors provide device driver and BSP to support their hardware)
Create and customize an OS design project for the hardware
Build customized Compact 7 OS run-time image for the hardware
Deploy Compact 7 OS run-time image to the hardware for testing and debugging
Generate Compact 7 SDK from the OS design to support application development
Develop application for the Compact 7 device
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 8
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Application development can take place concurrently, as the hardware and OS design being
fine-tuned
After the satisfied Compact 7 OS run-time image and application are created, deploy the
solution to the final hardware for distribution
Develop Compact 7 Applications with VS2008
Visual Studio 2008 supports application development for Compact 7 devices. There are multiple
options to develop Compact 7 applications using the VS2008 IDE:
Develop Native code application with Visual C++
Develop Managed code application with Visual C#
Develop Managed code application with Visual Basic
A Software Development Kit (SDK), generate from the OS design for the target device, is needed to
support native code application development for the target device using VS2008.
The Visual Studio IDE provides an efficient development environment, making it possible to
download the OS run-time image and application from the development station to the target device
for testing and debugging.
From the Visual Studio 2008 IDE with KITL and CoreCon connectivity, you are able to download OS
run-time image and application to a Compact 7 target device, launche the application, set
breakpoint and step through the codes one-line-at-a-time as the application runs on the target
device.
Silverlight for Windows Embedded
Silverlight is a user interface (UI) development framework designed to separate the graphical
presentation from the programming logic. Silverlight enables graphic designer to design the
graphical presentation for the application without the need to understanding the programming logic
and provides a structured system for the application developer and graphic designer to work
together, doing what they do best.
While the desktop and Windows Phone 7 Silverlight application’s code behind is based on managed
code, Silverlight for Windows Embedded application’s code behind is based on native code, which
provides an environment to develop small and efficient code to support embedded devices typically
built with limited hardware resources.
Silverlight for Windows Embedded enables UI designers to develop stunning UI for the device
without the need to understand complicated application code. At the same time, application
developer can focus on their core expertise, develop the application logic and leverage UI graphic
designer’s expertise to design user interface for the project.
Silverlight for Windows Embedded application for Compact 7 is developed using the combination of
C++ and XAML code, using Visual Studio 2008 and Expression Blend 3.
The Target Device
The term target device is referring to the hardware platform used in a Compact 7 development
project. For the exercises in this guide, the VDX-6318 single-board-computer (SBC) is used as the
target device.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 9
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Note:
We will refer to the VDX-6318 SBC as “SBC” or “Target Device” within this getting started guide.
A VDX-6318 BSP which includes the necessary hardware adaptation codes, device drivers and
configuration files to support Compact 7 OS development, is used for the exercises in this guide to
develop the OS design project, as shown in Figure 1.
Fig. 1 – ICOP_VDX6318_70B BSP for Compact 7
In addition to the device drivers, the following DLLs are included as part of the BSP to help
developers access the SBC’s GPIOs and Watchdog timers:
GPIO.dll (To access the GPIOs)
WDT.dll (To access the Watchdog timers)
When developing an OS design using the ICOP_VDX6318_70B BSP, these DLLs are included to the OS
design and compile into the OS run-time image by default.
Sample native and managed code projects showing how to use these DLLs are provided on the jump
start CD-ROM.
Refer to appendix L for more information about watchdog timer.
Refer to appendix M for more information about GPIO.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 10
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Abbreviation/ key word
Description and Representation
Compact 7
Windows Embedded Compact 7
Platform Builder
Windows Embedded Compact 7 Platform Builder
VS2008
Visual Studio 2008
IDE
Integrated Development Environment
BSP
Board Support Package: A group of Windows Embedded Compact
software components that includes the OEM adaptation layer code,
device drivers and configuration files, needed to create the OS design
project to generate OS run-time image for the targeted hardware.
OAL
OEM Adaptation Layer
Component
Component can be a device driver, BSP, programming library,
application, utility, configuration settings, fonts, etc... The OS design is
made up by a group of components.
Component Catalog
The component catalog lists all of the components provided by Platform
Builder and installed 3rd party components. The component catalog
provides the interface to add components to the OS design project and
remove components from the project. This is also the interface to view
which components are included to the OS design project.
OS Design
OS design is a Platform Builder project, containing components that
make up the OS run-time image. Windows Embedded Compact OS runtime image is generated from an OS design project.
Target Device
Refer to the device used in the Compact 7 development environment.
When working on exercise using an emulator, the emulator is the target
device. Virtual PC can also be a target device for the Compact 7
development environment. For the exercise in this guide, the VDX-6318
SBC is the target device.
OS Run-time Image
The binary file generated from the OS design project to deploy to the
target device.
Release Directory or
Build Release Directory
Referring to the directory where all files related to the OS design
projects are placed by the build tools prior to compiling the OS run-time
image.
SBC
Single-Board-Computer
Common Terminology
To minimize the need to write long description and the need to use lengthy term repeatedly, it’s a
common practice for developer in different industries to use abbreviated key words. To the new
comer, without knowing the terminologies used and what the abbreviated key words represent can
cause confusion.
The following table contains abbreviation for some of the common key words used in the Compact 7
development environment and this getting started guide:
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 11
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Variable Name
Description - Purpose
BSP_DISPLAY_NOP
Configure the OS design to include the stub display driver
(DDI_NOP.dll) to support headless device.
BSP_NOAUDIO
Configure the OS design to exclude all audio components from the
build.
IMGRAM256
Configure the OS design to generate run-time image supporting
256MB of RAM
PRJ_ENABLE_FSREGHIVE
Configure the OS design to enable Hive-based registry support
_WINCEROOT
Defines the root directory for the Compact 7 install, default is:
C:\WINCE700
_PLATFORMROOT
Represent the following directory:
$(_WINCEROOT)\PLATFORM
Or
C:\WINCE700\PLATFORM
Variable Name
Description - Purpose
BSP_VORTEX86DX_IDE
Enable support for IDE storage device.
BSP_VORTEX86DX_9120A
Enable support for IDE device built with 9120A chip.
BSP_NIC_R6040
Enable support for R6040 Ethernet controller.
BSP_DISPLAY_Z9S_xxxx
Multiple environment variables to configure display settings.
BSP_VDX_DisableAgressiveFlush
When enabled, it configures the OS design to disable aggressive
registry flushing.
Compact 7 Environment and Directory Variables
Within the Compact 7 development environment, environment variables are used to configure the
OS design to include, exclude associated components and control certain system behaviors.
Directory variables representing the associated directory are used to help make the codes and script
easier to understand and read. Here are some of these variables:
The above table lists a small sampling of variables used in the Compact 7 development environment.
For more information about these environment variables, visit the following URLs:
About Environment Variables:
http://msdn.microsoft.com/en-us/library/gg154986.aspx
BSP Environment Variables:
http://msdn.microsoft.com/en-us/library/ee478674.aspx
IMG Environment Variables:
http://msdn.microsoft.com/en-us/library/ee479025.aspx
PRJ Environment Variables:
http://msdn.microsoft.com/en-us/library/ee479112.aspx
Miscellaneous Environment Variables:
http://msdn.microsoft.com/en-us/library/ee479008.aspx
OEM Environment Variables
In addition to the environment variables established by Microsoft, hardware manufacture can
establish environment variables unique to their BSP to support the intended target device. The
following environment variables are unique to the ICOP_VDX6318_70B BSP:
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 12
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Part 2 – Development Environment Connectivity
It’s important to establish a proper development environment and understand different options
available to establish connectivity between the development station and the target device, to download
OS run-time image, and deploy application to the target device for testing and debug. This section talks
about connectivity between the development station and the target device.
Ethernet Connectivity
For the exercises in this guide, Ethernet is the primary connectivity used in the development
environment with both the development station and target device connected to the same Local
Area Network (LAN).
Ethernet connectivity is used to download the OS run-time image from the development station to
the target device and deploy application to the target device for testing and debugging.
Develop Compact 7 OS Run-time Image – OS Design
Compact 7 OS design is one of the project type supported by the VS2008 IDE, to generate
custom OS run-time Image.
As part of the OS design development process, connectivity between the development station
and target device is needed to download OS run-time image to the target device. While it’s
possible to use the serial port and other connectivity, Ethernet connection is efficient and
provides the bandwidth to download Compact 7 OS run-time image quickly. Comparing to a
serial connection, where the transfer rate is in the hundred kilo-byte (KB) range, Ethernet
connection’s transfer rate is in the mega-byte (MB) range.
Develop Compact 7 Applications with Visual Studio
The VS2008 IDE supports Compact 7 managed and native code applications development and
provides the environment to deploy application from the development station to the target
device.
As part of the application development exercises in this guide, with CoreCon connectivity
established over an Ethernet connection, the VS2008 IDE provides the facility to deploy
application to the target device, set breakpoint and enables the developer to step through the
code, line by line, as the application executes on the target device.
Serial Debug Connectivity
Serial Debug connectivity is established by connecting a null RS-232 serial modem cable between a
serial port on the target device and an available serial port on the development station. Serial
connection is useful for debugging headless device and the device’s startup process during the
bootloader phase where the Compact 7 OS run-time has not been fully launched.
A terminal emulation program, such as Hyper-Terminal or similar application, running on the
development station, is used to capture serial debug messages from the target device.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 13
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Development Workstation
Ethernet Hub
Server with DHCP
Target Device
Note:
The wireless-access-point-router device’s routing function filter and route network packets based
on the packet’s associated origin, destination and other information. In some router, the routing
algorithm may prevent some of the packets between the development station and target device
from reaching its destination and cause problem.
Development Environment Setup with DHCP
One of the common development environments to support Compact 7 development is to attach
both the development station and target device to the same LAN with DHCP service to provide IP
addresses dynamically with a null RS-232 serial modem cable connected between one of the serial
port on the target device and an available serial port on the development station.
Here is a typical setup to connect both the development station and target device to a LAN with
DHCP service, as shown in Figure 2.
Fig. 2 - Development environment with DHCP service provider
If the target device fails to establish connectivity with the development station as expected with this
configuration, it may be caused by one of the following:
The development station’s firewall software may be blocking the connection
DHCP service for the target device needs to be enabled on your network. Some secured
network may require the target device’s MAC address to be added to the authorized device
list to be serviced by the DHCP server
Using Wireless Access Point Router
When using a wireless-access-point-router with multiple Ethernet ports, connecting both the
development station and target device directly to the Ethernet port on the wireless-access-pointrouter may be problematic with certain model of access point, and prevent the development
environment from functioning as expected.
To minimize connectivity problem, instead of connecting directly to the wireless-access-point-router
device’s Ethernet ports, attach an Ethernet network hub to the wireless-access-point-router device,
to access the DHCP service provided by the wireless-access-point-router, connect both the
development station and target device to the Ethernet network hub. With both the development
station and target device connecting to the same Ethernet hub, the network traffics between them
are not filtered.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 14
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Development Workstation
Ethernet Hub
Target Device
Development Workstation
Null RS-232
Serial Modem Cable
Cross over RJ-45
Ethernet cable
Target Device
Development Environment Setup with Static IP
It’s possible to establish a Compact 7 development environment with Static IP addresses. Here are
two scenarios for setting up the development environment using static IP addresses:
Local Area Network without DHCP Service
The development station and target device are connected to the same LAN or Ethernet Hub,
without DHCP service, as shown in Figure 3.
Fig. 3 - Local Area Network without DHCP
Direct Connection using Cross-Over RJ-45 Ethernet Cable
Connectivity can be established by attaching the target device to the development station
directly, using a cross-over RJ-45 Ethernet cable, as shown in Figure 4.
Fig. 4 - Direct connection with cross-over RJ-45 Ethernet cable
Static IP Addresses
Without DHCP service to assign IP addresses dynamically, the target device and development
station must be configured with appropriate static IP addresses in order to establish
connectivity. Both the development station and target device must be configured with static IP
addresses within the same subnet.
Refer to appendix G for more information about using static IP addresses.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 15
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Part 3 – Required Software & Installation
The following software components are needed to work through the exercises in this getting started
guide:
Visual Studio 2008
Visual Studio 2008 service pack 1
Windows Embedded Compact 7
Visual Studio 2008 update for Windows Embedded Compact 7
ICOP_VDX6318_70B BSP
Vortex86DX_SDK_Compact7.msi
AutoLaunch_v300_Compact7.msi
Recommended Software Installation Sequence
It’s important to install the software in their proper sequences. Here is the recommended software
installation sequence:
Visual Studio 2008
Visual Studio 2008 service pack 1
Visual Studio 2008 service pack 1 is available from the following URL:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=fbee1648-7106-44a7-9649-6d9f6d58056e
Windows Embedded Compact 7
A 180 days evaluation version of Compact 7 software is available for download from
Microsoft, at the following URL:
http://www.microsoft.com/windowsembedded/en-us/downloads/download-windows-embeddedcompact-ce.aspx
Visual Studio 2008 update for Windows Embedded Compact 7
VS2008 update for Compact 7 is available for download from Microsoft, at the following
URL:
http://www.microsoft.com/download/en/details.aspx?id=11935
ICOP_VDX6318_70B_BSP.msi
This BSP is provided on the jump start kit CD, in the \WinCE700 folder.
Vortex86DX_SDK_Compact7.msi
This SDK is provided on the jump start kit CD, in the \WinCE700 folder.
AutoLaunch_v300_Compact7.msi
This AutoLaunch component is provided on the jump start kit CD, in the \WinCE700 folder.
RegFlush_v300_Compact7.msi
This RegFlush component is provided on the jump start kit CD, in the \WinCE700 folder.
Windows Embedded Compact 7 Installation
Since the Compact 7 development tool, Platform Builder, is a plug-in to the VS2008 IDE,
VS2008 must be installed to the develop workstation prior to installing the Compact 7 software.
When installing the Compact 7 software, during the installation options selection, select the Custom
install option, as shown in figure 5.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 16
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Note:
It’s strongly recommended to install all software to the default installation directory. Some of the 3rd
party components used for the exercises in this guide assume all software components are installed to
the default directory. When the software components are installed to a different directory, these 3rd
party components may not function as expected.
Fig. 5 - Installation Options (Custom install)
During the supported processor selection step, include support for the x86 Architecture, as shown in
Figure 6.
Fig. 6 - Supported processor architecture
Board-Support-Package Installation
VS2008 and Compact 7 must be installed prior to installing the Board-Support-Package (BSP). The
ICOP_VDX6318_70B BSP is provided on the jump start CD, in the \WinCE700 folder.
\WinCE700\ICOP_VDX6318_70B_BSP.msi
After installation, this BSP shows up on the Platform Builder 2008 component catalog as
“ICOP_VDX6318_70B : x86” under the \Third Party\BSP folder.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 17
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Note:
Files for the CoreCon component are installed to the development station as part of the Visual Studio
software installation.
For 32-bit Windows 7, XP and Vista development station, the CoreCon component files are installed to
the following directory:
\Program Files\Common Files\Microsoft Shared\CoreCon
For 64-bit Windows 7 development station, the CoreCon component files are installed to the following
directory:
\Program Files (x86)\Common Files\Microsoft Shared\CoreCon
SDK Installation
VS2008 and Compact 7 must be installed prior to installing the SDK. The Compact 7 SDK is needed
to support application development exercises in this guide, Vortex86DX_SDK_Compact7.msi, is
provided on the jump start CD, in the \WinCE700 folder.
\WinCE700\Vortex86DX_SDK_Compact7.msi
AutoLaunch Component Installation
The AutoLaunch catalog component for Compact 7 in self-installable file format,
AutoLaunch_v300_Compact7.msi, is provided with the jump start kit CD. To install, locate and
launch this component on the jump start CD, in the \WinCE700 directory.
\WinCE700\AutoLaunch_v300_Compact7.msi
After installation, this component shows up on the Compact 7 Platform Builder component catalog
as “AutoLaunch_v300_Compact7” under the “\Third Party\Embedded101” folder.
CoreCon Connectivity Component
In the previous version of the jump start kit, the CoreCon component was provided as a separate
component. For the exercise in this getting started guide, the CoreCon component is a subcomponent to the AutoLaunch component:
AutoLaunch_v300_Compact7/Autolaunch CoreCon
When the Autolaunch CoreCon sub-component is included in the OS design, it contains the
necessary command script and associated configuration parameters to include CoreCon files to the
final OS run-time image.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 18
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Part 4 – OS Design (Platform Builder Project)
In this section, with help from the OS Design wizard, you will work through the steps to create a new OS
design project.
Visual Studio 2008
The VS2008 IDE provides support to create different type of projects, such as Windows Application,
Console Application, Class Library, smart device application, Windows Services, Web Control, etc…
When starting a new project with VS2008, the VS2008 IDE provides different wizards and templates
to help create the initial workspace for the project. Platform Builder is one of the available project
types, to develop Compact 7 OS design project.
To begin, launch VS2008. From the VS2008 menu, select File → New → Project to bring up the new
project screen, as shown in Figure 7.
Fig. 7 - VS2008 New Project – Platform Builder 2008 (OS design)
From the New Project screen’s left pane, click to highlight the Platform Builder option.
From the right pane, click to highlight the OS Design option.
Enter VDX6318 as the name for the project.
Make sure the Create directory for solution check box is checked.
Click OK to continue.
Windows Embedded Compact 7 OS Design Wizard
When a new Platform Builder OS design project is selected, the OS Design Wizard launches, as
shown in Figure 8, and guides you through the process to configure the initial OS design project
using templates available as part of the VS2008 IDE.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 19
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Fig. 8 - OS Design Wizard
Click Next to continue and bring up the Create an OS Design - Board Support Packages
selection screen.
OS Design Wizard – Board Support Package (BSP)
In the BSP selection step, the OS Design Wizard provides the options to select one or more BSP for
the new project from the list of available BSPs. All of the installed BSPs, including BSPs from
Microsoft and third party companies are listed on the Create an OS Design - Board Support
Packages screen, as shown in Figure 9.
Fig. 9 - OS design Wizard – Select BSP
From the Select one or more BSPs pane, select the ICOP_VDX6318_70B: x86 BSP.
Click Next to continue and bring up the Create an OS Design - Design Templates screen.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 20
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
OS Design Wizard – Design Templates
In the design template selection step, the OS Design Wizard provides multiple design templates to
choose from, as shown in Figure 10.
Fig. 10 - OS design Wizard – Design Templates
Expand the Enterprise Device node and select the Industrial Controller template.
Click Next to continue and bring up the Create an OS Design - Application & Media screen.
OS Design Wizard – Applications & Media
In the applications & media selection step, the OS Design Wizard provides the options to select and
include the .NET Compact Framework, Internet Explorer, Network User Interface and other
components to the OS design, as shown in Figure 11.
Fig. 11 - OS Design Wizard – Applications & Media
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 21
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
In addition to the .NET Compact Framework 3.5 component, select and include the following
components to the OS design:
Console Window
Internet Explorer 7.0
Network User Interface
Waveform Audio
Windows Internet Services
Click Next to continue and bring up the Create an OS Design - Networking & Communication
screen.
OS Design Wizard – Networking & Communications
In the networking & communication selection step, the OS Design Wizard provides the options to
select communication, networking and security components, as shown in Figure 12.
Fig. 12 - OS Design Wizard – Networking & Communications
For the networking & communication selection step, keep the default selection.
Click Next to continue and bring up the Create an OS Design - OS Design Project Wizard
Complete screen, as shown in Figure 13.
At this point, the OS Design Wizard included the necessary OS components needed to configure the
initial OS design project.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 22
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Fig. 13 - OS Design Wizard – Completed
Click Finish to complete the OS Design Wizard step.
Security Warning - Catalog Item Notification
At the completion of OS Design Wizard step, the Catalog Item Notification screen is raised, with
security warning, to warn one or more of the components included in the OS design may pose
security risk, as shown in Figure 14.
Fig. 14 - Catalog Item Notification – Security Warning
Click Acknowledge to acknowledge the warning and close the warning screen.
At the completion of the OS Design wizard step, the initial project workspace for the OS design is
created in the following directory:
C:\WINCE700\OSDesigns\VDX6318\
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 23
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Part 5 – Configure and Customize Compact 7 OS Design
At this point, with help from the OS Design Wizard, the initial workspace for the OS design is created
using the Industrial Controller design template along with the ICOP_VDX6318_70B BSP and
components selected during the OS Design Wizard steps.
The following project folder and sub-folders are created for the OS design, under the main Compact 7
OS design project directory:
C:\WINCE700\OSDesigns\VDX6318\
This is the folder for the VDX6318 Solution. VS2008 supports different project types. A solution
provides a centralized work space to keep different project types supporting the same solution
in one location.
For example, the VDX6318 solution may include the “VDX6318 OS design”, “Visual Basic
managed code application”, “Visual C# managed code application” and “Visual C++ native code
application”.
C:\WINCE700\OSDesigns\VDX6318\VDX6318\
This is the folder for the VDX6318 OS design project.
The VS2008 IDE should look similar to the screen as shown in Figure 15.
Fig. 15 - VS2008 IDE after OS Design Wizard
Customize the OS Design – Add Additional Components
The OS design can be further customized with the following:
Add component(s) to the OS design.
Remove component(s) from the OS design.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 24
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Add application and library as subproject to the OS design.
Modify system configuration and registry files to customize system behavior.
With the VDX6318 OS design project active, from the VS2008 menu, select View → Other Windows
→ Catalog Items View to bring up the Catalog Item View window, as shown in Figure 16.
Fig. 16 - Catalog Items View (Component Catalog)
The Catalog Item View window on the VS2008 IDE contains all of the Compact 7 components,
including application, library, driver, utility and 3rd party components installed to the development
station which can be added to the OS design project.
From the Catalog Items View window, expand the component nodes and review the components
selected during OS Design Wizard steps:
o Component with a green check mark to the left indicates it was selected during the OS
Design Wizard steps, or manually added after the OS Design Wizard steps.
o Component with a solid green square to the left indicates the component is included to the
OS design as the result of being a dependency to another selected component.
o Component with a red cross to the left indicates the component is selected and is
dependent on one or more other components currently not included to the OS design.
(Component with a red cross to the left will not be included to the final image.)
Work through the following steps to customize the VDX6318 OS design project:
From the Catalog Items View window, expand the \Third Party\BSP node.
Expand all nodes under the ICOP_VDX6318_70B: X86 node, as shown in Figure 17.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 25
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Note:
The ATAPI (IDE) Storage component set the SYSGEN_ATAPI variable to include the ATAPI storage
driver, and the SYSGEN_FATFS variable to include FAT file system support.
Note:
The Hive-based registry component is needed to save registry settings to non volatile flash storage
between power reset.
Note:
Device driver to support the Z9s display controller.
Note:
The display setting is selected arbitrary for this HOL guide. You can select a different display
setting supported by the display monitor you are working with.
Note:
Device driver to support the R6040 Ethernet controller, built-in to the Vortex86DX System-OnChip.
Note:
This BSP component set the BSP_KEYBD_8042 environment variable to include the PS/2 Keyboard
and Mouse driver to the OS run-time image.
Fig. 17 - Catalog Items View (Component Catalog)
Check to ensure the following BSP components are selected and included to the OS design:
ATAPI (IDE) Storage driver
Hive-based registry support
Z9s XGI Display driver
VGA 1024x768x16 @ 60Hz
R6040 Ethernet driver
PS/2 Keyboard & Mouse driver
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 26
256MB RAM
Note:
The VDX-6318 SBC that comes with the jump start kit is built with 256MB. This component set the
IMGRAM256 environment variable and configure the OS run-time image to use the 256MB of
available system memory.
Improper system memory configuration can cause the Compact 7 OS run-time image not able to
complete the boot up process and reset the device.
Note:
This component set the BSP_SERIAL environment variable to include serial port driver to the OS
run-time to support COM1, the first serial port.
By default, the SBC’s first serial port is configured as follow:
- COM1: IRQ4, 3F8h
Note:
This component set the BSP_SERIAL2 environment variable to include serial port driver to the OS
run-time to support COM2, the second serial port.
By default, the SBC’s 2nd serial port is configured as follow:
- COM2: IRQ3, 2F8h
Note:
This component set the BSP_SERIAL3 environment variable to include serial port driver to the OS
run-time to support COM3, the third serial port.
By default, the SBC’s 3rd serial port is configured as follow:
- COM3: IRQ10, 3E8h
Note:
This component set the BSP_SERIAL4 environment variable to include serial port driver to the OS
run-time to support COM4, the fourth serial port.
By default, the SBC’s 4th serial port is configured as follow:
- COM4: IRQ11, 2E8h
Note:
This component set the BSP_VORTEX86DX_USB_AUDIO and SYSGEN_USB environment variables
to include the USB 2.0 driver and audio driver.
Note:
This component set the SYSGEN_USB_HID_CLIENTS environment variable to include the USB
Keyboard and Mouse HID class driver to the OS run-time image.
Note:
This component set the SYSGEN_USB_STORAGE environment variable to include the USB storage
class driver to the OS run-time image to support external USB storage.
st
1
2
Serial Port
nd
Serial Port
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
3rd Serial Port
4th Serial Port
USB Audio driver
USB Keyboard & Mouse (HID) class driver
USB Mass Storage class driver
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 27
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Note:
This component provides application installation & removal support. It’s needed to support
VS2008 application debug and deployment.
Note:
.NET Compact Framework components are needed to support managed code application. During
the OS Design wizard steps, .NET Compact Framework 3.5 components are included to the OS
design project. Expand the \Core OS\Windows Embedded Compact\Applications and Services
Development node to validate these two .NET Compact Framework components are selected.
Note:
The FTP server provides a convenience mechanism to upload file(s) to the target device, and
download file(s) from the target device, using an FTP client.
In the later section, the following registry entries will be added to the project to enable the FTP
server and enable support for anonymous login to the FTP server:
[HKEY_LOCAL_MACHINE\COMM\FTPD]
"IsEnabled"=dword:1
"UseAuthentication"=dword:0
"UserList"="@*;"
"AllowAnonymous"=dword:1
"AllowAnonymousUpload"=dword:1
"AllowAnonymousVroots"=dword:1
"DefaultDir"="\\"
Note:
With the appropriate registry entries, the AutoLaunch utility can be configured to launch one or
more application automatically when the Compact 7 OS starts.
The following sample registry entries configure the AutoLaunch utility to launch App1.exe and
App2.exe with 5 and 10 seconds delay respectively.
[HKEY_LOCAL_MACHINE\Startup]
“Process2”= “App1.exe”
“Process2Delay”=dword:00001388 ; delay 5 seconds before launching App1.exe
“Process3”= “App2.exe –c”
“Process3Delay”=dword:00002710 ; delay 10 seconds before launching App2.exe
Expand the \Core OS\Windows Embedded Compact\Applications – End User node, locate and
include the following components to the OS design to support CAB file installation and application
deployment from the Visual Studio 2008 IDE:
CAB File Installer/Uninstaller
Expand the \Core OS\Windows Embedded Compact\Applications and Services Development node,
locate and include the following components to the OS design to support managed code application:
.NET Compact Framework 3.5
OS Dependencies for .NET Compact Framework 3.5
Expand the \Core OS\ Windows Embedded Compact\Communication Services and
Networking\Servers node, select and include the FTP server component to the OS design:
FTP Server
Expand the \Third Party\Embedded101 node, select and include the following AutoLaunch
components to the OS design, a utility to launch application during startup:
AutoLaunch_v300_Compact7
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 28
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Note:
When this sub-component is added, it includes the command script to copy the necessary CoreCon
connectivity files to the OS design’s build release directory, and include the following registries to
launch CoreCon during startup:
[HKEY_LOCAL_MACHINE\Startup]
“Process0”=”ConmanClient2.exe”
“Process0Delay”=dword:00001388
[HKEY_LOCAL_MACHINE\System]
“CoreConOverrideSecurity”=dword:1
Note:
When this sub-component is added to the OS design, it sets the SYSGEN_CERDISP variable to
include the Remote Display application to the OS design and include the following registry entries
to launch the Remote Display application during startup:
[HKEY_LOCAL_MACHINE\Startup]
“Process1”=”cerdisp -c”
“Process1Delay”=dword:00002710
AutoLaunch_v300_Compact 7\Autolaunch CoreCon
AutoLaunch_v300_Compact 7\Autolaunch Remote Display application
Customize the OS Design – Locate Component by Search
The VS2008 IDE provides the search function to locate Compact 7 component from the catalog by
searching the catalog using key-word or partial key-word associated with the component. In this
section, you will use the search function to locate a component from the catalog and add the
component to the OS design.
From the Catalog Item View tab, enter Telnet in the search text box on the top right, and click the
green arrow to the right of the search text box to locate the Telnet Server component, as shown in
Figure 18.
Fig. 18 - Locate component using the search feature
The search engine locates and highlights the Telnet Server component, as shown in Figure 19.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 29
VDX-6318 Windows Embedded Compact 7 - Getting Started Guide
Note:
The Telnet Server component provides a convenience mechanism to access and the compact 7
device remotely. When this component is added to the OS design, it does not include the necessary
registry entries to launch the Telnet server.
In the later section, the following registry entries will be added to the project to enable the Telnet
server and enable support for anonymous login:
[HKEY_LOCAL_MACHINE\COMM\TELNETD]
"IsEnabled"=dword:1
"UseAuthentication"=dword:0
Fig. 19 - Locate component using the search feature
Select and include the Tenet Server component in the OS design.
Customize the OS Design – Configuration Manager
Using the configuration manager, the OS design can be configured to generate an OS run-time
image in checked, debug or release mode. An OS image built in release mode is optimized for
distribution, does not contain ASSERT and not able to output DEBUGMSG. An image built in debug
mode is not optimized and include additional resource to support debugging. However, a debug
mode image, without optimization, can be difficult to debug certain type of timing and performance
related problems. An image built in Checked mode (Checked mode is new to Compact 7), a hybrid
between the debug and release modes, is built with compiler optimization, contains ASSERT,
DEBUGMSG and RETAILMSG to provide the necessary resources needed for debugging.
A debug mode image will provide more detailed debug messages when the OS image loads and
executes applications and modules. The size of an OS image built in debug mode is generally about
50% larger than an OS image built in release mode, from the same OS design project. An OS image
built in release mode, with KITL enabled, provides sufficient debug information to support most of
the general application development environment. For the exercise in this guide, you will configure
the OS design to generate an OS run-time image in release mode.
From the VS2008 menu, select Build → Configuration Manager to bring up the
Configuration Manager screen, as shown in Figure 20.
Windows Embedded Compact 7 Getting Started Rev 2.00 Page 30
Loading...