Design review — control paths and I/O (sequencer logic/memory, IO, bus tester, backplane, video) — 2026-09-21¶
Section 4 of the 2026-09-21 control-paths and I/O review: the bus tester v1.1, findings 4.1-4.2. The other cards' sections ("above" and "below" in the original), the cross-card notes and the summary:
hardware/reviews/control-io-2026-09-21.md.
Second pass after the mechanical one in mechanical-2026-09-21.md. Read from the KiCad netlists (reports/netlist.net, pin
types from the Eagle symbols), chip values from the Eagle boards, the firmware that drives the ATmegas
(embedded/bus-tester/bus-driver, embedded/sequencer-card/sequencer4) and the microcode generator
(firmware/microcode/ucode-generator2). Gate pin-outs were checked against the symbol pin functions (I0/I1/O for
7400/08/32, O/I/I for 7402; 74175/74/192/244/374 pin functions as printed in the netlist).
Every finding: the trace (ref.pin -> net -> ref.pin, chip types), the failure scenario, severity (HIGH = stops the card / damages parts, MED = unreliable or latent, LOW = housekeeping), and how to confirm it on the bench. Already-known items (BACKLOG.md, video README) are not repeated except where a new detail changes them. Report only; no redesign.
Scripts used (not committed): a netlist dumper (parts + nets with pin function/type), an SV1/SV2 pin-by-pin comparator, a bus-driver-table-vs-tester-wiring check and a microcode-bit-vs-RAM-wiring check; the results of the three checks are in the "checked, no issue" lists below.
4. Bus tester v1.1 (hardware/cards/bus-tester/kicad/v1.1)¶
4.1 HIGH (the other side of 1.1) — nothing on the card can make the expanders passive; the firmware drives every control line and both buses from setup()¶
IC1 (0x20) A3–A18 = ADDR0–15, IC2 (0x21) A19–B6 = DATA0–15, IC3 (0x22) B7–B22, IC4 (0x23) B23–C10, IC5 (0x24)
C11–C26, IC6 (0x25) C27–C30 + the on-card LED/switch lines — MCP23017 GPIO pins straight onto the DIN pins, no
buffer, no enable. bus-driver.ino setup(): all pins INPUT first, then every table entry pinMode(OUTPUT) with
its inactive level, dataBusDir(BUS_WRITE), addrBusDir(BUS_WRITE), then only BR-COND, -INT and IN back to
INPUT. So from power-up the tester drives 32 bus + 52 control lines including -RESET (C30), -BUS-EN (C28), -RUN
(C29), OUT (C27) and the register-card ID/strobe lines that the logic card also drives (1.1). The 2020 V3.1
redesign (latches with enables) was the fix and was never built. Confirm: as 1.1.
4.2 LOW — RN1–RN4 pull up all 32 address/data lines on the bus; value not recorded¶
RN1–RN4 (RN-9, pin 1 = VCC) on A3–A18 and A19–B6. The v3.1 notes say "removing pull-ups ... on Data and Address lines", so they are known to be there; the Eagle value is blank. If they are 1k each driver on the bus sinks 5 mA per line (fine for LS244/245, tight for anything weaker). Confirm: measure RN1 pin 1–2.
Checked, no issue (bus tester)¶
- Signal table vs wiring vs bus: all 52 bus entries in
YACC_Common_header.h(chip, port, pin) reach the DIN pin that carries that signal in the V3.2 pinout (only the IOADDRn/IO-ADDRn spelling differs); the 12 on-card entries (OUT-LED, IN-SWITCH, LEDS-LD, SWITCHES-RD, BIT0–7) are local. - Local reset: ATmega p1, all six expander /RESET p18, CPU-RESET button and R2–R8 10k are one net that does not reach C30 — the bus -RESET is just IC6 GPA3.
- Switch/LED port: IC9 74LS244 enable = SWITCHES-RD (IC6 GPA7), outputs BIT0–7 shared with IC6 GPB0–7 and IC8
74LS374 D inputs; firmware sets SWITCHES-RD high at setup and GPB to input before pulling it low
(
read_switches), so the only bus fight would be a firmware bug. - I2C addresses 0x20–0x25 all distinct; EEPROM IC7 at 0x57; SCL/SDA 2.2k pull-ups.