

Control
Homebrew TTL ISA-compatible PDP-9 clone
- Size
- 206.4 × 137.5 mm
- Copper layers
- 2
- Thickness
- 1.6 mm
- Parts
- 67
- Nets
- 244
- Pads
- 720
- Tracks, vias
- 3,282, 79
- Pours
- 1
- Routed
- Yes
- KiCad
- KiCad 7 (file 20221018)
- Created
- 18 Apr 2025
- Updated
- 6 Oct 2026
Overview
Control is an open-source printed circuit board by tergav17, from the tergav17/RDP-9 repository on GitHub. It is a 2-layer board of 206.4 × 137.5 mm with 67 parts on 244 nets, routed with 3,282 tracks and 79 vias.
It is built around the 74LS253DC, 74LS377PC and 74LS257PC, with the 74LS273PC, 74LS32SC and 74LS74PC among its other parts. Its parts include 27 capacitors, 26 ICs, 11 resistors and 3 connectors.
Main components
774LS253DC
CDIP-160℃~+70℃ 35ns 35ns 35ns 4.75V~5.25V 4:1 CDIP-16 Analog Switches, Multiplexers ROHSTexas InstrumentsAnalog Switches, Multiplexers74LS377PC
PDIP-200℃~+70℃ 1 10ns 25ns@5V,15pF 28mA 30MHz 4.75V~5.25V 400uA 5ns 74LS Series 8 8mA D-Type Rising Edge Synchronous PDIP-20 Flip Flops ROHSTexas InstrumentsFlip Flops74LS257PC
DIP-160℃~+70℃ 12mA 2.6mA 24mA 27ns@5V,150pF 4.75V~5.25V 74LS Output enable high-impedance、Tri-state output DIP-16 Signal Switches, Multiplexers, DecodersTexas InstrumentsSignal Switches, Multiplexers, Decoders74LS273PC
PDIP-201 15ns 27mA 27ns@5V,15pF 30MHz 5ns 74LS Series 8 D-Type Reset Rising Edge PDIP-20 Flip Flops ROHSonsemiFlip Flops74LS32SC
-- Logic Gates ROHSTexas InstrumentsLogic Gates74LS74PC
DIP-140ns 0℃~+70℃ 1 2 20MHz 3.5pF 35ns@5V,50pF 4.5ns 4.75V~5.25V 400uA 74LS Series 8mA 8mA Asynchronous Complementary D-Type Rising Edge Set and Reset DIP-14 Flip FlopsTexas InstrumentsFlip Flops74LS86
DIP-14-20℃~+75℃ 10mA 2.7V 23ns@5V,15pF 2V 400mV 400uA 5V 74LS 800mV 8mA XOR Gate DIP-14 Logic Gates ROHSHITLogic Gates
README
README.mdRDP-9
Project Description
This project aims to build an ISA-compatible clone of the DEC PDP-9 system using primarily technology from the late 1970s - early 1980s period. I did this to ensure my design followed the same constraints that later genuine minicomputer systems were built with, while being able to significantly reduce the size and complexity compared to an actual PDP-9. The specifics are as follows
- Use only 74-series logic and other similar TTL logic level parts that would be available around the later 1970s timeframe. The exception to this is RAM, which I plan to use more “modern” SRAM chips instead of torturing myself with dynamic RAM.
- No FPGAs, PALs, GALs, microcontrollers, etc in the main processor path. The only exception to this is using standard 27C style ROM chips to hold the microcode.
- Usage of a period correct microcontroller or microprocessor for the disk / drum subsystem. Using another simpler processor to control complex devices like disks was done frequently on other minicomputer designs, so I’ll be doing it here too.
My end goal is to build a system that is capable of running most of the interesting software of the period. This includes DECsys, ADSS, DOS-15, and UNIX V0. To do this, the system will need:
- Full compatibility with the PDP-9 instruction set. This includes EAE instructions and extended memory
- The ability to hook up to a real or emulated paper tape punch / reader.
- The ability to hook up to a real or emulated ASR-33 teletype or similar serial terminal
- 8" floppy drive interface in place of DECtape. Software will require patching but it's better than trying to emulate DECtape
- IDE hard drive support using RB09/RF09 interface
Theory of Operation
Due to the complexity involved with the architecture of the DEC PDP-9, the system is split into two subsystems:
The first subsystem is the processor itself. It has a full 18-bit datapath with 15-bit address bus, and is implemented entirely using TTL logic.
The second subsystem is the I/O bus. This is directly controlled by the processor itself and is capable of servicing the following operations:
- Device interrupts
- IOT transactions
- Add-to-memory operations
- Data channel transfers
- DMA transfers
- READ-IN operation
Device Interrupts
Device interrupts simply tell the processor to begin an interrupt operation. When an interrupt is accepted, the I/O bus will be notified of the action and is responsible for turning off the "Program Interrupt" flag. If this does not happen, interrupts will continuously loop.
Steps:
-
Interrupt is accepted. MA is completely zeroed and the "INTERRUPT_DETECT" pulse is asserted for this clock cycle.
-
PC is stored in MB, OB
-
The logical OR of MB and OB is place in CORE at MA. The crossbar will add the LINK and MEMM flags
-
MA + 1 is placed in the PC. Extend is enabled to ensure that bank 0 is selected. The next fetch will ignore device requests
IOT Transactions
IOT transactions allow data to be transferred to or from the accumulator. IOTs also allow for skips to be requested. Every IOT is treated by the CPU as a Read-Modify-Write operation. By using the "EXTRN" signal, devices can notify the processor to read from the I/O bus instead of the writeback register. When the I/O bus is being sampled, the "IOT_SKIP" signal can be asserted to tell the processor to perform an addition increment of the program counter.
A wait signal is sampled at the beginning of the IOT as well. This can be used to add cycles to the writeback phase of the IOT if the device needs it.
Steps:
-
IOT transaction begins. Device address is placed on the I/O address bus. AC (or 0 if the flag is set) is written to the WRTBK register.
-
Signal "IOT_PULSE" is asserted.
-
Signal "IOT_PULSE" remains asserted. External input is sampled into MB. Signal "EXTRN" must be asserted to take value from device bus.
-
IF "IOT_WAIT" is asserted, goto step 3 in place. No IOT signals are asserted. Interally, the CPU is performing the logical OR and writeback of potential provided data.
-
No IOT signals are asserted. Internally, the CPU will perform the skip here if it has been requested. The next fetch cycle will ignore interrupts and device requests.
Device Requests
The final three transaction types (Add-to-memory, data-channels, and DMA transfers all share the "device request" pathway.
Steps:
-
Signal "REQ_ADDR_PHASE" and "DEV_REQ_GRANT" asserted and held. External value written to MA.
-
If DMA is selected, core is read at MA and written to WRTBK with next as step 8. Otherwise core is read at MA and written to MB, OB. "REQ_ADDR_PHASE" held
-
Value in MB, OB incremented and written back to core at MA and OB. "REQ_ADDR_PHASE" held
-
Value in MA incremented. If add to memory selected, Jump to fetch without device request logic. "INCREMENT_ZERO_PUSLE" will be generated if needed. "REQ_ADDR_PHASE" held
-
Core is read at MA and written to MB, OB.
-
Value in MB, OB incremented and written back to core at MA and MA
-
Core is read at MA and written to WRTBK
-
External value written to core at MA. "DEV_REQ_GRANT" reset. Jump to fetch without device request logic
READ-IN Operation
The read-in is used to transfer a set series of words into memory from one of the I/O devices. Only one I/O device can be be allowed to respond to READ-IN at any one time. When a READ-IN transaction is active, the CPU will stall until the designated device signals that it is ready. The device will either signal the CPU to commence another READ-IN cycle, or to terminate the READ-IN after any given transfer.
Steps:
-
SWR is moved into PC
-
"READ_IN_PULSE" is asserted, step will loop till either "IOT_WAIT" or "IOT_SKIP" are asserted.
-
"READ_IN_PULSE" remains asserted. EXTRN is moved into core at PC. Continue having the constant value asserted.
-
"READ_IN_PULSE" reset. If "IOT_SKIP" is asserted, jump to CONT logic. Otherwise move PC + 1 into PC
-
Null phase, "READ_IN_PULSE" remains reset.
-
Null phase, "READ_IN_PULSE" remains reset. Jump to step 2 on completion
Parts
67| Qty | Value | Footprint | References |
|---|---|---|---|
| 26 | 0.1uF | Capacitor_THT:C_Disc_D5.0mm_W2.5mm_P5.00mm | C1, C2, C10, C11, C12, C13, C14, C15, C16, C17, C18, C19, C20, C21, C22, C23 +10 |
| 11 | 4.7K | Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P7.62mm_Horizontal | R1, R2, R3, R4, R5, R6, R7, R8, R9, R10, R11 |
| 7 | 74LS253 | Package_DIP:DIP-16_W7.62mm | U11, U12, U13, U14, U15, U16, U17 |
| 7 | 74LS377 | Package_DIP:DIP-20_W7.62mm | U7, U8, U9, U10, U19, U20, U21 |
| 5 | 27C64 | Package_DIP:DIP-28_W15.24mm | U1, U2, U3, U4, U5 |
| 1 | 100 uF | Capacitor_THT:CP_Radial_D6.3mm_P2.50mm | C27 |
| 1 | 74LS08 | Package_DIP:DIP-14_W7.62mm | U24 |
| 1 | 74LS138 | Package_DIP:DIP-16_W7.62mm | U22 |
| 1 | 74LS257 | Package_DIP:DIP-16_W7.62mm | U18 |
| 1 | 74LS273 | Package_DIP:DIP-20_W7.62mm | U6 |
| 1 | 74LS32 | Package_DIP:DIP-14_W7.62mm | U23 |
| 1 | 74LS74 | Package_DIP:DIP-14_W7.62mm | U26 |
| 1 | 74LS86 | Package_DIP:DIP-14_W7.62mm | U25 |
| 1 | Control Connector | Connector_DIN:DIN41612_B_2x32_Male_Horizontal_THT | J1 |
| 1 | Data Connector | Connector_DIN:DIN41612_B_2x32_Male_Horizontal_THT | J2 |
| 1 | State Debug | Connector_IDC:IDC-Header_2x06_P2.54mm_Horizontal | J3 |
More from tergav17/RDP-9
7- 2 layers200 × 321.3 mm

- 2 layers204.5 × 107.3 mm

- 2 layers235 × 137.5 mm

- 2 layers170.2 × 107.3 mm

- 2 layers206.4 × 137.5 mm

- 2 layers206.4 × 137.5 mm

- 2 layers206.4 × 137.5 mm

Similar boards
- 2 layers236.8 × 169.8 mm

TK2000
clemarfolly/Microdigital-TK2000
Reprodução da PCB do TK-2000 da Microdigital, clone do Micro-Professor MPF-II
212 parts17 - 2 layers

EDiCPoster
Nik-Sch/EDiC
Developement, Simulation and Emulation of an 8 bit CPU including a Software Framework for my Masters Thesis
176 parts1 - 2 layers295 × 195 mm

- 2 layers426 × 307 mm

I7000
felipesanches/Itautec_I7000_KICAD
Esquemáticos do computador Itautec I-7000 G desenhados a partir de inspeção do circuito das PCBs
115 parts - 2 layers400.9 × 280.5 mm

- 2 layers364 × 203 mm

- 2 layers338.7 × 107.7 mm

- 2 layers244 × 244 mm

Questions
How big is the Control PCB?
It measures 206.4 × 137.5 mm and has 2 copper layers, 1.6 mm thick.
What parts does the Control use?
67 parts, built around the 74LS253DC, 74LS377PC, 74LS257PC and 74LS273PC. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
Where can I download the Control KiCad files?
From the tergav17/RDP-9 repository on GitHub, at the commit this page was made from: the board is kicad/Control/Control.kicad_pcb and its schematic kicad/ALU/ALU.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Can I use the Control design in my own project?
Its repository states no licence, so its author keeps all rights: ask tergav17 before reusing the design.