config.bib MEMORY Section

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi all,

currently my device has 64MB of RAM, configured as
32MB RAMIMAGE + 32MB RAM in config.bib, as follows in my config.bib:

RESERVED 80000000 00008000 RESERVED
DRV_GLB 80008000 00001000 RESERVED
CS8950 80010000 00030000 RESERVED
EDBG 80040000 00080000 RESERVED
FRAMEBUF 800C0000 00140000 RESERVED
NK 80200000 01E00000 RAMIMAGE
RAM 82000000 02000000 RAM

CONFIG
COMPRESSION=ON
PROFILE=OFF
ROMSTART=80200000
ROMSIZE=01E00000
ROMWIDTH=32
ROMOFFSET=0x80000000
ROMFLAGS=0
KERNELFIXUPS=ON
AUTOSIZE=OFF

In this configuration everything works fine but now I need more RAM
avalaible for application, for this reason I want to change this
settings to have:

16MB RAMIMAGE + 48MB RAM

I have changed my config.bib as follows:

RESERVED 80000000 00008000 RESERVED
DRV_GLB 80008000 00001000 RESERVED
CS8950 80010000 00030000 RESERVED
EDBG 80040000 00080000 RESERVED
FRAMEBUF 800C0000 00140000 RESERVED
NK 80200000 00E00000 RAMIMAGE
RAM 81000000 03000000 RAM

CONFIG
COMPRESSION=ON
PROFILE=OFF
ROMSTART=80200000
ROMSIZE=00E00000
ROMWIDTH=32
ROMOFFSET=0x80000000
ROMFLAGS=0
KERNELFIXUPS=ON
AUTOSIZE=OFF

and rebuild the platform but the kernel hangs with this debug output:

Booting Windows CE version 5.00 for (ARM)
&pTOC = 80209d1c, pTOC = 8061e0bc, pTOC->ulRamFree = 81074000, MemForPT
00000000

Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 12136, Secondary pages: 0, Filesystem pages
= 6068

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 81075000, extension: 00003000, length: 02f68000
ERROR: c:\macallan\private\winceos\coreos\nk\kernel\physmem.c line 284:
RemovePage : removing invalid address 0x82473000 (PFN 0xd4473000)
NK Kernel: DEBUGCHK failed in file c:\macallan\private\winceos\coreos\nk
\kernel\physmem.c at line 285

Well.. AFAIK 0x82473000 should be a valid address.. what's happening
here?!

If I reduce RAM config.bin option as follows:

RAM 81000000 01000000 RAM

there is no problem at all (but there is also not enough RAM, of course
;-)

Growing the option as

RAM 81000000 02000000 RAM
will come back with the same problem as above!

The only idea that comes into my mind is that 32MB is the size of the
RAM chip. I have two of them mapped as:
physical 0xd000:0000 to virtual 0x8000:0000
physical 0xd400:0000 to virtual 0x8200:0000
Is there a problem to have a RAM config.bib option that span across two
entry of OEMAddressTable()?!


Any idea in how to solve this problem?

Thanks in advance!

Best Regards,

Amon
.

Relevant Pages

  • Re: config.bib MEMORY Section
    ... RAM that is mapped in config.bib must be physically contiguous. ... > CONFIG ... > and rebuild the platform but the kernel hangs with this debug output: ... > Booting kernel with clean memory configuration: ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Newbie Setting up xserver
    ... Could be, but now that I know that low memory is causing the problem, I will ... The kernel gobbles up the rest of the physical memory huh. ... Actually my RAM is split into two ... >it could be that some of the processes related to setting the timezone ...
    (comp.os.linux.setup)
  • Re: PCMCIA: unable to map memory
    ... MB RAM. ... Linux conflicts here with the pcmcia-controller. ... - A patch for the kernel (2.2. ... BadRAM by Rick van Rein (and it's successor BadMEM ...
    (comp.os.linux.portable)
  • Re: [PATCH] reserve RAM below PHYSICAL_START
    ... The "reserved RAM" can be mapped by virtualization software with to ... You're right but the relocatable kernel only works if you relocate it ... only works up to address near 1G, we can't reserve more than 1G with ...
    (Linux-Kernel)
  • Re: [BUG] 2.6.26-rc1 lost half the RAM on UltraSPARC 5
    ... Top of RAM: 0x17f46000, Total RAM: 0xff40000 ... Memory hole size: 128MB ... Kernel: Using 1 locked TLB entries for main kernel image. ... Movable zone start PFN for each node ...
    (Linux-Kernel)