Mercurial > hg > Members > kono > nitros9-code

comparison docs/nitros9guide/exbin.refentry @ 1500:b00cf13c9f61

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Major changes for new NitrOS-9 manual
author boisy
date Mon, 05 Jan 2004 00:51:19 +0000
parents 4dae346c4969
children
comparison
equal deleted inserted replaced
1499:6cd590fc076f 1500:b00cf13c9f61
18 represent binary data in hexadecimal character form. This 18 represent binary data in hexadecimal character form. This
19 Motorola-standard format is often directly accepted by commercial PROM 19 Motorola-standard format is often directly accepted by commercial PROM
20 programmers, emulators, logic analyzers and similar devices that are 20 programmers, emulators, logic analyzers and similar devices that are
21 interfaced RS-232 interfaces. It can also be useful for 21 interfaced RS-232 interfaces. It can also be useful for
22 transmitting files over data links that can only handle character-type 22 transmitting files over data links that can only handle character-type
23 data; or to convert OS-9 assembler or compiler-generated 23 data; or to convert NitrOS-9 assembler or compiler-generated
24 programs to load on non-OS-9 systems. 24 programs to load on non-NitrOS-9 systems.
25 </para> 25 </para>
26 <para> 26 <para>
27 &quot;Path1&quot; is assumed to be an 27 &quot;Path1&quot; is assumed to be an
28 S-Record format text file which <command>exbin</command> converts to pure binary form on 28 S-Record format text file which <command>exbin</command> converts to pure binary form on
29 a new file called &quot;path2&quot;. The load addresses of each data record 29 a new file called &quot;path2&quot;. The load addresses of each data record
30 must describe continguous data in ascending order. 30 must describe continguous data in ascending order.
31 </para> 31 </para>
32 <para> 32 <para>
33 <command>Exbin</command> does not generate or check for the proper OS-9 module 33 <command>Exbin</command> does not generate or check for the proper NitrOS-9 module
34 headers or CRC check value required to actually load the binary 34 headers or CRC check value required to actually load the binary
35 file. The IDENT or VERIFY commands can be used to check the 35 file. The IDENT or VERIFY commands can be used to check the
36 validity of the modules if they are to be loaded or run. 36 validity of the modules if they are to be loaded or run.
37 Example: 37 Example:
38 </para> 38 </para>