To access Oricutron's debugger you need to press the F2 key. This will show you this screen:
In the monitor, number arguments are decimal by default, or prefixed with $ for hex or % for binary. Pretty much everything is output in hex.
In most places where you can enter a number or address, you can pass a CPU or VIA register. (VIA registers are prefixed with V, e.g. VDDRA). Anywhere you can pass an address, you can also use a symbol.
To use Oricutron's debugger, you need to know some keys:
- F2: Return to the emulator
- F3: Toggle console/debug output/memwatch
- F4: Toggle VIA/AY information
- F9: Reset cycle count
- F10: Step over code
- F11: Step over code without tracing into subroutines.
- F12: Skip instruction
You also have some more advanced commands:
- ? - Help
- Clear breakpoint
- Clear mem breakpoint
- bl - List breakpoints
- blm - List mem breakpoints
- Set breakpoint
[rwc] - Set mem breakpoint
- bz - Zap breakpoints
- bzm - Zap mem breakpoints
- Disassemble to file
- Dump memory
- Modify memory
- Memory watch at addr
- Load snapshot
- Save snapshot
- Set to
- q, x or qm - Quit monitor
- qe - Quit emulator
- Add or move user symbol
- Kill user symbol
- sc - Symbols not case-sensitive
- sC - Symbols case-sensitive
- Load user symbols
- Export user symbols
- sz - Zap user symbols
- Write mem to disk
Issue #34: Tap file that crash on first load but not on second:
Details: This does not happen for all program files but sometimes Oricutron will not properly execute a loaded .tap file and instead display the Monitor window showing the PC stuck at address $24D. When using the monitor to examine disassembled memory, the code is correctly present at address $600.
When that happens, issuing a RESET from Oricutron and typing manually CLOAD"" and re-inserting the proper .tap file is enough for the program to run normally.
For some reason, the first run always fail as described above but after a reset everything works as expected.
As noted, this happens only for one of my program, a 23,370 bytes long .tap file.
I can provide that .tap file and associated symbols file if needed.
Fixed in OSDK 1.12
Details: If the project is not located on the same drive as the OSDK; Oricutron will fail to launch because osdk_oricutron.bat does not point it to the right location. Using START /d "%OSDK%\Oricutron" %OSDKORICUTRON% instead fixes it.
comments powered by Disqus