Re: GrabFSPages causing exception

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: Windows 2000 Server StandardEdition /PAE Question
    ... I would like to add here that the reserved memory address space by the devices is not necessarily reserved to talk to the processor. ... They may not necessarily talk to the processor at those addresses but the end result is the same, the private addresses will be marked as off limits to the processor and the RAM will still end up short of addresses in the lower 4GB memory arena. ... For example, the BIOS and system board will reserve and use a bit less than 1 megabyte of address space directly at the processor, when the processor needs to talk with the BIOS or motherboard it will do so directly by using their reserved addresses, the addresses reserved by and given to the system board cannot be used by the RAM. ... Windows 2000 Professional, Windows 2000 Server, Windows XP 32-bits and Vista 32-bits do not make full use of this /PAE feature, they are unable to use RAM addressed above the 4GB boundary. ...
    (microsoft.public.win2000.general)
  • 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: Windows 2000 Server StandardEdition /PAE Question
    ... Every bit of data comes in to the processor from a memory address and every bit leaving the processor goes to a memory address. ... The problem is that if the processor gave all the addresses to the RAM it would have none left for other things, anything and everything that needs to talk to the processor would have to do it through the RAM or the processor would have to dump RAM addresses to talk to other devices! ... For example, the BIOS and system board will reserve and use a bit less than 1 megabyte of address space directly at the processor, when the processor needs to talk with the BIOS or motherboard it will do so directly by using their reserved addresses, the addresses reserved by and given to the system board cannot be used by the RAM. ... Windows 2000 Professional, Windows 2000 Server, Windows XP 32-bits and Vista 32-bits do not make full use of this /PAE feature, they are unable to use RAM addressed above the 4GB boundary. ...
    (microsoft.public.win2000.general)
  • 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)
  • FlashROM as as a FAT-disk in CE 5.0?
    ... Eboot.bib and virtual memory map and possibly ... RAM 83100000 $RAM ... Reserve ZBANK virtual block (No physical memory ...
    (microsoft.public.windowsce.platbuilder)
Loading