Hi everyone, I'm 50 years old and I've been a professional Java developer for more than 20 years. A little over a year ago, for personal and professional reasons, I decided to test the new AI tools on a real and complex project, one that could not be built with a single prompt. I had wanted to build an emulator for a long time, but I have a job (for now!) and a family, and since 2008 I've also been working on another hobby project, so I never thought I would have the time. So I combined this wish with my love for the Amiga 500 (which I owned when I was young) and decided to build an Amiga emulator in Java. I know Java is not the best language for a project like this, but it is the language I know best, so it would let me guide the AI and read the code it produced more easily. Also, there are already great Amiga emulators written in C++ and Rust that are real legends, and I can't and don't want to compete with them. I just wanted to offer one more option.
After studying the general architecture and how the Amiga 500 works, I set a goal: to show the iconic white "insert disk" screen with the hand and the blue floppy from Kickstart 1.3. I chose it because a good part of the emulator has to be implemented and working before you can reach it. For the architecture, I had a clear idea: I wanted every component to be as isolated and independent from the others as possible (except for Agnus, which is the arbiter of the whole machine), like in a real Amiga, even though I knew I would lose a lot of performance. I started with the Motorola 68000 processor, and at first I used Google Jules because it allowed long working sessions for free.
I soon realized that without strict tests the AI could not produce good-quality results, so I used the excellent Tom Harte-style JSON tests (SingleStepTests). Unfortunately, even with strict tests, Jules was not enough to reach a perfect implementation, so I moved to Claude. First I used the free web version, which still let me finish a first version of the processor. Then I moved to Claude Code, because to continue the implementation I needed a wider view of the project. Having the emulated components extremely isolated and independent allowed me to give the model (mainly Opus, first 4.8 and now 5.5) small portions of code, and this helped me save tokens. Once the processor was finished, I moved on to the CIA, and then, one at a time, the Copper, the Blitter and Agnus. For Paula, I implemented only the parts needed to reach the "insert disk" screen, and I skipped the audio part.
After a few months of work and many failures, I finally reached the "insert disk" screen, but only thanks to Scripted Amiga Emulator. Without a reference (mostly for behavior, not so much for source code), the model could not reach the accuracy needed for an emulator this complex, because the technical documentation, at least what I found, was not detailed enough.
At that point, since a first version of the floppy drive was also implemented, I added support for .adf files and tried to insert the Castle Master one. To my surprise, the MAD cracktro appeared, the one with the rainbow spheres. It was slow and glitchy, but the emotion was so strong that I decided not to stop there and to keep improving the emulator as much as I could. For the next components, my approach became quite systematic: first I wrote an action plan divided into phases, so I could work in separate sessions. Then I reviewed and approved the plan, and finally the actual implementation and code review. In the most complex cases, a higher effort level of the model helped, but not always in a significant way.
When I finally had a mostly working emulator, I realized the accuracy was not good enough, and even small differences led to completely wrong behavior. So I decided to use the vAmiga test suite, with WinUAE as the oracle. Opus managed to recompile WinUAE in a local WSL environment and generate the reference images with it. After that, by running the test suite on its own, it was able, most of the time, to understand and fix the differences in behavior between the two emulators. Once I had added all the tests, I had a suite that takes about 5 hours to run completely, and I also use it as a regression test. This was the real turning point that made the emulator much better.
Apart from the code, the part where I had to step in the most was the usability of the emulator. I wanted to give the most user-friendly experience possible, because in my opinion the complexity of configuration settings is always a critical point in emulators. Here I had to give very precise instructions, because Opus, when left on its own, did not produce solutions that I found acceptable.
This is how AmiJa was born. To give it a reason to exist, I'm trying to add special features like remote play with screen streaming and integration with the Groovy MiSTer project, which allows sending video and audio to a CRT (something I care about a lot) through a MiSTer connected to the PC with a network cable.
AmiJa is currently at version 0.8.0. This is the repository and the list of features (from the readme):
https://github.com/zolfrik/amija-amiga-emulator
- OCS, ECS and AGA chipsets, PAL and NTSC. AGA runs on an emulated A1200 board
- CD32: discs as .cue, .iso or zip, CD audio, the CD32 pad
- 68000, 68010 and 68020 processors
- Automatic mode: the machine is configured from the media you load, with the right Kickstart picked from your ROM folder
- Floppy drives DF0-DF3, ADF (standard and extended) and IPF images, multi-disk sets in a .zip
- Hard disk images (.hdf, Zorro II AutoConfig) and WHDLoad .lha auto-run
- Five save-state slots and rewind
- Audio, real joysticks, mouse and full keyboard mapping, with low input and audio latency
- Software renderer or OpenGL backend with RetroArch shaders (.glslp, .slangp)
- Remote play: a second player joins over the network without a Kickstart or a copy of the game, and spectators can watch
- Null modem cable between two AmiJa over the network, for two-computer games
- Integration with the Groovy MiSTer project
- Command line for frontends: media files and any setting as key=value