ok - found some time today.

This worked for me. edit your .cfg file to this:

MEMORY {
ZP: start = $0, size = $100, type = rw, define = yes;
RAM: start = $0200, size = $7F00, define = yes;
ROM: start = $C000, size = $4000, fill = yes;
}
SEGMENTS {
ZEROPAGE: load = ZP, type = zp, define = yes ...

I'll try to dust off my cc65 this weekend and see if I can duplicate the problem based on your files. Then I might be able to resolve it.

Daryl

Thanks a heap Daryl, here's my full crt0.s and kmain.c files

kmain.c

int main()
{
int x = 0;
int i;

for(i = 0; i < 1000; i++)
{
x = x + 1 ...

Space char(s) in your pathname?

Use of whitespace in filenames is generally considered to be bad practice, especially in a compiler "make file." Unfortunately, MS Windows actively promotes that sort of thing.

Oh yeah... Don't know what possessed me to put a space in the directory name... They ...

Okay, here's my batch files.

I have two, but I'll put them into one eventually:

BuildLib.bat

@ECHO off
SET CC65_BIN=E:\Users\Jesse\Documents\System I\cc65\bin
SET PATH=%CC65_BIN%
ca65 --cpu 6502 crt0.s
ar65 a dos.lib crt0.o
pause


dos.lib is copied and renamed from cc65/lib/supervision.lib as ...

Hi again,

I just stumbled upon how to create a custom target in the cc65 tutorial, so I have a correct library file, however I'm still getting some bizarre issues that I don't think I should be getting. I'm using the default crt0.s file as specified at:

http://www.cc65.org/doc/customizing-3.html ...

The __STARTUP__ label originates in the crt0.s source file for your target. You get crt0.o after it's compiled and you include this as the FIRST file in your linker chain. I usually rename the crt0.o file to match my target, i.e. for my sbc4 target, it becomes sbc4.o.

I too use windows batch files ...

Hey guys,
Sorry if this question has been answered a million times before, but I've researched a bit and haven't been able to come up with anything, so sorry for asking.

I've done systems programming before (writing small test operating systems in x86 assembly and C) and I've written a small CPU ...