1
00:00:00,060 --> 00:00:07,740
So when we export that hydrofoil into an SDK, OK, so some of the files are created by default and

2
00:00:07,740 --> 00:00:13,620
some of them are directly added form and we will just be taking in what you what are things that have

3
00:00:13,620 --> 00:00:14,730
been added by default?

4
00:00:14,730 --> 00:00:18,430
And then when we create a new project, what happens?

5
00:00:18,530 --> 00:00:23,610
So this would just be unusual because as we progress further, we'll be understanding a concept in a

6
00:00:23,610 --> 00:00:24,380
greater detail.

7
00:00:24,870 --> 00:00:32,430
So this folder that is designed for rapid hardware platform zero, this is the file that we export from

8
00:00:32,430 --> 00:00:35,760
and we write to consist of a big fight that you could really see.

9
00:00:35,940 --> 00:00:40,580
So when we see you exporting hardware, including a big tube.

10
00:00:41,040 --> 00:00:46,110
So we basically add the big file into their sticky right.

11
00:00:46,440 --> 00:00:49,020
So this is the first thing that we do and then rest.

12
00:00:49,030 --> 00:00:52,710
All the files are for the same processing initialization.

13
00:00:53,460 --> 00:00:59,340
So whenever we start running an application, these are the file which must be included to correctly

14
00:00:59,340 --> 00:01:01,980
run our application onto an FPGA.

15
00:01:02,040 --> 00:01:02,310
Right.

16
00:01:02,910 --> 00:01:06,590
The large file that we have is an hardware specification file.

17
00:01:06,600 --> 00:01:14,640
So if you just go to file, so you do see all the papers which are available by default and some of

18
00:01:14,640 --> 00:01:16,190
them which we already remove, right?

19
00:01:16,200 --> 00:01:19,310
So they are been removed from this specification.

20
00:01:19,620 --> 00:01:19,980
OK.

21
00:01:20,280 --> 00:01:26,340
But the peripheral which we have not removed, OK, will be available over here.

22
00:01:26,370 --> 00:01:33,030
So you could clearly see we have a set design in hierarchies so that are required when we work around

23
00:01:33,030 --> 00:01:35,700
with the drivers that are provided for them, right?

24
00:01:35,720 --> 00:01:42,480
We do not get much about what are the specific typos that we need to invoke to utilize that paper.

25
00:01:42,720 --> 00:01:48,150
But at least we can see that the address is known to us right now when we go ahead.

26
00:01:48,180 --> 00:01:53,530
And you could see we could also get an overview of an IP blocks that are present.

27
00:01:54,210 --> 00:02:00,990
So this is something that we get when we export and hardware looking into an SDK.

28
00:02:00,990 --> 00:02:02,190
So these are some of the sites.

29
00:02:02,190 --> 00:02:09,660
So you have your big file, though I think seeing initialization files and then the hardware specification

30
00:02:09,960 --> 00:02:16,950
that you get and etc. So usually we will not be working around the time of flight for accessing this

31
00:02:16,950 --> 00:02:18,110
address book.

32
00:02:18,150 --> 00:02:24,060
What we will do is we'll just be including when often header a that consist of all of these addresses

33
00:02:24,480 --> 00:02:27,500
for the benefit of that we have in our hardware, right?

34
00:02:27,510 --> 00:02:32,710
So we could just citing you and then X parameters.

35
00:02:32,790 --> 00:02:33,180
OK.

36
00:02:34,980 --> 00:02:37,110
NDIS Dot.

37
00:02:37,770 --> 00:02:44,220
So once you add this file and rebuild your program, you explore what is present inside this file.

38
00:02:44,220 --> 00:02:50,550
You would just click on S3 and then you could see all the peripherals which are available with this

39
00:02:50,940 --> 00:02:54,140
and the specific interest related information.

40
00:02:54,150 --> 00:02:59,940
So whenever we have a requirement of accessing an address, this will be the file that will be adding

41
00:02:59,940 --> 00:03:00,810
in our application.

42
00:03:01,080 --> 00:03:07,100
So this is the possibility that we have this will be getting when we export then hardware and an SD.

43
00:03:07,380 --> 00:03:08,700
The next folder is.

44
00:03:10,640 --> 00:03:11,870
OK, bye.

45
00:03:12,110 --> 00:03:17,900
If you choose this specific template, great, so this is created for our Halloween program and then

46
00:03:17,900 --> 00:03:19,000
you have this bias.

47
00:03:19,610 --> 00:03:25,910
So this is very important because this will consist of all the drivers, depending on and hardware that

48
00:03:25,910 --> 00:03:27,590
you have in your design, right?

49
00:03:27,620 --> 00:03:35,210
So you get set up and function, which I tested and verify for the specific benefit I could just work

50
00:03:35,210 --> 00:03:37,280
around with them to build a complex application.

51
00:03:37,310 --> 00:03:37,550
OK.

52
00:03:37,880 --> 00:03:40,610
So if you just go ahead, you have 16 Dot and Mrs.

53
00:03:40,640 --> 00:03:43,280
So this is something which is very, very important.

54
00:03:43,520 --> 00:03:46,660
And then you have seven Cortex-A9, zero.

55
00:03:46,670 --> 00:03:48,770
So here you have your library.

56
00:03:48,770 --> 00:03:54,050
So depending on the benefit of that, you add, this folder will be updating and then you get the set

57
00:03:54,050 --> 00:04:00,740
of for library so you could utilize anyone on the same day and build up your application on the top

58
00:04:00,740 --> 00:04:01,020
of it.

59
00:04:01,040 --> 00:04:06,110
So you get set up for functions which could be utilized to build a complex application.

60
00:04:06,140 --> 00:04:06,380
Right.

61
00:04:06,950 --> 00:04:10,280
So this is included in an VSP fight.

62
00:04:10,310 --> 00:04:10,670
OK.

63
00:04:10,760 --> 00:04:16,900
So you have all the drivers and access to a function which are verified and tested on the periphery,

64
00:04:16,910 --> 00:04:22,100
so you could build up a complex application on the top of iterate if you're going through their system

65
00:04:22,100 --> 00:04:22,400
data.

66
00:04:22,750 --> 00:04:29,690
So this is also very, very important because this will give us an access to the examples related to

67
00:04:29,690 --> 00:04:36,650
the specific benefit of that you had to design, as well as what are the specific drivers that you need

68
00:04:36,650 --> 00:04:39,620
to invoke for specific today.

69
00:04:40,040 --> 00:04:47,570
So if you consider if you want to use an S.U. timer, so the driver is a queue timer and then.

70
00:04:48,620 --> 00:04:54,590
So here you have two kinds of private drivers specific to the genetic drivers.

71
00:04:54,730 --> 00:04:58,730
Right, so we will be understanding more on this as we progress further.

72
00:04:58,940 --> 00:05:07,280
But Dr. Misfiled give us an access to the drivers that your boyfriend is most suited for, right?

73
00:05:07,280 --> 00:05:13,430
So you could just invoke this driver and you are ready to utilize the function that are written in that

74
00:05:13,430 --> 00:05:15,670
driver to build a complex application.

75
00:05:15,680 --> 00:05:20,630
You also get an documentation as well as an example for that specific chip.

76
00:05:20,720 --> 00:05:20,990
Right.

77
00:05:21,320 --> 00:05:25,640
So these are some of the folders which are issued when we start working with an hallowed.