Re: [cc65] Linker is not following configuration file

Hi Payton,

> OK, here's the scenario.  I want to leave a hole from $1000 to $3000
> for loading in music files.  I've setup my linker config as such:
> 
> […]
> 
> MEMORY {
>     ZP:       file = "", define = yes, start = $0002, size = $001A;
>     LOADADDR: file = %O,               start = $07FF, size = $0002;
>     HEADER:   file = %O,               start = $0801, size = $000C;
>     RAM1:      file = %O, define = yes, start = $080D, size = $07F3;
> # - __STACKSIZE__ - __OVERLAYSIZE__;
> 	MUSIC:		file = %O, define = yes, start = $1000, size = 
$2000;
> 	RAM:		file = %O, define = yes, start = $3000, size = 
$6000;
>     SCIENCELA:   file = "science.ovl",           start = $D000 -
> __OVERLAYSIZE__, size = $0002;
> […]
> 
> SEGMENTS {
>     LOADADDR: load = LOADADDR, type = ro;
>     EXEHDR:   load = HEADER,   type = ro;
>     STARTUP:  load = RAM1,      type = ro;
>     LOWCODE:  load = RAM,      type = ro,                optional =
> yes; INIT:     load = RAM,      type = ro,  define = yes, optional =
> yes; CODE:     load = RAM,      type = ro;
>     SCIENCELA: load = SCIENCELA, type = ro;
>     SCIENCECODE: load = SCIENCE,     type = ro,  define = yes;
> […]

Just a guess, but you might want to add ``fill = yes`` at appropriate 
places in the memory section.  The gap has to be filled with something, 
otherwise only the data that actually exists for a memory area is 
written to the file.

Ciao,
	Marc 'BlackJack' Rintsch
-- 
I'm not a complete idiot - several parts are missing.

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.