Export (0) Print
Expand All

Troubleshoot the Sample Virtual Device (Compact 2013)

3/26/2014

If you encounter problems while trying to connect to your virtual device and download the run-time image, check the following table for the error message or symptom you are seeing. If you see more than one error message, start by troubleshooting the message that appeared first on the virtual device’s display.

Error message or symptom

Cause and Solution

ERROR: BootTransportPb: Failed get IP address from DHCP server!

The virtual device cannot connect to a DHCP server. This is most likely a problem with your virtual switch settings or your virtual device settings, but it could also be a problem with your network configuration. For more information, see Virtual device cannot CONNECT TO DHCP SERVER.

ERROR: BootDownloadBin!ImageType: BootTransportRead Failed!

  • The virtual device timed out before it connected to Platform Builder. Reset the machine and try again.
  • If there are multiple devices on your network, make sure you selected the correct device.
  • Platform Builder cannot see the virtual device. For more information, see Platform Builder does not recognize the virtual device.

The virtual device does not appear in the Platform Builder list of available target devices.

For more information, see Platform Builder does not recognize the virtual device.

Use the troubleshooting hints in this section when your virtual device does not boot correctly and displays the following message, which may be the first of several error messages:

ERROR: BootTransportPb: Failed get IP address from DHCP server!

This error message indicates that your virtual device cannot connect to a DHCP server. The most common cause is a problem with the settings on your virtual device or your virtual switch.

JJ200416.note(en-us,WinEmbedded.80).gifTip:
If none of the following suggestions help with this problem, you can configure your virtual device with a static IP address. For more information, see Use the virtual device with a static IP address.

Check your virtual device settings

  • Make sure the virtual device has a kernel-mode network adapter. In all of the Hyper-V versions, the kernel-mode network adapter is referred to as a legacy network adapter.
  • Make sure the virtual device is set to use the correct virtual switch.

Check your virtual switch settings

If your physical computer can connect to the network and if the virtual switch and virtual device settings are correct, the problem could be a conflict between your virtual device and your network configuration. To troubleshoot this problem, make sure that your:

  • Virtual switch is connected to the network.
  • Virtual switch is mapped to the correct network adapter on the physical computer.
  • Virtual switch and your physical computer are both configured to share the network adapter.

Check your network configuration

If your physical computer cannot connect to the network, you may need to troubleshoot the network connection itself. Even though network troubleshooting is far beyond the scope of this guide, the following list describes some of the most common network configuration issues to check for:

  • Check the IP address of the DHCP server and verify that the virtual switch is in the same subnet.
  • Check the firewall settings on your network.

Use the troubleshooting hints in this section when Platform Builder does not acknowledge the BOOTME messages, or the virtual device does not appear in the list of available target devices.

This problem can be caused by the Connectivity Options in Platform Builder or by your computer’s firewall settings.

  1. In Platform Builder, open an OS design project.

  2. On the Target menu, detach any devices.

  3. On the Target menu, select Connectivity Options, and then select the problem device under Target Device.

  4. Make sure the settings for this device are correct.

  5. Restart your virtual device and try to connect to Platform Builder again.

JJ200416.note(en-us,WinEmbedded.80).gifTip:
If an error message displays when you open the device settings, delete the device and then add it again. (You can also add this device under a new name without deleting the old name.) For information about how to add and delete devices, see Target Device Connectivity Options Dialog Box.

  1. On the physical computer that runs Visual Studio, open Windows Firewall with Advanced Security.

  2. On the Inbound Rules page, look for two rules for Visual Studio, one for TCP and one for UDP. If you do not see these rules, create them.

  3. For each rule, open the Properties dialog box, and then go to the Advanced tab.

  4. Under Edge Traversal, select Allow edge traversal, and then click OK.

  5. Repeat this same procedure for Platform Builder Windows Embedded Compact Service Host.

For general information about Windows Firewall with Advanced Security, see Windows Firewall with Advanced Security Overview on TechNet.

JJ200416.note(en-us,WinEmbedded.80).gifImportant:
If your physical computer is connected to a domain network, be sure that any network or firewall settings comply with the domain security policies. Contact your network administrator if you have any questions.
Show:
© 2014 Microsoft