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

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks Silver:
i check this eception for some days but still can't find out where the bug
is.
would you help lookat if something wrong between my boot.bib and
config.bib??

boot.bib:

MEMORY
; Name Start Size Type
; ------- -------- -------- ----
FLASHRAM 80000000 02000000 RESERVED ; buffer for image to
flash

RAM 83000000 00400000 RAM ; eboot memory
STACK 83400000 00100000 RESERVED ; eboot stack
CLASSBUF 83500000 00010000 RESERVED
FREEBUF 83510000 00090000 RESERVED

BOOT 83610000 00040000 RAMIMAGE ; eboot image
BLOCK_SAVE 83700000 00080000 RESERVED ; BINSFAT MBR
NANDLOGO 83780000 00480000 RESERVED ; BINSFAT MBR
DISPLAY 83BFE000 00400800 RESERVED
DRV_GLB 83FFE800 00001000 RESERVED
ARGS 83FFF800 00000800 RESERVED ; common boot/hal
structure
FLASH 9FC00000 00040000 RESERVED

CONFIG
COMPRESSION=OFF
PROFILE=OFF
KERNELFIXUPS=ON
ROMOFFSET=0
BOOTJUMP=BFC00000
SRE=ON



MODULES
; Name Path
Memory Type
; -------------- --------------------------------------------------------------
-----------
nk.exe
$(_TARGETPLATROOT)\target\$(_TGTCPU)\$(WINCEDEBUG)\boot.exe BOOT




=======================================
config.bib:


MEMORY

NK 80001000 01FFF000 RAMIMAGE
RAM 82000000 01867800 RAM
CAMERA 83867800 00300000 RESERVED
DISPLAY 83BFE000 00400800 RESERVED
DRV_GLB 83FFE800 00001000 RESERVED
BOOTARGS 83FFF800 00000800 RESERVED
FLASH 9FC00000 00f80000 RESERVED

; This fix-up variable is a bitfield that can be used to initialize
; the OAL debug zones per oal_log.h. Uncomment the line and
; change the hexidecimal bits to enable the desired zones. The
; default value (0x0000000B) enables the OAL_LOG_ERROR,
; OAL_LOG_WARN, and OAL_LOG_INFO zones, and will be used by
; OEMInit if the line remains commented out.
;
; nk.exe:initialOALLogZones 00000000 0x0000000B FIXUPVAR

; This fix-up variable determines the amount of memory the BSP
; reserves for Watson dump capture. The current default behavior is
; to default to zero unless the image has SYSGEN_WATSON_DMPGEN
; defined. The default size is 300KiB.
;
; @CESYSGEN IF CE_MODULES_OSAXST0
nk.exe:dwOEMDrWatsonSize 00000000 0x4B000 FIXUPVAR
; @CESYSGEN ENDIF

;-------------------------------------------------------------------------------

CONFIG

; @CESYSGEN IF !NK_NKNOCOMP
COMPRESSION=ON
; @CESYSGEN ENDIF !NK_NKNOCOMP
; @CESYSGEN IF NK_NKNOCOMP
COMPRESSION=OFF
; @CESYSGEN ENDIF NK_NKNOCOMP
KERNELFIXUPS=ON
AUTOSIZE=ON

IF IMGFLASH
ROMOFFSET=1FC00000
ENDIF

IF IMGPROFILER
PROFILE=ON
ELSE
PROFILE=OFF
ENDIF

IF IMGSRE
SRE=ON
ELSE
SRE=OFF
ENDIF

;
; ROMFLAGS is a bitmask of options for the kernel
; ROMFLAGS 0x0001 Disallow Paging
; ROMFLAGS 0x0010 Trust Module only
;
IF IMGTRUSTROMONLY
ROMFLAGS=10
ELSE
ROMFLAGS=00
ENDIF


"Silver" <moc.liamtoh@gnirrevliseht>
???????:%23JuwJdd5IHA.4988@xxxxxxxxxxxxxxxxxxxxxxx
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

  • Prefetch Abort in FileSys
    ... I figured maybe I was just short of RAM. ... I know that possibly this is a memory mapping setup problem. ... Booting kernel with existing memory configuration: ... ; @CESYSGEN ENDIF CE_MODULES_TKTEST ...
    (microsoft.public.windowsce.platbuilder)
  • Re: how to use TLB to prevent Linux accessing a particular memory region
    ... on which Linux-2.6.18 kernel runs and another is DSP ... Out of 32MB of DDR 8MB is reserved for use by DSP ... into this reserved memory for the DSP. ... That reserves it ...
    (Linux-Kernel)
  • Re: 32 bit vista cant address more than 3.1-3.5 GB RAM
    ... It could use more memory for its own book-keeping. ... the kernel and kernel models share the *same* address space in OS ... On other OSes, the kernel is very special, and occupies a reserved chunk of address space that normal processes aren't allowed to use. ... Now, 32-bit Windows reserves 2 GB for the kernel by default, but can be configured to reserve only 1 GB, leaving more address space for programs. ...
    (comp.sys.mac.advocacy)
  • Re: Option Explicit
    ... but I thought that Access reserves a place in the memory only when you ... Explicit and declare your variables. ...
    (microsoft.public.access.formscoding)
  • Re: [RFC 2/9] Use NOMEMALLOC reclaim to allow reclaim if PF_MEMALLOC is set
    ... we are not guaranteed to have enough memory to ... Yes, that is due to the unbounded nature of direct reclaim, no? ... you might have to do block allocation, which itself might have to do ... the fact that reclaim reserves include the atomic allocation reserves. ...
    (Linux-Kernel)