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

There are two honest ways to get a Super Nintendo game onto a computer. You can download somebody else's ROM and inherit their bad dump, their region, their header edits, and whatever legal weather is currently blowing through your jurisdiction. Or you can pull the data off the cartridge already sitting in your drawer — byte for byte, verifiable against a public database — and know precisely what you have. The Retrode does the second thing, and it does almost nothing else, which is exactly why it has survived for over a decade while flashier gadgets came and went.

It is a plastic brick with a SNES slot on top and a Mega Drive slot on the bottom. Plug it into USB and it lies to your operating system, politely, claiming to be a small removable drive with your game sitting on it as a file. No installer, no vendor app, no account. This tutorial covers the device you can actually buy today — the Retrode 2 — with a running eye on the one you cannot buy yet, the Retrode 3, which DragonBox has now been promising “by the end of the year” for several end-of-years running. Budget about thirty minutes for your first cartridge and roughly ninety seconds for every one after it.

Why Dump Your Own Cartridges

The preservation case

A cartridge is not immortal. The mask ROM holding the game's code is genuinely durable — it will likely outlive everyone reading this — but the little CR2032 battery keeping your saved games alive is a chemical timer, and on most SNES and Mega Drive carts that timer started ticking in the early 1990s. Thirty-odd years in, the SRAM that stores your Chrono Trigger playthrough is running on fumes. Dumping the cartridge captures two different things: the ROM, which you want because your specific board revision and region may differ from the scene dump everyone else passes around, and the save, which you want because it is about to evaporate whether you back it up or not.

There is also the small matter of knowing what you actually have. A dump you make yourself can be hashed and checked against a public database such as No-Intro; a matching checksum tells you the read was perfect and the cartridge is a known-good copy. A ROM you downloaded tells you nothing except that a stranger once had a file with that name. Preservation institutions understand this distinction well — the University of Maryland's digital-humanities lab, MITH, has written publicly about using a Retrode to preserve SNES cartridges precisely because it produces an auditable, first-generation dump rather than a copy of a copy.

The legal grey, and why dumping is the clean path

The Machine is obligated to note that “I own the cartridge” is not the airtight legal defence the internet insists it is. In the United States there is no clear statutory right to format-shift a video game the way there arguably is for a CD you ripped in 2003; the closest thing is a patchwork of DMCA §1201 anti-circumvention rules and the narrow archival exemptions the Library of Congress renews every three years. None of that is legal advice, and none of it is fully settled.

What is not grey is the comparison. Dumping a cartridge you physically own does not involve acquiring, hosting, or distributing anyone else's copyrighted data. It is the same act an archivist performs, on hardware an archivist would recognise, producing a file that never leaves your possession. If you are going to draw a line, that is the cleanest side of it — categorically cleaner than downloading a stranger's dump, and a good deal more honest than pretending a handheld preloaded with a suspiciously round 6,041 games is a preservation project.

What the Retrode is, precisely

Strip away the nostalgia and the Retrode is a boring, well-behaved USB peripheral. When you plug it in it enumerates as a composite device: one part is a USB mass-storage endpoint — the fake thumb drive holding your ROM and save as files — and the other part is a set of USB HID gamepads, so the original SNES and Sega controllers you plug into its ports show up to your PC as standard game controllers. The official Retrode FAQ describes exactly this: cartridges appear as virtual files, controllers appear as HID-class devices, and the whole thing needs no drivers on Windows, macOS, or Linux.

Wikipedia's entry, useful as a neutral starting point, describes the Retrode as a USB adapter that lets you use game cartridges and controllers directly with emulators. That is the entire pitch. It is not a flash cart, it does not play games by itself, and — this is the part people trip over — it cannot write a ROM back onto a cartridge. ROM stands for read-only memory, and the Retrode takes that literally.

Retrode 2 vs Retrode 3: What Actually Ships

Retrode 2: the product that exists

Everything you can do today, you do with the Retrode 2. It is still manufactured and still sold. In Europe, DragonBox lists it at €64.90, with the optional plug-in adapters at around €25 each; in the United States, Stone Age Gamer carries it at $99.99 with adapters at $39.99. The manufacturer's own site quotes a suggested price of roughly “EUR 65 / USD 85.” Whatever the reseller, the box is spartan: the unit, a mini-USB cable, and an instruction sheet. There is no software in the box because there is no software to install.

Inside is an Atmel AVR microcontroller, the AT90USB646, running firmware built on Dean Camera's LUFA USB stack. That chip is the whole brain. It reads the cartridge's address and data lines, assembles the bytes into a file, and presents that file over USB. The SNES/SFC slot is the wide one on top; the Mega Drive/Genesis slot is the shorter one underneath. Along the front edge sit two SNES controller ports and two Sega ports, so you can pass original pads straight through to the PC.

Retrode 3: finished hardware, unfinished software

The Retrode 3 is the reason this article keeps one eye on the horizon, and the reason you should not wait for it if you have cartridges to dump this month. As of mid-2026 it is not for sale. DragonBox's product page carries a “notify me” button and nothing else — no order button, no firm date. The stated target is availability “by the end of the year” at a price “under €100,” with both figures explicitly unconfirmed because of component lead times. The page's status line is blunt: “The hardware is fully developed and we are currently working on the software.” A DragonBox social post put it more colourfully — ten fully working prototypes in hand, and a public call for developers.

On paper it is a genuine platform rather than a dongle refresh. It runs a full Linux userland (Debian) with built-in Wi-Fi, and instead of pretending to be a thumb drive it registers as a USB-Ethernet device, so you drive the entire thing from a web browser with — again — no drivers. It adds an NES slot alongside SNES/SFC and Mega Drive/Genesis, reads both ROM and SRAM, and, crucially, can write to certain flash carts: MegaDrive DragonDrive support is described as working today, with SNES and Atari Lynx flashing promised at launch. The read routines are adapted from Sanni's open-source Cart Reader, and fixes flow both ways between the two projects.

The processor nobody at DragonBox can agree on

Here is a detail that tells you exactly how finished the Retrode 3's marketing is: its own product page cannot decide what CPU it uses. The opening description calls it a MIPS processor; a few paragraphs down the same page refers to “its own ARM processor and a Linux operating system (Debian).” Both cannot be true. Treat the specific instruction set as unsettled — it is a small Linux SoC of some description — and treat anyone quoting the CPU as gospel with appropriate suspicion. When the hardware is done and the software isn't, the copy is the last thing to get proofread.

For the lore: the Retrode was conceived in 2009 by Matthias Hullin, who first floated it on the OpenPandora forums. It was sold through a small German company, Retrode UG, which wound down in the summer of 2013; the Retrode 2 hardware revision came back to market via OpenPandora GmbH in March 2015, and the line lives at DragonBox today. Historical footnote for the pricing archaeologists: TrendHunter's old coverage pegged the very first Retrode's pre-order at $84.99. That number is a museum piece, not a current price — do not let it anchor your expectations against today's €64.90 / $99.99.

Prerequisites: Hardware and Software

Hardware you actually need

The list is short and unglamorous. You need a Retrode 2; the mini-USB data cable it ships with (or any known-good data cable — more on that landmine later); a computer with a spare USB port, ideally a rear port on a desktop or a powered hub rather than a dainty laptop side port; and at least one cartridge. If you want to pass controllers through you need the original SNES or Sega pads. If you want anything beyond SNES and Mega Drive you need the relevant plug-in adapter, sold separately.

One quiet prerequisite that pays for itself: a way to clean cartridge contacts. Ninety-percent-plus isopropyl alcohol and a lint-free swab will resolve more “bad dumps” than any config-file tweak. Do not take a pencil eraser to the edge connector — it abrades the gold plating and leaves grit in the slot. The single most common reason a cartridge dumps at half its real size or produces a garbled filename is not the Retrode; it is thirty years of oxide on the pins.

Software (there isn't any)

The Retrode 2 needs no drivers and no companion application. What you will actually want is a small supporting cast: a checksum utility to verify dumps (sha256sum ships with macOS and Linux; on Windows, certutil -hashfile is built in), a text editor for the config file, and an emulator or frontend to confirm the ROM runs. For the last one, a current stable build of RetroArch is the pragmatic choice; the libretro documentation covers which core to load for each system, and it is worth reading rather than guessing.

When you plug the Retrode in on Linux, you should see it announce itself as a mass-storage device. Expected output from dmesg looks roughly like this:

$ dmesg | tail -5
usb 1-2: new full-speed USB device number 7 using xhci_hcd
usb 1-2: New USB device found, idVendor=..., idProduct=...
usb 1-2: Manufacturer: Retrode
usb 1-2: Product: Retrode
usb-storage 1-2:1.0: USB Mass Storage device detected
scsi 6:0:0:0: Direct-Access     Retrode  Retrode           PQ: 0 ANSI: 2

On macOS it appears under /Volumes; on Windows it takes a drive letter. No dialog, no install. If your system stays silent, jump to the troubleshooting table — nine times out of ten the cable is charge-only.

Firmware version check

The Retrode 2's firmware is frozen, and that is not the tragedy it sounds like. The last stable build is 0.18c, dated 22 April 2016, with a 0.18d beta 3 floating around from the same era. Config-file support — the feature that makes the device genuinely flexible — has existed since 0.17g. Because the hardware never changed, a firmware from 2016 dumps a cartridge in 2026 exactly as well as it did the day it shipped. Confirm your version before you troubleshoot anything, so you are debugging from a known baseline; if you are on something older than 0.17g and want the config features, the firmware section covers the flash.

The 13-Step Dump

What follows is the full sequence for a SNES or Mega Drive cartridge on the Retrode 2. Read the rationale on each step — the “why” is what turns a working dump into a reliable habit. After the list you will find the expected output at the key checkpoints.

1. Inspect and clean the cartridge. Look at the edge connector under a light; if it is dull or grimy, wipe it with 99% isopropyl alcohol and let it dry fully. Rationale: dirty contacts cause the overwhelming majority of half-size dumps and garbled filenames, and no software setting fixes a bad electrical connection.
2. Confirm your firmware version. Note whether you are on 0.18c / 0.18d beta 3 or something older. Rationale: config support needs 0.17g or later, and knowing your baseline means you are not chasing a bug that a flash would fix.
3. Connect the Retrode with a data cable — into a rear or powered port. Rationale: charge-only cables deliver enough power to light the LED but carry no data lines, so the drive never appears; underpowered front-panel hubs cause intermittent reads.
4. Wait for it to mount as a removable drive. Give the OS a second or two to enumerate the composite device. Rationale: it is USB mass storage, so there is nothing to install, but yanking your attention away before it finishes mounting is how people conclude, wrongly, that it is broken.
5. Seat the cartridge fully, then tap RESET. The lower of the two buttons is RESET. Rationale: the Retrode reads the cartridge at mount time; pressing RESET forces a re-scan, which is how you refresh the drive after inserting or reseating a cart.
6. Watch the LED. It should flicker as the Retrode walks the cartridge's address space. Rationale: LED activity is your first confirmation that the device is actually reading silicon and not just sitting powered but idle.
7. Open the virtual drive and read the filename. The Retrode names the file from the cartridge's internal header — a clean SNES read yields something like SUPERMET.SFC. Rationale: a sensible, human-readable name means the header parsed correctly; a filename full of garbage characters is a dirty-contact or bad-seat symptom, not something to copy and keep.
8. Copy the ROM off the drive to local storage. Drag it, or use rsync/cp. Rationale: never run an emulator directly against the Retrode's virtual drive — it is slow and re-reads the cart constantly; copy the file to real disk and work from there.
9. Verify the dump with a checksum. Hash the copied file and compare against a No-Intro reference. Rationale: a matching hash is proof of a perfect, known-good read; a mismatch tells you to clean the contacts and dump again before you trust the file.
10. Back up the SRAM save. Copy the .srm file the same way you copied the ROM. Rationale: the cartridge's save battery is decades old and dying; this is very likely your last clean chance to capture that save.
11. If you need to restore or move a save, enable writes. Set sramReadonly to 0 in RETRODE.CFG (see the saves section). Rationale: the Retrode write-protects saves by default so you cannot clobber a cartridge by accident; you opt in deliberately when you actually mean to write.
12. Eject or unmount before swapping cartridges. Rationale: hot-swapping a live cartridge can corrupt the on-cart save; the user guide explicitly advises ejecting first, and a dead save is not worth the ten seconds you saved.
13. Test the ROM in an emulator or frontend. Load it in RetroArch or drop it into your library. Rationale: the only real confirmation that a dump is good is watching the game boot and run; a checksum proves the bytes, a playthrough proves the experience.

Here is what a clean SNES dump looks like on the virtual drive — one ROM, one save, and the config file:

$ ls -l /Volumes/RETRODE
total 3080
-rwxr-xr-x  1 you  staff  3145728  1 Jan  2016  SUPERMET.SFC
-rwxr-xr-x  1 you  staff     8192  1 Jan  2016  SUPERMET.SRM
-rwxr-xr-x  1 you  staff      512  1 Jan  2016  RETRODE.CFG

Copying it off with rsync gives you a progress readout and, more importantly, a file on real storage you can hash and archive:

$ rsync -av --progress /Volumes/RETRODE/ ~/roms/dumped/
sending incremental file list
RETRODE.CFG
            512 100%    0.49MB/s    0:00:00 (xfr#1)
SUPERMET.SFC
      3,145,728 100%    1.98MB/s    0:00:01 (xfr#2)
SUPERMET.SRM
          8,192 100%    7.81MB/s    0:00:00 (xfr#3)

sent 3,155,102 bytes  received 73 bytes  2,103,450.00 bytes/sec
total size is 3,154,432  speedup is 1.00

Then verify. A single command turns “I think this dumped” into “this is a known-good copy”:

$ sha256sum ~/roms/dumped/SUPERMET.SFC
9a4d3e0b8c1f...  (64 hex characters)  SUPERMET.SFC
# Compare this hash against a No-Intro DAT entry.
# A match = a perfect, known-good dump.
# A mismatch = clean the contacts and dump again.

Backing Up Your Saves (SRAM)

Why saves are read-only by default

The Retrode exposes two kinds of data per cartridge: the ROM, which it will never let you write because ROM is read-only by physics and by name, and the SRAM save, which it can write but refuses to by default. That refusal is deliberate. The virtual drive presents your save as a small file — typically a .srm alongside the ROM — and if that file were writable by default, a stray drag, a misfired sync tool, or an over-eager backup daemon could overwrite a decades-old save with garbage. So the firmware ships with saves write-protected, and you flip the switch only when you mean it.

Enabling writes with sramReadonly 0

The control is a single line in RETRODE.CFG, a plain-text file that lives in the root of the Retrode's virtual drive. Set sramReadonly to 0, drop the file on the drive, and tap RESET so the firmware re-reads it. Now the save file is writable, and you can copy a .srm back onto the cartridge — to restore a backup, or to move a completed save from an emulator onto real hardware.

# 1. Create RETRODE.CFG in the root of the virtual drive:
sramReadonly 0

# 2. Tap RESET so the firmware re-reads the config (the LED blinks once).

# 3. The save is now writable. Restore a backup onto the cartridge:
$ cp ~/roms/dumped/SUPERMET.SRM /Volumes/RETRODE/SUPERMET.SRM

# 4. When finished, set sramReadonly back to 1 and RESET again.

When the firmware reads a new config the LED blinks to acknowledge it; that blink is your confirmation the setting took. Set sramReadonly back to 1 when you are done, unless you enjoy living with a loaded gun pointed at your save files.

The hot-swap trap that eats saves

The single most expensive mistake in this entire workflow is swapping cartridges while the Retrode is live. The official user guide is explicit that hot-swapping is “possible, but it can potentially damage on-cartridge savegames,” and recommends you eject or unplug first. The mechanism is unglamorous: pulling a cartridge mid-access can leave the save SRAM in a half-written state. The ROM you can always re-dump. The save you cannot. Treat every cartridge swap as a deliberate eject-then-insert, and treat RESET as the thing you press after the new cart is seated, never as a substitute for unmounting. The full sequence is documented in the primary-source Retrode user guide on the Internet Archive.

Co-Processor Cartridges: What Won't Dump Cleanly

How the Retrode sees a cartridge

The Retrode reads a cartridge the way a scanner reads a page: it walks the address lines and records whatever the ROM chip returns. That is a complete and faithful copy of the game's data. What it cannot do is capture the behaviour of an additional processor soldered onto the board — the co-processor or enhancement chips that some cartridges used to offload work the base console couldn't handle. When such a chip sits between the console and the ROM, remapping or gating access, a plain address-walk either can't reach the data cleanly or can't reproduce what the chip contributes at runtime. The dump is only as good as the bus the Retrode can see.

SA-1, S-DD1, and SVP: the refusals

Three families are the ones to remember, because they are the ones the official FAQ calls out as unsupported. SA-1, a fast companion CPU, sits behind games like Super Mario RPG, Kirby Super Star, and Kirby's Dream Land 3. S-DD1, a decompression chip, is in Star Ocean and Street Fighter Alpha 2. On the Sega side, the SVP (Sega Virtua Processor) powers Virtua Racing. Cartridges built around these chips will not dump cleanly on the Retrode — the mapping the chip imposes is not something a passive reader reproduces. If your target is one of these, this is not the tool for that particular cartridge, and no config setting changes that.

Super FX and DSP-1: the false alarms

Here is the distinction people get wrong, so commit it to memory: Super FX and DSP-1 games dump fine. Star Fox, Yoshi's Island, Pilotwings, Super Mario Kart — the Retrode reads the ROM without complaint, and the emulator supplies the chip's behaviour on playback. The FAQ lists Super FX and DSP-1 as supported precisely because the enhancement is handled emulator-side; only SA-1, S-DD1, and the SVP are the genuine no-gos. Do not lump Super FX in with the refusals. The failure mode of that confusion is skipping a dump that would have worked perfectly.

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

The three current adapters

Out of the box the Retrode 2 handles SNES/SFC and Mega Drive/Genesis. Everything else arrives through a plug-in adapter that seats into the SNES slot and re-routes the pins. Three are current, per the official adapters page: N64, Game Boy / Color / Advance (the “GBx” adapter), and Sega Master System. Each is sold separately — around €25 at DragonBox, $39.99 at Stone Age Gamer — and each has its own quirks worth knowing before you buy.

Voltages, seating, and save gotchas

The N64 adapter dumps ROMs and passes up to two controllers, but it wants 3.3V and should be connected before you plug the Retrode into USB; N64 cartridge save backup is still listed as pending, so plan to capture those saves by other means. The GBx adapter reads Game Boy, Game Boy Color, and Game Boy Advance ROMs, and backs up SRAM saves on GB/GBC titles; GBA save and flash support is pending. Mind the voltage difference — GB/GBC run at 5V, GBA at 3.3V. The Master System adapter reads ROMs, gained SMS SRAM reading in the 0.18 firmware line, and will often leave the header title blank because many SMS cartridges simply don't carry one.

The discontinued exotics and controller notes

Older, more exotic adapters existed and are effectively gone; the connectors became unobtainable and the line was discontinued. Do not go hunting for a mythical oddball adapter as if it were current stock — the official current set is N64, GBx, and SMS. Two controller footnotes that save frustration: the SNES mouse works only in the LEFT port, and the Sega 32X adapter works without its power supply for dumping — whereas the Super Game Boy adapter does not work, because it is a full console front-end rather than a simple cartridge pass-through.

Firmware, DFU, and the v0.22 Myth

The frozen firmware (and why that's fine)

The Retrode 2's firmware stopped moving in 2016 at 0.18c stable, with 0.18d beta 3 as the last experimental build. On most gadgets, “last updated 2016” is an obituary. Here it is a footnote, because the hardware it drives is fixed and the job it does — clocking bytes off a mask ROM — did not change. The 0.18 line's notable additions were improved size detection for N64 and GBA, a LUFA library refresh, a Master System plug-in bugfix, and, usefully, Master System SRAM reading. Config support arrived back at 0.17g. If your unit already does what you need, there is no reason to touch the firmware at all.

The v0.22 myth

Periodically a forum post or a search snippet claims that “Retrode firmware 0.22 added enhanced-chip cartridge support for SNES.” There is no version 0.22. It does not exist. The frozen line tops out at 0.18c stable / 0.18d beta 3, and no 0.22 build ever shipped to add SA-1 or S-DD1 support — those chips remain unsupported for the reasons in the co-processor section. If you see the claim, you are looking at a mangled memory or an invented changelog. Believe the documented history, not the myth, and do not go looking for a download that isn't there.

Flashing over DFU

If you do need to (re)flash — to move from a pre-0.17g build up to 0.18c, or to recover a unit — the AT90USB646 uses Atmel's DFU bootloader. Put the device into bootloader mode by holding the HWB button, tapping RESET, then releasing HWB. On Windows you can use Atmel's FLIP; on Linux or macOS, dfu-programmer is the clean command-line route. In bootloader mode the device enumerates with Atmel's well-documented DFU id, 03eb:2ff9 — seeing that is how you confirm it is listening.

# Enter DFU mode: hold HWB, tap RESET, release HWB.
# Confirm the bootloader is listening (Atmel DFU id):
$ lsusb | grep 03eb:2ff9
Bus 001 Device 009: ID 03eb:2ff9 Atmel Corp. at90usb DFU bootloader

# Erase, flash the frozen 0.18c build, then reset:
$ sudo dfu-programmer at90usb646 erase
$ sudo dfu-programmer at90usb646 flash Retrode_0.18c.hex
$ sudo dfu-programmer at90usb646 reset

Note the reassuring part: a device sitting in the DFU bootloader is not bricked, even if the main drive has vanished. It is waiting for a .hex. Flash one, reset, and it comes back.

Five Common Pitfalls (and Their Fixes)

Most Retrode grief traces to a handful of repeat offenders. Here are the ones worth internalising, grouped by where they bite.

Cable and mounting pitfalls

Pitfall 1 — the charge-only cable. A mini-USB cable that only carries power will light the Retrode's LED and mount nothing. It is the single most common “it's dead” report. Fix: use a known-good data cable, ideally the one in the box, straight into a rear USB port. Pitfall 2 — the starved hub. Cheap unpowered hubs and front-panel ports can under-deliver current, causing intermittent reads that look like a flaky cartridge. Fix: a rear motherboard port or a powered hub.

Dump-integrity pitfalls

Pitfall 3 — dirty contacts masquerading as a dead cart. Half-size dumps, garbled header filenames, and files that fail their checksum are usually oxide on the edge connector, not silicon failure. Fix: 99% isopropyl, a lint-free swab, reseat, tap RESET, re-dump. Pitfall 4 — trusting an unverified dump. A file that copied without error can still be a bad read. Fix: hash every dump and compare against No-Intro before you archive it; treat an unverified ROM as a draft, not a keeper.

Save-corruption pitfalls

Pitfall 5 — hot-swapping with saves you care about. Pulling a live cartridge to insert the next one can leave the SRAM half-written. Fix: eject or unmount first, every time. Pitfall 6 — leaving sramReadonly at 0. Once you have finished restoring a save, a still-writable virtual drive is a standing hazard. Fix: set sramReadonly back to 1 so a stray file operation can't overwrite a good save.

Troubleshooting Table

Read the LED before you read the forums

The Retrode's one LED is a surprisingly good diagnostic. It flickers on ROM and RAM access and gives a distinct blink when the firmware reads a new RETRODE.CFG. If you insert a cartridge, tap RESET, and see no activity at all, the problem is upstream of the cartridge — cable, port, or seating — and no amount of config editing will help. If it flickers but the drive is empty or the filename is garbage, the read is reaching the cart but not cleanly, which points at contacts.

Symptom, cause, fix

Work top to bottom; most real-world faults live in the first four rows.

When to blame the cartridge, not the Retrode

If a dump verifies clean against No-Intro for ten cartridges and fails only on one specific game, the Retrode is fine and that cartridge is either filthy, damaged, or carrying an unsupported co-processor. Clean it first. If it still fails and it is an SA-1, S-DD1, or SVP title, that is expected behaviour, not a fault — re-read the co-processor section and move on.

Advanced Tips: RETRODE.CFG in Anger

Forcing system, size, and mapper

RETRODE.CFG is where the device stops being plug-and-play and starts being a tool. When auto-detection guesses wrong — a Game Gear cartridge read as plain Master System, an odd board reporting the wrong size, a SNES mapper misidentified — you override it by hand. forceSystem pins the console (for example, GG for Game Gear; the 0.18d beta fixed a case where GG wasn't recognised automatically). forceSize nails the ROM size when detection under- or over-reads. forceMapper settles LoROM-versus-HiROM ambiguity on the SNES. Each is a scalpel; reach for them only when the automatic read is demonstrably wrong.

Checksums, extensions, and Sega quirks

Several smaller keys shape the output files. filenameChksum appends a checksum to the filename, handy if you are batch-dumping and want collision-proof names. detectionDelay adds settle time before a read, which can rescue a marginal contact. segaSram16bit handles the Mega Drive carts that store saves as 16-bit words. And the extension keys — snesRomExt, segaRomExt, sramExt — let you decide whether SNES dumps land as .SFC or .SMC, Sega as .BIN or .GEN, and saves as .SRM, so the files drop straight into your emulator's expected naming without a rename pass.

Scripting the dump

Once you are dumping in volume, the workflow deserves a script: copy whatever is mounted, hash it, and file it. A few lines of shell turn a per-cartridge chore into a one-command routine.

#!/bin/sh
# dump-cart.sh - copy whatever the Retrode mounted, hash it, archive it.
SRC="/Volumes/RETRODE"
DEST="$HOME/roms/dumped"
mkdir -p "$DEST"

for f in "$SRC"/*.SFC "$SRC"/*.BIN "$SRC"/*.SRM; do
  [ -e "$f" ] || continue
  name=$(basename "$f")
  cp -v "$f" "$DEST/$name"
  sha256sum "$DEST/$name"
done

Point that at the Retrode's mount path, run it after each RESET, and you get a copied, checksummed file every time — the difference between a pile of ROMs and an actual, auditable archive.

The Complete Working Config

The annotated RETRODE.CFG

Below is a complete config file annotated with every key discussed here. Treat it as illustrative of the format — the exact defaults and accepted values are documented by the project, and the official CFG documentation has moved around over the years (retrode.org now simply redirects to retrode.com). The key names are real; use this as a template and consult the current docs for edge cases.

# ============================================================
#  RETRODE.CFG - complete reference (illustrative of format)
#  Location: root of the Retrode's virtual drive.
#  Config support: firmware 0.17g and later (frozen at 0.18c).
#  Tap RESET after editing; the LED blinks when the file is read.
# ============================================================

# --- Saves --------------------------------------------------
sramReadonly     1      # 1 = protect saves (default); 0 = allow writes
segaSram16bit    0      # 1 = treat Mega Drive SRAM as 16-bit wide

# --- System and detection -----------------------------------
forceSystem      auto   # auto | SNES | MD | SMS | GG
forceSize        0      # 0 = auto-detect ROM size
forceMapper      auto   # auto | lorom | hirom  (SNES only)
detectionDelay   0      # extra settle time before reading a cart

# --- Filenames and extensions -------------------------------
filenameChksum   0      # 1 = append a checksum to each filename
snesRomExt       SFC    # SNES/SFC ROM extension (SFC or SMC)
segaRomExt       BIN    # Mega Drive/Genesis ROM extension (BIN or GEN)
sramExt          SRM    # save-file extension

A verification workflow

The config gets you clean files; a habit gets you a trustworthy archive. For every cartridge: dump, copy to local disk, hash with sha256sum, compare against No-Intro, and only then move the file into your library. Keep the .srm next to the ROM and dated, because the next time that cartridge's battery is this healthy is never. When a hash matches a known-good entry, you have done something a downloaded ROM can never offer — you have proof.

Where your ROMs go next

A verified dump is inert until something plays it. On a desktop or single-board computer, Batocera and RetroPie are the obvious frontends; both read your dumped SNES and Mega Drive files directly, and the libretro cores behind them are documented in detail. If you want your dumps running on cycle-accurate hardware rather than software emulation, a MiSTer FPGA board is the preservationist's endgame, and for N64 specifically the Analogue 3D plays original cartridges through an FPGA on a modern display. The point of dumping your own carts is that these files are yours, verified and first-generation — a different thing entirely from a handheld that arrived with someone else's library preinstalled.

Primary sources worth bookmarking: the official Retrode FAQ and DragonBox Retrode 3 page for current status; the full Retrode user guide on the Internet Archive for the primary documentation; Sanni's Cart Reader and the Retrode 3 OSCR repository on GitHub for the open-source software lineage; and Wikipedia's Retrode entry for neutral background. That set will outlast any forum thread.