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

There is a specific kind of dread that arrives when you power on a Super Nintendo cartridge you last touched in 1998 and the save file — your save file, the one with 300 hours in it — is simply gone. The battery died. It was always going to die. A CR2032 soldered next to the SRAM in 1994 owes you nothing.

The Retrode exists for the moment before that. It is a small USB box that turns a game cartridge into a removable drive: plug the cart into the top, plug the box into your computer, and the ROM appears as a file you can copy. The save appears next to it. No emulator exploits, no shady download, no account — just the bytes off the silicon you already own, read over a driverless mass-storage link that Windows, macOS, and Linux all understood a decade ago and still do.

This is the full walkthrough: prerequisites with real versions, twelve numbered steps from unboxing to a checksum-verified dump, the RETRODE.CFG file key by key, SRAM save backup and write-back, the three plug-in adapters, firmware flashing over DFU, the pitfalls that eat an afternoon, a troubleshooting table, and — because it is finally close — what the Retrode 3 changes when it lands late in 2026. The shipping unit is the Retrode 2, $99.99 at Stone Age Gamer or €64.90 direct from DragonBox. Let's get the cartridges off life support.

What the Retrode Really Is

Strip away the retro-gaming romance and the Retrode is a translator. On one side: a game cartridge, a slab of mask ROM and battery-backed SRAM speaking a parallel bus protocol that Nintendo and Sega froze in the early 1990s. On the other: a modern computer that speaks USB and nothing else. The Retrode sits between them and does exactly one clever thing — it presents the cartridge as a USB Mass Storage device, the same class your thumb drive uses, so the ROM shows up as an ordinary file you can drag off.

A cartridge as a thumb drive

Plug a Super Nintendo or Sega Genesis cartridge into the top of the unit, connect the USB cable, and a removable volume mounts. Inside sits a single ROM file — an .sfc for SNES, a .bin for Sega — usually a save file next to it, and a small text file called RETRODE.CFG. That is the entire interface. No installer, no launcher, no cloud. The device is a composite USB gadget: a mass-storage endpoint for the cartridge and a set of USB HID gamepads for the original controller ports on the front. Windows, macOS, and Linux all treat it as generic hardware and need no drivers — the same driverless story that let it run on the OpenPandora and Caanoo handhelds years ago.

Read-Only Memory means read-only

The Retrode reads. It does not, on the Retrode 2, write to ROM. The project's own FAQ answers the inevitable "can it flash a game onto a cart?" with the tautology it deserves: ROM stands for Read-Only Memory, hence, no. What it can write is the SRAM — the battery-backed save memory — provided you unlock it in the config. That distinction is the whole reason the device matters for preservation: the ROM is immutable and identical on every copy of a game, but your save is a unique artifact decaying on a thirty-year-old coin cell. More on that below.

Retrode 2 today, Retrode 3 on the horizon

The shipping product is the Retrode 2, and it is a second revision with a long, faintly Germanic corporate history. Matthias Hullin conceived the original on the OpenPandora forum in 2009; it sold through Retrode UG (haftungsbeschränkt) until that entity wound down in the summer of 2013; the Retrode 2 was resurrected through OpenPandora GmbH in March 2015 and is now handled by the DragonBox store. It costs $99.99 at Stone Age Gamer or €64.90 direct, with plug-in adapters at $39.99 / €25 each. The Retrode 3 — a genuine redesign around a Linux system-on-chip — is in development for late 2026, and we cover what it changes at the end of this guide. If you want the FPGA-accurate hardware angle on original carts instead, our writeup on the MiSTer Multisystem 2 is the companion piece.

Prerequisites and Versions

The Retrode's great virtue is that it asks for almost nothing. There is no dependency hell here, no toolchain to compile. But "almost nothing" is not "nothing," and the difference between a clean dump and a wasted afternoon usually lives in the prep.

The hardware you actually need

A Retrode 2 unit, obviously, plus the USB cable it ships with — the box is the unit, a cable, and a single instruction sheet, and that is all. A computer with a free USB port and, ideally, a powered hub if you are also driving power-hungry adapters. The cartridges themselves, with clean contacts: reach for 90%-plus isopropyl alcohol and a lint-free swab, and never — the lore is older than the hardware — blow into the connector. Human breath is humid and mildly corrosive; the 1988 playground ritual damaged more pins than it ever fixed. Optional but useful: the original SNES or Sega controllers if you want to map them as USB gamepads, and the plug-in adapters ($39.99 / €25 each, or €65 for all three) if you are dumping Game Boy, Nintendo 64, or Master System.

Software: less than you'd think

For dumping ROMs and saves, nothing is strictly required — it is a mass-storage drive, and copy is a first-class verb on every OS. What you want is a small verification kit. A checksum tool: sha1sum and a crc32 utility on Linux and macOS, or CertUtil -hashfile on Windows. A No-Intro DAT file and a ROM manager such as ClrMamePro or RomVault to compare your dump against the community's known-good hashes. An emulator to confirm the dump boots — RetroArch with the correct core is the pragmatic default, and our core-by-core RetroArch walkthrough covers which one to load for SNES versus Genesis. For firmware flashing only: Atmel FLIP on Windows, or dfu-programmer (version 0.7 or newer) on Linux and macOS.

Versions, and what you don't need

The firmware is frozen. The last builds are 0.18c (stable) and 0.18d beta 3, both from around 2016, and there is no newer line — if a listing or a forum post promises you a "v0.22 with enhanced cart support," it is fiction; no such version exists. You do not need special drivers, a proprietary cable, or a single byte from a ROM download site. That last point is the entire ethic of the device: you are reading cartridges you own, not acquiring games you don't. Where personal cartridge backups sit legally is its own gray thicket — format-shifting media you own is defensible in spirit, the DMCA's §1201 anti-circumvention language is less charitable in letter, and none of this is legal advice — but the Retrode itself circumvents no copy protection. It just reads the bus.

The 12 Steps

Here is the full procedure, unbox to verified dump. Each step carries its rationale, because "why" is what keeps you from cargo-culting the one time a cart misbehaves. Budget about twenty-five minutes for your first cartridge and five for every one after.

Steps 1 through 6: mount and inspect

1. Clean the cartridge contacts. Swab the edge connector with 90%-plus isopropyl and let it flash off. Rationale: the single most common cause of a no-mount or a garbage dump is oxidized or grimy contacts. Thirty years of finger oil is not a data channel.
2. Identify the two slots. The lower, shorter slot takes Sega Mega Drive / Genesis; the upper, wider slot takes SNES / Super Famicom. Rationale: the slots are keyed differently for a reason, and forcing a cart into the wrong one bends pins you cannot easily replace.
3. Seat the cartridge fully, label facing you. Firm, even pressure until it stops. Rationale: a partially seated cart makes intermittent contact, and intermittent contact produces a file that looks like a ROM and boots like static.
4. Attach any adapter first, then connect USB last. If you are using the N64, GBx, or SMS adapter, mount it before you plug the Retrode into the computer. Rationale: adapters are detected at USB enumeration; hot-plugging one after the drive has mounted is unsupported and simply won't register.
5. Wait for the volume to mount. A removable drive labeled RETRODE (or similar) appears within a second or two. Rationale: enumeration is near-instant; if nothing shows after five seconds, stop and reclean rather than yanking cables.
6. Open the drive and read the directory. You should see the ROM, a save file, and RETRODE.CFG. Rationale: this listing is your virtual filesystem and your first proof of a good read.

Expected directory on a healthy SNES cartridge:

$ ls -la /media/$USER/RETRODE/
total 4128
-r--r--r-- 1 user user 4194304 Jan  1  2000 SUPER~1.SFC
-rw-rw-rw- 1 user user    8192 Jan  1  2000 SUPER~1.SRM
-r--r--r-- 1 user user     311 Jan  1  2000 RETRODE.CFG

# Names are 8.3-truncated on the FAT volume; the ROM carries a
# read-only bit, the .SRM is read-write, and RETRODE.CFG is your
# settings file. On Windows the same volume shows as a drive letter.

Steps 7 through 9: copy and verify

7. Copy — never move — the ROM to local disk. Drag it to a working folder. Rationale: the source is read-only anyway, but copying (rather than opening in place) keeps the USB link from being hammered by an emulator reading over it, and gives you a stable local file to hash.
8. Compute a checksum. Take an SHA-1 and a CRC32 of the copied file. Rationale: a checksum is the only objective statement about whether your dump is bit-for-bit what it should be. Vibes are not verification.
9. Cross-check against a No-Intro DAT. Feed the file to a ROM manager and match the hash. Rationale: No-Intro is the reference set of clean, verified dumps; a match means you nailed it, a mismatch means either a bad read or a legitimately different regional revision — both worth knowing before you archive.

# Copy, don't move — the ROM is read-only anyway.
$ mkdir -p ~/dumps
$ cp \"/media/$USER/RETRODE/SUPER~1.SFC\" ~/dumps/super_mario_world.sfc
$ cp \"/media/$USER/RETRODE/SUPER~1.SRM\" ~/dumps/super_mario_world.srm

REM Windows equivalent (E: is the Retrode volume)
> copy E:\\SUPER~1.SFC %USERPROFILE%\\dumps\\super_mario_world.sfc

$ sha1sum ~/dumps/super_mario_world.sfc
<40-hex-sha1>  super_mario_world.sfc

$ crc32 ~/dumps/super_mario_world.sfc
<8-hex-crc32>

REM Windows has no built-in crc32; use CertUtil for SHA-1:
> CertUtil -hashfile super_mario_world.sfc SHA1

# Match the hash against the No-Intro DAT in ClrMamePro/RomVault.
# A match = bit-perfect dump. A mismatch = re-dump or a different revision.

Steps 10 through 12: saves, eject, confirm

10. Back up the SRAM save. Copy the .srm file to your working folder alongside the ROM. Rationale: this is the actual preservation win. The ROM is identical on every cart ever pressed; your save is a unique, decaying artifact, and the battery keeping it alive is on borrowed time.
11. Eject the volume before removing the cartridge. Use your OS's safe-remove, then pull the cart. Rationale: the user guide is explicit that hot-swapping can potentially damage on-cartridge savegames. Treat the eject as mandatory, not optional.
12. Load the dump in an emulator to confirm it boots. Point RetroArch (or your frontend of choice) at the file and watch it reach the title screen. Rationale: a checksum proves the bytes; a boot proves the experience. If you plan to keep a library on a handheld or an all-in-one box, this is the moment to file it — a Retroid Pocket or a Batocera build will happily take it from here.

The RETRODE.CFG File

The RETRODE.CFG file is the device's entire settings panel, delivered as plain text on the virtual drive. It has existed since firmware 0.17g, and it is where you change how the Retrode detects, names, and protects what it reads. Open it in any text editor, change a value, save, and the firmware re-reads it — the status LED blinks when it parses the file, which is your confirmation that the edit took.

Where the file lives and how it's read

The file sits at the root of the mounted volume, next to the ROM and save. It is parsed at mount time and again whenever you save changes to it. Keys are one-per-line as key/value pairs; unknown keys are ignored rather than fatal, which is forgiving but also means a typo'd key silently does nothing. One honest caveat: the canonical documentation page at retrode.org now 302-redirects to retrode.com, and the old CFG reference is effectively dead. Treat the exact syntax below as illustrative of the format; the key names are confirmed, but if a value doesn't behave, cross-check against the archived Retrode user guide rather than trusting any single blog's punctuation.

The keys, annotated

sramReadonly — 0 or 1. The default 1 write-protects on-cart saves; set it to 0 to write an .srm back to the cartridge. forceSystem — normally auto; override it to name a system the firmware mis-sniffs (the 0.18d beta fixed a case where Game Gear, GG, wasn't recognized). forceSize — 0 auto-detects ROM size; override only to rescue a bad read. forceMapper — 0 auto; override for oddball SNES memory mappers. detectionDelay — milliseconds of settle time added before detection, your friend for a flaky cart. filenameChksum — set 1 to append a CRC to the virtual filename. segaSram16bit — set 1 for Sega carts wired for 16-bit-wide SRAM. sramExt, snesRomExt, segaRomExt — the file extensions used for saves and for SNES and Sega ROM dumps respectively.

A working example

A conservative configuration — auto-detect everything, keep saves protected — looks like this:

# RETRODE.CFG  —  parsed at mount; the LED blinks when it is read.
# Lines are key/value. Unknown keys are ignored. Treat the exact
# syntax as illustrative — confirm against the archived user guide.

sramReadonly   1      # 1 = protect saves (default). 0 = WRITE .srm back.
forceSystem    auto   # auto | SNES | MD | GG | SMS ...
forceSize      0      # 0 = auto-detect ROM size
forceMapper    0      # 0 = auto; override for oddball SNES mappers
detectionDelay 0      # add ms if a flaky cart mis-detects on mount
filenameChksum 0      # 1 = append CRC to the virtual filename
segaSram16bit  0      # 1 for Sega carts with 16-bit-wide SRAM
sramExt        srm    # extension used for the save file
snesRomExt     sfc    # extension for SNES ROM dumps
segaRomExt     bin    # extension for Sega ROM dumps

Dumping SRAM Saves

If ROM dumping is the headline, SRAM is the story that matters. A ROM is redundant — millions of identical copies exist, and No-Intro has already archived a verified one. Your save is not redundant. It is a single copy, held in volatile memory by a coin cell soldered into the cartridge decades ago, and when that cell finally drops below the SRAM's retention voltage, the save is gone with no ceremony.

Why saves are the real prize

The CR2032 in a 1994 cartridge was specified for maybe ten to fifteen years. We are well past that. Every powered-off SNES or Genesis cart with battery-backed memory is now running on luck. The Retrode's ability to pull that .srm file off before the battery dies is, in preservation terms, the single most valuable thing it does — which is why the University of Maryland's digital-humanities researchers wrote about using it to rescue exactly this kind of volatile data. The ROM can wait. The save cannot.

Reading the save

By default the save file appears on the drive read-only and you simply copy it off, exactly as in step 10 above. That is the safe, non-destructive path and the one you want for archiving: it never touches the cartridge's memory, it just reads it. Master System SRAM reading, for the record, was only added in firmware 0.18 — older firmware won't pull SMS saves at all, which is one of the few concrete reasons to flash.

Writing a save back — and the risk

Writing is the dangerous direction. To restore a save — say you fixed a corrupted file, or you want to move a playthrough onto the physical cart — set sramReadonly 0 in RETRODE.CFG, then copy the .srm onto the drive. The firmware flushes it to the cartridge's SRAM. The hazard is obvious and unforgiving: if you unplug or hot-swap mid-write, you can corrupt the save you were trying to save. Always back up the existing file first, always sync/flush, and always eject before removing. The sequence:

# 1. Back up the existing save FIRST — always.
$ cp \"/media/$USER/RETRODE/SUPER~1.SRM\" ~/dumps/backup.srm

# 2. Unlock writing: open RETRODE.CFG on the drive and set
#      sramReadonly 0
#    Save it. The LED blinks when the firmware re-reads the CFG.

# 3. Write your save ONTO the cart, flush, and eject before removing.
$ cp ~/edited_save.srm \"/media/$USER/RETRODE/SUPER~1.SRM\"
$ sync

Plug-In Adapters

Out of the box the Retrode 2 handles SNES and Sega Genesis. Everything else — Game Boy, Nintendo 64, Master System — arrives through plug-in adapters that seat into the SNES slot and re-route the pins. The current official lineup is three, at $39.99 / €25 each or €65 for the set, and each has its own quirks and voltage rules worth knowing before you buy.

The three current adapters

The N64 adapter dumps ROM cleanly and exposes up to two controller ports, but N64 save support is still listed as "firmware pending" — you get the game, not the save, so pair it with a dedicated N64 save tool if the file matters. The GBx adapter covers Game Boy, Game Boy Color, and Game Boy Advance ROMs; GB and GBC SRAM saves read fine, but GBA's SRAM and flash saves are, again, "pending." The SMS adapter reads Master System ROMs, and — as of firmware 0.18 — Master System SRAM too; be aware many SMS cartridges never stored an internal title, so the header name often comes up blank and you'll rename by hand.

Voltage and ordering rules

Voltage is not decorative. The N64 adapter runs at 3.3V. The GBx adapter switches by system: 5V for GB and GBC, 3.3V for GBA — get this wrong on a homemade adapter and you cook a cartridge. The universal rule across all adapters is connect the adapter before you connect USB: the Retrode reads its configuration at enumeration, and an adapter added after the drive has mounted is invisible. The N64 adapter in particular wants its controllers attached before power, too.

The exotic and the discontinued

The Retrode's back catalog once reached genuinely obscure formats — Virtual Boy and other oddities via one-off adapters — but most of those are discontinued because the cartridge connectors themselves are no longer manufacturable. Two edge cases people still ask about: the Sega 32X adapter works without its external PSU, and the Super Game Boy adapter does not work, because the Super Game Boy is effectively a whole console rather than a passive cartridge and the Retrode has no interest in emulating one. If you need those systems, that is a job for FPGA hardware, not a bus translator.

Flashing the Firmware

Most Retrode owners will never flash their firmware, and that is the correct default. The line is frozen, the hardware is simple, and "if it enumerates and dumps, leave it alone" is sound engineering. But there are real reasons to reflash — a very old unit predating a fix, or the Master System SRAM support added in 0.18 — so here is how, carefully.

Why you'd flash at all (and why you usually shouldn't)

The current firmware is 0.18c (stable) or 0.18d beta 3, built on Dean Camera's LUFA USB stack — the same well-worn AVR library behind countless DIY USB devices. The 0.18 changelog is modest and telling: improved N64 and GBA size detection, a LUFA library update, a Master System plug-in bugfix, and the addition of SMS SRAM reading. If none of those describe a problem you actually have, flashing buys you nothing but risk. And to be blunt about a recurring myth: there is no 0.22, no "enhanced cart support" update, no secret newer branch. The frozen line is 0.18c / 0.18d beta 3, full stop.

Entering DFU: HWB + RESET

The Retrode's brain is an Atmel AVR, the AT90USB646, and it flashes over the standard Atmel DFU bootloader. To enter it: hold the HWB button (button 7 on the board), tap and release RESET (button 8), then release HWB. The chip drops out of Retrode mode and re-enumerates as the Atmel DFU bootloader with USB ID 03eb:2ff9 — a stable, well-documented identifier you can confirm before you write a single byte.

FLIP on Windows, dfu-programmer everywhere else

On Windows, Atmel's FLIP utility is the graphical path: point it at the at90usb646 target and the .hex file. On Linux and macOS, dfu-programmer is the command-line equivalent. Grab the official .hex, verify you are in DFU, and run the erase-flash-reset cycle:

# Enter DFU: hold HWB (button 7), tap RESET (button 8), release HWB.
# The AVR re-enumerates as the Atmel DFU bootloader:
$ lsusb | grep -i atmel
Bus 001 Device 014: ID 03eb:2ff9 Atmel Corp. atmega/at90usb DFU bootloader

# Flash 0.18c on Linux/macOS (get the .hex from the official site):
$ dfu-programmer at90usb646 erase
$ dfu-programmer at90usb646 flash retrode_0.18c.hex
$ dfu-programmer at90usb646 reset

# Windows: use Atmel FLIP with the at90usb646 target instead.

If the flash fails, you are almost always not actually in DFU (re-do the HWB/RESET dance) or you targeted the wrong MCU — it is at90usb646, nothing else.

Five Common Pitfalls

Every one of these has cost someone an afternoon. Most are avoidable with a single habit change.

Contacts, seating, and slots

Pitfall 1 — dirty or partially seated carts. The failure mode is insidious because the drive may still mount and hand you a file; it just hands you a wrong file, full of dropped bytes. The fix is boring and total: clean with 90%-plus isopropyl, seat firmly, and if a dump fails its checksum, reclean and re-dump before blaming anything else. Pitfall 2 — the wrong slot. Lower is Sega, upper is SNES; a cart shoved into the wrong slot at best won't read and at worst bends pins. Confirm the slot before you push.

Saves and hot-swapping

Pitfall 3 — hot-swapping cartridges without ejecting. This is the one that actually destroys data. The official user guide warns in plain language that swapping carts live can potentially damage on-cartridge savegames, and it means it. Eject the volume, unplug if you're being careful, then swap. Your thirty-year-old save has survived this long; don't let impatience be what finally kills it.

Coprocessors and the write fantasy

Pitfall 4 — expecting every chip-enhanced cart to dump. This is the subtle one. Cartridges with a Super FX or DSP1 chip dump perfectly — the Retrode reads the ROM and the emulator runs the coprocessor. But SA-1 (Super Mario RPG, Kirby Super Star, Kirby's Dream Land 3), S-DD1 (Star Ocean, Street Fighter Alpha 2), and Sega's SVP (Virtua Racing) are not supported, and no amount of recleaning changes that — it is a hardware limitation, not a contact problem. Don't lump Super FX in with the unsupported set; people do, and then chase a phantom fault. Pitfall 5 — trying to write a game to a cartridge. The Retrode 2 cannot flash ROM. Full stop. Writing games to flash carts is a Retrode 3 feature, and even there it is rolling out by system. If your goal was to burn a repro, this is the wrong tool.

Troubleshooting Table

Symptom, likely cause, fix. Work top to bottom — the common causes are near the top for a reason.

Reading the table

Most of these resolve to three root causes: dirty contacts, something plugged in the wrong order, or an unsupported cartridge. If a row's fix doesn't stick, re-verify with a checksum before escalating.

When none of it works

If you have cleaned, reseated, confirmed the slot, re-entered DFU where relevant, and the dump still fails its hash, the likeliest remaining answers are an unsupported coprocessor cart or a genuinely failing cartridge. Cross-check the specific title against the unsupported list before concluding your unit is broken.

Advanced Tips

Once the basic loop is muscle memory, the config file and a couple of habits turn the Retrode from a toy into a proper preservation station.

Verify against No-Intro, not vibes

Adopt the DAT as gospel. Set filenameChksum 1 so the virtual filename carries its CRC, then run every dump through ClrMamePro or RomVault against the current No-Intro set. A green match is a bit-perfect dump you can archive with confidence; anything else gets re-dumped. This single discipline is the difference between "I have some ROM files" and "I have a verified preservation copy."

Coax the stubborn carts

Flaky cartridge that mis-detects on mount? Raise detectionDelay to add settle time before the firmware reads the bus — a few hundred milliseconds often steadies an intermittent connector. An unusual SNES cart that auto-detects the wrong mapper or size? Override forceMapper and forceSize to nail it down. A Game Gear cart the firmware calls a Master System? forceSystem GG. The LED blinking on each CFG re-read tells you the change registered; the checksum tells you whether it helped.

Feed dumps to hardware, not just emulators

A verified dump is portable. Drop it into a Batocera build and it slots straight into the library scraper; load it onto a handheld; or, if you care about frame-accurate playback of the exact silicon you dumped, run it on FPGA hardware where the timing matches the original console rather than approximating it. For choosing the right emulator core to pair with each system, libretro's own core documentation is the authoritative reference. The Retrode's job ends at a trustworthy file — where that file goes next is the fun part.

The Retrode 3, Late 2026

The Retrode 2 is a frozen, finished product. The Retrode 3 is the reason to pay attention again. It is a ground-up redesign, in development at DragonBox for a target of late 2026 at a price under €100 (roughly $108). It is not for sale yet — the only thing you can do today is leave a "notify me" pre-registration — but the shape of it is clear, and it fixes the two things that dated the Retrode 2: the read-only ceiling and the driver-era interface.

A Linux SoC with a browser UI

Where the Retrode 2 is an AVR presenting mass storage, the Retrode 3 is a small computer. It runs Debian Linux, has built-in Wi-Fi, and registers over USB as an Ethernet device — which means its interface is a web page. You point a browser at it, on any OS, with no drivers at all, and drive the whole thing from there. DragonBox describes it as "practically unbrickable — just flash a new image" and "fully open source and therefore future-proof," and the openness is not marketing: it is Made in Germany with published hardware, kernel, and userspace.

New tricks: NES, flash-carts, and Sanni's Cart Reader

The slot list grows a NES port alongside SNES/SFC and Mega Drive/Genesis, reading ROM and SRAM from all of them. More importantly, it writes: flash-cart support is arriving by system — Mega Drive's DragonDrive works now, with SNES and Atari Lynx flashing slated for launch, and Lynx itself handled as a plug-in. The engine under all this is Sanni's open-source Cart Reader project (cartreader.net), adapted into a Linux CLI. The Retrode 3's code lives across four DragonBox repositories — retrode3-oscr, retrode3-kernel, retrode3 (the Debian userspace), and retrode3-hardware — under GPLv3 software and CC-licensed hardware. DragonBox has publicly said it has "10 fully working prototypes" and is "looking for developers," which tells you exactly how far along, and how community-driven, this is.

The MIPS-or-ARM question

One deadpan caveat, because we read the whole page so you don't have to: the official listing cannot decide what CPU it runs. The opening description says "MIPS processor"; a few paragraphs down it says "its own ARM processor and a Linux operating system (Debian)." Both cannot be true, and we are not going to pretend to resolve a contradiction the vendor hasn't. Call it "a Linux SoC," wait for shipping hardware, and check the silkscreen yourself. It is the kind of detail that gets fixed quietly before launch and never acknowledged.

Complete Configuration

Here is the whole thing in one place: a complete, annotated RETRODE.CFG tuned for the common case — clean ROM dumps, SRAM backup, saves protected from accidental writes. Drop it at the root of the mounted drive, and adjust the two or three values you actually need.

The full RETRODE.CFG

# ============================================================
#  RETRODE.CFG  —  complete working configuration
#  Retrode 2, firmware 0.18c. Drop this on the virtual drive.
#  Goal: clean ROM dumps + SRAM backup, saves protected.
# ============================================================

# --- Save handling ---
sramReadonly   1        # protect on-cart saves (flip to 0 to write)
sramExt        srm      # .srm alongside the ROM
segaSram16bit  0        # set 1 only for 16-bit-wide Sega SRAM carts

# --- System / mapper detection ---
forceSystem    auto     # let the firmware sniff SNES/MD/SMS/GG
forceSize      0        # auto-size the ROM (override only for bad reads)
forceMapper    0        # auto SNES mapper (LoROM/HiROM/etc.)
detectionDelay 0        # raise to 200-500 (ms) for flaky contacts

# --- File presentation ---
filenameChksum 0        # 1 appends CRC32 to the filename
snesRomExt     sfc      # SNES/SFC dump extension
segaRomExt     bin      # Mega Drive/Genesis dump extension

# ============================================================
#  Notes:
#  - SA-1, S-DD1, and Sega SVP carts are NOT supported.
#  - Super FX and DSP1 dump fine; the emulator runs the chip.
#  - Eject before swapping carts, or you risk the save.
# ============================================================

The one-line summary

Clean the contacts, use the right slot, copy don't move, checksum against No-Intro, back up the save, and eject before you swap. Set sramReadonly 0 only when you deliberately mean to write a save back, and set it to 1 again the moment you're done. Everything else the firmware auto-detects, and it has been auto-detecting it correctly since 2016.

The verdict

The Retrode 2 is not fast, not fancy, and not new — the firmware hasn't moved since 2016 and the industrial design is older than some of the people dumping carts with it. It doesn't need to be any of those things. It does one job — turning the cartridges you own into verified, archivable files, saves and all — and it does that job with the kind of driverless, no-nonsense reliability that has kept it relevant across three corporate owners and fifteen years. If you have a shoebox of SNES and Genesis carts with dying batteries, the clock is the only thing that matters, and this is the tool. If you want the follow-along version of the dumping loop, our 12-step field guide walks the same path with a different cart on the bench. When the Retrode 3 ships late in 2026 with its browser UI and flash-cart writing, we will put it through the same wringer. Until then, go clean some contacts.