Jump to content
Posted Tue Jun 7, 2011 6:22 AM
Posted Tue Jun 7, 2011 7:10 AM
I've been looking at various sources, and from my understanding the whole 64kB physical memory space is seen as RAM, except for the top 1kB which by default contains the system ROM, MMIO, etc. So to make use of the code/data on your cart I guess you'll first have to load it into RAM through the RCART registers(?).
That's fine I suppose, but I don't see how my code in an .LNX files actually starts running at boot. When I look at a disassembled system ROM (lynxboot.img) I only see it loading 50 bytes from the cart to $AA-$DB, and when I take a look at what those 50 bytes actually are in e.g. Lynxopoly they don't seem to contain anything meaningful (unless the data is encrypted).
Is there any info available on this subject? I.e. what part of an .LNX file is first executed, from what address is it executed, and how has the hardware been set up at that point?
Posted Tue Jun 7, 2011 11:50 AM
Posted Tue Jun 7, 2011 12:11 PM
I.e. could I just take the first 256 bytes after the LNX header from whatever game and put it in my own ROM?
Posted Wed Jun 8, 2011 3:06 AM
Ok. So is the encrypted loader standard? I.e. could I just take the first 256 bytes after the LNX header from whatever game and put it in my own ROM? And is there a disassembly of a decrypted loader somewhere that I could look at?
What I need to know is mainly how much of my own code that will be "automatically" loaded from the cart to RAM, from where, and to where (i.e. what ORG should it have?).
Posted Wed Jun 8, 2011 8:59 AM
Posted Wed Jun 8, 2011 1:07 PM
Posted Thu Jun 9, 2011 3:58 AM
I noticed that cc65 has support for outputting straight to .LNX, so I'll probably try that out first. And if I'm unhappy with cc65 I'll take a look at all those other tools.
Posted Sat Jun 18, 2011 9:02 AM
Posted Sat Dec 24, 2011 10:15 AM
Posted Sat Dec 24, 2011 4:20 PM
0 members, 0 guests, 0 anonymous users