Re: how to add 1 extra section in config.bib

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

It's possible, but more complex than what was described. You need to do a
multixip build, which Travis didn't mention in his article. A multi XIP
build allows you to specify multiple discontiguous memory regions where
executable code could reside. When you do the build, you'll get multiple
..bin files corresponding to each region, and it is your responsibility to
make sure that each region gets loaded correctly. There will be another
component (the chain) that tells the kernel where each region exists, and
what is located there.

This mechanism is complex, and wasn't originally designed to support what
you are trying to do. It was introduced to support WindowsMobile
(PocketPC2002 at the time) in order to allow Microsoft and the OEM to each
"own" separate areas of the image.

I'd say you would be better off identifying certain critical code sequences,
and copy them into internal memory as part of your normal driver code. But
first make sure it is really worth the effort...

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Michel Verhagen (eMVP)" <michel@xxxxxxxxxx> wrote in message
news:eQItD2k7IHA.1080@xxxxxxxxxxxxxxxxxxxxxxx
Hmmm, yes, Travis must be right... I never tried it either... Was probably
a bit to quick to answer, sorry!

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Sheetal wrote:
Hi Michel,

I thought there can be only one entry for RAMIMAGE in config.bib. Am
referring to http://www.windowsfordevices.com/articles/AT7569756651.html

Never tried this though. Regards,
-Sheetal.

"Michel Verhagen (eMVP)" wrote:

Yep, you should be able to do this. Just define another RAMIMAGE (not
RESERVED) section and name it CPUMEM (just an example, name it whatever
you want) and specify the 64 KB virtual address (you have to set up a
static virtual mapping to that memory of course). Then instead of
specifying NK behind a module name in platform.bib, specify "CPUMEM" (or
the name you specified).


Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

zix wrote:
Hi Sheetal,
thanx for the answer..
As I understand - you want to load certain dll into a different memory
section - is that so? Curious to know why would you want to do that
and am
wondering if one could do that....

Typically when you reserve a memory block in config.bib - you may want
to
reserve it for some module so that you have a chunk of contiguous
memory
allocated for that module.

yes, right...cause this is internal 64kb..and i want to put some
application dll's which are very often called in this section. is that
possible. Do you have any insight....I think if I am able to create a
section, then I dont see any reason why I cant do that.

thanks


.

Quantcast