MonkeyNES OpCode Development
The table below is used for tracking all op code related changes. The ones that I've written are shown below in black, and the spots that either have no documented op code or that I haven't written yet are shown in gray. Op codes that are coded but are known to have incorrect timing due to not having coded page boundry extra cycles are shown in blue.
This table will show you all extra OpCode information when you mouse over OpCodes
in the table. Assembly syntax, index, code, bytes, and cycles (base, page boundry,
and branch taken) are all shown. Please note that
OpCodes that have been validated to work correctly or have a test script that should work but fails will show up with a greenish or redish background respectively and will act as links to the verification output or the test script based on the radio buttons below the table.
Added a link in the key area below the table to the Master Test Bucket script. This script runs all other test scripts in one huge batch. Testing is not considered complete until the results of this master script comes back fully successful. This serves as a "second verify" opportunity that will show any errors created in opcodes that were already verified caused by correcting other subsequent opcodes.