Arakula / dasmfw

The DisASseMbler FrameWork
GNU General Public License v2.0
13 stars 4 forks source link

a09 will not assemble 6502 code produced with dasmfw, can you recommend an alternative Windows assembler? #3

Closed phillipeaton closed 2 years ago

phillipeaton commented 2 years ago

Perhaps the assembler you used for 6502 testing? You did do some testing, right? 😀

Thanks!

Arakula commented 2 years ago

Unfortunately, still not an area of expertise for me ... and no, I just did some eyeballing of the results for some specific opcodes.

Can you recommend one I might try on Windows or Linux, with download link, if possible?

phillipeaton commented 2 years ago

The last 6502 assembler I used was typed in from the back of a Melbourne House book in the mid-80s, so I'm no expert!

This week, I tried using as65 assembler from the assembler set here: kingswood-consulting.co.uk, because the 6809 version is popular with Vectrex users over the past 25 years or so. However, they're proprietary and the "-i" switch bug has had no response from the author for a long time.

A current popular assembler for the C64 that I'm currently looking at is Kick Assembler , maybe I'll migrate to this one after my inital tests, although it relies on Java, and I like things that are simple, so maybe I'll look elsewhere.

An alternative for me is the assembler inside the CBM Prg Studio, but, like the Kick assembler, it's not exactly a general purpose assembler. (Plus, it's author is currently working on additionally, supporting Kick Assembler.)

image

I'm not sure this is much help...

Arakula commented 2 years ago

Since I don't have any, it sure is :-)

Arakula commented 2 years ago

That Kick Assembler looks particularly interesting ... gives me really bad ideas ... like adding a Python interface to A09 :-)

phillipeaton commented 2 years ago

Or maybe you add 6502 capability to a09? (a02?) Maybe I should hide now 😉

Arakula commented 2 years ago

I won't. That would require quite some changes, mostly "thanks" to the fact that the 650X is a little-endian processor. That doesn't fit well into the A09 code. A separate "A02" would be an option ... and if/when I run into a situation where I might need it, that will presumably happen (I like having both disassembly and assembly under my thumb, following my rules ;-) ).