Gannio
@gannio.bsky.social
Programmer for the MaGMML series, and other projects. Expect variety from me, as my brain tends to jump around a lot.
Pfp by
https://bsky.app/profile/rheasimone1.bsky.social
Portfolio: https://gannio.github.io
Pfp by
https://bsky.app/profile/rheasimone1.bsky.social
Portfolio: https://gannio.github.io
By NES measurements that means apples are about 6 pixels tall.
February 10, 2026 at 6:48 PM
By NES measurements that means apples are about 6 pixels tall.
Actually, out of curiosity can Switch hardware even have support for older hardware communication in theory? Like at a hardware level is it possible?
Wii Remote makes sense because bluetooth, but I've always been curious about their other 2.4/5GHz-based methods like the DS/3DS, and Wii U gamepad.
Wii Remote makes sense because bluetooth, but I've always been curious about their other 2.4/5GHz-based methods like the DS/3DS, and Wii U gamepad.
February 6, 2026 at 7:19 PM
Actually, out of curiosity can Switch hardware even have support for older hardware communication in theory? Like at a hardware level is it possible?
Wii Remote makes sense because bluetooth, but I've always been curious about their other 2.4/5GHz-based methods like the DS/3DS, and Wii U gamepad.
Wii Remote makes sense because bluetooth, but I've always been curious about their other 2.4/5GHz-based methods like the DS/3DS, and Wii U gamepad.
Wonder if this has something to do with when GMS2 changed arguments to send args directly in instead of copy them.
Realstically this only mattered for arrays in principle, but in practice may have affected reals/strings too if execution is flawed. I know 1.4 had a similar bug with external dlls.
Realstically this only mattered for arrays in principle, but in practice may have affected reals/strings too if execution is flawed. I know 1.4 had a similar bug with external dlls.
February 2, 2026 at 11:09 PM
Wonder if this has something to do with when GMS2 changed arguments to send args directly in instead of copy them.
Realstically this only mattered for arrays in principle, but in practice may have affected reals/strings too if execution is flawed. I know 1.4 had a similar bug with external dlls.
Realstically this only mattered for arrays in principle, but in practice may have affected reals/strings too if execution is flawed. I know 1.4 had a similar bug with external dlls.
Trying to research these chips I managed to come across a further source? At least I'm pretty positive; it looks like it's covering Arte (J Bernard in the forum) asking other driver experts about whether or not overclocking was even feasible: community.osr.com/t/should-i-w...
Should I write a driver to disregard the exposed polling interval of a non-HID vendor device ?
On Apr 11, 2019, at 2:38 PM, Arte wrote: > > This is why I’d be surprised to conclude that the USB controller only receives data every 8ms, internally. Can it be so badly made that it’s another buff...
community.osr.com
February 2, 2026 at 5:40 AM
Trying to research these chips I managed to come across a further source? At least I'm pretty positive; it looks like it's covering Arte (J Bernard in the forum) asking other driver experts about whether or not overclocking was even feasible: community.osr.com/t/should-i-w...
Would love updates if you decide to pursue this, though disclaimer and all regarding firmware writing and whatnot; I dunno how powerful it can be, but it's possible writing it wrong could lead to a brick, hence why I was hesitant on going further without even knowing what chip I'm dealing with.
February 2, 2026 at 1:34 AM
Would love updates if you decide to pursue this, though disclaimer and all regarding firmware writing and whatnot; I dunno how powerful it can be, but it's possible writing it wrong could lead to a brick, hence why I was hesitant on going further without even knowing what chip I'm dealing with.
I remember having this problem with Mega Man 2 and Bass and finding that solution online back then. youtu.be/TqvNO09eauY
Thankfully I did almost everything at the end of a frame so I never ran into issues with what the nes left over, *except* if a frame lagged which I had to add an exception for.
Thankfully I did almost everything at the end of a frame so I never ran into issues with what the nes left over, *except* if a frame lagged which I had to add an exception for.
Mega Man 2 and Bass Version 1.0.0 Playthrough: Part 1
YouTube video by Gannio
youtu.be
February 2, 2026 at 12:54 AM
I remember having this problem with Mega Man 2 and Bass and finding that solution online back then. youtu.be/TqvNO09eauY
Thankfully I did almost everything at the end of a frame so I never ran into issues with what the nes left over, *except* if a frame lagged which I had to add an exception for.
Thankfully I did almost everything at the end of a frame so I never ran into issues with what the nes left over, *except* if a frame lagged which I had to add an exception for.
References to some of my research:
Reverse engineering: jefflongo.dev/posts/gc-ada...
Reddit comment who discovered the connection between 0x16 and 0x17 on these:
www.reddit.com/r/EmuDev/com...
Wii remote page on Wiibrew: wiibrew.org/wiki/Wiimote
WUP-028 overclocking: docs.google.com/document/d/1...
Reverse engineering: jefflongo.dev/posts/gc-ada...
Reddit comment who discovered the connection between 0x16 and 0x17 on these:
www.reddit.com/r/EmuDev/com...
Wii remote page on Wiibrew: wiibrew.org/wiki/Wiimote
WUP-028 overclocking: docs.google.com/document/d/1...
GameCube Adapter Reverse Engineering
Discrepancies with Emulators
jefflongo.dev
February 2, 2026 at 12:40 AM
References to some of my research:
Reverse engineering: jefflongo.dev/posts/gc-ada...
Reddit comment who discovered the connection between 0x16 and 0x17 on these:
www.reddit.com/r/EmuDev/com...
Wii remote page on Wiibrew: wiibrew.org/wiki/Wiimote
WUP-028 overclocking: docs.google.com/document/d/1...
Reverse engineering: jefflongo.dev/posts/gc-ada...
Reddit comment who discovered the connection between 0x16 and 0x17 on these:
www.reddit.com/r/EmuDev/com...
Wii remote page on Wiibrew: wiibrew.org/wiki/Wiimote
WUP-028 overclocking: docs.google.com/document/d/1...
But it could also just be used for general GBA homebrew, assuming we can run the adapter at enough of a Hz rate to respond fast enough with a GBA; and we *can* overclock this adapter ftr; Smash players do it on PC to get better response rates. But I digress.
February 2, 2026 at 12:40 AM
But it could also just be used for general GBA homebrew, assuming we can run the adapter at enough of a Hz rate to respond fast enough with a GBA; and we *can* overclock this adapter ftr; Smash players do it on PC to get better response rates. But I digress.
One of my big draws to research this btw is to see if Dolphin could someday support a direct GBA-to-PC link. It wouldn't necessarily need to facilitate direct communication like a gamecube would though; even if it could just stream the graphics from an emulated mGBA to a real GBA, that'd be enough.
February 2, 2026 at 12:36 AM
One of my big draws to research this btw is to see if Dolphin could someday support a direct GBA-to-PC link. It wouldn't necessarily need to facilitate direct communication like a gamecube would though; even if it could just stream the graphics from an emulated mGBA to a real GBA, that'd be enough.
C) Creating a means to expand that functionality if so (as well as preferably adding a backup feature for other users before writing to their firmware).
February 2, 2026 at 12:33 AM
C) Creating a means to expand that functionality if so (as well as preferably adding a backup feature for other users before writing to their firmware).
B) If they are, have an expert in this sort of thing experiment with using the 0x17 command to dump the firmware, in order to get an idea of what it does in this case, and also what room their may be for expanded functionality.
February 2, 2026 at 12:33 AM
B) If they are, have an expert in this sort of thing experiment with using the 0x17 command to dump the firmware, in order to get an idea of what it does in this case, and also what room their may be for expanded functionality.
Like I said about though, I'm not an expert on this.
The ways to investigate this further, I feel, would be to
A) Have someone willing to open up their adapter and upload high quality image of the chip layouts to see if they match or are close to the Wii Remote.
The ways to investigate this further, I feel, would be to
A) Have someone willing to open up their adapter and upload high quality image of the chip layouts to see if they match or are close to the Wii Remote.
February 2, 2026 at 12:33 AM
Like I said about though, I'm not an expert on this.
The ways to investigate this further, I feel, would be to
A) Have someone willing to open up their adapter and upload high quality image of the chip layouts to see if they match or are close to the Wii Remote.
The ways to investigate this further, I feel, would be to
A) Have someone willing to open up their adapter and upload high quality image of the chip layouts to see if they match or are close to the Wii Remote.
This has caused me to consider the theory that WUP-028 may share a similar chip, and if so, it may be possible to rewrite the EEPROM portion of the firmware; enough to add functionality for a "raw" format that just spits out what the Gamecube controller ports are sending in, regardless of protocol.
February 2, 2026 at 12:32 AM
This has caused me to consider the theory that WUP-028 may share a similar chip, and if so, it may be possible to rewrite the EEPROM portion of the firmware; enough to add functionality for a "raw" format that just spits out what the Gamecube controller ports are sending in, regardless of protocol.
Not only that, but the EEPROM also contains code! Enough seemingly to at least dump the contents of the firmware (including read-only areas): wiibrew.org/wiki/Wiimote...
Wiimote/Firmware - WiiBrew
wiibrew.org
February 2, 2026 at 12:31 AM
Not only that, but the EEPROM also contains code! Enough seemingly to at least dump the contents of the firmware (including read-only areas): wiibrew.org/wiki/Wiimote...
...but 0x16 and 0x17 are unique on the Remote; These act as write and read commands respectively that allow you to manage data within the Remote's EEPROM. This was used for an uncommon feature in Wii games of storing game data (Pokemon Battle Revolution does so with trainer cards), as well as Miis.
February 2, 2026 at 12:31 AM
...but 0x16 and 0x17 are unique on the Remote; These act as write and read commands respectively that allow you to manage data within the Remote's EEPROM. This was used for an uncommon feature in Wii games of storing game data (Pokemon Battle Revolution does so with trainer cards), as well as Miis.
I say this because the Wii Remote has a *slightly* similar instruction set, having communication in the 0x10 to 0x15 range, with Remote-exclusive features outside that range that don't exist in WUP-028. Those inside that range were replaced with GCN-specific instructions like Origins in WUP-028.
February 2, 2026 at 12:30 AM
I say this because the Wii Remote has a *slightly* similar instruction set, having communication in the 0x10 to 0x15 range, with Remote-exclusive features outside that range that don't exist in WUP-028. Those inside that range were replaced with GCN-specific instructions like Origins in WUP-028.
*However*, there are also commands 0x16 and 0x17. These commands aren't fully understood, but given their index, it's *possible* WUP-028 runs under a similar protocol to the Wii Remote (albeit in USB form instead of bluetooth).
February 2, 2026 at 12:28 AM
*However*, there are also commands 0x16 and 0x17. These commands aren't fully understood, but given their index, it's *possible* WUP-028 runs under a similar protocol to the Wii Remote (albeit in USB form instead of bluetooth).
This MITM is what makes communicating with the GBA impossible out the gate, as it relies on a seperate protocol for multiboot (link-cable payload) mode.
The protocol for the MITM uses four commands to communicate normally (0x11-0x14). 0x15 seems to just be a hard reset that requires restarting.
The protocol for the MITM uses four commands to communicate normally (0x11-0x14). 0x15 seems to just be a hard reset that requires restarting.
February 2, 2026 at 12:28 AM
This MITM is what makes communicating with the GBA impossible out the gate, as it relies on a seperate protocol for multiboot (link-cable payload) mode.
The protocol for the MITM uses four commands to communicate normally (0x11-0x14). 0x15 seems to just be a hard reset that requires restarting.
The protocol for the MITM uses four commands to communicate normally (0x11-0x14). 0x15 seems to just be a hard reset that requires restarting.
As it stands, the official adapter (WUP-028), is an HID device, that requires special drivers to properly respond as a game controller, acting as a MITM under the JOYBUS protocol.
February 2, 2026 at 12:26 AM
As it stands, the official adapter (WUP-028), is an HID device, that requires special drivers to properly respond as a game controller, acting as a MITM under the JOYBUS protocol.
(Mind you I'm not an expert on this stuff, and more hoping someone who is an expert is willing to look into this further. )
February 2, 2026 at 12:25 AM
(Mind you I'm not an expert on this stuff, and more hoping someone who is an expert is willing to look into this further. )