1 <!doctype linuxdoc system>
5 <title>Nintendo Entertainment System 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 NES runtime system as it is implemented for the
16 <!-- Table of contents -->
19 <!-- Begin the document -->
23 This file contains an overview of the NES runtime system as it comes
24 with the cc65 C compiler. It describes the memory layout, NES specific header
25 files, available drivers, and any pitfalls specific to that platform.
27 Please note that NES 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 NES target
37 is a machine language program with an INES cartridge header. It is of course
38 possible to change this behaviour by using a modified startup file and linker
41 <sect>Memory layout<p>
43 cc65 generated programs with the default setup run with the I/O area and a
44 CHR bank enabled, which gives a usable memory range of $8000 - $FFF3.
45 All boot ROM entry points may be called directly without additional code.
51 The text screen is located at VRAM $2000.
54 The C runtime stack is located at $7FFF and growing downwards.
57 The C heap is located at the end of the program and grows towards the C
64 <sect>Platform specific header files<p>
66 Programs containing NES specific code may use the <tt/nes.h/ header file.
69 <sect1>NES specific functions<p>
78 <sect1>Hardware access<p>
80 The following pseudo variables declared in the <tt/nes.inc/ include file do
81 allow access to hardware located in the address space.
86 The <tt/PPU/ defines allow access to the PPU chip.
89 The <tt/APU/ defines allow access to the APU chip.
95 <sect>Loadable drivers<p>
97 All drivers must be statically linked because no file I/O is available.
98 The names in the parentheses denote the symbols to be used for static linking of the drivers.
101 <sect1>Graphics drivers<p>
105 <tag><tt/nes-64-56-2.tgi (nes_64_56_2)/</tag>
106 This driver features a resolution of 64×56 with 2 colors using the
112 <sect1>Extended memory drivers<p>
114 No extended memory drivers are currently available for the NES.
117 <sect1>Joystick drivers<p>
121 <tag><tt/nes-stdjoy.joy (nes_stdjoy)/</tag>
122 A joystick driver for the standard four buttons joypad is available.
127 <sect1>Mouse drivers<p>
129 No mouse drivers are currently available for the NES.
132 <sect1>RS232 device drivers<p>
134 No serial drivers are currently available for the NES.
142 The existing library for the NES doesn't implement C file
143 I/O. There are no hacks for the <tt/read()/ and <tt/write()/ routines.
145 To be more concrete, this limitation means that you cannot use any of the
146 following functions (and a few others):
167 This software is provided 'as-is', without any expressed or implied
168 warranty. In no event will the authors be held liable for any damages
169 arising from the use of this software.
171 Permission is granted to anyone to use this software for any purpose,
172 including commercial applications, and to alter it and redistribute it
173 freely, subject to the following restrictions:
176 <item> The origin of this software must not be misrepresented; you must not
177 claim that you wrote the original software. If you use this software
178 in a product, an acknowledgment in the product documentation would be
179 appreciated but is not required.
180 <item> Altered source versions must be plainly marked as such, and must not
181 be misrepresented as being the original software.
182 <item> This notice may not be removed or altered from any source