Closed raybellis closed 4 years ago
Actually, I suspect it's the '*' comment delimiters, since I added some (in hindsight, not so) clever syntax checks for these. I'll investigate.
To check, you might add -oTSC to the command line. Might be that the error "magically goes away", Trump-style (meaning: it's still there, just masked by the "any blanks terminate the expression" rule implied by setting TSC assembler compatibility).
As an alternative, add the commandline option -cchar ; to the f9dasm invocation.
... And yes, confirmed, it's definitely the ''. The simple line
`haha lda haha hehe which has no 630x requirements at all gives the nice error
*** Error 3: Undefined label`
... which only makes sense if interpreted as "multiply haha by hehe and use the low byte of that result to fill A. Oops, hehe is undefined!".
Thanks - I changed the cchar
option in f9dasm
and that resolved this issue :)
I think I'll switch to the more universal ';' in f9dasm's next version.
Hi there - I'm using f9dasm to disassemble the HD63B03 firmware for the TX81Z synthesizer.
The source for A09 appears to suggest 6303 support, but almost every source line I try with the
-OH03
generates an error, e.g:even
FCB
lines don't workAlthough many single word opcodes do.
Please advise if this is a fundamental incompatibility between the packages or if there's a set of options to
f9fdasm
and/ora09
to make them mutually compatible.thanks! :)