LEDs on a RAM byte, DIPs unplugged, and a make target for the console

What I tried

b8008_top gains a LED_SHADOW_ADDR generic and a ram_byte_led output, a shadow of one RAM byte the same way the boot vector shadows byte 0. Both board tops put it on LEDs 7 to 1, bit n to LED n, 1 is on. LED0 (D25) stays the CPU-running light. In the monitor build the byte is 0x3FFF, so W 3FFF,FE lights all seven. In the BASIC build it’s 0x00FF, reached with MON, then W 00FF,FE, then G 1FB6. Port 8 is still latched by the core and no longer shown.

A cylon_ram sample sweeps the seven LEDs through the byte, G 2100, any key exits.

What broke

The DIP bank. On this board ON reads as 0. With the old wiring, my all-OFF bank selected the fetch-capture LED mode, and any flip of switch 6 or 7 halted the CPU through the READY hold or the interrupt input. So sw(1) through sw(7) are no-connects in both tops now: no capture modes, no switch interrupts, READY tied high, post-bootstrap break off. Only DIP 1, reset, remains.

What I measured

Two new regressions: monitor_led_tb at 900 ms of simulated time, and basic_led_tb at 2.1 s covering a full boot, MON, W, G 1FB6 and LIST. Timing reports refreshed.

The serial side: make monitor opens minicom, make kill-monitor closes it, and make send-hex HEX=name resolves against the samples directory. kill-monitor waits for minicom to finish its hangup and then settles 2 s before the port is reopened. At 0.5 s the first bytes of a send came through corrupted. Validated on the board.

Next

No plan for the core. This is the state the Byte Hamr card’s 8008 and the Apple II toolchain build on.