Homebrew coder builds an N64 SDK from scratch, then boots PS1 games on it

A GBAtemp developer has released Kestrel64-SDK, a from-scratch bare-metal Nintendo 64 toolchain, and used it to run a native PS1 emulator with Tekken 3 booting into gameplay.

AI-drafted from 3 sources. This story was written with AI from the outside reporting listed under Sources, and checked by automated tools before it went up. The originals have the full detail.

A developer going by celgadis84 has released Kestrel64-SDK, a Nintendo 64 development kit written entirely from scratch in C and MIPS assembly, with no dependency on either of the console's existing toolchains. As a stress test, the same project includes a proof of concept PlayStation 1 emulator running natively on N64 hardware, with Tekken 3 booting into playable, if not yet speedy, gameplay.

The release appeared on a GBAtemp thread posted by the developer, alongside a link to the source on GitHub. N64 homebrew has traditionally leaned on one of two existing stacks: Nintendo's own libultra, reverse engineered and pieced together by the community over decades, or libdragon, the open source reimplementation that most modern homebrew now targets. Kestrel64-SDK sidesteps both. The developer describes it as bare-metal, meaning it talks to the hardware directly rather than through either of those layers, with what the GBAtemp post calls “direct memory management” of the N64's PI, SI, VI and AI, the chips handling cartridge access, controller input, video output and audio respectively.

Why writing your own N64 toolchain is the hard way round

Building a console SDK without reusing existing code means reimplementing everything those libraries already solved, down to how the system boots and how memory gets mapped. The payoff, according to the thread, is control over the RSP, the N64's programmable co-processor, and the RDP, the chip that actually draws pixels. The post describes “custom RSP microcode that dispatches commands to the RDP via a ring buffer”, a queue structure that lets the RSP hand off drawing instructions without waiting on the CPU for each one. That is the kind of optimisation homebrew developers normally inherit from libultra or libdragon rather than write themselves, and doing it from first principles is presented as the whole point of the project: squeezing performance out of hardware that is now three decades old.

The PS1 emulator is the proof, not the product

The more eye-catching part of the release is the PS1 emulator, built as what the developer calls a stress test for the SDK rather than a finished tool. The GBAtemp post breaks down three components: a custom MIPS dynamic recompiler, or dynarec, which translates PS1 CPU instructions into code the N64's own MIPS-based CPU can run directly rather than interpreting them one by one; a “native GTE execution layer” handling the PS1's geometry transform engine, the fixed function unit the original console used for 3D maths; and a GPU translator that maps PS1 graphics calls onto custom RDP commands running on the RSP, effectively asking one console's graphics hardware to speak another's language.

The developer states that Tekken 3 is “bootable into gameplay” on this setup, though explicitly not at full speed, and frames ongoing work as shaving milliseconds off with each commit toward real-time execution. None of that has been independently verified beyond the GBAtemp post itself, and no benchmark figures, frame rates or wider compatibility claims appear in the thread beyond the one title named.

What is still open

What is unconfirmed is how far the PS1 emulator extends beyond Tekken 3, what the current frame rate actually is, and how usable the bare-metal SDK is for homebrew developers who are not the author. The GBAtemp thread frames the project as actively in progress, inviting feedback on “architecture ideas” and where further cycles might be squeezed out, which suggests the dynarec and RDP translation layer are still being refactored rather than settled. For now the interesting part is less that a PS1 game sort of runs on an N64, and more that someone built the entire low level plumbing needed to make that experiment possible without borrowing a single line of Nintendo's or the homebrew community's existing code.

Sources

Image: Illustration: AI-generated for Gaming World

More news from Gaming World