Re: GrabFSPages causing exception


We were able to solve that problem finally.
Our RAM was not properly configured. we changed some settings and it worked.
--
GD Shukla


"gd.shukla" wrote:

Hi

I called the NKForceCleanBoot() from OEMInit . I made a few changes into my
OEMAddressTable and config.bib which are given below:

config.bib

MEMORY

; Name Start Size Type
; ------- -------- -------- ----
RSVD 80000000 000FF000 RESERVED
ARGS 800FF000 00001000 RESERVED
NK 80100000 00160000 RAMIMAGE
RAM 80260000 03DA0000 RAM

-----
OEMAddressTable

ALIGN
g_oalAddressTable

DCD 0x80000000, 0xA0000000, 64 ; MAINSTONEII: SDRAM (64MB).
DCD 0x84000000, 0x5C000000, 1 ; BULVERDE: Internal SRAM
(64KB bank 0).
DCD 0x84100000, 0x58000000, 1 ; BULVERDE: Internal memory
PM registers.
DCD 0x84200000, 0x4C000000, 1 ; BULVERDE: USB host
controller.
DCD 0x84300000, 0x48000000, 1 ; BULVERDE: Memory controller.
DCD 0x84400000, 0x44000000, 1 ; BULVERDE: LCD controller.
DCD 0x84500000, 0x40000000, 32 ; BULVERDE: Memory-mapped
registers (peripherals).
DCD 0x86500000, 0x3C000000, 64 ; BULVERDE: PCMCIA S1 common
memory space.
DCD 0x8A500000, 0x38000000, 64 ; BULVERDE: PCMCIA S1
attribute memory space.
DCD 0x8E500000, 0x30000000, 32 ; BULVERDE: PCMCIA S1 I/O
space.
DCD 0x90500000, 0x2C000000, 64 ; BULVERDE: PCMCIA S0 common
memory space.
DCD 0x94500000, 0x28000000, 64 ; BULVERDE: PCMCIA S0
attribute memory space.
DCD 0x98500000, 0x20000000, 32 ; BULVERDE: PCMCIA S0 I/O
space.
DCD 0x9A500000, 0xE0000000, 1 ; MAINSTONEII: Zero-bank (in
reserved slot - no physical memory required).
DCD 0x9A600000, 0x14000000, 1 ; MAINSTONEII: nCS5:
eXpansion board header.
DCD 0x9A700000, 0x10000000, 1 ; MAINSTONEII: nCS4: SMSC
91C111 Ethernet controller.
DCD 0x9A800000, 0x0A000000, 1 ; MAINSTONEII: nCS2 (upper
half): 2MB SRAM.
;DCD 0x9A900000, 0x08000000, 1 ; MAINSTONEII: nCS2
(lower half): Board registers (FPGA).
;DCD 0x9AA00000, 0x04000000, 32 ; MAINSTONEII: nCS1:
Secondary flash (32MB).
DCD 0x9A900000, 0x00000000, 16 ; MAINSTONEII: nCS0: Boot
Flash (16MB).
DCD 0x9B900000, 0x50000000, 1 ; BULVERDE: Camera
peripheral interface.

DCD 0x00000000, 0x00000000, 0 ; end of table
--------

I am still getting the similar errors which are given below:

Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:21:58
ProcessorType=0411 Revision=7
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 8011548c
ABCEFGError Reporting Memory Reserved, dump size = 00020000
Booting Windows CE version 5.00 for (ARM)
&pTOC = 80109f9c, pTOC = 801f48e4, pTOC->ulRamFree = 80285000, MemForPT =
00000000
Configuring: Primary pages: 15702, Secondary pages: 0, Filesystem pages = 7851

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 81687000, extension: 81689000, length: 81688000
ERROR: c:\macallan\private\winceos\coreos\nk\kernel\physmem.c line 284:
RemovePage : removing invalid address 0x81e83000 (PFN 0xa1e83000)
NK Kernel: DEBUGCHK failed in file
c:\macallan\private\winceos\coreos\nk\kernel\physmem.c at line 285

Could anyone please suggest, what might the problem be.

--
GD Shukla


"Dean Ramsier" wrote:

For starters, you're not booting clean. Call NKForceCleanBoot() in OEMInit
to tell the kernel the RAM Filesystem contents are not valid.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"gd.shukla" <gdshukla@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D9EB0101-0F62-4587-9110-9D2406A85D78@xxxxxxxxxxxxxxxx
Hi

I am working on a BSP cloned from mainstone II on pxa270 processor. We are
downloading the image using ARMBOOT (over serial port). The execution flow
that we see, the image is executing upto GrabFSPages and is causing an
exception in RemovePage function in GrabFSPages (in private directory).
The flow goes like:
Startup->OALStartup->KernelStart->ARMInit->OEMDebugSerialInit->OEMInit->KernelFindMemory->GrabFSPages.
The last message the we get is:
Booting kernel with existing memory configuration:
Memory Sections:
[0] : start: 81687000, extension: 81689000, length: 81688000
[1] : start: 8168a000, extension: 8168c000, length: 8168b000
[2] : start: 8168d000, extension: 8168f000, length: 8168e000
[3] : start: 81690000, extension: 81692000, length: 81691000
[4] : start: 81693000, extension: 81695000, length: 81694000
[5] : start: 81696000, extension: 81698000, length: 81697000
ERROR: c:\macallan\private\winceos\coreos\nk\kernel\physmem.c line 284:
RemovePa
ge : removing invalid address 0x81e83000 (PFN 0xa1e83000)
NK Kernel: DEBUGCHK failed in file
c:\macallan\private\winceos\coreos\nk\kernel\
physmem.c at line 285

The config.bib is:
MEMORY

; Name Start Size Type
; ------- -------- -------- ----
RSVD 80000000 000FF000 RESERVED
ARGS 800FF000 00001000 RESERVED
NK 80100000 03000000 RAMIMAGE
RAM 83100000 00F00000 RAM

; Reserve ZBANK virtual block (No physical memory
; is required to back this virtual range).
;
ZBANK 96500000 00100000 RESERVED

The OEMAddressTable is:
g_oalAddressTable

DCD 0x80000000, 0xA0000000, 64 ; MAINSTONEII: SDRAM
(64MB).
DCD 0x84000000, 0x5C000000, 1 ; BULVERDE: Internal SRAM
(64KB bank 0).
DCD 0x84100000, 0x58000000, 1 ; BULVERDE: Internal memory
PM registers.
DCD 0x84200000, 0x4C000000, 1 ; BULVERDE: USB host
controller.
DCD 0x84300000, 0x48000000, 1 ; BULVERDE: Memory
controller.
DCD 0x84400000, 0x44000000, 1 ; BULVERDE: LCD controller.
DCD 0x84500000, 0x40000000, 32 ; BULVERDE: Memory-mapped
registers (peripherals).
DCD 0x86500000, 0x3C000000, 64 ; BULVERDE: PCMCIA S1
common
memory space.
DCD 0x8A500000, 0x38000000, 64 ; BULVERDE: PCMCIA S1
attribute memory space.
DCD 0x8E500000, 0x30000000, 32 ; BULVERDE: PCMCIA S1 I/O
space.
DCD 0x90500000, 0x2C000000, 64 ; BULVERDE: PCMCIA S0
common
memory space.
DCD 0x94500000, 0x28000000, 64 ; BULVERDE: PCMCIA S0
attribute memory space.
DCD 0x98500000, 0x20000000, 32 ; BULVERDE: PCMCIA S0 I/O
space.
DCD 0x9A500000, 0xE0000000, 1 ; MAINSTONEII: Zero-bank
(in
reserved slot - no physical memory required).
DCD 0x9A600000, 0x14000000, 1 ; MAINSTONEII: nCS5:
eXpansion board header.
DCD 0x9A700000, 0x10000000, 1 ; MAINSTONEII: nCS4: SMSC
91C111 Ethernet controller.
DCD 0x9A800000, 0x0A000000, 1 ; MAINSTONEII: nCS2 (upper
half): 2MB SRAM.
DCD 0x9A900000, 0x08000000, 1 ; MAINSTONEII: nCS2 (lower
half): Board registers (FPGA).
DCD 0x9AA00000, 0x04000000, 32 ; MAINSTONEII: nCS1:
Secondary flash (32MB).
DCD 0x9CA00000, 0x00000000, 32 ; MAINSTONEII: nCS0: Boot
Flash (32MB).
DCD 0x9EA00000, 0x50000000, 1 ; BULVERDE: Camera
peripheral interface.
DCD 0x00000000, 0x00000000, 0 ; end of table

Can anyone please suggest what might the problem be.

Thanks in advance.

--
GD Shukla
--
GD Shukla



.

Relevant Pages

  • Re: FlashROM as a disk in CE 5.0
    ... RAM 83100000 $RAM ... Reserve ZBANK virtual block (No physical memory ... Memory-mapped registers. ... attribute memory space. ...
    (microsoft.public.windowsce.embedded)
  • Re: FlashROM as a disk in CE 5.0
    ... Will try to build debug and look for messages related to flash. ... RAM 83100000 $RAM ... Reserve ZBANK virtual block (No physical memory ... attribute memory space. ...
    (microsoft.public.windowsce.embedded)
  • 128MB SDRAM Configuration
    ... RAM 83100000 04FFFFFF RAM ... Reserve ZBANK virtual block (No physical memory ... Memory-mapped registers. ... memory space. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: FlashROM as a disk in CE 5.0
    ... The flash is 64 MB starting at 92500000, ... RAM 83100000 $RAM ... Reserve ZBANK virtual block (No physical memory ... attribute memory space. ...
    (microsoft.public.windowsce.embedded)
  • FlashROM as a disk in CE 5.0
    ... but after booting the new image there are no folder for the flashROM disk. ... RAM 83100000 $RAM ... Reserve ZBANK virtual block (No physical memory ... attribute memory space. ...
    (microsoft.public.windowsce.embedded)
Loading