nes-test-roms
Collection of test ROMs for testing a NES emulator. (by christopherpow)
gb-test-roms
Collection of Game Boy test roms. (by retrio)
Our great sponsors
nes-test-roms | gb-test-roms | |
---|---|---|
11 | 17 | |
457 | 429 | |
- | 4.0% | |
0.0 | 0.0 | |
about 2 years ago | almost 9 years ago | |
Assembly | Assembly | |
- | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nes-test-roms
Posts with mentions or reviews of nes-test-roms.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-03.
- How is it possible to have CHR ROM of size 0 and yet FCEUX emulator has pattern tables?
- Nestest IRQ interrupt address begins at 0xC004 but in nestest.log it should be 0xC000
-
Any NES CPU tests that I can compare output of my CPU with output of the test?
nestest is the go-to for testing the CPU with logs. Here's the README, ROM, and log.
- My emulator can't write to address 0x8000 because its PRG ROM, but other emulators can?
- Basic CPU only test ROMS
- Confused about page crossing.
- New to developing emulation programs
- What's everyone currently working on?
- What cycles really are?
-
Question about nestest.nes
either check the results left in $02 and $03, or compare an execution log to e.g. this one.
gb-test-roms
Posts with mentions or reviews of gb-test-roms.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-08.
-
What's everyone working on?
Make sure you incorporate testing your implementation with test roms: https://github.com/retrio/gb-test-roms Do this as early in the project as possible. This will save you a huge migraine later on.
-
Some GameBoy games running at half speed
Have you tested your emulator against blargg's instruction timing test ROM? I believe this one only checks cycle counts, not memory timings: https://github.com/retrio/gb-test-roms/tree/master/instr_timing
- Need some help on how to progress with my gameboy emulator after opcodes.
- Getting weird desync on Super Mario Land (GB) between the attract mode and real gameplay. Any ideas?
-
Me again... Blarg's Gameboy test ROM
Yeah the source for cpu_instrs is in github. https://github.com/retrio/gb-test-roms/tree/master/cpu_instrs/source
-
What memory address do I load Blaargs test ROMs into? Is it 0x0100?
I actually have a question about this. I've been building a Gameboy emulator, the CPU works but when it runs the RET instruction the PC jumps to some really high address like 0x2000 or something when it's meant to jump to somewhere around 0x400 instead (after comparing it with another GB emulator). I think the RET address is meant to be read from HRAM, where the stack is stored, but when I look there it is the value around 0x2000 like I mentioned earlier. Are there any special quirks with this section of memory that I might not have implemented? I'm pretty much just reading and writing from an array for HRAM at the moment. I'm having the issue on one of blarggs cpu-instrs test roms https://github.com/retrio/gb-test-roms/blob/master/cpu_instrs/cpu_instrs.gb
-
Best documentation for the details?
So just start with implementing the CPU's fetch/decode/execute loop and a rudimentary memory bus, so that you can run simple test ROMs. You don't even need a display for many test ROMs (like Blargg's well-known test suite, which writes the results to the serial port as well as the display). After that you can do test-driven development (in a way) and focus on making more and more tests pass. Don't worry about details until you need to.
-
Gameboy emulator blargg test 02 EI failed #2
It looks like the test enables interrupts and then invokes the timer interrupt.
- Gameboy Blargg test 03 - Infinite loop
- [GameBoy] Problem with CD instruction.
What are some alternatives?
When comparing nes-test-roms and gb-test-roms you can also consider the following projects:
Ryujinx - Experimental Nintendo Switch Emulator written in C#
mooneye-gb - A Game Boy research project and emulator written in Rust
decaf-emu - Researching Wii U emulation.
jitboy - A Game Boy emulator with dynamic recompilation (JIT)
SNES - SNES Assembly Programming
DK86PC - A WIP Intel 8086 and IBM PC 5150 emulator.
dmg-acid2 - 😀 The Acid2 test, now for the original Game Boy! 😀
PSX - PlayStation Bare Metal Mips Assembly Programming
zipcpu - A small, light weight, RISC CPU soft core
gba-tests - A collection of Game Boy Advance tests.