gb-ctr VS mooneye-test-suite

Gekkio's GB-CTR is a good reference of the SM83 (Gameboy CPU) with access pattern withM cycle accuracy. The GB-research repo by the same author also contains a lot of information.

In case you're interested in the precise pinout, see Appendix D in gb-ctr: https://github.com/Gekkio/gb-ctr

Does anyone know of good documentation beyond: - Pan Docs - The Cycle-Accurate Game Boy Docs - Complete Technical Reference - Nitty Gritty Gameboy Cycle Timing

The thing about the Game Boy (or most consoles, really, but especially the Game Boy since it uses a custom CPU) is that we don't know all the details. People have had to reverse engineer it to figure stuff out. /u/gekkio is one of the people doing that work, and his technical reference and test suite are the (ongoing) results of that.

This is a great resource: the complete technical reference.

The thing about the Game Boy (or most consoles, really, but especially the Game Boy since it uses a custom CPU) is that we don't know all the details. People have had to reverse engineer it to figure stuff out. /u/gekkio is one of the people doing that work, and his technical reference and test suite are the (ongoing) results of that.

I tested it with the classic dmg-acid2 test rom and another rom called sprite_priority.gb which is part of the Mooneye Test Suite.

I am working on my Game Boy emulator and I'm trying to get the timer to work with mooneyes acceptance tests. Take this one as an example.

The mooneye-gb test suite has very specific tests for the timer (maybe too precise, they require emulating every little detail — but if you want that kind of accuracy, way to go)