-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Force extended addressing mode? #41
Comments
How about creating a macro for that situation and using the macro in an opcode-like fashion?
Then you'd just never use "JSR" but instead always "JSRX" Not quite answering your question about "forcing" but perhaps a better solution than inputting the raw bytes every single time. |
Yeah, that's not the worst idea for my particular use case. Thanks. And I do realize I probably shouldn't dasm for 6800. but I've used dasm for F8 in the past and I quite like it. Maybe the solution is to add 6800 support to dasm… |
The
Could be something to consider. |
Have you tried the postfix '.w'
Should create 'bd 00 40' (I've tested this) With dasm one can force addressing mode to direct address with postfix (.b) or to extended address (.w) |
Oh, interesting! No, I must have missed that in the documentation. Not sure if this kind of syntax is common and I just don't know about it. This looks perfect. |
My admin-gurus at the university used to say: "You've got the sources, luke .." (especcially when docs where missing ;-) |
Can this be closed? |
Yes. Thanks! |
Perhaps a bad idea, but I'm using
dasm
to write a program for the MC6800. 6803 code is backwards compatible with 6800's documented instructions, so I thought it'd be a safe thing to do.However, I just encountered a problem:
On a 6800, this would use extended addressing, since there's no direct (zero-page) JSR there, so it would be assembled into
$BD $0040
. The 6803 does have a direct JSR instruction though, anddasm
will obviously use it, creating code that's not compatible with 6800.In this specific case, it's even worse. The opcode for direct JSR on 6803 is
$9D
, which on the 6800 was an undocumented opcode: The mythical "halt and catch fire"!Anyway, my actual question is this: I realize
dasm
doesn't support 6800 and that maybe I should use something else, but is there a way to force it to use extended addressing in cases like this, without simply inputting the raw bytes?The text was updated successfully, but these errors were encountered: