Devolution - Gamecube loader for Wii/Wii U updated to r234

[Nintendo Maniac 64]

they didn't even know how to talk to the new wiimotes until the Dolphin devs told them.

Lawl, ok then...

Last question before I retire for the night - is there anyway to run Devolution off of a USB drive on a Wii U without the console nagging you to format the USB drive? I don't want to use a large SD card because older Wii games do not support SDHC cards and therefore I'm limited to 2GB, and AFAIK there's no way to do "SD card emulation" for Wii games like how you can do "memory card emulation" for Devolution.

[tueidj]

No, except for the "hold B to boot directly to wii mode" method to skip the nagging.

[N7Kopper]

they didn't even know how to talk to the new wiimotes until the Dolphin devs told them.

Lawl, ok then...

Last question before I retire for the night - is there anyway to run Devolution off of a USB drive on a Wii U without the console nagging you to format the USB drive? I don't want to use a large SD card because older Wii games do not support SDHC cards and therefore I'm limited to 2GB, and AFAIK there's no way to do "SD card emulation" for Wii games like how you can do "memory card emulation" for Devolution.

The only way to do this is to physically switch drives when you go from Wii U to vWii and vice-versa. (replace "switch" with "add/remove" if you don't use one in Wii U mode)
It is kind of possible to use SDHC cards with games not normally compatible with them, though. If you force the game to boot using a different IOS that supports those cards (and it doesn't crash horribly, or otherwise malfunction) then they will work. Problem being that certain apps, such as Riivolution, don't support this. It's the main reason why you use a standard 2 GB (or 4 GB if you manage to find one that isn't HC) SD Card for that app, and Wii homebrew in general. Well, that and the fact that not every IOS has USB 2.0 compatibility.

Now, for why I came here:
First, a capture log for Pokémon XD (Battle Bingo crashes after starting the second battle) http://pastebin.com/XZM6USPV

Second, the obligatory complaint about "muh LAN support isn't working with muh mario karts!" - but now I have information, and an intent to maybe write a newbie's guide if I can get it working on my end. I grabbed WireShark logs (although not logs from Devo itself - if anyone needs them let me know), and my laptop is perfectly capable of wirelessly detecting both my Wii and Wii U as they search for other games to connect to, but they never find each other. Maybe there's some simple way to diagnose the problem using DD-WRT, but I haven't found it yet. I tried testing with Dolphin, but none of the computers I own are 64 bit - and I couldn't find BBA support in any 32 bit Windows versions. I might be able to borrow a 64 bit system in a pinch, though.

Plain Text Wii U: http://pastebin.com/9C79gaHV
Raw Packets Wii U: http://pastebin.com/1wnS7DfK
Plain Text Wii: http://pastebin.com/swGGTvmA
Raw Packets Wii: http://pastebin.com/YHBakVeK

[tueidj]

Booting with a different IOS will not enable a game that doesn't support SDHC to use it. The offset value for reads/writes for non-SDHC cards is specified in bytes while SDHC cards use sectors. This value is calculated by the game's code and not the IOS, so a non-SDHC game doesn't know how to use sector addressing which is required for a SDHC card.
The Pokemon XD problem is fixed in the latest version.
Your network logs show there is some other device (HonHaiPr_0b:34:05) answering both the wii and the wiiu when they are searching for other systems. The LAN games aren't very robust, the manuals state that there shouldn't be any other devices on the network besides the gamecubes.

[Nintendo Maniac 64]

Just an FYI, that problematic wiimote still retained the Mii and SSBB profile data even after like 28 hours of having no batteries in said wiimote.

[tueidj]

Still waiting for that log.

[Nintendo Maniac 64]

Still waiting for that log.

Still waiting to a response to my question regarding said log:

So how do you want me to do it? [referring to said wifi log] Launch Devolution with said problematic wiimote? Launch Devolution with a working wiimote and then try to connect the problematic wiimote?

Another one to add to the list - launch devolution with the problematic wiimote when it's working, remove the batteries for 15 seconds, try and fail to connect it, then re-sync it?

[tueidj]

If you're just going to dick around I'm not even going to bother with you.
Your issue is "wiimote won't connect", so show a log of what happens when the wiimote fails to connect. It's not goddamn rocket science.

[Yohanov]

So tueidj as you said earlier the BBA emulation only support LAN and not online, therefore we can not play homeland online with it.

I was just curious Is this was something that might be supported one day or will it stay that way forever ?

Would be cool to play homeland online on real hardware without going the japanese gamecube console +bba route.


Also pardon me if that's a silly question but is there a way to make a Wii with bba emulation and a gamecube with a real BBA recognize each other for lan play ?

[tueidj]

A wii with BBA emulation works exactly like a gamecube with a real BBA for LAN play, it can play with other wiis/GCs/Dolphin.

[Nintendo Maniac 64]

One wifi log coming right up (BTW, is the wifi logging supposed to not work with USB Loader GX? It only seemed to work with the sample loader...)

For reference, this is the procedure I did:

1. Start Devolution app with problematic wiimote
2. Press the "2" button on said wiimote
3. Start wifi logging
4. Launch game "Nintendo Puzzle Collection"
5. When the game's title screen appeared, I pressed a bunch of buttons on the wiimote; all the player lights would flash but not connect
6. I then synced said wiimote with the console via the red sync buttons
7. The wiimote synced and the "Player 1" light was not blinking on and off
8. I ended the wifi log

Code: Select all

Wifi is ready
DFound 1 USB devices while searching for Mass Storage
Device 0: id e71f0021 VID 154B PID FA05
Got negative IPC reply for 932389E0 (-4)
USB Manufacturer: PNY Technologies
USB Product ID: USB 2.0 FD
USB Device Serial Number: 696F46EF1A0B2876
USB device reset returned 8
DSupported inquiry length: 36
Vendor ID "PNY" Product ID "USB 2.0 FD" Revision "8.07" Type 00
LUN 0 is a Direct Access device
USB_MS sector size for LUN 0: 512, max LBA: 250032127
Using storage device: "USB PNY USB 2.0 FD Rev 8.07", serial 1A0B2876
MFound an EFI partition table, 128 partition entries of 128 bytes each
Total allocated size of file: 524288 bytes in 1024 sectors
MEMCARD has 1 fragments
Memory card emulation activated (04)
Specified cluster for iso file: 000519D9
ISO file found: GPZJ Disc 1 Version 0
Disc Name: NINTENDO PUZZLE COLLECTION
Checking file fat chain...
THID device change callback was registered
HID device change: 0 devices present
HID device change callback was registered
Date of Apploader: 2002/09/05
AppStart: 81200258, rounded total_size 00001940
Apploader begin 81200278, load 81200298, finish 812002B8
Apploader Initialized.  $Revision: 31 $.
This Apploader built Sep  5 2002 05:58:53
app address: 812017E0, app section size 00000020, app offset 00000420
app address: 81201920, app section size 00000020, app offset 00000440
app address: 817FCEA0, app section size 00002000, app offset 00000440
T connection request (00 00 00)
app address: 81201800, app section size 00000100, app offset 0001EC00
app address: 80003100, app section size 00002440, app offset 0001ED00
app address: 80006780, app section size 000640C0, app offset 00021140
Bpp address: 80005540, app section size 00000740, app offset 00085200
app address: 80005C80, app section size 00000B00, app offset 00085940
app address: 8006A840, app section size 00000020, app offset 00086440
app address: 8006A860, app section size 00000020, app offset 00086460
app address: 8006A880, app section size 00053420, app offset 00086480
New WiFi channel: 1 (AFH_LO 0 AFH_HI 25)
HCI cmd complete: 03 3f 00
Found ICInvalidateRange inside Relocate() @ 80046B18
Found ICInvalidateRange inside Relocate() @ 80046B7C
Found ICInvalidateRange inside Relocate() @ 80047054
Found ICInvalidateRange inside Relocate() @ 800470B8
Patched DBAT mtspr 536 @ 80047390
Patched DBAT mtspr 537 @ 80047394
Patched DBAT mtspr 536 @ 80047398
Patched DBAT mtspr 528 @ 800473A0
Patched DBAT mtspr 529 @ 800473A4
Patched DBAT mtspr 528 @ 800473A8
Patched DBAT mtspr 540 @ 800473B0
Patched DBAT mtspr 541 @ 800473B4
Patched DBAT mtspr 540 @ 800473B8
Patched DBAT mtspr 532 @ 800473C0
Patched DBAT mtspr 533 @ 800473C4
Patched DBAT mtspr 532 @ 800473C8
Patched DBAT mtspr 536 @ 80047410
Patched DBAT mtspr 537 @ 80047414
Patched DBAT mtspr 536 @ 80047418
Patched DBAT mtspr 528 @ 80047420
Patched DBAT mtspr 529 @ 80047424
Patched DBAT mtspr 528 @ 80047428
Patched DBAT mtspr 540 @ 80047430
Patched DBAT mtspr 541 @ 80047434
Patched DBAT mtspr 540 @ 80047438
Patched DBAT mtspr 532 @ 80047440
Patched DBAT mtspr 533 @ 80047444
Patched DBAT mtspr 532 @ 80047448
Returning modem ID for EXI channel 2
<< Dolphin SDK - EXI	release build: Nov 11 2002 05:21:45 (0x2301) >>
<< Dolphin SDK - SI	release build: Sep  5 2002 05:33:08 (0x2301) >>
Set DBAT0U to 00000000 (00047390 00081002)
Set DBAT0L to 00000002 (00047394 00081002)
Set DBAT0U to 800001ff (00047398 00081002)
Set IBAT0U to 00000000 (000473a0 00081002)
Set IBAT0L to 00000002 (000473a4 00081002)
Set IBAT0U to 800001ff (000473a8 00081002)
Set DBAT2U to 00000000 (000473b0 00081002)
Set DBAT2L to 01000002 (000473b4 00081002)
Set DBAT2U to 810000ff (000473b8 00081002)
Set IBAT2U to 00000000 (000473c0 00081002)
Set IBAT2L to 01000002 (000473c4 00081002)
Set IBAT2U to 810000ff (000473c8 00081002)

Dolphin OS $Revision: 60 $.
Kernel built : Nov  5 2002 12:52:29
Console Type : Development HW-1 (10000002)
Memory 24 MB
Arena : 0x8023e140 - 0x817feea0
<< Dolphin SDK - OS	release build: Nov  5 2002 12:52:29 (0x2301) >>
<< Dolphin SDK - DVD	release build: Oct 29 2002 09:56:49 (0x2301) >>
<< Doweb socket was opened (2)
lphin SDK - CARD	release build: Sep  5 2002 05:35:20 (0x23web socket was bound
01) >>
<< web socket listening for a connection
Dolphin SDK - DSP	release build: Sep  5 2002 05:35:13 (0x2301) >>
<< Dolphin SDK - VI	release build: Sep  5 2002 05:33:13 (0x2301) >>
<< Dolphin SDK - PAD	release build: Sep  5 2002 05:34:02 (0x2301) >>
<< Dolphin SDK - GX	release build: Nov  7 2002 05:47:57 (0x2301) >>
Patched mfspr r16, sr0 @ 80040310
Patched mfspr r17, sr1 @ 80040314
Patched mfspr r18, sr2 @ 80040318
Patched mfspr r19, sr3 @ 8004031C
Patched mfspr r20, sr4 @ 80040320
Patched mfspr r21, sr5 @ 80040324
Patched mfspr r22, sr6 @ 80040328
Patched mfspr r23, sr7 @ 8004032C
Patched mfspr r24, sr8 @ 80040330
Patched mfspr r25, sr9 @ 80040334
Patched mfspr r26, sr10 @ 80040338
Patched mfspr r27, sr11 @ 8004033C
Patched mfspr r28, sr12 @ 80040340
Patched mfspr r29, sr13 @ 80040344
Patched mfspr r30, sr14 @ 80040348
Patched mfspr r31, sr15 @ 8004034C
Patched DBAT mfspr 528 @ 8004036C
Patched DBAT mfspr 529 @ 80040370
Patched DBAT mfspr 530 @ 80040374
Patched DBAT mfspr 531 @ 80040378
Patched DBAT mfspr 532 @ 8004037C
Patched DBAT mfspr 533 @ 80040380
Patched DBAT mfspr 534 @ 80040384
Patched DBAT mfspr 535 @ 80040388
Patched DBAT mfspr 536 @ 8004038C
Patched DBAT mfspr 537 @ 80040390
Patched DBAT mfspr 538 @ 80040394
Patched DBAT mfspr 539 @ 80040398
Patched DBAT mfspr 540 @ 8004039C
Patched DBAT mfspr 541 @ 800403A0
Patched mfspr SDR1 @ 800403B0
Patched mtspr sr0, r16 @ 800405B8
Patched mtspr sr1, r17 @ 800405BC
Patched mtspr sr2, r18 @ 800405C0
Patched mtspr sr3, r19 @ 800405C4
Patched mtspr sr4, r20 @ 800405C8
Patched mtspr sr5, r21 @ 800405CC
Patched mtspr sr6, r22 @ 800405D0
Patched mtspr sr7, r23 @ 800405D4
Patched mtspr sr8, r24 @ 800405D8
Patched mtspr sr9, r25 @ 800405DC
Patched mtspr sr10, r26 @ 800405E0
Patched mtspr sr11, r27 @ 800405E4
Patched mtspr sr12, r28 @ 800405E8
Patched mtspr sr13, r29 @ 800405EC
Patched mtspr sr14, r30 @ 800405F0
Patched mtspr sr15, r31 @ 800405F4
Patched DBAT mtspr 528 @ 8004060C
Patched DBAT mtspr 529 @ 80040610
Patched DBAT mtspr 530 @ 80040614
Patched DBAT mtspr 531 @ 80040618
Patched DBAT mtspr 532 @ 8004061C
Patched DBAT mtspr 533 @ 80040620
Patched DBAT mtspr 534 @ 80040624
Patched DBAT mtspr 535 @ 80040628
Patched DBAT mtspr 536 @ 8004062C
Patched DBAT mtspr 537 @ 80040630
Patched DBAT mtspr 538 @ 80040634
Patched DBAT mtspr 539 @ 80040638
Patched DBAT mtspr 540 @ 8004063C
Patched DBAT mtspr 541 @ 80040640
Patched mtspr SDR1 @ 80040650
<< Dolphin SDK - AR	release build: Sep  5 2002 05:34:27 (0x2301) >>
<< Dolphin SDK - ARQ	release build: Sep  5 2002 05:34:29 (0x2301) >>
<< Dolphin SDK - AI	release build: Sep  5 2002 05:34:25 (0x2301) >>
BT connection request (00 00 00)
BT connection request (00 00 00)
BT connection request (00 00 00)
BT connection request (00 00 00)
T connection request (00 00 00)
BT connection request (00 00 00)
BT connection request (00 00 00)
BT connection request (00 00 00)
BT connection request (00 00 00)
Vendor Event: 08
COD:08 05 00 RSSI:-51
SConnection Complete (000b)
HCI cmd complete: 01 0b 00

----------------------------------------------------------------

Holy bananas, thank you for making that post Yohanov and causing a notification email to be sent to my inbox - I've been occupied with replacing two older PCs and massively re-organizing my fileserver rig, and ended up completely forgetting about the wiimote wifi log!

Hopefully I can get it up by tomorrow.

[tueidj]

There's a bunch of stuff missing from that log, but this:

BT connection request (00 00 00)

shows that the wiimote is fried, it's not identifying itself as a game controller (those numbers should be something like 04 25 00). The wiimote's ROM is likely damaged.

[Nintendo Maniac 64]

Well that's just great.

Any idea if there's anyway to have this issue occur with commercial software, or am I just going to have to try everything and the kitchen sink in hopes that something somewhere will have an issue that may be enough for the wiimote to be accepted for RMA?

[N7Kopper]

Booting with a different IOS will not enable a game that doesn't support SDHC to use it. The offset value for reads/writes for non-SDHC cards is specified in bytes while SDHC cards use sectors. This value is calculated by the game's code and not the IOS, so a non-SDHC game doesn't know how to use sector addressing which is required for a SDHC card.
The Pokemon XD problem is fixed in the latest version.
Your network logs show there is some other device (HonHaiPr_0b:34:05) answering both the wii and the wiiu when they are searching for other systems. The LAN games aren't very robust, the manuals state that there shouldn't be any other devices on the network besides the gamecubes.

Ah. So the SDHC thing is closer to the GCN Adapter thing - you would need to patch the game to use it, not just the IOS. Gotya. (seemed like a thing that would be handled by the IOS, really)
If the latest version is released already, I guess I must have forgot to update. Don't worry, I'll test your fixes.
Thanks for the clarification. Really need to learn more about these things. I'm an embarrassment to power users everywhere. Heh. I guess I'll have to firewall off my systems somehow. Maybe create a virtual network with just those two devices? Any way to force Devolution to use a specific network profile? Or to play in LAN mode with the Classic Controller mapped so that A is A? Even if I have to write my own loader to use flags nobody else has written one to do.

[tueidj]

You don't have to write your own loader, you can just change the code for the sample loader and compile it (all the available flags are listed near the start).

[Yohanov]

A wii with BBA emulation works exactly like a gamecube with a real BBA for LAN play, it can play with other wiis/GCs/Dolphin.

Alright thanks, so about my first question concerning homeland bba support, I assume it is not part of your plans ? Not complaining, just would like to know.

[tueidj]

I don't speak japanese so I have no intention of getting that game.

[Yohanov]

Alright too bad it would have been convenient since devolution can run it without the text issues.

Sadly the translation project is not moving forward because we cant find programmers for it . But it's easily playable for non japanese speakers with the guides available online and combats are turn based so you learn fast. There are still people hosting homeland servers.

Might have been be too much work for a single niche game anyways.

[dancrane212]

So I've been playing around with the BBA emulation to try and link my Wii and Wii U with Double Dash but haven't had any luck.

Is there anything needed to enable the BBA in the first place? I may be misremembering but I was under the impression that just having a BBA connected would bring up the LAN menu on a GCN regardless if another system was connected. Don't even have that option in DD, running on Devolution, with a usb LAN adapter connected to a cascaded router or running via WiFi.

Perhaps I just need to try an offline switch instead of a router? I'll generate some logs when I give it another go - might be all the traffic like was mentioned in an earlier post.

*Scratch that, seems like running the game directly via devolution rather than USBLoader caused the issue? Getting the LAN mode option now so I can start going back through all my different network configurations again.*

[tueidj]

Sounds like you're using an old build of Devolution before BBA emulation was implemented, the LAN menu option should always appears regardless of the wii's physical networking hardware/setup.

[dancrane212]

Sounds like you're using an old build of Devolution before BBA emulation was implemented, the LAN menu option should always appears regardless of the wii's physical networking hardware/setup.

I did do that earlier where one version of Devoultion was out of date but the other was released with the BBA update but still no LAN menu. I looked at the directory structure when I tried launching directly from Devolution and saw that the ripped iso wasn't in the root of /games. Maybe that have caused an issue with launching the game from USB loader GX? It was set to use Devolution but maybe it defaulted to another loader since the games were in another path?

*Opening up USB loader after the directory change DD is now missing. Seems like that directory must have had something to do with the LAN option not showing.*

[tueidj]

Devolution doesn't know anything about the directory where the ISO is stored so it would make no difference. Sounds like the same old story of USB loaders screwing simple things up. This is why you're meant to use the sample loader to report issues...

[dancrane212]

Devolution doesn't know anything about the directory where the ISO is stored so it would make no difference. Sounds like the same old story of USB loaders screwing simple things up. This is why you're meant to use the sample loader to report issues...

Good to know!

Speaking of things that must be kinda obvious but I can't seem to figure out. Anyone have an idea what's going wrong by looking at these log files?

Worth noting my connection setup.

Modem -> Router -> Powerline Adapter -> Cascaded Router -> Wii/Wii U via ethernet cable.

A run where I captured the Wii log.

Code: Select all

Removed

A run where I captured the Wii U log.

Code: Select all

Removed

[SuperrSonic]

If you dim the display with the wiimote and then exit devolution it will remain like that on (possibly) all homebrew, but returns to normal on official software.
I wanted to ask since it looks exactly the same as the burn-in reduction level of dim, is it a hardware thing? Is that why it gets stuck? Or are they completely different things?

[tueidj]

It's the same as the burn-in reduction. Homebrew apps don't know anything about it so they don't know how to set it back to normal.