| |
null
Account closed
Registered: Jun 2006
Posts: 645 |
crossassembling
Since I have a laptop running Win2k now, I was looking for a crossassembler... but all I can find are tools to convert a .txt file to a c64 understandable format...(atleast, that's what I think they do...o.O)
Isn't there some kind of complete package running under Win2k, like you have Turbo Assambler on the c64?
and if there isn't... START CODING!!! =P
...nah, just kidding... in that case, I'd like to hear an easy solution for coding on a PC.
Cheers,
Knoeki. |
|
... 35 posts hidden. Click here to view all posts....
|
| |
Raf
Registered: Nov 2003
Posts: 343 |
Quote: step 1)
Download and install EditPlus.
step 2)
Download 64TASS. Put the files in a subfolder of the EditPlus directory.
step 3)
Configure EditPlus so that CTRL+1 compiles your code using 64TASS.
step 4)
Code 'macro assembly' in EditPlus and compile with 64TASS.
currently I'm using textpad (http://www.textpad.com) with DASM 2.20 by IaN Coog + I have 6502 syntax highlight too (also at textpad.com)
and... I setup it so ctrl+1 assembles too ;p
www.vulture.c64.org |
| |
null
Account closed
Registered: Jun 2006
Posts: 645 |
Quote: knoeki: enter monitor in vice and check wether it has loaded your prg (most probably it has not). Anyways you should see the emulated c64 telling you:
load"myprogram.prg",8,1
searching for myprogram.prg
loading
ready
run
if you dont see the above only the basic prompt, then vice havent loaded anything up.
in vice: alt+m, and then d1000 in the monitor prompt. if you dont see inc d020 at the 1000 adress then your prg is not loaded, then doublecheck your commandline settings in relaunch64.
well, this all doesn't work...o.O
and also, I was mistaken... I'm not using DASM, but ACME... sorry for the confusion...o.o; |
| |
hollowman
Registered: Dec 2001
Posts: 474 |
If I was to begin learning to code assembler on c64 I would start with turbo assembler on the c64, or run it under vice. Sure its nice to have all the memory available and not have to worry about crashing the c64 and trashing the source code in memory, but for trying out stuff its quicker and easier to use turbo assembler than setting up a crossdevelopment enviroment as the first step. |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
why would you worry about loosing source using vice ? loadstate / savestate is ther. (and actually thats how I used to code, since I cannot tear out my tasm roots) |
| |
cadaver
Registered: Feb 2002
Posts: 1160 |
To be honest I wouldn't trust an IDE, just make some one-letter bat files, one for running the editor and other for compiling+launching the emulator. Then hone your Alt+W reflex and I don't think the speed difference to using tasm is that much. Plus that way you can't screw up when you save a state instead of load. |
| |
Mace
Registered: May 2002
Posts: 1799 |
Knoeki, if you want some fast help from your Dutch friends, turn to 64TASS. You know where to find us.
You are being impractical and stubborn now ;-)
|
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
tastes are different. pressing accidentally save is a stupid argument, you can the same way not save your src when closing the editor or one can come up with 27 similar stupid arguments. there are much better arguments pro real cross asming than pressing accidentally alt-s :) |
| |
Slammer
Registered: Feb 2004
Posts: 416 |
>Yeah, I have that one... but I can't figure out how it works...o.o
Hey Knoeki, I'm a bit curious. What was it you didn't get to work?
|
| |
Marauder/GSS
Account closed
Registered: Jul 2006
Posts: 224 |
guess it's not running your file in vice, because your source-code doesn't get compiled...
I have tested it with Relaunch/ACME 0.90 and it works fine after changing commandline parameters for ACME to:
-f CBM -o OUTPUT INPUT
(and for VICE just -autostart)
after compiling the emulator should start and load your output-file like Oswald has posted before... and then you only need to run it by typing SYS 4096 (*=$1000 in your example)
|
| |
Melkor
Account closed
Registered: Apr 2006
Posts: 11 |
If your using ACME have you defined your output filename with !TO "filename.prg",cbm ? |
| Previous - 1 | 2 | 3 | 4 | 5 - Next |
