This is a project that provides a cross platform debugging environment for VICE emulator. It's build with .NET 7 and using Avalonia as UI. The goal is to create a nice environment for debugging VICE apps built with ACME Cross-Assembler while learning Avalonia, VICE and C64 machine language at the same time. Currently I'm testing only on Windows 10, but it might just work on Linux and MacOS as well. For communication with VICE it is using my other project VICE Binary Monitor Bridge for .NET.
App is currently in alpha state. Feel free to open issues, if you are in a mood for contributing a PR, ask first. Find binaries in the Release section, for now just win-x64. If you want to run it on another OS, compile it your self: just clone repo, open solution and compile it. Or just use dotnet command line.
I'm mostly hanging out at Everything C64 discord development channel and Mastodon as @[email protected].
Main development is going on on develop branch and specific features are being developed and dedicated feature/FEATURE branches until they are merged into develop branch.
Releases are published as framework dependent binaries (.NET 8.0 runtime required) here and there until an automated distribution system is put in place.
At this time new features are still being added any many pieces have yet to fall in place.
Also this documentation is outdated.
Application was first developed with ACME as compiler in mind, then it was modified to be compiler agnostic and lastly Oscar64 support was added where most of the work has been done since. Until I update documentation below, consider it quite obsolete and it might not even work with ACME for now.
Oscar64 compilation should use these parameters, to minimize optimizations:
oscar64 .\YOURFILE.c -g -tm=c64 -tf=prg -n -O0
Oscar64 compiler (preferebly as fresh as possible) or ACME Cross-Assembler and VICE emulator.
A simple application taken from ACME Cross-Assembler samples looks like:
!to "tiny.prg", cbm ; set output file and format
* = $0801
!wo boot
!wo 1 ; line number
!by $9e ; SYS
!TEXT "2061",0
boot !wo 0
* = 2061
;* = $c000 ; set program counter
CLEAR = 147 ; a global symbol definition
!addr basout = $ffd2 ; another one, marked as an address
; a string output loop:
start ldx #0
lda .string
beq + ; enter loop
- jsr basout ; output character
inx ; advance pointer
+ lda .string, x ; get character
bne - ; check whether last
rts
.string !pet "Dumb example", 13, 0The actual app starts at start label while the code in front makes it accessible from BASIC. The app itself just prints "Dumb example" text to C64 screen.
- Copy this code and save it into Sample directory somewhere, like Sample/tiny.asm.
- Make subdirectory out.
- Compile the code using arguments for creating debug information
acme -r out\tiny.report --vicelabels out\tiny.labels -o out\tiny.prg -f cbm .\tiny.asmIt will generate machine code and meta data in the out directory. Extensions .labels and .report are important. Also the cbm format. Do not modify them.
-
Install or compile the source.
-
Run Modern.Vice.PdbMonitor.exe (or an equivalent when not on Windows).
-
Upon start Settings dialog is open. Enter path to VICE. This information will be used to autostart VICE when required. Click Close. The Settings dialog will appear always at the start unless path to VICE is set.
-
Next the application without a project set is displayed.
-
Use File/New... to create a new project. Name it tiny (.mapd extension will be added) and place it into the Sample directory. Open File/Project Settings... and set path to tiny.prg file created when tiny.asm was compiled (path is relative to project). There are two ways to auto start the app. Using VICE which will start code from beginning (the first code block uses BASIC to start the app). Or use Auto starts at 'start' label address option which start the app at address defined by start label. Stop at label gives you the option to stop execution at certain label after auto start. This is mostly useful in combination with VICE auto start since we want app to stop at user code, not at bootstrap as in this case. Set Auto Start to Auto starts using VICE and Stop at label to start. Click Close.
-
Explorer is now populated with files and labels, both can be double clicked and open the code in the code viewer. Registers panel shows the current registers values.
-
Click the Run button to start the application. It will stop at start label.
-
Click Run again and app will complete. Since app has no real stop, app will still be showing as running. VICE will show this result.
-
A breakpoint can be also set. Click on left of the line numbers to automatically create a breakpoint. All breakpoints are listed in Breakpoints panel (breakpoint might be using arbitrary address, not a source line one). If you run the app now, it will stop at given breakpoint after second click on Run.
-
Breakpoints can be modified (right click on breakpoint in the list and Properties or double click on it) or created manually (Create button). When breakpoints are created like in previous step, they are linked to file and its line. To unbind it, click Full Unbind. When breakpoints are linked to label, they can be first unbound to file using Unbind to file. Once the breakpoint is fully unbound, its address start and end can be modified. Condition window lets you add a condition upon which the breakpoint is triggered. See Checkpoint commands for condition syntax (enter only <cond_expr> in the input). Sample condition would be
X == $3which trigger the breakpoint only when register X has value of $3. Breakpoints can be also disabled through Is enabled flag.
To enable diagnostics, place appsettings.json file in output directory where binaries are with content like this:
{
"Application": {
"MessagesHistory": true
}
}
Currently there is a single diagnostics helper.
- Messages History shows communication with VICE.
- Auto starts VICE if required
- Registers display
- Breakpoints support
- Source code viewer
- Automatically reloads debugging symbols upon start when sources are compiled
- Cross platform
- Will add other features through time