Simulator Startup
Once you have switched to debugger mode, you can start the program.
A debugger can only be called if we have the resulting program code. program code is created when you have no errors on the end of the assembly or loaded with the File/Open Code command... The presence of the resulting code represents a stamp
in the status bar. When you switch to the debugger, it changes to
.
In debugger mode, the 6502 (or 65C02) processor works simulated. The following commands are available:
- Run (F5) - executes the program at full speed with no status updates,
- Animate (Ctrl-F5) - Run, but updates the state of the registry window, allowing you to keep an account of changes,
- Step Into (F11) single step - follow one instruction,
- Step Over (F10) - single step from current line, but will complete a whole subroutine,
- Run to return (Ctrl-F11) - performs to exit the subroutine,
- Run to cursor (Ctrl-F10) - executes to the line where the cursor is,
- Skip instruction (Shift-F11) - bypasses the execution of the current instruction,
- Skip to Cursor (Ctrl-SHift-F11) - move command counter to the line where the cursor is,
- Stop - stops the simulator,
- Restart - restarts the simulator from teh beginning
- Breakpoint - sets a stopping place for Run
- Breakpoint parameters - sets the parameters of the stop location
- Pulse an IRQ - Cause an IRQ interrupt and will jump to location pointed to by IRQ vector ($FFFE)
- Pulse an NMI - Cause an NMI interrupt and will jump to location pointed to by NMI vector ($FFFA)
- Pulse a processor Reset - Cause a RESet and will jump to location pointed to by RES vector ($FFFC)
- Set timed Interrupts - sets the time intervals in ms for repeated IRQ and/or NMI Interrupts