1 <!doctype linuxdoc system>
5 <title>Commodore 128-specific information for cc65
6 <author><url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz">
10 An overview over the C128 runtime system as it is implemented for the cc65 C
14 <!-- Table of contents -->
17 <!-- Begin the document -->
21 This file contains an overview of the C128 runtime system as it comes with the
22 cc65 C compiler. It describes the memory layout, C128-specific header files,
23 available drivers, and any pitfalls specific to that platform.
25 Please note that C128-specific functions are just mentioned here, they are
26 described in detail in the separate <url url="funcref.html" name="function
27 reference">. Even functions marked as "platform dependent" may be available on
28 more than one platform. Please see the function reference for more
32 <sect>Binary format<p>
34 The standard binary output format generated by the linker for the C128 target
35 is a machine language program with a one line BASIC stub, which calls the
36 machine language part via SYS. This means that a program can be loaded as
37 BASIC program and started with RUN. It is of course possible to change this
38 behaviour by using a modified startup file and linker config.
41 <sect>Memory layout<p>
43 cc65 generated programs with the default setup run with the I/O area and the
44 kernal ROM enabled. Note that this is a non standard memory layout, and that
45 there is no "memory configuration index" for this layout. This means that
46 special care has to be taken when changing the configuration, or calling any
47 code that does this. The memory configuration register at $FF00 should
48 be saved and restored instead of relying on the memory configuration index
49 stored in the zero page.
51 The setup gives a usable memory range of $1C00 - $BFFF. Having
52 just the kernal ROM mapped in means, that kernal entry points may be called
53 directly, but using the BASIC ROM is not possible without additional code.
59 The text screen is located at $400 (as in the standard setup).
62 The C runtime stack is located at $BFFF, and growing downwards.
65 The C heap is located at the end of the program, and grows towards the C
72 <sect>Platform-specific header files<p>
74 Programs containing C128-specific code may use the <tt/c128.h/ or <tt/cbm.h/
75 header files. Using the later may be an option when writing code for more than
76 one CBM platform, since it includes <tt/c128.h/ and declares several functions
77 common to all CBM platforms.
80 <sect1>C128-specific functions<p>
82 The functions listed below are special for the C128. See the <url
83 url="funcref.html" name="function reference"> for declaration and usage.
94 <sect1>CBM-specific functions<p>
96 Some functions are available for all (or at least most) of the Commodore
97 machines. See the <url url="funcref.html" name="function reference"> for
98 declaration and usage.
126 <sect1>Hardware access<p>
128 The following pseudo variables declared in the <tt/c128.h/ header file do
129 allow access to hardware located in the address space. Some variables are
130 structures, accessing the struct fields will access the chip registers.
135 The <tt/VIC/ structure allows access to the VIC II (the graphics
136 controller). See the <tt/_vic2.h/ header file located in the include
137 directory for the declaration of the structure.
140 The <tt/SID/ structure allows access to the SID (the sound interface
141 device). See the <tt/_sid.h/ header file located in the include directory
142 for the declaration of the structure.
145 The <tt/VDC/ structure allows access to the VDC (the video display
146 controller). See the <tt/_vdc.h/ header file located in the include
147 directory for the declaration of the structure.
149 <tag><tt/CIA1, CIA2/</tag>
150 Access to the two CIA (complex interface adapter) chips is available via
151 the <tt/CIA1/ and <tt/CIA2/ variables. The structure behind these variables
152 is explained in <tt/_6526.h/.
154 <tag><tt/COLOR_RAM/</tag>
155 A character array that mirrors the color RAM of the C128 at $D800.
161 <sect>Loadable drivers<p>
163 The names in the parentheses denote the symbols to be used for static linking of the drivers.
166 <sect1>Graphics drivers<p>
168 The default drivers, <tt/tgi_stddrv (tgi_static_stddrv)/, point to <tt/c128-vdc.tgi (c128_vdc_tgi)/.
170 Note: The graphics drivers for the VDC are incompatible with the extended
171 memory drivers using the VDC memory!
174 <tag><tt/c128-vdc.tgi (c128_vdc_tgi)/</tag>
175 This driver was written by Maciej Witkowiak. It uses the 80-column display,
176 and features a resolution of 640*200 with two colors and an adjustable
177 palette (that means that the two colors can be chosen out of the 16 VDC
180 <tag><tt/c128-vdc2.tgi (c128_vdc2_tgi)/</tag>
181 This driver was written by Maciej Witkowiak. This driver uses the 80-column
182 display, and features a resolution of 640*480 with two colors and an
183 adjustable palette (that means that the two colors can be chosen out of the
184 16 VDC colors). The driver requires 64KB VDC RAM.
187 Note: The colors are translated from definitions in headers to correct VDC values;
188 so, please use definitions or VIC color numbers only. Colors <tt/GRAY3/ and <tt/BROWN/ are
189 missing on VDC, and are translated to the two colors missing from the VIC palette.
191 <sect1>Extended memory drivers<p>
195 <tag><tt/c128-efnram.emd (c128_efnram_emd)/</tag>
196 Extended memory driver for the C128 External Function RAM.
197 Written and contributed by Marco van den Heuvel.
199 <tag><tt/c128-georam.emd (c128_georam_emd)/</tag>
200 A driver for the GeoRam cartridge. The driver will always assume 2048 pages
201 of 256 bytes each. There are no checks, so if your program knows better,
204 <tag><tt/c128-ifnram.emd (c128_ifnram_emd)/</tag>
205 Extended memory driver for the C128 Internal Function RAM.
206 Written and contributed by Marco van den Heuvel.
208 <tag><tt/c128-ram.emd (c128_ram_emd)/</tag>
209 An extended memory driver for the RAM in page 1. The common memory area is
210 excluded, so this driver supports 251 pages of 256 bytes each.
212 <tag><tt/c128-ram2.emd (c128_ram2_emd)/</tag>
213 An extended memory driver for the RAM in pages 1-3. The common memory area
214 is excluded, so this driver supports up to 731 pages of 256 bytes each. The
215 driver can be used as a full replacement for <tt/c128-ram.emd/, because RAM
216 in pages 2+3 is autodetected, but it's larger and there are not many
217 machines with RAM in banks 2+3, so it has been made a separate driver. The
218 additional code was contributed by Marco van den Heuvel.
220 <tag><tt/c128-ramcart.emd (c128_ramcart_emd)/</tag>
221 A driver for the RamCart 64/128 written and contributed by Maciej Witkowiak.
222 Will test the hardware for the available RAM.
224 <tag><tt/c128-reu.emd (c128_reu_emd)/</tag>
225 A driver for the CBM REUs. The driver will test the connected REU to find
226 out how much RAM is present.
228 <tag><tt/c128-vdc.emd (c128_vdc_emd)/</tag>
229 A driver for the VDC memory of the C128, written and contributed by Maciej
230 Witkowiak. Autodetects the amount of memory available (16 or 64K), and offers
231 64 or 256 pages of 256 bytes each. Note: This driver is incompatible with
232 any of the graphics drivers using the VDC!
237 <sect1>Joystick drivers<p>
239 The default drivers, <tt/joy_stddrv (joy_static_stddrv)/, point to <tt/c128-stdjoy.joy (c128_stdjoy_joy)/.
243 <tag><tt/c128-ptvjoy.joy (c128_ptvjoy_joy)/</tag>
244 Driver for the Protovision 4-player adapter originally written by Groepaz
245 for the C64, and converted for the C128 by Uz. See <url
246 url="http://www.protovision-online.de/hardw/4_player.php?language=en"
247 name="Protovision shop"> for prices and building instructions. Up to four
248 joysticks are supported.
250 <tag><tt/c128-stdjoy.joy (c128_stdjoy_joy)/</tag>
251 Supports up to two joysticks connected to the standard joysticks ports of
258 <sect1>Mouse drivers<p>
260 The default drivers, <tt/mouse_stddrv (mouse_static_stddrv)/, point to <tt/c128-1351.mou (c128_1351_mou)/.
264 <tag><tt/c128-1351.mou (c128_1351_mou)/</tag>
265 Supports a standard mouse connected to port #0 of the C128.
267 <tag><tt/c128-inkwell.mou (c128_inkwell_mou)/</tag>
268 Supports the Inkwell Systems lightpens, connected to port #0 of the
269 C128. It can read both the one-button 170-C and the two-button 184-C pens.
270 (It can read other lightpens and light-guns that send their button signal to
271 the joystick left-button pin or the paddle Y [up/down] pin.) It works on
272 only the 40-column screen.
274 <tag><tt/c128-joy.mou (c128_joy_mou)/</tag>
275 Supports a mouse emulated by a standard joystick, e.g. 1350 mouse, in port
278 <tag><tt/c128-pot.mou (c128_pot_mou)/</tag>
279 Supports a potentiometer device, e.g. Koala Pad, connected to port #1 of
285 <sect1>RS232 device drivers<p>
289 <tag><tt/c128-swlink.ser (c128_swlink_ser)/</tag>
290 Driver for the SwiftLink cartridge. Supports up to 38400 BPS, hardware flow
291 control (RTS/CTS), and interrupt-driven receives. Note that, because of the
292 peculiarities of the 6551 chip, together with the use of the NMI, transmits
293 are not interrupt driven; and, the transceiver blocks if the receiver asserts
294 flow control because of a full buffer.
296 The driver uses the RS232 variables and buffers of the kernal (buffers at
297 $C00 and $D00).
310 <sect1>Passing arguments to the program<p>
312 Command-line arguments can be passed to <tt/main()/. Since this is not
313 supported directly by BASIC, the following syntax was chosen:
316 RUN:REM ARG1 " ARG2 IS QUOTED" ARG3 "" ARG5
320 <item>Arguments are separated by spaces.
321 <item>Arguments may be quoted.
322 <item>Leading and trailing spaces around an argument are ignored. Spaces within
323 a quoted argument are allowed.
324 <item>The first argument passed to <tt/main()/ is the program name.
325 <item>A maximum number of 10 arguments (including the program name) are
330 <sect1>Program return code<p>
332 The program return code (low byte) is passed back to BASIC by use of the
338 The runtime for the C128 uses routines marked as <tt/.INTERRUPTOR/ for
339 interrupt handlers. Such routines must be written as simple machine language
340 subroutines and will be called automatically by the interrupt handler code
341 when they are linked into a program. See the discussion of the <tt/.CONDES/
342 feature in the <url url="ca65.html" name="assembler manual">.
348 This software is provided 'as-is', without any expressed or implied
349 warranty. In no event will the authors be held liable for any damages
350 arising from the use of this software.
352 Permission is granted to anyone to use this software for any purpose,
353 including commercial applications, and to alter it and redistribute it
354 freely, subject to the following restrictions:
357 <item> The origin of this software must not be misrepresented; you must not
358 claim that you wrote the original software. If you use this software
359 in a product, an acknowledgment in the product documentation would be
360 appreciated but is not required.
361 <item> Altered source versions must be plainly marked as such, and must not
362 be misrepresented as being the original software.
363 <item> This notice may not be removed or altered from any source