Dear Sir,

I use PXA27X and WINCE 5.0 to develop my project.


I always see the following message in Image compile time.

Code space full, fixing up <XYZ-1.dll> to ram space
Code space full, fixing up <XYZ-2.dll> to ram space
...

As my understanding, The size of XIP is 32MB , and all of my project's
DLL is more than 32MB.
so the "Code Space Full" message will be displayed.


But the size of my project's NK.bin is 31.75MB , it is closed to 32MB.
Does the size of XIP and the size of NK.bin have any relation?
Should I enable multiple XIP if I do NOT want to see "Code Space Full"
message ?

Beside, when I execute any AP (Word-Viewer , Image-Viewer ... ) ,
system will display "Data Abort" message.
Does this error message have any relation with XIP or Image Size ?
How to fix this issue ?

In config.bib , I reserve 48MB for NK.
Is the Size NOT enough for my system ?

Does anyone have idea about this issue ?

BR,
dirwdirw.tw

Re: "Image Size" VS "Data Abort" VS "Code Space Full" by Henrik

Henrik
Thu Jun 15 13:45:20 CDT 2006

dirw, you're mixing up things here. The size of the os image, "nk.bin",
has nothing to do with the 32Mb process slot size CE implements. They
are totally unrelated.

About "Code space full, fixing up <XYZ-1.dll> to ram space":
Normally, all XIP .dll:s are fixed up to specific locations in process
"slot 1", which is 32Mb in size. Since you have more .dll:s than can be
fixed up into slot 1, they will load into slot 0 instead, effectively
limiting the available VM of that slot (which is the most important
slot of them all since it is used by all running processes).

I don't think I've ever seen a device (other than perhaps all VM5
devices) that use up all of slot 1's space and need to load xips into
slot 0. Is this a VM5 device?

Anyway, If your other problems are caused by filling up slot 0 with
.dll:s I don't know, but what you should do before adding multiple XIP
regions is to use the different memory tools available (like target
control command "mi") and see what kind of virtual memory preassure
your device suffers.Then, when you have a better view of the problem
you can descide if multiple XIP regions is the way to go or if you're
better off cleaning out unnessecary dll:s, merging small dll:s together
etc.

Henrik Viklund
http://www.addlogic.se

dirw wrote:
> Dear Sir,
>
> I use PXA27X and WINCE 5.0 to develop my project.
>
>
> I always see the following message in Image compile time.
>
> Code space full, fixing up <XYZ-1.dll> to ram space
> Code space full, fixing up <XYZ-2.dll> to ram space
> ...
>
> As my understanding, The size of XIP is 32MB , and all of my project's
> DLL is more than 32MB.
> so the "Code Space Full" message will be displayed.
>
>
> But the size of my project's NK.bin is 31.75MB , it is closed to 32MB.
> Does the size of XIP and the size of NK.bin have any relation?
> Should I enable multiple XIP if I do NOT want to see "Code Space Full"
> message ?
>
> Beside, when I execute any AP (Word-Viewer , Image-Viewer ... ) ,
> system will display "Data Abort" message.
> Does this error message have any relation with XIP or Image Size ?
> How to fix this issue ?
>
> In config.bib , I reserve 48MB for NK.
> Is the Size NOT enough for my system ?
>
> Does anyone have idea about this issue ?
>
> BR,
> dirwdirw.tw