The primary use for a watchdog timer, besides a meeting in event at a regular interval is to reset
our roster or to bring back our roster out of a deadlock, right?
So let's assume we already know that we have a max time that could be consumed by our application rate.
So we specified that amount in stock.
Daimler and as a counter insider, was Dr. Murray.
Just to zero basically indicate that we consume more time as expected from an application, right?
So what we're going to do is if our application runs perfectly well, then in that case, at the end
of our application, we'll just be restarting a watch dog name or in that case, was docked time or
won't be generating a reset signal.
But later do we consume the time that we specify the watchdog Daimler for running an application?
In that case, we basically mean that our application is stuck somewhere, right?
So to bring it out of a deadlock, what we do is we reset our system, right?
This is what we're going to do this now since we already connected a watch dog timer.
We will be bringing back our pointer to the first location, right?
This is what we're going to implement over here, right?
So only modification that we're going to do it here, we will be acknowledging and in shock will be
disabling.
OK.
And then we go ahead.
We will be.
Reminders, wristwatch, watchdog, timer also.
OK, we'll just be adding this school over here right now, what this does is it automatically bring
our pointer back to the first address, right?
So this will be bringing out our Rosseter out of date.
Right.
That is what we're going to do.
They'll be displaying the Doppler on the console and the same time you need to observe their pointer.
So the pointer is highlighted by a green color when we perform debugging.
So let me just go ahead and try to try to build an application that is the first thing that we do as
we update our application, then we'll select a configuration.
So this is a configuration that we are running right click and then we have a relaunch button, right?
So will be again programming RPG and we'll be running this application on to an FPGA, right?
So we go to and why this terminology right now here you could really see our pointer is shown with a
green color, right?
So our process, Ithaca is currently at this point, and as we resume our application, it we start
executing from this instance, right?
So let me just say that I took with this, you know, our application is so clear after an interval
of 10 second, OK.
So in this case, we are not restarting our washed up time.
All right.
So as soon as we rule out, you will clearly see we bring our pointer back to any flat, right?
So this could be when we are bringing our application back from the deadlock to the first location and
again, start executing right so that we that we have this, we could use the word timeout, reset our
microbes so that the application that is 249 flash memory of an effigy could be loaded and we again
start application on any right.