Memory Map Setting (config.bib and image_cfg.h...)

Hello.

Anyone who knows about image_cfg.h(inc), config.bib, AddressTable, virtual
address, physical address and etc?
I can find some articles about each of them, but cant get the whole picture
of the system.

Memory map setting is very confusing and driving me crazy.

Please, help me to know the concept of windows ce memory map.

If anyone knows about any article or is willing to explain it, I will really
appreciate it!

Thanks!


From KidsReturn!!

--
Engineer
(Developing Windows Mobile PDAs)

Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200806/1

Luca
Sun Jun 08 23:07:29 PDT 2008

**OEMAddressTable maps physical addresses to virtual addresses for example:

DCD 0x80000000, 0xA0000000, 128 ;128 MB of RAM for an ARM processor
DCD 0x88200000, 0x4C000000, 1 ; maps the USB host controller
registers


**config.bib describes the virtual memory map for the image, for example:

RSVD 80000000 000FF000 RESERVED
ARGS 800FF000 00001000 RESERVED ;use some RAM to
exchange data between

;the OS and the bootloader
NK 80100000 02700000 RAMIMAGE ;use some RAM for
the OS image
RAM 82800000 05800000 RAM ;use some
RAM for program/storage memory

**img_cfg.h reports some useful #define, for example

#define IMAGE_OSIMAGE_RAM_PA_START 0xA0100000 ; the physical address
corresponding to 0x80100000 in config.bib
#define IMAGE_OSIMAGE_RAM_SIZE 0x02700000 ; the OS image
size in config.bib


I know this is not much but HTH



--

Luca Calligaris
www.eurotech.it

"KidsReturn via PocketPCJunkies.com" <u25670@uwe> ha scritto nel messaggio
news:855c7dfba9db4@uwe...
> Hello.
>
> Anyone who knows about image_cfg.h(inc), config.bib, AddressTable, virtual
> address, physical address and etc?
> I can find some articles about each of them, but cant get the whole
> picture
> of the system.
>
> Memory map setting is very confusing and driving me crazy.
>
> Please, help me to know the concept of windows ce memory map.
>
> If anyone knows about any article or is willing to explain it, I will
> really
> appreciate it!
>
> Thanks!
>
>
> From KidsReturn!!
>
> --
> Engineer
> (Developing Windows Mobile PDAs)
>
> Message posted via PocketPCJunkies.com
> http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200806/1
>

Jack
Sun Jun 08 23:39:01 PDT 2008

I don't know which articles you read, but this post of Sue Loh gives a
pretty good overview about the memory organisation in windows ce:

http://blogs.msdn.com/ce_base/archive/2006/09/01/Understanding-Memory-Sections-in-config.bib_2C00_-boot.bib_2C00_-and-OEMAddressTable-in-Windows-CE-5.0-and-6.0.aspx

KidsReturn
Mon Jun 09 08:46:50 PDT 2008

Awesome!
Thanks mate!

Luca Calligaris wrote:
>**OEMAddressTable maps physical addresses to virtual addresses for example:
>
>DCD 0x80000000, 0xA0000000, 128 ;128 MB of RAM for an ARM processor
>DCD 0x88200000, 0x4C000000, 1 ; maps the USB host controller
>registers
>
>**config.bib describes the virtual memory map for the image, for example:
>
> RSVD 80000000 000FF000 RESERVED
> ARGS 800FF000 00001000 RESERVED ;use some RAM to
>exchange data between
>
> ;the OS and the bootloader
> NK 80100000 02700000 RAMIMAGE ;use some RAM for
>the OS image
> RAM 82800000 05800000 RAM ;use some
>RAM for program/storage memory
>
>**img_cfg.h reports some useful #define, for example
>
>#define IMAGE_OSIMAGE_RAM_PA_START 0xA0100000 ; the physical address
>corresponding to 0x80100000 in config.bib
>#define IMAGE_OSIMAGE_RAM_SIZE 0x02700000 ; the OS image
>size in config.bib
>
>I know this is not much but HTH
>
>> Hello.
>>
>[quoted text clipped - 15 lines]
>>
>> From KidsReturn!!

--
Engineer
(Developing Windows Mobile PDAs)

Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200806/1