Dave Hein wrote: »
p2asm is part of the p2gcc toolset. It is available from GitHub at https://github.com/davehein/p2gcc . p2asm is located in the p2asm_src subdirectory. You can also get the latest release from the Can't Wait for PropGCC on the P2? thread.
peter:BOOT$ ./p2asm ROM_137PBJ.spin2
ERROR: Expected ",", but found "["
Seairth wrote: »
I just want to point out that we've had roughly the same conversation several times over the last year or two. I think it's an indication that the current syntax is confusing and hard to remember. Is there an alternative syntax we could use that's more understandable, even if it isn't as terse?
Peter Jakacki wrote: »
@cgracey - the problem we have is that TAQOZ relocates to first 64k but while in TAQOZ a ^D only ends up using a relative jump to Cluso's debugger (can we refer to it simply as LSD ) but we were modifying the version of LSD in ROM so nothing happened. Looking at the machine code showed that the jump was relative but we had mistakenly thought that the @ would give us an absolute address but now we know it always refers to the hub address and we need to use \ to force absolute address or \@ for both. But we don't have an operator symbol to force relative although by default it looks like it does this.
In some other assembly languages the # forces absolute mode and @ relative but the Prop has register addressing by default so the # is used to force a jump to immediate address which means we can't use this symbol for absolute vs relative.
Maybe we could use:
@ Force absolute hub address
\ Use absolute address (cog or hub)
~ Try to use relative address but issue warning if out of range.
@"Dave Hein" - Is p2asm something I can run on my system as I like having a real listing? Is there source available that we can enhance?