pandocs VS gameroy

For Gameboy emulation, one of the most valuable resources are the pandocs: https://gbdev.io/pandocs/

During the development, these were the main resources I used: * Pan Docs * CPU instruction table * CPU Manual

if you just want to learn about how the hardware works, pandocs is the definitive guide to the game boy's hardware, and gbatek helped me a ton when writing my GBA emulator (it also includes some docs on the ds/dsi fwiw)

Pandocs: https://gbdev.io/pandocs

The Ultimate Game Boy Talk has some amazing information in it. In particular, the info on the pixel fifos was brand new to me. You can certainly write an emulator that runs most software without really understanding them, though.

I recently found https://github.com/Rodrigodd/gameroy to be a very complete implementation

Hey there! I've been working on a Game Boy emulator since last year and found the GameRoy project, which translated the PPU's logic from SameBoy, the (AFAIK) most accurate GB emulator around. I basically copied the PPU logic into my emulator and replaced the "state" property (an integer) with enums for some extra clarity.

https://github.com/nicolas-siplis/feboy

https://github.com/rodrigodd/gameroy

https://github.com/LIJI32/SameBoy/

What I did was isolate the logic of every component apart from the CPU (video, sound, timer, etc.) behind a correspondent fn update(cycle_count: u64) method (like in the sound controller or in the timer). Currently, I am calling these methods every 4 cycles, but the idea is that I would only need to call it before a read or write to a component register, or before a possible interrupt (I would need to figure out if it is possible to efficiently predict the next interrupt).