home *** CD-ROM | disk | FTP | other *** search
-
- The Z80MR creates two output files from an assembly language source file
- with a .AZM extention. The assembly language file can be any combination
- of Z80 mnemonics or assembler commands and pseudo-ops in the correct form
- as described in the file Z80MR.DOC. Each line of the source program is
- seperated by a carriage return linefeed and can be created on any editor.
-
- The object file is the executable machine code represented by ascii
- characters in a form known as Intel Hex Format. The object file will
- have the same filename as the source file but will have a .HEX extension.
- This format must be translated into the actual machine executable
- binary values in order to be run on a computer. This can be done with
- LOAD.COM or DDT.COM which came with your CP/M. (described later). Many
- EPROM burners only except the program to be burned in Hex format.
-
- The listing file is the other ouput by the assembler. It is ascii
- representation of the code actually produced by the assembler. There
- are many options available for controlling what is included in the
- listing file as described in Z80MR.DOC. The listing file will have the
- same filename as the source file but will have a .PRN extension.
-
- Invoking the Assembler.....................................................
-
- To assemble the file TEST.AZM the following command can be used:
-
- Z80MR TEST <carriage return>
-
- The assembler will read in the file TEST.AZM from the current drive and
- create an object file TEST.HEX and a listing file TEST.PRN.
-
- Controlling Output.........................................................
-
- Either of the output files (or both) may be omitted. In addition, the files
- may be located on different drives. Since the source file must always have
- a .AZM extention we may use the extention to control the output.
-
- Z80MR TEST.sol
-
- The letter in the 's' position tells the assembler where to find the source
- file and may be any disk drive letter from A to D. The letter in the 'o'
- position tells the assembler where to locate the object file and may be
- A-D as above or Z if the file is not desired. The letter in the 'l' position
- tells the assembler what to do with the listing file. It can be any drive
- letter from A-D or Z if the file is not desired. In addition the listing
- file may be sent to the console if an X is in that position.
-
- Loading Hex Files..........................................................
-
- The object file must be translated from Hex format to machine executable
- values by another program. If the program was written to ORG at 100H the
- program may be loaded with the CP/M utility LOAD.COM. All of the programs
- on this disk with a .COM extension are ORGed at 100H. This is where CPM
- loads its transient programs. To load TEST.HEX with LOAD.COM just enter
-
- LOAD TEST
-
- The extention of .HEX is assumed.
-
- If you have a program that does not ORG at 100H you must use DDT to read
- in the .HEX file which it does by translating the Hex format to binary
- as it reads it into memory. Once in memory you may manipulate it with
- DDT even SAVE an image of the program in memory actually creating a .COM
- file. If you write a program that ORGs where CP/M resides you can wipe
- out CP/M and have to reset the computer to recover. See the file PHASE.DOC
- for some more information on ORGing files at High memory locations.
-
- :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
-