Worklog Wii U R&D Thread (WURD)

Hi everyone, I’m not sure if I’m posting in the right place — if not, just let me know and I’ll delete this.
I’m trying to order the CafeFlex from JLCPCB, but I’m a bit of a beginner when it comes to custom PCBs.


JLCPCB gave me this error:




Then they gave me two options:


A: They enable the "replace file" button so I can try to fix it
B: I accept that the solder mask opening will expose the copper or trace, which might cause a short circuit


Thanks a lot for any help, and again, let me know if I’m posting in the wrong section!




Edit: Might be worth mentioning — I picked 0.11mm thickness and 1/3 oz copper in the JLCPCB settings, which might be tighter than expected. So maybe that’s why they flagged the spacing. Still learning the ropes here


I had the same question when I was ordering mine, so I asked Yveltal.

Screenshot 2025-04-24 085400.png


Not sure about the thickness and copper, I heard it's better to get the slightly thicker one.

Also, he does sell these on his website now, so that is an option as well.
 
Hello everyone!
I want to do a undevolting on my B1X Wii U
It's possible with stock regs?

If so, which regs reference voltage pins can I modify the voltage?
 
Does anyone think this would be a good shell (or at least shell style) for a Wii u portable? Its pretty chunky and its been proven that a lolwut fits in a dmg shell. obviously with Xbox style controls vs playstation
images (8).webp
 
heya! im a complete noob to all of this, but, as of now, how small can we make a wiiu?
 
I took last week off to work on a different project, but I'm back in the Wii U fray now. Long update incoming!

I cut out the SMC and RTC from a WUP-01 motherboard. I was so excited, I forgot to take microscope photos of the bare daughterboard! But here are some pics of the relocation.

View attachment 28975
View attachment 28976
View attachment 28977

Because I didn't rewire the SMC pins that normally enable the rear USB port protectors, I had to remove them and jumper 5V across the pads.

View attachment 28978

Despite taking shortcuts like this, the SMC and RTC still required an annoying amount of wiring. I2C for the SMC, EXI for the RTC, power button, R/B/Y LEDs, and all the GPIOs for the wireless modules. But the relocation worked!

View attachment 28980
View attachment 28979

After this, I spent some time cleaning up and consolidating the wiring and regs in preparation for a preliminary trim.
View attachment 28981
View attachment 28982
I was able to run the 3.3V line from the Pico's onboard regulator, which was convenient. I also moved the Pico to beneath the SOC (not shown).

Next up was the flash memory. Since the eMMC and NAND are tied to the console, you can't use ones from a different motherboard without some dumping/reflashing shenanigans. In other words, the NAND daughterboard must be cut from the same motherboard. This is an irreversible step and must be done at the same time as a mobo trim, which is why I saved this relocation for last.

NAND/eMMC daughterboard...
View attachment 28983View attachment 28984
...and with wires attached. The eMMC uses 4-bit SDIO (6 wires) and the TSOP NAND uses the same ONFI type interface as the Wii NAND (17 wires).
View attachment 28985View attachment 28986

Here's the trimmed Wii U motherboard after sanding. Keep in mind this is just a preliminary trim for testing purposes. :)
View attachment 28987

The NAND wiring was tricky. The NAND, eMMC, WiFi module, and even the debug port for the Pico de_Fuse modchip all connect to the same 0.8mm pitch grid of vias under the SOC! I also had to remove the Wifi module and move it to make room for the NAND daughterboard as mentioned previously.
View attachment 28989
View attachment 28996

After reconnecting Wifi and 3.3V/GND:
View attachment 28990

The fact that the components are so spread out has actually been a blessing in disguise. It means we can relocate everything with daughterboards instead of expensive custom PCBs. But a FPC for the NANDs, Wifi, and Pico wouldn't be a bad idea.
View attachment 28992

It boots! First ever trimmed Wii U! I played some BotW and WWHD, and it's totally stable. :awesome:

View attachment 28993

And finally, a size comparison with a stock mobo. Again, this is just a preliminary trim. Final trim coming soon!

View attachment 28995
as a total noob to all of this, and as someone who can only solder by making large balls and dropping them on where i want to solder too, this is truly amazing to see come together. beautifull work.
 
I just bought a second defective wii u and I made this purchase for a very specific reason: it is from the rare WUP-50 rev!!!

As already mentioned, it is defective and so I bought it for less than 20 bucks, considering that it is a WUP-50 (or even any other rev) was an excellent deal.

When I turn it on and press the Power button, the red LED flashes.
I made some measurements on the outlets of all the coils of the DC-DC converters and when I press the power button with the voltmeter connected, it "presents a value" and quickly disappears when the front LED starts to blink in red, except for the 1.15v rail (which feeds the Espresso) which has no voltage, even no peak.

Can you tell the main component responsible for generating this 1,15V voltage?
 
I just bought a second defective wii u and I made this purchase for a very specific reason: it is from the rare WUP-50 rev!!!

As already mentioned, it is defective and so I bought it for less than 20 bucks, considering that it is a WUP-50 (or even any other rev) was an excellent deal.

When I turn it on and press the Power button, the red LED flashes.
I made some measurements on the outlets of all the coils of the DC-DC converters and when I press the power button with the voltmeter connected, it "presents a value" and quickly disappears when the front LED starts to blink in red, except for the 1.15v rail (which feeds the Espresso) which has no voltage, even no peak.

Can you tell the main component responsible for generating this 1,15V voltage?
From what I can see from the documentation and WUP_50 scans, the 1.15V rail is connected to the Q1037 (Power Mosfet: TPCA 8A11-h) and Q1031 (Photo too blurry for me to read the part number, you would have to check on yours). Those are the "main" components, but there are many other factors that could be causing issues. Since you say it presents no power at all it could also be one of the other components connected to the supply rail. I believe that the WiiU uses buck converters for power, not LDO (Linear Regulators), and so there are many more than just one chip that can affect the voltage. Things you could try include:

Check continuity on the two legs of the inductor L1005

Check that C1242 and C1245 are both working

Check that R1199 has the correct resistance (should be around 7.5 miliohms, if it significantly less it may be causing problems)

Check capacitor C1394 and Resistor R1331

Also could you tell me what information is on the Q1061, it appears to be a buck converter/mosfet, but I can't tell and it only seems to appear on the 1.15V rail, so it could be a problem

The more information you give the better, do you see voltage on any of those chips? I have not looked at the chips on the bottom, those seem mostly capacitors, which shouldn't cause this problem.

* A picture of your board in high-ish quality would be very useful as any blown components will be spotted and I can double check your board matches the datasheets I have been going off of.
 
So 2 years ago I posted in this thread about SMC/RTC removal, and I just want to expand on that here.

tldr; SMC can be removed for free, RTC needs to stay (for now)

I've always had the thought that SMC can just be removed and the Wii U will work just fine, but I didn't actually prove it out. My post from 2 years ago was with de_Fuse, which was pretty much doing PoR on the SoC for the exploit effectively replacing the ICs. This is also most likely why Yveltal had issues trying to replicate it.

With my work on the Wii U Micro I figured out that the RTC is what does PoR on the SoC, so that left the SMC with module GPIOs / LEDs / Power and eject buttons (there is more it does but these are relevant to trims).
  • Module GPIOs were figured out long ago, none of the connections to the SMC are required for them to function, so that's a freebie.
  • LED's while nice to have, aren't required.
  • With the SMC removed, how are you going to power on the board? Well, if you short TP9 with GND, it will turn on. It seems that RTC is what responds to TP9 (or otherwise known as a "fake power button"). Maybe it's a leftover from early development before they added the SMC? (or you can just force the 15v PFET on lol)
  • This is also banking of anything running on the Starbuck actually caring about not getting a response from the SMC.
This time my setup consists of: SMC removed, RTC present, and a Pico purely for navigation in minute/logging. With the front buttons removed, it's not possible to navigate minute_minute without a Pico. There's a de_Fuse firmware that just takes the DEBUG port output from minute/IOSU (with a stroopwafel patch) and puts it on the Picos serial console with no reset shenanigans, and takes keyboard input from a PC and communicates that with the Wii U running minute. The software setup guide uses the fastboot minute though so this is not an issue, but with a testing setup I wanted the full minute and needed to wire a Pico (Okay I just realized I didn't NEED to if I set up the autoboot config but I like the logging still).

Anyway, it works! I'm able to launch Wii U games, vWii (though can't do much because no disc drive) and WiiVC/HAI!
nosmc_nsmbu.webp
nosmc_vwii.webp
nosmc_hai.webp

Note that this board has a bottom RTC.
Because I tested on a stock console there we're some things to do to get everything fully working:
  • Short TP173 (connected to pin 7 on WiFi) to 3v3, otherwise the WiFi module doesn't work
  • Remove R250 (connected to TP172 and pin 13 on BT), otherwise the Bluetooth module doesn't work. I figure that this is the module PoR for when the SoC is on, and with reset always low the module is never executing its code (not confirmed to be the moodule PoR but it's likely).
These are not a problem for trims. 3v3 should be wired to pin 7 on the WiFi module anyway (already done so on cafeFlex), and because the GPIOs between Bluetooth and the SMC are not required, R250 will not be connected to the pin and therefore (what is probably reset) will just be floating.
Idk the practicality of this though. SMC is an extra 2 wires for its I2C and it gives you LEDs that can be used for early-boot (boot0/boot1) diagnostics which can be useful to test a NAND relocation (not eMMC though).

Regarding RTC, because it does PoR and the SoC reads it for the "mode to boot in" (ie normally boot, ECO boot/PONLG_TMR, sdboot/UNSTBL_PWR), if RTC is removed EVERYTHING is set and it will forever go into ECO mode. ECO is standby mode and the GPU is not turned on/enabled in this mode. Idk the full extent of this but it's what requires RTC to stay for now. It can probably be replaced with heavy software patching (not sure) or a microcontroller.
 
After yesterdays post I couldn't help but look into removing RTC again.

It's actually quite easy to get rid of it, just lie!

The boot1 pseudo-code on WiiUBrew is a little hard to understand but here's what I think is happening:
The way the IOSU knows what to do (ECO, normal, reboot from vWii/HAI, etc) is a thing called "PRSH". I think boot1 does it instead of IOSU because of vWii but im not sure.
Anyway, on a stock system boot1 reads the RTC registers, specifically RTC_CONTROL0/RTC_CONTROL1 and stores the flags to a field called boot_state in the boot_info struct in PRSH, then writes it to MEM2. It also reads the SMC but it's not a problem for us.
On a system with isfshax this is mostly the same, with the difference that we have early code exec. I'm not exactly sure when in boot1 isfshax is triggered though. minute_minute being a boot1 replacement for de_Fuse does identical to boot1: reads the registers, sets the flags, writes PRSH to MEM2...
The problem is when the RTC is removed, basically every flag is set and the console thinks it's in standby mode.
But we can change minute to our hearts content!
So we lie about what flags are actually set after the initial read. minute_minute still sees the true flags but IOSU doesn't.
1794087696976.webp

(ignore the function name I wasn't expecting it to work)
What this is doing is overwriting the boot_state field with what we want. PON_SMC probably isn't needed but it works and I'm scared to change it.
I call it just before launching IOSU:
1794088214373.webp

I've published the edited code on Github: https://github.com/Lazr1026/minute_minute

Now for the hardware end of this:
RTC does PoR, so the first thing to knock out is that. I just used a U10 from a Wii board, but anything similar to it should be fine.
nortc_u10.webp

Obviously it would be on the inside of the trim line on a trim, but for testing this was a convenient spot to put it.

Now the RTC can be removed!

Everything was done on stock boards with stock regulators, so a few things are required to get everything functional. On a trim these shouldn't be a worry because either they are done anyway or not relevant.
Tying the PFET gate to GND is necessary. The cut here looks ugly and I'm not even sure if breaking the connection is required with RTC gone lol.
nortc_pfet.webp

3v3 is not provided to the WiFi module, so a jumper is required. Pin 3 on the 1v15 controller needs to be tied high. If you break the connection between ABLIC and the 5v controller that solder blob isn't necessary as it's pulled up elsewhere.
nortc_wifi.webp

Enable the 1v5 controller. Should use a 10k resistor instead of a wire but I got lazy.
no_rtc1v5.webp


And it boots! I've done this on 3 consoles so far just to make sure it can be replicated.
1794089885278.webp


Now I don't want to make any crazy claims like I did 2 years ago, so let me just say that I don't know the full implications that removing the SMC and RTC have. Idk if any games rely on the RTC being present. In theory every Wii U game should be compatible since all of the hardware goes through CafeOS/IOSU so if they're happy everything should be, but testing each game would be required.

I also want to create a little addendum to my previous post about SMC removal.
The I2C pullups (R221 and R223) need to be removed. On the original setup I cut the traces by the SoC before even trying to remove the chip so I wasn't aware they would cause issues.
nosmc.webp

Here's what shorting TP173 to 3v3 and R250 should look like:
nosmc_tp173.webp
nosmc_r250.webp


EDIT (like 5 hours after initially posting):

The custom minute_minute is no longer required.

tldr; grounding EXI0 MISO (TP176) causes every bit in boot_state to be 0's
(this is sounding very de_Fuse-y lol)

After initially posting this I was wondering how tf the code even worked and investigate why it wasn't working in the past, so I looked in my past DMs with Yveltal when we were trying to get it working in minute.
In one of the screenshots had a really weird boot_state (ffe20000) and thought "hm did I connect the pico to EXI then?". For reference, the boot_state I was getting here was 07e00000.
Uh, no. I only checked the pico setup pic after I wired up EXI to my current test boards pico but EXI was NOT wired.
I noticed something strange here though, the boot_state was all 0s? I guess the pico was holding MISO low? I was under the impression it was holding it high.
This planted a theory in my head: Surely just grounding TP176 wouldn't just work, right..? right....?
nortc_wire.webp
nortc_boot.webp

With TP176 tied to ground, it booted (Well in this pic its R65 but it's still MISO).
I even double checked this and replaced my custom minute_minute with one straight off the releases on Github, and it still booted.
I still don't know why the code worked this time. Maybe something in minute changed? Idk. I guess I don't have to bother trying to figure it out though.
 
Last edited:
Back
Top