none
Unable to establish connection to target device RRS feed

  • Question

  • I am running VS2005 with PB and WinCE 6.0 R3 under a Virtual PC 2007 running Windows XP SP3.
    I have a CE Device running my NK.bin booted from a DISKPREP'd Compact Flash.
    However, I am unable to establish any connection to the device under VS2005 using the remote tools or the debugger.

    * I have enabled the kernel debugger and KITL in the build options.
    * I have included the Target Control Support (SYSGEN_SHELL).
    * Host and Device are using DHCP and have aquired IP addresses.
    * Host and Device can ping each other.
    * Target is x86 ITOX NP101.


    Do I need more components included in my build? Could it be a problem running the host under a Virtual PC? Are there any components I can include in my build that would help?

    (I am new to Windows CE.)

    --Greg

    Thursday, June 2, 2011 4:49 PM

All replies

  • On 6/2/2011 6:49 PM, gloucks wrote:
    > I am running VS2005 with PB and WinCE 6.0 R3 under a Virtual PC 2007
    > running Windows XP SP3.
    > I have a CE Device running my NK.bin booted from a DISKPREP'd Compact Flash.
    > However, I am unable to establish any connection to the device under
    > VS2005 using the remote tools or the debugger.
    >
    > * I have enabled the kernel debugger and KITL in the build options.
    > * I have included the Target Control Support (SYSGEN_SHELL).
    > * Host and Device are using DHCP and have aquired IP addresses.
    > * Host and Device can ping each other.
    > * Target is x86 ITOX NP101.
    >
    >
    > Do I need more components included in my build? Could it be a problem
    > running the host under a Virtual PC? Are there any components I can
    > include in my build that would help?
    >
    > (I am new to Windows CE.)
    >
    > --Greg
    >
     
    Usually running the host in a virtual environment isn't an issue, but
    you should check that the networking has been set-up in the right way.
    This means net adapter in bridged mode on the host, no Windows Firewall
    or other FW software stopping PB network traffic etc.
    You can download the OS image but not connect with KITL or you can't
    even download?
     

    Valter Minute
    Windows Embedded MVP
    http://geekswithblogs.net/WindowsEmbeddedCookbook
    Friday, June 3, 2011 3:29 PM
  • I cannot download or connect in any way to the device.

    The firewalls on the virtual machine and the host machine are both disabled.

    The virtual machine network is configured in bridged mode.

     

    How do the debugger and the device establish connection? The only traffic is see from the device is the ARP/DHCP requests.

     

     

    Friday, June 3, 2011 4:26 PM
  • I have attached a serial port and discovered much debugging spam!

    Can anyone tell me what debugging messages I could look for to help my problem? I want to be sure that the KITL is initialized and attached to an ethernet driver. I think?

    Some examples:

    KD: Starting kernel debugger software probe (KdStub) - KD API version 22
    Calling KDEnableInt (FALSE, NULL) without previously calling KDEnableInt (FALSE, p)

    PCIReg(key: Drivers\BuiltIn\PCI\Instance\KITL, device: 0/0/0)
    Override Serial Driver: serial debug output selected on COM port 1, disabling serial driver for that port.
    Override Serial Driver: No COM port selected for serial KITL transport, no override necessary.

    DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE1) last 61 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\KITL\DllName) returned 2
    DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCI\Instance\KITL'
    DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI\Instance\KITL) last 55 TicksDeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) l
    ast 9542 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\AFD\Prefix) returned 2

    InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = 0, dwIoBase = 0, dwDfltType = 1) ...
    Intel(R) PRO/1000 KITL driver [Build: Jun  2 2011  14:59:12]
    Intel(R) PRO/1000 KITL driver [Build: Jun  2 2011  14:59:12]
    Intel(R) PRO/1000 KITL driver [Build: Jun  2 2011  14:59:12]
    Intel(R) PRO/1000 KITL driver [Build: Jun  2 2011  14:59:12]

     

    Friday, June 3, 2011 10:00 PM
  • On 6/4/2011 12:00 AM, gloucks wrote:
    > I have attached a serial port and discovered much debugging spam!
    >
    > Can anyone tell me what debugging messages I could look for to help my
    > problem? I want to be sure that the KITL is initialized and attached to
    > an ethernet driver. I think?
    >
    > Some examples:
    >
    > KD: Starting kernel debugger software probe (KdStub) - KD API version 22
    > Calling KDEnableInt (FALSE, NULL) without previously calling KDEnableInt
    > (FALSE, p)
    >
    > PCIReg(key: Drivers\BuiltIn\PCI\Instance\KITL, device: 0/0/0)
    > Override Serial Driver: serial debug output selected on COM port 1,
    > disabling serial driver for that port.
    > Override Serial Driver: No COM port selected for serial KITL transport,
    > no override necessary.
    >
    > DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE1)
    > last 61 TicksDEVICE!RegReadActivationValues
    > RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\KITL\DllName) returned 2
    > DEVICE!I_ActivateDeviceEx: can't find all required activation values in
    > 'Drivers\BuiltIn\PCI\Instance\KITL'
    > DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI\Instance\KITL) last 55
    > TicksDeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) l
    > ast 9542 TicksDEVICE!RegReadActivationValues
    > RegQueryValueEx(Drivers\BuiltIn\AFD\Prefix) returned 2
    >
    > InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = 0, dwIoBase = 0,
    > dwDfltType = 1) ...
    > Intel(R) PRO/1000 KITL driver [Build: Jun 2 2011 14:59:12]
    > Intel(R) PRO/1000 KITL driver [Build: Jun 2 2011 14:59:12]
    > Intel(R) PRO/1000 KITL driver [Build: Jun 2 2011 14:59:12]
    > Intel(R) PRO/1000 KITL driver [Build: Jun 2 2011 14:59:12]
    >
     
    This output looks like output from an image starting on your device.
    It seems that the device tries to boot a local image and does not try to
    download it from PB.
    You should be able to configure this using the serial menu of the loader.
    Eboot downloads an image from PB using TFTP.
     

    Valter Minute
    Windows Embedded MVP
    http://geekswithblogs.net/WindowsEmbeddedCookbook
    Saturday, June 4, 2011 7:48 AM
  • Perhaps I am misunderstanding something. I am booting my NK.BIN from a DISKPREP'd CompactFlash drive. Do I have to use Eboot to be able to use the kernel debugger? If so, how do I configure the BOOT.INI to use Eboot?

    It seems to me that there are two different boot processes: 1. LOADCEPC, which runs on a DOS formatted drive and is targetted more for development of the BSP, and 2. DISKPREP'd CE drive, which boots my image directly. I am not using LOADCEPC, but perhaps I need to use that to connect to my device?

    Greg.

    Tuesday, June 7, 2011 3:46 PM
  • According to this thread: http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/f0bb21bf5c838460, I am probably missing KITL support for my ethernet driver, since I am using the RTL8111C. Could this explain my lack of communication?

    Greg.

    Tuesday, June 7, 2011 9:26 PM