Now, since we do not need to do much of a confrontation, the call will be very simple.
The first thing that we do is to restrain the driver that could be utilized to correctly initialize
our watchdog timer.
So if you go to the board support package, so the driver that is highlighted is WTT DB, right?
So we just need to Ireland, says A.
So we go to an Helloworld or C, and the first thing that we do is to include the driver.
It will be x wd db, right.
This will consist of all the which could be used to correctly initialize our watchdog firmware as well
as utilize it right then parameter lautech, which would be used to find out and hard the hard way related
information.
Right then we the Clayton structure first one is the conflict structure and the next one is an instance
structure, right?
The first thing that we do while performing and initialization is called lookup config function, where
we will be adding the device, right?
So this device ID could be found out from X parameter and this function will return the config structure.
So once you have a conflict structure, you call CFD initialize, which required an instance structure,
the structure and a separate state.
So once you add this three argument to see if you initialize function that returns the status of initialization,
right safe status is explicitly sexists, then if that case, we could see that WD and it is successful.
Else we could see WTT.
And then in a case of a complex, very perilous discourse, we will also be performing self-destruct.
So we have EPA to perform a set of this, which required just a instance structure as an argument.
So once you add that argument, this will return the status of our self again.
We will be checking whether self-test is successful or not.
This is equal to existing success.
Then in that case, we could see that WD Self-Test is successful and we could just mention WD deserve
this.
So once boot, the thing and that is initialization is also successful and self test is also successful.
We are ready to work it out with an EPA which provided for WD, right when we go to our main goal,
the first thing that we do is after any black ops.
So any platform you get when you use an halloway resin template based, this consist of all the initialization
for and you what?
So without configuration, we could just proceed writing or utilizing third printing, right?
So need platform, cleaner platform and routine zero will be there when you invoke and halloway template.
Great, we call WD in.
This consist of all the initialization function for our washed off timer.
The only thing that we need to do is just to stop a wash up.
This will always be our strategy when we walk around with any of a time, right?
So we stop our timer and then we are starting our time right.
Then we have a function similar to what we have in any timer to check whether IWD gets fired or not
right now.
We already knew that we could not directly dynamically configure the fit of our count, right?
So we will be waiting for a timer to expire.
And then as our time expired.
We will be coming out of this look.
And we'll just be mentioning the politics by.
Right?
So if you just explode the functionality of this function, this returns to a five lost time has expired.
So this will happen only when the least to the specified count as specified while configuring a ripe
break.
So as soon as we elapse a 10 seconds, we will be getting through.
And for the first and second, when are counted as children will be always getting a false rate of sense,
we need to wait for that instance.
We have added the note operator, so this function will continuously retain the false for first and
second OK, since our WTT won't be expiring for that duration.
And as soon as it expired, it returns, do not approve, will be false and will be coming out of.
Similar to what is happening with any excitement odds, right?
And once that is done, we will just be sending WTT expired on.
So this is an entire application code, which is very, very simple.
That's compared to any time.
So we do not need to configure the safe option, the different options that are available with any site
or the risk value and all the things are not required to be.
Added into an application, so you just need to make sure that the delay that you want, you correctly
take them OK and while configuring WTT Time, right?
So when you create your block, is there itself, you need to make sure that you correctly calculate
the value off of it, depending on the day that you hit, and then you specify the week to write the
valid range or allow ranges from me to 31, right?
So with this, we will build up our application project.
So just pest control.
This will start the process of creating any left.
So once file is ready.
We could just go and select an application project, debug s launch and hide it right?
So here we are, already connected via this terminal to a serial terminal.
OK.
Two com six And it is operating at the standard border route just 9.6, right?
So we'll just need to click on this resume button.
So you could clearly see we are getting WD D and it's successful.
This means that initialization is successful also.
So this is also success, right?
And after an interval of the ticket, we will be getting WD expired, right?
So this is how we utilize the watchdog timer to Genndy.
This specific amount of the or it could be generating a specific event, depending on the time that
you just specify.