Re: [cc65] Maximum application size

Hi Andreas!

That's a lot of questions that I don't know the answer to right off
but I can answer some...

> 3) is it possible to split code into non-continous memory regions
> (without doing it "by hand" in assembly)

Yes - you can define multiple code segments in the linker.cfg file.
For example I did something like this once:

MEMORY {
    RAM: start = $f53, size = $20ad, define = yes, fill = yes;
    BIKESPRITERAM: start = $3000, size = $80, define = yes, fill = yes;
    RAM2: start = $3080, size = $f7f, define = yes, fill = yes;
}

SEGMENTS {
    CODE: load = RAM, type = rw;
    BIKESPRITES: load = BIKESPRITERAM, type = ro;
    CODE2: load = RAM2, type = rw;
}

And then in your C source, you can choose which segment you want to
put your code in with e.g.

#pragma codeseg ("CODE")

> 4) i have a 2k const array for the charset - what is the best method for
>   not wasting that memory, after the charset has been copied to its
> final destination. Can i locate one of my global arrays of structs at the
> same location?

If possible, maybe you can set up your linker.cfg so that the charset
data is loaded straight to where you want it? No need to store it in
two places.

> 5) can i place the arrays with sprite data at a 64 byte boundary so they
> can be used directly without relocating?

Yes :)  Again, use the linker.cfg.

Johan
-- 
http://www.rebelpetset.com
http://www.littlesounddj.com
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.