Retrode 2026: Dump Carts + Saves in 13 Steps, 30 Min

There is a specific flavor of self-delusion that sets in around the fifteenth year of owning a game collection: the belief that the cartridges will last forever. They will not. The mask ROMs are fine — those little dies will outlive all of us — but the battery-backed SRAM holding your 1996 save file is a coin cell quietly draining toward zero, and the edge connector is oxidizing a little more every time you blow into the cartridge like a barbarian. The Retrode exists for the people who have made peace with this and decided to do something about it before the something is done to them.

It is not an emulator. Read that twice, because the entire internet will spend the next decade trying to convince you otherwise. The Retrode is a USB interface: a dumb, honest little box that exposes a Super Nintendo or Sega Genesis cartridge to your computer as though it were a USB flash drive, and the original controllers as though they were USB gamepads. You plug a cart into the top, a file appears in a folder, you copy it. That is the entire magic trick. What you then do with that file — load it into a Batocera build, feed it to a flashcart, or archive it against the eventual heat-death of your coin cells — is your business, and, as the manufacturer is careful to note, your legal responsibility.

This is the long version of the workflow. If you want the fast, no-philosophy walkthrough, we keep a 13-step SNES-and-Genesis dump that gets you to a clean ROM in half an hour. What follows here is everything wrapped around it: the two hardware generations, the firmware that has not been meaningfully touched since 2016 and does not need to be, the co-processor carts that will quietly betray you, the plug-in adapters, and the complete configuration file at the very end that ninety percent of owners never open.

Why Dump Your Own Carts

Before the tools, the case for the exercise — because if you are not clear on why you are doing this, you will do it badly and blame the hardware.

The coin cell is already dying

Every Super Nintendo or Genesis cartridge that saves your progress does so on a small slab of static RAM kept alive by a CR2032-class coin cell soldered to the board. These batteries were installed between roughly 1989 and 1998. Lithium coin cells have a shelf life; the ones still holding a charge in 2026 are living on borrowed voltage. When the cell dies, the save vanishes — not corrupted, not recoverable, simply gone the instant you power down. The mask ROM holding the game itself is effectively immortal, but the thing that remembers you beat Phantoon is not. Dumping the ROM preserves the game; copying the .srm preserves the twenty-year-old save file, which is the part that is actually irreplaceable. Institutions treat this as preservation work, not hobbyism — the University of Maryland's MITH lab has documented dumping SNES cartridges precisely because the physical media is decaying on a clock nobody can reset.

Not an emulator — say it again

The Retrode's own FAQ states the point flatly: it is not an emulator, it is a USB interface for vintage cartridges and controllers. It exposes the cartridge as a virtual file and the controllers as USB HID devices. Nothing is simulated, interpreted, or approximated. When you copy the file off the virtual drive, you are copying the literal contents of the silicon, byte for byte, read straight off the address and data lines. Wikipedia describes it in the same unglamorous terms — a USB adapter for legacy video games that creates a copy of a cartridge's content. This matters practically: the quality of your dump is a function of the physical connection, not of any software cleverness. A clean contact gives a perfect read. A dirty one gives garbage, and no setting will fix that.

The legal grey zone, stated plainly

The Machine does not dispense legal advice, but it can read a statute. In the United States, backing up a cartridge you physically own is format-shifting, and it lives in a grey zone shaped by DMCA §1201's anti-circumvention rules and the periodic archival exemptions the Library of Congress grants and re-grants. It is meaningfully cleaner than downloading a stranger's ROM off a link aggregator: there is no distribution, no acquisition of a copy you do not own, and a defensible preservation rationale. It is not, however, blessed. The manufacturer's position is the honest one — the device lets you dump ROMs from your own carts, and it is explicitly your responsibility not to upload or redistribute them. Dump your shelf. Do not become a supplier. That distinction is the entire difference between an archivist and a defendant.

Retrode 2 vs. Retrode 3

There are two Retrodes in the wild in 2026, and only one of them is a product you can put in a cart. Getting this straight saves you from waiting months for hardware that is not finished, or buying hardware that already is.

The Retrode 2: what actually ships today

The Retrode 2 is the shipping unit and the subject of this tutorial. It runs about $99.99 at Stone Age Gamer in the US, or €64.90 direct from DragonBox in Europe, with the manufacturer's own suggested retail hovering around EUR 65 / USD 85. The box is spartan: the unit, a USB cable, an instruction sheet. It presents to your computer as a composite USB device — a mass-storage endpoint for the cartridge plus one or two USB HID gamepads for the controller ports — and needs no drivers on Linux, macOS, or Windows. The top wide slot takes SNES/Super Famicom carts; the shorter front slot takes Genesis/Mega Drive; four controller ports (two SNES, two Sega) sit alongside. Its lineage is a small saga: conceived in 2009 by Matthias Hullin on the OpenPandora forums, sold by Retrode UG in Germany until that entity wound down in the summer of 2013, revived as the Retrode 2 under OpenPandora GmbH in March 2015, and today carried by DragonBox. Its firmware has been frozen for a decade, which is a feature, not neglect — more on that below.

The Retrode 3: finished hardware, unfinished software

The Retrode 3 is the successor, and as of mid-2026 it is not for sale. DragonBox's own Retrode 3 page is blunt about the status: the hardware is finished and the team is still working on the software. The stated target is availability by the end of the year, at a price still undecided but aimed under €100 — you cannot order it, only sign up to be notified. Architecturally it is a different animal: a full Linux SoC running Debian with built-in Wi-Fi, presenting itself over USB as an Ethernet device so you drive the whole thing from a web browser with, again, no drivers. Worth flagging honestly — the marketing copy contradicts itself on the exact chip, describing a MIPS processor in one breath and an ARM processor in another, so treat the CPU as an unsettled detail rather than a spec. It adds an NES slot to the SNES and Mega Drive ones, reads ROM and SRAM, and — the genuinely new trick — writes flash carts (MegaDrive DragonDrive works today; SNES and Lynx flashing are promised at launch). It is built atop Sanni's open Cart Reader project, and the whole stack is open — the software is GPLv3, the hardware CC BY 4.0 — with the OS image published at DragonBox-Shop's GitHub. Because the OS lives on a reflashable image, DragonBox calls it practically unbrickable.

Which one to buy in 2026

If you have SNES and Genesis carts and you want to dump them this month, buy the Retrode 2. It is done, it is cheap, and this guide is written for it. If you specifically need the NES slot, want to write flash carts, or find the browser-based, driverless workflow appealing enough to wait for, put your email on the Retrode 3 notify list and be patient — end-of-year targets in this hobby have a way of becoming next-year realities. There is no shame in owning both eventually; there is real frustration in waiting for a shipping date that does not yet exist while your coin cells keep discharging.

Prerequisites

The Retrode asks for very little, which is exactly why people skip the little it asks for and then wonder why their dump is half the right size. Assemble this first.

Hardware you need

A Retrode 2 and its bundled USB cable — use that cable, not the mystery one from your drawer, because the unit is bus-powered and cheap cables sag under load. A rear, motherboard-mounted USB 2.0 port; front-panel ports and unpowered hubs are the number-one cause of phantom detection failures. Isopropyl alcohol at 90% or higher and a stack of lint-free swabs, because you will be cleaning edge connectors and you do not want residue. The cartridges themselves, obviously. Optionally: the original controllers if you plan to actually play through the dumped ROM to test it, and any plug-in adapters (N64, Game Boy, Master System) if your collection runs past the two native systems. That is the whole bill of materials. There is no power brick, no external drive, no dongle.

Software and versions

On the host side you need almost nothing, and that is the point. Any current Linux distribution, macOS, or Windows 10/11 will mount the Retrode with zero driver installation. What you may want on top: a ROM manager such as clrmamepro or RomVault plus a current No-Intro DAT for verifying dumps against the preservation community's reference checksums; a plain text editor for the eventual RETRODE.CFG edits; and, only if you intend to touch firmware, either dfu-programmer on Linux/macOS or Microchip/Atmel FLIP 3.4.7 on Windows. None of these are required to get a working dump — they are required to get a verified dump and a maintainable unit, which is a different and better goal.

There are no drivers (and the one exception)

The Retrode 2 enumerates as standard USB mass storage and standard USB HID. Your OS already ships the class drivers for both. The single exception is firmware flashing: the DFU bootloader needs a low-level USB shim — libusb or the Jungo driver FLIP installs on Windows, or a Zadig binding if Windows is being stubborn. You will not touch that unless you are deliberately reflashing. Confirm a healthy enumeration before you trust anything:

# Confirm the Retrode enumerated as a disk AND a HID gamepad (Linux)
lsusb | grep -i retrode
dmesg | tail -n 20              # look for: USB Mass Storage Device
lsblk -o NAME,LABEL,SIZE,MOUNTPOINT | grep -i RETRODE

# Expected: a small removable volume labelled RETRODE, plus one or two
# /dev/input/js* nodes, one per populated controller port.

The 13-Step Dump

This is the core procedure for a standard SNES or Genesis cartridge. Every step has a reason attached; the reasons are where the failures hide. Budget thirty minutes the first time, ten once it is muscle memory.

1. Check your firmware — or deliberately leave it alone. The Retrode 2 line is frozen at 0.18c stable (0.18d beta 3 for the adventurous). If your unit is from 2015 or later it already ships current, and you do nothing. Rationale: every detection behavior below assumes 0.18-era firmware; a genuinely ancient unit is the only case where flashing first is worth the risk.
2. Power down and inspect the cartridge edge. Look at the gold contacts under a light. Rationale: the Retrode reads exactly and only what those pins touch — visible corrosion or grime becomes bit errors in your file, and no software setting undoes that.
3. Clean the contacts. A swab dampened with 90%+ isopropyl along the edge connector, then let it dry completely. Rationale: oxidation causes intermittent contact, which produces non-deterministic dumps — the single most common reason two reads of the same cart disagree.
4. Identify the correct slot. Top wide slot for SNES/SFC, front short slot for Genesis/Mega Drive. Rationale: the connectors are physically keyed for different pinouts; forcing a cart into the wrong one bends pins and accomplishes nothing.
5. Insert the cartridge fully and squarely. Firm, even pressure until it seats. Rationale: a partially seated cart mounts as an empty or half-sized volume, which people misread as a dead game.
6. Connect controllers and adapters before the USB cable. If you want the gamepads or a plug-in adapter, attach them first. Rationale: the Retrode enumerates its HID endpoints at the moment of USB connection; anything added afterward may simply not register until you replug.
7. Plug the Retrode into a rear USB 2.0 port using the bundled cable. Straight into the machine, not through a hub. Rationale: the unit is bus-powered, and under-current from a weak port or long cheap cable causes dropouts mid-read.
8. Wait for the RETRODE volume to mount. A removable drive labelled RETRODE appears; no driver dialog should interrupt you. Rationale: if nothing mounts, stop here and troubleshoot — proceeding blind wastes the next five steps.
9. Open the volume and read the file list. You will see a ROM file, a save file, and the config. Rationale: the filenames are derived from the cartridge's internal header, so a garbled name is an early warning of a bad read or an exotic mapper the firmware guessed wrong.
10. Copy the ROM to your drive. Drag it out, or copy it on the command line, and let it finish — the activity LED lights during ROM access. Rationale: you are reading a slow mask ROM over USB 2.0; interrupting the copy truncates the file.
11. Copy the save file too, while the cart is in. Grab the .srm in the same session. Rationale: the coin cell is finite and you are already here — there is no reason to make a second trip for the save.
12. Verify the dump. Read the cart a second time and compare checksums, or match against a No-Intro DAT in a ROM manager. Rationale: a clean silicon read is deterministic; if two dumps disagree, the cart contacts are dirty, not the game.
13. Eject the volume, then remove the cartridge. Unmount in the OS first, always. Rationale: yanking a cart mid-write is the classic way to corrupt an on-cart save. To dump the next cart, insert it and press the Retrode's RESET button to remount.

What a healthy mount looks like — this is your expected output, roughly, for a 24-Mbit cart like Super Metroid:

$ ls -la /run/media/$USER/RETRODE     # macOS: /Volumes/RETRODE
Super Metroid.sfc      3145728   # 3 MB = 24 Mbit mask ROM
Super Metroid.srm         8192   # 8 KB battery-backed save
RETRODE.CFG                512   # the on-volume config file

If the .sfc is the size you expect for that cart's Mbit rating and the name matches the game, you are done. If it is half the size, the firmware misread the ROM size or the cart is barely seated — jump to the troubleshooting table.

Backing Up Your Saves

The ROM is replaceable; someone, somewhere, has a clean dump of every retail SNES game ever pressed. Your save file is not. This section is the part that actually justifies owning the hardware.

SRAM is write-protected by default

Out of the box the Retrode treats on-cart SRAM as read-only, governed by the sramReadonly key in the config, which defaults to 1. This is deliberate and correct: it means you cannot accidentally overwrite or damage a save just by having the cart mounted. The save surfaces on the virtual volume as a .srm file alongside the ROM — 8 KB on a typical SNES cart, sometimes 2 KB or 32 KB depending on the board. As long as you are only reading, you are physically incapable of harming the original. Copy freely.

Copying the save off

Pull the .srm exactly the way you pulled the ROM — it is just another file on the volume. On the command line, the whole job is a glob:

# Read the save OFF the cart (safe; SRAM is read-only by default)
VOL=/run/media/$USER/RETRODE
cp $VOL/*.srm ~/saves/

# To WRITE a save back, first set  sramReadonly 0  in RETRODE.CFG,
# remount, copy the .srm ONTO the volume, and wait for the LED to stop
# blinking before you eject. Hot-swapping mid-write corrupts saves.

Store that .srm somewhere with a backup. It is a 8-kilobyte file that represents a decade-old afternoon you are never getting back if the battery quits.

Writing a save back — and the hot-swap trap

The Retrode can also write a save onto a cart, which is how you restore a backup after a battery replacement, or move a save between two copies of the same game. To do it you must first flip sramReadonly to 0 in the config, remount, then copy your .srm onto the volume and — critically — wait for the activity LED to stop blinking before you eject. The blink is the write in progress. The user guide is explicit about the danger here: hot-swapping is 'possible, but it can potentially damage on-cartridge savegames,' and it advises you to eject or unplug the Retrode before changing carts. Treat that as gospel. The one operation that can destroy a save that survived thirty years is you pulling the cart while the LED is still blinking.

Co-Processor Cartridges

Here is where the honest limits live. Some Super Nintendo and Sega carts contain a chip that does more than store data, and the Retrode's relationship with those chips ranges from 'fine' to 'physically impossible.' Knowing which is which before you dump saves you a confused evening.

What the pins can and can't see

The Retrode reads the cartridge's ROM and SRAM by driving the address bus and latching the data bus. That is all it does. If a game's behavior depends on an on-cart coprocessor that computes results at runtime — not merely stores extra data — then dumping the ROM captures the program but not the chip. The ROM copies fine; it just will not run correctly in an emulator unless that emulator independently implements the coprocessor. The chip stays on the cart, where it was born. This is not a defect in the Retrode; it is the difference between reading memory and cloning silicon.

The carts that fail: SA-1, S-DD1, SVP

Three families to watch. SA-1 carts — Super Mario RPG, Kirby Super Star, Kirby's Dream Land 3 — carry an accelerator the Retrode cannot reproduce. S-DD1 carts — Star Ocean, Street Fighter Alpha 2 — use a hardware decompression chip; the compressed ROM dumps but is useless without the decompressor. On the Sega side, the SVP (Sega Virtua Processor) in Virtua Racing is a DSP the Retrode has no path to. In every case the file copies without error and then fails to boot or misbehaves in software. That is expected. If you own these games and need working ROMs, you want a full-featured flashcart or a dedicated dumper that handles the coprocessor, not the Retrode.

The carts that are fine: Super FX and DSP-1

Do not lump every enhancement chip into the failure bucket — a common mistake. Super FX games (Star Fox, Yoshi's Island, Doom) and DSP-1 games (Super Mario Kart, Pilotwings) dump correctly and run correctly, because modern emulators implement those chips natively; the Retrode only needs to hand over the ROM, which it does. The FAQ confirms this split directly. The rule of thumb: if the coprocessor's logic is reproduced in your emulator, the Retrode's plain ROM dump is enough. If the logic only exists on the cart, it is not. Super FX and DSP-1 are in the first camp; SA-1, S-DD1, and SVP are in the second.

Plug-In Adapters

The Retrode's expansion port turns it from a two-system dumper into a small archive rig. The official current lineup is three adapters, sold separately (about $39.99 each at Stone Age Gamer, or €25 at DragonBox), documented on the plug-in adapters page.

N64, Game Boy, and Master System

The N64 adapter dumps cartridge ROM cleanly; its save support (the various N64 EEPROM and SRAM formats) is listed as firmware-pending, so treat it as a ROM dumper only and back up N64 saves with a dedicated tool. The Game Boy adapter covers Game Boy, Game Boy Color, and Game Boy Advance ROMs, plus GB/GBC SRAM saves; GBA save and flash handling is still under development. The Master System adapter reads SMS ROMs, with SRAM support pending and a cosmetic quirk that some carts expose no standard title in the header, so the auto-generated filename comes out blank. Everything beyond these three — the exotic connectors of years past — is discontinued because the physical connectors became unobtainable, so ignore any listing that promises otherwise.

Voltage and the order of operations

Adapters are voltage-specific for a reason: a GB/GBC cart runs at 5V, a GBA cart at 3.3V, the N64 adapter at 3.3V. The adapter handles the level; your job is not to improvise. The procedural rule that trips people: connect the adapter (and any controllers) to the Retrode before you connect the Retrode's USB cable to the computer. The unit reads its configuration at power-up. Hot-attaching an adapter to a live Retrode frequently results in it not being recognized until you replug. And one lore detail that costs people an hour: the SNES mouse only works in the LEFT controller port. The right port will not see it. This is by design, not a fault.

The 32X adapter works; Super Game Boy doesn't

Two edge cases worth memorizing because they look similar and behave oppositely. A Sega 32X adapter — used without its power supply — is confirmed to work for dumping. A Super Game Boy adapter does not work, because the Super Game Boy is effectively a complete console-in-a-cart rather than a passive passthrough, and the Retrode has no way to drive it. If you are trying to dump a Game Boy cart, use the dedicated Game Boy plug-in adapter, not a Super Game Boy in the SNES slot. The distinction is passive adapter versus active console; the Retrode speaks to the former and is deaf to the latter.

Firmware and Flashing

Most owners will never flash their Retrode, and most owners are correct not to. But you should understand the mechanism, both to fix a genuinely broken unit and to inoculate yourself against the recurring myth that there is newer firmware you are missing.

Frozen at 0.18, and that's the point

The Retrode 2 firmware line ends at 0.18c stable, with 0.18d beta 3 as the last testing build, both dating to around 2016. It is built on Dean Camera's LUFA USB stack, and configuration-file support has existed since 0.17g. This is a finished product doing a finished job. Periodically a search result or forum post will claim a 'version 0.22' that 'added enhanced chip cart support for SNES' — this is false. No 0.22 exists; the real line stops at 0.18. Treat any such claim as folklore. The contrast with the emulation ecosystem downstream is instructive: while the thing that reads the silicon has sat unchanged for a decade, the software that runs the dumps churns constantly — RetroBat's changelog alone logs builds like Dolphin 2606 and DuckStation 0.1.11295.0 dated 10 May 2026. The dumper is done. The emulators never are. Both facts are correct and neither is a problem.

Entering DFU mode

The Retrode's microcontroller is an Atmel AVR AT90USB646, and it flashes over the standard AVR DFU bootloader. To enter it: hold the HWB button (button 7 on the board), tap and release the RESET button (button 8), then release HWB. The unit re-enumerates as an Atmel DFU device with the well-documented bootloader ID 03eb:2ff9 — seeing that ID is your confirmation you are in the bootloader and safe to write. If you do not see it, you are not in DFU mode, and every flash command will fail with 'no device present.' Do the button dance again.

Flashing: dfu-programmer or FLIP

On Linux or macOS the toolchain is dfu-programmer, which speaks AT90USB646 natively:

# Enter DFU: hold HWB (button 7), tap RESET (button 8), release HWB.
lsusb | grep 03eb:2ff9         # Atmel DFU bootloader, AT90USB646

sudo dfu-programmer at90usb646 erase
sudo dfu-programmer at90usb646 flash retrode-0.18c.hex
sudo dfu-programmer at90usb646 reset

On Windows the equivalent is Microchip/Atmel FLIP, which wraps the same operation in a GUI and installs the USB shim it needs on first run:

:: Windows: Microchip/Atmel FLIP 3.4.7
:: 1. Enter DFU (HWB + RESET), install the libusb/Jungo driver FLIP offers.
:: 2. Device  > Select     > AT90USB646
:: 3. File    > Load HEX   > retrode-0.18c.hex
:: 4. Tick Erase + Program + Verify, then Run.
::    No libusb device visible? Bind it with Zadig, then retry.

Either way: erase, flash the .hex, verify, reset. The unit reboots into normal mass-storage mode and you are back in business.

Common Pitfalls

The Retrode is simple enough that when it fails, it fails in a small number of predictable ways. Here are the six that account for nearly every support thread, grouped by where they bite.

Detection and mounting

• Nothing mounts at all. Almost always the USB path, not the Retrode. Front-panel ports, unpowered hubs, and tired cables starve the bus-powered unit. Fix: bundled cable, straight into a rear USB 2.0 port. If it mounts there, your case's front USB is the culprit, not the hardware.
• The volume mounts but is empty. The cartridge is not making contact. Fix: eject, reseat the cart firmly and squarely, clean the edge connector with 90%+ IPA, reinsert, and press RESET to remount. An empty RETRODE volume is a contact problem nine times in ten.

Dump integrity

• The dumped ROM is half the expected size. The firmware misjudged the ROM size, or the cart is marginally seated. Fix: reseat and redump first; if it persists, set forceSize to the correct Mbit value in RETRODE.CFG rather than leaving auto-detect to guess wrong.
• Two dumps of the same cart have different checksums. Intermittent contact during the read — the read is not deterministic because the connection is not stable. Fix: clean contacts again, dump on a solid surface without jostling the unit, and compare once more. A stable read of the same silicon is always bit-identical.

Saves and swapping

• A save will not copy back onto the cart. sramReadonly is still 1, protecting the SRAM. Fix: set it to 0, remount, copy the .srm, and let the LED stop blinking before ejecting.
• A save got corrupted after swapping carts. You hot-swapped or pulled a cart mid-write. Fix: there is no fix after the fact — this is why you eject first and never change carts while the LED blinks. Prevention is the only cure.

Troubleshooting Table

When something misbehaves, work symptom-first. This table covers the failures that are not obvious from the pitfalls above.

Reading the symptoms

Match your observed behavior in the left column, confirm the likely cause, apply the fix. Most entries resolve to either a physical-contact issue or a configuration/firmware-mode issue — those are the two axes the Retrode fails along.

When it's the cartridge, not the Retrode

Before you blame the hardware, run a control experiment: dump a cartridge you know reads cleanly. If that one works and your problem cart does not, the fault is the cart — dirty contacts, a dead save battery, or an unsupported coprocessor. The Retrode is a fixed variable; the carts are thirty years old and heterogeneous. A blank save on a game whose battery visibly corroded is not a Retrode failure, it is a physics failure that happened years before you plugged anything in.

When to just reflash

If a unit that previously worked starts behaving erratically across multiple known-good carts — inconsistent mounts, garbled filenames on games that used to name correctly — and the USB path is confirmed clean, a reflash of 0.18c is the reset button. It is rarely necessary. But because the AT90USB646 DFU process is safe and idempotent, re-writing the stock firmware costs you two minutes and rules out corrupted flash as a cause. Do it only after you have exhausted contacts and cabling, which are far likelier culprits.

Advanced Tips

Once the basic dump is routine, the Retrode rewards a little scripting and a little rigor. This is also where the Retrode 3's very different workflow becomes worth previewing.

Scripting bulk archival

If you are digitizing a whole shelf, the bottleneck is human — insert, press RESET, copy, eject, repeat. You can shave the copy step down to a keypress. This loop waits for you to swap and RESET a cart, then pulls every ROM and save off the volume in one shot:

#!/usr/bin/env bash
# Batch-archive carts. Insert cart, press the Retrode RESET, then Enter.
DEST=$HOME/roms/incoming
VOL=/run/media/$USER/RETRODE
mkdir -p $DEST
while read -rp 'Insert cart, press RESET, Enter (Ctrl-C quits) '; do
  rsync -a $VOL/*.sfc $VOL/*.bin $VOL/*.srm $DEST/ 2>/dev/null
  echo Copied. Eject before you swap the cart.
done

It is deliberately dumb: no filename cleverness, no parallelism, just a reliable copy-per-cart with a prompt that reminds you to eject. Reliability beats elegance when the input is irreplaceable silicon.

Verifying against No-Intro

A dump you have not verified is a dump you do not trust. The preservation community maintains reference checksums — the No-Intro database — for essentially every retail cart. Match your dump against them and you have proof your read was perfect:

# A clean silicon read is deterministic: dump twice, compare.
sha1sum 'Super Metroid.sfc' 'Super Metroid.copy.sfc'

# Or match CRC32/SHA-1 against a No-Intro DAT in a ROM manager
# (clrmamepro, RomVault). A match = bit-identical to the reference
# dump. A mismatch = dirty contacts, not a bad cartridge.

A matching hash means your read is byte-identical to the community reference — the gold standard. A mismatch, on a standard cart, is almost never a unique variant; it is contamination on the edge connector. Clean and redump. For where those verified files ultimately live and play, the same logic that governs a dumped cart governs a curated handheld library — the kind we picked apart in the Miyoo Mini Plus game-list breakdown, or a RetroPie build on a Pi. Dumping your own is the only entry in that chain with a clean provenance.

A preview of Retrode 3's browser workflow

The Retrode 3 discards the mass-storage model entirely. Instead of mounting a virtual drive, it presents as a USB-Ethernet device and serves a local web page; you dump carts, back up SRAM, and — new for this generation — write flash carts from a browser tab, no drivers and no host software beyond the browser you already have. Because the Debian OS lives on a reflashable image, a botched update is a reflash away from fixed, which is what DragonBox means by practically unbrickable. It is the same philosophy as the Retrode 2 — expose the cartridge honestly, emulate nothing — rebuilt on a Linux SoC with a network stack. It is not shipping yet, but it is the direction the line is going, and it pairs naturally with playback on dedicated FPGA hardware like the Analogue 3D for people who want original silicon on both the dumping and the playing end.

The Complete RETRODE.CFG

The configuration file is the Retrode's one concession to power users, and most owners run a blank one forever. Here is the whole surface area, so when you do need it, you are editing from knowledge rather than superstition.

Where RETRODE.CFG lives and how it loads

The file sits in the root of the RETRODE volume, as plain text. On mount, the firmware reads it; the activity LED blinks once when the config is parsed and written. An empty file — or one with only comments — means full auto-detection, which is the correct setting for the overwhelming majority of standard carts. You only reach for the keys when auto-detection guesses wrong on an oddball board, or when you deliberately want to change behavior like unlocking SRAM writes. Configuration support has existed since firmware 0.17g, so any current unit honors it.

Every key, annotated

The documented keys, briefly: sramReadonly gates save writing (1 protects, 0 unlocks). forceSystem overrides the header-based system guess (auto, or an explicit SNES/GENESIS/GG/SMS/N64). forceSize pins ROM size in Mbit when auto-size misreads. forceMapper handles headerless or unusual SNES boards (LOROM/HIROM). detectionDelay adds a settle time before reading a freshly inserted cart. filenameChksum appends a checksum to the dumped filename. segaSram16bit handles the handful of Mega Drive carts with 16-bit-wide saves. And sramExt, snesRomExt, and segaRomExt control the file extensions for saves and each system's ROM dumps. Because the official documentation for the CFG format has drifted offline over the years, treat the file below as illustrative-of-format — the key names are real and current, but always cross-check values against the primary user guide before overriding auto-detection.

The complete file

A fully commented reference. Copy it to the volume's root, uncomment only what you actually need, and leave the rest to auto-detect:

; RETRODE.CFG — place in the root of the RETRODE volume.
; A blank or comment-only file = full auto-detection (recommended).
; Every line below shows the DEFAULT unless noted. Firmware 0.18c / 0.18d-beta3;
; config support since 0.17g. Key NAMES are real and current; VALUES here are
; illustrative-of-format — cross-check the official user guide before overriding.

sramReadonly    1        ; 1 = protect saves (default). 0 = allow writing .srm back.
forceSystem     auto     ; auto | SNES | GENESIS | GG | SMS | N64 — override header guess
forceSize       0        ; 0 = auto ROM size. Set in Mbit only if auto-size misreads.
forceMapper     auto     ; auto | LOROM | HIROM — for headerless / oddball SNES boards
detectionDelay  0        ; ms to settle before reading a freshly inserted cart
filenameChksum  0        ; 1 = append a checksum to the dumped filename
segaSram16bit   0        ; 1 = treat a Sega save as 16-bit wide (a few MD carts need this)
sramExt         srm      ; extension used for the virtual save file
snesRomExt      sfc      ; extension for SNES/SFC dumps (sfc | smc)
segaRomExt      bin      ; extension for Mega Drive/Genesis dumps (bin | gen | md)

That is the entire device, end to end: a box that reads silicon honestly, a firmware that finished its job a decade ago, and a config file most people are right to ignore. Dump your shelf, verify your dumps, back up the saves the batteries are trying to take with them — and keep the files to yourself. For the fast-path version of the dump itself, the 13-step SNES-and-Genesis walkthrough is the companion to this one. The primary sources — the full Retrode user guide, the official FAQ, and the libretro documentation for whatever you run the ROMs in — are where you go when this article ends.