WinCE Kernel init problem

Tutorials Win: Microsoft Windows Forum

Hi,
I'm developing a Win CE platform for my Strong ARM target.
In Platform Builder Debug Windows I obtain :

Kernel debugger is waiting to connect with target.
0 PID:0 TID:0 ProcessorType=0b11 Revision=9
0 PID:0 TID:0 sp_abt=ffff5000 sp_irq=ffff2800
sp_undef=ffffc800 OEMAddressTable = 8c141018
0 PID:0 TID:0 +OEMInit
0 PID:0 TID:0 Windows CE Firmware Init
0 PID:0 TID:0 Stack=0xFFFFC79C
0 PID:0 TID:0 Initialize timer used for delays in
the HAL
0 PID:0 TID:0 InitClock...
0 PID:0 TID:0 Initialize driver globals area...
0 PID:0 TID:0 Firmware Init Done.
0 PID:0 TID:0 -OEMInit
0 PID:0 TID:0 Sp=ffffc7cc

On serial port I obtain:
...
Stack=8C067FA8h

Jumping to Physical Address 0xC0141000h (Virtual Address
0x8C141000h)...


+OEMKitlInit
Stack=FFFFC768h
CS8900: MAC Address: 22:0:33:0:44:0 iobase:0xa7000300
membase:0xa6000000
INFO: Probe: CS8900 is detected.
INFO: CS8900_IO_MODE
INFO: Init: CS8900_Init OK.
::: OEMEthInit() IP Address : 10.21.4.228
::: OEMEthInit() Netmask : 255.255.255.0
Device HANDBOX17408, IP 10.21.4.228, Port 981
Calling EdbgInitDHCP
-OEMKitlInit
Host connected
Host IP: 10.21.4.89, port 1307
KITLGlobalState == 0x61
KITL Initialized
Windows CE Kernel for ARM Built on Mar 13 2003 at
22:54:19


OEMInit seems OK.
I have same doubt about the value of stack pointer
Sp=ffffc7cc. Is it correct ?

After OEMInit, what function is called by kernel ?

Is the problem only an insufficient stack size ? (before
calling Kernel start I make
...
ldr r0, =DRAM_BANK1A_C_VIRTUAL
add sp, r0, #0x61000

mov r0, pc
add r0, pc, #OEMAddressTable-(.+8);

bl KernelStart
)


Thanks

Best Regards
Dario
Top

Re: WinCE Kernel init problem by sc

sc
Thu Sep 25 07:39:06 CDT 2003

I have a similar problem and I haven't figure out why yet.
I posted my problem on 9-22, but there was no answer.

suprise, SP= is your cputype not your stack pointer!
Take a look at mdarm.c's ARMInit().
==> NKDbgPrintfW(L"Sp=%8.8x\r\n", &cpuType);
After I build a debug version, it went as far as
NK Kernel: DEBUGCHK failed in file
c:\talisker2\private\winceos\coreos\nk\kernel
\schedule.c at line 659
which is DEBUGCHK (!pth->pUpSleep); in schedule.c's RunqDequeue(), which
doesn't tell me anything.

hope this help you a bit. Please let me know if you figure anything out.
I'm using CE.NET 4.0, cpu=Sharp Bluestreak(ARM core)



"dario73" <dario.getto@erxa.it> wrote in message
news:0bc801c38352$6a8ae3f0$a001280a@phx.gbl...
> Hi,
> I'm developing a Win CE platform for my Strong ARM target.
> In Platform Builder Debug Windows I obtain :
>
> Kernel debugger is waiting to connect with target.
> 0 PID:0 TID:0 ProcessorType=0b11 Revision=9
> 0 PID:0 TID:0 sp_abt=ffff5000 sp_irq=ffff2800
> sp_undef=ffffc800 OEMAddressTable = 8c141018
> 0 PID:0 TID:0 +OEMInit
> 0 PID:0 TID:0 Windows CE Firmware Init
> 0 PID:0 TID:0 Stack=0xFFFFC79C
> 0 PID:0 TID:0 Initialize timer used for delays in
> the HAL
> 0 PID:0 TID:0 InitClock...
> 0 PID:0 TID:0 Initialize driver globals area...
> 0 PID:0 TID:0 Firmware Init Done.
> 0 PID:0 TID:0 -OEMInit
> 0 PID:0 TID:0 Sp=ffffc7cc
>
> On serial port I obtain:
> ...
> Stack=8C067FA8h
>
> Jumping to Physical Address 0xC0141000h (Virtual Address
> 0x8C141000h)...
>
>
> +OEMKitlInit
> Stack=FFFFC768h
> CS8900: MAC Address: 22:0:33:0:44:0 iobase:0xa7000300
> membase:0xa6000000
> INFO: Probe: CS8900 is detected.
> INFO: CS8900_IO_MODE
> INFO: Init: CS8900_Init OK.
> ::: OEMEthInit() IP Address : 10.21.4.228
> ::: OEMEthInit() Netmask : 255.255.255.0
> Device HANDBOX17408, IP 10.21.4.228, Port 981
> Calling EdbgInitDHCP
> -OEMKitlInit
> Host connected
> Host IP: 10.21.4.89, port 1307
> KITLGlobalState == 0x61
> KITL Initialized
> Windows CE Kernel for ARM Built on Mar 13 2003 at
> 22:54:19
>
>
> OEMInit seems OK.
> I have same doubt about the value of stack pointer
> Sp=ffffc7cc. Is it correct ?
>
> After OEMInit, what function is called by kernel ?
>
> Is the problem only an insufficient stack size ? (before
> calling Kernel start I make
> ...
> ldr r0, =DRAM_BANK1A_C_VIRTUAL
> add sp, r0, #0x61000
>
> mov r0, pc
> add r0, pc, #OEMAddressTable-(.+8);
>
> bl KernelStart
> )
>
>
> Thanks
>
> Best Regards
> Dario
>
>
>
>
>
>
>


Top

Re: WinCE Kernel init problem by Karel

Karel
Tue Sep 30 22:30:02 CDT 2003

The SP value can be ok. I just didn't get your problem. Can you be more
specific?
--
Karel Danihelka
Windows CE Core OS
---
This posting is provided "AS IS" with not warranties, and confers no rights.
---
"dario73" <dario.getto@erxa.it> wrote in message
news:0bc801c38352$6a8ae3f0$a001280a@phx.gbl...
> Hi,
> I'm developing a Win CE platform for my Strong ARM target.
> In Platform Builder Debug Windows I obtain :
>
> Kernel debugger is waiting to connect with target.
> 0 PID:0 TID:0 ProcessorType=0b11 Revision=9
> 0 PID:0 TID:0 sp_abt=ffff5000 sp_irq=ffff2800
> sp_undef=ffffc800 OEMAddressTable = 8c141018
> 0 PID:0 TID:0 +OEMInit
> 0 PID:0 TID:0 Windows CE Firmware Init
> 0 PID:0 TID:0 Stack=0xFFFFC79C
> 0 PID:0 TID:0 Initialize timer used for delays in
> the HAL
> 0 PID:0 TID:0 InitClock...
> 0 PID:0 TID:0 Initialize driver globals area...
> 0 PID:0 TID:0 Firmware Init Done.
> 0 PID:0 TID:0 -OEMInit
> 0 PID:0 TID:0 Sp=ffffc7cc
>
> On serial port I obtain:
> ...
> Stack=8C067FA8h
>
> Jumping to Physical Address 0xC0141000h (Virtual Address
> 0x8C141000h)...
>
>
> +OEMKitlInit
> Stack=FFFFC768h
> CS8900: MAC Address: 22:0:33:0:44:0 iobase:0xa7000300
> membase:0xa6000000
> INFO: Probe: CS8900 is detected.
> INFO: CS8900_IO_MODE
> INFO: Init: CS8900_Init OK.
> ::: OEMEthInit() IP Address : 10.21.4.228
> ::: OEMEthInit() Netmask : 255.255.255.0
> Device HANDBOX17408, IP 10.21.4.228, Port 981
> Calling EdbgInitDHCP
> -OEMKitlInit
> Host connected
> Host IP: 10.21.4.89, port 1307
> KITLGlobalState == 0x61
> KITL Initialized
> Windows CE Kernel for ARM Built on Mar 13 2003 at
> 22:54:19
>
>
> OEMInit seems OK.
> I have same doubt about the value of stack pointer
> Sp=ffffc7cc. Is it correct ?
>
> After OEMInit, what function is called by kernel ?
>
> Is the problem only an insufficient stack size ? (before
> calling Kernel start I make
> ...
> ldr r0, =DRAM_BANK1A_C_VIRTUAL
> add sp, r0, #0x61000
>
> mov r0, pc
> add r0, pc, #OEMAddressTable-(.+8);
>
> bl KernelStart
> )
>
>
> Thanks
>
> Best Regards
> Dario
>
>
>
>
>
>
>


Top