wup-homebrew brings native homebrew menu to the Wii U GamePad

This new open source project turns the Wii U GamePad into a standalone homebrew platform, allowing for homebrew to be played independently without the Wii U console.

21 replies Share
  • Like
  • Love
  • Wow

The wup-homebrew project brings native homebrew and a homebrew menu launcher to the Wii U gamepad.

The project runs on real Wii U gamepad hardware (model WUP-010) without any soldering and can be flashed from the Wii U console directly to the gamepad.

Once installed, holding A while powering the gamepad loads menu, which comes with an App Store and Software Updater. The gamepad still as normal when you don't hold A.

Two apps are available so far, each in its own repository and delivered through the built-in App Store:

GitHub README said:
WUP Stream - a computer's picture, sound and controls on the GamePad: libwupstream on the computer, the app on the pad
WUP Boy - Game Boy and Game Boy Color games, with save states, rewind and fast forward

You need a Wii U running Aroma and can install the mod through the gamepads own firmware update mechanism, which can take a couple of minutes. There is one important limitation: only GamePad firmware LVC rev 7677 (NR4_12_20140805_release) which is Nintendo's last is supported.

No Nintendo code or firmware is included and the emulator and install tools need dumps of your own pad to get started.

:arrow: wup-homebrew on GitHub
 

Related news

Discussion

Now this is interesting. The thought hadn't even crossed my mind that the Gamepad itself would be capable of operating standalone given its design goals, but I guess it makes sense when you consider the quick launch and remote control functions.

Looking into the project docs a bit - Does anybody know how much space this bundle actually leaves on-device for homebrew apps? The installer's README suggests that it hooks into (rather than replaces) the existing firmware to retain stock functionality, but I can see that working as a bit of a double-edged sword when the thing only has 32MB of flash.

Beyond that - How much working memory does the gamepad actually have? I did some looking around, but I couldn't find any specific number for that.
 
THIS IS SO COOL!!!!!!!!!!!!!!!!!!!!!!!!!!!

I've been waiting for something like this forever, thank you for bringing this to the front page!
 
This left me feeling... mixed. At face value, it is incredible there is now a user-friendly way to run something other than the fully tethered experience (and TV remote). I knew it was coming, but the GamePad scene has been small and silent for a long time.

But then I immediately noticed every single commit was "co-authored by" Claude. Is this actually proven to be safe to run? Has it bricked any units? For a project with no clear way of knowing how long it took to get to 1.0 and commits that look like it was fully vibe coded, I don't trust it anywhere near a discontinued piece of hardware like this.

I recognise the same author also worked on HBLauncher for SmileBasic and some other projects, but I'm not convinced, not for something where there's an extremely high chance of having to reflash it with a hardware flasher due to a bug.


Also, friendly reminder that it may be best to use the GamePad less for better longevity; the WiFi chips on Wii U and (especially) GamePad side tend to be the first part to fail in the system, and they are tailor made for the system, so replacements would have to come from a donor.
 
Last edited by lightwo,
the WiFi chips on Wii U and (especially) GamePad side tend to be the first part to fail in the system, and they are tailor made for the system, so replacements would have to come from a donor.
Every two months or so I learn about new ways to be afraid of my Wii U kicking the bucket and boy-oh-boy it is NOT a fun experience.
 
> ravensclawx
1795109223924.png
 
  • Like
Reactions: lightwo
Every two months or so I learn about new ways to be afraid of my Wii U kicking the bucket and boy-oh-boy it is NOT a fun experience.
I mean, at least these chips are fairly straightforward to replace, they're not soldered on or anything. It's just that they will only be available as long as there are healthy donors to take them out of, and they're not really that cheap to get.

But then I immediately noticed every single commit was "co-authored by" Claude. Is this actually proven to be safe to run? Has it bricked any units? For a project with no clear way of knowing how long it took to get to 1.0 and commits that look like it was fully vibe coded, I don't trust it anywhere near a discontinued piece of hardware like this.

I recognise the same author also worked on HBLauncher for SmileBasic and some other projects, but I'm not convinced, not for something where there's an extremely high chance of having to reflash it due to a bug.
Felt as much...
 
I mean, at least these chips are fairly straightforward to replace, they're not soldered on or anything. It's just that they will only be available as long as there are healthy donors to take them out of, and they're not really that cheap to get.
Let's not forget this theory
Hello, I'm new here so please excuse any formatting errors.

I picked up a Wii U recently on the cheap, sold as untested, and of course it has the famous gamepad wifi card failure. The console connects to wiimotes and the internet but the gamepad will not connect. After researching the issue, I have seen that the wifi card issue is fairly prevalent. Here is what my research has come up with and what I believe to be a potential solution that I am going to attempt on my dead card.


First off, there seems to be two part numbers available. 2878D-MICA2 and DWM-W081. iFixit provides a look at the MICA2 board without the emi shield, and after removing it from my DWM-W081, I have confirmed that the two boards are absolutely identical - same exact layout, same exact parts. I'm guessing the two part numbers may be from different production lines, but this is unconfirmed.


As for my theory on why it is dying, I believe it may be the SiGe SE5008L 5ghz amplifier chip. Based on reports I've read on symptoms of the failure before it's entirely failed, it seems that the gamepad will start by having a shorter and shorter range, eventually requiring it being within a foot or two of the console, before not being able to connect at all. To me, that sounds like a signal amplification issue rather than the main Broadcom BCM4319 chip failing.


Of course this is all just theory right now, and I need to order some SE5008L packages to test it. I also only have my one dead module, which I believe I may have damaged in the process of pulling the shield off (some of the solder mask came up while attempting to desolder it).


So that being said, if anyone knows a source where I could purchase a few dead MICA2 or DWM-W081 modules, I'd greatly appreciate it. I have all the tools to do the work, just a bit rusty.

But it appears nobody has tried so far; I'd love to but currently I don't have the equipment, money or time for it

EDIT: idk how to create those links to a post showing the nice preview
 
  • Like
Reactions: lightwo
EDIT: idk how to create those links to a post showing the nice preview
  1. Copy link on post ID (number on top right corner)
  2. Paste as plain text URL in the post

Although I suppose the copied quote is better as that preserves it in case the original post gets deleted/edited, and still links to the source.
 
Finally, at last! Seemed like it was totally possible, but nobody had figured it out until now...

It looks promising! Now, maybe I'll be able to get some use out of a second Gamepad. Looking forward to look into app development, too!
 

Site & Scene News

New Hot Discussed User Submitted