Skip to main content

NASM Programming

Many of you, if you are like me, might be interested in how assembly works.  You will be very surprised that assembly is very very easy, especially after you write a couple of simple programs.  But don't get me wrong, you will be frustrated at first, however that frustration, if you channel it right, will lead to serious life long learning and will give you a deeper appreciation of the beauty of assembly.

For more tutorial on assembly and visualization of these information, visit my youtube channel.

Okay so lets get started.

We will be using Netwide Assembler (NASM) to write our program.
The general format of NASM file is this:

;This is a comment
SECTION .data
;declare variable here


SECTION .bss
;declare actual, dynamic variable


SECTION .text
;where your program code/assembly code lives


;

Working with Data Section
In your .data section, you can declare variables like this:

nameOfVariable: db 32 ;this declares a variable names nameOfVariable with byte value of 32
nameOfVariable2: dw 302 ;declare variable of 2 bytes
someString: db "This is an example of a string",10,0 ;we declare an array of string, 10=newline return and 0=termination of array(NULL)

So, db is define byte, dw is define word, and dd is define double word.  Here, byte is 8 bits, word is two bytes, and double word is two words.  Basically you used these to define a initialized variables.

Working with BSS Section
In your .bss section, you declare variables like this:



nameOfVariable: 
resb  256 ;this reserves space for a 256 bytes
nameOfVariable2: resw  1 ;this reserves space for 1 word, otherwise known as 2 bytes
someString: resd  ;this reserves space for 1 double word



Working with Text Section
The .text section is your program code.  It is what makes a program a program.  Simple as that.

You will arrange your instructions in whatever manner to achieve your particular logic goals.

Usually, you will want to have or start with something like this:



global main     ;export the symbol main so that external program can see this memory address
main:     ;here "main:" is a label--labels are an alias for memory address
       ;setup our stack frame
       push ebp
       mov ebp, esp
   

       ;clean u stack frame
       mov esp, ebp
       pop ebp
       ret 
      

Comments

Popular posts from this blog

Creating local variables In Assembly

Lets go over how to create local variables inside of a pure assembly source code. Much like always, you will start with a *.asm file that looks like this: source code SECTION .data SECTION .bss SECTION .text global main ;make main available to operating system(os) main: ;create the stack frame push ebp push mov ebp, esp ;destroy the stack frame mov esp, ebp pop ebp ret So, the above is the general layout of an NASM source file.  Our goal here is to create a local variable inside of the main method.  The only way to create a local variable is by using the stack.  Why?  Because we can only declare variable in storage locations and the only available storage locations are: text, bss, and data.  However, text section is only for code, so it is out of the question.  The bss and data sections are appealing, but to declare our "local" variable in these sections will defeat the purpose of these variables being local, t

Introduction to Linux Kernel Programming

The Linux kernel is designed as a mixture of a monolithic binary image and a micro-kernel.  This combination allows for the best of both worlds.  On the monolithic side, all the code for the kernel to work with the user and hardware is already installed and ready for fast access, but the downside is that to add more functionality you need to rebuild the entire kernel.   In a different manner, a micro-kernel is composed of small pieces  of code that can be meshed today and more pieces can be added or removed as needed.  However, the downside to micro-kernel is a slower performance. Adding a module to the Kernel Linux is organized as both monolithic, one huge binary, and micro-kernel, as you can add more functionality to it.  The process of adding more functionality to the kernel can be illustrated by the crude image to the left. The process begins by using the command insmod with the name of the kernel module you want (which usually ends with extension *.ko).  From here, the mod