Mercurial > hg > Members > kono > nitros9-code
diff docs/nitros9guide/exbin.refentry @ 1014:d9ed9d44b70c
Some character entities had missing semicolons. It's &CPU;
The os9l1guide and os9l2guide are now much more modular simply because
the sections that are not to be included in one of them is defined as
the empty string in the <!ENTITY declaration
Split exbin and binex pages so the occur at the right place in the manual.
Got the content for wcreate from the Internet.
| author | roug |
|---|---|
| date | Tue, 04 Mar 2003 20:05:50 +0000 |
| parents | |
| children | b5ff125a1d60 |
line wrap: on
line diff
--- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/docs/nitros9guide/exbin.refentry Tue Mar 04 20:05:50 2003 +0000 @@ -0,0 +1,44 @@ +<refentry id="exbin"> +<refnamediv> +<refname id="exbinname">EXBIN</refname> +<refpurpose>Convert S-Record To Binary File</refpurpose> +</refnamediv> + +<refsynopsisdiv> +<cmdsynopsis> + <command>EXBIN</command> + <arg choice="plain"><replaceable>path2</replaceable></arg> + <arg choice="plain"><replaceable>path1</replaceable></arg> +</cmdsynopsis> +</refsynopsisdiv> + +<refsect1><title>Description</title> +<para> +S-Record files are a type of text file that contains records that +represent binary data in hexadecimal character form. This +Motorola-standard format is often directly accepted by commercial PROM +programmers, emulators, logic analyzers and similar devices that are +interfaced RS-232 interfaces. It can also be useful for +transmitting files over data links that can only handle character-type +data; or to convert OS-9 assembler or compiler-generated +programs to load on non-OS-9 systems. +</para> +<para> +"Path1" is assumed to be an +S-Record format text file which EXBIN converts to pure binary form on +a new file called "path2". The load addresses of each data record +must describe continguous data in ascending order. +</para> +<para> +EXBIN does not generate or check for the proper OS-9 module +headers or CRC check value required to actually load the binary +file. The IDENT or VERIFY commands can be used to check the +validity of the modules if they are to be loaded or run. +Example: +</para> +<screen> +exbin program.S1 cmds/program +</screen> +</refsect1> +</refentry> +