Tag: debug80

• The VS Code Skeleton

  2026-01-20 | Series: debug80diaries | Tags: debug80, vscode, dap, typescript, architecture

  

  Building a debugger means implementing the Debug Adapter Protocol. For Debug80, I chose an inline implementation to keep the connection between the interface and the machine model as tight as possible.

• Listings, Mapping, and Making Execution Legible

  2026-01-20 | Series: debug80diaries | Tags: debug80, asm80, mapping, debugging, z80

  

  Debug80 treats assembler listings as primary data and uses them to build explicit mappings between source code, addresses, and runtime execution.

• Debug80 as a System

  2026-01-20 | Series: debug80diaries | Tags: debug80, vscode, asm80, debugging, architecture

  Debug80 integrates a JavaScript Z80 assembler with VS Code’s debugging infrastructure to create a coherent environment for building and observing Z80 programs.

• The TEC-1 as a Platform

  2026-01-20 | Series: debug80diaries | Tags: debug80, z80, tec1, platforms, hardware

  

  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.

• Why I Came Back to the Z80

  2026-01-20 | Series: debug80diaries | Tags: debug80, z80, tec1, retrocomputing, tooling

  

  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.