Mercurial > hg > Members > kono > nitros9-code
annotate docs/nitros9guide/binex.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 | c565a4700689 |
children | b5ff125a1d60 |
rev | line source |
---|---|
134 | 1 <refentry id="binex"> |
2 <refnamediv> | |
1014
d9ed9d44b70c
Some character entities had missing semicolons. It's &CPU;
roug
parents:
975
diff
changeset
|
3 <refname id="binexname">BINEX</refname> |
d9ed9d44b70c
Some character entities had missing semicolons. It's &CPU;
roug
parents:
975
diff
changeset
|
4 <refpurpose>Convert Binary To S-Record File</refpurpose> |
134 | 5 </refnamediv> |
6 | |
7 <refsynopsisdiv> | |
8 <cmdsynopsis> | |
9 <command>BINEX</command> | |
975
c565a4700689
The entitity replstart was replaced with <replaceable>
roug
parents:
134
diff
changeset
|
10 <arg choice="plain"><replaceable>path1</replaceable></arg> |
c565a4700689
The entitity replstart was replaced with <replaceable>
roug
parents:
134
diff
changeset
|
11 <arg choice="plain"><replaceable>path2</replaceable></arg> |
134 | 12 </cmdsynopsis> |
13 </refsynopsisdiv> | |
14 | |
15 <refsect1><title>Description</title> | |
16 <para> | |
17 S-Record files are a type of text file that contains records that | |
18 represent binary data in hexadecimal character form. This | |
19 Motorola-standard format is often directly accepted by commercial PROM | |
20 programmers, emulators, logic analyzers and similar devices that are | |
21 interfaced RS-232 interfaces. It can also be useful for | |
22 transmitting files over data links that can only handle character-type | |
23 data; or to convert OS-9 assembler or compiler-generated | |
24 programs to load on non-OS-9 systems. | |
25 </para> | |
26 <para> | |
27 BINEX converts "path1", an OS-9 binary format file, to a new file | |
28 named "path2" in S-Record format. If invoked on a non-binary load | |
29 module file, a warning message is printed and the user is asked if | |
30 BINEX should proceed anyway. A "Y" response means yes; any other | |
31 answer will terminate the program. S-Records have a header record | |
32 to store the program name for informational purposes and each data | |
33 record has an absolute memory address which is not meaningful to OS-9 | |
34 since it uses position-independent-code. However, the S-Record | |
35 format requires them so BINEX will prompt the user for a program | |
36 name and starting load address. For example: | |
37 </para> | |
38 <screen> | |
39 binex /d0/cmds/scanner scanner.S1 | |
40 Enter starting address for file: <emphasis>$100</emphasis> | |
41 Enter name for header record: <emphasis>scanner</emphasis> | |
42 </screen> | |
43 <para> | |
44 To download the program to a device such as a PROM programmer | |
45 (for example using serial port T1) type: | |
46 </para> | |
47 <screen> | |
48 list scanner.S1 >/T1 | |
49 </screen> | |
50 </refsect1> | |
51 </refentry> | |
52 |