Question on Bandon / Lubbock Config.bib file:

Question on Bandon / Lubbock Config.bib file
If the image is loaded into Flash, the full contiguous 64megs of SDRAM is used (32 megs for the OS
& 28 megs for the RAM). However, when the OS is run directly from the FLASH, still onl
28megs is allocated for the RAM. Why not all 32+28megs

******From the Bandon (very similar to Cotulla) Config.bib*************************
; Name|Virtual/Cached |Size| Region Typ
MEMOR
IF IMGFLASH !
IF IMGRECOVERY
NK 80288000 02000000 RAMIMAGE ; SDRAM 32MB: [8028 8000 -> 8228 7FFF
ELSE ; IMGRECOVERY
NK 80289000 001C0000 RAMIMAG
ENDIF ; IMGRECOVERY
RAM 82288000 01A30000 RAM ; SDRAM 28MB: [8228 8000 -> 83CB 7FFF
EDBG 83F8D000 00020000 RESERVED ; x20000 for EBOOT - 3 mem pools of 24
ENDI

IF IMGFLASH
IF BUILD_ROM_BI
NK 98380000 01F80000 RAMIMAGE ; FLASH 32MB - 0x80000: Locate above EBO
ENDI
IF BUILD_ROM_NB
NK 98300000 01E00000 RAMIMAGE ; FLASH 32MB - Replace EBOOT Imag
ENDI

RAM 820B8000 01C00000 RAM ; SDRAM 28MB: [820B 8000 -> 83CB 7FFF
ENDI

*****Proposed Change*********************************************

If the image is running in flash, should'nt config.bib be changed

IF IMGFLASH
IF BUILD_ROM_BI
NK 98380000 01F80000 RAMIMAGE ; FLASH 32MB - 0x80000: Locate above EBO
ENDI
IF BUILD_ROM_NB
NK 98300000 01E00000 RAMIMAGE ; FLASH 32MB - Replace EBOOT Imag
ENDI

RAM 800B8000 03C00000 RAM ; SDRAM 28MB+32MB: [800B8000->83CB7FFF
ENDI

I tried this but could not get winCE to recognize the extra 32megs as RAM. This seems
amazing since it works correctly when it boots CE from the SDRAM. This would seem
to imply that all the low level stuff, memmap.inc, etc are set correctly to recognize
the full 64megs of SDRAM.

Thanks in advance for any input, Jef

Dean
Thu Apr 29 07:45:39 CDT 2004

I don't see anything wrong, what makes you think it isn't working?

--
Dean Ramsier - eMVP
Accelent Systems
http://www.accelent.com


"JeffS" <anonymous@discussions.microsoft.com> wrote in message
news:5EB0C50C-CC2E-449F-A200-58C438EC1CBA@microsoft.com...
> Question on Bandon / Lubbock Config.bib file:
> If the image is loaded into Flash, the full contiguous 64megs of SDRAM is
used (32 megs for the OS
> & 28 megs for the RAM). However, when the OS is run directly from the
FLASH, still only
> 28megs is allocated for the RAM. Why not all 32+28megs?
>
>
> ******From the Bandon (very similar to Cotulla)
Config.bib**************************
> ; Name|Virtual/Cached |Size| Region Type
> MEMORY
> IF IMGFLASH !
> IF IMGRECOVERY !
> NK 80288000 02000000 RAMIMAGE ; SDRAM 32MB: [8028
8000 -> 8228 7FFF]
> ELSE ; IMGRECOVERY !
> NK 80289000 001C0000 RAMIMAGE
> ENDIF ; IMGRECOVERY !
> RAM 82288000 01A30000 RAM ; SDRAM 28MB: [8228
8000 -> 83CB 7FFF]
> EDBG 83F8D000 00020000 RESERVED ; x20000 for EBOOT - 3 mem
pools of 24K
> ENDIF
>
>
> IF IMGFLASH
> IF BUILD_ROM_BIN
> NK 98380000 01F80000 RAMIMAGE ; FLASH 32MB - 0x80000: Locate
above EBOT
> ENDIF
> IF BUILD_ROM_NB0
> NK 98300000 01E00000 RAMIMAGE ; FLASH 32MB - Replace EBOOT
Image
> ENDIF
>
> RAM 820B8000 01C00000 RAM ; SDRAM 28MB: [820B
8000 -> 83CB 7FFF]
> ENDIF
>
>
> *****Proposed Change**********************************************
>
> If the image is running in flash, should'nt config.bib be changed :
>
> IF IMGFLASH
> IF BUILD_ROM_BIN
> NK 98380000 01F80000 RAMIMAGE ; FLASH 32MB - 0x80000: Locate
above EBOT
> ENDIF
> IF BUILD_ROM_NB0
> NK 98300000 01E00000 RAMIMAGE ; FLASH 32MB - Replace EBOOT
Image
> ENDIF
>
> RAM 800B8000 03C00000 RAM ; SDRAM 28MB+32MB:
[800B8000->83CB7FFF]
> ENDIF
>
> I tried this but could not get winCE to recognize the extra 32megs as RAM.
This seems
> amazing since it works correctly when it boots CE from the SDRAM. This
would seem
> to imply that all the low level stuff, memmap.inc, etc are set correctly
to recognize
> the full 64megs of SDRAM.
>
> Thanks in advance for any input, Jeff
>

anonymous
Thu Apr 29 15:01:08 CDT 2004

Hi Dean

Thanks for the quick response. When I use Tools->system info on the platform builder I get the following

Memory Load = 15
Total Physical Memory = 30576 K
Available Physical Memory = 25996 K
Page File Size = 0 K
Available Page File Size = 0 K
Total Virtual Memory = 32768 K
Available Virtual Memory = 26048 K
Store Pages = 764
RAM Pages = 764
Page Size = 4096 byte

I am expecting to see total physical mem = approx 64meg

-Jef

Dean
Fri Apr 30 08:03:50 CDT 2004

There are a couple of variables that can override the config.bib memory
settings. You could check to see if MainMemoryEndAddress is being modified
in OEMInit(). That value is initialized with the config.bib RAM setting,
and the OEM has the opportunity to modify it before the kernel uses it.

--
Dean Ramsier - eMVP
Accelent Systems
http://www.accelent.com


"Jeff S" <anonymous@discussions.microsoft.com> wrote in message
news:01FE92A5-E356-499B-AB9B-7035A9578DC1@microsoft.com...
> Hi Dean,
>
> Thanks for the quick response. When I use Tools->system info on the
platform builder I get the following:
>
> Memory Load = 15%
> Total Physical Memory = 30576 KB
> Available Physical Memory = 25996 KB
> Page File Size = 0 KB
> Available Page File Size = 0 KB
> Total Virtual Memory = 32768 KB
> Available Virtual Memory = 26048 KB
> Store Pages = 7644
> RAM Pages = 7644
> Page Size = 4096 bytes
>
> I am expecting to see total physical mem = approx 64meg
>
> -Jeff
>

anonymous
Fri Apr 30 16:36:03 CDT 2004

Hi Dean

Thanks very much for the reply. I studied oeminit() and cant see how its setting MainMemoryEndAddress. I do see MainMemoryEndAddress being set in KernelRelocate (in loader.c). However, it is passed a ROMHDR structure, and I can not figure out who sets this structure. The ROMHDR struct is defined in romldr.h where I can see the ulRAMEND & ulRAMStart. But where are these getting set? Any clues would be greatly appreciated

Thanks again! -Jef

Steve
Sat May 01 14:58:35 CDT 2004

Look at the CEPC implementation the XScale one doesn't have anything for
MainMemoryEndAddress.

--
Steve Maillet (eMVP)
EmbeddedFusion
smaillet_AT_EmbeddedFusion_DOT_com