Mercurial > hg > Members > kono > nitros9-code
view docs/nitros9guide/exbin.refentry @ 2772:0a3f4d8ea6d5
Found ENDC in wrong location in dwread.asm and dwwrite.asm. Corrected.
Moved the native 6309 code in dwread.asm and dwwrite.asm into the H6309 labeled area and changed IFEQ H6309 to IFNE H6309. Also moved the 57600bps 6809 code to the default location. This change had been done in the old dwread.asm and dwwrite.asm files to make it easier to follow. Though these two files were overwritten from the HDBDOS project dwread.asm and dwwrite.asm files. So this conversion needed to be done again so it made the source easier to follow.
author | drencor-xeen |
---|---|
date | Wed, 23 Jan 2013 12:36:55 -0600 |
parents | b00cf13c9f61 |
children |
line wrap: on
line source
<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 NitrOS-9 assembler or compiler-generated programs to load on non-NitrOS-9 systems. </para> <para> "Path1" is assumed to be an S-Record format text file which <command>exbin</command> 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> <command>Exbin</command> does not generate or check for the proper NitrOS-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>