Retrode 2 2026: Dump Carts & Saves in 12 Steps, 25 Min

Type retrode into a search engine in 2026 and the algorithm assumes you fat-fingered retrograde. It hands you Mercury, it hands you Uranus, it hands you a horoscope and a shopping list of healing crystals. That is not what this is. The Retrode is a small black box with cartridge slots that turns your original SNES and Sega Genesis carts into files your computer can read, over plain USB, with no drivers and no pilgrimage to a ROM site of questionable provenance. No planets are involved. No mood is being read.

It is also, in mid-2026, a faintly strange product to write a tutorial about, because nothing about it is new. The shipping model — the Retrode 2 — has run frozen firmware since roughly 2016. Its successor, the Retrode 3, has been “coming by the end of the year” for longer than some of the consoles it reads have been discontinued. And yet the thing works, it works the same way it worked a decade ago, and that inertness is the entire point. This is preservation hardware. You want it boring. A cartridge dumper that ships a breaking update every quarter is a cartridge dumper you cannot trust with the only copy of a save file your ten-year-old self wrote in 1996.

What follows is the full procedure: what to buy and for how much, how the device presents itself to your operating system, the twelve steps to pull a clean dump of a cartridge and its battery-backed save, the entire RETRODE.CFG configuration file key by key, how to reflash the microcontroller if you brick it, which cartridges it flatly refuses to read, and exactly where the Retrode 3 stands as of July 2026. Read the prerequisites before you spend a hundred dollars. Some carts it cannot dump, and it would be a shame to discover that the hard way with the one cart you actually cared about.

What the Retrode Is, and What 2026 Changed

Strip away the enthusiasm and the Retrode is a USB peripheral that reads the address and data lines of a game cartridge and exposes what it finds as a file. That is the whole trick. It does not emulate. It does not stream. It does not phone home. It reads silicon you already own and writes it to a folder.

A cartridge reader, not a ROM site

The distinction matters legally and practically. When you dump a cart you own with a Retrode, you produce a personal backup of software you paid for, sourced from the physical media in your hand. That is a categorically different act from downloading an anonymous file that some stranger uploaded, and the difference is the reason preservation institutions take the device seriously — the University of Maryland's digital-humanities group has written about using Retrode-style dumping for archival work. A dump you made yourself has a known provenance: this cart, this day, this checksum. If you would rather understand where the sprawling “complete” ROM sets that float around the internet actually come from, we picked that apart in our look at the Miyoo Mini Plus and its phantom game list, and the short version is: nobody can vouch for them, which is precisely why you dump your own.

Two devices wear the name in 2026

There are two Retrodes in play, and conflating them is the single most common error in every forum thread on the subject. The Retrode 2 is the product you can buy today. It is an Atmel AVR microcontroller in a plastic shell, driverless, with frozen firmware, and it does SNES and Genesis out of the box with optional adapters for other systems. The Retrode 3 is an in-development successor from DragonBox — a full Linux computer with a browser interface, built on Sanni's open-source Cart Reader, targeting late 2026 at under €100, and as of this writing it is a notify-me pre-registration and nothing more. When someone says “the Retrode does NES,” they mean the unreleased 3. The shipping 2 does not.

Where it came from

The lore, because The Machine keeps the lore straight: the Retrode was conceived in 2009 by Matthias Hullin, posted first to the OpenPandora handheld forums as a hobbyist project. It was commercialized through a small German entity, Retrode UG (haftungsbeschränkt), which ceased trading in the summer of 2013. The second revision — the Retrode 2 you buy now — came back to market through OpenPandora GmbH around March 2015 and today lives under the DragonBox banner. If a brief tells you the Retrode was invented in 2007 by a man named Peter Lück and originally sold as a Retrode 1 for $84.99, close the brief. None of that is true, and it recurs in AI-generated research blocks like a bad penny. The Wikipedia article on the Retrode has the dates and the microcontroller part number right, which is more than most secondary sources manage.

Prerequisites: Hardware and Software Versions

The Retrode's great virtue is how little it demands. There is no toolchain to install, no account to make, no companion app that will be abandoned in two years. But “little” is not “nothing,” and a couple of the requirements are the kind you only discover you were missing at the worst moment.

The hardware bill of materials

You need the Retrode 2 unit itself. In the United States, Stone Age Gamer lists it at $99.99; direct from DragonBox in Europe the base unit is €64.90. Plug-in adapters — for Nintendo 64, Game Boy, and Sega Master System — run $39.99 each at Stone Age Gamer or €25 each at DragonBox, with an all-three bundle around €65. You do not need any adapter to dump SNES and Genesis; those slots are built in. Confirm current pricing at the source before you buy — the Stone Age Gamer Retrode 2 listing is the US authority and DragonBox is the EU one. Beyond the unit you need a USB cable (a mini-B cable is in the box), a computer, and the cartridges you intend to dump. Optionally, a cotton swab and isopropyl alcohol for cleaning contacts, which you will want more often than you expect.

Software and firmware versions

On the host side there is genuinely nothing to install for a normal dump. The Retrode is a composite USB device that presents as mass storage and a couple of gamepads; Windows, macOS, and Linux all mount it with their built-in drivers, as do the old Pandora and Caanoo handhelds it was designed alongside. The pieces of software you might want are all optional: a checksum tool (sha1sum, md5sum, or clrmamepro against a No-Intro DAT) to verify dumps; an emulator or frontend such as RetroArch, Batocera, or RetroPie to actually play them; and, only if you intend to reflash firmware, Atmel FLIP on Windows or dfu-programmer on Linux/macOS. The firmware itself is frozen: the last builds are 0.18c (stable) and 0.18d beta 3, both from around 2016. There is no 0.22, there is no “Enhanced Cart Support” update, and any brief claiming otherwise is hallucinating a changelog. Your unit almost certainly already runs a 0.18-series build.

What the Retrode will not do

Set expectations before money changes hands. The Retrode 2 will not write a ROM back to a cartridge — ROM is Read-Only Memory, and the device treats that as scripture. It will not dump every cartridge: carts using the SA-1 co-processor (Super Mario RPG, Kirby Super Star, Kirby's Dream Land 3), the S-DD1 chip (Star Ocean, Street Fighter Alpha 2), or Sega's Virtua Processor (Virtua Racing) are unsupported and will produce garbage or nothing. It will not back up GBA saves or flash carts (listed as pending, indefinitely), and N64 and Master System save backup are likewise “pending” and have been for years. And it will not work with a Super Game Boy adapter, because that adapter is a whole console's worth of hardware the Retrode cannot drive. Know all of this now.

How the Composite USB Device Works

Understanding what the Retrode presents to your operating system is not academic. It explains every quirk in the dump procedure, every save-corruption warning, and half the troubleshooting table at the end.

Mass storage and gamepads at once

The Retrode enumerates as a composite USB device: one mass-storage endpoint plus a set of USB HID gamepads. The mass-storage half is why the cartridge shows up as a removable drive with no driver install — your OS already knows how to mount a USB stick, and the Retrode pretends to be one. The HID half is why the four controller ports (two SNES-style, two Sega-style) can be used as actual USB game controllers, which is a genuinely useful side effect: plug a real SNES pad into the Retrode and you have a driverless USB controller for your emulator. Do not overthink this dual identity; just know that when the drive mounts, the gamepads mount too.

The files on the virtual drive

When a cartridge is seated and the device is plugged in, the mounted volume — labeled RETRODE — contains a small, predictable set of files generated on the fly. For a SNES cart you get <game>.sfc (the ROM) and, if the cart has a save battery, <game>.srm (the SRAM). For a Sega cart it is <game>.bin and, again, <game>.srm. Alongside them sits RETRODE.CFG, the plain-text configuration file. The onboard LED lights during ROM and RAM access and blinks when the config file is written — a small but real feedback channel. Here is what a healthy mount looks like on Linux:

$ dmesg | tail -4
usb 1-2: new full-speed USB device number 7 using xhci_hcd
usb 1-2: Product: Retrode
usb-storage 1-2:1.0: USB Mass Storage device detected
sd 6:0:0:0: [sdb] Attached SCSI removable disk

$ ls -la /media/you/RETRODE
total 3072
-r--r--r-- 1 you you 3145728 Jul 17  2026 'Chrono Trigger.sfc'
-r--r--r-- 1 you you    8192 Jul 17  2026 'Chrono Trigger.srm'
-rw-rw-rw- 1 you you     512 Jul 17  2026 RETRODE.CFG

Note the permissions. The ROM and the save both come up read-only by default; only the config is writable. That is deliberate, and the next detail explains why.

Read-only by design

The Retrode's own FAQ answers the “can I write to the cart?” question with the driest line in the entire product's documentation: ROM is Read-Only Memory, hence: no. The ROM file is a live view of the cartridge, not a copy sitting in a buffer, which is why you must copy it off to real disk before doing anything with it. The save file is likewise write-protected by default so that a stray operating-system write — a thumbnail cache, a .DS_Store, an antivirus scan — cannot silently corrupt the battery-backed memory on a cart you may never be able to replace. You can lift that protection deliberately, which is the entire subject of the saves section below. The full Retrode user guide is archived on the Internet Archive and is the primary source for all of this; it is worth reading once, front to back, before you dump anything irreplaceable.

The 12-Step Dump: SNES and Genesis

Here is the core procedure, twelve steps, each with the reason it exists. Follow it in order. The whole thing takes about twenty-five minutes the first time and under ten once it is muscle memory. The rationale attached to each step is not padding — skipping a step because it “looks optional” is how you end up with a 2 MB dump of a 3 MB game.

1. Inspect and clean the cartridge contacts. Wipe the edge connector with a cotton swab dampened in isopropyl alcohol and let it dry fully. Rationale: thirty-year-old contacts oxidize, and a dirty contact produces a short read or a checksum that will never match a known-good DAT. Ninety percent of “my dump is wrong” reports are dirty pins.
2. Seat the cart in the correct slot, with the device unplugged. The lower, shorter slot is Genesis/Mega Drive; the upper, wider slot is SNES/Super Famicom. Rationale: inserting a cart into a live device risks arcing across the data lines and, on a save-equipped cart, risks the battery memory. Seat it fully and squarely before power.
3. Attach any plug-in adapter before you connect USB. If you are using the N64, Game Boy, or Master System adapter, mate it to the Retrode now. Rationale: the adapters are detected at enumeration; the N64 adapter in particular expects to be connected before the host sees the device, or it will not be recognized.
4. Plug the Retrode into a powered rear USB port. Prefer a port directly on the machine over a bus-powered hub. Rationale: reading a cartridge is a power-hungry operation, and an under-supplied hub is the second-most-common cause of truncated dumps after dirty contacts.
5. Wait for enumeration and confirm the mount. Watch for the RETRODE volume to appear and the LED to settle. Rationale: if the volume never mounts, stop here — every later step depends on it, and the fix is upstream (cable, port, seating), not in the file operations.
6. Open the volume and identify the ROM file and its reported size. Note the file name the Retrode derived from the cart header, and the size in bytes. Rationale: the size is your first sanity check. A cart you know is 24 Mbit (3 MB) that shows as 2 MB is telling you the read is incomplete before you have wasted time copying it.
7. Copy the ROM file to local disk. Drag <game>.sfc or <game>.bin into a working folder. Rationale: the file on the volume is a live view of the cartridge, not a stored image. Never emulate or edit off the live mount — copy first, always.
8. Copy the .srm save if the cart has one. If the game had a battery, grab the save now. Rationale: this is the file that cannot be re-created — the ROM is identical to every other copy of that game, but this save is uniquely yours, and the battery that holds it may be near death.
9. Copy RETRODE.CFG for your records. Keep a copy of the config as it shipped, then edit the working copy if you need to. Rationale: if a later config change misbehaves, you want the known-good original to restore.
10. Verify the dump against a known-good checksum. Hash the copied ROM and compare it to a No-Intro or Redump DAT. Rationale: a dump you have not verified is a dump you cannot trust. This is the step that separates archiving from hoarding. See the expected output below.
11. Eject and unmount before removing the cart. Use your OS's safe-eject, then unplug or press RESET before pulling the cartridge. Rationale: the user guide is explicit that hot-swapping “can potentially damage on-cartridge savegames,” and it advises you to eject or unplug first. To swap to another cart on the same session, seat the new one and press the RESET button to re-mount.
12. Rename and file the output per No-Intro convention, and store the original cart. Give the files their canonical names and archive them somewhere with a backup. Rationale: a verified dump with a nonsense filename in a folder you will lose is not preservation. Name it once, correctly, and it is findable forever.

Step 10 is the one people skip and regret. Here is what verification looks like in a shell:

$ cp '/media/you/RETRODE/Chrono Trigger.sfc' ~/dumps/
$ cd ~/dumps
$ sha1sum 'Chrono Trigger.sfc'
2d1f... (your 40-hex-digit hash)   Chrono Trigger.sfc

# Compare that hash to the matching entry in the No-Intro SNES DAT,
# either by eye or by loading the DAT into clrmamepro and scanning
# the folder. A match means byte-perfect. A mismatch means re-dump.

If the hash matches the DAT, you are done: that file is byte-identical to the reference dump and will run in anything. If it does not match, do not assume the DAT is wrong. Re-seat the cart, re-clean the contacts, move to a rear USB port, and dump again.

Backing Up and Restoring SRAM Saves

The ROM is fungible. The save is not. This section is the one that justifies owning a Retrode at all, because copying a ROM is something a hundred tools can do, but pulling the actual battery-backed memory off your cartridge — the file with your name entered in 1994 — is the thing only a hardware dumper can do.

Why saves are write-protected by default

As shown earlier, the .srm file mounts read-only. The Retrode's designers made that the default on purpose: the save file is a live window onto the SRAM chip on the cartridge, and any write your operating system performs to that file — even an accidental metadata write — goes straight onto the cart's battery memory. Read-only-by-default means you cannot corrupt a thirty-year-old save just by opening the folder. The user guide puts it plainly: the RAM files are “by default write-protected.” To back up a save you do not need to change anything — you can read a read-only file. You only lift the protection when you want to write a save back to the cart.

Flipping sramReadonly

Restoring a save to a cartridge — say, copying a save from one copy of a game onto another cart, or writing an edited save back — requires enabling SRAM writes in the config. The key is sramReadonly: set it to 0 and the .srm file becomes writable. Create or edit RETRODE.CFG at the root of the volume so it contains at minimum:

# RETRODE.CFG - allow writing saves back to the cartridge
# 0 = SRAM writable, 1 = SRAM read-only (default)
sramReadonly 0

Save the file, then press RESET (or re-plug) so the firmware re-reads the config — the LED blinks when the config is written. Now you can copy an .srm onto the volume and it will be written to the cart's SRAM. When you are finished, set sramReadonly back to 1. Leaving writes enabled permanently is asking for exactly the accidental corruption the default exists to prevent.

Battery warnings and the Sega quirk

Two cautions. First, on Sega carts the SRAM can be stored as either 8-bit or 16-bit, and if a restored Genesis save comes back scrambled, the segaSram16bit key exists to force the correct width — more on that in the config section. Second, and this bears repeating because the guide repeats it: do not hot-swap carts with SRAM writes enabled. Eject, unplug, or at minimum press RESET between carts. A save battery that has survived three decades deserves better than to be killed by a lazy swap. If the cart's battery is visibly corroded or the save reads as all-zeros or all-ones, the battery is likely dead and there is nothing on it left to rescue — the dump is capturing an empty chip, not a lost save.

RETRODE.CFG: Every Key, Annotated

The configuration file is where the Retrode stops being a toy and becomes a tool. It is a plain-text file at the root of the mounted volume, read at mount time. A caveat before the keys: the official configuration documentation on retrode.org now 302-redirects to the current retrode.com store page, so the canonical online reference is effectively gone. The key names below are confirmed from the archived guide and firmware notes; treat any full example file as illustrative of the format rather than a doc you can cite line-for-line.

Where it lives and how it loads

The file lives in the root of the RETRODE volume as RETRODE.CFG. The firmware reads it when the device mounts, so any change requires a RESET or re-plug to take effect. The onboard LED blinks when the config is written, which is your confirmation that the firmware accepted the file. Configuration support has existed since firmware 0.17g; if your unit is older than that, the file will simply be ignored, which is a decent reason to be on the frozen 0.18c build.

The forceSystem, forceSize, and forceMapper trio

Three keys exist for carts the auto-detection gets wrong. forceSystem overrides the detected console — useful for Game Gear cartridges through the Master System adapter, where the abbreviation is GG; the 0.18d beta 3 build specifically fixed a bug where forceSystem GG was not recognized. forceSize overrides the detected ROM size, for the rare cart whose header lies about its own capacity or a homebrew/reproduction that has no sensible header at all. forceMapper overrides the detected memory mapper, for SNES carts whose bank layout confuses the automatic logic. In normal use all three stay unset and detection is automatic; you reach for them only when a specific cart misbehaves in a specific, repeatable way.

The full annotated key set

Beyond that trio, the confirmed keys are: sramReadonly (0/1, covered above); filenameChksum, which appends a checksum to the generated filename so two similarly-named carts do not collide; detectionDelay, which lengthens the settle time before the firmware reads a cart, a real fix for flaky or slightly-oxidized connectors; segaSram16bit, the 8-bit/16-bit save-width toggle for Genesis; and the extension overrides sramExt, snesRomExt, and segaRomExt, which let you change the file suffixes the Retrode generates (for instance to .smc instead of .sfc, or .md instead of .bin, if your frontend is fussy about extensions). A representative slice:

# --- RETRODE.CFG (annotated excerpt) ---
sramReadonly 1       # 1 = protect saves (default); 0 = allow writes
filenameChksum 1     # append a checksum to output filenames
detectionDelay 0     # increase if carts read intermittently
segaSram16bit 0      # set 1 if Genesis saves come back scrambled
snesRomExt sfc       # SNES ROM extension (sfc / smc)
segaRomExt bin       # Sega ROM extension (bin / md / gen)
sramExt srm          # save-file extension

The complete, ready-to-drop file appears at the very end of this article.

Firmware 0.18 and DFU Flashing

You will almost never need this section. That is the good news. But if you buy a used unit on an ancient build, or if a botched flash leaves the device unresponsive, this is how you recover it — and because the microcontroller has a hardware DFU bootloader, the Retrode is very hard to permanently brick.

What the 0.18 line actually changed

The firmware is frozen, and the last two builds are 0.18c (stable) and 0.18d beta 3. For the record, since AI research blocks love to invent version history: the 0.18 series improved N64 and GBA ROM-size detection, updated the underlying LUFA USB library, fixed a Master System plug-in bug, and — the one genuinely new capability — added Master System SRAM reading. The 0.18d beta 3 build additionally fixed the forceSystem GG recognition bug mentioned earlier. There is no 0.22. There is no “SNES Enhanced Cart Support” release. The frozen line runs roughly 0.17d through 0.18d beta 3, and the Softpedia firmware mirror confirms 0.18c as the last stable. This stasis is a feature; it is the same reason we admire a platform like RetroPie sitting frozen at v4.8 while the Raspberry Pi marches on — a preservation tool that stops changing is a preservation tool you can rely on.

Entering DFU mode

The heart of the Retrode 2 is an Atmel AVR AT90USB646 microcontroller, and its USB firmware is built on Dean Camera's LUFA library. That chip has a factory DFU (Device Firmware Update) bootloader that cannot be overwritten by a bad application flash, which is why the device is nearly unbrickable. To enter it: hold the HWB button (button 7, the one the firmware otherwise uses for custom functions), press and release the RESET button (button 8), then release HWB. The device now enumerates as an Atmel DFU bootloader with the well-documented USB ID 03eb:2ff9 — not as the RETRODE mass-storage volume. If you see that ID, you are in DFU mode and ready to flash.

FLIP versus dfu-programmer

On Windows, Atmel's FLIP utility is the graphical path: select the AT90USB646, load the .hex, erase, program, verify. On Linux and macOS, dfu-programmer is the command-line equivalent, and it is the cleaner experience:

# Linux/macOS - reflash the frozen 0.18c firmware
# 1. Enter DFU: hold HWB, tap RESET, release HWB
$ lsusb | grep 03eb
Bus 001 Device 012: ID 03eb:2ff9 Atmel Corp. atmega/at90usb DFU bootloader

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

After the reset the device leaves DFU mode and comes back up as the normal Retrode volume. If erase complains that the chip is not blank on a first run, that is expected on a chip with existing firmware; the command handles it. Never unplug mid-flash — but even if you do, you re-enter DFU and start over, because the bootloader itself is untouchable.

Plug-In Adapters and Exotic Carts

The two built-in slots cover the two most-collected 16-bit libraries. Everything else the Retrode 2 does, it does through adapters — and the adapter situation is a mix of “works well” and “works with asterisks.”

The three current adapters

Three adapters remain in production. The N64 adapter dumps ROMs correctly; save backup is listed as “firmware support pending,” it runs at 3.3V, supports up to two controllers, and — critically — must be connected to the Retrode before you plug the Retrode into USB. The GBx adapter handles Game Boy, Game Boy Color, and Game Boy Advance ROMs; GB and GBC SRAM saves back up fine, but GBA SRAM and flash saves are pending; note the voltage split, 5V for GB/GBC and 3.3V for GBA. The Master System adapter dumps ROMs and, since firmware 0.18, reads SMS SRAM; be aware that many SMS carts have no title in their header, so the generated filename may be generic and need manual naming. The official Retrode FAQ is the authority on adapter status, and it is worth checking before you buy an adapter for a save-dependent library.

Controllers and the co-processor wall

The controller ports are more capable than they look, with two caveats worth memorizing. The SNES mouse works, but only in the left port. The Sega 32X adapter works when used without its power supply. And the Super Game Boy adapter does not work, because it is effectively a full console the Retrode cannot drive. Now the co-processor wall, the fact most people get backwards: cartridges with the Super FX chip (Star Fox, Yoshi's Island) and the DSP1 chip (Super Mario Kart, Pilotwings) dump perfectly — the Retrode reads the ROM and the emulator does the chip's math. What the Retrode cannot handle are SA-1 (Super Mario RPG, Kirby Super Star, Kirby's Dream Land 3), S-DD1 (Star Ocean, Street Fighter Alpha 2), and the Sega Virtua Processor (Virtua Racing). Do not lump Super FX in with the unsupported set; it is supported. This distinction is in the FAQ and it is the single most-repeated error in Retrode discussions.

The discontinued exotics

Over the years there were other adapters — more obscure connectors, and the occasional experiment — but most were discontinued because the connectors themselves became unobtainable. If a listing anywhere offers you a “Virtual Boy plug-in” or some similar oddity, treat it as a historical curiosity from the device's peak, not a current product. The supported, in-production set in 2026 is exactly three: N64, GBx, and SMS. Everything beyond that is either the built-in SNES/Genesis slots or a story about what the Retrode community once tried.

Loading Dumps in RetroArch and Batocera

A verified dump is a file like any other ROM, which means every emulator and frontend loads it with zero special handling. The only reason this section exists is to point out the two places where a Retrode dump behaves differently from a random download — which are, happily, both in the Retrode dump's favor.

Pointing a core at the file

In RetroArch, load the appropriate libretro core and hand it the file. For SNES that is Snes9x or bsnes; for Genesis, Genesis Plus GX. From the command line it is a one-liner; from the GUI it is Load Content, then pick the core:

# RetroArch: run a Retrode dump with the SNES core
$ retroarch -L cores/snes9x_libretro.so ~/dumps/'Chrono Trigger.sfc'

# Or add ~/dumps as a Content Directory in Settings and
# let the scanner match it against the RetroArch database.

The scanner uses the same No-Intro-derived hashes you verified against in step 10, so a correctly dumped, correctly named cart will match the database on the first pass and pull down its box art automatically. If you want the full walkthrough of picking and configuring cores, we covered that end-to-end in the guide to getting the right RetroArch core installed in 12 steps. The libretro documentation is the reference for per-core options.

Frontends: Batocera and RetroPie

On a dedicated emulation box, drop the dumps into the appropriate system folder and the frontend does the rest. Batocera and RetroPie both organize ROMs by system directory — snes/, megadrive/, gb/ — and both scrape metadata by hash. If you are building such a box, our Batocera 43.1 install walkthrough gets you from blank drive to running frontend, at which point your Retrode dumps simply belong in the right folders. The virtue of a self-dumped library here is that every hash matches on the first scrape, because you know exactly what each file is.

Which carts will not play

The co-processor wall from the adapters section applies at playback too, but inverted in your favor: because Super FX and DSP1 carts dump correctly, they play correctly in any competent core. The carts that will not play are the ones that never dumped in the first place — SA-1, S-DD1, and SVP titles. If a Super Mario RPG dump loads to a black screen, the problem is not your emulator or your core; it is that the Retrode could not read that cart, and no amount of core-switching will fix a bad dump. Verify the dump before you blame the emulator.

Five Pitfalls and How to Dodge Them

Every one of these has cost someone an afternoon, and most have cost someone a save file. They are ordered roughly by how often they bite.

• Emulating or editing off the live mount. The files on the RETRODE volume are live views of the cartridge, not stored copies. Point an emulator at the volume and you are hammering the cartridge's contacts continuously; edit a save there without protection and you write straight to the battery. Fix: copy every file to real disk first (step 7), then work from the copy. Always.
• Hot-swapping carts without ejecting. Pulling a cart while the volume is mounted — especially with SRAM writes enabled — can corrupt the save. The user guide says so in as many words. Fix: eject/unmount, or unplug, or at minimum press RESET before you touch the cartridge, and re-seat the next cart before pressing RESET again.
• Feeding it from an under-powered hub. Bus-powered hubs and long daisy-chains sag under the current a cartridge read demands, producing truncated dumps that look complete until the checksum fails. Fix: use a USB port directly on the machine, ideally a rear port on a desktop, and skip the hub entirely.
• Expecting SA-1 / S-DD1 / SVP carts to dump. Super Mario RPG, Kirby Super Star, Star Ocean, Virtua Racing — the Retrode 2 cannot read these, full stop. Fix: know your cart's chip before you try. If it is SA-1, S-DD1, or Sega Virtua Processor, the Retrode is the wrong tool and you need a Sanni Cart Reader or equivalent instead.
• Dirty contacts producing silent bad dumps. Oxidized pins yield a file that is the right size but the wrong bytes, so it fails verification for no obvious reason. Fix: clean the edge connector with isopropyl alcohol before every dump of an old cart, and increase detectionDelay in the config for a stubborn one.
• Trying to write a ROM back to a cart. It cannot be done on a Retrode 2; ROM is read-only in hardware. Fix: accept it. If you need to write flash carts, that is a Retrode 3 capability (MegaDrive today, SNES and Lynx at launch), covered below — not a thing the 2 will ever do.

Troubleshooting Table and Expected Output

Symptom-to-fix, in the order you should suspect causes. If the table does not resolve it, the expected-output block below shows what a healthy versus an unhealthy dump looks like at the byte level.

Expected output: good versus bad

The fastest diagnostic is the file size on the mount. A 24 Mbit SNES cart is 3,145,728 bytes; a 16 Mbit Genesis cart is 2,097,152. If the number is short, the read failed — stop and fix the cause before copying:

$ ls -la /media/you/RETRODE
# HEALTHY - full 3 MB read:
-r--r--r-- 1 you you 3145728 Jul 17  2026 'Super Metroid.sfc'

# BAD - short read, only 2 MB of a 3 MB game:
-r--r--r-- 1 you you 2097152 Jul 17  2026 'Super Metroid.sfc'
#   -> dirty contacts or an under-powered hub.
#   Re-clean, move to a rear USB port, raise detectionDelay, re-dump.

When to RMA versus when to reflash

Distinguish a firmware problem from a hardware one. If the device enters DFU mode cleanly (you see 03eb:2ff9 on lsusb) but never mounts as a normal volume, it is a firmware problem — reflash 0.18c and it will almost certainly come back. If it will not enter DFU at all, does not enumerate on any port with any cable, or the LED never lights, that is a hardware fault and a warranty conversation with the seller. The reflash costs you five minutes; try it before you assume the unit is dead.

The Retrode 3 and a Complete Config

The recurring question in 2026 is whether to buy the 2 or wait for the 3. The honest answer is “buy the 2, because the 3 is not for sale,” but the 3 is real enough to describe, and the config that closes this article is the last thing you need for the 2.

The spec, and the CPU that contradicts itself

The Retrode 3 is DragonBox's in-development successor, and it is a genuine step up: a full Linux computer that registers as a USB-Ethernet device so its entire interface runs in a web browser with no drivers on any OS; built-in Wi-Fi; slots for SNES/Super Famicom, Mega Drive/Genesis, and — new — NES, plus Lynx as a plug-in; ROM and SRAM reading; and, crucially, flash-cart writing (MegaDrive DragonDrive works now; SNES and Lynx writing are promised “when it ships”). It is built on Sanni's open-source Cart Reader, and it is spread across four public repositories — the OSCR fork, the kernel, the Debian userspace, and the hardware — under GPLv3 software, CC BY 4.0 hardware, and CC0 docs. One caveat The Machine cannot let pass: DragonBox's own page contradicts itself on the processor, describing a “MIPS processor” up top and “its own ARM processor and a Linux operating system (Debian)” lower down. Do not repeat “MIPS” as settled fact; it is, for now, “a Linux SoC” until the shipping unit resolves the discrepancy.

Status, openness, and whether to wait

As of July 2026 it is target-end-of-year, under €100, out of stock, notify-me only. DragonBox has said publicly there are “10 fully working prototypes” and that they are “looking for developers,” which tells you exactly where it is: functional hardware, unfinished software, no ship date you should plan around. Its pitch is being “practically unbrickable — just flash a new image” and “fully open source and therefore future-proof,” and because it is built on the same OSCR codebase, Sanni Cart Reader plugins are cross-compatible in both directions. If you want to browse the actual code, the retrode3-oscr repository and the DragonBox product page are the primary sources. My advice: if you need to dump a cart this month, buy the Retrode 2, which is proven and driverless. If you want NES, flash writing, and a browser UI, register for the 3 and check back at year's end — and in the meantime, if your interest is in how far dedicated preservation hardware has come, our deep dive on the Analogue 3D's firmware is the companion piece on the FPGA side of the same hobby.

Advanced tips and the complete RETRODE.CFG

A few things that separate a casual dumper from a careful one. Keep a No-Intro/Redump DAT on hand and verify every dump — an unverified dump is a rumor. Turn on filenameChksum when batch-dumping similarly-named carts so two “Sonic” files do not overwrite each other. Raise detectionDelay for any cart with marginal contacts rather than fighting it. Remember that the Retrode's controller ports double as driverless USB gamepads — a genuinely useful second life for the device between dumping sessions. And label your output the moment you make it, because a folder of game(1).sfc is a folder you will re-dump in a year. Here is a complete, drop-in RETRODE.CFG that reflects sane defaults; place it at the root of the volume and RESET to load it (the exact key set is confirmed, though the online doc has since gone dark, so treat the file as illustrative-of-format):

# ============================================================
# RETRODE.CFG - complete working configuration
# Place at the root of the RETRODE volume; press RESET to load.
# Config support requires firmware >= 0.17g (use 0.18c stable).
# ============================================================

# --- Save protection ---
# 1 = SRAM read-only (safe default). Set 0 ONLY to write saves
# back to a cart, then set it to 1 again when you are done.
sramReadonly 1

# --- Filenames ---
# Append a checksum to output names so similar carts don't collide.
filenameChksum 1

# --- Detection ---
# Settle delay before reading a cart. Raise it (e.g. 1-2) for
# carts with marginal or lightly-oxidized contacts.
detectionDelay 0

# --- Overrides (leave blank/unset for auto-detection) ---
# forceSystem  - override detected console (e.g. GG for Game Gear)
# forceSize    - override detected ROM size (odd/homebrew carts)
# forceMapper  - override detected SNES mapper
# forceSystem
# forceSize
# forceMapper

# --- Sega SRAM width ---
# Set 1 if Genesis/Mega Drive saves come back scrambled.
segaSram16bit 0

# --- Output extensions ---
snesRomExt sfc       # SNES ROM extension (sfc / smc)
segaRomExt bin       # Sega ROM extension (bin / md / gen)
sramExt    srm       # save-file extension
# ============================================================

That is the whole tool. A read-only window onto silicon you already own, a config file with ten keys, and firmware that has not changed since 2016 because it did not need to. In a hobby full of devices chasing the next benchmark, the Retrode's refusal to move is the most reassuring thing about it. Dump your carts, verify your hashes, protect your saves, and file the results somewhere with a backup. The cartridges are not getting any younger, and the batteries inside them are getting older by the day.