Re: prefetch data abort on WinCE kernel

Hi Umesh,

Thanks, for your help.

Here my problem is after through debugging i came to know that i am
blocking in loader initialization function it self ,
Here i am not allocating the Dll First virtual memory address to
physical address correctly

Here i am giving my address table for reference that how i have mapped

DCD 0x80000000, 0x80000000, 128 ; SDRAM
DCD 0x88000000, 0x40200000, 4 ; ISRAM
DCD 0x88400000, 0x08000000, 1 ; Debug Board
DCD 0x88500000, 0x48000000, 24 ; L4 Peripherals -
24 MB mapped
DCD 0x89D00000, 0x68000000, 16 ; L3 Peripherals -
16 MB mapped
DCD 0x8AD00000, 0x6C000000, 16 ; SMS
DCD 0x8BD00000, 0x6D000000, 16 ; SDRC
DCD 0x8CD00000, 0x6E000000, 16 ; GPMC
DCD 0x8DD00000, 0x50000000, 1 ; GFX
DCD 0x8DE00000, 0x00000000, 256 ; CS0
DCD 0x9DE00000, 0x40000000, 1 ;BootRom
DCD 0x00000000, 0x00000000, 0 ; End of Table.


Here is my latest debug messages

PB Debugger The Kernel Debugger is waiting to connect with target.
101 PID:0 TID:0 Setting up softlog at 0x85ffc000 for 0x800 entries
3576 PID:0 TID:0 Booting Windows CE version 6.00 for (ARM)
3577 PID:0 TID:0 &pTOC = 853b7c1c, pTOC = 847ce20c, pTOC->ulRamFree
= 853bc000, MemForPT = 00001000
3578 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
3578 PID:0 TID:0 Configuring: Primary pages: 3132, Secondary pages:
6956, Filesystem pages = 394
3579 PID:0 TID:0
Booting kernel with clean memory configuration:
3579 PID:0 TID:0 Memory Sections:
3580 PID:0 TID:0 [0] : start: 853be000, extension: 00002000,
length: 00c3c000
3581 PID:0 TID:0 [1] : start: 86000000, extension: 00004000,
length: 01b2c000
3582 PID:0 TID:0 NKStartup done, starting up kernel.
3582 PID:0 TID:0 Windows CE KernelInit
3595 PID:400002 TID:2 Reserve VM for kernel XIP DLls, first =
c0010000, last = c0b90000
3597 PID:400002 TID:2 g_pprcNK == 0x853b5aa0
3598 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00017000
3598 PID:400002 TID:410002 Initializing Memory Mapped File Support
3599 PID:400002 TID:410002 Scheduling the first thread.
3599 PID:400002 TID:410002 Detecting VFP...
3600 PID:400002 TID:410002 VFP Not Found!
3600 PID:400002 TID:410002 LoaderInit: Initialing loader
3602 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00017000
3603 PID:400002 TID:410002 Updated eptr->e32_vsize to = 000a2000
3604 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00022000
3634 PID:400002 TID:410002 Heap Statistics at 0xC01A5A68


Please let me know where i am doing wrong in my memory mappings

Thanks,
Seshu

.

Relevant Pages

  • Re: Booting questions ....
    ... >> where memory is already setup to be one flat address space. ... > loader and executed. ... Memtest86 is not for the faint of heart to look at. ... The next step would be to "imitate" a kernel booting to the point where I got ...
    (freebsd-arch)
  • Verify loader initialization in WinCE kernel
    ... Here i have stuck in kernel startup sequence at verify loader ... initialization functionality (Which verifies all the Virtual Memory ...
    (microsoft.public.windowsce.platbuilder)
  • loader init failed in winCE kernel
    ... blocking in loader initialization function it self in private winCE ... Here i am not allocating the Dll First virtual memory address to ... PB Debugger The Kernel Debugger is waiting to connect with target. ... 3600 PID:400002 TID:410002 LoaderInit: Initialing loader ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Booting questions ....
    ... > addresses using PTOVand vice versa using VTOP. ... >>right after the setting up of the memory ranges. ... > bit of memory mapped in the loader, same with sparc64, etc. ... Ehhhh, again more reasons to put this in the kernel, or something that closely ...
    (freebsd-arch)
  • [UNIX] Linux Kernel do_brk() Vulnerablility (Explained)
    ... Get your security news from a reliable source. ... A critical security bug has been found in the Linux kernel 2.4.22 (and ... earlier) memory management subsystem. ... for the code working at the lowest privilege level. ...
    (Securiteam)