Scribd
Upload
190 views

Microprocessor Lab 3

This document describes the features of the emu8086 software. It discusses the different types of output files that can be generated - #make_com#, #make_exe#, and #make_bin#. It provides details on each file type, including how they are assembled, limitations, and how execution begins. The document also notes that the assembler reports errors separately and saves additional files (.asm, .debug, .binf) that enable viewing the original source code in the emulator.

Uploaded by

asddsa
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
190 views

Microprocessor Lab 3

This document describes the features of the emu8086 software. It discusses the different types of output files that can be generated - #make_com#, #make_exe#, and #make_bin#. It provides details on each file type, including how they are assembled, limitations, and how execution begins. The document also notes that the assembler reports errors separately and saves additional files (.asm, .debug, .binf) that enable viewing the original source code in the emulator.

Uploaded by

asddsa
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Experiment No.

03
Objective:
The brief understanding of all the features of emu8086 software.

Theory:
Type your code inside the text area, and click compile button. We will be asked for
a place where to save the compiled file. After successful compilation you can click emulate
button to load the compiled file in emulator.

The output files type directives:


#make_com#
#make_bin#
#make_boot#
#make_exe#
You can insert these directives in the source code to specify the required output type
for the file. Only if compiler cannot determine the output type automatically and it when it
cannot find any of these directives it may ask for you for output type before creating the
file.
There is virtually no difference between how .com and .bin are assembled because
these files are raw binary files, but .exe file has a special header in the beginning of the file
that is used by the operating system to determine some properties of the executable file.
Description of the output files types:
 #make_com# - the oldest and the simplest format of an executable file, such files
are loaded with 100h prefix (256 bytes). Select Clean from the New menu if you
plan to compile a COM file. Compiler directive ORG 100h should be added before
the code. Execution always starts from the first byte of the file. This file type is
selected automatically if org 100h directive is found in the code, supported by DOS
and Windows Command Prompt.
 #make_exe# - more advanced format of an executable file, not limited by size and
number of segments, stack segment should be defined in the program, you may
select exe template from the new menu in to create a simple exe program with pre-
defined data, stack and code segments, the entry point (where execution starts) is
defined by a programmer, this file type is selected automatically if stack segment is
found, supported by DOS and Windows Command Prompt.
 #make_bin# - a simple executable file. You can define the values of all
registers,segment and offset for memory area where this file will be loaded. When
loading “MY.BIN” file to emulator it will look for a “MY.BINF” file, and load
“MY.BIN” file to location specified in “MY.BINF” file, registers are also set using
information in that file (open this file in a text editor to edit or investigate), in case
the emulator is not able to find “MY.BINF” file, current register values are used
and “MY.BIN” file is loaded at current CS:IP, bin file type is not unique to the
emulator, however the directives are unique and will not work if .bin file is executed
outside of the emulator because their output is stored in a separate file independently
from pure binary code, .BINF file is created automatically if assembler finds any of
the following directives.
Assembly language compiler (or assembler) reports about errors in a separate
information window:
MOV DS, 100 – is illegal instruction because segment registers cannot be set directly,
general purpose register should be used, for example MOV AX, 100
MOV AL, 300 – is illegal instruction because AL register has only 8 bits, and thus
maximum value for its 255 (or 11111111b), and minimum is – 128.
When saving an assembled file, compiler also saves 2 other files that are later used
by the emulator to show original source code when you run the binary executable, and
select corresponding lines. Very often the original code differs from the disabled code
because there are no comments, no segment and no variable declarations. Compiler
directives produce no binary code, but everything is converted to pure machine code
instructions, this is done mainly for the compatibility with original 8086 microprocessor
(for example ROL AAL, 5 is assembled into five sequential ROL AL, 1 instruction).
 *.asm – this file contains the original source code that was used to make an
executable file.
 *.debug – this file has information that enables the emulator select lines of original
source code while running the machine code.
 *.binf – this ASCII file contains information that is used by emulator to build file
at specified location, and set register values prior emulation.

You might also like