Troubleshooting¶
Symptoms seen during bring-up and their likely causes.
Hardware / bus symptoms¶
Symptom |
Likely cause |
|---|---|
Address bus stuck at one value, never changes |
No clock on PHI2 (check GP28 → CPU pin 37) or power fight (external 3.3 V on Pico VSYS while USB connected) |
65C02 address bus doesn’t change |
RDY floating (verify R1) or clock not reaching the CPU |
Address bus stuck at |
CPU in reset (RESB low — check R5 + Pico GP27 should be INPUT after boot) |
Address goes |
D0–D7 / address lines mis-wired, or ROM image wasn’t uploaded correctly |
Reset vector fetches correct bytes but jumps to wrong address |
Endianness — reset vector low byte at |
Watch shows |
Address-line crosstalk onto the data bus — use |
Watch shows |
RAM OE# still on GND — move it to +3.3 V |
RAM reads return garbage (writes seem to work) |
HM62256 at 3.3 V is out of spec — replace with 3.3 V SRAM for production |
Random behavior when touching the breadboard |
Loose wire or missing decoupling — re-seat connections; a 100 nF cap helps |
Pico USB disconnects when the 65C02 boots |
Brownout — the 3.3 V supply can’t deliver enough current |
Hardware API / host symptoms¶
Symptom |
Likely cause |
|---|---|
Upload: Device or resource busy |
Another program holds the serial port — close serial monitors first |
|
ASCII monitor still enabled — run |
|
Stale or mismatched firmware — rebuild and reflash |
|
Wrong port, no firmware flashed, or a plain serial monitor is open on the port |
|
ROM missing |
|
Run host commands from the Romulan checkout ( |