Skip to content

Add description for out of bounds MBC ram access #594

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions src/MBCs.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,3 +20,10 @@ so, it might be nevertheless possible to use Double Speed during periods
which use only code and data which is located in internal RAM. Despite the
above, a self-made MBC1-EPROM card appears to work stable and fine even in
Double Speed Mode.

## MBC Unmapped RAM Bank Access

On most of the MBC's in case an unmapped RAM bank is selected (which would be translate to an out of bounds RAM address by the MBC controller),
the MBC controller will simply wrap around the internal ram address and would access valid RAM address.

The MBC internal address being accessed can be calculated using this formula: `((address - external_ram_start_address) * ram_bank_size) % max_external_ram_size`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd have expected (active_ram_bank % nb_ram_banks) * 0x1000 + (address - 0xA000). Am I missing something?

Loading