1
00:00:00,310 --> 00:00:03,850
Lily, to understand how we do profiling with any set time.

2
00:00:03,870 --> 00:00:04,170
All right.

3
00:00:04,560 --> 00:00:08,830
So what we're going to do is in a fundamental block design, we'll just be adding any second.

4
00:00:09,160 --> 00:00:12,480
So we are here utilizing only single time.

5
00:00:12,580 --> 00:00:15,270
So this second option should be A. Right?

6
00:00:15,630 --> 00:00:22,200
And the most important parameter for us is to understand the field clock frequency because when we are

7
00:00:22,200 --> 00:00:29,100
calculating the amount of time that our function to execute, we must know what is the frequency at

8
00:00:29,100 --> 00:00:30,600
which time is tell.

9
00:00:31,140 --> 00:00:38,250
So if you just reconfigure same processing system and go to clock configuration, there you have a fabric

10
00:00:38,250 --> 00:00:39,650
clock specification, right?

11
00:00:39,660 --> 00:00:44,430
So we are creating, I feel, fabric lock 50 Maycock.

12
00:00:44,820 --> 00:00:48,620
So this is an operating frequency for our excitement, right?

13
00:00:48,630 --> 00:00:50,190
So this is an important parameter.

14
00:00:50,520 --> 00:00:57,300
Now we remember when we are getting the counter value, so we basically know how many clock ticks are

15
00:00:57,330 --> 00:01:03,180
left straight because each clock are counted, value will increment or decrement depending on the mood

16
00:01:03,180 --> 00:01:04,640
that we have set, right?

17
00:01:04,950 --> 00:01:11,580
So something that could be getting old when we call gate counter value function is the number of clock

18
00:01:11,580 --> 00:01:13,070
ticks that have been elapsed.

19
00:01:13,740 --> 00:01:21,540
So just your fundamental triangulation since APL fabric is operating at 50 MIGA, so inverse of it will

20
00:01:21,540 --> 00:01:25,440
be zero point two into 10 to minus seven.

21
00:01:25,470 --> 00:01:25,770
Right?

22
00:01:26,220 --> 00:01:34,560
So to get the delay in microsecond, we just need to shift one digit left to zero point zero two into

23
00:01:34,570 --> 00:01:35,610
tennis to minus six.

24
00:01:35,620 --> 00:01:41,670
So whenever you want to calculate the delay in microsecond, you just need to find out the number of

25
00:01:41,670 --> 00:01:43,470
clock ticks that are left standing.

26
00:01:43,560 --> 00:01:46,680
You just need to multiply them with the zero point zero.

27
00:01:46,800 --> 00:01:51,900
Now remember, here we are multiplying within our starting point number, so we will be printing the

28
00:01:51,900 --> 00:01:54,110
value in the starting point for my right.

29
00:01:54,600 --> 00:01:58,110
When we consider lettuces, you mean one delay in a nanosecond rate.

30
00:01:58,140 --> 00:02:04,890
So if we just do the inverse of 50 into the industry, six, that will be getting 0.2 intuitiveness

31
00:02:04,890 --> 00:02:05,730
to minus seven.

32
00:02:06,090 --> 00:02:06,420
OK.

33
00:02:06,630 --> 00:02:10,710
So if you just multiply by 100 here, we could add in this to minus two, right?

34
00:02:10,980 --> 00:02:13,620
So it was zero point two and two hundred and two.

35
00:02:13,620 --> 00:02:15,030
Then this two minus nine.

36
00:02:15,090 --> 00:02:15,360
Right.

37
00:02:15,690 --> 00:02:20,010
And if you just multiply this two, we will be getting twenty nine.

38
00:02:20,410 --> 00:02:20,660
Great.

39
00:02:20,670 --> 00:02:27,270
So whenever you want to calculate the delay in a nanosecond, you just need to multiply whatever the

40
00:02:27,270 --> 00:02:33,240
clock ticks that you are getting when you subtract, start dining counterbalance and then you'll be

41
00:02:33,240 --> 00:02:35,600
multiplying it with that 20, right?

42
00:02:36,090 --> 00:02:38,610
So with this calculation, we'll just be setting five.

43
00:02:38,820 --> 00:02:42,560
Now this is a goal which we also discussed in a pool, right?

44
00:02:43,080 --> 00:02:45,220
So we first initialize our timer.

45
00:02:45,300 --> 00:02:52,500
OK, specifying the device addy and then the instant structuring config structure, performing the self-test.

46
00:02:52,500 --> 00:02:57,660
And then we are just checking whether initialization of time very successful or not great.

47
00:02:58,170 --> 00:03:00,480
And here we are, just setting up an option.

48
00:03:00,750 --> 00:03:01,200
So.

49
00:03:02,470 --> 00:03:09,640
Had the option that we set is down more, so our counter will be counting in, OK, and that basically

50
00:03:09,640 --> 00:03:13,520
mean related, you may declare to where you will do it right.

51
00:03:13,540 --> 00:03:15,910
So this is the function which we want to.

52
00:03:16,990 --> 00:03:23,110
Used for our profile, so we'll just be calculating the time elapsed for this function, right?

53
00:03:23,320 --> 00:03:31,120
So we have two variable stock variable and variable rate and both of them Spiral EU-Turkey like right

54
00:03:31,540 --> 00:03:36,100
now get value will basically return the current value of our counter right hand.

55
00:03:36,340 --> 00:03:38,760
Here we are utilizing the single timer.

56
00:03:38,770 --> 00:03:42,440
So here we specified see right and EMI as the timer instant.

57
00:03:42,460 --> 00:03:44,530
So here we will be getting some value.

58
00:03:44,920 --> 00:03:53,050
And since our counter is operating in a normal so and value will be less than stock than it was when

59
00:03:53,050 --> 00:03:55,780
we reach over here are accountable.

60
00:03:56,950 --> 00:04:01,060
Reduce its value depending on the to collapse, right?

61
00:04:01,660 --> 00:04:08,440
So when we consider the down option, the value that we calculate will be stock minus the egg because

62
00:04:08,470 --> 00:04:14,980
our stock value of a counter will be more as compared to hey, right now, this will represent the number

63
00:04:14,980 --> 00:04:18,670
of laps we'll get for a valuation of this.

64
00:04:19,790 --> 00:04:28,150
Specific function that we considered here, it is sobering now to calculate the time elapsed in nanosecond

65
00:04:28,220 --> 00:04:31,760
as this because we just need to multiply by 20.

66
00:04:31,800 --> 00:04:36,800
OK, so what are you up to that we receive would just be multiplying them with a 20 and will be getting

67
00:04:36,800 --> 00:04:38,640
the DV in nanoseconds, right?

68
00:04:38,660 --> 00:04:40,360
And that is what we are doing here.

69
00:04:40,460 --> 00:04:43,430
So this is an integer we are utilizing.

70
00:04:43,430 --> 00:04:46,500
But since the start line isn't like the play by play.

71
00:04:46,760 --> 00:04:55,490
Now when we consider that we want to have a value in a microsecond, OK, so we need to multiply by

72
00:04:55,490 --> 00:04:56,510
zero point zero.

73
00:04:56,900 --> 00:05:01,940
So here we already discussed we need to multiply by 0.02 to get microsecond.

74
00:05:02,630 --> 00:05:06,200
And since this is a floating point number, we utilize brain death.

75
00:05:06,320 --> 00:05:06,680
OK.

76
00:05:06,710 --> 00:05:14,180
This will be timeless in microseconds and here puts into your graph stack minus it multiplied by zero

77
00:05:14,180 --> 00:05:14,810
point zero.

78
00:05:15,260 --> 00:05:18,680
So this is how we will be displaying the values on a.

79
00:05:19,100 --> 00:05:19,400
Right?

80
00:05:19,610 --> 00:05:23,630
So first, we are getting the number of plotted, and that will be very simple.

81
00:05:23,900 --> 00:05:30,080
We just need to calculate the difference between these two variable to get the values in a nanosecond.

82
00:05:30,080 --> 00:05:31,760
We've just been multiplying by 10.

83
00:05:32,180 --> 00:05:33,480
And to get the values in.

84
00:05:34,990 --> 00:05:41,280
And to get the values in a microsecond, we just need to multiply it by zero point zero rate.

85
00:05:42,390 --> 00:05:48,570
So this complete, then it will let it just proceed for execution of a court that gets be clicking on

86
00:05:48,570 --> 00:05:53,940
program FPGA first and then right click run as launch on.

87
00:05:54,490 --> 00:05:54,750
Right.

88
00:05:55,620 --> 00:06:01,440
So here you are an illusion as 10 minutes the time you need to successfully and.

89
00:06:02,600 --> 00:06:11,150
Here you could see that this is the string that is sending on a console and it is used for competition

90
00:06:11,150 --> 00:06:12,530
rates, the number of clock ticks.

91
00:06:13,190 --> 00:06:14,090
127.

92
00:06:14,600 --> 00:06:18,000
Time elapsed in nanoseconds two five four zero.

93
00:06:18,500 --> 00:06:20,300
OK and time elapsed.

94
00:06:20,450 --> 00:06:24,920
Microsecond is two point five four zero, right?

95
00:06:25,070 --> 00:06:32,240
So this is how you could utilize any side timer to profile the functions or any other construct that

96
00:06:32,240 --> 00:06:34,130
you want your new application.