Creating the Run-Time Images for the IPv6 Test Lab (Windows Embedded CE 6.0)

1/6/2010

The IPv6 test lab uses specific Windows Embedded CE-based run-time images. To build each run-time image and download it to a Windows Embedded CE powered device, follow the instructions in the order provided.

Ee493476.note(en-US,WinEmbedded.60).gifNote:
You must build CLIENT2 first because you need its IP address when building CLIENT1.
Ee493476.note(en-US,WinEmbedded.60).gifNote:
For information on network cards and interface names, see Configuring the Gateway Registry.

  1. In Platform Builder, create a new OS design. The following list shows the choices to make in the Windows Embedded CE OS Design Wizard:

    1. Name the OS design CLIENT2.
    2. Choose the CEPC x86 BSP.
    3. Choose the Industrial Device design template category.
    4. Choose the Enterprise Web Pad design template.
    5. Skip the Applications_Media wizard page.
    6. Skip the Gateway Extensions wizard page.
    7. On the Networking_Communications wizard page, make sure Tcp/IPv6 support is selected.

    For information about creating a new OS design, see Creating an OS Design with the Windows Embedded CE OS Design Wizard.

  2. Disable VMini interface on Ethernet adapters.

    1. In the Solution Explorer window, right-click on <Project Name>, and choose Properties.
    2. In Configuration Properties, select Environment.
    3. Create the following environment variables:
      BSP_NOSHAREETH = 1;
      IMGNOSHAREETH = 1;
    4. Choose OK to confirm changes.
  3. To build the CLIENT2 run-time image, from the Build menu, ensure that the following sub-menu items for Global Build Settings are selected:

    Copy Files to Release Directory after Build

    Make Run-Time Image After Build

  4. From the Build menu, choose Advanced Build Commands, and then choose Build and Sysgen.

    The time required to build the run-time image depends on the Catalog items included in the OS design. You can observe the build process on the Output tab and by looking at the status icon at the bottom right of the IDE.

  5. Configure a connection from the development workstation to the CLIENT2 CEPC target device. For more information about configuring this connection, see Configuring an Ethernet Remote Connection.

  6. If you have not previously created a boot floppy disk for the CEPC, do so now. For more information, see Creating a Boot Floppy Disk for an x86 SDB.

  7. To download the operating system (OS) image to the CEPC, from the Target menu, choose Attach Device.

    If the download does not start within a few minutes, restart the CEPC.

    After the image is downloaded, the UI appears on the CEPC.

  8. On the CEPC, from a command prompt, run IPConfig.

  9. Capture the IPv4 and IPv6 addresses for use later in these procedures.

  10. To disconnect from the CEPC, perform the following steps:

    1. On the Debug menu, choose Stop Debugging.
    2. On the Target menu, choose Detach Device.

  1. In Platform Builder, create a new OS design. The following list shows the choices to make in the Windows Embedded CE OS Design Wizard:

    1. Name the OS design CLIENT1.
    2. Choose the CEPC x86 BSP.
    3. Choose the Industrial Device design template category.
    4. Choose the Enterprise Web Pad design template.
    5. Skip the Applications_Media wizard page.
    6. Skip the Gateway Extensions wizard page.
    7. Make sure Tcp/IPv6 support is selected.

    For information about creating a new OS design, see Creating an OS Design with the Windows Embedded CE OS Design Wizard.

  2. To set up the Hosts file, perform the following steps. For more information, see Troubleshooting: Setting Up and Using the IPv6 Test Lab.

    1. From the Solution Explorer window, expand Parameter Files.
    2. Expand the CEPC folder.
    3. Open the Project.reg file.
    4. In project.reg, select the Source tab.
    5. Type the following information:
      ;Set up Hosts file
      [HKEY_LOCAL_MACHINE\Comm\Tcpip\Hosts\IPv6 CLIENT2]
      "ExpireTime"=hex:FF,FF,FF,FF,FF,FF,FF,FF
      "Ipaddr6"=hex:<CLIENT2 IPv6 address><CLIENT2 ScopeID>
      "Ipaddr"=hex:0a,00,03,02
      When you specify a link-local address, you should also specify a scope ID, which further defines the reachability scope for non-global addresses. For more information about reachability scope, see IPv6 Addressing. For more information about scope ID, see IPv6 Addresses.
      Before you convert the addresses and scope ID to hexadecimal, you must expand them. Expand the IPv6 address to the full 16-bytes, expand the scope ID to 4-bytes, and then separate byte boundaries with a space.
      You must also convert IPv4 to hexadecimal. For example, if the CLIENT2 IPv6 address and scope ID is 2000:::f1b3:240:5ff:fe70:2628%1, and the IPv4 address is 10.0.3.2, you would type: "Ipaddr6"=hex:20,00,00,00,00,00,f1,b3,02,40,05,ff,fe,70,26,28,01,00,00,00
      "Ipaddr"=hex:0a,00,03,02
      For more information, see Troubleshooting: Setting Up and Using the IPv6 Test Lab and Troubleshooting: Setting Up and Using the IPv6 Test Lab.
    6. Save and close the Project.reg file.
  3. Disable VMini interface on Ethernet adapters.

    1. In the Solution Explorer window, right-click on <Project Name>, and choose Properties.
    2. In Configuration Properties, select Environment.
    3. Create the following environment variables:
      BSP_NOSHAREETH = 1;
      IMGNOSHAREETH = 1;
    4. Choose OK to confirm changes.
  4. To build the CLIENT1 run-time image, on the Build menu, ensure that the following sub-menu items for Global Build Settings are selected:

    Copy Files to Release Directory after Build

    Make Run-Time Image After Build

  5. From the Build menu, choose Advanced Build Commands, and then choose Build and Sysgen.

    The time required to build the run-time image depends on the Catalog items included in the OS design. You can observe the build process on the Output tab and by looking at the status icon at the bottom right of the IDE.

    If an error occurs in the build, verify that you typed the information correctly in the Project.reg file. For more information, see Troubleshooting: Setting Up and Using the IPv6 Test Lab.

  6. Configure a connection from a development workstation to the CEPC target device. For more information about configuring this connection, see Configuring the Connection to a Target Device Using Platform Manager.

  7. If you have not previously created a boot floppy disk for the CEPC, do so now. For more information, see Creating a Boot Floppy Disk for an x86 SDB.

  8. To download the run-time image to the CEPC, from the Target menu, choose Attach Device.

    If the download does not start within a few minutes, restart the CEPC.

    After the image is downloaded, the UI appears on the CEPC.

  9. To disconnect from the CEPC, perform the following steps:

    1. From the Debug menu, choose Stop Debugging.
    2. From the Target menu, choose Detach Device.

  1. In Platform Builder, create a new OS design. The following list shows the choices to make in the Windows Embedded CE OS Design Wizard:

    1. Name the OS design ROUTER1.
    2. Choose the CEPC x86 BSP.
    3. Choose the Industrial Device design template category.
    4. Choose the Gateway design template.
    5. Select the Tcp/IPv6 support check box.
    6. Clear the Firewall check box. After you create the OS design, verify that the Firewall Catalog item is not selected in the Catalog. This item is located at Core OS\Communication Services and Networking\Networking - General\Firewall.
  2. To configure the TCP/IP protocol, you must change the registry. Perform the following steps to open the Project.reg file:

    1. In the Solution Explorer window, expand Parameter Files.
    2. Expand the CEPC folder.
    3. Open the Project.reg file.
  3. In project.reg, choose the Source tab.

  4. To configure the TCP/IP protocol for the interface on Subnet1, type the following information:

    ; Configure TCP/IP for the private interface, Subnet1

    [HKEY_LOCAL_MACHINE\Comm\<Private Network Interface Name (Adapter 1)>\Parms\Tcpip]

    "EnableDHCP"=dword:0

    "IPAddress"="10.0.1.1"

    "SubnetMask"="255.255.255.0"

  5. To configure the TCP/IP protocol for the public interface on Subnet2, type the following information:

    ; Configure TCP/IP for the public interface, Subnet2

    [HKEY_LOCAL_MACHINE\Comm\<Public Network Interface Name (Adapter 2)>\Parms\Tcpip]

    "EnableDHCP"=dword:0

    "IPAddress"="10.0.2.1"

    "SubnetMask"="255.255.255.0"

    "DefaultGateway"="10.0.2.2"

  6. Save and close the Project.reg file.

  7. Disable VMini interface on Ethernet adapters.

    1. In the Solution Explorer window, right-click on <Project Name>, and choose Properties.
    2. In Configuration Properties, select Environment.
    3. Create the following environment variables:
      BSP_NOSHAREETH = 1;
      IMGNOSHAREETH = 1;
    4. Choose OK to confirm changes.
  8. To build the ROUTER1 run-time image, from the Build menu, ensure that the following sub-menu items for Global Build Settings are selected:

    Copy Files to Release Directory after Build

    Make Run-Time Image After Build

  9. From the Build menu, choose Advanced Build Commands, and then choose Build and Sysgen.

    The time required to build the run-time image depends on the number of Catalog items included in the OS design. You can observe the build process on the Output tab and by looking at the status icon at the bottom right of the IDE.

    If an error occurs in the build, verify that you typed the information correctly in the Project.reg file. For more information, see Troubleshooting: Setting Up and Using the IPv6 Test Lab.

  10. Configure a connection from a development workstation to the ROUTER1 CEPC target device. For more information about configuring this connection, see Configuring the Connection to a Target Device Using Platform Manager.

  11. If you have not previously created a boot floppy disk for the CEPC, do so now. For more information, see Creating a Boot Floppy Disk for an x86 SDB.

  12. To download the run-time image to the CEPC, from the Target menu, choose Attach Device.

    If the download does not start within a few minutes, restart the CEPC.

  13. To verify ROUTER1, perform the following steps:

    1. On the Target menu, choose Target Control.
    2. In the Target Control window, type s ipconfig /d.
    3. Verify that the IP addresses displayed are the ones that you entered.
    4. If the IP addresses do not match, verify that the Ethernet adapters are recognized as expected. To do this, compare the names shown in the ipconfig output with the actual registry entries from step 3 and step 4. If a change must be made, you must also rebuild the run-time image.

Community Additions

ADD
Show: