1
00:00:00,120 --> 00:00:02,550
We have created a new application project.

2
00:00:02,580 --> 00:00:08,640
Now we proceed to build an application for our two full time the right, so if you go to a good support

3
00:00:08,640 --> 00:00:09,150
package.

4
00:00:09,540 --> 00:00:15,830
OK, so the recommended driver for DC is the DCP s right.

5
00:00:15,840 --> 00:00:19,080
So this is what we are going to include in our Halloway Darcy.

6
00:00:19,110 --> 00:00:19,290
Right.

7
00:00:19,350 --> 00:00:23,830
So Ash, can you then the driver is you?

8
00:00:24,750 --> 00:00:25,570
Yes, OK.

9
00:00:25,800 --> 00:00:27,330
You just need to add a prefixes.

10
00:00:27,450 --> 00:00:33,570
So this will give us an access to a driver related to dispatch time again to roadside the driver that

11
00:00:33,570 --> 00:00:34,040
we require.

12
00:00:34,080 --> 00:00:38,490
Frequently, this experiment is done.

13
00:00:38,880 --> 00:00:41,620
So this consists of all the hardware related information.

14
00:00:41,670 --> 00:00:46,740
Right now, we proceed to first initialize out the reference of what you see in it.

15
00:00:48,120 --> 00:00:54,870
Then we will be declaring all the necessary functions that could be used to initialize our duties.

16
00:00:55,470 --> 00:00:58,380
So we go to CPS driver.

17
00:00:58,420 --> 00:00:58,760
OK.

18
00:00:59,980 --> 00:01:05,830
So to see more, you grew by three independent timer or counter money that can each be clocked using

19
00:01:05,830 --> 00:01:13,600
either a system clock or SWG the clock to the right now we are driving our D.D.S. with the system clock

20
00:01:13,600 --> 00:01:13,920
rate.

21
00:01:14,740 --> 00:01:20,260
In addition, each counter can independently reskill its selected clock input rate.

22
00:01:20,260 --> 00:01:26,740
So that is something which is giving us an advantage that pre-schooler could be independently used for

23
00:01:26,740 --> 00:01:28,690
the three different timer and counting.

24
00:01:28,720 --> 00:01:35,120
Right now, we go ahead and try to find out the functions which are available in this table, right?

25
00:01:35,140 --> 00:01:40,450
So we have a fixed structure and then the instant structure, right?

26
00:01:40,450 --> 00:01:45,100
So we first caller conflict structure, we create a pointer of it, right?

27
00:01:45,100 --> 00:01:46,420
So we go ahead on.

28
00:01:46,420 --> 00:01:51,970
We are conflict structure really just name the sets DVC on config rate.

29
00:01:51,970 --> 00:01:54,430
The next one that we required is an instance structure.

30
00:01:54,430 --> 00:01:58,530
So we just copy this and then we have a few, right?

31
00:01:58,630 --> 00:02:05,200
So these are the two structures which are mandatory to perform an initialization for an effective rate.

32
00:02:05,200 --> 00:02:13,300
So if you go ahead and driver, you'll be finding we have the function and start to the DC to stop it,

33
00:02:13,840 --> 00:02:14,110
right?

34
00:02:14,110 --> 00:02:20,470
So this could be used to start and stop our timer, then whether the DC started or not, that could

35
00:02:20,470 --> 00:02:22,410
also be checked right.

36
00:02:22,630 --> 00:02:28,690
By utilizing this function, then we could also sample the current value over time by utilizing get

37
00:02:28,690 --> 00:02:30,190
counter-rally function rate.

38
00:02:30,340 --> 00:02:36,580
Then we go ahead and look for the function that are available.

39
00:02:36,760 --> 00:02:40,780
So we do have a lookup config and see of initialization to look up.

40
00:02:40,780 --> 00:02:46,570
Config is the first function that we required where we add a device idea, and this basically included

41
00:02:46,570 --> 00:02:47,950
in the config structure, right?

42
00:02:48,250 --> 00:02:56,500
So we go ahead, and for us, the config structure is to DC on fit, OK, and this will be given to

43
00:02:56,500 --> 00:02:59,700
look up config where we need to pass the device, right?

44
00:03:00,010 --> 00:03:04,840
So where we find the device is by utilizing an X parameter, not h right.

45
00:03:05,020 --> 00:03:07,120
And look for DC, right?

46
00:03:07,120 --> 00:03:10,750
So here you get all the information related to this.

47
00:03:10,750 --> 00:03:16,660
So this is the device, Haiti that we need to add as an input to a lookup configuration as soon as you

48
00:03:16,660 --> 00:03:17,410
add a device.

49
00:03:17,650 --> 00:03:24,610
This Gen-Z config structure and then we will be calling the C of initialize right where we need to pass

50
00:03:24,610 --> 00:03:29,410
an instance structure, config structure and the base address and this return the status of initialization.

51
00:03:29,950 --> 00:03:34,080
So here you really notice that the value tenses started right.

52
00:03:34,480 --> 00:03:40,590
So we will be declaring this 32 variable that could be used to store the status of initialization.

53
00:03:40,600 --> 00:03:42,280
Then we called CMG.

54
00:03:42,310 --> 00:03:47,230
Initialize here for this document is the instant structure is just UTC Knox.

55
00:03:48,220 --> 00:03:54,100
The next one is a concrete structure, so if you do see conflict right, and then again.

56
00:03:55,230 --> 00:03:59,750
We know that we said this from D.D.S. config structure.

57
00:04:00,600 --> 00:04:06,570
This completes the process of initialization, then we'll just be verifying whether initialization is

58
00:04:06,570 --> 00:04:07,800
successful or not.

59
00:04:07,810 --> 00:04:08,910
Great save status.

60
00:04:09,960 --> 00:04:12,140
Music was to exist.

61
00:04:14,310 --> 00:04:16,170
So in that guy's so good.

62
00:04:17,360 --> 00:04:24,350
Mention that device initialization is success rates of DDC inept.

63
00:04:25,450 --> 00:04:32,020
Success for right else is and we could just mention D.D.S..

64
00:04:32,530 --> 00:04:32,950
OK?

65
00:04:33,280 --> 00:04:36,010
Admit he read, this makes sense.

66
00:04:36,670 --> 00:04:39,160
So this completes the process of initialization.

67
00:04:39,250 --> 00:04:45,600
Then the since we are working with the time to counter this belongs to an intermediate and complex benefited.

68
00:04:46,120 --> 00:04:51,170
We need to also perform self-restraint so that will verify whether hardware is properly configured.

69
00:04:51,520 --> 00:04:54,220
So here we have the self-test, right?

70
00:04:54,220 --> 00:04:56,360
So we just need to blast to structure to it.

71
00:04:56,380 --> 00:05:02,850
So let me just go ahead and agree with us to this variable rate of students will be forced to self test

72
00:05:02,860 --> 00:05:09,410
where we just need to pass the instance structure we just see and then we will do everything again.

73
00:05:09,430 --> 00:05:12,170
The simplest is successful or not, right?

74
00:05:12,190 --> 00:05:17,590
So we go ahead and again check whether status is equal to existing success.

75
00:05:17,590 --> 00:05:23,620
And if that is the case, we'll just be mentioning self-tests successfully as we will be mentioning

76
00:05:23,620 --> 00:05:25,380
self-test, right?

77
00:05:25,720 --> 00:05:29,710
So this completes the process of initialization of our DTC it.

78
00:05:29,890 --> 00:05:33,210
So what we are doing is first, we are calling a lookup config.

79
00:05:33,220 --> 00:05:34,990
This generate the config structure.

80
00:05:34,990 --> 00:05:41,800
Then we are calling CMG initialize to perform an initialization that we are verifying whether initialization

81
00:05:41,800 --> 00:05:42,830
is successful or not.

82
00:05:42,850 --> 00:05:44,830
Finally, we are also calling center stage.

83
00:05:44,830 --> 00:05:50,890
So let me just go to our main application and first call the initialization function, which is GDC

84
00:05:50,890 --> 00:05:53,230
and in the mean function.

85
00:05:54,820 --> 00:05:59,530
So now the option that we need to set in that DDC rate will be fighting it.

86
00:05:59,800 --> 00:06:06,850
There are multiple things that we require to add so we can automatically lower the counter value as

87
00:06:06,850 --> 00:06:12,360
we are doing in a previous case that we are working with the private to do the timer or of watchdog

88
00:06:12,370 --> 00:06:12,580
time.

89
00:06:12,610 --> 00:06:12,910
All right.

90
00:06:12,910 --> 00:06:16,780
So here you could see we have multiple parameters we have of this killer.

91
00:06:17,020 --> 00:06:21,490
Then we have a frequency interval and.

92
00:06:22,950 --> 00:06:29,500
We also have an option, right, so there are multiple parameters that we need to set to properly consider

93
00:06:29,520 --> 00:06:35,220
if that is the primary difference that we'll be finding between the timer that we previously discussed.

94
00:06:35,220 --> 00:06:35,910
And that's it's.

95
00:06:36,450 --> 00:06:38,160
So let me just declare one structure.

96
00:06:38,160 --> 00:06:43,290
I it is always a good idea when you work it out with the DDC, where you want to configure a multiple

97
00:06:43,290 --> 00:06:50,370
parameter, you create a structure where you incorporate all the parameters into a single structure.

98
00:06:50,460 --> 00:06:54,570
So that makes an entire process of setup very easy, right?

99
00:06:54,580 --> 00:06:58,200
So you go ahead and let it just declare one structure, right?

100
00:06:58,200 --> 00:06:58,530
So.

101
00:06:59,530 --> 00:07:01,180
Type death, OK?

102
00:07:01,210 --> 00:07:02,530
This is how we define this.

103
00:07:02,830 --> 00:07:08,420
Now, if you do not know how you define this structure, just go to the driver here.

104
00:07:08,440 --> 00:07:13,780
We already know that the two structures are already declared that this config structure needs to structure,

105
00:07:13,790 --> 00:07:14,050
right?

106
00:07:14,380 --> 00:07:20,800
So if you go ahead and analyze the structure, you'll easily able to understand the format of declaring

107
00:07:20,800 --> 00:07:21,460
the structure right.

108
00:07:21,460 --> 00:07:26,940
So you could see we start with the typedef then structure, OK, then you add the members, which are

109
00:07:27,220 --> 00:07:31,690
which you want to add to the structure and then finally, you provide the name to a structure, right?

110
00:07:31,990 --> 00:07:33,740
So this is how you declare the structure.

111
00:07:33,760 --> 00:07:36,460
We go ahead and follow the same format, right?

112
00:07:36,700 --> 00:07:40,000
So type there and then strapped.

113
00:07:40,060 --> 00:07:46,240
OK, then finally, basis and this will be DDC setup structure, right?

114
00:07:46,600 --> 00:07:47,950
And then we add a semicolon.

115
00:07:47,980 --> 00:07:49,750
Now we need to add a member state.

116
00:07:49,750 --> 00:07:55,510
So just to analyze the parameter that you required, OK to perform the different configuration.

117
00:07:55,510 --> 00:07:59,560
So first parameter that you have is the.

118
00:08:00,640 --> 00:08:02,920
This killer, which is of you eat that right?

119
00:08:03,250 --> 00:08:05,650
So we go ahead and you wait.

120
00:08:07,220 --> 00:08:11,280
Then we just need to assess, please keep the right to be safe.

121
00:08:11,300 --> 00:08:13,640
And then you need to add a semi-final, right?

122
00:08:14,390 --> 00:08:17,750
The next data that we require is an x interval, right?

123
00:08:17,750 --> 00:08:20,380
So this is of an x interval type, right?

124
00:08:20,390 --> 00:08:24,180
So we just started and it's interval and let it just mean this as interval.

125
00:08:24,200 --> 00:08:25,100
This is the second.

126
00:08:26,160 --> 00:08:31,940
Remember that we have in our structure, the third one is a frequency right, which is of study to date.

127
00:08:32,330 --> 00:08:36,410
So let me just go ahead and start off frequency so you that you do.

128
00:08:36,860 --> 00:08:40,400
Let me just name this as output secrets.

129
00:08:41,900 --> 00:08:50,390
So we arrived at our pregnancy killer and then into the last parameter that you required is an option,

130
00:08:50,390 --> 00:08:50,720
right?

131
00:08:50,720 --> 00:08:52,730
So let you just go ahead and.

132
00:08:54,340 --> 00:08:56,090
So we have an option of debut.

133
00:08:56,470 --> 00:09:02,050
Right, so this is what we're going to add as our last member, which is required for a proper configuration

134
00:09:02,050 --> 00:09:05,350
of our deed so you that we do and then it just added an option.

135
00:09:05,530 --> 00:09:11,020
So these are the four parameters which are required to correctly configure D.D.S., right?

136
00:09:11,380 --> 00:09:17,170
So once you do this, let just go to our mean application and call PDC set up, right?

137
00:09:17,180 --> 00:09:18,880
So this is the structure that we have.

138
00:09:19,220 --> 00:09:22,730
And let let's just name this SGI now to perform an initialization.

139
00:09:22,750 --> 00:09:30,310
So we do want to have a frequency of 108 output frequency that we are expecting from IBD is one heart

140
00:09:30,460 --> 00:09:30,670
rate.

141
00:09:30,670 --> 00:09:36,130
So we just need to add frequency, evaluate and hopes in a case of an output frequency.

142
00:09:36,340 --> 00:09:40,340
So let me just add one to it, right and rest of the parameters we do not know.

143
00:09:40,360 --> 00:09:42,380
So let me just initialize them to zero.

144
00:09:42,410 --> 00:09:44,140
So, all right.

145
00:09:44,140 --> 00:09:50,410
So this basically suggests that output frequency is one plus member in our structure as an output frequency,

146
00:09:50,410 --> 00:09:50,780
right?

147
00:09:50,810 --> 00:09:53,650
And here we have a value of one for our force member.

148
00:09:53,860 --> 00:09:59,470
So this suggests that we are targeting the frequency off of one hertz and the rest of the parameter.

149
00:09:59,470 --> 00:10:04,180
We need to calculate utilizing the functions that are available with the driver, right?

150
00:10:04,180 --> 00:10:08,530
So pre-schooler is interval is also zero, where an option is also zero, right?

151
00:10:08,530 --> 00:10:17,590
So now if you go to the D.D.S. driver, right, so you have a calculate interval from a frequency right.

152
00:10:17,590 --> 00:10:23,980
So this is the function that will basically calculate interval value as well as a pre-schooler value

153
00:10:23,980 --> 00:10:25,460
for a given frequency.

154
00:10:25,540 --> 00:10:25,810
Right.

155
00:10:26,020 --> 00:10:28,870
And we already specified the frequency of this one hertz.

156
00:10:28,870 --> 00:10:35,140
Right now, this function could be utilized to calculate the double killer from the frequency, right?

157
00:10:35,140 --> 00:10:36,670
So they just call this function.

158
00:10:37,540 --> 00:10:40,000
OK, so we will be calling this function.

159
00:10:40,030 --> 00:10:44,840
And then first argument must be an instance of which is Gizzi, right?

160
00:10:45,310 --> 00:10:52,300
The next argument that we have is that frequency of frequency is the first member of our data structure,

161
00:10:52,300 --> 00:10:52,510
right?

162
00:10:52,510 --> 00:10:59,020
So we could just access a frequency like this data, which is a structure that use a dot operator and

163
00:10:59,020 --> 00:11:00,730
the output frequency, right?

164
00:11:00,970 --> 00:11:02,620
So this is equal to what?

165
00:11:04,160 --> 00:11:10,250
The next argument that we have is a pointer to an interval and pointer to upskill, all right, give

166
00:11:11,090 --> 00:11:12,620
this to our pointers, right?

167
00:11:12,950 --> 00:11:18,380
So we just need to add another person and then data dot.

168
00:11:18,380 --> 00:11:24,990
The third argument is an interval, so we'd just be storing an interval value in an interval member,

169
00:11:25,010 --> 00:11:25,310
right?

170
00:11:25,640 --> 00:11:29,420
Similarly, data don't the preschooler the last.

171
00:11:29,600 --> 00:11:33,670
So again, we need to use an embassy and then specify the scale.

172
00:11:33,950 --> 00:11:34,810
This makes sense, though.

173
00:11:34,820 --> 00:11:38,920
This is how we will be calculating interval as well as p.

174
00:11:38,930 --> 00:11:44,300
Scalar from an output frequency would just confirm that the third argument is interval and the last

175
00:11:44,300 --> 00:11:45,950
argument is a risky right.

176
00:11:46,190 --> 00:11:53,210
So once you compute and double entry scalar from a frequency, the next step is to set the preschooler

177
00:11:53,210 --> 00:11:54,950
and set the interval value rate.

178
00:11:54,980 --> 00:11:56,810
So do, said the pre scalar value.

179
00:11:56,810 --> 00:12:01,190
We have this function where we just need to pass an instance structure and the pre scalar value, which

180
00:12:01,190 --> 00:12:02,360
we have computed rate.

181
00:12:02,780 --> 00:12:03,740
So we go ahead.

182
00:12:04,900 --> 00:12:07,300
And for a start and install structure, right?

183
00:12:07,510 --> 00:12:13,300
And we know that now we have updated the AP scalar value of five structure, right?

184
00:12:13,300 --> 00:12:19,030
So we'll just be adding that we're here now just to confirm whether it is asking about it.

185
00:12:19,030 --> 00:12:22,000
There are simple value regulators asking for a value.

186
00:12:23,200 --> 00:12:25,600
So we just need to get to the heart.

187
00:12:26,950 --> 00:12:27,510
Risky.

188
00:12:27,550 --> 00:12:27,910
Right?

189
00:12:28,060 --> 00:12:35,230
So this is how we feed the this killer, well, we must be having a function to set up the integral

190
00:12:35,230 --> 00:12:35,770
value, right?

191
00:12:35,770 --> 00:12:39,450
So we would just be exploring the functions which are available.

192
00:12:39,460 --> 00:12:43,330
So do you quickly go to all the countries which are present in the driveway?

193
00:12:43,330 --> 00:12:47,890
You would just go to an outline tap and then find out whether we have a function to set up an interval,

194
00:12:47,900 --> 00:12:48,130
right?

195
00:12:48,130 --> 00:12:51,790
So this gives them easy access to all the function which operates in the chamber.

196
00:12:52,090 --> 00:12:53,250
So we'll just be copying this.

197
00:12:53,260 --> 00:12:55,420
This again required an instant structure.

198
00:12:55,490 --> 00:12:58,000
OK, and then the interval value, right?

199
00:12:58,000 --> 00:13:00,820
So we go ahead and we call this function.

200
00:13:01,890 --> 00:13:07,720
Look, first, one is an instance to register UTC and then the interval value, right?

201
00:13:07,720 --> 00:13:11,380
So the turnout interval where we have to run into one right, right?

202
00:13:11,680 --> 00:13:14,800
So this is how we configure reskill.

203
00:13:14,840 --> 00:13:19,030
And the last thing that is required is to set up the correct option, right?

204
00:13:19,390 --> 00:13:25,360
So let me just go ahead and analyze the different options which are present in our driver, right,

205
00:13:25,360 --> 00:13:25,660
Rachel?

206
00:13:26,860 --> 00:13:31,720
We are not utilizing an external clock, so this is what we do not require.

207
00:13:31,810 --> 00:13:37,720
We also do not required trialing each forex 10:00 since we are not working with an external clock.

208
00:13:37,930 --> 00:13:42,360
We will be working in that interval mode and that it just work in a downward rate.

209
00:13:42,370 --> 00:13:46,900
So those are the two things that we need to configure, right?

210
00:13:46,900 --> 00:13:48,220
So let me just go ahead.

211
00:13:49,300 --> 00:13:51,190
You are mean cold, right?

212
00:13:52,320 --> 00:13:54,540
And we'll be updating an option, right?

213
00:13:55,650 --> 00:13:57,270
So data dot.

214
00:13:58,250 --> 00:14:05,180
All right, so this will leak was to the existing option that we have, right, so did the dark option.

215
00:14:06,730 --> 00:14:10,770
OK, I will just be ordering it with the option that we want to separate.

216
00:14:10,960 --> 00:14:15,880
This is the same strategy that we follow when we want to set the specific option, right?

217
00:14:15,880 --> 00:14:18,220
So we'll be calling an interval mode option.

218
00:14:19,530 --> 00:14:26,790
OK, and one more thing that we're going to add is the down, right, so just be calling for decrement

219
00:14:26,790 --> 00:14:27,260
with you.

220
00:14:27,360 --> 00:14:27,630
Right?

221
00:14:28,230 --> 00:14:29,900
So these are the two options that we want.

222
00:14:30,210 --> 00:14:36,540
So once we update the the number of structure, we just need to look for any that could be used to set

223
00:14:36,540 --> 00:14:37,260
an option, right?

224
00:14:37,260 --> 00:14:43,410
So we go ahead and in and out later, we will be finding out whether we have a function to set an option

225
00:14:43,410 --> 00:14:43,680
rate.

226
00:14:45,200 --> 00:14:51,170
So here we have the set option, right, so we go ahead and copy this function.

227
00:14:51,320 --> 00:14:53,150
OK, and then Hala will not see.

228
00:14:54,880 --> 00:15:00,640
So this required a first argument as an instance section, and the second argument is the option that

229
00:15:00,640 --> 00:15:01,390
you want to say.

230
00:15:02,050 --> 00:15:07,870
So first argument is though instead such a registry, and we know that the option of presenting an.

231
00:15:08,950 --> 00:15:14,470
Leader adoption rate, so this is how you set up an option, right, so all the food parameters which

232
00:15:14,470 --> 00:15:19,990
are required to correctly configure it, describing what I've incorrectly specified, right?

233
00:15:19,990 --> 00:15:26,710
So we specify that output frequency utilizing an output frequency, we computed interval this and then

234
00:15:26,710 --> 00:15:28,870
we set up pre-schooler as well as into it.

235
00:15:29,140 --> 00:15:31,720
Finally, we also correctly set up an option, right?

236
00:15:31,720 --> 00:15:38,800
So before we proceed to start an operation, the first thing that we always do is to stop forcefully

237
00:15:38,800 --> 00:15:39,490
stop our.

238
00:15:40,420 --> 00:15:44,240
Damon wrote a counter right, so to do that, we do have a functional here.

239
00:15:44,340 --> 00:15:46,390
So let me just go on this over here.

240
00:15:46,900 --> 00:15:51,250
So first thing, before we configure it, we will be stopping.

241
00:15:52,690 --> 00:15:53,920
All right.

242
00:15:53,980 --> 00:15:56,830
So now we are done with all the configuration that you need to do.

243
00:15:56,860 --> 00:15:59,290
OK, so you need to correctly setup an option.

244
00:15:59,300 --> 00:16:03,220
You need to specify input output frequency that you want.

245
00:16:03,460 --> 00:16:10,130
Then utilizing calculated double trauma frequency, you'll be calculating interval as well as a preschooler.

246
00:16:10,150 --> 00:16:10,480
OK.

247
00:16:10,630 --> 00:16:18,520
And then you'll be utilizing set preschooler insect interval function to add the interval entry scalar

248
00:16:18,520 --> 00:16:20,200
value that you get from this function.

249
00:16:20,230 --> 00:16:21,060
Great to know.

250
00:16:21,070 --> 00:16:23,560
Let's try to start an operation off fire.

251
00:16:25,330 --> 00:16:31,940
Great in first, guess what we're going to do is we will just be analyzing the values of a counter after

252
00:16:31,940 --> 00:16:32,050
that.

253
00:16:32,050 --> 00:16:32,860
I love the Emirates.

254
00:16:32,860 --> 00:16:37,990
We know that we have used an output frequency of winners, so this will give us a delay of one second,

255
00:16:38,260 --> 00:16:38,560
right?

256
00:16:38,650 --> 00:16:44,020
So we go ahead and try to find out the function that we have to stack the timer operation, right?

257
00:16:44,020 --> 00:16:46,360
So we have a bad start.

258
00:16:46,600 --> 00:16:51,990
We just required an instant structured as an argument, and this is used to start an operation of our

259
00:16:52,060 --> 00:16:52,870
ADC late.

260
00:16:52,900 --> 00:16:53,950
So we'll just be adding.

261
00:16:54,950 --> 00:17:02,390
Start here and then right now, if you analyze the functions that are available in driver, we do not

262
00:17:02,390 --> 00:17:08,900
have a function like is expired, which is available in the case of a 32 bit private time, right?

263
00:17:09,620 --> 00:17:15,830
So we do not find anything as is expired over here, right to in the previous case, we utilized that

264
00:17:15,830 --> 00:17:19,310
as a pooling function, which is utilizing the CPU resources.

265
00:17:20,610 --> 00:17:24,490
And giving us an idea about whether timer is expired on.

266
00:17:24,660 --> 00:17:24,890
Right.

267
00:17:25,140 --> 00:17:30,000
But we do have another function, which is exactly similar to what we utilize in the previous year.

268
00:17:30,000 --> 00:17:32,310
Also so here also, we have a great counter value.

269
00:17:32,790 --> 00:17:35,340
And since we are operating in a downward so.

270
00:17:36,310 --> 00:17:42,790
Depending on are in double frequency and a preschooler, somebody will be loaded in encounter and then

271
00:17:42,790 --> 00:17:49,140
our counter will start discriminating because we are choosing the mode of operation to be out.

272
00:17:49,150 --> 00:17:54,340
And we know that at the end of the time that we specified this will be that zero, right?

273
00:17:54,370 --> 00:17:56,170
So let me just use this function.

274
00:17:56,260 --> 00:17:56,890
We're here.

275
00:17:58,000 --> 00:17:59,050
Gate counter value.

276
00:17:59,350 --> 00:18:05,500
And this returns if you analyze so this written a 16 16 bit value rate, so you're 16.

277
00:18:05,950 --> 00:18:09,880
I didn't like you, so I trust and be associate returns.

278
00:18:09,970 --> 00:18:11,560
You did what innocuous?

279
00:18:11,560 --> 00:18:12,400
It can be better today.

280
00:18:12,480 --> 00:18:13,690
U16 value it.

281
00:18:13,990 --> 00:18:16,590
So let me just declare you 16 valuable, OK?

282
00:18:16,630 --> 00:18:20,950
And that will be storing the value that has been written by that function, right?

283
00:18:21,070 --> 00:18:21,460
So.

284
00:18:22,830 --> 00:18:29,790
This required an argument that an instance of direct, so we'll go ahead and act now immediately.

285
00:18:29,790 --> 00:18:37,140
Once we start, our DTC will add some needed right and then we will be calling this get out of the well.

286
00:18:37,150 --> 00:18:42,270
Now we know that since we are working within one hertz frequency, so the max do you that in Karachi

287
00:18:42,360 --> 00:18:43,290
is one second, right?

288
00:18:43,530 --> 00:18:45,930
So we will be utilizing you sleep great.

289
00:18:45,930 --> 00:18:49,230
So this provides us the delay in microsecond.

290
00:18:49,260 --> 00:18:55,370
And here we try to add a delayed millisecond race, the first at three, zero and then hundreds.

291
00:18:55,400 --> 00:19:01,320
So this basically will give us a time of hundred milliseconds or delay of a millisecond and then will

292
00:19:01,320 --> 00:19:03,390
be capturing the current counter-rally.

293
00:19:03,720 --> 00:19:04,050
OK.

294
00:19:04,110 --> 00:19:06,300
That really will be sending one to concentrate.

295
00:19:06,390 --> 00:19:12,070
So what we got to do is we will be changing the delay and then we'll be observing whether Counter-rally

296
00:19:12,070 --> 00:19:13,800
was actually discriminating or not.

297
00:19:13,980 --> 00:19:21,270
So that help us understand that there are is correctly operating in a downward right to intent and then

298
00:19:22,080 --> 00:19:23,490
count value.

299
00:19:23,940 --> 00:19:24,260
Right.

300
00:19:24,270 --> 00:19:27,180
So let me just bring the value in on decimal format.

301
00:19:27,480 --> 00:19:32,490
Do not forget to add a new line character, and the variable that is holding the value of our account

302
00:19:32,490 --> 00:19:33,750
is called right.

303
00:19:34,350 --> 00:19:35,990
So this completes our application.

304
00:19:36,000 --> 00:19:41,190
This will be executing for a few instances just to analyze whether RTC is correctly operating.

305
00:19:41,190 --> 00:19:45,890
And then we will understand how the continuous speech and the dealer at a regular interval, right?

306
00:19:45,900 --> 00:19:47,850
So let's just build our application budget.

307
00:19:49,060 --> 00:19:54,360
So press control, we do start the process of reading your application project, and once builders finished,

308
00:19:54,370 --> 00:19:56,260
we will select our application project.

309
00:19:56,380 --> 00:19:59,980
OK, debug as large one hardware, right?

310
00:20:01,220 --> 00:20:05,960
Now we have already corrected our right this terminal to account, but only thing that we need to do

311
00:20:05,960 --> 00:20:07,730
is to click on this resume button, right?

312
00:20:08,160 --> 00:20:09,940
So now you could see DDCA need.

313
00:20:10,000 --> 00:20:15,830
A successful self-test is also successful in the counter value that we are getting is that our food

314
00:20:15,830 --> 00:20:18,170
aid, the fight rate.

315
00:20:18,170 --> 00:20:20,930
So this is for a delay of second rate.

316
00:20:21,770 --> 00:20:22,730
Now what are we going to do?

317
00:20:23,120 --> 00:20:24,740
We will be increasing our delay, right?

318
00:20:24,740 --> 00:20:29,460
So instead of one hundred milliseconds already just make it two hundred millisecond rate in this case,

319
00:20:29,460 --> 00:20:32,510
since our DTC is working in adult mode.

320
00:20:32,510 --> 00:20:35,450
So we are expecting the value to be lower than this value rate.

321
00:20:35,450 --> 00:20:38,600
So it should be lower than forty three fight, right?

322
00:20:38,600 --> 00:20:40,970
So let's just build our application project back.

323
00:20:42,190 --> 00:20:48,280
Once again, right, and then we will be again relaunching our application, so this is our debugger.

324
00:20:48,580 --> 00:20:51,370
Right click and then just relaunch our.

325
00:20:52,130 --> 00:20:52,390
Right?

326
00:20:54,830 --> 00:21:00,340
So once programming is successful, we just click on resume, but right now you could see in the previous

327
00:21:00,380 --> 00:21:06,350
case that we have either of or millisecond the value that we are getting is four, three five.

328
00:21:06,770 --> 00:21:12,050
And then when we increase it to two hundred millisecond, we are getting the current value of around

329
00:21:12,290 --> 00:21:13,930
four three four one five eight.

330
00:21:13,930 --> 00:21:19,190
So this suggests that that it is this correct operating in a downward because as compared to a previous

331
00:21:19,190 --> 00:21:23,000
case, as we increase the delay, our Kotwali should be DiClemente great.

332
00:21:23,720 --> 00:21:26,210
Let us just try to implement value one more time.

333
00:21:27,080 --> 00:21:32,020
Let us meet this as 500 millisecond rate build an application project target.

334
00:21:33,500 --> 00:21:38,000
So once Bill, finish against, select the debugger and click on the launch rate.

335
00:21:39,600 --> 00:21:46,560
So we go to a light and click on a resume, but right now you can clearly observe that within five minutes,

336
00:21:46,920 --> 00:21:50,130
we reached up to two seven one five five, right?

337
00:21:51,580 --> 00:21:54,700
So this clearly indicates that we are correctly operating in a dump.

338
00:21:55,120 --> 00:21:58,330
Now let me just try to modify her, who says that we will do?

339
00:21:59,330 --> 00:22:05,000
To need to do that and regular intervention will just be commenting all this out right now.

340
00:22:05,120 --> 00:22:05,540
John Reid.

341
00:22:06,260 --> 00:22:10,160
DeLay or continuous delay of one second vote to leave first utilized why?

342
00:22:10,160 --> 00:22:13,400
Even so, this allows us to continue to see the need to delay.

343
00:22:13,580 --> 00:22:17,650
The first thing that we're going to do here is to start our.

344
00:22:18,770 --> 00:22:23,180
Judy, right, so once we start our deeds now, we will beat the LA.

345
00:22:24,120 --> 00:22:29,610
Delivery just to a zero rate that we do not have any function that could be giving us an idea whether

346
00:22:29,610 --> 00:22:34,960
our timer is expired or not, but we could take the help of get out the value because at the end when

347
00:22:34,980 --> 00:22:41,520
our P.T.S.D, just to the time specified by and use it, this will return zero rate so we can just copy

348
00:22:41,520 --> 00:22:42,240
this function.

349
00:22:43,050 --> 00:22:47,820
OK, we could use a loop again and then we visualize this get down.

350
00:22:47,830 --> 00:22:50,390
The value function does require just a single argument.

351
00:22:50,400 --> 00:22:52,830
We just see right now we know that.

352
00:22:54,240 --> 00:23:00,900
Anything other than zero will be considered as great, so whenever we do, whenever we have to, we

353
00:23:00,900 --> 00:23:04,740
will be simply waiting over here as soon as dysfunctional rate zero.

354
00:23:04,770 --> 00:23:07,350
So that will be my fault and never will be coming out, right?

355
00:23:07,710 --> 00:23:13,680
So this also suggests that we reached to the time that you specified all the delay that you want out

356
00:23:13,680 --> 00:23:16,020
of or duty rates as soon as this rate zero.

357
00:23:16,410 --> 00:23:22,530
We completed the time that you want to reiterate are the account that we have no date for a specified

358
00:23:22,530 --> 00:23:24,630
output frequency right after this.

359
00:23:25,290 --> 00:23:27,270
What we want to do is we'll just be.

360
00:23:28,400 --> 00:23:30,290
Stopping the.

361
00:23:31,370 --> 00:23:36,040
You see, this is just a two way security that we do, in fact, we already know that it was just a

362
00:23:36,040 --> 00:23:36,390
zero.

363
00:23:36,400 --> 00:23:38,080
It won't be running again.

364
00:23:38,440 --> 00:23:45,550
This is just a two way security that we act, that we will be forcefully stopping our DDC rate and then

365
00:23:45,550 --> 00:23:46,810
we'll just be mentioning.

366
00:23:47,770 --> 00:23:50,560
Our delay of one second achieve, right, so delay.

367
00:23:51,620 --> 00:23:53,180
Off one second.

368
00:23:54,450 --> 00:23:54,950
To you.

369
00:23:55,710 --> 00:23:56,070
OK.

370
00:23:57,070 --> 00:23:59,440
And then we will just be resetting.

371
00:24:01,570 --> 00:24:05,410
So if you just analyze the function that are available, OK?

372
00:24:06,790 --> 00:24:11,740
So we do have a function that could be used to reset our counter value.

373
00:24:11,960 --> 00:24:17,200
So this micro reset, the counter, this trend, this is what we want so that again, we could generate

374
00:24:17,200 --> 00:24:18,520
a delay of one second rate.

375
00:24:18,520 --> 00:24:19,810
So let's just go ahead.

376
00:24:20,780 --> 00:24:22,790
And called dysfunction.

377
00:24:24,470 --> 00:24:24,760
OK.

378
00:24:25,070 --> 00:24:29,930
And this again required a single instance, such as an occupancy rate.

379
00:24:31,320 --> 00:24:36,720
Now what this will do is this will be continuously running because we are utilizing violent, right?

380
00:24:36,960 --> 00:24:42,180
So we are starting an operation, then we are waiting for our timer to expire as soon as it expired

381
00:24:42,210 --> 00:24:43,380
will be coming out here.

382
00:24:43,680 --> 00:24:45,570
We are forcibly stopping Nazi.

383
00:24:45,570 --> 00:24:48,510
Then we are printing the delay of one second, achieve OK.

384
00:24:48,690 --> 00:24:52,780
And then we are resetting the counter right, right?

385
00:24:53,040 --> 00:24:56,850
So as soon as we reset a counter rally again, we will be starting to operate.

386
00:24:58,260 --> 00:25:04,190
Our TDCi again will be waiting for a timer to expire and then again sending this string on to a consumer.

387
00:25:04,290 --> 00:25:04,430
Right.

388
00:25:04,470 --> 00:25:09,480
So this is how you need the delay at a regular interval, depending on the output frequency that you

389
00:25:09,480 --> 00:25:14,610
want your output frequency frequencies one hearts we will be getting a delay of around one second rate

390
00:25:14,610 --> 00:25:19,210
delay, just build our application and see whether it is working as expected, right?

391
00:25:19,700 --> 00:25:22,470
So we, as rebels finish, we go ahead and.

392
00:25:23,620 --> 00:25:26,140
Debug as launch on heart rate.

393
00:25:27,090 --> 00:25:31,770
Now we already have our right, this terminal connected to a composite, we'd just be clearing up our

394
00:25:31,770 --> 00:25:35,880
console now and then we will be clicking on the resume.

395
00:25:35,880 --> 00:25:38,250
But right, so it is successful.

396
00:25:38,490 --> 00:25:46,920
And then you could clearly see after a delay of one second, OK, we able to continuously get the string

397
00:25:47,220 --> 00:25:48,120
printing on the this.

398
00:25:48,870 --> 00:25:49,140
Right?

399
00:25:49,260 --> 00:25:50,940
This is how you utilize it.

400
00:25:51,570 --> 00:25:57,150
Now this is a bit different as compared to our 32 bit private timer and a washed off timer because we

401
00:25:57,150 --> 00:25:59,520
need to perform a different configuration, right?

402
00:25:59,520 --> 00:26:02,640
So whenever you have multiple parameters that are used to.

403
00:26:03,580 --> 00:26:09,250
Configure you up to see that you declared a structure, because then it becomes very easy to handle

404
00:26:09,250 --> 00:26:10,120
the structure, right?

405
00:26:10,510 --> 00:26:13,090
And then you perform an initialization.

406
00:26:13,330 --> 00:26:20,260
So now you have an idea about what are we going to do is since we can deduce the will to need the delay

407
00:26:20,260 --> 00:26:27,130
of one second, OK, we could modify this court says that we able to generate the blinking effect on

408
00:26:28,150 --> 00:26:29,050
the right.

409
00:26:29,050 --> 00:26:34,990
So we'll just be modifying on hybrid design and the code just to have an understanding of how you incorporate

410
00:26:34,990 --> 00:26:36,010
multiple basis.

411
00:26:36,340 --> 00:26:39,760
You can utilize D.D.S. to generate the event data regularly.
