WEBVTT

00:00.090 --> 00:06.540
Now, let us try to understand how we invoke and all synchronicity first modification that you want

00:06.540 --> 00:08.400
to do is long with the clock.

00:08.410 --> 00:12.660
We'll also be adding We sit in this institute, illustrate this is the first thing that we do.

00:13.050 --> 00:17.400
Now, before locking event, we will be defining the behavior, right?

00:17.400 --> 00:18.060
So in.

00:19.140 --> 00:27.960
Respect is equal to one, right in that case in that this deal will be equal to zero.

00:29.110 --> 00:29.340
Right.

00:30.250 --> 00:38.320
Unless and if right and if if we have a blocking event that is healthy, right?

00:38.620 --> 00:45.320
Writing is off lock, then we will just be following the value of.

00:45.910 --> 00:48.070
So this is how you implement.

00:49.080 --> 00:56.520
The US synchronicity rate, so what we did is we have a reset and clock in the sense of duty list,

00:56.850 --> 01:01.890
every state is high, then out will be equal to zero else.

01:01.920 --> 01:07.200
If we have a rising edge of a clock, then die out will be simply falling, right?

01:07.230 --> 01:15.150
So if we just see the code and you try to reload the schematic here, you will be noticing that the

01:15.990 --> 01:20.160
component that we invoke for this type of food is the.

01:21.190 --> 01:27.940
Ideals regard us great, so I think basically indicate that the type of research that we are utilizing

01:27.940 --> 01:29.680
is asynchronous, right?

01:30.100 --> 01:35.530
So this is how you implement the difference with asynchronous research or no synchronization state.

01:35.770 --> 01:38.470
Now here you could further modify this correct.

01:38.500 --> 01:40.270
This is difficult to digest, right?

01:40.330 --> 01:48.270
What you would do is we could just add else OK and in site else, we could just add a right right,

01:48.380 --> 01:52.990
raising a whole lot right there.

01:53.440 --> 01:53.780
OK.

01:54.100 --> 01:59.020
Or we could just take this out will be close to the right time.

01:59.020 --> 02:02.140
Since we have Saturday it, we'll just be ending the lot.

02:02.710 --> 02:09.750
And the first one, right where we are sensing their sensing, the reset that also we need to integrate.

02:09.760 --> 02:19.450
So this method will also result in do the same synchronous reset with the discord if you just reload

02:19.450 --> 02:20.290
the schematic.

02:20.330 --> 02:27.790
Now, you could argue, observe the component that is invoked again and ideal wreck us.

02:27.970 --> 02:28.300
Right.

02:28.510 --> 02:28.870
So.

02:29.940 --> 02:35.680
You could use this method or you will use just LC, right, but the method will just work fine.