1
00:00:00,060 --> 00:00:05,970
You know, let's assume you are in a situation where you want to profile your entire application consisting

2
00:00:05,970 --> 00:00:12,720
of four different function rates, so instead of individually utilizing the time since, we do have

3
00:00:12,720 --> 00:00:14,420
a limited number of any time.

4
00:00:14,850 --> 00:00:15,180
OK.

5
00:00:15,330 --> 00:00:22,710
So in that is the good idea will be to utilize an internal feature that we have in any way designed

6
00:00:22,800 --> 00:00:27,510
to profile our entire application rate so will be understanding an entire process.

7
00:00:27,540 --> 00:00:33,390
Now this is bit difficult at the start because we need to follow a lot of different configurations stating

8
00:00:33,630 --> 00:00:39,120
that we'll just be blindly replicating our process for first three to, for example.

9
00:00:39,720 --> 00:00:45,240
And then you could perform the profiling for a different application on your great tool.

10
00:00:45,360 --> 00:00:47,340
Here we have utilized that script.

11
00:00:48,310 --> 00:00:53,800
And created a fundamental block to saying, right now what we're going to do is we will be fighting

12
00:00:53,800 --> 00:01:00,640
any excitability for which we will be writing an application consisting of a number of functions, OK,

13
00:01:00,640 --> 00:01:01,810
which we'll be profiling.

14
00:01:01,810 --> 00:01:05,560
So let's restore seed and customize our block.

15
00:01:05,600 --> 00:01:05,940
OK.

16
00:01:07,090 --> 00:01:13,630
Now, this to include the number of quote, which are necessary to interface the Dubai with the zinc

17
00:01:13,630 --> 00:01:14,380
processing just.

18
00:01:15,410 --> 00:01:19,910
So we go ahead to a beer spill configuration will enable our clock reset.

19
00:01:20,760 --> 00:01:26,160
OK, and then we also required an essay Zero in the Voice.

20
00:01:26,180 --> 00:01:26,570
OK.

21
00:01:26,600 --> 00:01:29,120
We also required a clock for our fabric.

22
00:01:29,120 --> 00:01:32,970
I know remember the profiling is done considering a clock rate.

23
00:01:32,990 --> 00:01:39,350
So if you consider the Blades, we need to add any timer, IP and independent timer IP that could not

24
00:01:39,350 --> 00:01:40,680
be used for any other purpose.

25
00:01:40,700 --> 00:01:47,660
Similarly, when we consider an processing system, since we have a number of internal timers available

26
00:01:47,660 --> 00:01:54,470
with the Xeon processing system for reprofiling, we prefer to use an issue timer rate to remember we

27
00:01:54,470 --> 00:01:57,080
are utilizing LSU timer for reprofiling.

28
00:01:57,320 --> 00:02:00,170
So you could not use it for any other purpose.

29
00:02:00,370 --> 00:02:01,850
So this is an important point to note.

30
00:02:02,150 --> 00:02:07,290
Now here we have added all the necessary ports which are required to Indivior's any excess GPI like

31
00:02:07,320 --> 00:02:11,150
Polaris grass seed and had any, say, GPI.

32
00:02:11,720 --> 00:02:14,060
So we'll just configure it to work with a reality.

33
00:02:14,060 --> 00:02:18,300
So we'll select the single channels and we'll use an default.

34
00:02:18,650 --> 00:02:19,850
So this is what we're going to do.

35
00:02:20,120 --> 00:02:23,980
And then we perform a connection or commission, so this will automatically connect.

36
00:02:24,350 --> 00:02:26,170
I say GPI.

37
00:02:26,290 --> 00:02:31,620
It was interesting system utilizing any sign to connect to this completes our fundamental block today.

38
00:02:32,310 --> 00:02:34,640
We go and validate our design.

39
00:02:35,240 --> 00:02:41,630
So once validation is successful, right, so we proceed to a small step and we create an actual wrapper,

40
00:02:41,630 --> 00:02:41,920
right?

41
00:02:43,390 --> 00:02:44,590
So a rapper is ready.

42
00:02:44,620 --> 00:02:50,860
Now, if you go to a board that Rachel, you could clearly see we have one, two and three boards which

43
00:02:50,860 --> 00:02:52,000
are present in our design.

44
00:02:52,300 --> 00:02:57,110
So we already know that we are, in fact, is connected to the respect to hardware.

45
00:02:57,620 --> 00:02:57,910
Right.

46
00:02:57,910 --> 00:03:03,580
If you consider a little bit too, you do see a low mark just neighboring to affordability, and this

47
00:03:03,580 --> 00:03:08,830
signifies that the LCD board has been already connected to the respective hardware.

48
00:03:09,190 --> 00:03:12,340
So we could directly proceed for generation of.
