RE: Configuring RAM to 256MB on CEPC - Windows Mobile 5.0 ??

Tech-Archive recommends: Fix windows errors by optimizing your registry

I thought Windows Mobile 5 was not available for Windows CE 5?
When you say Windows Mobile 5 do you mean Windows CE 5?

Windows Mobile 5 has significant hardware considerations not addressed by CE5.
It came out 12 months after CE5.

--
David Jones
Senior Lecturer
School of Electrical & Computer Engineering
RMIT University
+61 3 99255318


"Sathish" wrote:

Hi Guys,

I am using Windows Mobile 5.0. The CEPC has 256MB of RAM, but when i
see the memory tab in "start->settings->system->memory" tab it shows
that there is only 15MB program and around 97MB storage memory. I have
made some changes in config.bib, oeminit.asm and startup.asm to make my
CEPC recognize the 256MB ram, but i see that it's of no use.

The changes made are as follows

config.bib:

RAMFMD 80200000 01000000 RESERVED
NK 81200000 00A00000 RAMIMAGE
RAM 81C00000 E400000 RAM

startup.asm:

_OEMAddressTable:
;
; OEMAddressTable defines the mapping between Physical and
Virtual Address
; o MUST be in a READONLY Section
; o First Entry MUST be RAM, mapping from 0x80000000 ->
0x00000000
; o each entry is of the format ( VA, PA, cbSize )
; o cbSize must be multiple of 4M
; o last entry must be (0, 0, 0)
; o must have at least one non-zero entry

; RAM 0x80000000 -> 0x00000000, size 64M
; dd 80000000h, 0, 04000000h
dd 80000000h, 0, 10000000h

; FLASH and other memory, if any
; dd FlashVA, FlashPA, FlashSize

; Last entry, all zeros
dd 0, 0, 0

oeminit.asm:

_OEMAddressTable:
;
; OEMAddressTable defines the mapping between Physical and
Virtual Address
; o MUST be in a READONLY Section
; o First Entry MUST be RAM, mapping from 0x80000000 ->
0x00000000
; o each entry is of the format ( VA, PA, cbSize )
; o cbSize must be multiple of 4M
; o last entry must be (0, 0, 0)
; o must have at least one non-zero entry

; RAM 0x80000000 -> 0x00000000, size 64M
;dd 80000000h, 0, 04000000h
dd 80000000h, 0, 10000000h

; FLASH and other memory, if any
; dd FlashVA, FlashPA, FlashSize

; Last entry, all zeros
dd 0, 0, 0

After these changes, i have executed the following commands in the path
"C:\WM500\PUBLIC\COMMON\OAK\CSP\X86\OAL"

1. build
2. sysgen i486oal
3. Blddemo -c clean cleanplat

After all these changes, i see no result.

Can you guys tell me whether what i've done is right or wrong? Also can
you tell me what to do, if i've done it wrong or missed something.

Thanks,
Sathish


.

Relevant Pages

  • Re: Configuring RAM to 256MB on CEPC - Windows Mobile 5.0 ??
    ... When you say Windows Mobile 5 do you mean Windows CE 5? ... o First Entry MUST be RAM, mapping from 0x80000000 -> ... o each entry is of the format (VA, PA, cbSize) ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Configuring RAM to 256MB on CEPC - Windows Mobile 5.0 ??
    ... Whilst I have downloaded Windows Mobile 5.0 to my PPC 2003 and it works OK, ... undertsood that an embedded CE system (eg CEPC) created from Platform Builder ... o First Entry MUST be RAM, ... o each entry is of the format (VA, PA, cbSize) ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Configuring RAM to 256MB on CEPC - Windows Mobile 5.0 ??
    ... Windows Mobile is based on CE5, and doesn't really have any dependencies ... When you say Windows Mobile 5 do you mean Windows CE 5? ... o First Entry MUST be RAM, ... o each entry is of the format (VA, PA, cbSize) ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Problems with drivers on Vista
    ... "Martin" wrote in message ... It shows the driver Not Loading I think. ... If it DOES contain the entry called "Windows Mobile Device", please try the following in an attempt to work around this problem. ...
    (microsoft.public.pocketpc.activesync)
  • RE: Expired appointments and tasks appearing in WM5 device
    ... We are making progress on your issue but have not completely resolved it ... I hope to have the mapping we discussed resolved by Monday. ... Windows Mobile 5 device? ... Does this only happen affter you sync? ...
    (microsoft.public.exchange2000.connectivity)