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

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

You're confused on what's really going on. You downloaded an upgrade from a
device manufacturer that allowed your particular device to move from PPC2003
to WM5. That upgrade is only available for your device, and is a binary
release. You can't install it on any other device, including a CEPC.

The original poster is a device builder - he has access to the actual
WindowsMobile tree with source code based on the contents of the post. He
is building the operating system, you are just using one provided by your
OEM. Since he has the tree, he can do a build targeted to any CPU supported
by the tree, including X86 if that exists.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"David Jones" <davejones@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B008D4E8-066A-41D2-BE4F-D9DDAE4C8457@xxxxxxxxxxxxxxxx
Whilst I have downloaded Windows Mobile 5.0 to my PPC 2003 and it works
OK, I
undertsood that an embedded CE system (eg CEPC) created from Platform
Builder
5.0, running activesysnch, .NETCF won't support Windows Mobile 5. I
haven't
tried this.
--
David Jones
Senior Lecturer
School of Electrical & Computer Engineering
RMIT University
+61 3 99255318


"Dean Ramsier" wrote:

Windows Mobile is based on CE5, and doesn't really have any dependencies
that CE5 can't support. This post does appear to be in reference to a
build
on WindowsMobile, but not for a real device since the CPU in question is
x86. That tree is usually always present because many developers use it
as
a test platform.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"David Jones" <davejones@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E6F7FF4F-E2C1-4E06-A690-48F1A9622351@xxxxxxxxxxxxxxxx
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 ??
    ... I thought Windows Mobile 5 was not available for 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: Virtual and physical addresses
    ... The virtual address range you can use for the virtual-to-physical mapping ... Suppose you define in your OEMAddressTable an entry for 128MB of flash as ... Why cant we map in the region where caching is disabled(ie 0xA000_0000 to ...
    (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)