Export (0) Print
Expand All

How to Use Platform Builder to Connect to Multiple Target Devices (Windows Embedded CE 6.0)

1/5/2010

From a single development workstation, you can connect to multiple Windows Embedded CE–based devices. For each simultaneous connection to a target device, you must open a separate instance of Platform Builder on your development workstation. You must also create a separate named connection for each target device.

Connecting to multiple devices can improve the efficiency of the development process. Through multiple connections, you can manage several target devices simultaneously from the same development workstation. You can create connections to multiple target devices that all run identical run-time images. The target devices can also all run different run-time images.

Step Topic

1. Decide which target devices you want to use.

You can use a target device if the run-time image for the target device includes kernel independent transport layer (KITL) support.

Supporting KITL in an OS Design

2. Verify that the run-time image for each target device includes the appropriate board support package (BSP) for the hardware of the target device.

Supported Board Support Packages

3. If you have not already built a run-time image for each target device that you want to use, build an OS design into run-time image for each target device that lacks one.

Building a Run-Time Image

4. In the Output window, on the Output tab, verify that the build contains no errors.

Build Error Debugging Process

5. Choose a download service appropriate for the connection hardware. The download service will download a run-time image to each target device.

Download Service Selection

6. Set up and configure the connection hardware required for the download service. That hardware connects each target device to the development workstation, on which Platform Builder is installed. Examples of connection hardware include cables, a hub, or Ethernet network adapters.

Hardware Configuration

7. If you selected Serial Download Service in step 5, configure the HyperTerminal terminal emulation application to display the serial debug output from the serial port on the target device.

This configuration requires a null-modem cable connected to a serial port, such as COM1.

Configuring HyperTerminal for BSPs

8. Turn on each target device so that it becomes active on the Ethernet network or over the serial connection, and Platform Builder can discover it.

Not applicable

9. In Platform Builder, create a named connection for each target device.

Creating a Named Connection

10. Configure each named connection.

Choose the appropriate topic based on whether the development workstation and each target device are connected by an Ethernet network or a serial port connection.

Configuring an Ethernet Remote Connection

Configuring a Serial Remote Connection

11. Choose the named connection that corresponds to the first target device, and then connect your development workstation to the first target device.

Connecting to a Target Device Over an Existing Named Connection

12. Start another instance of Platform Builder on your development workstation.

Not applicable.

13. In the instance of Platform Builder you just started, choose the named connection that corresponds to the next target device, and then connect your development workstation to the next target device.

Connecting to a Target Device Over an Existing Named Connection

14. Repeat steps 9 and 10 for each additional target device you want to connect to your development workstation.

Not applicable.

Community Additions

ADD
Show:
© 2014 Microsoft