none
ICOP eBox3310A: endless loop "KITLConnectToDesktop: Sending to CFG to desktop" RRS feed

  • Question

  • Hi

    I have a Compact 7-based OS image for ICOP eBox3310A .  If KITL is disabled everything boots fine.  But with KITL enabled the system is hung and endlessly emits the message that I quoted in this post's title.  (I can't seem to quote that line here as the parser keeps munging it up in the body of this message).

    Could anyone provide insight as to what I'm missing?.   Thanks.

    Here is the serial port output:

    Microsoft Windows CE Bootloader Common Library Version 1.4 Built Jan 30 2009 14:30:14
    Microsoft Windows CE Ethernet Bootloader 3.7 for CE/PC (Jan 30 2009)
    Boot Args @ 0x1E246 and  ucLoaderFlags is 1
    FlashInit
    -FlashInit:Fails!!!!
    PCI Device Configurations (1 PCI bus(es) present)...
    ========================================================
     Bus, Device, Function = 0, 3, 0
     Vendor ID, Device ID  = 0x18CA, 0x0020
     Base Class, Subclass  = 3, 0 => DISPLAY_CTLR
     Interrupt             = 0
     BaseAddress[0]        = 0xF8000000 (Memory)
     BaseAddress[1]        = 0xFEFC0000 (Memory)
     BaseAddress[2]        = 0xEF80 (I/O)
    ========================================================
     Bus, Device, Function = 0, 8, 0
     Vendor ID, Device ID  = 0x17F3, 0x6040
     Base Class, Subclass  = 2, 0 => NETWORK_CTLR
     Interrupt             = 10
     BaseAddress[0]        = 0xEC00 (I/O)
     BaseAddress[1]        = 0xFEFBB400 (Memory)
    ========================================================
     Bus, Device, Function = 0, 10, 0
     Vendor ID, Device ID  = 0x17F3, 0x6060
     Base Class, Subclass  = 12, 3 => SERIAL_BUS_CTLR
     Interrupt             = 11
     BaseAddress[0]        = 0xFEFB9000 (Memory)
    ========================================================
     Bus, Device, Function = 0, 10, 1
     Vendor ID, Device ID  = 0x17F3, 0x6061
     Base Class, Subclass  = 12, 3 => SERIAL_BUS_CTLR
     Interrupt             = 11
     BaseAddress[0]        = 0xFEFBB800 (Memory)
    ========================================================
     Bus, Device, Function = 0, 11, 0
     Vendor ID, Device ID  = 0x17F3, 0x6060
     Base Class, Subclass  = 12, 3 => SERIAL_BUS_CTLR
     Interrupt             = 11
     BaseAddress[0]        = 0xFEFBA000 (Memory)
    ========================================================
     Bus, Device, Function = 0, 11, 1
     Vendor ID, Device ID  = 0x17F3, 0x6061
     Base Class, Subclass  = 12, 3 => SERIAL_BUS_CTLR
     Interrupt             = 11
     BaseAddress[0]        = 0xFEFBBC00 (Memory)
    ========================================================
     Bus, Device, Function = 0, 12, 0
     Vendor ID, Device ID  = 0x17F3, 0x1011
     Base Class, Subclass  = 1, 1 => MASS_STORAGE_CTLR
     Interrupt             = 14
     BaseAddress[0]        = 0xEF00 (I/O)
     BaseAddress[1]        = 0xEE80 (I/O)
     BaseAddress[2]        = 0xEE00 (I/O)
     BaseAddress[3]        = 0xED80 (I/O)
     BaseAddress[4]        = 0xED00 (I/O)
    ========================================================
    InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = 0, dwIoBase = 0, dwDfltType = 1) ...
    InitKitlNIC: Found PCI Ethernet NIC (type = 10, IRQ=10, IOBase=0xEC00).
    R6040InitDMABuffer: 0x200000, 131072
    DRV.R6040Init
    R6040 Edbg driver for eboot and KITL debug mode.
    MAC Address:0:1b:eb:21:2c:88
    Returned MAC Address:00:1B:EB:21:2C:88
    System ready!
    Preparing for download...
    OEMPreDownload  ucLoaderFlags is 0
    x86KitlCreateName: Using Device Name 'VDX8611400'
    Using device name: VDX8611400
    Hit ENTER within 3 seconds to enter static IP address!InitDHCP():: Calling ProcessDHCP()
    ProcessDHCP()::DHCP_INIT
    Got Response from DHCP server, IP address: 192.168.60.202
    
    ProcessDHCP()::DHCP IP Address Resolved as 192.168.60.202, netmask: 255.255.255.0
    Lease time: 86400 seconds
    Got Response from DHCP server, IP address: 192.168.60.202
    No ARP response in 2 seconds, assuming ownership of 192.168.60.202
    +EbootSendBootmeAndWaitForTftp
    Sent BOOTME to 255.255.255.255
    Packet has the following data:
      boot.bin[NULL]octet[NULL]blksize[NULL]1024[NULL]
    TFTP packet could have 2 name/value pairs
    Locked Down Link 1
    Src IP 192.168.60.202 Port 03D4   Dest IP 192.168.60.201 Port DBAE
    Default TFTP block size set to: 512 bytes
    This TFTP packet contains 1 options.
    We currently only look at the first and expect it to be BLKSIZE.
    The packet's option name is blksize.
    The option's value is 1024
    with a value that is in range.
    BLKSIZE will be adjusted to 1024.
    EthDown::TFTPD_OPEN::boot.bin
    An OACK packet is the proper acknowledgement
    -EbootSendBootmeAndWaitForTftp
    
    BL_IMAGE_TYPE_BIN
    
    
    Download file information:
    -----------------------------------------------------
    [0]: Address=0x220000  Length=0x35C10E4  Name=
    
    ****** OEMVerifyMemory Checking Range [ 0x220000 ==> 0x37E10E3 ]
    ****** RAM Address ******
    
    rom_offset=0x80000000.
    ImageStart = 0x220000, ImageLength = 0x35C10E4, LaunchAddr = 0x226940
    
    Completed file(s):
    -------------------------------------------------------------------------------
    [0]: Address=0x220000  Length=0x35C10E4  Name="" Target=RAM
    ROMHDR at Address 00220044h
    OEMLaunch   ucLoaderFlags is 7
    Download successful! Jumping to image at 00226940h...
    Got EDBG_CMD_JUMPIMG
    Got EDBG_CMD_CONFIG, flags:0x00000000
    NAND_FLASH with g_bDownloadImage=1 ,  pBootArgs->ucLoaderFlags=7
    Lauch Windows CE from address 0x226940
    Debug Serial Init
    
    SysInit: GDTBase=8382c000 IDTBase=83830c00 KData=837e9800
    Windows CE Kernel for i486 Built on Sep  5 2012 at 14:21:16
    InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = A, dwIoBase = EC00, dwDfltType = 10) ...
    InitKitlNIC: Found PCI Ethernet NIC (type = 10, IRQ=10, IOBase=0xEC00).
    Using a KITL device on the PCI bus, not a legacy device.
    DeviceId................. VDX86
    pArgs->flags............. 0x2D
    pArgs->devLoc.IfcType.... 5
    pArgs->devLoc.LogicalLoc. 0x800
    pArgs->devLoc.PhysicalLoc 0x0
    pArgs->devLoc.Pin........ 10
    pArgs->ip4address........ 192.168.60.202
    pDevice->Name............ VDX
    pDevice->ifcType......... 5
    pDevice->id.............. 0x604017F3
    pDevice->resource........ 0
    pDevice->type............ 2
    pDevice->pDriver......... 0x837EB074
    g_kitlLock = 0x83810740
    DMA Buffer [FFFFFFFF, FFFFFFFF]
    DMA Buffer [A38198E0] pa[38198E0] UA=>CA[838198E0] CA=>UA[A38198E0]
    R6040InitDMABuffer: 0xa38198e0, 65536
    DRV.R6040Init
    R6040 Edbg driver for eboot and KITL debug mode.
    MAC Address:0:1b:eb:21:2c:88
    x86KitlCreateName: Using Device Name 'VDX86RD11400'
    OALKitlCreateName: Using Device Name 'VDX86RD11400'
    KITL: *** Device Name VDX86RD11400 ***
    KITL: using sysintr 0x10
    KITL will run in interrupt mode
    DHCP Renew successful, IP = 192.168.60.202, Lease time = 43200 seconds
    KITL: DHCP get device IP: 192.168.60.202
    VBridge:: built on [Oct 22 2012] time [16:13:56]
    VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
    Tx buffer [0x838118A0] to [0x838158A0].
    Rx buffer [0x838158C0] to [0x838198C0].
    VBridge:: NK add MAC: [0-1B-EB-21-2C-88]
    Connecting to Desktop
     KITLConnectToDesktop: Including 12 bytes of custom transport config data.
     KITLConnectToDesktop: Encoding packet
     KITLConnectToDesktop: Sending to CFG to desktop
     KITLConnectToDesktop: Sending to CFG to desktop
     KITLConnectToDesktop: Sending to CFG to desktop
     KITLConnectToDesktop: Sending to CFG to desktop
     KITLConnectToDesktop: Sending to CFG to desktop
     KITLConnectToDesktop: Sending to CFG to desktop
     KITLConnectToDesktop: Sending to CFG to desktop
     KITLConnectToDesktop: Sending to CFG to desktop
     KITLConnectToDesktop: Sending to CFG to desktop
     KITLConnectToDesktop: Sending to CFG to desktop
    





    • Edited by jeffcarey Monday, October 22, 2012 9:47 PM
    Monday, October 22, 2012 9:35 PM

All replies

  • Hi,

     Actually, you should decide - to use or not the KITL connection.
    If yes, it needs to adjust "connectivity options" to use KITL as a kernel transport.


    • Edited by iShust Tuesday, October 23, 2012 8:12 AM
    Tuesday, October 23, 2012 8:07 AM
  • Thanks, iShust.
    In fact, it turned out to be necessary to update the Ethernet bootloader on the device. The one there worked for CE 6, but not in this situation.
    It's working now.

    Wednesday, October 24, 2012 11:12 AM