Re: CE 5.0 config.bib minimum ram

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

No bug. You simply can't span memory that is not *physically* contiguous in
config.bib.

You don't need the RESERVE sections that Geoff mentioned, but you do need to
have your RAMIMAGE area mapped to an 8MB section, and your RAM area mapped
to another 8MB section. Leave the AUTOSIZE option off to makimg doesn't try
to adjust the boundary.

You have two remaining noncontiguous sections, so you can't report both of
them with OEMGetExtensionDRAM. You'll need to use OEMEnumExtensionDRAM
which allows you to report multiple regions.

Note that the RESERVE keyword does absolutely nothing, except cause the
build tools to crash if you try to use memory in those sections. It is
essentially a comment for the developer.


--
Dean Ramsier - eMVP
BSQUARE Corporation


"Geoff" <moc.liamtoh@gnirrevliseht> wrote in message
news:OErQeWmOHHA.4992@xxxxxxxxxxxxxxxxxxxxxxx
That bug is still there? That got reported in CE2.10

Anyway, just use multiple sections in the config.bib but leave a page at
the end of each section so the the bug is masked. Or use Multiup XIP to
increase you image size. This was done on the StrongARM board Brutus for
this exact reason. This is I worked on that in 1998 so my memory is
getting dim on that subject.

I am not sure what you memory looks like (and why you haven't yet given
the hardware guy a kicking) but take this scenario

Physical RAM

0xC0000000 -> 0xC0800000
0xC1000000 -> 0xC1800000
0xC2000000 -> 0xC2800000
0xC3000000 -> 0xC3800000

Make this contiguous in the OEMAddressTable 0x80000000 mapping to
0xC0000000

I think we did something like this:

MEMORY

NK 81800000 00800000 RAMIMAGE
RAM 80000000 00800000 RAM
RESERVE 807FF000 00001000
RESERVE 80FFF000 00001000
RESERVE 817FF000 00001000

I think it then used OEMGetExtensionDRAM to get the rest of the RAM. You
may get away with putting all of RAM in there with the reserved sections.


Geoff
--


Stan wrote:
Hi,

What's the minimum amount of ram you can set in config.bib?

I have a board with non-contiguous ram, 4x8MB. AFAIK, there's a bug in
CE5.0 that prevents NK from spanning across non-cont ram sections, even
though the mmu presents a cont's virtual ram space. Ah, well.. So I have
a ram-based os image that takes up around 7MB. There's also buffers and
eboot space reserved, so there's very little space within the first 8MB
segment for the RAM section. Of course, I use pOEMEnumExtensionDRAM to
let the system know about the extra 3x8MB sections, but when in
config.bib I have NK ~7Mb and RAM <1MB the system doesn't boot. Is this
normal?

Thanks for any hints
Stan


.

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: 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)
  • 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)
  • Re: 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 ... PM registers. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Windows 2000 Server StandardEdition /PAE Question
    ... Every bit of data comes in to the processor from a memory address ... The processor has enough addresses for 4GB of RAM, ... the BIOS and system board will reserve and use a bit less ... Advanced Server or better to be able to fully use this /PAE feature. ...
    (microsoft.public.win2000.general)