Re: error wince600 boot message after dowload PB6 OS to HW board

It is getting rather far in the bootup, which is good.

Exception 'Access Violation' (2): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'

I would suspect that you have a memory layout problem, either the bootloader is using memory that is clobbering the downloaded image in some way, or the memory layout in the config.bib is wrong. Also somethign in OEMInit (or a call fro mit may be clobbering RAM too.

Try to boot a really small NK image to start with and take it from there.




"vincent" <vincent.tsai@xxxxxxxxxxxxxx> wrote in message news:OfPfMsZ5IHA.1176@xxxxxxxxxxxxxxxxxxxxxxx
Hi:

we migrate our BSP from wce500 to wce600.
after i build this bsp successfully in wce600 then download the boot.nb0 to my board.
the bootloader can bootup OK and print out menu and message on UART terminal.
then bootloader connect winth PC'sPB6 to download OS image.
then the error message printed from OS as the following:

hope anyone can tell us what (why) thuis error is.

Thnaks and BR

vincent



======>

ImageStart = 0x80001000, ImageLength = 0x2D3C658, LaunchAddr = 0x80001004

Computing checksum: image start = 0x80001000, len = 0x2D3C658

Checksum = 0xB3E069A2 (0x2D3C658 bytes)



Completed file(s):

-------------------------------------------------------------------------------

[0]: Address=0x80001000 Length=0x2D3C658 Name="" Target=FLASH

+OEMWriteFlash: ulAddr=0x80001000, ulSize=0x02d3c658

-OEMWriteFlash: Write Flash Done

ROMHDR at Address 80001044h

+OEMLaunch

Got EDBG_CMD_JUMPIMG

Got EDBG_CMD_CONFIG, flags:0x00000000

-OEMLaunch: Jumping to Address 0x80001000

Windows CE Kernel for MIPS Built on Sep 30 2007 at 22:35:49

INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb

+++ OEMInit()

+OALInterruptInit

+++ OALTimerInit()

OALTimerInit(): g_oalTimer.actualMSecPerSysTick = 0x1

-OEMInit

Error Reporting Memory Reserved, dump size = 00020000

Setting up softlog at 0x83843800 for 0x800 entries

Booting Windows CE version 6.00 for (MIPS32)

MIPS16 Instructions NOT Supported

&pTOC = 82d8ba10, pTOC = 82d3b66c, pTOC->ulRamFree = 82da1000, MemForPT = 00000000



Old or invalid version stamp in kernel structures - starting clean!

Configuring: Primary pages: 2719, Secondary pages: 0, Filesystem pages = 1276



Booting kernel with clean memory configuration:

Memory Sections:

[0] : start: 82da2000, extension: 00002000, length: 00a9f000

Windows CE KernelInit

Reserve VM for kernel XIP DLls, first = c0010000, last = c10a0000

g_pprcNK == 0x82d86a84

Updated eptr->e32_vsize to = 00014000

Initializing Memory Mapped File Support

Scheduling the first thread.

OALTimerIntrHandler(), S1: 0x0

LoaderInit: Initialing loader

Updated eptr->e32_vsize to = 00014000

Updated eptr->e32_vsize to = 0009e000

Updated eptr->e32_vsize to = 00017000

Exception 'Access Violation' (2): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'

PC=8000c95c(NK.EXE+0x0000b95c) RA=8000c950(NK.EXE+0x0000b950) SP=d001fb58, BVA=00000000

Exception 'Access Violation' (2): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'

PC=00000000(???+0x00000000) RA=80047be4(kernel.dll+0x00018be4) SP=d001f950, BVA=00000000

Exception 'Access Violation' (2): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'

..................
..................
..................


PC=00000000(???+0x00000000) RA=80047be4(kernel.dll+0x00018be4) SP=d0011508, BVA=00000000

!FATAL ERROR!: Secure stack overflow - IP = 8005d424

!FATAL ERROR!: Killing thread - pCurThread = 83842028

Exception 'Access Violation' (3): Thread-Id=00410002(pth=83842028), PC=800a3234 BVA=d0010fc0

SR=00000003 AT=82d8ba20 V0=00000000 V1=00000000

A0=c00000fd A1=8005d424 A2=00000000 A3=d001107c

T0=00000000 T1=d0011228 T2=00000001 T3=00000000

T4=d0011300 T5=00000000 T6=c01c3564 T7=82d3f220

S0=ffffd800 S1=ffffd800 S2=82d86a84 S3=ffffd800

S4=80038384 S5=82d86a84 S6=ffffd800 S7=80038384

T8=bdbdbdbd T9=00000000 LO=00000000 HI=00000000

GP=bdbdbdbd SP=d0010fb0 S8=bdbdbdbd RA=80045284

CHECKTAKECRITSEC: Violation of critical section ordering, holding CS 82d8b640 (4) while taking CS 82d86b78 (13)

NK Kernel: DEBUGCHK failed in file D:\yamafp-3\private\winceos\COREOS\nk\kernel\nknormal\..\schedule.c at line 376

DEBUG_BREAK @80087508 Ignored.

Exception 'Access Violation' (3): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'

PC=800a34ac(kernel.dll+0x000744ac) RA=800a34a0(kernel.dll+0x000744a0) SP=d0010ee0, BVA=00000014

Exception 'Access Violation' (2): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'

PC=00000000(???+0x00000000) RA=80047be4(kernel.dll+0x00018be4) SP=d0010cd8, BVA=00000000

Exception 'Access Violation' (2): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'

PC=00000000(???+0x00000000) RA=80047be4(kernel.dll+0x00018be4) SP=d0010ad0, BVA=00000000

Exception 'Access Violation' (2): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'

PC=00000000(???+0x00000000) RA=80047be4(kernel.dll+0x00018be4) SP=d00108c8, BVA=00000000

Exception 'Access Violation' (2): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'

PC=00000000(???+0x00000000) RA=80047be4(kernel.dll+0x00018be4) SP=d00106c0, BVA=00000000

NK Kernel: DEBUGCHK failed in file D:\yamafp-3\private\winceos\COREOS\nk\kernel\nknormal\..\vm.c at line 1261



Faulted in KCall, pCurThread->dwStartAddr = 800888a0, PageFreeCount = 00000551!!

Original Context when thread faulted:

Exception 'Divide By Zero' (9): Thread-Id=00410002(pth=83842028), PC=80086180 BVA=d000ffe8

SR=00000003 AT=82d8ba20 V0=80030074 V1=00000000

A0=8003411c A1=d0010018 A2=d0010120 A3=00000180

T0=00000020 T1=00000061 T2=83842da0 T3=00000000

T4=d00104b8 T5=00000000 T6=c01c3564 T7=82d3f220

S0=ffffd800 S1=ffffd800 S2=82d86a84 S3=ffffd800

S4=80038384 S5=82d86a84 S6=ffffd800 S7=80038384

T8=bdbdbdbd T9=00000000 LO=00000000 HI=00000000

GP=bdbdbdbd SP=d000ffc0 S8=bdbdbdbd RA=80084eb0

Context when faulted in KCall:

Exception 'Divide By Zero' (9): Thread-Id=00410002(pth=ffffd5e8), PC=8005db70 BVA=d000ffe8

SR=00000003 AT=00000000 V0=00000070 V1=00000000

A0=82d90000 A1=00410002 A2=82d86784 A3=0000000a

T0=00000000 T1=83842028 T2=0000000a T3=00000001

T4=d00104b8 T5=00000000 T6=c01c3564 T7=82d3f220

S0=83842028 S1=ffffd800 S2=82d86a84 S3=ffffd800

S4=80038384 S5=82d86a84 S6=ffffd800 S7=80038384

T8=bdbdbdbd T9=00000000 LO=00000000 HI=00000001

GP=bdbdbdbd SP=ffffd6e0 S8=bdbdbdbd RA=8005db4c

DEBUG_BREAK @8005db70 Ignored.

DEBUG_BREAKAccess Violation' (2): Thread-Id=00410002(pth=83842028), Proc-Id=00400002(pprc=82d86a84) 'NK.EXE', VM-active=00400002(pprc=82d86a84) 'NK.EXE'



.

Relevant Pages

  • Re: copy_from_user/copy_to_user question
    ... >> from the kernel world, ... But if this page is not mapped somewhere in memory ... label 4, label 5, ... exceptions, looking for the address where the exception took place. ...
    (Linux-Kernel)
  • Re: Dib
    ... i did a debug & i found out that when sending or receiving the same ... exception happens which is Access violation at a certain memory ...
    (microsoft.public.vc.mfc)
  • handling 0C0000005h exception in kernel mode
    ... Is there any way to handle 0C0000005h exception in kernel mode at ... I mean - I can catch an exception if I read/write into the user-mode area ... memory manager could read those pages for me back into the physical memory.. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Strange access violations
    ... not an exact error message. ... There will be an Exception Code... ... >>which kind of Access Violation took place... ... Accessing Memory before it's acquired. ...
    (comp.lang.pascal.delphi.misc)
  • Re: How to troubleshoot bugchecks on my own?
    ... not a memory problem. ... From that exception record and context, ... execute the instruction - without a problem. ...
    (microsoft.public.win32.programmer.kernel)