Your comment got downvoted but I think there's deep truth in it. I've been decompiling GBA games from my childhood and it's remarkable how engineless they seem to be.
MomsAVoxell•Jul 12, 2026
Yeah, the purpose of these kinds of designs is to not have to deal with 3rd party engines. The machine is the engine.
makapuf•Jul 12, 2026
Its not a computer, its a small device. You dont have many unknown peripheral you dont have other programs. The memory and peripherals are there, just use them. Heap is complicated ? Preallocate everything. A peripheral is not used ? Just leave it there. Security ? Of what ? Thats the appeal of those devices.
flopsamjetsam•Jul 11, 2026
From the GitHub page:
> It is a Gameboy Advance from a parallel universe where RISC-V existed in 2001. A love letter to the handheld consoles from my childhood, and a 3AM drunk text to the technology that powered them.
jihadjihad•Jul 12, 2026
Thank you to the author for writing a GitHub page in 2026 that is entirely devoid of emoji.
tough•Jul 12, 2026
on the other hand having emoji on the readme is a great signal of llm-slop on my radar
jstanley•Jul 12, 2026
Isn't that the same hand?
christophilus•Jul 12, 2026
On the other hand, it does appear to be the same hand.
LukeShu•Jul 12, 2026
I mean no disrespect to Luke Wren, but he did not write it in 2026; he wrote it in 2018-2021. :)
joshu•Jul 11, 2026
i love the "hardware from an alternate universe" projects.
MomsAVoxell•Jul 12, 2026
All hardware exists in an alternative universe until it is manifest in ours.
bananaboy•Jul 12, 2026
Oh this is Luke Wren’s work. He’s an ASIC design engineer at Raspberry Pi. Amazing project, I love it!
LukeShu•Jul 12, 2026
I think "ASIC design" engineer is under-selling him--he's working on their CPU cores too!
He works at Raspberry Pi, and designed the Hazard3 RISC-V core that is at the heart of the RP2350--although he did Hazard3 in his spare time. It's actually a fork of the "Hazard5" core that he designed for the RISCBoy.
LukeShu•Jul 12, 2026
I'm surprised to see that it's OK that he has opensource AHB/APB stuff in it--I'd avoided learning them too much about them assuming that they were ARM proprietary.
bri3d•Jul 12, 2026
AMBA has been an open standard for a really long time, I think maybe since it was released?
The programmable scanline-buffer-based rendering pipeline described in the PDF is worth a read for fans of such things.
haebom•Jul 12, 2026
Is the greatest challenge in adopting this new hardware architecture the technology itself, or the lack of an existing developer ecosystem and software toolchains?
Dwedit•Jul 12, 2026
The GBA was designed around having no cache. With a few exceptions (such as Internal RAM, Video RAM, IO registers, BIOS, OAM, Palettes), everything goes out to an external bus. Going out to an external bus with no cache will basically slow you down to 80s computer speeds. Fetching instructions from the cartridge ends up being around twice as fast as a GBC.
The way around that is using a cache, and sequentially fetching multiple words. Sequential fetches can be made faster, increasing throughput, and that can hide the latency if enough instructions/data gets cached.
I wonder how this system is designed, is it going to the memory bus for all fetches, or does it use a cache?
dmitrygr•Jul 12, 2026
The author of this is one of the greatest minds of our time. While doing this is cool, he also designed the Hazard3 core in the RP2350 as well as the QSPI unit in it -- the only memory-mapped QSPI unit I've encountered so far that I've not been able to crash or hang.
MomsAVoxell•Jul 12, 2026
I echo your QSPI sentiments .. and the RP2350 is simply badass. So many, many applications. The sonic screwdriver of bus pirates ..
11 Comments
More practical would be to port https://github.com/gbdk-2020/gbdk-2020 so that https://github.com/chrismaltby/gb-studio could support it.
> It is a Gameboy Advance from a parallel universe where RISC-V existed in 2001. A love letter to the handheld consoles from my childhood, and a 3AM drunk text to the technology that powered them.
https://github.com/Wren6991/PicoDVI
The way around that is using a cache, and sequentially fetching multiple words. Sequential fetches can be made faster, increasing throughput, and that can hide the latency if enough instructions/data gets cached.
I wonder how this system is designed, is it going to the memory bus for all fetches, or does it use a cache?