Answer Q1 - Q3 (From Tutorial Available in Emulator) What Is Assembly Language?
Answer Q1 - Q3 (From Tutorial Available in Emulator) What Is Assembly Language?
assembly language is a low level programming language. you need to get some
knowledge about computer structure in order to understand anything. the simple
computer model as i see it:
Goutam Sanyal
the system bus (shown in yellow) connects the various components of a
computer.
The CPU is the heart of the computer, most of computations occur inside
the CPU.
RAM is a place to where the programs are loaded in order to be executed.
Goutam Sanyal
8086 CPU has 8 general purpose registers, each register has its own name:
despite the name of a register, it's the programmer who determines the usage for
each general purpose register. the main purpose of a register is to keep a number
(variable). the size of the above registers is 16 bit, it's something
like: 0011000000111001b (in binary form), or 12345 in decimal (human) form.
4 general purpose registers (AX, BX, CX, DX) are made of two separate 8 bit
registers, for example if AX= 0011000000111001b, then AH=00110000b and
AL=00111001b. therefore, when you modify any of the 8 bit registers 16 bit
register is also updated, and vice-versa. the same is for other 3 registers, "H" is for
high and "L" is for low part.
because registers are located inside the cpu, they are much faster than memory.
accessing a memory location requires the use of a system bus, so it takes much
longer. accessing data in a register usually takes no time. therefore, you should
try to keep variables in the registers. register sets are very small and most
registers have special purposes which limit their use as variables, but they are still
an excellent place to store temporary data of calculations.
segment registers
although it is possible to store any data in the segment registers, this is never a
good idea. the segment registers have a very special purpose - pointing at
accessible blocks of memory.
segment registers work together with general purpose register to access any
memory value. For example if we would like to access memory at the physical
address 12345h (hexadecimal), we should set the DS = 1230h and SI = 0045h. This
is good, since this way we can access much more memory than with a single
register that is limited to 16 bit values.
CPU makes a calculation of physical address by multiplying the segment register
by 10h and adding general purpose register to it(1230h * 10h + 45h = 12345h):
Goutam Sanyal
and other general registers, but it is possible to change values of system registers
using some tricks that you will learn a little bit later.
Memory Access
to access memory we can use these four registers: BX, SI, DI, BP.
combining these registers inside [ ] symbols, we can get different memory
locations. these combinations are supported (addressing modes):
d8 - stays for 8 bit signed immediate displacement (for example: 22, 55h, -1,
etc...)
d16 - stays for 16 bit signed immediate displacement (for example: 300, 5517h, -
259, etc...).
generally the compiler takes care about difference between d8 and d16, and
Goutam Sanyal
generates the required machine code.
there is an easy way to remember all those possible combinations using this
chart:
you can form all valid combinations by taking only one item from each column or
skipping the column by not taking anything from it. as you see BX and BPnever go
together. SI and DI also don't go together. here are an examples of a valid
addressing modes: [BX+5] , [BX+SI] , [DI+BX-4]
the value in segment register (CS, DS, SS, ES) is called a segment,
and the value in purpose register (BX, SI, DI, BP) is called an offset.
When DS contains value 1234h and SI contains the value 7890h it can be also
recorded as 1234:7890. The physical address will be 1234h * 10h + 7890h =
19BD0h.
7h = 7
70h = 112
Goutam Sanyal
in order to say the compiler about data type,
these prefixes should be used:
for example:
sometimes compiler can calculate the data type automatically, but you may not
and should not rely on that when one of the operands is an immediate value.
MOV instruction
Goutam Sanyal
both operands must be the same size, which can be a byte or a word.
REG: AX, BX, CX, DX, AH, AL, BL, BH, CH, CL, DH, DL, DI, SI, BP, SP.
the MOV instruction cannot be used to set the value of the CS and IP registers.
ORG 100h ; this directive required for a simple 1 segment .com program.
MOV AX, 0B800h ; set AX to hexadecimal value of B800h.
Goutam Sanyal
MOV DS, AX ; copy value of AX to DS.
MOV CL, 'A' ; set CL to ASCII code of 'A', it is 41h.
MOV CH, 1101_1111b ; set CH to binary value.
MOV BX, 15Eh ; set BX to 15Eh.
MOV [BX], CX ; copy contents of CX to memory at B800:015E
RET ; returns to operating system.
you can copy & paste the above program to the code editor, and press [Compile
and Emulate] button (or press F5 key on your keyboard).
the emulator window should open with this program loaded, click [Single
Step] button and watch the register values.
1. select the above text using mouse, click before the text and drag it down
until everything is selected.
as you may guess, ";" is used for comments, anything after ";" symbol is ignored
by compiler.
Goutam Sanyal
actually the above program writes directly to video memory, so you may see
that MOV is a very powerful instruction.
Variables
name DB value
name DW value
name - can be any letter or digit combination, though it should start with a letter.
It's possible to declare unnamed variables by not specifying the name (this
variable will have an address but no name).
Goutam Sanyal
value - can be any numeric value in any supported numbering system
(hexadecimal, binary, or decimal), or "?" symbol for variables that are not
initialized.
As you probably know from part 2 of this tutorial, MOV instruction is used to copy
values from source to destination.
Let's see another example with MOV instruction:
ORG 100h
VAR1 DB 7
var2 DW 1234h
Copy the above code to the source editor, and press F5 key to compile it and load
in the emulator. You should get something like:
Goutam Sanyal
As you see this looks a lot like our example, except that variables are replaced
with actual memory locations. When compiler makes machine code, it
automatically replaces all variable names with their offsets. By default segment is
loaded in DS register (when COM files is loaded the value of DS register is set to
the same value as CS register - code segment).
In memory list first row is an offset, second row is a hexadecimal value, third row
is decimal value, and last row is an ASCII character value.
Compiler is not case sensitive, so "VAR1" and "var1" refer to the same variable.
The offset of var2 is 0109h, and full address is 0B56:0109, this variable is
a WORD so it occupies 2 BYTES. It is assumed that low byte is stored at lower
address, so 34h is located before 12h.
You can see that there are some other instructions after the RET instruction, this
happens because disassembler has no idea about where the data starts, it just
processes the values in memory and it understands them as valid 8086
instructions (we will learn them later).
Goutam Sanyal
You can even write the same program using DB directive only:
ORG 100h
DB 0A0h
DB 08h
DB 01h
DB 8Bh
DB 1Eh
DB 09h
DB 01h
DB 0C3h
DB 7
DB 34h
DB 12h
Copy the above code to the source editor, and press F5 key to compile and load it
in the emulator. You should get the same disassembled code, and the same
functionality!
As you may guess, the compiler just converts the program source to the set of
bytes, this set is called machine code, processor understands the machine
codeand executes it.
ORG 100h is a compiler directive (it tells compiler how to handle the source
code). This directive is very important when you work with variables. It tells
compiler that the executable file will be loaded at the offset of 100h (256 bytes),
so compiler should calculate the correct address for all variables when it replaces
the variable names with their offsets. Directives are never converted to any
real machine code.
Why executable file is loaded at offset of 100h? Operating system keeps some
Goutam Sanyal
data about the program in the first 256 bytes of the CS (code segment), such as
command line parameters and etc.
Though this is true for COM files only, EXE files are loaded at offset of 0000, and
generally use special segment for variables. Maybe we'll talk more about EXEfiles
later.
Arrays
b is an exact copy of the a array, when compiler sees a string inside quotes it
automatically converts it to set of bytes. This chart shows a part of the memory
where these arrays are declared:
You can access the value of any element in array using square brackets, for
example:
MOV AL, a[3]
You can also use any of the memory index registers BX, SI, DI, BP, for example:
MOV SI, 3
MOV AL, a[SI]
Goutam Sanyal
If you need to declare a large array you can use DUP operator.
The syntax for DUP:
for example:
c DB 5 DUP(9)
is an alternative way of declaring:
c DB 9, 9, 9, 9, 9
Of course, you can use DW instead of DB if it's required to keep values larger then
255, or smaller then -128. DW cannot be used to declare strings.
There is LEA (Load Effective Address) instruction and alternative OFFSET operator.
Both OFFSET and LEA can be used to get the offset address of the variable.
LEA is more powerful because it also allows you to get the address of an indexed
variables. Getting the address of the variable can be very useful in some
situations, for example when you need to pass parameters to a procedure.
Reminder:
In order to tell the compiler about data type,
these prefixes should be used:
Goutam Sanyal
WORD PTR - for word (two bytes).
For example:
BYTE PTR [BX] ; byte access.
or
WORD PTR [BX] ; word access.
assembler supports shorter prefixes as well:
sometimes compiler can calculate the data type automatically, but you may not
and should not rely on that when one of the operands is an immediate value.
ORG 100h
RET
Goutam Sanyal
VAR1 DB 22h
END
ORG 100h
RET
VAR1 DB 22h
END
These lines:
LEA BX, VAR1
MOV BX, OFFSET VAR1
are even compiled into the same machine code: MOV BX, num
Goutam Sanyal
num is a 16 bit value of the variable offset.
Please note that only these registers can be used inside square brackets (as
memory pointers): BX, SI, DI, BP!
(see previous part of the tutorial).
Constants
Constants are just like variables, but they exist only until your program is
compiled (assembled). After definition of a constant its value cannot be changed.
To define constants EQU directive is used:
For example:
k EQU 5
MOV AX, k
MOV AX, 5
You can view variables while your program executes by selecting "Variables" from
the "View" menu of emulator.
Goutam Sanyal
To view arrays you should click on a variable and set Elements property to array
size. In assembly language there are not strict data types, so any variable can be
presented as an array.
You can edit a variable's value when your program is running, simply double click
it, or select it and click Edit button.
.STACK
.DATA
.CODE
MOV DS, AX
Goutam Sanyal
MOV AH, 09H ; for string display
INT 21H
mov ah ,1
int 21h ; dos interrupt function
INT 21H
.model small
.data
Goutam Sanyal
.stack 100H
.code
MAIN PROC
MOV AX ,@DATA
MOV DS,AX
LEA DX,MSG
MOV AH,9
INT 21H
MOV AH,1
INT 21H
MOV BL,AL
INT 21H
MOV CL,AL
ADD BL,CL
SUB BL,48
MOV AH,2
MOV DL,BL
INT 21H
MOV AH,4CH
INT 21H
MAIN ENDP
END MAIN
Goutam Sanyal
3. Program to input numbers into an array and display
INCLUDE 'EMU8086.INC'
.MODEL SMALL
.STACK 100H
.DATA
NUMBER DB 10 DUB(?)
MAIN PROC
MOV AX ,@DATA
MOV DS,AX
XOR BX,BX
MOV CX,5
MOV AH,1
FOR:
INT 21H
MOV NUMBER[BX],AL
INC BX
LOOP FOR
XOR BX,BX
MOV CX,5
PRINTN
MOV AH,2
Goutam Sanyal
FOR2:
MOV DL,NUMBER[BX]
INT 21H
INC BX
LOOP FOR2
INT 21H
MAIN ENDP
END MAIN
; sting reverse
.MODEL SMALL
.STACK 100H
.DATA
TEXT2 DB 13 DUP(?)
COUNT DW 13
.CODE
BEGIN:
MOV AX ,@DATA
MOV DS ,AX
Goutam Sanyal
MOV ES, AX
MOV SI ,0
MOV DI ,0
ADD DI,COUNT
DEC DI
AGAIN:
MOV AL ,TEXT1[SI]
MOV TEXT2[DI],AL
INC SI
DEC DI
LOOP AGAIN
MOV AH ,4CH
INT 21H
END BEGIN
Goutam Sanyal
Goutam Sanyal