TRX64

TRX64 is a cycle-accurate Commodore emulator runtime with an unusually deep reverse-engineering toolkit. It is best for developers and experienced C64 investigators who need inspectable execution, programmable control, or repeatable debugging. The main tradeoff is clear: powerful instrumentation comes with ROM setup work and little formal support.

Overview

TRX64 emulates the Commodore 64, 1541 and 1581 in Rust, but its purpose extends beyond running disk images. A daemon exposes every documented capability through JSON-RPC 2.0 over WebSocket, making the runtime a practical backend for custom tools and services. Users can also work through trx64cli, a terminal cockpit with an optional native emulator window, or C64RE, a browser-based reverse-engineering workbench. That range suits technical users who want to choose their interface; it is less appropriate for anyone expecting a single polished desktop application.

The daemon offers c64, u64 and 128 machine selections, including documented PAL and NTSC C64 models. Media support covers D64 and G64 disks in 1541 drives, D81 disks in 1581 drives, multiple cartridge types, REU, GeoRAM and the Ultimate Command Interface. Snapshot and investigation workflows can use .c64re machine snapshots, .c64rering reverse-debug buffers and .c64retrace trace logs, with conversion from VICE .vsf snapshots.

Key features

Reverse debugging

Rewind and byte-exact reverse stepping let an investigator move backward to the precise state that matters, rather than merely restarting a run. Write tracking, observers, traces and marks expose how execution changes memory and behavior, while sandboxes provide a way to isolate investigative work. This is the strongest reason to choose TRX64 over a conventional emulator: it is designed for reconstructing program behavior, not just displaying it.

Programmable runtime

The WebSocket JSON-RPC interface makes the emulator controllable from external software, and the project describes each capability as having a JSON-RPC method. That is valuable when a team is building an analysis workflow or integrating emulation into another application. A typed UniFFI library with Swift bindings extends that integration path, while TRX64 is described as the runtime backend for C64RE and the C64U / UE2 Emulator.

Hardware and compatibility coverage

Support for 1541 and 1581 disk formats, cartridges, REU, GeoRAM and the Ultimate Command Interface gives preservation and reverse-engineering projects more room than a minimal C64 core. The documented C64, C128, Ultimate 64, Elite II and C64 Ultimate selections address several related machine targets. Prebuilt release assets cover Linux, macOS and Windows, including x86_64 and arm64 builds where provided; Homebrew installation and a cargo build --release source route offer additional deployment choices.

Pricing

TRX64 has one plan: Free and open source at free, under GPL-3.0-or-later. There is no paid tier, subscription renewal or trial period to manage. The free plan is therefore suitable for personal investigation, development and projects able to comply with the license. It does not bundle the C64 ROMs, so users must supply their own files rather than treating the zero price as a complete turnkey package.

Platforms

The published platform list covers Windows, macOS and Linux, with releases offering x86_64 and arm64 assets where listed. TRX64 also exposes an API and supports self-hosted deployment, so it can serve as a runtime behind other software rather than only as a local interface. The documented installation paths are Homebrew or building from source with Cargo.

Who it's for

Choose TRX64 if you are reverse-engineering C64 software, building an emulator-driven tool, or need deterministic inspection with rewind and trace artifacts. It is also a strong fit for contributors comfortable with an open-source Rust project and for developers targeting Swift through UniFFI. Look elsewhere if you want ROMs included, a conventional ready-to-run desktop package, or dependable vendor assistance: the maker directs users to GitHub issues and says real support cannot be provided.

Pros and cons

Pros

• Byte-exact reverse stepping and rewind: lets investigators examine earlier execution states precisely.
• Broad inspection toolkit: write tracking, observers, traces, marks and sandboxes support different analysis methods.
• API-first design: JSON-RPC over WebSocket and Swift bindings make custom integrations practical.
• Wide C64 ecosystem support: multiple machine selections, disk formats, cartridges and expansion hardware cover serious compatibility work.
• Open-source and free: GPL-3.0-or-later licensing removes purchase cost and permits code contributions.

Cons

• ROMs are your responsibility: C64 ROMs and the 1581 DOS ROM are excluded and must be supplied from ~/.trx64/roms or with --rom-dir.
• Technical setup: users may need Homebrew or a source build, and the tool's multiple interfaces favor experienced operators.
• Limited support commitment: issue-based help and the stated lack of real support may be unsuitable for production-critical users.

Alternatives

For a broader emulator directory, browse Commodore 64 Emulators. Pick VICE instead if you want free GNU GPL software with Android support as well as Linux, macOS and Windows. Breadbin466 is another free Linux, macOS and Windows option under the MIT license, though its Commodore ROM images are not covered by that license. Buddi is budgeting software rather than an emulator. Frodo is a free Linux, macOS and Windows alternative. Choose VirtualC64 for a free, open-source option on macOS and the web. Atari 5200DS targets Atari 5200 emulation instead. C64 Forever offers a free Windows Express Edition within a freemium product. Hoxs64 is a free Windows-only alternative.

Verdict

TRX64 is the right choice for developers and serious C64 reverse-engineering work who value cycle accuracy, programmable control and reversible debugging. Choose it for the depth of its inspection and integration tools; look elsewhere if supplying ROMs, handling a technical runtime and relying mainly on community issue tracking are unacceptable.