So when we export that hydrofoil into an SDK, OK, so some of the files are created by default and
some of them are directly added form and we will just be taking in what you what are things that have
been added by default?
And then when we create a new project, what happens?
So this would just be unusual because as we progress further, we'll be understanding a concept in a
greater detail.
So this folder that is designed for rapid hardware platform zero, this is the file that we export from
and we write to consist of a big fight that you could really see.
So when we see you exporting hardware, including a big tube.
So we basically add the big file into their sticky right.
So this is the first thing that we do and then rest.
All the files are for the same processing initialization.
So whenever we start running an application, these are the file which must be included to correctly
run our application onto an FPGA.
Right.
The large file that we have is an hardware specification file.
So if you just go to file, so you do see all the papers which are available by default and some of
them which we already remove, right?
So they are been removed from this specification.
OK.
But the peripheral which we have not removed, OK, will be available over here.
So you could clearly see we have a set design in hierarchies so that are required when we work around
with the drivers that are provided for them, right?
We do not get much about what are the specific typos that we need to invoke to utilize that paper.
But at least we can see that the address is known to us right now when we go ahead.
And you could see we could also get an overview of an IP blocks that are present.
So this is something that we get when we export and hardware looking into an SDK.
So these are some of the sites.
So you have your big file, though I think seeing initialization files and then the hardware specification
that you get and etc. So usually we will not be working around the time of flight for accessing this
address book.
What we will do is we'll just be including when often header a that consist of all of these addresses
for the benefit of that we have in our hardware, right?
So we could just citing you and then X parameters.
OK.
NDIS Dot.
So once you add this file and rebuild your program, you explore what is present inside this file.
You would just click on S3 and then you could see all the peripherals which are available with this
and the specific interest related information.
So whenever we have a requirement of accessing an address, this will be the file that will be adding
in our application.
So this is the possibility that we have this will be getting when we export then hardware and an SD.
The next folder is.
OK, bye.
If you choose this specific template, great, so this is created for our Halloween program and then
you have this bias.
So this is very important because this will consist of all the drivers, depending on and hardware that
you have in your design, right?
So you get set up and function, which I tested and verify for the specific benefit I could just work
around with them to build a complex application.
OK.
So if you just go ahead, you have 16 Dot and Mrs.
So this is something which is very, very important.
And then you have seven Cortex-A9, zero.
So here you have your library.
So depending on the benefit of that, you add, this folder will be updating and then you get the set
of for library so you could utilize anyone on the same day and build up your application on the top
of it.
So you get set up for functions which could be utilized to build a complex application.
Right.
So this is included in an VSP fight.
OK.
So you have all the drivers and access to a function which are verified and tested on the periphery,
so you could build up a complex application on the top of iterate if you're going through their system
data.
So this is also very, very important because this will give us an access to the examples related to
the specific benefit of that you had to design, as well as what are the specific drivers that you need
to invoke for specific today.
So if you consider if you want to use an S.U. timer, so the driver is a queue timer and then.
So here you have two kinds of private drivers specific to the genetic drivers.
Right, so we will be understanding more on this as we progress further.
But Dr. Misfiled give us an access to the drivers that your boyfriend is most suited for, right?
So you could just invoke this driver and you are ready to utilize the function that are written in that
driver to build a complex application.
You also get an documentation as well as an example for that specific chip.
Right.
So these are some of the folders which are issued when we start working with an hallowed.