Use standard SATA drives in your RDX dock.
Important
OpenRDX is not limited to RDX cartridges. It also supports compatible, unlocked standard SATA drives in the supported RDX dock, while retaining RDX cartridge support.
Compatibility is guarded, but not every disk is promised to work. See the current validation boundary.
OpenRDX is firmware for the Tandberg Data RDX QuikStor external USB 3.0 compatibility receiver. It keeps the familiar removable-drive experience while opening the dock to qualifying standard SATA media.
Why OpenRDX
| Flexible media | Familiar operation | Guarded access |
|---|---|---|
| Use supported RDX cartridges or qualifying standard SATA drives. | Keep one removable USB drive, safe eject behavior, and RDX cartridge write protection. | Media must pass admission checks before it becomes available to the host. |
Choose your media
| Media | What OpenRDX provides | What to expect |
|---|---|---|
| RDX cartridge | The cartridge workflow, identity, protected data area, and supported management features. | A cartridge must retain valid identifying information and pass its access checks. |
| Standard SATA drive | Direct access to the drive's native capacity after guarded admission. | The drive must be compatible and unlocked. Support is not a guarantee for every HDD or SSD. |
Both paths appear through the same stable removable USB drive. An empty bay or rejected medium stays safely unavailable instead of being silently accepted. For everyday operation, media rejection, ejection, and write protection, read Using OpenRDX.
Supported hardware
OpenRDX currently targets one receiver family only:
- Tandberg Data RDX QuikStor external USB 3.0 compatibility receiver;
- built around the Texas Instruments TUSB9261; and
- identified before installation by preinstalled vendor firmware revision
0283.
After installation, OpenRDX reports receiver revision 0001 instead.
Support for other RDX docks, bridge chips, or receiver revisions is not implied.
Experimental status
OpenRDX is experimental and incomplete. Hardware validation and compatibility coverage are limited, and unknown issues may affect normal operation with RDX cartridges or standard SATA drives. Full reliability and complete RDX Manager compatibility are not yet established.
See Firmware behavior for detailed evidence, known limitations, and remaining validation work.
Get started
Install OpenRDX
Use a newly generated, complete, verified release bundle and follow the
guarded installation guide. The
checked-in dist/ directory is a historical snapshot, not a verified release
for current main.
Git preserves the exact bytes of generated dist/ files so release checksums
remain valid across checkout platforms and source archives.
Firmware installation changes the receiver and requires Windows, stable USB power, an empty bay, and careful target selection. Read the safety procedure in full before starting.
For a receiver already running OpenRDX, follow Update existing OpenRDX.
Build from source
Maintainers can start with the common build and test guide.
Documentation
- Documentation index — choose the authoritative guide for installation, use, development, or reference.
- Using OpenRDX — media, write protection, ejection, and supported management behavior.
- Install OpenRDX — guarded update workflow for the supported receiver.
- Build and test — supported toolchains, commands, and artifact roles.
- Release process — generate and verify a complete release bundle.
- Firmware recovery — recovery and restoration instructions.
- Firmware behavior — implementation detail and the hardware-validation boundary.
License
OpenRDX was created by André Fiedler / aka SunboX.
Repository-owned OpenRDX software is offered under
AGPL-3.0-or-later. OpenRDX documentation and non-code media are offered under
CC-BY-SA-4.0 where identified by .reuse/dep5. Texas Instruments material and
third-party documentation retain their own notices and terms.
The public license does not grant permission for use that cannot comply with its
terms. A separate commercial or proprietary license may be available from the
copyright holder. See LICENSE,
COMMERCIAL-LICENSE.md, and NOTICE.