hello all,

i am designing an EDBG library for Intel82559 card with modules:
InitDMABuffer, InitNIC, SendFrame, GetFrame, EnableInterrupt,
DisableInterrupt, GetpendingInterrupt. it is working upto downloading
of the OS. but after that, initialization of KITL is failing. serial
debug message is showing error in InitKitl funtion.

what might be the condition causing the failure of InitKitl()?

the serial debug messages is


In Creating name1
In Creating name2
In Creating name3
OALKitlCreateName: Using Device Name 'CEPC8426'
KITL: *** Device Name CEPC8426 ***
ERROR: OALKitlInit: KitlInit failed
CEPC Firmware Init
RTC - Status Reg B - 0x02
g_dwCPUFeatures = bfebfbff
g_nMtrrCnt = 8
MTRR PhysMask0: 0000000fe0000800
MTRR PhysBase0: 0000000000000006
MTRR PhysMask1: 0000000ffff80800
................
...........


waiting for reply

Re: OALKitlInit: KitlInit failed by Piet

Piet
Fri Oct 28 03:55:29 CDT 2005


Possibly because your OEMKitlInit fails. This is called by KitlInit.

It would be a good idea to check the private code, all of this can be
found under C:\WINCE500\PRIVATE\WINCEOS\COREOS\NK.

Regards,
Piet



mona schreef:

> hello all,
>
> i am designing an EDBG library for Intel82559 card with modules:
> InitDMABuffer, InitNIC, SendFrame, GetFrame, EnableInterrupt,
> DisableInterrupt, GetpendingInterrupt. it is working upto downloading
> of the OS. but after that, initialization of KITL is failing. serial
> debug message is showing error in InitKitl funtion.
>
> what might be the condition causing the failure of InitKitl()?
>
> the serial debug messages is
>
>
> In Creating name1
> In Creating name2
> In Creating name3
> OALKitlCreateName: Using Device Name 'CEPC8426'
> KITL: *** Device Name CEPC8426 ***
> ERROR: OALKitlInit: KitlInit failed
> CEPC Firmware Init
> RTC - Status Reg B - 0x02
> g_dwCPUFeatures = bfebfbff
> g_nMtrrCnt = 8
> MTRR PhysMask0: 0000000fe0000800
> MTRR PhysBase0: 0000000000000006
> MTRR PhysMask1: 0000000ffff80800
> ................
> ...........
>
>
> waiting for reply


RE: OALKitlInit: KitlInit failed by anonymous

anonymous
Sun Oct 30 07:46:02 CST 2005

I think more than likely you're not getting send packets returned back to the
stack.

You get packets from the stack you are to send out. When they are either
sent out, rejected, or whatever, you have to return them to the stack.
Something about that return process is most likely broken.


"mona" wrote:

> hello all,
>
> i am designing an EDBG library for Intel82559 card with modules:
> InitDMABuffer, InitNIC, SendFrame, GetFrame, EnableInterrupt,
> DisableInterrupt, GetpendingInterrupt. it is working upto downloading
> of the OS. but after that, initialization of KITL is failing. serial
> debug message is showing error in InitKitl funtion.
>
> what might be the condition causing the failure of InitKitl()?
>
> the serial debug messages is
>
>
> In Creating name1
> In Creating name2
> In Creating name3
> OALKitlCreateName: Using Device Name 'CEPC8426'
> KITL: *** Device Name CEPC8426 ***
> ERROR: OALKitlInit: KitlInit failed
> CEPC Firmware Init
> RTC - Status Reg B - 0x02
> g_dwCPUFeatures = bfebfbff
> g_nMtrrCnt = 8
> MTRR PhysMask0: 0000000fe0000800
> MTRR PhysBase0: 0000000000000006
> MTRR PhysMask1: 0000000ffff80800
> .................
> ............
>
>
> waiting for reply
>
>

Re: OALKitlInit: KitlInit failed by mona

mona
Fri Nov 04 04:21:23 CST 2005

hello all,

thanks a lot for all your generous response. i have overcome the
problem of kitl failure at that stage. the reception module had some
problem.

however i have again got stuck in the next step. during kitl
initialization, it needs renewing of IP address when it is provided by
DHCP. by putting some debug strings i came to know that but it was
failing there. the following debug messages were coming.

.......................
In Creating name3
OALKitlCreateName: Using Device Name 'CEPC8426'
KITL: *** Device Name CEPC8426 ****
ETH82559GetFrame(): RU is in NO RESOURCE STATE
ETH82559GetFrame(): RU is in NO RESOURCE STATE
VBridge:: built on [Aug 24 2005] time [11:53:00]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA03E0280] to [0xA03E4280].
Rx buffer [0xA03E42A0] to [0xA03E82A0].
VBridge:: NK add MAC: [0-D0-B7-17-20-EA]
ERROR: OALKitlInit: KitlInit failed
CEPC Firmware Init

just to bring it into working condition, i tried with the static
address. with static address it passes this step but gets stuck as
following.

Tx buffer [0xA03E0280] to [0xA03E4280].
Rx buffer [0xA03E42A0] to [0xA03E82A0].
VBridge:: NK add MAC: [0-D0-B7-17-20-EA]
KITL: Connected host IP: 10.50.41.26 Port: 2171
KeyIndex 0 = -1
KeyIndex 1 = -1
KeyIndex 2 = -1
KeyIndex 3 = -1
KeyIndex 4 = -1
KeyIndex 5 = -4194305
KeyIndex 6 = -4194305
KeyIndex 7 = -1
+KITLRegisterDfltClient, service:0
+KITLRegisterDfltClient, service:1
KITLGlobalState == 0x61
Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0
ProcessAdminMsg: Receive Config message for service PPSH
ETH82559SendFrame() :: !
ProcessAdminMsg: Receive Config message for service DBGMSG
ETH82559SendFrame() :: !
ProcessAdminMsg: Receive Config message for service PPSH
ETH82559SendFrame() :: !
ProcessAdminMsg: Receive Config message for service DBGMSG

it keeps on calling SendFrame( ). and does not receive
"KITLRegisterDfltClient, service:2 "/ Config message for KDBG.

the statistical counter is showing that frames are being received from
wire. and since the same SendFrame and GetFrame modues are used for
boot loading also, and they are working well there (since it sends
boot-me packet and downloads the image from host system) i could not
configure out the problem.

waiting for reply.


Re: OALKitlInit: KitlInit failed by mona

mona
Thu Nov 10 00:32:34 CST 2005

Hi
the problem of continuous calling of SendFrame( ) and GetFrame( ), as i
mentioned in my last mail, has been solved by creating a significant
amount of dealy in sending a frame. after this, the Kitl debugger is
also initialized. but after getting the OEMAddressTable address, it
stops abruptly.

although it registers the services PPSH and DBGMSG, it is not getting
the service for KDBG. i have not changed anything in config.bib neither
in OEMAddresstable. with the same setting RTL card works fine.



the kitl debugger output is as follows

TID:0 CEPC Firmware Init
TID:0 RTC - Status Reg B - 0x02
TID:0 g_dwCPUFeatures = bfebfbff
TID:0 g_nMtrrCnt = 8
TID:0 MTRR PhysMask0: 0000000fe0000800
TID:0 MTRR PhysBase0: 0000000000000006
TID:0 MTRR PhysMask1: 0000000ffff80800
TID:0 MTRR PhysBase1: 000000001f780000
TID:0 MTRR PhysMask2: 0000000fff800800
TID:0 MTRR PhysBase2: 000000001f800000
TID:0 MTRR PhysMask3: 0000000000000000
TID:0 MTRR PhysBase3: 0000000000000000
TID:0 MTRR PhysMask4: 0000000000000000
TID:0 MTRR PhysBase4: 0000000000000000
TID:0 MTRR PhysMask5: 0000000000000000
TID:0 MTRR PhysBase5: 0000000000000000
TID:0 MTRR PhysMask6: 0000000000000000
TID:0 MTRR PhysBase6: 0000000000000000
TID:0 MTRR PhysMask7: 0000000000000000
TID:0 MTRR PhysBase7: 0000000000000000
TID:0 PhysMask0: 0000000fe0000800
TID:0 PhysMask1: 0000000ffff80800
TID:0 PhysMask2: 0000000fff800800
TID:0 PhysMask3: 0000000000000000
TID:0 PhysMask4: 0000000000000000
TID:0 PhysMask5: 0000000000000000
TID:0 PhysMask6: 0000000000000000
TID:0 PhysMask7: 0000000000000000
TID:0 g_nMtrrInuse = 3
TID:0 OEM Extra DRAM Detected @ base = xA1C00000, size=36 MB
TID:0 Looking for rom chain
TID:0 Rom chain NOT found
TID:0 Firmware Init Done.
TID:0 Error Reporting Memory Reserved, dump size = 00020000
TID:0 Booting Windows CE version 5.00 for (x86)
TID:0 &pTOC = 80227a08, pTOC = 802ce75c, pTOC->ulRamFree = 80406000,
MemForPT = 00004000
TID:0
Old or invalid version stamp in kernel structures - starting clean!
TID:0 Configuring: Primary pages: 15313, Secondary pages: 0, Filesystem
pages = 7656
TID:0
Booting kernel with clean memory configuration:
TID:0 Memory Sections:
TID:0 [0] : start: 8040b000, extension: 00004000, length: 03bd1000
TID:0 X86Init done, OEMAddressTable = 8023e318.

Please help if any of you has
any idea of this problem.


mona wrote:
> hello all,
>
> thanks a lot for all your generous response. i have overcome the
> problem of kitl failure at that stage. the reception module had some
> problem.
>
> however i have again got stuck in the next step. during kitl
> initialization, it needs renewing of IP address when it is provided by
> DHCP. by putting some debug strings i came to know that but it was
> failing there. the following debug messages were coming.
>
> .......................
> In Creating name3
> OALKitlCreateName: Using Device Name 'CEPC8426'
> KITL: *** Device Name CEPC8426 ****
> ETH82559GetFrame(): RU is in NO RESOURCE STATE
> ETH82559GetFrame(): RU is in NO RESOURCE STATE
> VBridge:: built on [Aug 24 2005] time [11:53:00]
> VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
> Tx buffer [0xA03E0280] to [0xA03E4280].
> Rx buffer [0xA03E42A0] to [0xA03E82A0].
> VBridge:: NK add MAC: [0-D0-B7-17-20-EA]
> ERROR: OALKitlInit: KitlInit failed
> CEPC Firmware Init
>
> just to bring it into working condition, i tried with the static
> address. with static address it passes this step but gets stuck as
> following.
>
> Tx buffer [0xA03E0280] to [0xA03E4280].
> Rx buffer [0xA03E42A0] to [0xA03E82A0].
> VBridge:: NK add MAC: [0-D0-B7-17-20-EA]
> KITL: Connected host IP: 10.50.41.26 Port: 2171
> KeyIndex 0 = -1
> KeyIndex 1 = -1
> KeyIndex 2 = -1
> KeyIndex 3 = -1
> KeyIndex 4 = -1
> KeyIndex 5 = -4194305
> KeyIndex 6 = -4194305
> KeyIndex 7 = -1
> +KITLRegisterDfltClient, service:0
> +KITLRegisterDfltClient, service:1
> KITLGlobalState == 0x61
> Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0
> ProcessAdminMsg: Receive Config message for service PPSH
> ETH82559SendFrame() :: !
> ProcessAdminMsg: Receive Config message for service DBGMSG
> ETH82559SendFrame() :: !
> ProcessAdminMsg: Receive Config message for service PPSH
> ETH82559SendFrame() :: !
> ProcessAdminMsg: Receive Config message for service DBGMSG
>
> it keeps on calling SendFrame( ). and does not receive
> "KITLRegisterDfltClient, service:2 "/ Config message for KDBG.
>
> the statistical counter is showing that frames are being received from
> wire. and since the same SendFrame and GetFrame modues are used for
> boot loading also, and they are working well there (since it sends
> boot-me packet and downloads the image from host system) i could not
> configure out the problem.
>
> waiting for reply.