THIS SECTION OF THE REPO IS ONLY FOR V1.0 HARDWARE. If you have have V1.1 or newer, this firmware will NOT work on your device. No warranty, flash at your own risk, etc. etc. The firmware for the circuit that deals with updates is separate from the firmware for the rest of the device so a failed update is as easy to recover from as just attempting to update again. That being said, the firmware updates can be extremely tempermental. Sometimes it just works, sometimes it doesn't work no matter what and it just starts working again later. You have been warned.
If your device works and you're not missing <feature> that was added after release, probably just leave well enough alone. If you insist anyway but are having trouble deciding what to install, this firmware seems to be working pretty well.
A Windows PC (or Windows 10 Phone) is REQUIRED for Firmware updates. Ubuntu, macOS, Android (Samsung), and iOS (iPadOS) all tested failed. The issue appears related to how the OS itself handles mounted file systems and file transfers. I have found and tested a repeatable workaround for openSUSE users and I still need to work on paring down the steps, isolating the specific issue, and making it easily repeatable (via BASH script or something) though I am unlikely to make any progress on this. I have not found any workarounds for macOS devices aside from just installing Windows via a bootcamp partition (so good luck anyone with Apple hardware made in the last four years).
Sniffing some packets of a successful update (on Windows) and comparing to those from a failed update (on macOS), it looks like updating is handled via some form of DAPLink implementation so the observed behavior may have the same cause. Despite that, however, the listed workarounds are NOT working.
So you've decided to tinker despite the numerous warnings. I certainly don't blame you but keep in mind that I am NOT funnyplaying nor am I on their payroll. We just have a good working relationship via mutual partners. If you run into technical issues updating, no support will be provided. You have been warned. Again.
Instructions on this process in video linked above; skip to the one hour mark.
To update:
- On your favorite Windows PC (10/11 tested and verified, older versions should work too), download the firmware "update.bin" file for the firmware you wish to flash.
- File must be named "update.bin". You cannot rename after copying.
- Switch FPGA GBC on with no game inserted
- Plug console into PC via USB C data cable (USB 2.0 is fine but USB 3.0 or USB C host type cables should also work)
- Copy "update.bin" file over to 1MB "FUNNY_PLAY_" file system
- Device will automatically update and reboot
- Device may now be disconnected or switched off (or just played, I don't judge) once file copy completed
Note that sometimes file copy may fail or get stuck at around 27% and device may only be partially updated. If this happens, unplug device, power cycle, and repeat steps. If this happens repeatedly, you may attempt to copy via powershell. If it's still failing, restart your PC and try again or try a different PC.
Powershell example: Copy-Item .\update.bin -Destination e:
Copy-Item <path to "update.bin" file> -Destination <drive letter of "FUNNY_PLAY_">
These firmware files have been provided to me via Funnyplaying directly and published with their permission. I have not coded, compiled, or had any involvement on the technical side here. My only direct involvement was an unpaid* QA role. They provided me the device and firmware files, I provide(d) them actionable feedback on the device. If you have feature requests or bug reports, I recommend you contact funnyplaying directly.
Quotes
are from funnyplaying directly,
- bullet points are me paraphrasing.
I don't have proper change logs for these updates. I only have context clues from funnyplaying directly and they communicate via a translator so sometimes context is lost. Internal build numbers just look to be based on the compilation date so build 0725 is an unknown version but it was compiled from the main branch July 25th (of 2023). Sometimes there are two firmware updates the same day and FP will tack on a .1 or 01 interchangeably.
- No internal version number -- Fixes audio pop on start and adds stereo support to speaker
- Not first firmware version but first firmware version that can be flashed without a dedicated FPGA programmer. Earlier versions not provided (and not yet dumped)
- No internal version number -- Fixes GB Camera and Pokemon Crystal (US) compatibility and other SRAM/FRAM cart compatibility (insideGadgets and HDR carts)
- Adds GBC palette mode display option. Toggle this option if sprites do not render properly in games under the GBC core (e.g. GB game running under GBC core may require a different option than just using the GB core)
- "Engineering test build" -- menu open on every boot (may simply be closed)
- Unknown changes, no notes, not tested
This version is unstable Other new problems have emerged
The timing is already saturated ，Further details need to be optimized
It's better not to update yet Waiting for my new version
- Unknown changes, not tested
- No internal version number -- added variable clock rate control
- Version 0.86? I think my notes are wrong
- Looks to be missing a screen display mode, full + pixel grid
IMPORTANT -- When updating to this build or newer from an older build, it is possible to glitch your display mode. Full Screen + Pixel Grid mode was REMOVED but the configuration does NOT reset upon reflashing. Recommend change display mode before updating. If your display mode gets glitched, roll your firmware back to an earlier version, change display modes, then try again.
- Version 0.87 in the menu -- lowered speaker minimum volume
- Fixed unknown (to me) audio issues in some games. I didn't press for specifics.
- If you want factory firmware, this is it.
- Unknown changes, no notes, not tested
- Version 0.88 in the menu
- Unknown changes, not tested
- Latest stable version
- This is the version FP recommends.
- Unknown changes, not tested
There's a big problem
- Version 0.89 in the menu
- Fixed backlight management and controls
- Experimental sleep mode -- press and hold menu button to sleep or wake device
- This is the version I recommend.
- Version 0.9 in the menu
- Initial firmware on v1.1 hardware revisions
- Unknown changes
- Version 1.02 in the menu
- Updated boot screens now use Funnyplaying logos instead of Nintendo logos
Optimised left and right channels
- Fixed Tetris multiplayer link
- Graphical corruption on first boot1
- Latest test version.
Footnotes
-
After updating to the test version 1.02, my console experienced bootlooping and severe graphical corruption for the first several boots. After about five power cycles, the problem hasn't reocurred. I was able to reproduce this exact behavior on a second unit by going from the most recent firmware to this version. ↩