WEBVTT

00:00.060 --> 00:06.570
So let us now start to understand how we can fight and Viorel inside our design so will understand the

00:06.570 --> 00:12.720
simplest procedure of fighting a viable design so that you won't be confusing yourself.

00:12.750 --> 00:20.010
So this project next will be sticking to the project and default project.

00:20.010 --> 00:27.480
Location will choose an art project and the file will be naming it as LATISM top.

00:28.530 --> 00:36.570
OK, and then we'll just go and select so the ball that we are planning to use is Nexxus Hoodia, so

00:36.570 --> 00:38.760
we'll just select tag.

00:39.690 --> 00:41.070
And then we'll finish.

00:41.460 --> 00:45.100
So this is the normal procedure that we've been following from the beginning.

00:45.480 --> 00:49.260
Now, the school that we are planning to implement is to trigger.

00:50.170 --> 00:50.800
And.

00:52.880 --> 00:59.510
Drinking, so, yes, we have implemented a blinking circuit, so that will be used to blink an eye

00:59.960 --> 01:07.400
at an interval of one second and to Stockton, stop an operational type thinking circuit we required

01:07.400 --> 01:07.700
once.

01:08.240 --> 01:11.600
So this is what our typical system specification is.

01:11.630 --> 01:15.440
So we have one switch which will be used to start and stop blinking circuit.

01:15.830 --> 01:21.290
And once you start the blinking circuit or the reality that is connected to our circuit will be blinking

01:21.290 --> 01:23.520
at a rate of one second.

01:23.570 --> 01:26.070
OK, so you'll be guessing that we require three.

01:26.360 --> 01:30.030
First one is a clock, which is used to generate the specific data.

01:30.050 --> 01:32.150
That is one second delay then.

01:33.370 --> 01:37.830
We required a reset or instead of reset, we'll just knew it had to start.

01:38.470 --> 01:43.150
So as user press the start, you're applying new high signals to start.

01:43.390 --> 01:45.400
The blinking circuit will start operating.

01:45.430 --> 01:46.870
And finally, we required in.

01:47.840 --> 01:56.300
And Lady Outsing there will be connected to this should be an outbreak and each will have a single.

01:56.930 --> 01:59.780
So we'll just proceed and then we have.

02:04.120 --> 02:12.070
Now, since we want to do so, we will require to use a new standard library, we'll just add a new

02:12.280 --> 02:21.510
standard library here and will specify unsign library, gold standard and school logic.

02:21.760 --> 02:23.920
The school unsane.

02:26.090 --> 02:28.360
OK, now what we'll do is.

02:29.350 --> 02:36.290
Since we want to reduce the previous year to four blinking circuit, we exactly need to know what is

02:36.290 --> 02:37.060
the previous to it.

02:37.360 --> 02:43.140
If the realities in on street, we need to complement it and we need to make it zero.

02:43.360 --> 02:50.950
OK, so here basically four and out, we need to know and be with and then only we can decide what to

02:50.950 --> 02:51.480
do next.

02:51.680 --> 02:58.840
OK, we already know that the foods which are declared as an out cannot be use and.

03:00.100 --> 03:04.450
Cannot be used inside an expression, so we just add a temp.

03:05.050 --> 03:08.830
OK, that will be used to hold the result of our lady.

03:09.100 --> 03:16.750
OK, and that utilizing the signal allow us to actually use each state to generate the next one to signal

03:16.750 --> 03:18.190
them standard and the logic.

03:18.430 --> 03:21.190
And for a counter variable, we will use an integer.

03:21.490 --> 03:26.740
So we'll just neumar variable to count integer and range.

03:28.850 --> 03:29.960
Zero to.

03:30.950 --> 03:37.630
Then into days to six, that is what can be required to generate the approximately Adelia of one ticket.

03:37.650 --> 03:42.430
So 10 then one, two, three, then again, one, two, three.

03:42.440 --> 03:47.300
So this extends to six straight down into the distributors.

03:47.300 --> 03:50.660
And then we'll just add one to one more count.

03:52.380 --> 03:55.830
That's compared to the required time, you'll just initialize it to a Z.

03:56.250 --> 03:58.310
OK, so this is a counter variable.

03:58.440 --> 04:03.660
And then we have also declared one of the variable which will be holding the status of finally.

04:04.350 --> 04:06.010
Now, we'll just prosecutor logic.

04:06.030 --> 04:08.450
Now, this is a sequence of planning.

04:08.460 --> 04:10.200
So we'll start with the process.

04:11.720 --> 04:16.070
Will make our process in situ two o'clock, right then big.

04:17.030 --> 04:25.460
So if start is zero, right, to start to zero, then in that case what we'll be doing is the temp,

04:25.460 --> 04:29.570
which is holding the value of our ability, should be right.

04:30.710 --> 04:39.930
And as if L's indicate that you want to start the system, so here will be checking where the value

04:39.930 --> 04:44.370
is less than 10 one, two, three, one, two, three.

04:44.370 --> 04:44.610
Right.

04:44.630 --> 04:50.820
So then including the specifics, then, if that is the case, will simply be incrementing count by

04:50.820 --> 04:52.610
one for each block saken.

04:53.770 --> 04:59.650
OK, as soon as it reaches to that value or becomes greater than that value, then in that case will

04:59.650 --> 05:04.060
be making on ground zero as VILLUS will be.

05:06.380 --> 05:13.870
Complementing whatever the value that we have at this makes sense and will just end its treatment,

05:14.180 --> 05:20.360
similarly here also will identify something that we have not idalis syncing the clock.

05:20.600 --> 05:24.650
So that is the first thing that will be doing and then will be performing our logic.

05:24.670 --> 05:27.350
So if they're using each.

05:28.280 --> 05:29.730
Of luck.

05:30.110 --> 05:34.860
OK, then and then this will be our logic that will be implemented.

05:35.150 --> 05:40.790
Finally, the identification process and since the time have a global scope.

05:40.800 --> 05:42.490
So finally out.

05:43.130 --> 05:47.180
OK, so we have an idea out as our report will be equal.

05:48.440 --> 05:49.210
This makes it.

05:51.320 --> 05:54.230
So this completes what we are doing is we are sensing.

05:55.190 --> 06:02.380
Then it started the output of zero as we are checking with account value reaches to the desired outcomes

06:02.390 --> 06:04.090
that we're able to generate.

06:04.730 --> 06:10.760
So if it reaches to that value, we will be simply complementing our previous value of time.

06:10.820 --> 06:12.770
OK, then counted again.

06:13.280 --> 06:14.030
So this will.

06:14.980 --> 06:18.010
Again, the remaining in that state for this.

06:18.370 --> 06:20.410
And then finally will be complemented.

06:20.440 --> 06:28.570
So this is purely random, but this will allow us to actually see lady blinking right now, will proceed.

06:29.170 --> 06:36.250
And the simplest way to either Viorel, this will be finding if we try to add an IP, OK, and try to

06:36.290 --> 06:41.800
perform a structure more or less, it becomes very, very difficult because, OK, so if you just go

06:41.800 --> 06:48.920
to an aioli and if you just try for and we go, OK, let's see what is a.

06:50.140 --> 06:56.350
So school that to be required, one input from where we'll be connecting it out and we required one

06:56.350 --> 07:01.300
output, which will be connecting to a start, and that can be triggered by a user.

07:01.360 --> 07:08.260
OK, so we require just a single input and single output and they should have a dimension of single

07:08.260 --> 07:08.710
project.

07:08.750 --> 07:11.000
So this is also single this as well as a single.

07:11.350 --> 07:14.160
So we do not need to configure much about envy.

07:14.410 --> 07:22.930
And now if I just try to generate a VIP, so the major part for us is an insane creation code that we

07:22.930 --> 07:24.910
get within VIP.

07:24.940 --> 07:30.170
So if that is in Vergiat, then performing a mapping becomes very, very easy.

07:30.370 --> 07:38.290
But if we get that code in a very low, then we'll be finding performing the code mapping or a structural

07:38.290 --> 07:42.150
modeling state between visual and very difficult.

07:42.160 --> 07:43.840
If we compare it with another.

07:44.200 --> 07:51.340
That is, if you have a source code in a very low and IP is having a pool in a Usdin, then performing

07:51.340 --> 07:56.140
the connection between them is easy because very loosely type language.

07:56.440 --> 08:04.900
But if you considered the small school in and then IP coding and very low, the mapping is very, very

08:04.900 --> 08:05.380
difficult.

08:05.410 --> 08:12.060
We will be finding that our whole lot of errors that we'll be getting and usually we avoid them.

08:12.340 --> 08:17.740
OK, in that scenario we follow other methods and that will be utilized.

08:18.010 --> 08:22.580
So I'll just show you what is the code that we get when we create an IP.

08:22.600 --> 08:28.600
So if you just click on Desierto, OK, we will get an instant template over here and that can be used

08:28.600 --> 08:31.920
to declare the component inside our.

08:34.750 --> 08:41.110
So they'll be fighting now you have this school and this is actually Montu, so this is written in very

08:41.110 --> 08:49.210
long and you'll be finding that we now need to use this school inside of issue and it becomes very,

08:49.210 --> 08:49.930
very difficult.

08:49.930 --> 08:56.860
So whenever you have a scenario where you have a virtual school or you are writing a visual code and

08:56.860 --> 08:58.960
you have an IEP, which is.

08:59.970 --> 09:05.570
Provided with the deluxe school, then you do not try to perform the.

09:06.900 --> 09:12.720
Structural that is using this as a component and performing both mapping will be finding that a whole

09:12.720 --> 09:16.950
lot of area that you'll be getting and in fact, it becomes very, very complicated.

09:16.980 --> 09:21.330
OK, so in that is what you do is so I just keep this IP as it is.

09:21.330 --> 09:23.100
I'll just go to a block the same.

09:24.690 --> 09:31.650
In such a scenario, it is recommended that you follow, we are to integrate, OK, so that we automatically

09:31.650 --> 09:36.510
handle the type conversion that is required in between and we do not need to worry much.

09:37.140 --> 09:43.200
So what we'll do is, no, we'll just go and topcoat inside.

09:44.460 --> 09:47.560
So we have a lock, stock and trade.

09:47.680 --> 09:54.620
So the reports are there and we'll also be adding a value to what we'll do is we'll just go ahead,

09:54.630 --> 09:57.690
we'll click on our IP and then we'll search for.

10:00.120 --> 10:03.210
OK, so now we have video and we also have.

10:07.460 --> 10:12.740
So if you just see or if you want to configure, you can just double click on Enviropig.

10:15.010 --> 10:20.950
The finding that we required a single and we also required a single occupant to default setting will

10:20.950 --> 10:24.330
work fine for us and the work that we required is also a single single.

10:24.490 --> 10:27.400
So this configuration setting will work fine for us.

10:27.440 --> 10:31.750
OK, so when you consider of this is the pool that will be generating.

10:32.260 --> 10:32.620
Right.

10:32.650 --> 10:40.540
So this we want to connect to start date because when we send in high from this, we want that our system

10:40.540 --> 10:41.370
should start working.

10:41.380 --> 10:46.320
And then at that specific instance, we want to analyze what is the value that we are getting at.

10:46.780 --> 10:51.220
So this will be connecting to the proven Benoff.

10:51.360 --> 10:53.790
We can we will be making clock.

10:54.190 --> 10:54.430
Right.

10:54.670 --> 10:59.890
So it'll be finding, if you remember that when you are working with Annihilate, you need to perform

10:59.890 --> 11:00.970
about mapping support.

11:00.970 --> 11:01.960
Mapping is mandatory.

11:02.180 --> 11:04.750
OK, that is, you need to connect.

11:04.750 --> 11:07.480
You are all looking to something on an FPGA.

11:07.490 --> 11:12.180
But if you consider the will now start and out is already connected.

11:12.200 --> 11:12.520
We are.

11:12.850 --> 11:14.560
We just need to fill the portal.

11:15.160 --> 11:17.230
We will decide when put.

11:18.120 --> 11:20.030
So will create a pope.

11:20.860 --> 11:24.020
OK, and we'll just name this as a clock, OK?

11:24.330 --> 11:28.080
In fact, we want to use this as a clock.

11:28.080 --> 11:32.250
So what we'll do is just go in here.

11:34.620 --> 11:36.590
So creative input.

11:36.750 --> 11:40.610
OK, we'll just name this as a clock and it will be a clock signal for.

11:42.450 --> 11:43.340
I will hit.

11:44.710 --> 11:47.770
Now, what we'll do is we'll just take this to.

11:49.060 --> 11:54.600
Both the clock and so will the selected clock will connected to.

11:59.510 --> 12:05.540
So we'll just have to Nimetz clock and then we'll connect this thing to put the clock in, that we have

12:06.230 --> 12:06.770
to wipe the.

12:10.130 --> 12:15.770
So this completes all the connection with this region and validate our desire to want validation is

12:15.770 --> 12:17.410
successful, we can do that.

12:17.780 --> 12:20.270
So we'll just go in and create initiative to.

12:21.900 --> 12:25.160
No one is ready, we'll just proceed to synthesis.

12:25.320 --> 12:27.240
OK, we'll perform a synthesis.

12:30.440 --> 12:32.580
Now, we'll just open our sentences, say.

12:35.270 --> 12:38.710
OK, and you'll be finding that, no, we our.

12:40.530 --> 12:41.610
As well, as I did say.

12:42.700 --> 12:47.380
So if you just go to Alioto and select an eye opening look, it'll be fine.

12:47.500 --> 12:51.120
We only have one scaleup, which is right.

12:51.340 --> 12:57.760
So here we'll just select tell we see more solitary and will select the correct package, that is.

12:59.320 --> 13:02.470
Etomidate, so that is the on plot blog that we have.

13:03.380 --> 13:04.530
And we'll just see.

13:05.150 --> 13:05.430
Right.

13:05.450 --> 13:07.450
So this will allow us to see even existed.

13:07.520 --> 13:12.770
So if we compare this with an aioli, you do not need to specify the.

13:13.890 --> 13:20.520
Package been for all the support that you have connected to a vehicle as opposed to an idea where you

13:20.520 --> 13:24.720
need to feed all the food somewhere on the beach.

13:25.320 --> 13:27.220
So this completes our design.

13:27.300 --> 13:30.960
Now, what we'll do is we'll just go ahead and generate a bidstrup.
