Re: [cc65] Odd problems creating a new target.

From: L. Adamson <>
Date: 2012-06-21 20:36:27
On Thu, Jun 21, 2012 at 10:56 AM, Oliver Schmidt <> wrote:
> crt0.s: (note that init and exit code is
>> commented out. 6502 housekeeping is done by the bootloader and not needed,
>> as well).
> Why do you think that 'zerobss' and 'initlib' are not needed?

A bad choice of wording on my part.  I figured that since I was not
accessing any uninitialized values or making any library calls, that it
would be safe to temporarily disable them so that the generated code was
shorter and easier to trace through.  It is reenabled now that the problem
has been solved.


> I'd consider the following "SEGMENTS" section more promising:

Thanks for taking the time to help me out!  For some reason, it didn't even
enter my mind that the order mattered.  Lack of coffee, I s'pose. :P  I've
made the changes you suggest and the disassembly looks a good bit more
orderly now.

The root of the problem ended up being that I wasn't padding multi-sector
images properly to a multiple of 128 bytes, and the last sector of images
of size > 1 sector wasn't getting loaded from the virtual disk!  It's
always something silly that you don't find until the next day and after
posting to a mailing list about, isn't it?  I do apologize for spamming the
list about something so trivial. :3

To unsubscribe from the list send mail to with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Thu Jun 21 20:36:45 2012

This archive was generated by hypermail 2.1.8 : 2012-06-21 20:36:49 CEST