Vortex86DX-MSJK CE 6.0 Jump Start - Getting Started Guide
Vortex86DX-MSJK Windows Embedded CE 6.0 R3 Jump Start Rev 2.0
Page 123
Appendix I –
CoreCon Connectivity
CoreCon connectivity is needed to establish link between the CE 6.0 target device and the Visual Studio
(2005 and 2008) IDE for the purpose of developing application and deploying the application to the
target device for testing and debug.
The CoreCon files are installed to the development workstation as part of the VS2005 and VS2008
installation to the following folder on the development workstation:
\Program Files\Common Files\Microsoft shared\CoreCon\1.0\Target\WCE400\<CPU>
There are multiple set of CoreCon files installed to sub-folders under the above directory, to support
ARM, MIPS and x86 processors, with the processor family as the sub-folder name. Each of these
CoreCon files supports a designated processor family.
The VDX-6326 SBC is engineered with an x86 processor, the required CoreCon files to support VDX-6326
SBC are in the following folder:
\Program Files\Common Files\Microsoft shared\CoreCon\1.0\Target\WCE400\x86\
To establish connectivity between the Visual Studio IDE and CE 6.0 target device, the appropriate
CoreCon files need to be launched on the target device when CE 6.0 starts. In order to use these
CoreCon files, they must be included to the CE 6.0 OS runtime image, copied to the target device’s local
storage or make available to the target device via Network share or external storage attached to the
target device.
To help ease the process of including the required CoreCon files to the OS design, an installable CoreCon
component for CE 6.0,
CoreCon_v200_x86_WinCE600.msi
, is provided with this jump start kit. Locate
and launch the
CoreCon_v200_x86_WinCE600.msi
installation file from the jump start kit CD, in the
\Software
folder, to install the software to the development workstation.
After installing the
CoreCon_v200_x86_WinCE600.msi
file, the CoreCon component is installed to the
\Third Party\CoreCon folder on the component catalog, and listed as
CoreCon_v200_x86
on the
component catalog. When selected and included to the OS design, the necessary CoreCon files are
copied to the build release directory and compiled as part of the OS runtime image.
Note:
There are different versions of CoreCon. CoreCon version 8.0 is installed with VS2005. When VS2008 is
installed, it updates the CoreCon to version 9.0.
A development workstation with both VS2005 and 2008 installed will have CoreCon version 9.0.
CE 6.0 image built with different version of CoreCon from one development workstation will not be able
to establish connectivity to another development workstation with different version of CoreCon.
The CoreCon_v200_x86 component does not include the actual CoreCon binary files. When the
CoreCon_v200_x86 component is included in the OS design, it references and adds the necessary build
steps to include the CoreCon files already installed to the development workstation, by the VS2005 and
VS2008 installation process, to the OS runtime image.
Following the steps provided in this getting started guide to develop an OS design with
CoreCon_v200_x86 component selected, the OS runtime image generated from the OS design will have
the correct version of CoreCon installed on the development workstation to support connectivity
between the target device and the development workstation.