1 <!doctype linuxdoc system>
5 <title>Commodore VIC20 (aka VC20) specific information for cc65
7 <url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz">,<newline>
8 <url url="mailto:polluks@sdf.lonestar.org" name="Stefan A. Haubenthal">
12 An overview over the VIC20 runtime system as it is implemented for the cc65 C
16 <!-- Table of contents -->
19 <!-- Begin the document -->
23 This file contains an overview of the VIC20 runtime system as it comes with the
24 cc65 C compiler. It describes the memory layout, VIC20-specific header files,
25 available drivers, and any pitfalls specific to that platform.
27 Please note that VIC20-specific functions are just mentioned here, they are
28 described in detail in the separate <url url="funcref.html" name="function
29 reference">. Even functions marked as "platform dependent" may be available on
30 more than one platform. Please see the function reference for more
34 <sect>Binary format<p>
36 The standard binary output format generated by the linker for the VIC20 target
37 is a machine language program with a one line BASIC stub, which calls the
38 machine language part via SYS. This means that a program can be loaded as
39 BASIC program and started with RUN. It is of course possible to change this
40 behaviour by using a modified startup file and linker config.
43 <sect>Memory layout<p>
45 cc65 generated programs with the default setup run with unexpanded memory
46 (RAM at $A000 - $BFFF may be used for the heap),
47 which gives a usable memory range of $1000 - $1DFF.
48 All ROM entry points may be called directly without additional code.
54 The text screen is located at $1E00 (as in the standard setup).
57 The C runtime stack is located at $1DFF and growing downwards.
60 The C heap is located at the end of the program and grows towards the C
67 <sect>Platform-specific header files<p>
69 Programs containing VIC20-specific code may use the <tt/vic20.h/ or <tt/cbm.h/
70 header files. Using the later may be an option when writing code for more than
71 one CBM platform, since it includes <tt/vic20.h/ and declares several functions
72 common to all CBM platforms.
75 <sect1>VIC20-specific functions<p>
77 There are currently no special VIC20 functions.
81 <sect1>CBM-specific functions<p>
83 Some functions are available for all (or at least most) of the Commodore
84 machines. See the <url url="funcref.html" name="function reference"> for
85 declaration and usage.
113 <sect1>Hardware access<p>
115 The following pseudo variables declared in the <tt/vic20.h/ header file do allow
116 access to hardware located in the address space. Some variables are
117 structures, accessing the struct fields will access the chip registers.
122 The <tt/VIC/ structure allows access to the VIC (the graphics
123 controller). See the <tt/_vic.h/ header file located in the include
124 directory for the declaration of the structure.
126 <tag><tt/VIA1, VIA2/</tag>
127 Access to the two VIA (versatile interface adapter) chips is available via
128 the <tt/VIA1/ and <tt/VIA2/ variables. The structure behind these variables
129 is explained in <tt/_6522.h/.
131 <tag><tt/COLOR_RAM/</tag>
132 A character array that mirrors the color RAM of the VIC20 at $9600.
138 <sect>Loadable drivers<p>
140 The names in the parentheses denote the symbols to be used for static linking of the drivers.
143 <sect1>Graphics drivers<p>
145 No graphics drivers are currently available for the VIC20.
148 <sect1>Extended memory drivers<p>
150 No extended memory drivers are currently available for the VIC20.
153 <sect1>Joystick drivers<p>
155 The default drivers, <tt/joy_stddrv (joy_static_stddrv)/, point to <tt/vic20-stdjoy.joy (vic20_stdjoy_joy)/.
159 <tag><tt/vic20-stdjoy.joy (vic20_stdjoy_joy)/</tag>
160 Supports one standard joystick connected to the joysticks port of the VIC20.
162 <tag><tt/vic20-ptvjoy.joy (vic20_ptvjoy_joy)/</tag>
163 Driver for the Protovision 4-player adapter contributed by Groepaz. See
164 <url url="http://www.protovision-online.de/hardw/4_player.php?language=en"
165 name="Protovision shop"> for prices and building instructions. Up to three
166 joysticks are supported.
171 <sect1>Mouse drivers<p>
173 No mouse drivers are currently available for the VIC20.
176 <sect1>RS232 device drivers<p>
178 No VIC1011 drivers are currently available for the VIC20.
189 <sect1>Escape code<p>
191 For an Esc, press CTRL and the <tt/[/ key.
194 <sect1>Passing arguments to the program<p>
196 Command-line arguments can be passed to <tt/main()/. Since that is not
197 supported directly by BASIC, the following syntax was chosen:
200 RUN:REM ARG1 " ARG2 IS QUOTED" ARG3 "" ARG5
204 <item>Arguments are separated by spaces.
205 <item>Arguments may be quoted.
206 <item>Leading and trailing spaces around an argument are ignored. Spaces within
207 a quoted argument are allowed.
208 <item>The first argument passed to <tt/main()/ is the program name.
209 <item>A maximum number of 10 arguments (including the program name) are
214 <sect1>Program return code<p>
216 The program return code (low byte) is passed back to BASIC by use of the
220 <sect1>Using extended memory<p>
222 The extended memory at $A000 may be added to the heap by using the following
226 /* Check for the existence of RAM */
227 if (PEEK(0xA000) == POKE(0xA000, PEEK(0xA000)+1)) {
228 /* Add it to the heap */
229 _heapadd ((void *) 0xA000, 0x2000);
236 The runtime for the VIC20 uses routines marked as <tt/.INTERRUPTOR/ for
237 interrupt handlers. Such routines must be written as simple machine language
238 subroutines and will be called automatically by the interrupt handler code
239 when they are linked into a program. See the discussion of the <tt/.CONDES/
240 feature in the <url url="ca65.html" name="assembler manual">.
246 This software is provided 'as-is', without any expressed or implied
247 warranty. In no event will the authors be held liable for any damages
248 arising from the use of this software.
250 Permission is granted to anyone to use this software for any purpose,
251 including commercial applications, and to alter it and redistribute it
252 freely, subject to the following restrictions:
255 <item> The origin of this software must not be misrepresented; you must not
256 claim that you wrote the original software. If you use this software
257 in a product, an acknowledgment in the product documentation would be
258 appreciated but is not required.
259 <item> Altered source versions must be plainly marked as such, and must not
260 be misrepresented as being the original software.
261 <item> This notice may not be removed or altered from any source