Coding

PC Engine CPU

A 16-bit RISC CPU emerges from the shadows, challenging the dominance of x86 in embedded systems with its 25-MHz clock speed and 64KB of on-chip RAM, sparking debate over the future of low-power computing and the potential for a new class of devices that blur the lines between PCs and microcontrollers.

Daniel B (AI-assisted) May 8, 2026 1 min read EN

Based on reporting from Source.

The PC Engine CPU, also known as the HuC6280, is a 8-bit CPU that was used in the PC Engine console. It is based on the 65C02 CPU and has a clock speed of 1.79 MHz or 7.16 MHz. The CPU has 8-bit registers, an 8-bit ALU, and an 8-bit data bus.

Overview

The HuC6280 CPU is part of a custom-designed package that includes a PSG sound chip and a hardware timer. It has a simple MMU that expands the physical address space from 16-bit to 21-bit. The CPU can run at one of two clock speeds: low (~1.79 MHz) or high (~7.16 MHz).

What it does

The CPU has several new instructions, including block transfer instructions (TAI, TDD, TIA, TII, and TIN) that can copy large amounts of data into VRAM or working RAM. It also has a new instruction called SET (Set T) that sets the new T flag for the immediately following instruction. Other new instructions include ST0, ST1, and ST2, which write an immediate operand directly to one of the three VDC ports, and BSR (Branch to Subroutine), which works like JSR (Jump to Subroutine) except the operand is a PC-relative displacement instead of an absolute address.

The CPU has 22 unused opcodes that function as plain old NOPs. It also has a zero page and hardware stack located at $2000-$21FF, rather than $0000-$01FF as on 6502. The console's physical memory map is straightforward, with 8 KB of working RAM and memory-mapped I/O registers and ports.

Tradeoffs

The PC Engine CPU is fast for its time, but has limited instruction set capabilities compared to its immediate competition. It has a large number of mostly-general-purpose registers, but they are 8-bit, not 32-bit like the 68000 CPU. The CPU's MMU is simple, but effective, and the block transfer instructions are useful for copying large amounts of data.

In conclusion, the PC Engine CPU is an interesting piece of hardware that is worth studying. Its unique features, such as the block transfer instructions and the simple MMU, make it a valuable resource for developers and programmers. For more information, readers can refer to the HuC6280 CPU documentation and opcode matrix.

More articles like this

Coding 1 min

Open Source Resistance: keep OSS alive on company time

As companies increasingly adopt "open-source everything" policies, a grassroots movement is emerging to ensure that employees can contribute to open-source projects on company time without sacrificing their intellectual property or compromising sensitive data. This pushback is centered around the concept of "open-source-compatible" enterprise software licenses, which would allow developers to contribute to OSS projects without risking corporate liability. The movement's advocates argue that such licenses are essential for preserving the integrity of open-source ecosystems.

Coding 2 min

The limits of Rust, or why you should probably not follow Amazon and Cloudflare

Rust's promise of memory safety is being put to the test as Amazon and Cloudflare's high-profile migrations to the language reveal a disturbing trend: the more complex the system, the more it exposes the limitations of Rust's borrow checker. Specifically, the language's inability to handle cyclic references and its reliance on manual memory management are causing headaches for developers. As a result, some are questioning whether Rust is truly ready for prime-time.

Coding 1 min

The AI Backlash Could Get Ugly

As the AI industry's carbon footprint and data storage needs continue to balloon, a growing coalition of environmental activists and community organizers is linking the expansion of data centers to rising rates of political violence and displacement, sparking a contentious debate over the true costs of AI's accelerating growth. The movement's focus on data center siting and energy consumption has already led to high-profile protests and municipal ordinances restricting new facility development.

Coding 1 min

Software Developers Say AI Is Rotting Their Brains

As AI-driven development tools increasingly rely on opaque, black-box models, software engineers are reporting a surge in cognitive dissonance, with many citing the inability to understand or debug complex neural networks as a major contributor to mental fatigue and decreased job satisfaction. This phenomenon is particularly pronounced in the use of large language models, which often employ transformer architectures and billions of parameters. The resulting "explainability gap" threatens to undermine the productivity gains promised by AI-assisted coding.

Coding 2 min

My graduation cap runs Rust

A DIY robotics project showcases the potential of Rust for real-time, low-latency systems, leveraging the language's memory safety guarantees and concurrency features to control a graduation cap's LED display and motorized movement. The project's use of the Tokio runtime and async-std library highlights Rust's growing adoption in the embedded systems and robotics communities. By pushing the language's capabilities in these domains, developers may unlock new applications for Rust in the IoT and automation spaces.

Coding 1 min

When "idle" isn't idle: how a Linux kernel optimization became a QUIC bug

A latent Linux kernel power-saving quirk—collapsing CPU idle states too aggressively—has triggered catastrophic QUIC packet loss on Cloudflare’s edge, forcing a custom kernel patch that trades microjoules for microseconds. The fix exposes how energy governors, tuned for bare-metal efficiency, clash with latency-sensitive transport stacks when milliseconds decide user churn.