-
Notifications
You must be signed in to change notification settings - Fork 98
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
Issue with fewer banks than slots #630
Comments
Thanks for this report also, I'll try to fix this asap... |
Ok, I put your code inside code.s and ran this wla-z80 -i -k -v -o code.o code.s Then I ran (code.o being in linkfile's [objectives] wlalink -v -S -i linkfile linked.rom -> code.lst linked.sym Used hex editor in Emacs to see that the .SECTIONs are where they should be, so I'm guessing your emulator doesn't work properly with ROMs that have 3 banks. Does the platform (SMS?) support 3 bank ROMs? |
…k X's allocation info wasn't printed with -v switch. Affects GitHub issue #630.
Ah thanks, yes I've just tried the ROM on a real system and it works fine, so I'll reach out to the emulator maintainer to see if they are able to help :) |
Thanks for looking into this. It seems some emulators treat 48KB ROMs as not having a hardware mapper. I've padded my ROM to 64KB to prevent that issue so I'm happy to close this now :) |
I'm glad I could help! :) |
Hi there,
Sorry, I'm seeing a strange mapping issue whereby the following code results in the
bank1Code
andbank2Code
labels being assigned to the same address despite being in different banks:The
wla-z80
output indicates they are mapped to the correct banks:...but when running in an emulator like Emulicious I can see both labels occupying the bank 1 address. It's possible I'm making a paging error in my actual code (and the simplified example above doesn't do any paging), but changing the
rombankmap
to contain 4 banks seems to fix the issue and assigns the two different labels to the different banks. Is it related to having fewer banks than there are slots?The text was updated successfully, but these errors were encountered: