Since one can get parts that provide a full memory map, even though one doesn't have to use the entire map, it's possible to use a part with 64KB flash even though one only uses 16K for the target code. BASIC52 lives comfortably in an 8K memory map.

I doubt a well-designed monitor will take up more than that, though it probably could take up more than that without being a problem. The first resident monitor program I used was smaller than 256 bytes, though not by much.

If a table-driven assembler/disassembler were added to a C-coded debugger, I'd expect it to consume perhaps as much as 24KB. That wouldn't be a problem in most cases, since pin-compatible memory can be used, along with CPU's that are pin-compatible but contain more PROM space.

It really doesn't matter how large the debugger is, so long as the total of monitor + target code remains within the 64K map.

RE