1 <!doctype linuxdoc system>
5 <title>Watara Supervision specific information for cc65
6 <author>Stefan A. Haubenthal, <htmlurl url="mailto:polluks@sdf.lonestar.org" name="polluks@sdf.lonestar.org">
10 An overview over the Supervision runtime system as it is implemented for the
14 <!-- Table of contents -->
17 <!-- Begin the document -->
21 This file contains an overview of the Supervision runtime system as it comes
22 with the cc65 C compiler. It describes the memory layout, Supervision specific header
23 files, available drivers, and any pitfalls specific to that platform.
25 Please note that Supervision specific functions are just mentioned here, they are
26 described in detail in the separate <htmlurl 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 information.
31 <sect>Binary format<p>
33 The standard binary output format generated by the linker for the Supervision target
34 is a 2×16 kbyte machine language program. It is of course
35 possible to change this behaviour by using one of the different linker configs.
37 <sect>Memory layout<p>
39 cc65 generated programs with the default setup run with the I/O area enabled,
40 which gives a usable memory range of $8000 - $FFF9.
41 More ROM may need additional bankswitching code.
47 <!-- The text screen is located at VRAM $4000.-->
48 No conio support is currently available for the Supervision.
51 The C runtime stack is located at $1FFF and growing downwards.
54 The C heap is located at the end of the program and grows towards the C
61 <sect>Platform specific header files<p>
63 Programs containing Supervision specific code may use the <tt/supervision.h/ header file.
66 <sect1>Supervision specific functions<p>
74 <sect1>Hardware access<p>
76 The following pseudo variables declared in the <tt/supervision.inc/ include file do
77 allow access to hardware located in the address space.
82 The <tt/IO/ defines allow access to the IO chip.
88 <sect>Loadable drivers<p>
90 <sect1>Graphics drivers<p>
92 No graphics drivers are currently available for the Supervision.
93 <!--A TGI driver for the standard graphics mode (160×160 in 4 colors) is
94 available, but must be statically linked, because no file I/O is available.
95 See the documentation for the <htmlurl url="co65.html" name="co65 utility">
96 for information on how to do that.-->
98 <sect1>Extended memory drivers<p>
100 No extended memory drivers are currently available for the Supervision.
103 <sect1>Joystick drivers<p>
105 No joystick drivers are currently available for the Supervision.
106 <!--A joystick driver for the standard buttons is available, but must be
107 statically linked, because no file I/O is available. See the documentation for
108 the <htmlurl url="co65.html" name="co65 utility"> for information on how to do
111 <sect1>Mouse drivers<p>
113 No mouse drivers are currently available for the Supervision.
116 <sect1>RS232 device drivers<p>
118 No communication port drivers are currently available for the Supervision.
126 The existing library for the Supervision doesn't implement C file
127 I/O. There are even no hacks for the <tt/read()/ and <tt/write()/ routines.
129 To be more concrete, this limitation means that you cannot use any of the
130 following functions (and a few others):
149 <sect>Bugs/Feedback<p>
151 If you have problems using the library, if you find any bugs, or if you're
152 doing something interesting with it, I would be glad to hear from you. Feel
153 free to contact me by email (<htmlurl url="mailto:uz@cc65.org"
154 name="uz@cc65.org">).
160 This software is provided 'as-is', without any expressed or implied
161 warranty. In no event will the authors be held liable for any damages
162 arising from the use of this software.
164 Permission is granted to anyone to use this software for any purpose,
165 including commercial applications, and to alter it and redistribute it
166 freely, subject to the following restrictions:
169 <item> The origin of this software must not be misrepresented; you must not
170 claim that you wrote the original software. If you use this software
171 in a product, an acknowledgment in the product documentation would be
172 appreciated but is not required.
173 <item> Altered source versions must be plainly marked as such, and must not
174 be misrepresented as being the original software.
175 <item> This notice may not be removed or altered from any source