| |
Slammer
Registered: Feb 2004
Posts: 416 |
Kick Assembler Thread 2
The previous thread took a little long to load, so this is a new fresh one.. |
|
... 590 posts hidden. Click here to view all posts....
|
| |
Maxlide
Registered: Apr 2003
Posts: 29 |
This syntax highlithing file was uploaded by me.
I've just downloaded and checked it again. No problems here.
I am using the latest Notepad++ version 6.1.3. |
| |
Conrad
Registered: Nov 2006
Posts: 833 |
Is there a commandline to output files bigger than 64K? ... for the case of writing .crt files? |
| |
JAC
Registered: Aug 2002
Posts: 56 |
In -dtv mode, are the illegal instructions of 6510 still valid? I first thought no, but then DTV would not run plain C64 stuff. But then again DTV could have 2 modes of operation. ... Please enlight me, so I can do the highlighting correctly. |
| |
tlr
Registered: Sep 2003
Posts: 1714 |
Quote: In -dtv mode, are the illegal instructions of 6510 still valid? I first thought no, but then DTV would not run plain C64 stuff. But then again DTV could have 2 modes of operation. ... Please enlight me, so I can do the highlighting correctly.
Undocumented 6510 opcodes are mostly supported by the C64DTV. A few do not work correctly. DCP has some problems IIRC. |
| |
Slammer
Registered: Feb 2004
Posts: 416 |
Conrad: No, Not right now. I have never worked with .crt files, but it sounds like a minor adjustment or? What are the requirements for such files?
JAC: Kick Assember assembles all illegal instructions in DTV mode.
|
| |
Slammer
Registered: Feb 2004
Posts: 416 |
V3.23 is out now. There are some improvements:
- The && and || operators are now short circuiting.
- You can now use escape sequences to insert " in strings.
As a new feature you can write your own macro plugins in java, graphics Converters etc. If you make some good ones feel free to send them to me so they can be downloaded from the website or included in KickAssembler.
|
| |
Pantaloon
Registered: Aug 2003
Posts: 124 |
slammer, NICE! |
| |
Conrad
Registered: Nov 2006
Posts: 833 |
Quote: Conrad: No, Not right now. I have never worked with .crt files, but it sounds like a minor adjustment or? What are the requirements for such files?
JAC: Kick Assember assembles all illegal instructions in DTV mode.
There's no real major adjustment for .crt files other than just allow output files to be bigger than 64K. As long as ".pseudopc" is used in code that will be assembled outside the 64K range, I wouldn't think there would be an issue.
This is primarily for developing EasyFlash carts that can be 1MB big. :) |
| |
Slammer
Registered: Feb 2004
Posts: 416 |
Conrad: So you never want a start address above $ffff? The following source would be a problem because the format of the output file only have two bytes to note the start address:
.pc=$11000
.byte 1,2,3
|
| |
Conrad
Registered: Nov 2006
Posts: 833 |
Quote:Conrad: So you never want a start address above $ffff?
No, not for .crt files. They have their own header at the start of the file and don't have, let's say, a "start address" unlike normal .prg files.
check:
http://codebase64.org/doku.php?id=base:crt_file_format
so in essence, I would set .pc to $0000, and each "CHIP" block of data would always be mapped at $8000,$a000/$e000 (using .psuedopc) and would never be out of range.
I know that this additional feature would break the rule for normal .prg files, but that's the coder's choice really. If it's going to fuck up things like object-mapping, then by all means don't include it. I can find other ways around it. |
| Previous - 1 | ... | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | ... | 60 - Next |
