Re: ClearCase + WINCE 5.0 = headache



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



.



Relevant Pages

  • Re: Quick Huffman theory question
    ... application compresses and decompresses, compression appears to ... categories as context. ... good text compression requires gigabytes of memory. ... don't bother with Huffman codes. ...
    (comp.compression)
  • Re: view menu
    ... When the file is opened into any graphical viewer or editor, the data is transferred from disk to memory so that the program can work with the data. ... We know that png uses data compression, so we can expect the uncompressed size to be much more. ... The image is 1080 pixels wide and 902 pixels high for a total of 1080x902 = 974160 pixels. ...
    (comp.graphics.apps.gimp)
  • Re: Suspend 2 merge
    ... >> spend most of your time eating memory so that you only have a few megs ... >> compression I think it achieved something close to double that, ... >> suspend faster, more reliable, more user friendly, more versatile or the ... > They are neccessary because of two-stages LRU saving... ...
    (Linux-Kernel)
  • Re: Suspend 2 merge
    ... > amount of memory you eat, then you need to work to make the I/O ... not enough RAM to suspend to disk". ... > compression I think it achieved something close to double that, ... Puting suspend hooks into ...
    (Linux-Kernel)
  • Re: What File System supports Application XIP
    ... > You won't gain at runtime by using XIP though. ... I thought that when you XIPed from flash, ... directly back to the flash memory address. ... There shouldn't be a RAM ...
    (Linux-Kernel)

Loading