Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
Now, the unofficial opcodes can be implemented, and then the PPU and
APU.
|
|
|
|
|
|
|
|
Also improve logging.
|
|
|
|
|
|
|
|
https://old.reddit.com/r/EmuDev/comments/15plfes/having_an_issue_with_nestest_on_my_6502_emulator/jvyck7k/
With this, it seems that all official opcodes run as nestest expects.
Now, it's the unofficial opcodes that need to be implemented.
|
|
Perhaps a refactor is in order for the arguments to the opcodes.
|
|
|
|
JSR was pushing 1 too high PC and RTS was 1 too low
RTI was only pulling the low byte of PC
|
|
It seems that is what was expected when run with nestest.
|
|
|
|
|
|
|
|
|
|
|
|
The stack's PUSH and PULL weren't proper and JSR was reading wrong
argument it seems.
|
|
|
|
So this is why tests should be written while writing the program
and instructions instead of all at once later. If this were all to be
rewritten (which it probably will), I should add tests for each opcode
instead of waiting until the end for ROM loading support.
|
|
It seems like the test ROM loads fine but the instructions are not,
but that's exactly what the test ROM is for I suppose.
|
|
They're both the same and the compiler might have already optimized it
away. It also conveys the message better in my opinion.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Of course all of these opcodes need to be tested later...
|
|
|
|
|
|
|
|
|
|
The JSON is from https://github.com/ericTheEchidna/65C02-JSON/ and
saved me a lot of time from writing the cases for each opcode by hand.
|
|
|
|
|
|
|
|
|
|
|
|
|