mirror of
https://github.com/cc65/cc65.git
synced 2024-06-17 16:29:32 +00:00
remove dangling spaces
This commit is contained in:
parent
bfb8568a5f
commit
680f0c17f5
|
@ -84,7 +84,7 @@ The names are the usual ones you can find in system reference manuals. Example:
|
||||||
tics = OS.rtclok[1] // get ticks
|
tics = OS.rtclok[1] // get ticks
|
||||||
...
|
...
|
||||||
</verb></tscreen>
|
</verb></tscreen>
|
||||||
|
|
||||||
<sect1>Atari 5200 specific functions<p>
|
<sect1>Atari 5200 specific functions<p>
|
||||||
|
|
||||||
<itemize>
|
<itemize>
|
||||||
|
@ -221,7 +221,7 @@ you cannot use any of the following functions (and a few others):
|
||||||
|
|
||||||
<sect1>CAR format<p>
|
<sect1>CAR format<p>
|
||||||
|
|
||||||
AtariROMMaker (<url url="https://www.wudsn.com/index.php/productions-atari800/tools/atarirommaker"> )
|
AtariROMMaker (<url url="https://www.wudsn.com/index.php/productions-atari800/tools/atarirommaker"> )
|
||||||
can be used to create a <tt/.CAR/ file from the binary ROM image cc65 generates.
|
can be used to create a <tt/.CAR/ file from the binary ROM image cc65 generates.
|
||||||
This might be more convenient when working with emulators.
|
This might be more convenient when working with emulators.
|
||||||
|
|
||||||
|
|
|
@ -3622,7 +3622,7 @@ See: <tt><ref id=".ASCIIZ" name=".ASCIIZ"></tt>,<tt><ref id=".BYTE" name=".BYTE"
|
||||||
|
|
||||||
<sect1><tt>.PDTV</tt><label id=".PDTV"><p>
|
<sect1><tt>.PDTV</tt><label id=".PDTV"><p>
|
||||||
|
|
||||||
Enable the 6502DTV instruction set. This is a superset of the 6502
|
Enable the 6502DTV instruction set. This is a superset of the 6502
|
||||||
instruction set.
|
instruction set.
|
||||||
|
|
||||||
See: <tt><ref id=".P02" name=".P02"></tt>
|
See: <tt><ref id=".P02" name=".P02"></tt>
|
||||||
|
|
|
@ -119,9 +119,9 @@ Here is a description of all the command line options:
|
||||||
<item>4510
|
<item>4510
|
||||||
</itemize>
|
</itemize>
|
||||||
|
|
||||||
6502x is for the NMOS 6502 with unofficial opcodes. 6502dtv is for the
|
6502x is for the NMOS 6502 with unofficial opcodes. 6502dtv is for the
|
||||||
emulated CPU of the C64DTV device. huc6280 is the CPU of the PC engine.
|
emulated CPU of the C64DTV device. huc6280 is the CPU of the PC engine.
|
||||||
4510 is the CPU of the Commodore C65. Support for the 65816 currently
|
4510 is the CPU of the Commodore C65. Support for the 65816 currently
|
||||||
is not available.
|
is not available.
|
||||||
|
|
||||||
|
|
||||||
|
@ -253,8 +253,8 @@ for this CPU. Invalid opcodes are translated into <tt/.byte/ commands.
|
||||||
With the command line option <tt><ref id="option--cpu" name="--cpu"></tt>, the
|
With the command line option <tt><ref id="option--cpu" name="--cpu"></tt>, the
|
||||||
disassembler may be told to recognize either the 65SC02 or 65C02 CPUs. The
|
disassembler may be told to recognize either the 65SC02 or 65C02 CPUs. The
|
||||||
latter understands the same opcodes as the former, plus 16 additional bit
|
latter understands the same opcodes as the former, plus 16 additional bit
|
||||||
manipulation and bit test-and-branch commands. Using 6502x as CPU the illegal
|
manipulation and bit test-and-branch commands. Using 6502x as CPU the illegal
|
||||||
opcodes of 6502 CPU are detected and displayed. 6502dtv setting recognizes the
|
opcodes of 6502 CPU are detected and displayed. 6502dtv setting recognizes the
|
||||||
emulated CPU instructons of the C64DTV device.
|
emulated CPU instructons of the C64DTV device.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -1332,7 +1332,7 @@ This function returns the GEOS Kernal version combined (by logical OR) with the
|
||||||
<p>
|
<p>
|
||||||
This function returns the PAL/NTSC flag combined (by logical OR) with the 40/80 columns flag. This is
|
This function returns the PAL/NTSC flag combined (by logical OR) with the 40/80 columns flag. This is
|
||||||
not the best way to check if the screen has 40 or 80 columns since a PAL/NTSC check is always
|
not the best way to check if the screen has 40 or 80 columns since a PAL/NTSC check is always
|
||||||
performed and it can take as long as a full raster frame. If you just want to know if the
|
performed and it can take as long as a full raster frame. If you just want to know if the
|
||||||
screen has 40 or 80 columns use the expression <tt/graphMode & 0x80/ which returns <tt/0/ for
|
screen has 40 or 80 columns use the expression <tt/graphMode & 0x80/ which returns <tt/0/ for
|
||||||
40 columns and <tt/0x80/ for 80 columns. Remember that this value can be changed during
|
40 columns and <tt/0x80/ for 80 columns. Remember that this value can be changed during
|
||||||
runtime. It is unclear if this will work for GEOS 64 so you probably do not want to test
|
runtime. It is unclear if this will work for GEOS 64 so you probably do not want to test
|
||||||
|
|
|
@ -410,7 +410,7 @@ Available at <url
|
||||||
url="https://github.com/commanderx16/x16-emulator/releases">:
|
url="https://github.com/commanderx16/x16-emulator/releases">:
|
||||||
|
|
||||||
Emulates the Commander X16 Single Board Computer, with sound, SD card images,
|
Emulates the Commander X16 Single Board Computer, with sound, SD card images,
|
||||||
VGA and NTSC video, and a NES game controller emulation. Includes a monitor.
|
VGA and NTSC video, and a NES game controller emulation. Includes a monitor.
|
||||||
It runs on all SDL2 platforms.
|
It runs on all SDL2 platforms.
|
||||||
|
|
||||||
Compile the tutorial with
|
Compile the tutorial with
|
||||||
|
@ -459,7 +459,7 @@ Substitute the name of a Commodore computer for that <tt/<sys>/:
|
||||||
Start the desired version of the emulator (CBM610 programs run on
|
Start the desired version of the emulator (CBM610 programs run on
|
||||||
the CBM II [<tt/xcbm2/] emulator).
|
the CBM II [<tt/xcbm2/] emulator).
|
||||||
|
|
||||||
Choose <bf>File>Autostart disk/tape image...</bf>, choose your executable,
|
Choose <bf>File>Autostart disk/tape image...</bf>, choose your executable,
|
||||||
and click <bf/OK/.
|
and click <bf/OK/.
|
||||||
|
|
||||||
The file has a 14-byte header which corresponds to a PRG-format BASIC program,
|
The file has a 14-byte header which corresponds to a PRG-format BASIC program,
|
||||||
|
|
|
@ -36,7 +36,7 @@ Here is a small traditional Hello World program for the Atari Lynx.
|
||||||
<tscreen><verb>
|
<tscreen><verb>
|
||||||
#include <lynx.h>
|
#include <lynx.h>
|
||||||
#include <tgi.h>
|
#include <tgi.h>
|
||||||
#include <6502.h>
|
#include <6502.h>
|
||||||
|
|
||||||
void main(void) {
|
void main(void) {
|
||||||
tgi_install(tgi_static_stddrv);
|
tgi_install(tgi_static_stddrv);
|
||||||
|
|
|
@ -112,7 +112,7 @@ For a C test compiled and linked with <tt/--target sim6502/ the
|
||||||
command line arguments to <tt/sim65/ will be passed to <tt/main/,
|
command line arguments to <tt/sim65/ will be passed to <tt/main/,
|
||||||
and the return value from <tt/main/ will become sim65's exit code.
|
and the return value from <tt/main/ will become sim65's exit code.
|
||||||
The <tt/exit/ function may also be used to terminate with an exit code.
|
The <tt/exit/ function may also be used to terminate with an exit code.
|
||||||
|
|
||||||
Exit codes are limited to 8 bits.
|
Exit codes are limited to 8 bits.
|
||||||
|
|
||||||
The standard C library high level file input and output is functional.
|
The standard C library high level file input and output is functional.
|
||||||
|
|
|
@ -48,7 +48,7 @@ using 4k config run in the memory range of $200 - $0FFF. The 32k
|
||||||
this range to $7FFF. Memory above 32k can be used to extend the heap, as described below.
|
this range to $7FFF. Memory above 32k can be used to extend the heap, as described below.
|
||||||
The starting memory location and entry point for running the program is $200, so when the
|
The starting memory location and entry point for running the program is $200, so when the
|
||||||
program is transferred to the Sym-1, it is executed by typing 'g 200'. The system returns control
|
program is transferred to the Sym-1, it is executed by typing 'g 200'. The system returns control
|
||||||
back to the monitor ROM when the program terminates, providing the '.' prompt.
|
back to the monitor ROM when the program terminates, providing the '.' prompt.
|
||||||
|
|
||||||
Special locations:
|
Special locations:
|
||||||
|
|
||||||
|
@ -58,7 +58,7 @@ Special locations:
|
||||||
|
|
||||||
<tag/Stack/
|
<tag/Stack/
|
||||||
The C runtime stack is located at $0FFF on 4kb Syms, or at $7FFF for 32kb systems.
|
The C runtime stack is located at $0FFF on 4kb Syms, or at $7FFF for 32kb systems.
|
||||||
The stack always grows downwards.
|
The stack always grows downwards.
|
||||||
|
|
||||||
<tag/Heap/
|
<tag/Heap/
|
||||||
The C heap is located at the end of the program and grows towards the C runtime stack. Extended
|
The C heap is located at the end of the program and grows towards the C runtime stack. Extended
|
||||||
|
|
|
@ -192,9 +192,9 @@ port cardridge.
|
||||||
Telemon 2.4 returns in keyboard buffer the direction of the joysticks. This means that
|
Telemon 2.4 returns in keyboard buffer the direction of the joysticks. This means that
|
||||||
if you get input from keyboard by conio cgetc function, you will get direction from joysticks.
|
if you get input from keyboard by conio cgetc function, you will get direction from joysticks.
|
||||||
|
|
||||||
Anyway, if you don't want to use ROM, you can use joysticks standard drivers in your code.
|
Anyway, if you don't want to use ROM, you can use joysticks standard drivers in your code.
|
||||||
|
|
||||||
The standard driver manages two joysticks. Only one button is managed for these joysticks.
|
The standard driver manages two joysticks. Only one button is managed for these joysticks.
|
||||||
|
|
||||||
Telestrat can handle one button for the left port, and three buttons for the right port (but this port was designed for a mouse).
|
Telestrat can handle one button for the left port, and three buttons for the right port (but this port was designed for a mouse).
|
||||||
|
|
||||||
|
@ -217,7 +217,7 @@ RS232 port with Telemon calls (see XSOUT primitive for example)
|
||||||
Telemon 3.0 handles fopen, fread, fclose primitives. It means that this
|
Telemon 3.0 handles fopen, fread, fclose primitives. It means that this
|
||||||
function will crash the Telestrat because Telemon 2.4 does not have these
|
function will crash the Telestrat because Telemon 2.4 does not have these
|
||||||
primitives. By the way, Telemon 3.0 uses an extension "ch376 card" which
|
primitives. By the way, Telemon 3.0 uses an extension "ch376 card" which
|
||||||
handles sdcard and FAT 32 usb key. In the next version of Telemon, FT DOS,
|
handles sdcard and FAT 32 usb key. In the next version of Telemon, FT DOS,
|
||||||
Sedoric, Stratsed will be handled in these 3 primitives (fopen, fread, fclose).
|
Sedoric, Stratsed will be handled in these 3 primitives (fopen, fread, fclose).
|
||||||
|
|
||||||
<itemize>
|
<itemize>
|
||||||
|
@ -227,10 +227,10 @@ Sedoric, Stratsed will be handled in these 3 primitives (fopen, fread, fclose).
|
||||||
</itemize>
|
</itemize>
|
||||||
|
|
||||||
<sect1>conio<p>
|
<sect1>conio<p>
|
||||||
Functions textcolor and bgcolor are available only with Telemon 3.0 (Orix).
|
Functions textcolor and bgcolor are available only with Telemon 3.0 (Orix).
|
||||||
Telemon 2.4 primitives can't handle any change of colors in text mode except with XINK or
|
Telemon 2.4 primitives can't handle any change of colors in text mode except with XINK or
|
||||||
XPAPER primitives which put on the first and second columns ink and paper attributes.
|
XPAPER primitives which put on the first and second columns ink and paper attributes.
|
||||||
The only way to change color on the same line for text is to handle it in pure assembly
|
The only way to change color on the same line for text is to handle it in pure assembly
|
||||||
without systems calls.
|
without systems calls.
|
||||||
|
|
||||||
<sect>Other hints<p>
|
<sect>Other hints<p>
|
||||||
|
|
Loading…
Reference in New Issue
Block a user