Skip to content

Writes to OAMADDR should corrupt OAM. #5

@TheDreadedAndy

Description

@TheDreadedAndy

On original hardware, writes to OAMADDR cause the values at the 8-byte block of OAM previously pointed to to be written to a non-random location. Additionally, a value in OAMADDR greater than 7 will cause that 8-byte chunk to be written to the start of OAM. This corruption must be emulated to ensure full compatibility.

More details on this corruption behaviour can be found here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    EmulationAn issue within the emulatorPPUAn issue in the PPUUnimplemented BehaviorBehavior in original hardware that is not currently emulated

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions