Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 16 Jul 2004 02:37 PM by  cdwhatley
KITL Send Timeout during WinCE OS boot
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
cdwhatley
New Member
New Member
Posts:8


--
14 Jul 2004 02:29 PM
    Just today, I started playing with the Zoom Starter Kit. I found the LoCE Windows CE BSP Quick Start Guide and started stepping through it. I was able to get the "Tiny Kernel" example running the first time I tried -- beginner's luck I guess. The end result was that Platform Builder 4.2 displayed a window on the left that had a Window CE prompt.

    Well, it was all downhill after that. I tried to repeat the process and ended up getting the following error:

    0xC1BF1F8E: KITLSend(0): Timed out waiting for ack (AckExpected: 24, TxSeq: 3255
    170512)

    This error occurred after everything seemed to boot OK (I got all the messages listed in Figure 16 of the Quick Start Guide). However, the Window CE prompt did not appear in Platform Builder and I started getting a stream of these KITL error messages.

    I had some trouble with my boot string in EEPROM and overwrote it a few times. I think I ran out of room one time and other times the CR-LF must have not been in at the end of the exec command. Anyway, I finally got one in there and here it is:

    echo "exec dbg_serial:A400_UART:dbg_enet:91C111:dbg_enet_base:0x70000000:dbg_enet_irq:0x00000007:share_eth:1" /dev/serial_eeprom


    I'm now seeing the following error -- after seeing many KITL errors spewed out on LoLo:

    Error! no room in packet list
    pckt_list_insert() -- no room

    Thanks in advance for any help.
    cdwhatley
    New Member
    New Member
    Posts:8


    --
    15 Jul 2004 01:59 PM
    More information - a dump of the Platform Builder messages while attempting to boot WinCE on Zoom Starter Kit:


    I got 2 errors in the output:
    -1- 4294767812 PID:e1be923e TID:e1beefda 0x81be9000: Initobj : Error, continuing (1)...
    -2- 4294767299 PID:1bff002 TID:1bff262 0x81bff024: Detecting VFP...
    4294767300 PID:1bff002 TID:1bff262 0x81bff024: VFP Not Found!

    I have no clue what either of them mean.

    Below is the entire PB output...

    Kernel debugger is waiting to connect with target.
    0 PID:0 TID:0 Booting Windows CE version 4.20 for (ARM)
    0 PID:0 TID:0 &pTOC = 800e16ac, pTOC = 80244a6c, pTOC->ulRamFree = 8103a000, MemForPT = 00000000
    0 PID:0 TID:0
    Old or invalid version stamp in kernel structures - starting clean!
    0 PID:0 TID:0 Configuring: Primary pages: 3012, Secondary pages: 0, Filesystem pages = 1506
    0 PID:0 TID:0
    Booting kernel with clean memory configuration:
    0 PID:0 TID:0 Memory Sections:
    0 PID:0 TID:0 [0] : start: 8103b000, extension: 00001000, length: 00bc4000
    0 PID:0 TID:0 Sp=ffffc7cc
    1 PID:0 TID:0 Windows CE KernelInit
    4294767296 PID:1bff002 TID:1bff262 Updated eptr->e32_vsize to = 000a2000
    4294767297 PID:1bff002 TID:1bff262 Scheduling the first thread.
    4294767298 PID:1bff002 TID:1bff262 0x81bff024: KernelInit2: pCurThread=81bff024 hCurThread=01bff262 hCurProc=01bff002, KernelInit = 80115c78
    4294767299 PID:1bff002 TID:1bff262 0x81bff024: Detecting VFP...
    4294767300 PID:1bff002 TID:1bff262 0x81bff024: VFP Not Found!
    4294767301 PID:1bff002 TID:1bff262 0x81bff024: Updated eptr->e32_vsize to = 00016000
    4294767302 PID:1bff002 TID:1bff262 0x81bff024: Debugger 'kd.dll' loaded
    4294767303 PID:1bff002 TID:1bff262 0x81bff024: Entering ConnectDebugger
    4294767307 PID:1bff002 TID:1bff262 0x81bff024: >>> Loading module NK.EXE at address 0x800E0000-0x80182000 (RW data at 0x81006000-0x810330EB)
    Kernel debugger connected (KDBG stream opened).
    Kernel Version 1169 loaded at 0x800e0000, data relocated at 0x81006000
    Debugger connection established (Target CPU is ARM).
    Loaded symbols for 'C:\WINCE420\PUBLIC\TEST_TINYKERNEL\RELDIR\LOCE_A400_REL_101DEBUG\NK.EXE'
    Loaded symbols for 'C:\WINCE420\PUBLIC\TEST_TINYKERNEL\RELDIR\LOCE_A400_REL_101DEBUG\KD.DLL'
    Finished re-loading kernel modules.
    4294767315 PID:1bff002 TID:1bff262 0x81bff024: first = 01ff0000, last = 02000000, SharedDllBase = 03f50000
    4294767356 PID:1bff002 TID:1bff262 0x81bff024: >>> Loading module coredll.dll at address 0x03F90000-0x03FFC000 (RW data at 0x01FFF000-0x01FFF810)
    Loaded symbols for 'C:\WINCE420\PUBLIC\TEST_TINYKERNEL\RELDIR\LOCE_A400_REL_101DEBUG\COREDLL.DLL'
    4294767430 PID:e1be923e TID:e1beefda 0x81be9000: >>> Loading module filesys.exe at address 0x04010000-0x0405E000
    Loaded symbols for 'C:\WINCE420\PUBLIC\TEST_TINYKERNEL\RELDIR\LOCE_A400_REL_101DEBUG\FILESYS.EXE'
    4294767439 PID:e1be923e TID:e1beefda 0x81be9000: FileSystem Starting - starting with clean file system
    4294767718 PID:e1be923e TID:e1beefda 0x81be9000: >>> Loading module fsdmgr.dll at address 0x03F50000-0x03F6C000 (RW data at 0x01FF9000-0x01FF9754)
    Loaded symbols for 'C:\WINCE420\PUBLIC\TEST_TINYKERNEL\RELDIR\LOCE_A400_REL_101DEBUG\FSDMGR.DLL'
    4294767738 PID:e1be923e TID:e1beefda 0x81be9000: >>> Loading module relfsd.dll at address 0x03F80000-0x03F8B000 (RW data at 0x01FFD000-0x01FFDABC)
    Loaded symbols for 'C:\WINCE420\PUBLIC\TEST_TINYKERNEL\RELDIR\LOCE_A400_REL_101DEBUG\RELFSD.DLL'
    4294767812 PID:e1be923e TID:e1beefda 0x81be9000: Initobj : Error, continuing (1)...
    4294768221 PID:e1be923e TID:e1beefda 0x81be9000: FSREG: Logging in default user.
    4294768222 PID:e1be923e TID:e1beefda 0x81be9000: SetCurrentUser: Logging out (nobody), logging in default
    4294768223 PID:e1be923e TID:e1beefda 0x81be9000: FS: Using default path "\profiles\"
    4294768225 PID:e1be923e TID:e1beefda 0x81be9000: SetCurrentUser: User hives not supported -- using same registry for all users
    4294768226 PID:e1be923e TID:e1beefda 0x81be9000: FS: Using default path "Windows\"
    4294768373 PID:e1be923e TID:e1beefda 0x81be9000: FS: Using default path "Windows\"
    4294768378 PID:e1be923e TID:e1beefda 0x81be9000: Filesystem initialized!
    cdwhatley
    New Member
    New Member
    Posts:8


    --
    16 Jul 2004 02:37 PM
    Don't know how it worked the first time, but I had the Ethernet IRQ setting wrong for my SDK every time I tried it. I have a Rev A SDK. The settings for each Rev are as follows:

    RevA -- dbg_enet_irq:0x0000001A
    Rev B -- dbg_enet_irq:0x00000007

    The example in the Quick Start Guide uses the Rev B setting. It doesn't specify that this setting is for Rev B. The manual should be corrected to give the values for both board Revs.

    Since by Ethernet IRQ setting was wrong, KITL could not communicate from the WinCE OS on the target to the Platform Builder debugger.
    You are not authorized to post a reply.