Re: IMGRAM64 problem
- From: "Davidw" <david.weinstein@xxxxxxxxxxx>
- Date: Sun, 15 Mar 2009 13:52:23 +0200
Hi,
I found the cause of my problem.
There is a different in the way PlatformBuilder WINCE 5.0 and WINCE 6.0:
In 5.0:
- I set the Run-time image Can be Larger then 32 MB (IMGRAM64=1)
- I set IMGRAM256 = 1 in the environment. Or as I have in my device
IMGRAM504 = 1
This let me see the 256 MB of the RAM
or the 504 MB
In 6.0:
- I set the Run-time image Can be Larger then 32 MB (IMGRAM64=1) ***** this
should be unset
- I set IMGRAM256 = 1 in the environment.
This let me see the 256 MB of the RAM
In all cases the video memort is part of the full memory.
Thanks,
David.
"Bruce Eitman [eMVP]" <bruce.eitman.nospam@xxxxxxxxxxxxxxxxxxx> wrote in
message news:OpBDEhPoJHA.4372@xxxxxxxxxxxxxxxxxxxxxxx
Okay, so what do you have in your config.bib? You may also require
support for this in your kernel.
--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman
EuroTech Inc.
www.EuroTech.com
"Davidw" <david.weinstein@xxxxxxxxxxx> wrote in message
news:%23s547LPoJHA.5360@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for fast answer.
I read your message in your blog, week ago.
In my config.bib I have IMGRAM512 and I set it.
I did not saw that I have more memory as I got in WinCE 5.0. and that
make me to be more specific in message, and ask for help.
Thanks,
"Bruce Eitman [eMVP]" <bruce.eitman.nospam@xxxxxxxxxxxxxxxxxxx> wrote in
message news:OolQklNoJHA.1340@xxxxxxxxxxxxxxxxxxxxxxx
Back up and read my post from 2/16 where I point to a blog post that
explains this.
--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman
EuroTech Inc.
www.EuroTech.com
"Davidw" <david.weinstein@xxxxxxxxxxx> wrote in message
news:%23FhbEWMoJHA.5980@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
Please help me to understand this.
I am using PCM-9375 board it is from Advantch, CPU LX-800, with 512MB
Ram memory.
In WinCE 5.0 I set the IMGRAM504 to 1 and got 504MB + 8MB(Video)
I can this in the Control Panel/System/Memory - Allocated 253MB to
Program and 253MB to Storage.
I am trying to the same in the WinCE 6.0 with no luck.
In WinCE 6.0 the key is IMGRAM512 - it say that it will automatic
manage the needs for the Video (if I am undrsanding correct)
I also tried to set IMGRAM256 with no success.
Please Help me on this.
Thanks,
David.
"KMOS" <kmos_AT_rocketmail_DOT_com> wrote in message
news:uykPCdslJHA.4372@xxxxxxxxxxxxxxxxxxxxxxx
The memory.c in x86's platform\common library is for memory sizing in
a given range and there is nothing there you need to modify.
But in the other hand, if one only enlarge the RAM/RAMIMAGE without
having corresponding modification for OEMAddressTable (either edit the
code or by using FIXUPVAR in BIB file) that is still not working.
Current memory sizing approach provided in memory.c is Read after
Write some pattern into RAM, another approach might be replied on ACPI
to obtain the memory size info. but the drawback is ACPI is not always
available especially for some embedded systems.
"Samuel Phung [eMVP]" <sam@xxxxxxxxxx> wrote in message
news:ewgxa18kJHA.3760@xxxxxxxxxxxxxxxxxxxxxxx
It's not likely that you need to edit the codes in memory.c
Take a look at the Config.bib file using Notepad or a text editor.
(You can find this file in the \Files folder in the Via BSP
directory.)
Look for the following entries:
#if defined IMGRAM64
.
.
#elif defined IMGRAM128
.
.
#elif defined IMGRAM256
.
.
All of the IMGRAMxxx memory configurations you see in the Config.bib
file are supported by the BSP.
The amount of RAM you have available may be less than the actual
memory module you installed.
Many x86 device's graphic chip use the RAM as video memory and will
reduce the amount of RAM available to the OS.
You can access the device BIOS setting to see if there is a setting
for shared video memory.
Samuel Phung / eMVP
ICOP
"KMOS" <kmos_AT_rocketmail_DOT_com> wrote in message
news:uByk9aTkJHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
If the OAL is leveraged with PQOAL (linked with
platform\common\...), it could auto detect the memory size in the
specific memory configuration.
You will like to take a look at x86InitMemory in
platform\common\src\x86\common\memory\memory.c if your OAL is
similiar to the CEPC (platform\cepc\src\oal\)
And still be aware of the only if your config.bib does define
IMGRAM512 or other IMGRAMxxx otherwise it does change nothing!
"Oliver" <Oliver@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4A98DBA1-AF67-4F80-AFAE-A7A6A3703D6F@xxxxxxxxxxxxxxxx
Thanks Bruce and KMOS,
Useful as always!
I will check out the bib files that you mentioned and will see
which IMGRAM
variables are defined in the VIA BSP.
Is it good idea to set IMGRAM to the closes possible setting to the
actual
amount of ram your device has? Say if VIA defines IMGRAM512 and the
Artigo
has 512mb of RAM then is it a good idea to use IMGRAM512 rather
than just the
default?
I guess it would only matter if you actually needed that much
memory (maybe
for a media device or real-time streaming of heavy media content).
Probably
depends on the applications, but I guess if you have 512mb why not
tell the
system that you have that much available right?...
.
- References:
- Re: IMGRAM64 problem
- From: Davidw
- Re: IMGRAM64 problem
- From: Bruce Eitman [eMVP]
- Re: IMGRAM64 problem
- From: Davidw
- Re: IMGRAM64 problem
- From: Bruce Eitman [eMVP]
- Re: IMGRAM64 problem
- Prev by Date: 3rd party mp3 decoder filter
- Next by Date: how can occur a USB RE-Enumeration?
- Previous by thread: Re: IMGRAM64 problem
- Next by thread: Measuring USB Through put of USB to LAN driver
- Index(es):
Relevant Pages
|
