Skip to content

OpenRDX v1.11

Latest

Choose a tag to compare

@SunboX SunboX released this 10 Oct 11:00
· 4 commits to main since this release

OpenRDX 1.11 fixes cartridge capacity reporting, failed-command USB cleanup,
and the manufacturing-write safety lock at boot.

  • Preserves the admitted RDX data-area capacity and translation offset when a
    host queries cache settings. Runtime IDENTIFY refreshes update only the cache
    bits under the existing media-epoch and ATA ownership guards, preventing a
    capacity increase that could cause end-of-disk reads or formatting to fail.
  • Avoids counting completed USB OUT bytes twice during failed SCSI command
    cleanup. Regression coverage includes completed, partial, active, and repeated
    cleanup.
  • Explicitly initializes the manufacturing-write safety lock at boot for the
    TI ARM9 COFF runtime. A real manufacturing mutation still locks further
    changes and firmware updates until restart.
  • Supports the reduced SCons environment used by the Windows PlatformIO build
    and documents the preceding native Windows update and readback checks.

Manufacturing backup and restore, serial repair, and firmware-update preservation
from 1.10 remain available. Use a compatible OpenRDXManager and keep a backup of
the receiver's manufacturing data outside the dock before updating.

Supported hardware remains the Tandberg Data RDX QuikStor external USB 3.0
TUSB9261 compatibility receiver identified by receiver identifier 0283.

This release remains experimental. Automated regression tests and the supported
Windows TI ARM CGT 5.2.5 release gate cover the source and installation bundle.
Preceding 1.10 candidates completed normal Manager updates with independent
complete SPI comparisons on one selected Windows receiver. Read-only checks on
that receiver and one 3 TB cartridge confirmed stable capacity across cache
queries and readable end sectors. Those results apply to the exact candidate
images recorded in the verification report; the versioned 1.11 image has not
been physically validated. Successful hardware formatting, macOS updates,
other receivers, manufacturing restore, and power-loss recovery remain unverified.

See the installation guide,
recovery guide, and
native Windows verification report.

Download the complete installation bundle and verify it against SHA256SUMS from this release.