|
134
|
1 <refentry id="binex">
|
|
|
2 <refnamediv>
|
|
|
3 <refname id="binexname">BINEX / EXBIN</refname>
|
|
|
4 <refpurpose>Convert Binary To S-Record File / Convert S-Record To Binary File</refpurpose>
|
|
|
5 </refnamediv>
|
|
|
6
|
|
|
7 <refsynopsisdiv>
|
|
|
8 <cmdsynopsis>
|
|
|
9 <command>BINEX</command>
|
|
|
10 <arg choice="plain">&replstart;path1&replend;</arg>
|
|
|
11 <arg choice="plain">&replstart;path2&replend;</arg>
|
|
|
12 </cmdsynopsis>
|
|
|
13 <cmdsynopsis>
|
|
|
14 <command>EXBIN</command>
|
|
|
15 <arg choice="plain">&replstart;path2&replend;</arg>
|
|
|
16 <arg choice="plain">&replstart;path1&replend;</arg>
|
|
|
17 </cmdsynopsis>
|
|
|
18 </refsynopsisdiv>
|
|
|
19
|
|
|
20 <refsect1><title>Description</title>
|
|
|
21 <para>
|
|
|
22 S-Record files are a type of text file that contains records that
|
|
|
23 represent binary data in hexadecimal character form. This
|
|
|
24 Motorola-standard format is often directly accepted by commercial PROM
|
|
|
25 programmers, emulators, logic analyzers and similar devices that are
|
|
|
26 interfaced RS-232 interfaces. It can also be useful for
|
|
|
27 transmitting files over data links that can only handle character-type
|
|
|
28 data; or to convert OS-9 assembler or compiler-generated
|
|
|
29 programs to load on non-OS-9 systems.
|
|
|
30 </para>
|
|
|
31 <para>
|
|
|
32 BINEX converts "path1", an OS-9 binary format file, to a new file
|
|
|
33 named "path2" in S-Record format. If invoked on a non-binary load
|
|
|
34 module file, a warning message is printed and the user is asked if
|
|
|
35 BINEX should proceed anyway. A "Y" response means yes; any other
|
|
|
36 answer will terminate the program. S-Records have a header record
|
|
|
37 to store the program name for informational purposes and each data
|
|
|
38 record has an absolute memory address which is not meaningful to OS-9
|
|
|
39 since it uses position-independent-code. However, the S-Record
|
|
|
40 format requires them so BINEX will prompt the user for a program
|
|
|
41 name and starting load address. For example:
|
|
|
42 </para>
|
|
|
43 <screen>
|
|
|
44 binex /d0/cmds/scanner scanner.S1
|
|
|
45 Enter starting address for file: <emphasis>$100</emphasis>
|
|
|
46 Enter name for header record: <emphasis>scanner</emphasis>
|
|
|
47 </screen>
|
|
|
48 <para>
|
|
|
49 To download the program to a device such as a PROM programmer
|
|
|
50 (for example using serial port T1) type:
|
|
|
51 </para>
|
|
|
52 <screen>
|
|
|
53 list scanner.S1 >/T1
|
|
|
54 </screen>
|
|
|
55 <para>
|
|
|
56 EXBIN is the inverse operation; "path1" is assumed to be a
|
|
|
57 S-Record format text file which EXBIN converts to pure binary form on
|
|
|
58 a new file called "path2". The load addresses of each data record
|
|
|
59 must describe continguous data in ascending order.
|
|
|
60 </para>
|
|
|
61 <para>
|
|
|
62 EXBIN does not generate or check for the proper OS-9 module
|
|
|
63 headers or CRC check value required to actually load the binary
|
|
|
64 file. The IDENT or VERIFY commands can be used to check the
|
|
|
65 validity of the modules if they are to be loaded or run.
|
|
|
66 Example:
|
|
|
67 </para>
|
|
|
68 <screen>
|
|
|
69 exbin program.S1 cmds/program
|
|
|
70 </screen>
|
|
|
71 </refsect1>
|
|
|
72 </refentry>
|
|
|
73
|
