<!doctype linuxdoc system>
<article>
-
<title>Oric Telestrat-specific information for cc65
<author>
-<url url="mailto:jede@oric.org" name="Jede">,<newline>
-
-<date>2017-01-22
+<url url="mailto:jede@oric.org" name="Jede">
<abstract>
-An overview over the Telestrat (telemon 3.0 : http://orix.oric.org) runtime system as it is implemented for the cc65 C
-compiler.
+An overview over the Telestrat (Telemon 2.4 & Telemon 3.x : http://orix.oric.org) runtime system as it is implemented for the cc65 C compiler.
</abstract>
<!-- Table of contents -->
<sect>Overview<p>
This file contains an overview of the Telestrat runtime system as it comes with the
-cc65 C compiler. It describes the memory layout, Telemon3.0-specific header files,
+cc65 C compiler. It describes the memory layout, Telestrat-specific header files,
available drivers, and any pitfalls specific to that platform.
-Please note that Telemon3.0-specific functions are just mentioned here, they are
+Please note that Telestrat-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
more than one platform. Please see the function reference for more
information.
+<sect>Binary format<p>
+
+The standard binary output format generated the linker for the Telestrat
+target is a machine language program with a 20 bytes header described <url
+name="here" url="http://orix.oric.org/doku.php?id=orix:header">
+This header is used for Telemon 3.0.
-<sect>Binary format<p>
+Anyway, for Telemon 2.4, there is no file management, there is no TAPE routine in Telemon, there is no way to load a binary easily.
+
+Stratsed (the Telestrat operating system) handles files management. Stratsed is loaded to memory from floppy disk.
-The standard binary output format generated by the linker for the Telemon 3.0 target
-is a machine language program with a 20 bytes header described here : http://orix.oric.org/doku.php?id=orix:header
+There is no tool to insert a binary in a Stratsed floppy disk.
+The only way to load a binary (for Telemon 2.4) is to:
+<itemize>
+<item>remove the 20 bytes header
+<item>download <url name="osdk" url="http://osdk.defence-force.org/index?page=download">
+<item>use Floppybuilder in OSDK to insert the binary with the tool (please read FloppyBuilder manual to insert your binary, and to start microdisc boot sector when Telestrat starts)
+</itemize>
+
+Please note also, that the binary converted into TAP file, will not produce
+a right stratsed file when tap2dsk and old2mfm are used. You will be in the
+case that Telestrat/Stratsed crashed when you do "DIR" command.
+
+If you know the Stratsed disk format, please contact the author of this doc.
<sect>Memory layout<p>
available. ROM calls are possible without further precautions.
-
Special locations:
<descrip>
<sect>Platform-specific header files<p>
-Programs containing Telemon 3.0 -specific code may use the <tt/telemon.h/ header file.
+Programs containing Telestrat-specific code may use the <tt/telestrat.h/ header file.
-<sect1>Tele
mon 3.0-specific functions<p>
+<sect1>Tele
strat-specific functions<p>
-The functions listed below are special for the Telemon 3.0. See the <url
+The functions listed below are special for the Telestrat. See the <url
url="funcref.html" name="function reference"> for declaration and usage.
<itemize>
<item>ping
<item>shoot
<item>zap
-<item>oupsx
+<item>oups
</itemize>
<sect1>Hardware access<p>
-The following pseudo variables declared in the <tt/atmos.h/ header file do allow
+The following pseudo variables declared in the <tt/telestrat.h/ header file do allow
access to hardware located in the address space. Some variables are
structures; accessing the struct fields will access the chip registers.
</descrip><p>
-
<sect>Loadable drivers<p>
-<em>Note:</em> Since the Atmos doesn't have working disk I/O
-(see <ref id="limitations" name="section "Limitations"">), the
-available drivers cannot be loaded at runtime (so the term "loadable drivers"
-is somewhat misleading). Instead, the drivers have to be statically linked. While
-this may seem overhead, it has two advantages:
+<sect1>TGI<p>
+
+TGI drivers is available on Oric Telestrat with some functions :
+
+<itemize>
+<item>tgi_done
+<item>tgi_install
+<item>tgi_init
+<item>tgi_clear
+<item>tgi_line
+<item>tgi_setpixel
+</itemize>
<sect1>Extended memory drivers<p>
-No extended memory drivers are currently available for the Atmos.
+No extended memory drivers are currently available for the Telestrat.
<sect1>Joystick drivers<p>
<descrip>
-telemon 3.0 manages joysticks but it had been handled yet.
+telemon 2.4 & 3.0 manages joysticks but it had been handled yet.
-</descrip><p>
+</descrip>
<sect1>Mouse drivers<p>
-Telemon 3.0 manages also mouse, but it had been no handled yet in this version.
+<descrip>
+
+Telestrat manages also mouse, but it had been no handled yet in this version.
+
+</descrip>
<sect1>RS232 device drivers<p>
<descrip>
-not done
-
-</descrip><p>
-
+Telestrat has a RS232 port, but it's not usable in cc65.
+</descrip>
<sect>Limitations<label id="limitations"><p>
<sect1>Disk I/O<p>
-This version handles fopen, fread, fclose primitives. Because Telemon 3.0 handles these two primitives. By the way,
-it uses an extension "ch376 card" which handles sdcard and FAT 32 usb key.
+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
+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,
+Sedoric, Stratsed will be handled in these 3 primitives (fopen, fread,
+fclose).
<itemize>
<item>fclose
<item>fopen
<item>fread
-
</itemize>
projects / cc65 / blobdiff