This file contains an overview of the KIM-1 runtime system as it comes with the cc65 C compiler. It describes the memory layout, KIM-1 specific header files, available drivers, and any pitfalls specific to the platform.
Please note that KIM-1 specific functions are just mentioned here, they are described in detail in the separate function reference. Even functions marked as "platform dependent" may be available on more than one platform. Please see the function reference for more information.
The output format generated by the linker for the KIM-1 target is a raw binary BIN file, which is essentially a memory image. You can convert this to a papertape format file using Convert8bithexformat or KIMPaper, which are open-source conversion utility programs. A papertape format files can be transferred to the KIM-1 using the RS-232 terminal port (TTY), just as if the machine-code was entered by hand. Enter 'L' in the TTY and start the paper tape file transfer.
Included with this distribution is a 4k configuration file and a 60k config file. The KIM-1 on-board memory is limited to 4 kbytes but system memory can be increased to 60 kbytes of contiguous RAM with aftermarket add-on boards. So choose the config file that matches your system configuration before compiling and linking user programs.
The ROMs and I/O areas are defined in the configuration files, as are most of the entry points for useful subroutines in the KIM-1 monitor ROM. cc65 generated programs compiled and linked using 4k config run in the memory range of $200 - $0FFF. The 60k config expands this range to $DFFF. When using the 4k config the starting memory location and entry point for running the program is $200, so when the program is transferred to the KIM-1, it is executed by typing '200 G'. With the 60k config the default starting memory location and entry point is $2000.
Special locations:
Conio support is not currently available for the KIM-1. But stdio console functions are available.
The C runtime stack is located at $0FFF on 4kb KIM-1s, or at $DFFF for 60kb systems. The stack always grows downwards.
The C heap is located at the end of the program and grows towards the C runtime stack.
Programs containing KIM-1 code may use the kim1.h header file. See the header file for more information.
No graphics drivers are currently available for the KIM-1.
No joystick driver is currently available for the KIM-1.
No mouse drivers are currently available for the KIM-1.
No communication port drivers are currently available for the KIM-1. It has only the "master console" e.g. stdin and stdout.
The existing library for the KIM-1 doesn't implement C file I/O.
To be more specific, this limitation means that you cannot use any of the following functions (and a few others):
This header exposes KIM-1 specific I/O functions that are useful for reading and writing its ports and front panel.
See the kim1.h include file for a list of the functions available.
As stated earlier, there are config files for 4kb and 60kb systems. If you have 60kb RAM, then you will probably want to use the kim1-60k configuration, but if not - if you are using the kim1-4k configuration - then you may want to use functions like getchar, putchar, gets and puts rather than functions like scanf and printf. Printf, for example, requires about 1KB because it needs to know how to process all the format specifiers.
These sample programs can be found in the samples/kim1 directory:
This software is provided 'as-is', without any expressed or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: