You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At http://problemkaputt.de/gbatek-gba-memory-map.htm these mentioned memory locations are suppossed to be read/write, but in mGBA you cannot poke them manually, just as if these memory locations were completely read-only.
The text was updated successfully, but these errors were encountered:
getCursorsExe
changed the title
mGBA system bus: I/O registers, VRAM, OAM,
mGBA system bus: I/O registers, VRAM, OAM, GamePak SRAM cannot be written maually through system bus
Jan 24, 2023
getCursorsExe
changed the title
mGBA system bus: I/O registers, VRAM, OAM, GamePak SRAM cannot be written maually through system bus
mGBA system bus: I/O registers, VRAM, OAM, GamePak SRAM cannot be written manually through system bus
Jan 25, 2023
Since GBAPatch16 and GBAPatch32 do implement those things, we could fix it in the memory domain by adding separate writeshort and writelong implementations. This would probably be good enough, as in real usage you'd have little reason to write only 8 bits at a time to most of these locations.
At http://problemkaputt.de/gbatek-gba-memory-map.htm these mentioned memory locations are suppossed to be read/write, but in mGBA you cannot poke them manually, just as if these memory locations were completely read-only.
The text was updated successfully, but these errors were encountered: