The next IP that we're going to use is an exact time based watchdog name, right?
So we just click on this plus button, right, and look for the timer.
You have to eyepiece right.
So the exciting mode, which we previously discussed now, will be discussing the exciting based version
of that right now, if you just go through the leadership of the exciting based virtual timer.
And since we are focusing primarily on the full mode of our timer, right, we want to upgrade our time
based watchdog timer in a WTT mode, Rachel.
The double time interval is configured by a parameter to tools to offer WTT clock correct.
So this this will be the delay that you'll be getting.
So once you set up the.
OK, so whatever clock you feed to the WTT, OK, that will be multiply it to rise to the fit of a WTT,
and that is the delay that you get out of the time based watchdog, right?
The weight of the parameter is an integer ranging from eight to 13 right to decide the valid range,
which are allowed to utilizing an IP.
That interval is set at co-generation time and cannot be modified dynamically through a controlled register,
right?
So this is something which is important point to note that as we configured our IP there with this fixed
and later on when we developed our application, we are not allowed to change the OK.
And you'll be finding that when we explore the driver of our time based washed off timer, you won't
be finding any API that allows us to change the control we take.
So we need to.
Sector with depending on the dealer that we are targeting next.
So let's assume we feed a clock of 100 meters, 600 megawatts is equal to 10 nanosecond and we set up
the WTT to be 30.
Right.
So the deal that we'll be getting is around 11 second rate.
So how we calculate delays due to the weight of WTT, which is 30 that we set up and the clock that
we are feeding is having a block period of 10 nanosecond breaks.
So how do you calculate the property?
You simply take an inverse of the clock frequency, right?
So we will be configuring f clock to be operating at 100 megawatt.
So if you take an inverse of it, it will be giving us 10 nanoseconds, right?
Let us see how we configure this and whether we are able to get the delay of 11 Typekit, right?
So we go to every model right now to interface this IP.
Since this have us leave Levitsky interface, look at that and say we need to enable the zero put on
and sync processes.
So and that will allow us to interface zinc processing system to a time based director will just reconfigure
zinc processing system.
So three things that we need to add OK, so we need to add risk.
OK, so we go to a general that we enable a reset.
We also enable Master ex-KGB zero interface and the clock that we are targeting for the yield fabric
is 100 meters, right?
So this is what we're going to have.
So you need to consider this to be handed me that.
So now we get the period of 10 second, so click OK.
Once you do this, we will automatically show us collection automation right now.
We are allowed to collect this and make zero to a slew of interviews of time with the right to perform
collection automation.
So once you perform an action automation now, you could clearly analyze we have a signal processing
system utilizing any exciting technique to be able to connect zinc processing system to a time base
Vostok time.
So we won't be utilizing any of this output, but we will keep them floating, right?
So we'll just perform our validation of the site and was validation is successful.
OK, we will just be generating an.
It's likely going to be blog design.
And create an elaborate.
So I design just consist of two pools, which are DDR and fixed air, and we already know that these
are already matched to their respective hardware.
So we kinetic need proceed for generation off of it, right?