Writing into being.
When debugging user programs on the TEC-1 I kept hitting a wall at ROM boundaries. The debugger could step through my code but the moment execution jumped into the monitor ROM the source view went dark. I fixed that by teaching Debug80 to load external listings then build source maps from assembly files at session start.
I removed the TEC-1 program loader from the core debug80 extension and moved machine content into its own repo. This entry explains why the split mattered and how the platform pack is laid out. It also shows what makes the setup runnable on day one.
I built a TEC-1 memory panel so the debugger could show live memory state without guesswork. This entry explains the snapshot request and the windowing rules, then shows how the panel grew into a multi-view dashboard with symbol context.
True hardware emulation requires more than just instruction execution; it requires a deterministic model of time based on processor cycles. This article explores the CycleClock and the challenges of emulating the TEC-1 periphery.
The TEC-1 defines a small but complete hardware platform. Its memory map, I/O model, and human interface provide a concrete starting point for Debug80’s platform system.
My work with the Z80 began on paper in the late 1970s and became real hardware in the early 1980s. This series documents a return to that architecture through the construction of a modern debugging environment.