I wanted to see the IVs of my pokemon on my Gen III games but I don't have a GameCube link cable (you can use this with a modded Wii to transfer SAV files). I have an Action Replay Max Duo but getting the software set up for this is a pain - you need to install a virtual machine running an old Windows OS. I don't think the max duo was ever capable of extracting SAV files as far as I know, but I saw a post about using Claude to hack into a Samsung TV and rewrite the OS so wanted to give this a go and add some new functionality. It worked - I can now use my action replay with some custom firmware and python script to read all my sav files. You could extend these ideas to write to the cartridge but I haven't tried this yet.
Summary from Claude if you're interested in technical details:
**What it does**
- Copies the save from a GBA cartridge to a Windows 10/11 PC as a normal `.sav`. It opens in PKHeX or an emulator.
- Tested on Pokémon Ruby, Sapphire, FireRed and LeafGreen. A full 128 KB save takes about 50 seconds.
- Every save is double-checked: the GBA and the PC each compute a checksum, and they must agree. 21 backups in a row came out byte-for-byte identical.
- It also does a cartridge health report: header, ROM size, a whole-ROM checksum you can compare with known-good dumps, and read stability.
**How it works**
- The MAX DUO could only ever back up DS saves, and Datel's drivers don't work on modern Windows. The tool talks to it through Windows' generic WinUSB driver instead (one-time setup with Zadig).
- A small firmware update adds GBA save reading. It goes in the empty space inside Datel's own firmware and installs through Datel's normal update process.
- I can't share Datel's firmware, so you supply the official 1.06 update file. A script checks it and builds the new version on your PC.
**Is it safe?**
- Your game's save is only ever read. Erase and write commands are blocked on both the PC and the GBA, and Datel's own delete commands are refused outright.
- The firmware update is the one step that writes, and only to the DUO. It asks you to type UPDATE first, and you can go back to Datel's firmware the same way.
**Some things I learned along the way**
- The save chip ignores everything until the game's ROM has been read once after the DUO switches to the cartridge. I couldn't find this "wake read" documented anywhere.
- The DUO's USB chip holds one 8-byte message, and the two sides must strictly take turns. My first fast version broke that rule and stalled.
- The board has an SST 512 KB flash, an Actel antifuse FPGA marked "NDS_eX_01", and a Cypress CY7C63743 USB controller hidden under the cartridge slot. There are photos and a full write-up in the repo; as far as I can tell, it's the first public teardown of the DUO.
- **Warning for other DUO owners:** a GBA Action Replay tool on GitHub sends command 0x1C at start-up. On a MAX DUO, that command deletes a stored file.
**For the tinkerers**
The repo has everything:
- the GBA assembly for every version;
- a simulator that runs Datel's real firmware in an ARM emulator, with about 60 tests and planted bugs to test the tests;
- every lab experiment I ran on the real hardware, with the logs.
**Repo:** https://github.com/fredreckless/AR-PokeSAV-Transfer-Tool