So let us try to understand any tax rates of the driver files that you require to work with a washed
up time or is the right.
So this is a driver file which consist of all the apps that help us to work with then washed off times.
Then we have an experimental stage which help us to get any hardware related information or an identity
related.
So you have an exciting PC for then?
Exceptionally literally, we have two exceptions, right?
First, we stack the declaration of two structure, right?
So this will be for initializing our took time off.
So we declared the config structure and instead structure right?
And then we proceed for performing initialization of and washed off names, right?
So we here we have the function that performs an initialization often washed off name.
So we call lookup config where we need to pass the device A.D. So as soon as you pass this document,
this Genndy, the config structure for us, which we are storing in it, the ability to configure and
then that config structure we are utilizing, along with the base address and the instance structure
inside to see what initialize to initialize our watchdog timer, right?
And this value, which is written by C of G initialize we are sorting in that status variable.
So here, if the initialization is successful, it will simply retain existing success and it will retain
existing fleet, right?
So if it's due to the system success, we are just mentioning the end user that WD initialization is
successful and we are sending WD D and Nick Field on a console right then in the case of a complex favorite.
We prefer to perform a service and that is what we are doing away here.
So we call the self-test API where we just need to apply an instant structure, right?
So which serve as an argument for this function.
And then there's also written whether sentences are successful or not.
Right?
We again need to check whether status is equal.
Strict is just a sign.
If that is the case, we could just mention that self-test is successful, and if studios is not equal
to existing success, we could just mention self-test.
Right.
So these are all the things that you need to do that to correctly initialize WD, right?
So once this is done, the next step is to correctly initialize IPC, right?
So which itself so is one of the things that it that since we are planning to utilize and initialize
function.
We just required an instance structure, right?
So document foreign initializes and instance structure and the device idea, right?
So once you pass this to arguments, this will perform an initialization of an intra controller and
then it will return the status of an initialization, which we are storing in that state as variable.
So if status is racist or sexist, we could just mention that I indicia needed successful LS.
We could mention I in this nick.
Right?
Then we start with the configuration, right?
The first step is we will be initializing exception handler and then we will be specifying what is the
type of an exception that we have?
Finally, we need to enable great.
So all the space that you require to work with an exception is available in the exception directory.
So we call the exception in it.
This will initialize an exception handler.
Then we need to specify the type of an exception so died for an exception.
Is this one which is the first document far out its Australia?
Then we specify which will be the handler for this exception.
So this will be the master handler that we have init I in DC rate driver.
So that is what we have added over here.
And the reader that we want has a callback is the instance structure that I anticipate and then we enable.
So this remain similar to what?
We've been using the and UPI as well this time.
Right.
The next step is to specify the unique IED that we get for the injury and then what should be the function
that will be executed when we have an interest rate.
So do specify that we call a connect function here.
The first argument is an instance structure.
Then we get a unique IED for our watchdog timer.
This could be found out from an experimental stage that we specified in Handler for it, right?
So here we declared one function, which is INTC handler, and that will serve as an handler when the
interest from WTT occur, right?
And the callback to the reader that we want to collect evidence is an instance structurally to offer
WTT right?
So this elderly discourse, whenever you want some data, in most of the cases, it will be the instance
actually top up everything, right?
Finally, we need to know clues switcher rate, so that could be done by calling an enabled switch rate.
So here we again need to add an instance of and a unique idea that if we get four WTT now, if you explore
the WTT driver, right, so I'll just be going to our WTT driver five.
And here you could clearly notice that we do not have something as global enabled or simple enable.
And whenever we are in a situation where we do not find global enable or our peripheral specific animal,
we could skip the step to where we are enabling us to write this bill today.
This is the last thing that we do is to start an operation or firing controller in a real right.
This is what we specified.
We're here.
So let's try to understand the code for in England, all right, so what we're going to do is we will
be first acknowledging our interest rate.
So once we acknowledge and interrupt, the next step is to disable any further interest from this suicide
rate.
So whatever I do that we specified do here.
So microplates will be serving or receiving an interest from that specific idea, right?
Then we are double checking whether washed up name is really expired or not, similar to what we did
with any set time world, right?
And the only one thing that we are going to do in this specific function is sending up an introductory
string one again.
So this is what we need to do and we have that interest rate.
So remember, we have not had a restart watchdog timer.
So what would happen is are most of them accountable, right?
And we will be able to get the single interrupt occurred on the.
Cancelled, right?
If we want to have a repeat event from this WTT, you need to restart your watchdog timer and you also
need to enable an interest rate.
So in this case, we only want to have the single interest from a washed up time.
So what we are doing is we have first acknowledging an interest, then we are disabling any further
interest from a watchdog timer.
We are checking whether washed up timer is really expired or not and that we are performing the required
processing as per user specific requirements.
So here we just want to say and interrupt good message on purpose, and that is what we are doing.
So we are not restarting our watchdog timer.
So this will make sure that I have launched a counter right?
And we do not generate any further requests of any interest from I was docked time.
Right.
So let me just go ahead and try to fill the entire application project, right?
So once Bill is successful, we are going to go ahead and we will be launching our application or going
to select the bogus launch on hard right.
So here we already connected with Terminal to Column six to operate at nine six zero zero port.
So we'll just go ahead and click on the resume button, right?
So we could clearly notice that WTT and newly successful sectors is just successful.
I and it is also successful and after an interval of 10 second, will be getting a single inch of perchlorate.
And after that, we won't be getting anything because we configure our application code in such a way
that we will only receive a single interest request.
Now let us try to understand how we modified this code so that we will to get the multiple interpret
with only thing that we can do here is we will be as we complete serving our answer that is sending
an interlock around the console.
We will just be restarting our washed off camera, so this will again initialize our counter back to
the value that will be giving us 10 seconds.
OK, and we again need to enable the interrupt from the source, right?
And that could be done by calling and enable.
Function, OK, or here, and then we will be adding the instance structure as well as a height.
Right.
So this will be your procedure when you want to be done multiple entry from a logical time of day rights
that I didn't just build up our project.
Let's be less successful.
We could just select the configuration and click on relaunch, right?
So what this will do is this will again program FPGA and then we believe it to run the new application
or to an FPGA, right?
So again, we have our pointer over here again in black and white is terminal is already connected to
the specific support we just need to click on resume.
Right.
So now here we need to analyze whether we are receiving the multiple request from either washed up that
worked in the previous case, we will be able to receive a single request.
Now as we update our application code.
OK, so here we already have our first request.
Now let us wait for 10 second and see whether we get the second request.
So here you will clearly analyze that.
Now we are getting the second request.
And if you further wait for 10 more second, you could still see that we are getting an interpreter,
right?
So this way you could get the multiple incorrect request from the WTO.
Guess only thing that you need to configure is you need to restart the watchdog timer and you need to
again enable a reception off an intro from watchdog time.