TASEmulators / TASEmulators/BizHawk

mGBA system bus: I/O registers, VRAM, OAM, GamePak SRAM cannot be written manually through system bus

Open
#3,537 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Core: mGBA Repro: Fixed/added in upstream stable Repro: Patch pending
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the manual-write behavior through the mGBA system bus, using the GBA memory map linked in the issue as the reference. Check writes to I/O registers, VRAM, OAM, and GamePak SRAM; done means these regions accept the writes that the memory map identifies as read/write.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.