1
00:00:00,060 --> 00:00:04,800
Who let us start building an application, right, so here I have invoked an excessive fight that we

2
00:00:04,800 --> 00:00:11,190
have exploded in and seemed to we have our Revatio project and I've also created an application project

3
00:00:11,340 --> 00:00:14,030
and utilizing and had to wait and wait.

4
00:00:14,460 --> 00:00:21,860
So the first step is to find out the driver, which I recommended for you at this rate.

5
00:00:21,860 --> 00:00:25,450
So we'll just be going ahead in a boob support package.

6
00:00:25,470 --> 00:00:27,780
OK, and here you have yes.

7
00:00:27,780 --> 00:00:28,340
You what?

8
00:00:28,980 --> 00:00:29,250
Well.

9
00:00:29,400 --> 00:00:32,530
And for that, the recommended driver is you watch the SUV.

10
00:00:32,760 --> 00:00:36,030
That is what we're going to include in our mean quite so harsh.

11
00:00:36,050 --> 00:00:37,670
Include you.

12
00:00:38,430 --> 00:00:38,870
Yes.

13
00:00:38,880 --> 00:00:43,380
So and you just need to add a prefix asics dot h.

14
00:00:43,530 --> 00:00:43,800
Right?

15
00:00:44,220 --> 00:00:45,950
So this is the driver for you.

16
00:00:45,960 --> 00:00:46,290
What?

17
00:00:47,210 --> 00:00:51,830
We also required one more driver that consists of all the hardware related information.

18
00:00:52,250 --> 00:00:54,820
Again, that is experimented on each way.

19
00:00:54,890 --> 00:00:55,130
Right?

20
00:00:55,340 --> 00:00:59,600
So first, we'll just be proceeding to you what you say and understanding the content of it.

21
00:00:59,660 --> 00:00:59,930
Right?

22
00:01:00,290 --> 00:01:03,450
So if you go to a driver, right?

23
00:01:03,470 --> 00:01:07,550
So here you have a different option that you could set for you all you want.

24
00:01:07,910 --> 00:01:08,210
Right?

25
00:01:08,600 --> 00:01:12,200
Then you also have a different mode of an operation, right?

26
00:01:12,470 --> 00:01:18,640
So you could either operate in a normal mode, the local look back mode or eco mode and remotely pack.

27
00:01:19,040 --> 00:01:24,440
So we'll be demonstrating normal mode and the local loop back mode in this specific example.

28
00:01:25,070 --> 00:01:29,750
You could explore the other modes, such as eco and remote.

29
00:01:29,750 --> 00:01:30,170
Look back.

30
00:01:30,350 --> 00:01:30,620
Right?

31
00:01:31,350 --> 00:01:38,400
Then if you analyze, so we have again the same structure, which we finding another driver also, right?

32
00:01:38,450 --> 00:01:39,730
So you have you what?

33
00:01:39,740 --> 00:01:44,150
Yes, which is an instance structure and you also have.

34
00:01:45,390 --> 00:01:49,650
A config structure, right, so both the structures are and over here.

35
00:01:50,080 --> 00:01:50,400
OK.

36
00:01:50,520 --> 00:01:58,860
And then if you go to a function, OK, you have a function to enable the transmitter and receiver of

37
00:01:58,860 --> 00:02:02,010
you are to disable transmitter entry several if you want.

38
00:02:02,370 --> 00:02:02,700
OK.

39
00:02:02,970 --> 00:02:07,980
The transmitter and receiver offer you what to consist of local fiefdoms, right?

40
00:02:07,980 --> 00:02:13,410
So we do have a function to verify whether the people are empty or not, right?

41
00:02:13,650 --> 00:02:16,430
And other than that, you'll be finding we have a look at conflicts.

42
00:02:16,440 --> 00:02:19,620
You have to initialize the lower level function to send the data.

43
00:02:19,910 --> 00:02:20,570
OK by.

44
00:02:21,060 --> 00:02:26,940
You also have a function to receive the data by, but by then you have a function to chase the moderate

45
00:02:26,940 --> 00:02:27,310
Hokie.

46
00:02:27,720 --> 00:02:31,350
To set the different mode of operation, you have a safe option.

47
00:02:32,440 --> 00:02:38,710
So to new and existing option that we configured for a what we also have a cake option.

48
00:02:39,070 --> 00:02:41,970
OK, do we have a function to sick, though?

49
00:02:41,980 --> 00:02:43,030
If you put, we show.

50
00:02:43,330 --> 00:02:43,690
OK.

51
00:02:43,780 --> 00:02:51,370
And then we have a pool more function, which allows us to verify whether you are complete the data

52
00:02:51,370 --> 00:02:52,630
transmission on or great.

53
00:02:53,560 --> 00:02:56,800
Then we also have a function to set up the receive timeout.

54
00:02:57,070 --> 00:02:57,390
OK.

55
00:02:57,670 --> 00:03:00,330
And the interpretative function, right?

56
00:03:00,340 --> 00:03:04,930
So we do have a good amount of function available in any light driver.

57
00:03:05,170 --> 00:03:08,890
OK, let us first proceed with a initialization of fire.

58
00:03:09,130 --> 00:03:09,790
You are right.

59
00:03:09,790 --> 00:03:12,070
So we required a config structure first.

60
00:03:12,460 --> 00:03:13,990
We go ahead to our mean core.

61
00:03:14,260 --> 00:03:19,230
We declare the config structure and this should be a pointer to what config?

62
00:03:19,450 --> 00:03:22,510
OK, along with this, we also required an instance, right?

63
00:03:22,510 --> 00:03:26,470
So we'll just be copying this and let it just name decides and want.

64
00:03:26,710 --> 00:03:31,840
So once this is done, we declared an independent function, which we named as a new light in it, and

65
00:03:31,840 --> 00:03:34,900
this will perform an initialization of a new library.

66
00:03:34,970 --> 00:03:38,140
So first thing is to generate the config structure, right?

67
00:03:38,140 --> 00:03:43,660
So to generate a config structure, we have a lookup conflict where we need to provide the device right?

68
00:03:43,660 --> 00:03:46,120
So you what config?

69
00:03:46,240 --> 00:03:48,700
OK, and this will be what's to look up config.

70
00:03:48,910 --> 00:03:52,600
And here we need to add a device like this where you find the device IDs.

71
00:03:52,900 --> 00:03:58,830
You just need to go to an X parameter dot and then you need to search for you like this, right?

72
00:03:58,840 --> 00:04:04,310
So this really goes to the location where we have all the data related to an instance of any like this.

73
00:04:04,320 --> 00:04:07,660
So this is a device that we need to add over here.

74
00:04:07,850 --> 00:04:13,600
OK, and as soon as you feel the device, I need to look upon to function, this will generate the config

75
00:04:13,600 --> 00:04:14,230
search, right?

76
00:04:14,230 --> 00:04:20,440
So once we have a config structure, we'll just be utilizing CFG initialize to initialize our benefit.

77
00:04:20,440 --> 00:04:22,600
And now this returns S30, right?

78
00:04:22,810 --> 00:04:24,410
So we'll just declare s32.

79
00:04:24,430 --> 00:04:27,190
Let me just name this as status.

80
00:04:29,010 --> 00:04:34,260
And here we are required to pass the argument first, first document is an instance structure, then

81
00:04:34,260 --> 00:04:36,490
we need to pass the config structure.

82
00:04:36,510 --> 00:04:43,650
And the last argument is the basic research, which could also be invoked from our config structure,

83
00:04:44,040 --> 00:04:44,220
right?

84
00:04:44,250 --> 00:04:49,530
So these the three argument that you need to pass to see if initialize and once you pass this, this

85
00:04:49,530 --> 00:04:54,900
will automatically perform an initialization of a benefit, and this will also return the status of

86
00:04:54,900 --> 00:04:56,100
an initialization, right?

87
00:04:56,580 --> 00:05:00,000
Our agenda will be to verify whether statuses exist.

88
00:05:00,000 --> 00:05:00,810
666 That's OK.

89
00:05:00,810 --> 00:05:05,160
If that is the case, we can see the initialization is successful, right?

90
00:05:05,190 --> 00:05:05,490
So.

91
00:05:06,450 --> 00:05:13,200
If status is access to success in that case, they could just stand still, plaintiff OK and mention.

92
00:05:14,370 --> 00:05:18,200
You worked in it successfully.

93
00:05:18,350 --> 00:05:24,190
Right, this makes sense, as we can see, still brain death.

94
00:05:24,930 --> 00:05:29,250
And then here we will mention you worked in it.

95
00:05:30,310 --> 00:05:36,870
We night this completes the process of initialization now you could actually perform a set of disposal,

96
00:05:37,170 --> 00:05:40,800
so that will verify whether hardware is properly configured, right?

97
00:05:41,040 --> 00:05:45,690
Well, this system now we go ahead and copy the you what init function?

98
00:05:45,750 --> 00:05:49,290
OK, and then we will be adding it to work here.

99
00:05:49,320 --> 00:05:51,090
Right now we proceed.

100
00:05:51,330 --> 00:05:53,540
And us just do more district right?

101
00:05:53,550 --> 00:06:01,500
So first, let it just work around with changing the body and analyzing whether we are able to sustain

102
00:06:01,740 --> 00:06:03,450
the DTI for different body types.

103
00:06:03,450 --> 00:06:08,690
So by default, we know that you are configured to work at one one five two zero zero, right?

104
00:06:08,700 --> 00:06:14,280
So this we already know if you just customizable or double click on anything processing system and you

105
00:06:14,280 --> 00:06:18,450
spill configuration, OK and Agendas tab, you get an access to you.

106
00:06:18,450 --> 00:06:23,580
Like one board, which is one one five two zero zero eight two, this is the default border which is

107
00:06:23,730 --> 00:06:25,470
set by a board, you said.

108
00:06:25,680 --> 00:06:27,840
Now let's try to modify the board.

109
00:06:27,840 --> 00:06:29,850
We try to say if you go to and you like this.

110
00:06:30,510 --> 00:06:32,670
So here you have an option to set the bar.

111
00:06:33,090 --> 00:06:34,590
So if you click on an F3.

112
00:06:35,160 --> 00:06:38,310
So this will basically give it this description of this function.

113
00:06:38,320 --> 00:06:40,890
So this set the bar rate for a device.

114
00:06:41,230 --> 00:06:48,060
Take the input for a valid and also verifies that the requested rate can be configured within the maximum

115
00:06:48,360 --> 00:06:52,350
range specified by the MAX or the error rate.

116
00:06:52,650 --> 00:06:57,360
If the provider rate is not possible, then the current setting is unchanged.

117
00:06:57,360 --> 00:06:58,770
So this is something interesting.

118
00:06:59,010 --> 00:07:05,190
If you specify the bar rate, which is view on the MAX board that you are, you can configure.

119
00:07:05,700 --> 00:07:08,990
It will be simply keeping an existing border.

120
00:07:09,060 --> 00:07:10,410
It won't be changing it right.

121
00:07:10,830 --> 00:07:18,020
And this retains this axis if everything is configured successfully and it returns the excess to board

122
00:07:18,030 --> 00:07:18,720
it, right?

123
00:07:18,960 --> 00:07:21,090
So we'll go ahead and copy this now.

124
00:07:21,090 --> 00:07:26,340
This request to our first one is that instead, Sucher and then we have a border, right?

125
00:07:26,340 --> 00:07:26,700
So.

126
00:07:27,760 --> 00:07:32,030
He would just be copping this, and then we go back to our mean.

127
00:07:32,280 --> 00:07:33,840
Right, so here we are this function.

128
00:07:34,760 --> 00:07:39,380
And then first argument is thanks to a structure, which is you are in this case.

129
00:07:39,620 --> 00:07:44,330
Now let us first try to add the border as nine six zero zero, which is lower.

130
00:07:44,330 --> 00:07:49,430
That's compared to the border, which is said by default, that is one one five two zero zero, right?

131
00:07:49,670 --> 00:07:54,410
And we'll just be verifying whether the still able to get the seed right.

132
00:07:54,410 --> 00:07:56,780
So let's just go ahead.

133
00:07:57,350 --> 00:08:03,680
And I said, Plaintiff, OK, here we are not utilizing the lower level function which we send and receive

134
00:08:03,680 --> 00:08:04,010
that up.

135
00:08:04,010 --> 00:08:07,820
Resonator driver first will just be predominantly working on the border.

136
00:08:07,850 --> 00:08:14,090
So once we understand our configuration of the border, it will be slowly progressing towards a lower

137
00:08:14,090 --> 00:08:14,890
level if we are right.

138
00:08:14,900 --> 00:08:20,390
So let me just mention board eight nine six zero zero, right?

139
00:08:20,390 --> 00:08:27,220
So this is the string that we like to say right now it will just be building up our project first.

140
00:08:27,620 --> 00:08:33,710
So once I build a successful right, we select our application project debug as launch and hardware.

141
00:08:33,760 --> 00:08:36,260
Now this will automatically program my future.

142
00:08:36,560 --> 00:08:41,570
First thing that we're going to do is to configure a way to create terminal to an incorrect border.

143
00:08:41,690 --> 00:08:41,930
Right.

144
00:08:41,930 --> 00:08:47,750
So we know that we have to change our border from one one five two zero zero two nine six zero zero.

145
00:08:47,990 --> 00:08:53,390
Let us go ahead and select one one five two zero zero, which is the default border that we've been

146
00:08:53,390 --> 00:08:55,880
using from the beginning and silicone four.

147
00:08:56,120 --> 00:08:57,260
So once we click OK?

148
00:08:58,240 --> 00:09:03,050
And click on Resume Button now you can clearly see we wouldn't be able to understand that, right?

149
00:09:04,000 --> 00:09:06,880
This is because we have our differences in the border.

150
00:09:07,010 --> 00:09:09,740
Right now will just be disconnecting our serial.

151
00:09:10,420 --> 00:09:12,940
And then again, click on the resume button.

152
00:09:13,360 --> 00:09:14,590
Click on this plus button.

153
00:09:14,930 --> 00:09:18,460
OK, and now choose the border to be nine six zero zero.

154
00:09:18,580 --> 00:09:23,050
Right now, you could see we are connected to a counselor at nine six zero zero.

155
00:09:23,260 --> 00:09:27,280
We'll just be clearing Arkansas and then relaunching our application.

156
00:09:27,280 --> 00:09:28,810
So this is our debugger session.

157
00:09:29,110 --> 00:09:31,360
Right click and then you have a relaunch option.

158
00:09:31,610 --> 00:09:31,840
Wait.

159
00:09:32,980 --> 00:09:39,310
So once we relaunch our session now, we know that our serial terminal is operating at 19 00 border.

160
00:09:39,370 --> 00:09:45,340
I'll just click on the resume right now and you could clearly see that we now get a reality, right?

161
00:09:45,520 --> 00:09:50,710
So this is how we can very dynamically the body esperar requirement.

162
00:09:50,740 --> 00:09:50,930
Right.

163
00:09:50,950 --> 00:09:58,960
So this is the first study now since we plan to keep our body constant for this specific example.

164
00:09:59,200 --> 00:10:04,420
We could just add this body OK in the white init function.

165
00:10:04,420 --> 00:10:11,910
It's so already decided that after we perform an initialization, we can't figure out you want to operate

166
00:10:11,920 --> 00:10:12,190
at.

167
00:10:13,090 --> 00:10:14,230
Nine, six zero zero.

168
00:10:14,410 --> 00:10:15,160
All right.

169
00:10:15,570 --> 00:10:18,880
Once this is done now, let me just again build our application project.

170
00:10:20,220 --> 00:10:25,050
And once bullets finish will again be launched, you got application rate, so they just go ahead and

171
00:10:25,050 --> 00:10:26,880
try to launch our application again.

172
00:10:28,020 --> 00:10:34,350
And now we go to a white minute and click, OK, right now you will see you are in it is successful.

173
00:10:34,350 --> 00:10:40,380
As well as Baldry, which is nine six zero zero that is said by user, is also displayed great.

174
00:10:40,380 --> 00:10:42,790
So put of this thing is working as expected.

175
00:10:42,820 --> 00:10:46,700
Now we proceed to work on the lower level API rate.

176
00:10:46,890 --> 00:10:52,420
So how we work, then sing and rescue function that we have in and you are obviously.