- Announcement about May 10th, 2018 update and your password.
PNut and p2asm and other P2 tools
I thought I'd start this thread and although it was about a comment about PNut, it also crosses over into p2asm and perhaps other tools.
My current ROM file can no longer be assembled by PNut since it exceeds the 1024 dat symbols that are handled by PNut. Any quick way around this other than trimming?
p2asm assembles this fine, but I have to load it as a 1M obj file so that it can replace hub ROM at $FC000. Do the p2gcc tools include a loader that handles this? (
I need to check mind you
Also noticed some discrepancies between PNut and p2asm. I had a "callpa #"x",#xxxx" operation where the address lay in cog memory but PNut said the "relative jump" was too far whereas p2asm compiled it fine as it should since I though it was only a 9-bit cog address. This might be a documentation problem?
Also wrlong with an immediate source seems to be limited to 8-bits in PNut but p2asm handles an immediate of $17C fine as it should.
PNut: Constant must be from 0 to 255
fe97c fc64417c wrlong rxwrC,#rxrd
EDIT: it does not seem to work with an immediate source of 9-bits though.....