512MB RAM and 256MB NOR Flash memory mapping in WinCE 6.0
SIDDIQ
Platform. I would like to know how to configure the OEMAddresstable for
512MB, 256MB NOR flash and other peripherals too. WinCE supports only 512MB
of cached address. So If I map the entire 512 MB of cached virtual address
to 512MB RAM, how to map the 256MB Nor Flash and other pheripherals? Please
help me in this regard.
Thanks in Advance.
Vinoth [MCTS]
Go through this thread, which will answer your question.
good luck.
--
vinoth.R
Aritcles:
http://www.windowsfordevices.com/articles/AT8185724467.html
http://e-consystems.com/gprsconnectivity.asp
http://vinoth-vinothblog.blogspot.com
http://www.e-consystems.com/blog
Bruce Eitman [eMVP]
OEMAddressTable. That means that the theoretical limit for RAM is 512MB.
Theoretical becuase more than likely, you will need to map other hardware
for the kernel to use via OEMAddressTable.
--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT Eurotech DOT com
My BLOG http://geekswithblogs.net/bruceeitman
Eurotech Inc.
www.Eurotech.com
"Vinoth [MCTS]" <vin...@discussions.microsoft.com> wrote in message
news:8C525666-3204-4304...@microsoft.com...
Vinoth [MCTS]
mapping of hardware through OEMAddressTable and the Sue Loh's blog for
accessing the RAM more that that.
direct allocation of RAM area for the OS through the OEMAddressTable is
theorically 512MB and practically based on the other peripherals that is
going to map on the OEMAddressTable.
the link i showed you is having another link. the purpose of the links is to
get some idea based on the previous discussions.
---
Aritcles:
http://www.windowsfordevices.com/articles/AT8185724467.html
http://e-consystems.com/gprsconnectivity.asp
http://vinoth-vinothblog.blogspot.com
http://www.e-consystems.com/blog
"Bruce Eitman [eMVP]" wrote:
> .
>
SIDDIQ
Based on your information I understand that We can't map any hardware more
than 512MB in WinCE.
I am planning to use 256MB RAM and 256MB NOR Flash. In that, in WinCE, I
will map entire 256 MB of RAM and Only 200MB of NOR Flash (Remaining 56MB for
Boot code and WinCE image storage). Other pheripherials will be mapped on
this remaining 56MB.
Other Option to have 512MB RAM and 256MB Flash storage means I need to go to
"Nand Flash" Instead of "NOR Flash". As NOR Flash is an SRAM interface, we
need to map the entire 256MB in WinCE. But in the case of NAND Flash we need
to map only 1MB, as we are accessing page by page. In this case I will map
500MB of RAM out of 512 MB and the remaining 12MB will be used to map other
hardwares.
Is my understanding is correct?
thanks for your help
Bruce Eitman [eMVP]
--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT Eurotech DOT com
My BLOG http://geekswithblogs.net/bruceeitman
Eurotech Inc.
www.Eurotech.com
"SIDDIQ" <SID...@discussions.microsoft.com> wrote in message
news:362728C7-B936-4246...@microsoft.com...
Vinoth [MCTS]
To use NAND Flash, your processor has to support NAND controller or through
some hardware provisions. In this case you can map more RAM area.
Good Luck,
siddiq via PocketPCJunkies.com
similar to SRAM. Because of this, NOR flash memory is suitable for XIP
designs where the CPU is allowed to fetch instructions directly from flash
memory.
So we need to map the entire NOR memory in the kernel.
But in the case of NAND Flash, we are issuing commands and getting data page
by page. So we need to map only NAND Flash registers (1MB) in kernel memory.
Please correct me if i am wrong?
Bruce Eitman [eMVP] wrote:
>Why do you need to map your flash memory into the kernel?
>
>> Thank you so much Vinoth & Bruce.
>>
>[quoted text clipped - 70 lines]
>>> >
>>> > .
--
Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200912/1