Re: NK.BIN size and Ram Usage.
- From: Chris Ingraham <ingraham-at-xelic-dot-com>
- Date: Wed, 5 Dec 2007 04:38:06 -0800
Hi Bruce,
Sorry I left out that piece. Here is the information reported by the Remote
System Information tool for the memory component:
Memory Load 92%
Total Physical Memory 6496 KB
Available Physical Memory 576 KB
Page File Size 0 KB
Available Page File Size 0 KB
Total Virtual Memory 32768 KB
Available Virtual Memory 25472 KB
Store Pages 1623
RAM Pages 1624
Page Size 4096 bytes
Please let me know if you need any other information.
Thanks,
Chris
"Bruce Eitman [eMVP]" wrote:
So how much RAM do you have a run time? You didn't tell us that..
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"Chris Ingraham" <ingraham-at-xelic-dot-com> wrote in message
news:CE8F7ED0-C084-445E-9031-B40DFAA620BE@xxxxxxxxxxxxxxxx
Hi All,
I've created an OS Image that results in an NK.BIN image that's around
14Mb.
My platform has 32Mb of SDRAM installed on it. According to the
Config.bib
file I'm using (see below), 2 Mb should be reserved for a Frame Buffer, 2
Mb
should be reserved for USBDMA usage, and the remaining should get shared
between the RAMIMAGE and RAM sections when AUTOSIZE=ON.
Given this setup, I would expect to see somewhere around 14 Mb of ram
available for applications and data. (32Mb - 2Mb - 2Mb - 14Mb = 14Mb).
However, after my OS Boots, and I run the Remote System Information tool
that
comes with Embedded Visual C++ 4.0, it reports that I'm at 92% Ram
utilization with only 568KB Available Physical Memory. Where did all my
RAM
go?
Below are the current settings in my Config.bib that apply:
;-------------------------------------------------------------------------------
; MEMORY SECTION
;-------------------------------------------------------------------------------
MEMORY
;------------------ Reserved Region Mapping (2 MB) ---------------------
; Start Addr End Addr Mem Type Region Name Size
; 0x88000000 0x88000FFF SDRAM OALARGS 4 KB
; 0x88001000 0x881FFFFF SDRAM FRAMEBUFFER (2MB -
4KB)
;-----------------------------------------------------------------------
; Name Address Size Type
OALARGS 88000000 00001000 RESERVED
FRAMEBUFFER 88001000 001FF000 RESERVED
; 64MB SDRAM Configuration Values
;---------------------------- ADS RAM image -----------------------------
; Start Addr End Addr Mem Type Region Name Size
; 0x88000000 0x881FFFFF SDRAM reserved 2 MB
; 0x88200000 0x8A0FFFFF SDRAM NK 31 MB
; 0x8A100000 0x8BFFFFFF SDRAM RAM 31 MB
; 0x8BE00000 0x8BFFFFFF USBDMA RAM 2 MB
;-----------------------------------------------------------------------
; Name Address Size Type
NK 88200000 01F00000 RAMIMAGE
RAM 8A100000 01D00000 RAM
USBDMA 8BE00000 00200000 RAM
;-------------------------------------------------------------------------------
; CONFIG SECTION
;-------------------------------------------------------------------------------
CONFIG
KERNELFIXUPS=ON
AUTOSIZE=ON
; 64MB SDRAM Configuration Values
ROMSIZE=04000000
ROMSTART=88000000
ROMWIDTH=32
- Follow-Ups:
- Re: NK.BIN size and Ram Usage.
- From: Chris Ingraham
- Re: NK.BIN size and Ram Usage.
- References:
- Re: NK.BIN size and Ram Usage.
- From: Bruce Eitman [eMVP]
- Re: NK.BIN size and Ram Usage.
- Prev by Date: Re: DDGPE driver for CE 6.0
- Next by Date: Re: ClearCase + WINCE 5.0 = headache
- Previous by thread: Re: NK.BIN size and Ram Usage.
- Next by thread: Re: NK.BIN size and Ram Usage.
- Index(es):
Relevant Pages
|