How the Commodore Plus/4 Managed System Clock and Timing
The Commodore Plus/4 utilized a unique architecture centered around the TED chip to handle system timing, diverging from the dual-CIA setup of the Commodore 64. This article explores the hardware foundation, clock signal division, and integrated timer mechanisms that governed the Plus/4’s operations. Readers will learn about the crystal oscillator frequencies, the role of the MOS 7501 and 8501 CPUs, and how software interrupts leveraged these hardware components for precise execution.
The TED Chip Architecture
At the heart of the Plus/4’s timing management was the TED (Text Editing Device) chip, specifically the MOS 7360 for NTSC systems and the MOS 8360 for PAL systems. Unlike its predecessor, the Commodore 64, which relied heavily on two 6526 Complex Interface Adapter (CIA) chips for input/output and timing, the Plus/4 integrated many of these functions directly into the TED chip. This integration was a cost-saving measure that fundamentally changed how the system managed clocks and intervals. The TED chip handled video generation, sound, and crucially, system timing registers, consolidating responsibilities that were previously spread across multiple integrated circuits.
Crystal Oscillator and Frequency Division
The system clock originated from a crystal oscillator connected to the TED chip. In NTSC machines, this crystal operated at approximately 17.734470 MHz, while PAL machines used a crystal running at 17.734475 MHz. This high-frequency signal was the master pulse for the entire system. The TED chip was responsible for dividing this master clock to generate the various frequencies required by different components. The CPU, either the MOS 7501 or 8501, received a clock signal derived by dividing the master crystal frequency by ten. This resulted in a CPU clock speed of approximately 1.77 MHz, which dictated the instruction execution rate for the processor.
Integrated Timers Within the TED
A distinct feature of the Plus/4’s timing management was the presence of two 16-bit timers built directly into the TED chip. In the Commodore 64, developers relied on the timers found within the CIA chips for tasks such as generating interrupts, measuring intervals, or driving peripherals. On the Plus/4, with only one CIA chip present for keyboard and serial port management, the TED’s internal timers became essential for system operations. These timers could be programmed to count down from a specific value and generate an interrupt request (IRQ) when they reached zero. This allowed the operating system and applications to maintain accurate timekeeping and schedule tasks without overburdening the single remaining CIA chip.
Interrupts and Raster Timing
System timing was closely tied to the interrupt structure of the machine. The Plus/4 supported standard IRQ and Non-Maskable Interrupt (NMI) lines. The TED chip could generate interrupts based on its internal timers or video beam positions, known as raster interrupts. Raster interrupts were vital for developers who needed to synchronize code execution with the television screen’s refresh cycle. By leveraging the timing signals from the TED, programmers could change colors, update sprites, or modify memory at precise moments during the video frame draw. This synchronization ensured that visual updates occurred without tearing or flickering, relying on the stable clock division provided by the main hardware architecture.
Software Implications and Kernal Routines
The Commodore Kernal, the system’s built-in operating system, utilized these hardware timers to maintain the system clock visible to the user. A specific timer interrupt would trigger periodically, usually 60 times per second on NTSC systems, to increment the internal clock counters stored in RAM. Software developers accessing the system through BASIC or machine language had to be aware of the single CIA limitation. While the Kernal abstracted much of this complexity, direct hardware manipulation required careful management of the TED’s timer registers. Mismanagement could lead to drift in timekeeping routines or conflicts with video generation, as the TED chip was multitasking both display timing and system interval counting simultaneously.
Legacy of the Timing Design
The timing management of the Commodore Plus/4 represents a specific moment in home computer evolution where integration began to trump expandability. By moving timers into the video chip, Commodore reduced the component count and cost, but it also created a unique environment for programmers accustomed to the C64’s architecture. The reliance on the TED chip for clock stability and interrupt generation ensured that the system remained coherent despite the reduced hardware footprint. Understanding this flow from crystal oscillator to CPU cycle and interrupt request provides insight into how the Plus/4 maintained operational rhythm during its commercial lifespan.