What to emulate next?

[u/MrSkittlesWasTaken]

Hi. I just got into emulation development and I just finished a very basic CHIP8 Emulator. Now I don't know what my next project should be. Some say I should do Intel8080/Space Invaders while other say that I should skip that and go for GB next. What should I do next? If so, what resources? Because I can't find any tutorial like resources. I want something like [this](https://austinmorlan.com/posts/chip8_emulator/) type of resource. TYIA!

[u/jimbojetset35]

Add a debugger to your Chip8 emulator. This will be good practice when building more complex emulators where debuggers become invaluable.

[u/Ashamed-Subject-8573]

Something you're passionate about. If you're passionate about GB, do that, that's a good next step.

[u/FrequentMethod7786]

GB is fun, and not too hard

[u/JescoInc]

https://www.zimmers.net/cbmpics/c64s.html

Commodore 64 is a nice jump up. And this has everything you need. It is where I got everything I needed to build mine, granted my first emulator was a Gameboy. As jimbo said, the debugger is a good option and Ashamed's reply is great advice as well.

Do what interests you for whatever reason. My goals are for an emulation framework with stepwise CPU cycles that can support my GB, C64 emulators in addition to the Apple 2, 486, NES, Sega Genesis and SNES for emulators. Apple 2 because is it an extension of the 6502 CPU i've already done work on (thanks to the C64), the NES uses a Ricoh 2A03 (RP2A03) CPU, Sega Genesis is the 68000 CPU and SNES uses the Ricoh 5A22 (based on the 65C816).
The core idea for the framework is that the base CPU is implemented wholesale and the emulator will define the extensions on the CPU that it needs. This will allow for me to understand each of these CPU and their extensions while having something that properly uses them. In addition, it lets me understand the cost of emulating that architecture via software

[u/khedoros]

Something that you'd be interested in seeing working.

Going for a tutorial would teach you how to build that one thing, and in that one way. I think it's better to try things yourself, failing sometimes and being forced to try a different method. At least as far as learning goes. Of course, that's not very efficient if your goal is just to produce the piece of software ;-)

If you really do just want to follow a tutorial, I'll bet you could find something for most of the more commonly emulated systems.

[u/Darkmarth32]

I’d just recommend going for a console you really like and are passionate about. 8 bit consoles/handhelds are probably an easier target though for the most part.

[u/rasmadrak]

Debugger, XO-chip, GB, CGB

Those would be my recommendations. :)

[u/Alternative-Emu2000 → u/[deleted]]

That's a massive leap in complexity for someone who "just got into emulation development and I just finished a very basic CHIP8 Emulator".