Ryujinx is gone. Suyu got taken down. Yuzu shut its doors back in 2024. If you have spent any time in the Switch emulation scene over the past two years, you already know the landscape keeps shrinking for one very specific, very old machine: the Nintendo GameCube. But GameCube emulation never had that problem, because Dolphin has quietly been the most stable, most actively developed emulator in the entire hobby for over a decade. And buried inside Dolphin is a feature almost nobody outside speedrunning and RNG-manipulation circles has ever touched: Integrated GBA, a built-in Game Boy Advance emulator that lets you plug a virtual GBA cartridge straight into a virtual GameCube link port.
That matters a lot if you own Pokémon Colosseum or Pokémon XD: Gale of Darkness, because both GameCube titles were built around trading Pokémon with a Game Boy Advance cartridge through the official Nintendo GameCube–Game Boy Advance Game Link Cable. Nobody has that physical cable and a working CRT-era GBA lying around in 2026. Dolphin does not need one. This tutorial walks through the full setup, from downloading a current Dolphin build to completing an actual trade between a GBA ROM and Colosseum or XD, plus the new Game Boy Player mode Dolphin shipped in its June 2026 build. By the end you will have a working link between two emulated Nintendo handhelds and a console that were never designed to talk to anything running on a PC.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Why Dolphin’s Integrated GBA Feature Matters for Pokémon Fans
Pokémon Colosseum and Pokémon XD: Gale of Darkness are both compatible with all five Generation III Game Boy Advance games: Ruby, Sapphire, Emerald, FireRed, and LeafGreen. That connectivity runs through the Phenac City Pokémon Center’s Trade Center, and it is bidirectional. You can send your GBA party into either GameCube game, and you can send GameCube Pokémon back out to the handheld cartridge. XD is the more interesting half of that trade, because it is the only in-game way to obtain a Lugia on a GBA or GameCube game without attending a real-world event: you snag and purify a Shadow Lugia during the story, then trade it out to your GBA cartridge.
None of that works without a link cable, and for twenty years the only way to recreate it on PC meant running two separate emulators, such as a standalone mGBA install configured for Pokémon, side by side and bridging them over a network socket. Dolphin removed that friction in July 2021, when its developers announced Integrated GBA: a stripped-down instance of the mGBA emulator built directly into Dolphin itself. Set a controller port to “GBA (Integrated),” point Dolphin at a GBA BIOS file, and the GameCube game treats the emulated handheld as if it were plugged in with a real cable. No second program, no socket configuration, no separate window to manage beyond the mGBA pop-up Dolphin spawns automatically.
What makes 2026 a good time to revisit this feature is Dolphin’s June 25 release, internally numbered 2606, which added native Game Boy Player support on top of the same embedded mGBA code. That update lets Dolphin boot standalone GBA Pokémon games through an emulated Game Boy Player accessory rather than only using the GBA as a link-cable peripheral. Combined, the two features turn Dolphin into a one-stop shop for anyone trying to reconstruct the entire Gen III Pokémon ecosystem, GameCube games included, inside a single emulator window. If your only goal is getting Colosseum and XD running smoothly on their own, without the GBA link, our dedicated Pokémon Colosseum and XD Dolphin setup guide covers that baseline configuration in more depth.
What Is Dolphin’s Integrated GBA (And How It Differs From Standalone Emulators)
Integrated GBA is not a full mGBA installation with menus, save-state slots, and a game library. It is a purpose-built, minimal version of mGBA that Dolphin spins up automatically whenever a controller port is set to “GBA (Integrated).” Its entire job is connectivity: booting a GBA ROM, exposing a save file, and staying clock-synced with Dolphin’s GameCube emulation so the two systems agree on timing during a trade or battle. The Dolphin wiki pages for link-cable-dependent titles such as The Legend of Zelda: Four Swords Adventures describe the setup in one sentence: set a GBA (Integrated) controller and make sure a GBA BIOS is configured under Options → Configuration → GameCube, and “everything else with connecting will be handled automatically.”
Dolphin gives you a second option too, labeled “GBA (TCP).” That mode talks to a genuinely separate, full-featured mGBA instance (version 0.9.0 or newer) running outside Dolphin, using the Joybus protocol over a local network socket. It is the older approach, and it still works, but it means juggling two completely separate applications, two separate configuration screens, and two separate places a setup can go wrong. For a straightforward Colosseum or XD trade, Integrated GBA is simpler in almost every case. The TCP route only earns its keep if you specifically need mGBA’s full debugging tools, cheat search, or a GBA-only feature Integrated GBA’s stripped-down build does not expose.
One more distinction worth knowing before you start: Integrated GBA can run more than one instance at once. Games such as Four Swords Adventures and Final Fantasy Crystal Chronicles support up to four simultaneous GBA links, one per player, assigned to GameCube controller ports 2, 3, and 4, with the fourth freed up by disconnecting the port 1 GameCube controller. Pokémon Colosseum and XD only ever need one GBA connection, but knowing the multi-instance ceiling matters if you also emulate other link-cable-dependent GameCube titles.
Prerequisites: Software, ROMs, and BIOS Files You Will Need
Get everything below in place before you touch a controller setting. Trying to configure Integrated GBA with a missing BIOS or a mismatched game region is the single most common source of a “GBA not detected” error later in this guide.
| Requirement | Minimum | Notes |
|---|---|---|
| Dolphin build | 5.0-14690 or newer | Any rolling release from July 2021 onward includes Integrated GBA; use the current 2606 series or later for Game Boy Player support |
| GameCube ISO/RVZ | Pokémon Colosseum or Pokémon XD: Gale of Darkness | Must be a legally dumped copy from a disc you own |
| GBA ROM | Ruby, Sapphire, Emerald, FireRed, or LeafGreen | Legally dumped from your own cartridge |
| GBA BIOS file | gba_bios.bin, 16 KB | Required for Integrated GBA to boot at all; dump it from your own GBA hardware |
| CPU | Quad-core, 3.0 GHz+ | Dolphin is single-thread heavy on the main emulation core; GBA link adds minor overhead |
| GPU | Vulkan or Direct3D 11 capable | Vulkan backend is the current recommendation for both desktop and Android builds |
| RAM | 8 GB | 16 GB recommended if you also run Dolphin’s netplay or Game Boy Player mode simultaneously |
| Storage | 4 GB free | Colosseum and XD ISOs run 1.3–1.4 GB each; leave room for save states |
A quick note on legality: Dolphin’s own project stance, and the stance we take here, is that dumping ROMs and BIOS files from hardware and physical media you personally own is the only legitimate path. Downloading dumps you did not create yourself from someone else’s cartridge or disc is piracy, full stop, regardless of how old the games are.
You will also want to confirm your GBA BIOS checksum before wasting time troubleshooting a bad dump. On Linux or macOS, run:
sha1sum gba_bios.bin
# A correct dump returns:
# 300c20df6731a33952ded8c436f7f186d25d3492On Windows PowerShell, the equivalent command is:
Get-FileHash gba_bios.bin -Algorithm SHA1If the hash does not match, redump the BIOS from your GBA hardware rather than continuing. A corrupted or incomplete BIOS file is the number-one reason Integrated GBA fails to boot at all.
Step 1-4: Installing and Configuring Dolphin for GBA Connectivity
Step 1: Download the current Dolphin build. Grab the latest rolling release from Dolphin’s official downloads page for your platform (Windows, macOS, Linux, or Android). Dolphin dropped versioned major releases like “5.0” or “6.0” back on July 2, 2024, moving instead to a continuous rolling-release model, so you will see build numbers like 2606 (June 2026) rather than a traditional version string. Any build from that series or later ships with both Integrated GBA and Game Boy Player support out of the box.
Step 2: Install and launch Dolphin, then add your game folder. Point Dolphin’s game library at the directory containing your Colosseum or XD ISO/RVZ file and your GBA ROM folder separately; Dolphin only scans for GameCube and Wii formats in the main library, so the GBA ROM does not need to live in the same folder.
Step 3: Set your GBA BIOS path. Open Options → Configuration → GameCube. In the GameCube tab, locate the GBA settings section and browse to your gba_bios.bin file. This single field is what Integrated GBA reads every time it boots; skip it and the feature silently fails.
Step 4: (Optional) Set a default GBA ROM to auto-load. Still inside the GameCube configuration tab, you can specify a default ROM path so Integrated GBA loads your chosen game automatically every time, instead of prompting you to select one manually. This is worth doing if you plan to run the same GBA cartridge against Colosseum repeatedly, for example while grinding trades for a Pokédex.
If you would rather manage this by hand-editing Dolphin’s configuration file instead of the GUI, the relevant keys live under the [Core] section of GC.ini:
[Core]
GBABIOS = C:\Dolphin\GBA\gba_bios.bin
GBARom1 = C:\Dolphin\GBA\PokemonEmerald.gba
SlotB = 9SlotB = 9 corresponds to Integrated GBA in Dolphin’s internal device numbering; setting it directly in the .ini is a faster way to script multiple GBA/GameCube pairings if you are testing several cartridges back to back.
Step 5-8: Linking Your GBA Pokémon Game to Colosseum or XD
Step 5: Open the Controllers dialog. From Dolphin’s main toolbar, click Controllers. You will see four GameCube controller port dropdowns.
Step 6: Set the correct port to “GBA (Integrated).” Port 1 stays set to your normal controller, since that is the port you play Colosseum or XD from. Set Port 2 to GBA (Integrated). This mirrors how the real hardware worked: the GameCube player used the standard controller in port 1, and the connected GBA plugged into port 2.
Step 7: Launch Colosseum or XD. Start the game normally from Dolphin’s library. As soon as the game boots, a second window titled something like “GBA1” or “Integrated GBA” will pop up alongside Dolphin’s main GameCube window. If you set a default ROM in Step 4, it loads automatically here; if not, you will see a blank mGBA-style window waiting for input.
Step 8: Load your GBA ROM if it did not auto-load. Right-click inside the Integrated GBA window, select Load ROM, and choose your Ruby, Sapphire, Emerald, FireRed, or LeafGreen file. The GBA game boots inside that secondary window exactly as if it were running on real hardware plugged into the GameCube’s second controller port.
Step 9-12: Completing the Trade and Verifying the Connection
Step 9: Meet the trade prerequisites on the GBA side. Ruby, Sapphire, and Emerald require at least two non-Egg Pokémon in your active party before the game will allow a trade with Colosseum or XD. FireRed and LeafGreen have an extra hurdle: you must upgrade Celio’s Pokémon Network Center to Link Level 2, which means handing over a Ruby and a Sapphire cartridge in-game during the Sevii Islands questline. Skip this step and the connection will appear to work, but the trade option will stay grayed out.
Step 10: Save your GBA game inside a Pokémon Center. The GameCube-to-GBA trade requires the handheld save file to be sitting at a Pokémon Center, not out in the overworld or a dungeon. Walk your character to the nearest Pokémon Center’s healer counter and save there before attempting the link.
Step 11: Navigate to the Phenac City Pokémon Center in Colosseum or XD. Inside the GameCube game, walk into the Trade Center room on the Colosseum/XD side. Select the GBA connection option; Dolphin’s Integrated GBA link means this should immediately recognize the running GBA instance without any additional cabling steps.
Step 12: Confirm the trade completes on both windows. A successful link shows the standard Pokémon trade animation on the GameCube screen, and the corresponding Pokémon should vanish from, or appear in, the GBA window’s party screen once you check it. If the trade hangs indefinitely or the GameCube game reports “no GBA detected,” right-click the Integrated GBA window and select Reset, then retry from Step 11. This single fix resolves the large majority of failed-detection cases reported by users setting this up for the first time.
New in 2026: Dolphin’s Game Boy Player Support Explained
Integrated GBA was built for link-cable connectivity, not for playing a standalone GBA game full-screen. Dolphin’s June 25, 2026 build, numbered 2606, closed that gap by adding native Game Boy Player emulation, reusing the same embedded mGBA code that powers Integrated GBA. Android Authority covered the underlying mechanism back on April 1, 2026, noting that Dolphin’s developers confirmed the feature runs on the mGBA instance already built into the emulator since 2021, rather than a new, separate GBA core.
Practically, this means you can now load a GBA Pokémon ROM through a new “Game Boy Player ROM” option in Dolphin’s settings dialog, then boot the official Game Boy Player Start-Up disc or the Game Boy Interface, and Dolphin automatically attaches the emulated accessory hardware through its INI settings. If you prefer manual control over automatic attachment, the setting lives directly in Dolphin.ini:
[Core]
HSPDevice = 2Setting HSPDevice to 2 forces Dolphin to treat the connected GBA slot as a Game Boy Player accessory rather than a link-cable peripheral. For the Colosseum/XD workflow in this tutorial you want the automatic, link-cable behavior from Steps 5-12, not Game Boy Player mode; the two features share code but serve different purposes. Game Boy Player mode is the better pick if your actual goal is playing Pokémon Ruby or Emerald full-screen through Dolphin on a big-screen TV setup, the same way the original Nintendo GameCube accessory let players do on a CRT back in 2003.
Running Multiple GBA Instances for Four-Player Link Games
Pokémon Colosseum and XD only need a single GBA connection, but if you are already deep into GameCube emulation you will likely run into other titles that expect two, three, or four simultaneous GBA links. The Legend of Zelda: Four Swords Adventures and Final Fantasy Crystal Chronicles are the two most common examples, and Dolphin can genuinely spin up four separate Integrated GBA windows at once.
The port assignment follows the same pattern the original hardware used, documented on Bulbapedia’s Group Battle page for the equivalent real-cable setup: for fewer than four GBAs, connect them to ports 2, 3, and 4 in order. To reach a fourth simultaneous GBA connection, you disconnect the GameCube controller from port 1 and assign that port to a GBA instance as well, since a real GameCube only exposes four controller ports total and one is normally reserved for the primary player’s pad.
Each additional Integrated GBA window draws its own share of CPU time, so a quad-core system that handles a single Colosseum-to-GBA link comfortably may start dropping frames with three or four instances running concurrently, especially at higher internal resolutions. If you are only working with Pokémon Colosseum or XD, you can safely ignore this multi-instance scenario entirely and stick to the single Port 2 setup from earlier in this guide.
Playing GBA-Linked Pokémon Games Over Netplay
Dolphin’s netplay documentation confirms that GBA controllers have worked over netplay via Integrated GBA since build 5.0-14690, the same release that introduced the feature in the first place. This opens up a genuinely unusual possibility: two people in different physical locations, each running their own copy of a GBA Pokémon game locally, connecting through a shared Dolphin netplay session hosted around a copy of Colosseum or XD.
The catch is that Dolphin’s netplay guide is explicit about one requirement: every participant needs their own valid GBA BIOS file configured locally on their own machine. Integrated GBA loads that BIOS automatically once configured, but it does not transmit or share it over the network connection, both for licensing reasons and because BIOS mismatches between players would desync the emulated timing Integrated GBA depends on to stay in lockstep with the host’s GameCube emulation.
To set this up, the host creates a netplay session from Dolphin’s Tools menu and shares the traversal code or direct IP with the other player, exactly as you would for any other Dolphin netplay game. Both players then need matching Dolphin builds, matching game dumps (same region and revision), and their own correctly configured GBA BIOS before the session will sync GBA connectivity correctly.
Complete Working Project: Trading a Purified Shadow Lugia From XD to a GBA Cartridge
Here is a full, start-to-finish workflow that puts everything above into practice, using the single most requested reason people look up this connectivity feature in the first place: pulling a Lugia out of Pokémon XD: Gale of Darkness and onto a portable GBA cartridge. According to XD’s own documentation, this remains the only in-game method to obtain a Lugia on a GBA or GameCube game without attending a real-world Nintendo distribution event.
- Progress through Pokémon XD’s main story until you encounter and snag the Shadow Lugia. This happens well into the campaign, at Citadark Isle.
- Return to the Purification Chamber built into your PC storage system and cycle Lugia through the machine until its Shadow status clears completely; a Shadow Pokémon cannot be traded out until it is fully purified.
- On your GBA cartridge (Ruby, Sapphire, Emerald, FireRed, or LeafGreen), confirm you meet the trade prerequisite: two non-Egg Pokémon in the active party for R/S/E, or a Link Level 2 upgrade at Celio’s Network Center for FR/LG.
- Save the GBA game while standing at a Pokémon Center counter.
- In Dolphin, set GameCube controller Port 2 to GBA (Integrated) and load your GBA ROM in the Integrated GBA window per Steps 5-8 above.
- Inside XD, walk to the Phenac City Pokémon Center Trade Center and select the connected GBA game.
- Choose the now-purified Lugia from your XD party and initiate the trade toward the GBA side.
- Confirm the trade animation completes and check your GBA game’s party or PC box; Lugia should now appear as a fully portable, tradeable Pokémon independent of your GameCube save file.
From here, Lugia (and any other Pokémon you move the same way) behaves like any normal Generation III Pokémon on your GBA cartridge, meaning it can move forward again through Pal Park once you own a Generation IV DS title, extending the lineage of a Pokémon that started life as a Shadow-type boss encounter on a GameCube disc all the way into the modern Pokémon HOME ecosystem, provided you keep migrating it forward through each subsequent generation’s official transfer method.
Verifying Your Setup With Dolphin’s Log Window
If a trade fails and the Reset trick from Step 12 does not fix it, the fastest way to find out what is actually going wrong is Dolphin’s built-in logging console rather than guessing through trial and error. Open View → Show Log from Dolphin’s menu bar, then open View → Show Log Configuration next to it. In the configuration panel, enable the SerialInterface and Core log categories, and set the verbosity level to Info or higher. Reboot Colosseum or XD with the GBA connected, and watch the log as you walk into the Phenac City Trade Center.
A healthy connection shows SerialInterface entries acknowledging a device on the relevant port the moment the GBA window finishes booting. If you instead see repeated timeout or “no response” lines tied to that port, the two most likely causes are a BIOS path that silently failed to load, or a port mismatch between what you configured in the Controllers dialog and what the game itself is polling. Save a copy of the log with File → Save Log before you start changing settings; comparing a failing log against a working one from a later attempt makes it much easier to spot exactly which line stopped appearing.
# Enable verbose GBA/SerialInterface logging from the command line instead of the GUI
dolphin-emu --logger --verbosity=info --exec="PokemonColosseum.iso"Running Dolphin from a terminal with the flags above streams the same log output directly to your console window, which is faster to search through with grep than scrolling Dolphin’s in-app log panel if you are trying to isolate a specific SerialInterface error across several boot attempts.
Batch-Testing Multiple GBA Cartridges Against the Same GameCube Save
If you own dumps of several GBA cartridges and want to check which Pokémon are eligible to move into Colosseum or XD before committing to a specific trade, it is faster to swap the GBARom1 path in GC.ini between attempts than to click through Dolphin’s file browser every time. A short shell script handles the swap and relaunch automatically:
#!/bin/bash
# swap-gba-rom.sh — relaunch Dolphin with a different GBA ROM pre-loaded
INI="$HOME/.dolphin-emu/GC/GC.ini"
ROM="$1"
ISO="$2"
if [ -z "$ROM" ] || [ -z "$ISO" ]; then
echo "Usage: ./swap-gba-rom.sh /path/to/game.gba /path/to/colosseum.iso"
exit 1
fi
sed -i "s|^GBARom1 = .*|GBARom1 = ${ROM}|" "$INI"
dolphin-emu --exec="$ISO"Save this as swap-gba-rom.sh, make it executable with chmod +x, and call it once per cartridge you want to test: ./swap-gba-rom.sh Emerald.gba PokemonXD.iso, then ./swap-gba-rom.sh FireRed.gba PokemonXD.iso, and so on. Each run boots straight into XD with the new GBA ROM already configured in Integrated GBA, which saves a meaningful amount of time if you are cataloguing which Pokémon across five old cartridges are worth pulling into a fresh Colosseum save.
Windows users can achieve the same result with a short PowerShell script that edits the equivalent GC.ini path under %USERPROFILE%\Documents\Dolphin Emulator\Config\GC.ini, then launches Dolphin.exe with the -e flag pointed at the target ISO. The logic is identical: edit the GBARom1 line, relaunch, repeat.
Dolphin Integrated GBA vs GBA (TCP) vs Physical Hardware
| Method | Setup complexity | Requires second program | Netplay support | Best for |
|---|---|---|---|---|
| Integrated GBA | Low — one BIOS path, one controller dropdown | No | Yes, since 5.0-14690 | Colosseum/XD trades, casual link-cable use |
| GBA (TCP) | Higher — separate mGBA 0.9.0+ install and socket config | Yes | Limited, host-dependent | Advanced users needing full mGBA debug tools |
| Real GBA + link cable | Highest — requires working period hardware | N/A | No | Preservation purists, TV-capture speedrunners |
For the overwhelming majority of players who just want their Ruby cartridge to talk to Colosseum again, Integrated GBA is the correct default. GBA (TCP) only becomes worth the extra setup time if you specifically need a feature the stripped-down Integrated build does not expose, such as mGBA’s built-in cheat search or its more detailed debugging console. If Dolphin itself feels like overkill for a game that does not need GBA connectivity, our Dolphin vs Primehack vs Slippi comparison breaks down which GameCube-focused fork fits which use case.
Common Pitfalls When Setting Up GBA Connectivity in Dolphin
Pitfall 1: Forgetting the GBA BIOS entirely. Integrated GBA will not boot without a valid gba_bios.bin file configured under Options → Configuration → GameCube. Skipping this step is the most common reason the feature appears “broken” on a first attempt.
Pitfall 2: Using a region-mismatched GBA ROM. A PAL Pokémon Emerald will not reliably trade with an NTSC-U Pokémon XD, and vice versa. Match your GBA ROM’s region to your GameCube ISO’s region before attempting a link.
Pitfall 3: Skipping the Celio’s Network Center upgrade on FireRed/LeafGreen. The trade option stays visible but non-functional until Link Level 2 is unlocked by handing Celio your Ruby and Sapphire cartridges in-game.
Pitfall 4: Saving outside a Pokémon Center. The GameCube-to-GBA trade specifically checks that your handheld save is anchored at a Pokémon Center. A field save or a save made mid-battle will not satisfy this requirement.
Pitfall 5: Confusing Integrated GBA with Game Boy Player mode. These two 2026-era features share the same underlying mGBA code but serve opposite purposes. Integrated GBA is for link-cable connectivity between two games; Game Boy Player mode (HSPDevice = 2) is for playing a standalone GBA ROM full-screen. Setting the wrong mode will leave your Colosseum trade permanently unable to detect a connected GBA.
Pitfall 6: Assuming Mt. Battle unlocks from the GBA link. It does not. Mt. Battle in both Colosseum and XD is unlocked through normal main-story progression and has no documented connection to GBA connectivity, despite persistent community myths suggesting otherwise.
Troubleshooting Guide: Fixes for Common Connection Failures
1. “GBA not connected” message inside Colosseum/XD. Right-click the Integrated GBA window and select Reset, then re-enter the Trade Center menu.
2. Integrated GBA window never appears at all. Confirm Port 2 (or whichever port you assigned) actually shows “GBA (Integrated)” in the Controllers dialog; it is easy to accidentally leave it set to Standard Controller or None.
3. GBA window opens but shows a black screen. This almost always means the BIOS path is empty or points to a corrupted file. Re-verify the SHA-1 checksum from the Prerequisites section.
4. Trade option is grayed out entirely in the Colosseum/XD menu. Check both trade prerequisites again: two non-Egg party Pokémon for Ruby/Sapphire/Emerald, or a completed Link Level 2 upgrade for FireRed/LeafGreen.
5. Audio desync or stuttering during the trade animation. Lower Dolphin’s internal resolution temporarily during the trade sequence; the Integrated GBA sync process is timing-sensitive and heavy GPU load can occasionally introduce a few frames of audio drift.
6. Netplay session shows a GBA BIOS mismatch error. Every participant needs an independently, correctly dumped BIOS file locally. A BIOS that works for the host will not automatically propagate to guests.
7. Dolphin crashes when closing the Integrated GBA window manually. Do not close the GBA window directly during an active session; instead, stop emulation from Dolphin’s main window first, which shuts down the linked GBA instance cleanly.
8. Default GBA ROM path stops loading after a Dolphin update. Rolling releases occasionally reset paths stored in older GC.ini files during a major internal refactor. Re-browse to your GBA ROM path manually in Options → Configuration → GameCube after any significant Dolphin update.
9. Trade completes on the GameCube side but the Pokémon never appears on GBA. Reopen your GBA save file’s party and PC boxes; some trades briefly place the incoming Pokémon in the first open PC box slot rather than the active party.
10. Game Boy Player Start-Up disc will not boot after enabling HSPDevice. Confirm you are using the correct disc image and that no controller port is simultaneously set to GBA (Integrated), since the two modes can conflict on the same port.
Advanced Tips for Performance and Save Management
Back up your GBA save file before every trading session. Integrated GBA writes save data to the same .sav format standalone mGBA uses, so you can copy it out and restore it with a normal file copy if a trade ever corrupts party data. Keep a dated backup folder rather than overwriting the same file repeatedly.
If you are chaining multiple trades in one sitting, for example moving several Pokémon back and forth to test different combinations, leave the Integrated GBA window open between trades rather than closing and reopening Dolphin each time. Re-establishing the BIOS handshake from a cold boot takes longer than simply resetting the existing session if a desync occurs.
For anyone running this setup on lower-end hardware, disable Dolphin’s higher internal resolution options specifically during the GBA link sequence, then raise them back up once you are back in normal gameplay. The GBA link handshake window is short but timing-sensitive, and shaving GPU overhead during that specific moment reduces the odds of a desync-triggered reset.
Finally, if your long-term goal is migrating a full team of Pokémon out of the GameCube era and into the current Pokémon HOME ecosystem, plan the full chain before you start: GBA cartridge to a Generation IV DS game via Pal Park, DS game to Pokémon Bank or HOME once you reach a compatible modern title, and HOME into whatever current-generation game you are actually playing today. Each hop in that chain has its own prerequisites, and skipping ahead without meeting them is the single biggest reason cross-generation Pokémon transfers stall out partway through. For a broader look at which emulator handles which Pokémon generation best before you start a migration project like this, see our roundup of the best Pokémon emulators.
Frequently Asked Questions
Do I need a real Game Boy Advance to use Dolphin’s Integrated GBA feature?
No. Integrated GBA is a software-only emulation of the connectivity a real GBA and GameCube–GBA link cable would have provided. You do need a legally dumped GBA ROM and a legally dumped GBA BIOS file, both taken from hardware you own.
Does connecting a GBA game to Pokémon Colosseum unlock Mt. Battle?
No. Mt. Battle is unlocked through Colosseum’s own main-story progression and has no documented dependency on GBA connectivity, despite a long-running community assumption to the contrary.
Can I get the Bonus Disc Jirachi using Dolphin?
The Jirachi distribution most people associate with GameCube connectivity actually comes from the separate Pokémon Colosseum Bonus Disc released in the US, not the main Colosseum game. It requires an English Ruby or Sapphire cartridge, an empty party slot, and the same GameCube–GBA link cable mechanism, so the same Integrated GBA setup applies if you have a legal dump of that Bonus Disc.
What is the difference between Integrated GBA and Dolphin’s new Game Boy Player support?
Integrated GBA connects a running GBA game to a GameCube game over an emulated link cable. Game Boy Player mode, added in Dolphin’s June 2026 build, instead emulates the physical Game Boy Player accessory so you can play a standalone GBA game full-screen through Dolphin. They share the same underlying mGBA code but are configured and used differently.
Can two players trade over the internet using Dolphin netplay and Integrated GBA?
Yes. Dolphin’s netplay guide confirms GBA controllers have worked over netplay via Integrated GBA since build 5.0-14690. Every participant needs their own correctly configured GBA BIOS file locally; the BIOS itself is never transmitted between players.
Why does my FireRed or LeafGreen cartridge refuse to trade with XD?
FireRed and LeafGreen require an extra unlock step beyond Ruby, Sapphire, and Emerald: you must upgrade Celio’s Pokémon Network Center to Link Level 2 by giving him a Ruby and a Sapphire cartridge during the in-game Sevii Islands questline before GameCube trading becomes available.
Is Dolphin still receiving updates in 2026, or has development slowed down?
Dolphin remains actively developed under a rolling-release model adopted in July 2024. The June 25, 2026 build (2606) that added Game Boy Player support, followed by a September 4, 2026 security patch (2606a), shows the project shipping meaningful updates well into 2026.
Can I run Integrated GBA on Android, or is it a desktop-only feature?
Integrated GBA and Game Boy Player support are both part of Dolphin’s shared codebase across desktop and Android builds, though performance on mobile hardware will depend heavily on your specific device’s CPU and GPU driver support.
Related Coverage
- Trade Pokémon Between Emulators: 12 Steps, No Cable [2026]
- Set Up Pretendo Network for Pokémon 3DS Trading: 13 Steps [2026]
- EmulatorJS Setup: Pokémon in Your Browser, 13 Steps [2026]
- Dolphin Triforce Arcade Setup: 12 Steps, 90 Min [2026]
- How to Set Up mGBA for Pokemon Games: 12 Steps, Free [2026]
