gb-test-roms
PSX
| gb-test-roms | PSX | |
|---|---|---|
| 17 | 3 | |
| 429 | 103 | |
| 4.0% | - | |
| 0.0 | 0.0 | |
| almost 9 years ago | about 4 years ago | |
| Assembly | Assembly | |
| - | - |
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.
gb-test-roms
-
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.
PSX
-
Noctane: WIP PSX emulator
I am using the tests from here: https://github.com/PeterLemon/PSX
- What's everyone currently working on?
-
Duckstation got an update
Games shown are: - Hover Racing: http://www.psxdev.net/forum/viewtopic.php?t=636 - Fromage: https://chenthread.asie.pl/fromage/ - PSXNICCC Demo: https://github.com/PeterLemon/PSX/tree/master/Demo/PSXNICCC
What are some alternatives?
mooneye-gb - A Game Boy research project and emulator written in Rust
temu-vsb - TEMU ("Tandy Emulator") and VSB ("Virtual Sound Blaster"), two nifty MS-DOS TSR utilities originally developed by Andrew Zabolotny (Андрей Заболотный).
jitboy - A Game Boy emulator with dynamic recompilation (JIT)
gba-tests - A collection of Game Boy Advance tests.
Ryujinx - Experimental Nintendo Switch Emulator written in C#
DK86PC - A WIP Intel 8086 and IBM PC 5150 emulator.
dmg-acid2 - 😀 The Acid2 test, now for the original Game Boy! 😀
GBA - Game Boy Advance Bare Metal Assembly Programming
decaf-emu - Researching Wii U emulation.
nes-test-roms - Collection of test ROMs for testing a NES emulator.
Projects - Ted Fried's MicroCore Labs Projects which include microsequencer-based FPGA cores and emulators for the 8088, 8086, 8051, 6502, 68000, Z80, Risc-V, and also Typewriter and EPROM Emulator projects. MCL51, MCL64, MCL65, MCL65+, MCL68, MCL86, MCL86+, MCL86jr, MCLR5, MCLZ8