Retrode 2 2026: Dump SNES/Genesis in 12 Steps, 20 Min

There is a particular silence that settles over a piece of hardware once it stops receiving updates, and the Retrode has been sitting in it since about 2016. This is not, by itself, a criticism. The Retrode 2 is a small grey box that reads a Super Nintendo or Sega Genesis cartridge and hands your computer the ROM as an ordinary file, and it does this so reliably, and so unglamorously, that no one has needed to touch the firmware in a decade. Whether that is a triumph of engineering or the death rattle of a product category depends entirely on your mood when you plug it in.

This is a tutorial for the device that actually exists. The Retrode 2 ships today; the long-promised Retrode 3 does not, and as of 15 July 2026 it remains a pre-registration page and a stack of GitHub repositories. We will get to that vaporware near the end, because it is genuinely interesting. First, the useful part: how to take a cartridge you own, connect a driverless USB reader, and walk away with a verified, headerless dump you can archive, emulate, or feed into an FPGA — in roughly twelve steps and twenty minutes, most of which is spent cleaning contacts rather than moving data.

What the Retrode 2 Actually Is

Before you buy anything, understand what this device does and, more importantly, what it refuses to do. The Retrode is not an emulator, not a flash cart, and not a subscription. It is a bridge between a physical cartridge and your filesystem, and it is deliberately dumb about it.

A cartridge reader, not an emulator

The Retrode reads the mask ROM inside a game cartridge and presents its contents to your computer. It does not run the game. It does not decrypt, patch, or “improve” anything. When you insert a Super Metroid cartridge, a file called SUPER METROID.sfc appears on a small virtual drive, and that file is a bit-for-bit copy of the ROM chip. The official documentation is blunt about the one direction it will not go: ROM stands for Read-Only Memory, so writing a new game onto a retail cartridge is not on the menu. Save RAM is a different story, which we will cover in its own section.

The two-slot, four-port layout

A Retrode 2 has two cartridge slots. The wide upper slot takes SNES and Super Famicom carts; the shorter lower slot takes Sega Mega Drive and Genesis carts. It is region-free at the connector level — a Japanese Super Famicom board and a US SNES board both mount, because the Retrode reads silicon, not lockout chips. Along the front are four controller ports (two SNES-style, two Sega-style) wired to the USB HID side of the device, plus two buttons on the board: HWB (button 7, reserved for custom firmware functions) and RESET (button 8, which re-scans the slots). An LED lights during ROM or RAM access and blinks when the config file is rewritten.

Why it still matters in 2026

Cartridge preservation is not a solved problem, it is an ongoing one, and the Retrode remains the friendliest on-ramp to it. Dumping your own carts gives you clean, headerless files that match preservation databases, that load identically into software emulators and into hardware like an FPGA MiSTer Multisystem 2, and that will outlive the increasingly brittle battery-backed SRAM inside a thirty-year-old board. The University of Maryland's preservation group has written about exactly this workflow. The Retrode is boring, and boring is precisely what you want from an archival tool.

System	Slot / Adapter	ROM dump	SRAM save	Notes
SNES / Super Famicom	Native (upper slot)	Yes	Yes (many carts)	Region-free; SA-1 and S-DD1 titles unsupported
Mega Drive / Genesis	Native (lower slot)	Yes	Yes	Some 16-bit SRAM carts need segaSram16bit
Game Boy / Color	GBx adapter	Yes	Yes	5V logic; connect adapter before USB
Game Boy Advance	GBx adapter	Yes	Firmware pending	3.3V logic; save/flash support not finished
Nintendo 64	N64 adapter	Yes	Firmware pending	3.3V; up to two pads; ROM only for now
Master System	SMS adapter	Yes	Firmware pending	No header title — filename comes out blank
Game Gear	SMS adapter	Yes	Firmware pending	May need forceSystem GG on older firmware
Sega 32X	32X cart	Yes	—	Works without its external PSU attached

Prerequisites: Hardware and Software Versions

The good news, and the reason this tutorial is shorter than most of ours, is that the software list is nearly empty. The Retrode was designed to work without drivers on every operating system that supported USB mass storage in 2011, which by now means all of them.

Hardware you need

You need a Retrode 2. In 2026 it ships from two places worth naming: DragonBox in Germany lists the base unit at about €64.90 with plug-in adapters at €25 each (or €65 for the N64/GBx/SMS three-pack), and Stone Age Gamer in the US sells it at $99.99 with adapters at $39.99 each. Its original MSRP a decade ago was $89.99; you will occasionally see that number quoted as if it were current, and it is not. The retail box contains the unit, a USB cable, and a single instruction sheet. Beyond that you need a data-capable USB cable (a shocking number of “USB cables” are charge-only), a free USB-A port, and the cartridges you intend to dump. A pack of 99% isopropyl alcohol and some lint-free swabs will do more for your dump quality than any software setting.

Software you (mostly do not) need

For basic dumping: nothing. The Retrode mounts as a removable drive on Windows, macOS, and Linux — and, as a period detail, on the old Pandora and Caanoo handhelds it was partly designed alongside. You copy files off it with your file manager. You will only need software in two situations. First, to play the dumps, you want a modern emulator front-end — a current RetroArch build with the right libretro cores installed is the standard answer. Second, on the rare occasion you decide to reflash the firmware, you need Atmel's FLIP (Windows) or the dfu-programmer command-line tool (Linux and macOS), plus a copy of the last firmware image. That is the entire toolchain.

The cartridges themselves

The Retrode reads what is physically on the board, so the board has to be readable. Inspect each cartridge's edge connector under a light. Grey, hazed, or corroded contacts are the single largest cause of bad dumps, far ahead of any firmware limitation. Clean them before you start, not after your first garbage dump. If a cartridge has a save battery you care about, note that hot-swapping carts while the Retrode is powered can, per the official user guide, “potentially damage on-cartridge savegames” — so plan to eject and re-seat deliberately, not casually.

How It Works: Mass Storage Meets HID

Understanding the Retrode's two personalities makes every later step and every troubleshooting entry obvious rather than mysterious. It is a composite USB device: it enumerates as two things at once.

The USB Mass Storage device

The first personality is a tiny USB flash drive. When you connect the Retrode, the operating system sees a small FAT volume labelled RETRODE — on the order of megabytes, not gigabytes, because it is not real storage. It is a window onto the cartridges. On Linux the kernel logs a mass-storage device and a block device appears; on macOS and Windows a removable drive shows up. Something like this:

$ dmesg | tail -4
usb 1-2: new full-speed USB device using xhci_hcd
usb 1-2: New USB device found, Product: Retrode
usb-storage 1-2:1.0: USB Mass Storage device detected
scsi 6:0:0:0: Direct-Access  Retrode  Retrode  0.18  PQ: 0 ANSI: 2

$ lsblk -o NAME,LABEL,SIZE,FSTYPE
NAME   LABEL    SIZE FSTYPE
sdb    RETRODE   16M vfat

The same volume looks like this elsewhere. The label is the constant you key on:

# macOS
$ diskutil list | grep -i retrode
   1:  DOS_FAT_16  RETRODE  16.7 MB  disk4s1

# Windows (PowerShell): a removable drive named RETRODE
PS> Get-Volume | Where-Object FileSystemLabel -eq 'RETRODE'
DriveLetter FileSystemLabel FileSystem DriveType Size
E           RETRODE         FAT        Removable 16 MB

The HID gamepad side

The second personality is a set of USB Human Interface Devices — the four controller ports. Plug a real SNES or Sega pad into the front of the Retrode and your computer sees a standard USB gamepad, no driver required. This is genuinely useful: it means you can dump a game and play it on original controllers through the same box. One quirk that trips people up: the SNES mouse only works in the left controller port. If Mario Paint refuses to see the mouse, you have it in the wrong socket, not a broken device.

What a dumped file looks like

Insert a cartridge and the virtual drive populates. SNES carts produce a .sfc ROM and, if the game saves, a .srm file; Sega carts produce a .bin ROM and a matching .srm. A RETRODE.CFG file always sits alongside them. The ROM file is presented read-only; the save file is writable but write-protected by default. A directory listing tells you everything:

$ ls -la /media/$USER/RETRODE
total 3080
-r--r--r-- 1 user user 3145728 Jan  1  2016 SUPER METROID.sfc
-rw-rw-rw- 1 user user    8192 Jan  1  2016 SUPER METROID.srm
-rw-rw-rw- 1 user user     512 Jan  1  2016 RETRODE.CFG

Note the permissions: the 3 MB ROM is r-- (24 megabit, exactly right for Super Metroid), the 8 KB save is rw-, and the config is editable. The filename comes from the cartridge's own internal header, which is why a Master System cart — whose header has no title field — arrives with a blank name.

Dumping SNES and Genesis in 12 Steps

Here is the core workflow. Read the rationale on each step once; after your third cartridge it becomes muscle memory and takes under a minute per game. The twenty-minute estimate assumes you are also cleaning contacts and verifying checksums, which you should be.

Steps 1 to 4: connect and mount

1. Clean the cartridge edge connector. Dampen a lint-free swab with 99% isopropyl alcohol and wipe the contacts until the swab comes away clean. Rationale: dirty contacts are the number-one cause of corrupt dumps, and no software can fix a bad electrical connection. Let it dry fully before inserting.
2. Connect the Retrode to your computer with a data USB cable, before inserting any cartridge. Rationale: the device should enumerate cleanly first, and certain adapters (the N64 adapter especially) expect to be connected before USB power is applied. Confirm the RETRODE drive appears.
3. Insert the cartridge fully and squarely into the correct slot. SNES/SFC in the wide upper slot, Genesis/Mega Drive in the shorter lower slot. Rationale: a half-seated cart reads partial or mirrored data. It should sit firmly, the way it sits in the original console.
4. Press RESET (button 8) to re-scan the slots. Rationale: the Retrode reads cartridge headers on reset and on connect. If you inserted the cart after mounting, RESET is what makes the ROM file appear. Watch the LED flicker as it reads.

Steps 5 to 9: copy and verify

1. Open the RETRODE drive and confirm the ROM file is present and the right size. A 24-megabit game should be roughly 3 MB; a 4-megabit game roughly 512 KB. Rationale: a wildly small or zero-byte file means a bad read — stop and re-clean rather than copying garbage.
2. Copy the ROM file off the Retrode to a working folder on your real disk. Do not edit it in place. Rationale: the virtual drive is not real storage and the file is regenerated from the cart; your archive should live on an actual filesystem you control.
3. If the game has a save you want, copy the .srm file off as well. Rationale: the on-cart battery is decades old. Backing up the SRAM now is often the whole reason to own a Retrode, and it costs you one extra copy operation.
4. Compute a checksum of the copied ROM. Run sha1sum (Linux/macOS) or a hashing tool on Windows. Rationale: the hash is how you prove the dump is clean, by comparing it against a preservation database in the next step.
5. Compare the checksum against a No-Intro DAT. Rationale: the Retrode produces headerless SNES dumps — no 512-byte copier header — which is exactly the format No-Intro catalogues. A match confirms a perfect dump; a mismatch sends you back to cleaning the contacts.

Steps 10 to 12: eject and archive

1. Safely eject or unmount the RETRODE drive before removing the cartridge. Rationale: the user guide explicitly prefers ejecting or unplugging over hot-swapping, because live swaps can corrupt on-cart saves. Treat it like any other removable drive.
2. Remove the cartridge, insert the next one, and press RESET. Rationale: RESET re-reads the freshly inserted cart. This is your loop for dumping a whole shelf; repeat steps 5 through 10.
3. Rename and file your dumps with a consistent convention, then back them up. Rationale: the header-derived names are inconsistent (ALL CAPS, truncated, occasionally blank), and a single unverified copy is not an archive. Store at least two copies on separate media.

Backing Up and Restoring SRAM Saves

The ROM is immortal; your save is not. Battery-backed SRAM is the most fragile thing in a retro cartridge, and the Retrode's ability to read and write it is arguably more valuable than its ability to dump ROMs, which you can find online anyway. Your childhood Link to the Past file, you cannot.

Reading a save off the cart

Reading is automatic. When a save-capable cartridge is mounted, the .srm file simply appears next to the ROM, and you copy it off like any other file. This works out of the box because reading SRAM is non-destructive. For most games the .srm maps directly to the format modern emulators expect, so a Retrode-dumped save often drops straight into RetroArch's save folder for that core. Do this before you do anything else with an old cart, because the next step — writing — carries a small risk, and you want a backup first.

Writing a save back to the cart

Writing is where the safety interlock lives. By default the RETRODE.CFG sets sramReadonly to 1, which write-protects the on-cart save so you cannot clobber it by accident. To restore or transplant a save, edit the config on the RETRODE drive, set the key to 0, save the file (the LED blinks to confirm the config was rewritten), then copy your .srm onto the drive over the existing one:

# On the RETRODE drive, edit RETRODE.CFG:
sramReadonly   0

# Then copy your backup save back onto the cart:
$ cp "$HOME/roms/saves/SUPER METROID.srm" /media/$USER/RETRODE/

When you are done, set sramReadonly back to 1. Leaving write enabled is how people overwrite the wrong save. Some Sega carts use 16-bit-wide SRAM and will need segaSram16bit set to 1 for saves to read and write correctly; if a restored Sega save reads as garbage, that is the first key to flip.

The battery you should replace anyway

None of this matters if the coin cell is dead. A cartridge whose CR2032 has finally given out will accept a written save that evaporates the moment you remove power. If you are going to the trouble of restoring saves, replace the battery — read the SRAM out first, swap the cell, then write the save back. The Retrode makes the save survive the surgery, which is the entire point.

Adapters and Other Systems

The two native slots cover the 16-bit era, but the Retrode's expansion header accepts plug-in adapters for a wider range of systems. This is where the honesty in the documentation earns its keep: several adapters read ROM perfectly while their save support is still, a decade on, listed as “pending.”

The plug-in adapter pack

Three adapters are current: N64, GBx (Game Boy family), and SMS (Sega 8-bit). They sell for $39.99 each at Stone Age Gamer, or €25 each / €65 for the set at DragonBox. Each plugs into the top of the Retrode and, importantly, should be connected before you apply USB power — the N64 adapter in particular runs at 3.3V and expects to be seated first. Older adapters for other systems were discontinued years ago because their cartridge connectors became unobtainable, which is the recurring tragedy of retro hardware: the limiting factor is rarely the silicon, it is a plastic connector no one manufactures anymore.

Game Boy, GBA, and N64

The GBx adapter reads Game Boy, Game Boy Color, and Game Boy Advance ROMs cleanly. Save support splits by generation: GB and GBC SRAM reads and writes fine (5V logic), while GBA save and flash support remains unfinished (3.3V logic). The N64 adapter dumps cartridge ROMs and supports up to two controller pads, but its save backup is firmware-pending — treat it as ROM-only for now. The SMS adapter dumps Master System and Game Gear ROMs; Game Gear carts may need forceSystem GG in the config on older firmware, a bug that the 0.18d beta 3 build specifically addressed.

SNES mouse, controllers, and the 32X

On the controller side, standard SNES pads and Sega 3- and 6-button pads all enumerate as USB gamepads. Two edge cases are worth memorising because they come up constantly: the SNES mouse works only in the left port, and the Sega 32X cartridge dumps successfully without its external power supply connected — a pleasant surprise, since the 32X was otherwise a power-hungry disaster in its own lifetime. The one adapter that does not work is the Super Game Boy: it is effectively a whole console on a cart, and the Retrode cannot drive it. Dump your Game Boy carts with the GBx adapter instead.

Firmware: Frozen at 0.18 Since 2016

Let us address the elephant, which is that the Retrode's firmware development ended during the Obama administration. This is presented online as a scandal roughly once a year. It is not one, but you should understand the reality before you go looking for updates that do not exist.

Why you probably should not touch it

The last builds are 0.18c (stable) and 0.18d beta 3 (roughly 2016), sitting atop an older 0.17 line. There is no 0.22, no “Enhanced Cart Support” update, no secret newer release — if a listing claims one, it is wrong. The firmware is built on Dean Camera's LUFA USB stack and runs on an Atmel AVR AT90USB646 microcontroller. For the overwhelming majority of owners, the shipping firmware already does everything the hardware can do, and reflashing buys you nothing but risk. The config-file system (added back in 0.17g) handles all the runtime behaviour you would otherwise want to change. So the honest advice is: leave it alone unless you have a specific reason, such as recovering a unit that shipped on an ancient build or applying the 0.18d Game Gear fix.

Entering DFU mode

If you must flash, the Retrode uses the standard Atmel Device Firmware Upgrade path. You enter the bootloader by hand: hold the HWB button (7), tap and release RESET (8), then release HWB. The board stops being a mass-storage device and comes up as an Atmel DFU bootloader instead, which you can confirm by its well-documented USB ID:

# Enter DFU: hold HWB (7), tap RESET (8), release HWB.
# Confirm the bootloader enumerated (Atmel, not the RETRODE drive):
$ lsusb | grep -i atmel
Bus 001 Device 009: ID 03eb:2ff9 Atmel Corp. atmega/at90usb DFU bootloader

Flashing with FLIP or dfu-programmer

On Windows, Atmel's FLIP is the GUI route: point it at the AT90USB646 target and load the .hex. On Linux and macOS, dfu-programmer is the command-line equivalent, and the three-command dance is always the same — erase, flash, reset:

$ sudo dfu-programmer at90usb646 erase
$ sudo dfu-programmer at90usb646 flash retrode_0.18c.hex
$ sudo dfu-programmer at90usb646 reset

The AT90USB646 bootloader is essentially unbrickable through this path — a failed flash just leaves you in DFU mode to try again, because the bootloader lives in protected memory. If the flash appears to fail, the usual cause is that the device never actually entered DFU mode (you will not see 03eb:2ff9) or you named the wrong target. Re-do the HWB/RESET sequence and confirm the ID before blaming the tool.

Five Pitfalls That Waste Your Afternoon

Every Retrode support thread is a rerun of the same handful of mistakes. Internalise these and you will skip the frustrated forum-searching phase entirely.

Dirty contacts and half-seated carts

Pitfall 1 — filthy edge connectors. This is the cause of the overwhelming majority of “bad dump” complaints. A cart that boots fine in a real console can still read poorly through the Retrode if the contacts are hazed, because the console has decades-old spring pressure the Retrode's fresh connector lacks. Fix: clean every cart with 99% isopropyl and a lint-free swab, let it dry, and re-seat firmly. Re-dump and re-checksum.

Pitfall 2 — the half-seated cartridge. A cart that is not fully home reads partial, mirrored, or truncated data, sometimes producing a plausible-looking-but-wrong file. Fix: push the cart in until it seats with the same firmness it has in the original hardware, then press RESET and re-check the file size.

Special-chip games that will not dump

Pitfall 3 — coprocessor carts. The Retrode cannot correctly dump SNES carts using the SA-1 or S-DD1 chips, nor Sega's SVP. That is a hardware/firmware limitation, not a technique problem, and no amount of contact-cleaning changes it. Fix: there is none via the stock Retrode — recognise these titles in advance and use a different dumper (such as a Sanni OSCR build) or source a verified dump for those specific games. Super FX and DSP-1 carts do dump fine, but need a coprocessor-aware emulator to run.

Chip	Example titles	Retrode dump?	Plays where?
Super FX / FX2	Star Fox, Yoshi's Island	Yes	Emulator/FPGA with Super FX support
DSP-1	Super Mario Kart, Pilotwings	Yes	Emulator/FPGA with DSP-1 support
SA-1	Super Mario RPG, Kirby Super Star	No	Use another dumper
S-DD1	Star Ocean, Street Fighter Alpha 2	No	Use another dumper
SVP (Sega)	Virtua Racing	No	Use another dumper

Saves, cables, and blind trust

Pitfall 4 — assuming saves are writable, or that they are not. The default sramReadonly value of 1 protects your saves, which surprises people trying to restore a backup (nothing happens). Conversely, leaving it at 0 while you fumble files is how saves get overwritten. Fix: flip sramReadonly deliberately — 0 only while writing, 1 the rest of the time.

Pitfall 5 — charge-only USB cables and blind trust in the dump. A power-only cable makes the Retrode appear to power on (LED lights) while never enumerating as a drive; and a dump you never checksummed is a dump you cannot trust. Fix: use a known data cable in a rear/motherboard USB port, and verify every ROM's hash against No-Intro before you consider it archived. A sixth honourable-mention pitfall: hot-swapping carts. Do not — eject first, every time, or risk the very saves you came to preserve.

Troubleshooting Table

When something goes wrong, work down this table before you post anywhere. Nearly every real-world Retrode failure is one of these twelve, and most resolve at the physical layer rather than the software one.

The table

Symptom	Likely cause	Fix
No RETRODE drive appears at all	Charge-only cable or dead port	Swap to a known data cable; use a rear USB port; try another OS to isolate
Drive mounts but no ROM file	Cart not seated, or inserted after mount	Re-seat the cart, press RESET (button 8) to re-scan
ROM file is tiny or zero bytes	Dirty or oxidised contacts	Clean with 99% isopropyl, dry, re-seat, re-dump
ROM dumps but checksum never matches	Partial seat, worn cart, or copier header expectation	Re-clean; confirm you are comparing to a headerless No-Intro entry
SNES special-chip game will not run	SA-1 or S-DD1 cart, unsupported	No fix on stock firmware; use another dumper for that title
.srm will not copy back onto the cart	sramReadonly is 1 (default)	Set sramReadonly 0 in RETRODE.CFG, then copy; set back to 1 after
Restored Sega save reads as garbage	16-bit-wide SRAM cart	Set segaSram16bit 1 and rewrite the save
Written save vanishes on power-off	Dead cartridge battery (CR2032)	Read SRAM out, replace the coin cell, write the save back
Game Gear cart not recognised	Older firmware detection bug	Set forceSystem GG, or flash 0.18d beta 3
Master System filename is blank	SMS header has no title field	Expected behaviour — rename the file manually after copying
SNES mouse not detected	Plugged into the right port	Move the mouse to the LEFT controller port
Firmware flash fails	Device not actually in DFU / wrong target	Re-run HWB+RESET, confirm ID 03eb:2ff9, target at90usb646

When to suspect the cart, not the Retrode

If one specific game misbehaves while everything else dumps perfectly, the Retrode is fine and the cartridge is the variable. Corroded contacts, a cracked trace, or a battery that has leaked onto the board all produce game-specific failures. Clean it, inspect it under magnification, and compare against a known-good copy of the same title if you have one.

When to suspect the USB stack

If every cart fails identically, or the drive comes and goes, the fault is upstream: the cable, the port, a flaky hub, or an aggressive USB power-saving setting. Plug the Retrode directly into a rear motherboard port, never through an unpowered hub, and disable USB selective suspend on Windows. A composite USB device from 2011 does not love modern power management.

Advanced Tips and the Legal Line

Once the basics are automatic, a few habits separate a pile of files from an actual archive — and one section of this hobby that people would rather ignore deserves a plain statement.

Checksums, No-Intro, and headerless dumps

Verification is the difference between hoarding and preserving. The Retrode produces headerless SNES dumps, which is the correct, database-matching format — you do not want the 512-byte copier headers that old SNES backup units added. Hash each dump and look it up. A tiny reproducible workflow:

$ sha1sum "SUPER METROID.sfc"
c9c2...redacted...e41  SUPER METROID.sfc

# Look that SHA-1 up in a No-Intro DAT. A match = a clean, headerless dump.
# A mismatch = dirty contacts, a worn cart, or a stray header. Re-dump.

Do not skip this because a dump “looks fine.” A single flipped bit from a marginal contact will boot and play for hours before it corrupts a save or crashes in a late level, and by then you will have archived the bad copy over the good one.

Loading dumps into RetroArch, FPGA, and handhelds

A verified dump is portable across the entire modern retro stack, which is the payoff for doing it yourself. The files load into a properly configured RetroArch install, into a full-fat box running Batocera or RetroPie on a Raspberry Pi, into cycle-accurate FPGA hardware, and onto pocket emulators like those covered in our Miyoo Mini Plus library breakdown. Because you dumped and verified them, you know they are correct going in — which is more than can be said for most files that circulate.

The legal reality of dumping your own carts

Here is the part the marketing copy skips. Dumping a cartridge you physically own, for your own use, is a defensible personal-backup use in many jurisdictions — but it is not the clean, settled right the internet pretends it is. In the United States, DMCA §1201 anti-circumvention rules muddy format-shifting, and the moment you distribute a ROM you have committed straightforward copyright infringement regardless of whether you own the cart. The Machine is not your lawyer and this is not legal advice. The practical, defensible line is simple: dump only carts you own, keep the files to yourself, and treat the Retrode as a preservation and personal-backup tool rather than a distribution pipeline. That is both the ethical position and the one least likely to generate a letter.

Retrode 3: The Long Wait

Now the vaporware, which is more interesting than vaporware usually is. If you came here searching for 2026 Retrode news, this is the entirety of it, and it is thin: the Retrode 3 exists as hardware and does not exist as a product.

What is confirmed, and what is not

As of 15 July 2026 the Retrode 3 is not for sale. The target is “end of 2026,” the price is “under €100” (roughly $108), and neither is confirmed — no firm date, no final price, no version number, because you cannot version a product that has not shipped. The only thing you can do today is leave your email on a “notify me” pre-registration at the DragonBox partner store; the official site cannot take orders. Every other outlet — Polygon, Ars Technica, Engadget, Eurogamer — has published nothing on it, because there is nothing to review. Anyone quoting a Retrode 3 release date as fact is guessing.

The OSCR and Sanni lineage

The architecture is a genuine departure from the AVR-based Retrode 2. The Retrode 3 is a small Linux computer: a MIPS processor running Debian with built-in Wi-Fi, fully open-source in hardware and software, made in Germany, and “practically unbrickable” because the OS lives on an SD card you can simply re-flash. Instead of mounting as a mass-storage drive, it registers as a USB-Ethernet device and serves a web interface — you dump carts, back up SRAM, and even write flash carts from a browser tab, no drivers on any OS. It slots SNES/SFC, Mega Drive/Genesis, and — new for this generation — NES. Under the hood it is built on Sanni's Open Source Cartridge Reader, adapted into a Linux CLI (a C++ codebase, GPLv3 software with CC-licensed hardware and docs), and the plug-in logic is cross-compatible with the upstream Cart Reader project in both directions. DragonBox has said publicly there are “10 fully working prototypes” and that they are “looking for developers,” which tells you exactly where the bottleneck is: not the silicon, the software.

Should you wait?

No. If you have cartridges to dump in 2026, the Retrode 2 does the job today, and “end of year” targets on open-source hardware projects have a way of becoming next year. If the Retrode 3 ships on time, is genuinely under €100, and delivers the browser-based NES-plus-SNES-plus-Genesis workflow it promises, it will be the obvious recommendation — a driverless, unbrickable, region-free reader for three console families is a real upgrade. But recommend the hardware you can hold. Right now that is the Retrode 2, and it will keep working long after this article is stale.

A Complete Working Configuration

To close, here is a complete, annotated setup you can lift wholesale: the config file, a batch dump-and-verify script, and a final checklist. Treat the config keys as illustrative of the format — confirm exact behaviour against the official user guide, since the Retrode's own documentation is the authority and some keys behave subtly differently across firmware builds.

The RETRODE.CFG (illustrative)

This lives at the root of the RETRODE drive. Blank values mean “let the firmware auto-detect,” which is what you want almost everywhere. The two keys you will actually change are sramReadonly (to write saves) and, for stubborn Sega carts, segaSram16bit.

# RETRODE.CFG  —  illustrative; confirm keys against the user guide.
# Config support added in firmware 0.17g. Blank = firmware auto-detects.

sramReadonly   1        # 1 = protect on-cart saves (default). 0 = allow WRITING saves.
forceSystem             # blank = auto. e.g. GG to force Game Gear detection.
forceSize               # blank = auto. Override dump size only if detection is wrong.
forceMapper             # blank = auto. SNES mapper hint (LoROM / HiROM).
snesRomExt     sfc      # extension for SNES / Super Famicom dumps.
segaRomExt     bin      # extension for Mega Drive / Genesis dumps.
sramExt        srm      # extension for save (SRAM) files.
segaSram16bit  0        # 1 for Sega carts with 16-bit-wide SRAM.
detectionDelay          # blank = default. Raise if a cart mounts before it settles.
filenameChksum 0        # 1 appends a checksum to each filename.

A dump-and-verify shell script

For dumping a shelf of carts, this POSIX script copies every ROM and save off the drive and hashes the ROMs so you can diff them against a No-Intro DAT afterward. It deliberately skips the config file and leaves the originals untouched.

#!/bin/sh
# dump-verify.sh — copy every ROM/save off the Retrode and hash it.
SRC="/media/$USER/RETRODE"
DEST="$HOME/roms/incoming"
mkdir -p "$DEST"

# Copy SNES (.sfc), Sega (.bin) and saves (.srm); skip RETRODE.CFG.
for f in "$SRC"/*.sfc "$SRC"/*.bin "$SRC"/*.srm; do
  [ -e "$f" ] || continue
  cp -v "$f" "$DEST/"
done

# Hash the ROMs so you can check them against a No-Intro DAT later.
cd "$DEST" && sha1sum *.sfc *.bin 2>/dev/null
echo "Done. Verify the SHA-1s above before you call this an archive."

The final checklist

Print this, or memorise it. It is the whole tutorial compressed into the order you actually perform it.

• Clean the cartridge contacts with 99% isopropyl and let them dry.
• Connect the Retrode with a data USB cable and confirm the RETRODE drive mounts.
• Insert the cart squarely in the correct slot; press RESET to scan.
• Verify size — the ROM file should match the game's known megabit count.
• Copy the ROM and any .srm off to real disk; never edit in place.
• Checksum each ROM with sha1sum and match it against No-Intro.
• Restore saves only with sramReadonly set to 0, then set it back to 1.
• Eject before swapping carts — never hot-swap a save-bearing cartridge.
• Back up to at least two separate media before you call it archived.

That is the Retrode: a decade-old, feature-frozen, thoroughly documented box that quietly does exactly one job well while its successor spends another year in prototype. For the authoritative details, go to the source — the official Retrode site and its FAQ, the full user-guide text on the Internet Archive, the Wikipedia entry for the AT90USB646 hardware history, and, for the future, the open-source repositories at DragonBox-Shop/retrode3-oscr and upstream Sanni Cart Reader. Read the primary sources, dump only what you own, and verify everything.