Apart from the information you get from this cause it would be worth taking a look at some reference
documents off the board like the the microcontroller data sheets for instance is fairly standard in
a new hardware you buy you have to take some time to look through the data sheet as we go through this
course.
Yes we're going to go through the data sheets together to extract just what we need to worry that data
sheet is quite large.
You don't need to memorize it.
You don't need to learn at all.
It's just a reference manual like a sort of dictionary if you want to do something.
You go and check in the data sheet.
So it's worth downloading and having it on your computer.
Another one is DTV see Launchpad User's Guide this.
Also worth a read.
And yes finally we are ready to write our first assembly code.
How excited are you.
I'm certainly excited.
I remember the first time I wrote assembly.
Yes.
So our first program is fairly simple.
It's called the read on what this diocese the read LCD.
Remember we have the our GDP.
We have green blue and green LCD already on our board.
What this program would do is keep that red LCD on.
It doesn't blink.
Remember when you buy the board there is a program that makes the lights blink on this first program
we're going to write.
It's going to keep the lights on and we're going to write it in assembly.
Then after that we improve these programs that by step we start adding things to it.
And a well-structured program must begin with a requirements document.
Yes I think it's important to have a requirement documents for every program.
So we'll start this first one by trying to write down some requirements analysis for this program.
And as we go on this a very simple program in fact we wouldn't we don't even need to write such a document
for it.
But I think it's a good practice to do.
Yes.
So we just go through some of the things we write and the requirement documents have the requirement
document enforced determine determine and the needs of the system through asking questions they see
some of the questions we can ask what is the opportunity of this project.
Yes it is to design build and test a system that turns on the red LCD.
How will the project be developed.
The program will be written in color youth vision develop to use an at TVC launch part.
How will it fit into existence systems.
The read on program will be callable from systems having to see microcontroller.
That's good.
What will this system do precisely.
Yes the system will start by setting up the required pieces on the board and then into an infinite loop
that keeps the red LCD turned on.
So this a fairly fair.
Very very short requirement document.
But I know you understand based on this if you write in a big up program you would know the questions
to ask.
This is just to give you what such a requirement document would.
Now let's take a look at the projects set up every call you Vision Project contains two paths that when
you create a new project comes along with it and these files are the same file written in C and then
assembly.
And what this file should do is that this sets up the starting point of the program.
They have what we call a reset handler the block of code that is it's run every time you press the reset
button.
Also this file is outlined a stack size and a heap size.
I know we've not talked about stuck in a heap.
We'll talk about them later.
I just wanted to know the functions of the startup files and without these files you cannot compile
your program you would receive error messages.
So when you create your project you get these files.
They also contain the reset factor and all interrupt vectors.
We'll talk about interrupt later as we mentioned earlier the reset handler runs every time the reset
button is pressed on your microcontroller board.
And what this does is that it jumps straight to the starting point of your program and in C program
in code written and c the start point as to main function.
So what this means is that if we're right in our program entirely in assembly and we want the program
to start from the assembly side we would have to go to the reset handler and change the starting point
to the starting points that we give our program.
We would see this when we create our program.