<article>
-<title>PC-Engine (TurboGrafx) System specific information for cc65
+<title>PC-Engine (TurboGrafx 16) System-specific information for cc65
<author><url url="mailto:groepaz@gmx.net" name="Groepaz/Hitmen">,<newline>
<url url="mailto:greg.king5@verizon.net" name="Greg King">
-<date>2018-02-12
+<date>2018-02-24
<abstract>
An overview over the PCE runtime system as it is implemented for the
<sect>Overview<p>
This file contains an overview of the PCE runtime system as it comes
-with the cc65 C compiler. It describes the memory layout, PCE specific header
+with the cc65 C compiler. It describes the memory layout, PCE-specific header
files, available drivers, and any pitfalls specific to that platform.
-Please note that PCE specific functions are just mentioned here, they are
-described in detail in the separate <url url="funcref.html" name="function
-reference">. Even functions marked as "platform dependent" may be available on
+Please note that PCE-specific functions are just mentioned here; they are
+described, in detail, in the separate <url url="funcref.html" name="function
+reference">. Even functions marked as "platform dependent" might be available on
more than one platform. Please see the function reference for more
information.
<sect>Memory layout<p>
-cc65 generated programs with the default setup run with the I/O area and a
+cc65-generated programs with the default setup run with the I/O area and a
CHR bank enabled, which gives a usable memory range of $8000 - $FFF3.
All boot ROM entry points may be called directly without additional code.
<descrip>
<tag/Text screen and Font/
- The text screen is located at VRAM $0000,
+ The text screen is located at VRAM $0000;
the Font is located at VRAM $2000.
<tag/Stack/
- The C runtime stack is located in system RAM at $3FFF and growing downwards.
+ The C runtime stack is located in system RAM at $3FFF; and, grows downwards.
<tag/Data and BSS/
The Data (initialized variables) and BSS (uninitialized variables) sections are
-<sect>Platform specific header files<p>
+<sect>Platform-specific header files<p>
-Programs containing PCE specific code may use the <tt/pce.h/ header file.
+Programs containing PCE-specific code may use the <tt/pce.h/ header file.
-<sect1>PCE specific functions<p>
+<sect1>PCE-specific functions<p>
<itemize>
<item>waitvsync</item>
</itemize>
-
<sect1>Hardware access<p>
-The following pseudo variables declared in the <tt/pce.inc/ include file do
-allow access to hardware located in the address space.
+The following pseudo variables, declared in the <tt/pce.inc/ include file, do
+allow access to hardware that is located in the address space.
<descrip>
<descrip>
<tag><tt/pce-stdjoy.joy (pce_stdjoy)/</tag>
- A joystick driver for the standard two buttons joypad is available.
+ A joystick driver for the standard two-button joypad is available.
- Note that the japanese 6-button pad is currently not supported.
+ Note that the Japanese 6-button pad currently is not supported.
</descrip><p>
<item>interruptor support in crt0 (and cfg) is missing
</itemize>
+
<sect1>Disk I/O<p>
The existing library for the PCE doesn't implement C file
<item>...
</itemize>
+
+
<sect>Other hints<p>
<itemize>
emulator to use for the PC-Engine.
</itemize>
-some useful resources on PCE coding:
+Some useful resources on PCE coding:
<itemize>
<item><url url="http://blog.blockos.org/?tag=pc-engine">
<item><url url="http://www.zeograd.com/parse.php?src=hucf">
</itemize>
+
+
<sect>License<p>
-This software is provided 'as-is', without any expressed or implied
+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.
freely, subject to the following restrictions:
<enum>
-<item> The origin of this software must not be misrepresented; you must not
- claim that you wrote the original software. If you use this software
- in a product, an acknowledgment in the product documentation would be
- appreciated but is not required.
-<item> Altered source versions must be plainly marked as such, and must not
- be misrepresented as being the original software.
-<item> This notice may not be removed or altered from any source
- distribution.
+<item>The origin of this software must not be misrepresented; you must not
+ claim that you wrote the original software. If you use this software
+ in a product, an acknowledgment in the product documentation would be
+ appreciated, but is not required.
+<item>Altered source versions must be marked plainly as such; and, must not
+ be misrepresented as being the original software.
+<item>This notice may not be removed or altered from any source
+ distribution.
</enum>
</article>