gbdk-2020 VS ENGAGE

If you want to program the Gameboy or Gameboy color with C or C++ the SDCC compiler is typically used: https://sdcc.sourceforge.net/ There's a ton of good info and dev tools here: https://github.com/gbdk-2020/gbdk-2020

This is a game jam where you make a Game Boy game in three months. If you don't know a lot of programming you can use GB Studio, you can learn the nitty gritty of how the Game Boy works by using assembly programming with RGBDS, or you can use C with GBDK or ZGB.

I was messing around with GBDK just last night, so I'm in no position to poke fun at you ;)

There is a c library for this. https://github.com/gbdk-2020/gbdk-2020

If you have some programming experience, you can make your game using languages ​​like C and assembly. However, you don’t need to know how to code to start making your own game. There’s a free and open source game creator named GB Studio, that allows you to create your own title using a drag and drop tool. In this case, I decided to use C with the GBDK 2020 library for my project, as it gave me adequate flexibility without the need to dive into a low-level language like assembly to do so. You can read this guide to choose which tool suits you best.

Last year i got started making Gameboy homebrew games. As a way to better learn the process, i decided to try re-making some classic games. In addition, i would post a tutorial. They say "In learning you teach, and in teaching you learn". This rings true for me, as in writing these tutorials it forces me to really analyze what aspects of game development i understand and what aspects i do not. Most recently i remade Space Invaders using GBDK-2020 and C. All source code and assets are available for free on GitHub.

To fix this, some very recent communities are working on updated versions of the library without these issues: GBDK-N and GBDK 2020. I've personally moved on to the latter, but any tutorials for the original GBDK are still valid, such as the rudimentary ones on the GBDK wiki, or most notably Gaming Monsters' Youtube chanel (which sadly didn't exist when I got into GB development lol).

Could be, take a look at the batteryless Gameboy for example: https://github.com/TUDSSL/ENGAGE

But I don't know how to design at all, and RAM on its own is a lot harder to integrate into a board, and isn't as simple as soldering 8MB PSRAM on a Teensy pad. That said, this academic group did that with An Apollo3 MCU: https://github.com/tudssl/engage The Apollo4 will have 1.8MB SRAM, which I think will be more than a lot of these boards have https://ambiq.com/apollo4/ at much lower power. The Apollo3 Blue+ has 768K SRAM.

Thanks for the analysis! I am not an engineer so I try to glean as much as I can from this so hopefully I can find the right components and discard the things that aren't needed. This board here used the same MCU in my link above: https://github.com/tudssl/engage so I am looking for ways to turn it into a solarpowered laptop with e-ink that doesn't shutoff/sleep every 10 seconds but can idle 24hrs using a few of these https://www.powerfilmsolar.com/products/electronic-component-solar-panels/indoor-light-series/ll200-2-4-75. I had considered the ESP-32WROVER with 8MB RAM but the PSRAM is not as low power as FRAM.

I became curious because this project ran a game on a 48mhz processor using FRAM: https://github.com/tudssl/engage