Appendix A
At the debugger bench
Leave this page open next to a paused machine. Start with the question you have about the program, then pick the view that can answer it.
Which view answers my question?
| Your question | Where to look | What to read there |
|---|---|---|
| What will execute if I step once? | Debug → Show Debugger → Inspector | Read PC and the instruction at the arrow. At a store breakpoint, the register can already hold the new value while RAM still holds the old one. |
| What already executed while I let the machine run? | Trace | Select a recorded instruction and compare its before and after states. The shift trace shows both the input and the result. |
| Where did a CPU write land? | Inspector → MMU, then Memory | Read the active task, CPU block and bank. Add the byte’s offset to the physical bank base. Check the effective mapping and compare both views. |
| Where is the picture that BASIC drew? | Graphics Preview | Compare Current Video Page with At Address. Choose the matching graphics mode and color set. Use Pixel Inspector to locate an individual field within a byte. |
| Why did the picture change when the pixel byte stayed the same? | Graphics Preview and the program’s screen or palette instructions | The program can display a different page or change the color assigned to a pixel code. Flip the page, then compare the palette register example. |
| What should I send someone who wants to reproduce this? | Memory Tools and Trace | A raw range preserves the bytes. A trace records what ran. Write down the address space, range, stop and setup so the files have meaning outside your session. |
Put the two exercises on your bench
pixel-mask.asm is the short assembly experiment. In the native reader, save a working copy, then open it in Develop → Assembly Development…. Assemble the supplied source as written for the first run so the named instructions and the addresses in the book agree.
BEACON.bas opens an editable BASIC example from the native reader. If you are reading in a web browser, save the file and open it in Develop → BASIC Development…. Opening the example lets you inspect its source. Choose Run when you are ready to replace the practice machine’s BASIC program.
Both exercises use Disk BASIC, 512 KB, RGB. Save your current program before switching setups. The two CPUs give the same checkpoints in these exercises. A recording can contain different interrupt rows from one run to the next. Compare the named instructions and their results first.
When your stop looks different
The byte is already $40. Look at PC. If it points to RTS, the store has executed. Re-run the assembly source with the breakpoint on the store instruction. A fresh build image initializes its own sample byte to zero.
The monitor still shows the house. At BASIC line 80, that is the expected picture. In Graphics Preview, inspect the hidden page at mapped $1A00 in PMODE 1, Set 0. Read X=81, Y=32 there. After restoring any edit, remove the line breakpoints, Continue in the BASIC workspace, click the CoCo display, and tap and release Space once.
A RAM address seems much too large. Check the heading above the number. The CPU has a 16-bit address. Physical RAM on this 512 KB machine extends to $7FFFF. A CPU address and a physical RAM address can denote the same byte at this stop. Record both alongside the active map before changing the machine.
Trace stopped, but the screen is still changing. A trace stop closes the recording. Use a breakpoint when you also need to hold RAM and the video page still. A trace sample stores CPU state at an earlier moment. Selecting it does not rewind RAM.
Books behind the experiments
- Tandy Corporation. Color Computer 3 Service Manual. Section V, “Theory of Operation,” figure 5-7, “MMU Block Diagram.” Use the diagram to follow the path from the CPU’s address lines to the banked memory.
- Tepolt, Laurence A. Assembly Language Programming for the CoCo 3. TEPCO, 1987. Figures 3-4 and 4-1, pp. 20 and 23. Processor and video addressing on the CoCo 3.
- Motorola, Inc. MC6809–MC6809E 8-Bit Microprocessor Programming Manual. M6809PM (AD), March 1981, reprinted May 1983. Chapters 1–2 and Appendix A. Registers, condition codes and instruction behavior.
- Atkinson, Darren. Motorola 6809 and Hitachi 6309 Programmer’s Reference. 2009. Parts I–II. Instructions and register differences between the two processors.
For assembly syntax, operands and condition codes, the Book 9 instruction directory is available offline. For the Mac controls around the machine, use The VCC Plus User’s Handbook.
The Color Computer Archive preserves historical documentation that informed this book. The lessons and programs here were written for VCC Plus.
Original VCC Plus prose and instructional images © 2026 Brian K. Holman. See the application’s Licenses & Notices and the library’s artwork credits.