WEBVTT

00:00.060 --> 00:06.320
Let's start understanding how quickly so this will be the first examples we will follow from the beginning.

00:07.050 --> 00:09.500
Let's start with the CREATE project with the next.

00:09.630 --> 00:13.360
Now we'll stick to a different project name and project location, OK?

00:14.100 --> 00:16.140
And will select another project.

00:16.140 --> 00:17.380
Will next.

00:17.730 --> 00:20.330
OK, so we'll just create a file over here.

00:20.610 --> 00:28.460
We'll just name it as a human and we'll be implementing first Canongate and then we'll try to build

00:28.470 --> 00:29.310
a complex design.

00:29.370 --> 00:29.700
OK.

00:30.090 --> 00:32.200
Now remember when you are selecting a board.

00:32.460 --> 00:38.900
OK, so this gives us an ability to specifically choose for which specific category of device your IP

00:38.940 --> 00:39.870
will be compatible.

00:39.900 --> 00:47.960
OK, so for example, if I here choose a nexus for the idea, OK, which consists of an Arctic seven.

00:48.780 --> 00:51.900
So our IP will be compatible with an Arctic seven.

00:52.380 --> 00:58.940
So we do get a provision to change for all category of devices that IP will support.

00:59.250 --> 01:05.430
But in general, if you do not change, the basic setting will be finding your IP will only be eligible

01:05.430 --> 01:07.200
for working with an exception.

01:07.230 --> 01:15.690
OK, so this gives us an ability to selectively enable and disable IP in the repository when we send

01:15.690 --> 01:16.470
it to a user.

01:17.390 --> 01:19.900
Which created a project on a specific goal.

01:20.080 --> 01:26.690
OK, so we'll just be aware when we are selecting the device so that we by default, make our IP compatible

01:26.690 --> 01:28.910
with that specific FPGA family.

01:28.940 --> 01:29.140
OK.

01:29.180 --> 01:33.700
So when other users try to create a project with other family, this is, what, seven?

01:34.010 --> 01:38.460
And if we have made our compatibility of an IP only for an four, it's seven.

01:38.810 --> 01:43.190
So even though he had an IP to a repository, but he won't be able to see.

01:43.910 --> 01:51.100
OK, so this is how we can use the feature to of compatibility to selectively choose which family are

01:51.110 --> 01:51.320
right.

01:52.070 --> 01:54.610
OK, then we'll take next and we'll take.

01:57.360 --> 02:03.070
Now, this will create a whole lot of love inside our project where we can work around and complete

02:03.450 --> 02:10.260
picture design, OK, so far and what we'll do is we'll assume that there are two inputs and we have

02:10.260 --> 02:19.260
an output and will be implementing a multiple times resume that we are implementing and eat that and

02:19.260 --> 02:26.280
try to go to inputs, will have a series of feedback and we will be an output with the size of the largest.

02:28.430 --> 02:36.620
OK, so now if you just go ahead, so we'll be finding that we have a completely OK and the implementation

02:36.620 --> 02:38.030
of it is very simple.

02:38.040 --> 02:47.360
So we'll be sticking with an dataflow model states the WI will be equal to the and this is the behavior

02:47.360 --> 02:57.680
that we want for great no here will first try to understand how we create and I will go to once and

02:57.680 --> 02:59.330
then we choose, create and package.

02:59.690 --> 03:06.740
OK, so here you get a provision where you can package a new IP for Wiwa to Apicultural, or you can

03:06.740 --> 03:14.360
in fact create any say Pettifer and attach it to an IP so that that IP can be utilized with those Syncora

03:14.360 --> 03:14.920
Micropolis.

03:14.930 --> 03:22.970
Plus because the default communication interface that is used for communication with an SPG based associates

03:22.970 --> 03:24.260
is an xiphoid.

03:24.950 --> 03:31.820
So we buy the IP package that you to you can use in that you could create an IP and then finally you

03:31.820 --> 03:37.580
can add that into an IP repository, which is the first option or the first provision that we get out

03:37.580 --> 03:38.590
of a package IP.

03:39.170 --> 03:47.920
And the second one that we get is the addition of an ex-wife to ah, OK, so we can in fact the Masters

03:47.930 --> 03:51.650
live or stream interface that will learned later on.

03:51.890 --> 03:55.220
If we have a requirement now we'll just click next.

03:55.940 --> 04:01.940
Now here you get an option whether to package your IP on the current project or you want to package

04:01.940 --> 04:09.110
or IP to a specific directory will choose the default option, which is package your IP to a current

04:09.110 --> 04:11.830
project that you also get an option to either accept.

04:12.350 --> 04:13.790
OK, next.

04:14.890 --> 04:21.970
And then we just click finish now, once you set up a configuration setting the finding, you get an

04:21.970 --> 04:22.660
IP package.

04:23.090 --> 04:25.680
OK, so you have an ID.

04:25.690 --> 04:32.620
So where we will be specifying the name of an IP and the description of an IP, the display name and

04:32.620 --> 04:33.440
so on and so forth.

04:33.700 --> 04:36.190
So what we do is we just name it as an.

04:38.710 --> 04:42.940
It look, in fact, what we do is and.

04:44.500 --> 04:45.540
And, Don.

04:49.390 --> 04:49.790
Eight.

04:51.200 --> 04:58.140
But OK, so this is I will be naming and then this is the first version, so we'll stick to this neat.

04:58.510 --> 05:02.300
OK, and the display name that we want is there.

05:02.330 --> 05:06.380
This is who we want it to be aligned to it.

05:09.960 --> 05:17.520
OK, this is what we want as it is right now, will go to a compatability, so here you can specifically

05:18.150 --> 05:23.070
choose, OK, which family your IP will support.

05:23.100 --> 05:28.710
OK, so what we'll do is we can just go ahead and then we can choose an Arctic seven.

05:28.870 --> 05:30.480
OK, to add.

05:31.360 --> 05:35.350
A new family, you have this option and to remove the family, you have this option.

05:35.370 --> 05:39.850
So, for example, if we want to make our IP compatible, we will give it another seven.

05:40.030 --> 05:46.150
OK, so what we can do is we just select everything, will just remove all the devices, then we click

05:46.150 --> 05:50.080
on plus, OK, and then we'll.

05:51.210 --> 05:54.240
Go to family explicitly offshoot.

05:54.580 --> 05:58.980
OK, and then we will select our Arctic seven.

05:59.030 --> 06:05.670
OK, so we'll just be selecting an Arctic seven related boot and then we'll be finding that we have

06:05.670 --> 06:07.020
chosen compatibility.

06:07.290 --> 06:14.010
So if you try to create a project with a different family, you simply won't be able to see an OK and

06:14.040 --> 06:16.540
you can in fact, choose a lifecycle also.

06:16.560 --> 06:22.500
So whether it is reproduction production discontinued and so on and so forth.

06:22.530 --> 06:27.550
OK, so get of a whole lot of option when you walk around with a compatibility.

06:27.630 --> 06:32.930
OK, then you'll be finding that we have our vision to be 90.

06:33.150 --> 06:41.640
OK, and then since you have not added so here also we get the same simulation right then customization

06:41.640 --> 06:42.130
parameter.

06:42.150 --> 06:48.280
We have not added so we can make our IP in such a way that we can migrate to an higher version.

06:48.300 --> 06:57.120
So we in the future will understand that that and it can be migrated to an eight or any other size as

06:57.120 --> 06:58.150
per user requirements.

06:58.150 --> 07:05.670
So there will be finding we get the customization parameter highlighted here and then Fuson interfaces

07:05.670 --> 07:07.590
will be finally we have to input ports.

07:07.850 --> 07:15.540
OK, and in the mouse, besides the seven analyst, besides the civility, we have a Y as a loose.

07:17.600 --> 07:22.310
Direction and sizes you need addressing and memory will not be there.

07:22.370 --> 07:30.290
This will be available when we walk around with an exciting in when we are still in the face that we

07:30.290 --> 07:32.960
walk around with an address and a memory.

07:33.370 --> 07:36.190
OK, here Will you won't be finding a new option.

07:36.230 --> 07:39.840
Then you go to Adua, you'll be finding that this is our.

07:39.900 --> 07:40.670
I will look.

07:41.120 --> 07:48.350
So we have to be good then put on a say then we have one on the right side and each have their respective

07:48.350 --> 07:48.660
sides.

07:49.280 --> 07:54.020
OK, so when you add a customization parameter here, you will be finding this speech.

07:54.200 --> 07:56.550
You get an option to configure the sites.

07:56.600 --> 08:01.170
OK, now we just go ahead and package IP and then we'll package.

08:01.220 --> 08:01.550
Right.

08:01.850 --> 08:07.070
OK, so once you see the finished packaging, he is successful.

08:07.320 --> 08:13.760
OK, what you can do is know what we'll do is we'll try to understand how.

08:15.160 --> 08:17.200
The refresh are positive.

08:17.260 --> 08:18.730
OK, so by default, we.

08:20.260 --> 08:27.880
We'll be having that if you work on any project directly or what we'll do is we'll consider an example

08:27.910 --> 08:34.870
where we are working in the same project that we have our blog design in the same territory that we

08:34.870 --> 08:35.470
have created.

08:35.830 --> 08:37.590
So let me just proceed with that example.

08:37.600 --> 08:44.140
So we'll click on three properties they will hit, OK, and then we'll just go ahead, click plus button

08:44.140 --> 08:48.220
and we'll try to search for and I and find it.

08:48.230 --> 08:52.690
We have our IP been added with no reason.

08:52.690 --> 08:56.350
If you try to find out why the IP is automatically.

08:57.880 --> 09:04.390
The threshed in a repository, so you just can go to a setting, OK, and then if you just go to an

09:04.390 --> 09:05.470
IP, OK?

09:06.450 --> 09:13.170
So you have a particular option, so there would be finding by default or project location is will be

09:13.230 --> 09:19.130
finding that IP repository is invoking and use IP or by default from our project.

09:19.420 --> 09:25.440
And for that reason, we do not need to specifically mention the location where we have an IP if we

09:25.440 --> 09:30.240
create a block design in the same directive that we have created an IP.

09:30.450 --> 09:39.690
So this has been identified by the repository and that is the reason we automatically able to see our

09:39.690 --> 09:41.370
IP IP repository.

09:41.430 --> 09:43.290
OK, now you see the differences.

09:43.590 --> 09:48.180
OK, so this also suggests is that if we have a block to say.

09:50.290 --> 09:57.430
Or if we have a repository located in different location, then in that case we wouldn't be able to

09:57.430 --> 09:58.830
refresh our deposit.

09:59.080 --> 10:04.960
OK, so we need to manually refresh the repository so that we understand in the next lecture we'll know.

10:05.020 --> 10:08.800
What we'll do is we'll just try to test whether it is working fine.

10:09.520 --> 10:14.860
We'll just go ahead to land and get over here, OK?

10:14.950 --> 10:17.990
And then we'll just create a booth for this will, right.

10:18.040 --> 10:19.870
Click and we'll make it extended.

10:19.880 --> 10:26.620
So this will act as our input similarly will be on the beam to those who will make it external and for

10:26.620 --> 10:29.410
wireless will make a decision that will like to change the name.

10:29.770 --> 10:31.120
So this should be a.

10:32.370 --> 10:41.790
OK, then this we want to be finally this, we want to have a one sided design, designers ready will

10:41.790 --> 10:42.960
just recently clear.

10:43.020 --> 10:46.620
So this will clean up our diagram and then we'll validate our design.

10:46.640 --> 10:49.720
So once validation is successful, we go to a small step.

10:50.040 --> 10:54.060
So here we have our blog that I click and we create Tannishtha and.

10:55.640 --> 11:01.600
Again, will allow vibrato to automatically create a rapport for us, will not be specifying any specific

11:01.600 --> 11:01.990
second.

11:04.150 --> 11:06.340
Now, once we have our code ready.

11:06.970 --> 11:13.600
OK, are we ready then whatever we have done from the beginning, you can follow the same tradition,

11:13.990 --> 11:18.820
same procedure, and can work around with the visual cues that we have.

11:18.820 --> 11:19.060
Right.

11:19.090 --> 11:25.530
So once we have a visual, whatever we've been doing from the beginning, we can do on this knows right

11:25.720 --> 11:31.030
now what we do is we'll just try to perform a simulation just to verify whether the IP is working fine

11:31.030 --> 11:31.360
or not.

11:31.370 --> 11:33.310
So we'll go to a simulation.

11:33.310 --> 11:41.110
Susanville first observe whether the rapper is a rapper, is are will go to run a simulation and will

11:41.110 --> 11:42.910
perform a simulation.

11:43.640 --> 11:46.730
And then what we'll do is we do a full question.

11:46.810 --> 11:51.820
So we'll just use false concern and we'll specify the number in the binary format.

11:51.820 --> 12:00.070
So one zero one zero one one one one night and four, we also will use a false constitution, specify

12:00.070 --> 12:05.230
the number in the binary format, one one zero zero one one one.

12:05.560 --> 12:08.340
OK, and then we'll try to perform a simulation.

12:08.350 --> 12:15.880
So if you just try to bring the formula out, OK, and if you just try to win a bet and use the ratings

12:16.420 --> 12:24.790
to the binary, OK, so we'll just select all the reform and we'll change the ratings to a binary.

12:26.180 --> 12:32.530
OK, they'll be finding that this for one and this one will result in two fold.

12:33.140 --> 12:34.100
This makes sense.

12:34.520 --> 12:38.300
And then we have one zero one zero one one zero zero.

12:38.300 --> 12:41.170
So we should only get one and then all zeros.

12:41.690 --> 12:45.120
So the gate, the gate that we have to look is working.

12:45.540 --> 12:51.190
OK, I know you can try out following an entire process and then working around with them.

12:51.190 --> 12:59.000
And in fact, if we just perform an actual analysis and observe the schematic, still able to see and

12:59.720 --> 13:03.130
take input, and that will give us more to your understanding.

13:03.140 --> 13:08.190
So we just explore how we get the schematic in an actual analysis.

13:08.300 --> 13:14.990
You also have a good picture about the underlying circuit which is being generated for the stuff that

13:14.990 --> 13:16.030
we have created.

13:16.550 --> 13:22.760
So we have an above and an notebook and then here we have a design is explored.

13:22.840 --> 13:29.020
So finally you'll be finding that is simple, that we have implemented an angle and there are eight

13:29.060 --> 13:29.450
such.

13:29.810 --> 13:30.020
Right.

13:30.290 --> 13:32.010
So this is working as expected.

13:32.540 --> 13:40.370
Right now, what we'll do is we'll understand how we refresher oppositely when we have our IP in a different

13:40.370 --> 13:42.560
location and the design designing a different.
