Re: ClearCase + WINCE 5.0 = headache
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Wed, 21 Nov 2007 13:07:27 -0500
XIP is separate from the compression you're talking about. The memory
region in your config.bib file that corresponds to the RAMIMAGE section is
where you are going to run your code. At least some of your code will XIP
from that region. That memory region must be physically contiguous.
--
Dean Ramsier - eMVP
BSQUARE Corporation
"Roger Williamson" <RogerWilliamson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:CB4AAB95-FB53-4694-878B-073064003411@xxxxxxxxxxxxxxxx
Dean,
I didn't think that we were using XIP at all, since we are compressing
our
image. Then again, our config.bib file has some odd detection script
which
selects whether the image gets compressed at build time.
I wonder if I should hard configure compression either on or off.
Thanks for the input,
Roger
"Dean Ramsier" wrote:
I can't speak for your source control issues, that's something you'll
have
to figure out. But the error message indicates you're trying to run code
from a memory region that is *physically* discontiguous. That is not
allowed. The only way you can do that is to use a multixip
configuration,
and each of the XIP regions must be contained in physically (as well as
virtually) contiguous memory regions.
--
Dean Ramsier - eMVP
BSQUARE Corporation
.
- References:
- Re: ClearCase + WINCE 5.0 = headache
- From: Dean Ramsier
- Re: ClearCase + WINCE 5.0 = headache
- Prev by Date: Re: ClearCase + WINCE 5.0 = headache
- Next by Date: Re: USB flash key
- Previous by thread: Re: ClearCase + WINCE 5.0 = headache
- Next by thread: Re: ClearCase + WINCE 5.0 = headache
- Index(es):
Relevant Pages
|
Loading