Retrode 2026: Dump SNES + Genesis in 13 Steps, 30 Min

There is a particular fiction the retro-hardware market keeps selling, and it goes: your cartridges are safe. They are not. Mask ROM degrades slowly, the coin cell that keeps a battery-backed save alive degrades quickly, and cartridge edge connectors oxidize on their own schedule regardless of how you feel about it. The only copy of a game you genuinely control is the one that also exists as a file on storage you control. That is the entire argument for a cartridge dumper, and the Retrode is the device that made the argument approachable.

A Retrode is a small box with a Super Nintendo slot on top and a Sega Mega Drive/Genesis slot on the front. Plug it into a computer over USB and it presents your cartridge as a virtual drive: the ROM shows up as a file you can copy, and — with one setting flipped — your save shows up next to it. No soldering, no bit-banging a parallel port, no drivers on any operating system that matters. It has been the sensible on-ramp to cartridge preservation for over a decade, and in 2026 it sits at an awkward hinge: the shipping Retrode 2 works exactly as it always has, while the long-promised Retrode 3 is almost here and not orderable.

This is a tutorial for the device you can actually use today. We will dump a SNES and a Genesis cartridge end to end in thirteen steps, back up the saves, deal with the cartridges that refuse to cooperate, flash the firmware if you must, and finish with a complete, annotated configuration file. Where the Retrode 3 changes the calculus, we will say so — but you cannot write a tutorial for hardware whose own maker says the software isn't finished, so the Retrode 3 stays in its lane: a news item, not a workflow.

Why Dump Your Own Cartridges

The archivist's argument

Downloading a ROM and dumping your own are not the same act, and not only in the legal sense. A file you pulled off some anonymous set is of unknown provenance: unknown region, unknown revision, possibly a bad dump with a flipped bit that crashes a boss fight forty hours in, possibly a hack you didn't ask for. A file you dumped from a cartridge in your hand has provenance you can verify. You know the region because you're holding the region. You can hash the result and compare it against the community reference databases that catalog every known-good dump. When your hash matches, you have not just a ROM — you have a verified ROM, which is the only kind worth archiving.

The University of Maryland's Institute for Technology in the Humanities has written about exactly this workflow — using a Retrode to preserve SNES cartridges as part of serious digital-preservation practice. When a research library reaches for the same €65 box you can buy off a shop shelf, that tells you the tool is not a toy. See MITH's own writeup on preserving virtual SNES games.

The legal grey zone, stated plainly

The Machine is not your lawyer, but the Machine reads statutes. In the United States, making a personal backup of media you own lives in a genuine grey zone rather than a bright-green one. The relevant hazard is the Digital Millennium Copyright Act's Section 1201, which prohibits circumventing technological protection measures. A bare mask-ROM cartridge has no meaningful copy protection to circumvent, which is part of why cartridge dumping is treated far more gently in practice than, say, ripping an encrypted disc. Format-shifting a game you physically own into a file for your own use is categorically cleaner than downloading someone else's copy, and it is the exact activity libraries and archivists perform under recognized preservation practice.

None of this is a license to redistribute. Dump your carts, keep the files, sleep fine. Upload them and you have left the grey zone entirely.

What a Retrode actually is

Per the manufacturer's own FAQ, a Retrode is a USB interface for vintage video-game cartridges and controllers. Mechanically it does two unrelated jobs at once: it exposes the cartridge's memory as virtual files on a USB mass-storage drive, and it exposes the original controllers plugged into it as standard USB HID game controllers. That second job is easy to forget and genuinely useful — the same box that dumps your Chrono Trigger cart also lets you play it, in an emulator, with a real SNES pad, and zero additional hardware.

Retrode 2 vs. Retrode 3: What to Buy in 2026

The Retrode 2 — the one you can actually use

The Retrode 2 is the product. It has been shipping in one revision or another since the original Retrode UG folded in the summer of 2013 and the design passed through OpenPandora GmbH in March 2015 on its way to its current custodian, DragonBox. The concept itself dates to 2009, when Matthias Hullin floated it on the Pandora handheld forums. In 2026 you buy it from DragonBox in Europe for about €64.90 (the maker's own suggested price is quoted as roughly EUR 65 / USD 85), or from Stone Age Gamer in the United States for $99.99. Plug-in adapters for N64, Game Boy, and Master System run €25 each in Europe or $39.99 each stateside.

Under the shell it is an Atmel AVR microcontroller — specifically an AT90USB646 — running frozen firmware. There is no cloud, no account, no app. It is a USB peripheral from an era when that phrase meant something simple, and its simplicity is exactly why it still works flawlessly on a 2026 operating system that has never heard of it.

The Retrode 3 — finished hardware, unfinished software

The Retrode 3 is the interesting story and the wrong thing to build a workflow around. As of 2026 the official line, verbatim, is that the hardware is fully developed and the team is currently working on the software. It is targeted for availability by the end of 2026 at a price under €100, with no exact date and no confirmed final price. You cannot order one; you can only leave your email on the DragonBox notify page. DragonBox has publicly described having ten fully working prototypes and being on the hunt for developers — which is another way of saying the software is the bottleneck.

Architecturally it is a different animal. Where the Retrode 2 is a dumb-in-the-good-way mass-storage device, the Retrode 3 is a small Linux computer: Debian on an SoC, built-in Wi-Fi, presenting itself as a USB-Ethernet device so its entire interface runs in a web browser with no drivers on any host. It adds an NES slot alongside SNES and Mega Drive, reads ROM and SRAM, and — the genuinely new trick — can write flash carts: the MegaDrive DragonDrive works today, with SNES and Atari Lynx flashing promised when it ships. It is built on the open-source lineage of Sanni's Cart Reader, and the maker calls it practically unbrickable because the OS lives on an SD image you can simply reflash.

The MIPS-or-ARM question

One caveat worth flagging, because the vendor's own page cannot keep it straight: the top of the Retrode 3 description calls it a MIPS processor, while further down the same page it refers to its own ARM processor. Both cannot be true. Treat the CPU architecture as unsettled marketing copy rather than a spec you can quote with confidence — “a Linux SoC” is the honest description until the hardware ships and someone runs uname -m on it. It is a small thing, but it is exactly the kind of small thing that tells you a product is still cooking. Buy the Retrode 2 today; register interest in the Retrode 3 for later.

Prerequisites: Hardware and Software

The hardware you need

The list is mercifully short:

• A Retrode 2. The box ships with the unit, a USB cable, and an instruction sheet. That is the entire bill of materials for basic dumping.
• The cartridges you own. SNES/Super Famicom go in the wide upper slot; Sega Mega Drive/Genesis go in the shorter lower slot. Both slots are always live.
• A USB-A port and cable. The Retrode is a full-speed USB 1.1 device — do not expect it to saturate a USB-C dock, and do not put it behind a flaky unpowered hub.
• Optional: original controllers. Two SNES ports and two Sega ports live on the shell, exposed as USB HID pads.
• Optional: plug-in adapters for N64, Game Boy, or Master System if you plan to dump beyond the two built-in slots.

A can of contact cleaner and a lint-free swab are not on the box's bill of materials, but they belong on yours. Ninety percent of “my Retrode is broken” turns out to be a dirty cartridge edge connector, and no software setting fixes oxidation.

The software you need

Here is the part that ages well: essentially none. The Retrode 2 is a class-compliant USB mass-storage device and a class-compliant USB HID device, which means Windows, macOS, and Linux all mount it with drivers they already shipped with. There is nothing to install to dump a cartridge — you copy a file off a drive, and that is the whole software stack.

You will want a few things around the edges:

• A checksum utility — md5sum/sha1sum on Linux and macOS, or a Windows equivalent — to verify dumps against the emulation ecosystem's reference databases.
• An emulator or frontend to actually play the results.
• For firmware work only: Atmel FLIP on Windows, or dfu-programmer on Linux/macOS. You will not touch these unless something is wrong.

What the Retrode will not do

Set expectations before you plug anything in. The Retrode 2 will not dump cartridges that rely on certain co-processor chips (more on that below). It will not write to a normal mask-ROM cartridge — ROM stands for Read-Only Memory, and the Retrode respects the acronym. Out of the box it treats SRAM as read-only too, until you tell it otherwise. And it is not a Game Boy Advance flash-save solution, an arcade-board reader, or a disc drive. It reads cartridges. It reads them well. That is the deal.

The 13-Step Dump: SNES and Genesis

The dumping procedure, step by step

Budget about thirty minutes for your first cartridge and about ninety seconds for every one after that. The rationale matters more than the mechanics, so each step says why.

1. Clean the cartridge first. Blow out the slot, wipe the edge connector with isopropyl alcohol on a lint-free swab, and let it dry. Rationale: the single most common cause of a bad dump is a dirty contact, and cleaning is free. Do this before you blame the hardware.
2. Seat the cartridge in the correct slot. SNES/SFC in the wide upper slot, Genesis/Mega Drive in the shorter lower slot. Rationale: the slots are keyed to their systems; forcing the wrong cart is how connectors die.
3. Connect the Retrode to the computer after the cartridge is seated. Rationale: the firmware reads cartridge headers at mount time. Insert first, enumerate second, and the drive comes up already populated.
4. Wait for the drive to mount. A new removable volume named after the Retrode appears in your file manager. Rationale: enumeration and header parsing take a moment; a premature copy grabs a half-mounted drive.
5. Confirm the device enumerated as both storage and HID. On Linux, dmesg shows a mass-storage disk and an input device. Rationale: if only one endpoint appears, you have a cable or hub problem, not a cartridge problem.
6. Open the virtual drive and read the file list. You should see a ROM file named from the cartridge's internal header, plus RETRODE.CFG. Rationale: the filename comes from the cart itself, so a garbage name means a bad read.
7. Check the reported file size against reality. A 4-Mbit game reads as 512 KB; a 32-Mbit game as 4 MB. Rationale: a wildly wrong size is the earliest signal of a detection or contact fault.
8. Copy the ROM file to your computer. Drag it off the drive to a working folder. Rationale: never operate on the file in place — the virtual drive is a live view of the cartridge, not a scratch disk.
9. Copy the save file too, if present. Battery-backed carts expose a .srm next to the ROM. Rationale: the coin cell keeping that save alive is decades old and dying; this may be your last chance to rescue it.
10. Compute a checksum of your copy. Run sha1sum (or md5sum) on the file you just copied. Rationale: the hash is your proof the dump is complete and stable.
11. Dump the same cartridge a second time and compare hashes. Rationale: two identical reads mean a clean, repeatable dump; two different reads mean dirty contacts or a marginal connection — go back to step 1.
12. Compare against a reference database. Match your hash to a No-Intro/Redump entry for your region and revision. Rationale: a match promotes your file from “a dump” to “a verified good dump.”
13. Eject the drive, then remove the cartridge. Unmount in software first, then physically pull the cart. Rationale: yanking a live cartridge — hot-swapping — can corrupt the on-cart save. The user guide is explicit: eject first.

Expected output: what you should see

On Linux, plugging in a Retrode with a SNES cart seated produces enumeration like this — note both the mass-storage disk and the HID input device:

$ dmesg | tail -n 7
usb 1-2: new full-speed USB device number 7 using xhci_hcd
usb 1-2: Product: Retrode2
usb 1-2: Manufacturer: Retrode
usb-storage 1-2:1.0: USB Mass Storage device detected
scsi host6: usb-storage 1-2:1.0
sd 6:0:0:0: [sdb] Attached SCSI removable disk
input: Retrode Retrode2 as /devices/pci0000:00/.../input/input21

Mount the volume and the file listing is the payoff — ROM, save, and config, all named from the cartridge header:

$ ls -lh /media/retrode/
total 4.0M
-rwxr-xr-x 1 user user 4.0M Jul 31 12:14 'CHRONO TRIGGER.sfc'
-rwxr-xr-x 1 user user 8.0K Jul 31 12:14 'CHRONO TRIGGER.srm'
-rwxr-xr-x 1 user user  512 Jul 31 12:14 RETRODE.CFG

Verifying the dump (checksums)

Copy first, then hash the copy — never hash the file on the live drive, because a marginal contact can change the answer between reads. Two consecutive dumps that hash identically are your green light:

$ cp /media/retrode/'CHRONO TRIGGER.sfc' ~/roms/
$ cd ~/roms
$ sha1sum 'CHRONO TRIGGER.sfc'
2d9e0f...c8f1  CHRONO TRIGGER.sfc
# dump the cart a second time, then:
$ sha1sum 'CHRONO TRIGGER.sfc'
2d9e0f...c8f1  CHRONO TRIGGER.sfc   # identical = clean read

The truncated hash above is illustrative. What matters is not the specific value but that two reads agree, and that the value matches a reference entry for your cartridge's region and revision.

Backing Up Your Saves (SRAM)

Why SRAM is the real treasure

ROMs are effectively immortal — the same mask ROM that shipped in 1995 will read the same bits in 2026 and in 2056. Your saves are not. Battery-backed SRAM is kept alive by a coin cell soldered into the cartridge, and those cells are now decades past their design life. The 200-hour file on your childhood copy of a JRPG is the single most irreplaceable thing in the cartridge, and it is the thing most likely to vanish the next time the battery gives out. The Retrode can rescue it as a standard .srm file, the same format emulators use.

Unlocking write mode

By default the Retrode mounts SRAM read-only, which is the correct and cowardly default: it means you cannot accidentally clobber a save. To copy a save off the cart you need nothing special — read-only is fine for reading. To write a save back onto a cartridge, you must flip a single key in RETRODE.CFG:

# In RETRODE.CFG on the Retrode's virtual drive:
sramReadonly    0        # 0 = writable, 1 = read-only (default)

With that set, dropping a .srm onto the drive writes it into the cartridge's SRAM — which is how you restore a save to original hardware, or move a save between two copies of the same game. The LED blinks when the configuration file is written and lights during RAM access, so you get visual confirmation the write happened.

The hot-swap hazard

The user guide could not be clearer, so neither will I: writing saves and hot-swapping cartridges do not mix. Swapping a cart while the drive is mounted can potentially damage on-cartridge savegames, and the guide's advice is to eject or unplug the Retrode before changing carts. If you are only reading ROMs, a swap-and-press-RESET workflow is merely risky to the save; if you have SRAM writing enabled, it is asking for a corrupted file. Eject first. Every time.

The Co-Processor Cartridge Problem

What works: Super FX and DSP-1

The single most common Retrode misconception is that it chokes on every “special chip” SNES cartridge. It does not. Cartridges with the Super FX chip (Star Fox, Yoshi's Island, Doom) and the DSP-1 (Super Mario Kart, Pilotwings) dump perfectly fine. The Retrode reads the ROM data off those carts without complaint; the enhancement chip's behavior is then reproduced by your emulator at playback time, not by the dumper. The FAQ says as much: Super FX and DSP-1 are supported.

What doesn't: SA-1, S-DD1, and the SVP

The chips that genuinely defeat the Retrode 2 are a shorter, more specific list. The SA-1 — a faster in-cart CPU — reroutes the address lines the Retrode depends on, and it cannot read those carts. The S-DD1 decompression chip likewise breaks the read. On the Sega side, the SVP (Sega Virtua Processor) is unsupported. These are hardware-level incompatibilities, not settings you can force — no RETRODE.CFG key rescues them.

The games you'll actually miss

Concretely, here are the notable cartridges the Retrode 2 will not dump:

• SA-1: Super Mario RPG: Legend of the Seven Stars, Kirby Super Star, Kirby's Dream Land 3, and a chunk of late-life Japanese releases.
• S-DD1: Star Ocean and Street Fighter Alpha 2 — both large carts that leaned on hardware decompression.
• SVP: Virtua Racing on the Mega Drive, the sole retail SVP cart.

If your collection's crown jewel is Super Mario RPG, the Retrode is the wrong tool and you want a Sanni Cart Reader build or the forthcoming Retrode 3, which inherits Sanni's broader chip support. For everything else — the overwhelming majority of the SNES and Genesis libraries — the Retrode 2 is exactly right.

Plug-In Adapters: N64, Game Boy, Master System

The N64 adapter

The official adapter lineup currently covers three systems, and the N64 adapter is the headliner. It dumps N64 cartridge ROMs cleanly. Its caveat is saves: N64 save hardware is a zoo of EEPROM, SRAM, and Flash types, and the Retrode's firmware support for reading those is listed as pending. The adapter runs at 3.3 V, can host up to two controllers, and — like the base unit — wants to be connected before you plug the Retrode into USB. If your goal is N64 ROM preservation, it works; if your goal is rescuing an N64 save or simply playing carts, temper expectations and consider dedicated hardware such as the modern N64 clone consoles that read carts natively.

The Game Boy adapter

The GBx adapter is the most capable of the three. It dumps Game Boy, Game Boy Color, and Game Boy Advance ROMs. Game Boy and Game Boy Color SRAM saves read fine; GBA saves — again the EEPROM/Flash problem — are listed as pending. Mind the voltage: original GB and GBC cartridges are 5 V parts while GBA cartridges are 3.3 V, and the adapter handles the distinction, but it is a reminder that these are not interchangeable slots. For pure ROM dumping across three Game Boy generations from one adapter, it is hard to beat.

The Master System adapter

The SMS adapter dumps Sega Master System cartridge ROMs. Its two quirks: SRAM support is pending, and because Master System cartridges do not carry an internal header title the way SNES carts do, the generated filename is generic — you'll want to rename dumps yourself. It also handles the Game Gear's library with the right forceSystem setting, since the two Sega machines are close cousins. Note that adapters beyond these three have been discontinued over the years, largely because the vintage connectors became unobtainable — the current three are the ones you can still buy.

Firmware and DFU Flashing

The frozen firmware line

The Retrode 2's firmware is finished in the most literal sense: development stopped years ago. The last builds are 0.18c (stable) and 0.18d beta 3, both dating to around 2016. The 0.18 line's changelog added improved N64 and GBA size detection, an update to the underlying LUFA USB library, a Master System plug-in bugfix, and — usefully — Master System SRAM reading. Configuration-file support has existed since 0.17g. The firmware is built on Dean Camera's LUFA library, the standard for AVR USB stacks.

One persistent myth deserves a stake through it: there is no firmware “version 0.22” that added enhanced-chip SNES support. It does not exist. Search snippets occasionally claim it; they are wrong. The frozen line tops out at 0.18c stable / 0.18d beta 3, and no firmware update will ever make an SA-1 cart dump on Retrode 2 hardware, because the limitation is in the silicon, not the code. If you see “0.22” cited as fact, you have found a hallucination.

Entering DFU mode

You will almost never need to reflash — the firmware is frozen and it works. But if you brick a flash attempt or want to move between stable and beta, the AT90USB646 has a hardware DFU bootloader. The entry sequence is a small finger-gymnastics routine: hold the HWB button, briefly press and release RESET, then release HWB. The device drops off the USB bus as a Retrode and reappears as an Atmel DFU bootloader. On Linux you can confirm it by its well-documented bootloader ID:

$ lsusb | grep -i atmel
Bus 001 Device 009: ID 03eb:2ff9 Atmel Corp. atmega/at90 DFU bootloader

Flashing with FLIP or dfu-programmer

On Windows, Atmel's FLIP utility does the job with a GUI. On Linux or macOS, dfu-programmer is the command-line path. The sequence is erase, flash, launch:

# With the device in DFU mode (03eb:2ff9):
$ dfu-programmer at90usb646 erase
$ dfu-programmer at90usb646 flash Retrode2_0.18c.hex
$ dfu-programmer at90usb646 launch
# The Retrode re-enumerates as a normal mass-storage device.

If dfu-programmer reports no device, you are not in DFU mode — repeat the HWB/RESET dance. If it reports a permission error on Linux, you need a udev rule for the Atmel bootloader ID or a one-time run under sudo. Do not flash firmware you did not download from the official source, and do not flash at all unless you have a concrete reason; a working Retrode does not need it.

Common Pitfalls (and How to Fix Them)

Hardware and connection pitfalls

Pitfall 1 — Dirty contacts masquerading as a dead Retrode. By a wide margin the most common failure. A cartridge that dumps as garbage, wrong size, or not at all is usually oxidized. Fix: isopropyl alcohol on a lint-free swab, both the cart edge and, gently, the slot; dry fully; re-seat. Confirm with two matching hashes.

Pitfall 2 — Powering through a flaky hub. The Retrode is USB 1.1 full-speed and modest on power, but an unpowered or overloaded hub still causes intermittent enumeration and half-mounted drives. Fix: plug directly into a rear-panel USB port on a desktop, or into a powered hub.

Filesystem and data pitfalls

Pitfall 3 — Editing the ROM on the virtual drive. The mounted volume is a live view of the cartridge, not a working disk. Renaming, hashing, or opening files in place invites marginal-read errors. Fix: always copy off first, then work on the copy.

Pitfall 4 — Hot-swapping and corrupting a save. Pulling a cart while the drive is mounted can damage on-cartridge SRAM, especially with writing enabled. Fix: eject/unmount in the OS, then remove the cart. Treat the RESET-button swap as a convenience for ROM-only reading, not a save-safe operation.

Pitfall 5 — Expecting to write to a ROM. You cannot flash a normal mask-ROM cartridge with a Retrode 2; ROM is read-only by physics. Fix: adjust expectations. Writing is a Retrode 3 feature, and only for actual flash carts.

Firmware and compatibility pitfalls

Pitfall 6 — Blaming firmware for a silicon limit. No amount of reflashing makes an SA-1 or S-DD1 cart dump. Fix: recognize the chip, use a Sanni Cart Reader or wait for the Retrode 3, and ignore any claim of a magic “0.22” firmware — it does not exist.

Pitfall 7 — Game Gear detected as Master System. The SMS adapter reads Game Gear carts, but they can be misidentified. Fix: set forceSystem GG in RETRODE.CFG. A 0.18d beta specifically fixed a case where forceSystem GG was not being recognized, so keep firmware current within the frozen line if you rely on it.

Troubleshooting Table

The quick-reference table

Symptom on the left, most-likely cause and fix on the right. Work top to bottom; the cheap fixes are near the top for a reason.

Reading the LED

The Retrode's single LED is a surprisingly good diagnostic. It lights during ROM and RAM access and blinks when the configuration file is written. If you copy a ROM and the LED never flickers, the read isn't reaching the cartridge — that points at contacts or seating, not at your computer. If it blinks when you save RETRODE.CFG, your config change registered.

When it's the cartridge, not the Retrode

Before you RMA anything, isolate the variable. Dump a different cartridge of the same system: if a known-good cart dumps cleanly and hashes correctly, the Retrode is fine and your problem cart is the suspect — clean it harder, or accept it has a fault. If every cart fails identically, suspect the Retrode, the cable, or the port. This two-minute test saves a lot of misdirected frustration.

Advanced Tips

Batch dumping and scripting

The virtual-drive model makes batch work trivial: everything is just files. A tiny shell script copies whatever cart is currently mounted, checksums it, and reminds you to swap. Because the Retrode presents a plain mass-storage device, no special SDK is involved:

#!/bin/sh
# batch-dump.sh - copy + checksum whatever cart is mounted
SRC=/media/retrode
DEST=$HOME/roms/incoming
mkdir -p "$DEST"
for f in "$SRC"/*.sfc "$SRC"/*.bin "$SRC"/*.srm; do
  [ -e "$f" ] || continue
  cp -v "$f" "$DEST/"
done
cd "$DEST" && sha1sum *.sfc *.bin > checksums.txt 2>/dev/null
echo "Copied. Eject, swap cart, and re-run for the next one."

Remember to eject between carts rather than hot-swapping — the script copies data, but it cannot un-corrupt a save you damaged by yanking a live cartridge.

Forcing system and mapper detection

The auto-detection is good but not omniscient. When a cart's header lies or a region confuses it, the force* family in RETRODE.CFG takes over: forceSystem pins the console (the Game Gear case above), forceSize overrides a misread ROM size, and forceMapper corrects a bad mapper guess. Use them surgically — a forced value that's wrong produces a confidently bad dump, which is worse than an obviously bad one. Change one key, dump, verify, repeat.

Where your ROMs should live

A verified dump is only useful if you play it. The files the Retrode produces drop straight into any modern emulation setup: a Batocera build on a spare PC, a RetroPie box on a Raspberry Pi, or a pocketable target like a Miyoo Mini Plus if you want your verified library in your jeans. If you'd rather feed original cartridges into FPGA hardware for cycle-accurate playback instead of emulation, a MiSTer Multisystem is the other end of the same hobby — the Retrode preserves the bits; the FPGA replays them.

The Complete RETRODE.CFG

The annotated configuration file

Here is a complete RETRODE.CFG covering the keys the Retrode's firmware recognizes. The key names are the real ones; the values are illustrative of the format, because the maker's own configuration documentation has been folded into the main site and the canonical reference page now redirects. Treat this as a working template, verify behavior against your own dumps, and consult the primary user guide (linked below) if a key misbehaves.

; ------------------------------------------------------------
; RETRODE.CFG - place in the root of the Retrode virtual drive.
; Key names are real; values are illustrative of the format.
; Config-file parsing has existed since firmware 0.17g.
; ------------------------------------------------------------

; --- Saves (SRAM) ---
sramReadonly    0        ; 0 = allow writing SRAM back, 1 = protect (default)
segaSram16bit   0        ; 1 for the rare 16-bit-wide Sega SRAM carts

; --- System / detection ---
forceSystem     auto     ; auto | SNES | MD | GG | SMS | N64 ...
forceSize       0        ; 0 = auto-detect ROM size; else override in bytes
forceMapper     auto     ; override the cart mapper when the header lies
detectionDelay  0        ; add delay (ms) if a cart mounts before it settles
filenameChksum  0        ; 1 = append a checksum to the generated filename

; --- File extensions ---
snesRomExt      sfc      ; extension for SNES / SFC ROM dumps
segaRomExt      bin      ; extension for Mega Drive / Genesis ROM dumps
sramExt         srm      ; extension for battery-save (SRAM) files

Applying and verifying changes

Editing is refreshingly low-tech: open RETRODE.CFG on the virtual drive in any text editor, change a value, save. The LED blinks to confirm the write. Some changes take effect on the next mount, so the safe ritual is edit, save, eject, re-plug, re-read the file listing. If a key you changed had a visible effect — a different file extension, a forced system, writable saves — you'll see it immediately in the new listing.

The Retrode 3 future

Everything above describes a device whose design was frozen in 2016 and which still does its one job perfectly. The Retrode 3 promises to move all of this into a browser — dump carts, back up SRAM, and write flash carts from a web UI served off a little Linux box, with an NES slot added and the Atari Lynx arriving as a plug-in. Until its software is finished and it can actually be ordered, the Retrode 2 remains the answer to “how do I dump my cartridges in 2026.” Buy the shipping one, verify your dumps, back up your saves before the batteries finish dying, and leave your email on the notify list for the successor. The full text of the original user guide — still the most authoritative primary source — lives at the Internet Archive, and the broader product history is summarized on Wikipedia.