I will leave it as it is then. Thank you. 2012/9/17 Payton Byrd <plbyrd@gmail.com> > > > On Mon, Sep 17, 2012 at 11:07 AM, Sandro Mestre <san.mes@gmail.com> wrote: > >> Can someone help me understand what this warning means: ld65.exe: >> Warning: Segment `CODE' in module `v2.obj' requires larger alignment . What >> I am doing that prompts this warning? >> >> My CODE segment is taking memory from $800 to $dff. >> >> This is my cfg file: >> >> MEMORY { >>> ZP: start = $0002, size = $00fe, type = rw; >>> RAM: start = $07fe, size = $f801, fill = yes, file = %O; >>> } >>> >> > You're telling the linker to create a single file with $f801 bytes because > of the fill = yes. If you don't want all of the memory in that range in > the file then make that fill = no. If you need segments filled, you will > need to define multiple memory segments and output them to the same file, > but fill them as necessary. > > > >> >>> SEGMENTS { >>> CABECEIRAPRG: load = RAM, type = ro; >>> CODE: load = RAM,type = ro; >>> ECRAS: load RAM, start = $3000, type = ro; >>> STILES: load RAM, start = $4000, type = ro; >>> >>> >>> BORDADURA: load = RAM, start = $7000, type = ro; >>> BORDADURASRAM: load = RAM, start = $7900, type = ro; >>> BORDADURACRAM: load = RAM, start = $7c00, type = ro; >>> TILES: load = RAM, start = $8400, type = ro; >>> TILESCRAM: load = RAM, start = $8c00, type = ro; >>> TILESSRAM: load = RAM, start = $8d00, type = ro; >>> >>> SRAM: load = RAM, start = $c000, type = ro; >>> >>> SPR: load = RAM, start = $d000, type = ro; >>> SPR2: load = RAM, start = $d080, type = ro; >>> >>> BITMAP: load = RAM, start = $e000, type = ro; >>> >>> >>> #ZEROPAGE: load = ZP, type = zp; >>> #RODATA: load = RAM, type = ro; >>> #DATA: load = RAM, type = rw; >>> >>> } >>> >> >> Thx >> > > > > -- > Payton Byrd > <http://www.paytonbyrd.com> > <http://it.toolbox.com/blogs/paytonbyrd> > ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Mon Sep 17 18:51:06 2012
This archive was generated by hypermail 2.1.8 : 2012-09-17 18:51:10 CEST