Re: [cc65] drive code with shared segments

>>>>> "UvB" == Ullrich von Bassewitz <uz@musoftware.de> writes:

UvB> Sorry, but I have to admit that I didn't really understand what
UvB> you're trying to do. What I understand is that you have 1 shared
UvB> piece of code, plus 4 pieces of unique code. Is there any other
UvB> code?

Well, the code for the host side, that does drive model detection and
uploads the shared code + model specific code.

UvB> What do you want the linker to output? 4 files? 1 file?

One file. The drive's memory map looks like this:

  $0400 .. $04ff	ram buffer
  $0500 .. X		shared code
  X + 1 .. Y		model specific code

The main program determins which drive is connected, and then uploads
the shared code, followed by the model specific code. The problem is
that the size of the shared code is not known (it's under develop-
ment), so I can't just make two different segments in the linker. Or,
rather, I could, but it requires manual tweaking. Currently I'm
working with a SHARED segment at $0500..$05ff, and a MODEL segment at
$0600..$06ff, but if either segment grows I'll need to tweak the
config again. I was hoping that ld65 would do that for me :) But I
guess that would require expression support in ld65...

-- 
    ___          .     .  .         .       . +  .         .      o   
  _|___|_   +   .  +     .     +         .  Per Olofsson, arkadspelare
    o-o    .      .     .   o         +          MagerValp@cling.gu.se
     -       +            +    .     http://www.cling.gu.se/~cl3polof/
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.