1
00:00:00,150 --> 00:00:02,640
Now we know how we use any timer.

2
00:00:02,670 --> 00:00:08,760
Now let us try to explore the other, that is an to work that we have discussed when we are working

3
00:00:08,760 --> 00:00:10,860
with the rather time world, right?

4
00:00:11,490 --> 00:00:13,230
So to enable or to learn more.

5
00:00:13,260 --> 00:00:16,580
We just need to go ahead and look for adoption, right?

6
00:00:16,590 --> 00:00:22,740
So if you go to the Daimler driver file, right, so here you get the list of an option which are allowed

7
00:00:22,740 --> 00:00:24,540
to use with any exciting right.

8
00:00:25,540 --> 00:00:29,300
So to utilize an outlaw or we just need to enable it.

9
00:00:29,520 --> 00:00:32,080
So just copy and to reload option.

10
00:00:32,590 --> 00:00:35,650
Go back to our main goal where we are creating an option.

11
00:00:35,710 --> 00:00:37,890
So here we are updating our option, right?

12
00:00:37,890 --> 00:00:43,960
So we just need to add again in our operator and then we need to as an it or to reload option.

13
00:00:44,100 --> 00:00:45,850
Right now, what this will do is.

14
00:00:46,880 --> 00:00:53,540
As soon as our timer expired or just to a value of zero, it will automatically reload it with the value

15
00:00:53,540 --> 00:00:57,710
that we specified that is providing a delay of five second rate.

16
00:00:57,710 --> 00:00:59,530
So to verify that behavior.

17
00:00:59,570 --> 00:01:02,570
What we going to do is we'll just modify our application.

18
00:01:02,570 --> 00:01:04,120
So let it just use a whiteboard.

19
00:01:04,940 --> 00:01:05,270
OK.

20
00:01:06,510 --> 00:01:13,170
Because with the lottery more, be able to generate a continuous event rate, so even at an interval

21
00:01:13,170 --> 00:01:13,890
of five second.

22
00:01:14,340 --> 00:01:16,230
So we will be utilizing a light.

23
00:01:16,500 --> 00:01:17,720
We are starting a timer.

24
00:01:17,730 --> 00:01:24,270
So the count that we have loaded into our county register will start discriminating, right, because

25
00:01:24,270 --> 00:01:26,310
we are operating our timer in their normal.

26
00:01:26,520 --> 00:01:29,430
And then we will be waiting till it reaches to a zero.

27
00:01:29,750 --> 00:01:38,910
OK, and as soon as it reaches to zero, since we are utilizing water, it will again be re initializing.

28
00:01:38,910 --> 00:01:41,550
I count registered to this value, right?

29
00:01:41,820 --> 00:01:44,550
So we'll be finding that we bring this statement.

30
00:01:44,550 --> 00:01:48,390
And again, when we go up, we will start operating our timer, right?

31
00:01:48,660 --> 00:01:53,790
So let me just go ahead and try to verify whether this is working as expected, right?

32
00:01:54,000 --> 00:01:56,620
So remember, we enable all options.

33
00:01:56,660 --> 00:01:58,890
We just lost our application project.

34
00:01:59,670 --> 00:02:03,600
You could, in fact, had a stop student who were here.

35
00:02:03,870 --> 00:02:08,710
OK, then bring the statement and then again, start a timer that could also be done right.

36
00:02:08,760 --> 00:02:11,560
So if you want, you would just copy this, OK?

37
00:02:11,580 --> 00:02:18,490
And as I would expect, we will be forcefully stopping our timer, then sending the string on to a console

38
00:02:18,510 --> 00:02:20,150
and then again, starting our timer.

39
00:02:20,370 --> 00:02:23,320
So let's go ahead and try to build our application project.

40
00:02:23,340 --> 00:02:28,200
This is the first step that we do as we complete our development of our application.

41
00:02:28,410 --> 00:02:33,870
So once Bill is finished with select our application project debug launch on hardware.

42
00:02:33,920 --> 00:02:34,170
Right.

43
00:02:34,740 --> 00:02:37,020
So this will automatically program and FPGA.

44
00:02:37,060 --> 00:02:40,710
It would also switch our perspective from design to DBA.

45
00:02:41,070 --> 00:02:46,250
Right now we go ahead and we just need to connect the to Syria told me, right?

46
00:02:46,310 --> 00:02:48,740
So we'll click on this plus button with select confirm.

47
00:02:49,080 --> 00:02:52,770
And the body that will be choosing is one one five two zero zero.

48
00:02:52,810 --> 00:02:53,020
Right.

49
00:02:53,050 --> 00:02:55,220
So once this is done, just click on resume button, right?

50
00:02:55,230 --> 00:02:58,910
So time related, successful and self test is also successful.

51
00:02:59,130 --> 00:03:04,430
So after an interval of five second, you'll be noticing that we get a delay of five second you right?

52
00:03:04,890 --> 00:03:10,380
And since we enable the not to reload more, you could actually see at an individual fight.

53
00:03:10,380 --> 00:03:15,750
Second, OK, we are getting a multiple event rate, so we get a delay of five second.

54
00:03:15,750 --> 00:03:22,230
Again, we reload our counter to the value that we specified and then again, we start our time, right?

55
00:03:22,470 --> 00:03:28,470
So this is how you could see with an auto reload mode, we could continuously to date night and regular

56
00:03:28,470 --> 00:03:29,210
intervals, right?

57
00:03:29,220 --> 00:03:34,400
So this is a difference that you find between an auto load mode and a normal rate.

58
00:03:34,440 --> 00:03:38,310
Two in a normal mode, once our counter expired, it will stay at zero.

59
00:03:38,400 --> 00:03:45,320
But when we enable auto reload mode, in that case, our counter will be automatically reloaded with

60
00:03:45,570 --> 00:03:47,410
value that user specified right?
