pandocs VS dmg-acid2

Use https://gbdev.io/pandocs/ , https://gbdev.io/gb-opcodes/optables/ and https://github.com/gbdev/awesome-gbdev to get started.

Probably the most important one (the one I've used the most for reference) was the Game Boy Pandocs.

Based on my reading of https://gbdev.io/pandocs/

The pandocs are probably the most up to date documentation about the GameBoy in existence. It's a console which is still under active research - these days it's very focused on the extremely low level hardware behaviour.

The Pandocs are easy to read and contain pretty much everything you need to know to get a basic GB emulator up-and-running. The section on the Power-Up Sequence would answer this question for you and then some. You would've gotten the answer to your question yesterday if you looked at the Memory Map section, which tells you where ROM is mapped, and then some.

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

For actual documentation, you probably know the pandocs, but there are a lot of more specific information in the docs linked in their references, especially the cycle-accurate GB docs, the GB complete technical reference by Gekkio. You can also check the source code of the relevant test roms, like the Blargg’s test roms for more general behaviour and the MooneyeGB test suite for more specific things.

For the Game Boy, being a closed system, there's fewer resources. Nintendo made a programming manual, but it's not very good. Pandocs is a good supplement: https://gbdev.io/pandocs/

Very cool article!

If you want to know more about the hardware side of the Game Boy (Color), have a look at the Pan Docs: https://gbdev.io/pandocs/

It's been revamped in the recent years, in terms of presentation. I do kind of miss the old version which had a refreshing "old-school" UI like the RFCs of the IETF, but the newest version is IMHO much more usable when developing an emulator.

My Game Boy emulator has almost passed dmg-acid2, except that it has the "Eye displayed instead of right chin" failure mode. The README says that this signals an issue with the "window internal line counter," but I don't see where that's documented. Can someone enlighten me?

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.

For everything beyond opcodes, and especially graphics, the pandocs go over almost everything you need. For testing graphics, you can use the dmg-acid2 test roms which have tests for most of the common graphics errors.

Adequate PPU emulation (passes dmg-acid2 test). This emulator uses Pixel FIFO, as opposed to common scanline renderer.

acid-dmg, this is a really nice PPU test, you can try to complete it step by step.