Configuring a Core Connection to a Target Device
Other versions of this page are also available for the following:
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
You can configure settings that affect how an application image downloads to a target device, and how Platform Builder communicates with the target device after the application launches.
To configure a connection to a target device
From the Target menu, choose Connectivity Options.
In the Target Connectivity Options dialog box, choose Kernel Service Map.
In the Target Device box, choose a target device.
You can configure as many device connections as you want, as long as each connection has a unique name.
If a connection to a named target device is already configured, the settings associated with the connection to the target device appear in the Download box and the Transport box.
In the Download box, choose a download service.
At the right of the Download box, choose Settings.
If you are connecting to the Device Emulator, the default download service Device Emulator (DMA) appears in the drop-down list.
For more information about download settings, see Configuring a Connection for Downloading and Debugging.
Configure the settings for the download service and then choose OK.
In the Transport box, choose a kernel transport
If you are connecting to the Device Emulator, the default download service Device Emulator (DMA) appears in the drop-down list.
Otherwise, choose Ethernet, Serial, or USB.
At the right of the Transport box, choose Settings.
If you select a transport that requires configuration, Platform Builder displays a dialog box where you can configure the kernel transport.
If necessary, modify the following settings for the kernel transport and then choose OK.
- Ethernet KITL settings: specify the target device KITL name and target device boot loader name.
For an Ethernet connection, the development workstation and target device must be on the same subnet. Otherwise, you cannot connect to the target device or debug a Windows Embedded CE OS on the target device. - Serial KITL settings: specify COM port, baud rate, data bits, and parity and flow control.
If you use a serial connection to download a run-time image to a CEPC, you cannot use an Ethernet connection with the KITL protocol to debug the Windows Embedded CE OS.
- Ethernet KITL settings: specify the target device KITL name and target device boot loader name.