13 lines
1.7 KiB
Markdown
13 lines
1.7 KiB
Markdown
# C64 Livecoding demo
|
|
|
|
Livecoding a Commodore 64 in a language compiled on a modern PC written via an editor running on a VT220.
|
|
|
|
## Editor
|
|
|
|
In a real hardware setup, the editor, which is integrated with the compiler, runs the show. In this setup, running it is simple. Running it interactively is almost as simple.
|
|
|
|
If you have Roswell installed, running the editor can be done by running one of the two start scripts, `run-editor-real.ros` for situations where the host program will not change, and `run-editor-preview.ros` for situations where it may. These are run like any other script from the shell. The scripts must be given a parameter in the form `/dev/<the tty device>` where `<the tty device>` is the terminal you wish to have the editor run on. This is most likely `/dev/ttyUSB0`, but may be something like `/dev/pts/3` if you're testing without a real VT220.
|
|
|
|
The editor should now run. Keybindings will eventually be listed, but for now the source code is the canonical list of bindings. A *clear screen* command is required before anything will show on the display.
|
|
|
|
The editor will, when the *compile* command is issued, perform a compilation, write statistics and IR to standard output, save both the source code and 6502 binary to the current working directory, then attempt to upload the code to the C64 via a serial device on `/dev/ttyACM0`. This path should ideally not change, but if the need arises, it can be changed simply be changing the variable `USC::*C64-TTY*`. In the event this transfer fails to begin, for example if the serial device is missing, a warning is printed to standard output, but the editor does not display anything. Saved files are unaffected by a failed transfer.
|