1 00:00:00,060 --> 00:00:04,720 Now, since we do not need to do much of a confrontation, the call will be very simple. 2 00:00:05,020 --> 00:00:10,470 The first thing that we do is to restrain the driver that could be utilized to correctly initialize 3 00:00:10,470 --> 00:00:11,420 our watchdog timer. 4 00:00:11,550 --> 00:00:18,150 So if you go to the board support package, so the driver that is highlighted is WTT DB, right? 5 00:00:18,150 --> 00:00:19,830 So we just need to Ireland, says A. 6 00:00:20,730 --> 00:00:25,390 So we go to an Helloworld or C, and the first thing that we do is to include the driver. 7 00:00:25,390 --> 00:00:28,650 It will be x wd db, right. 8 00:00:28,650 --> 00:00:34,320 This will consist of all the which could be used to correctly initialize our watchdog firmware as well 9 00:00:34,320 --> 00:00:41,910 as utilize it right then parameter lautech, which would be used to find out and hard the hard way related 10 00:00:41,910 --> 00:00:42,480 information. 11 00:00:42,490 --> 00:00:48,690 Right then we the Clayton structure first one is the conflict structure and the next one is an instance 12 00:00:48,690 --> 00:00:49,380 structure, right? 13 00:00:49,740 --> 00:00:56,880 The first thing that we do while performing and initialization is called lookup config function, where 14 00:00:56,880 --> 00:00:59,640 we will be adding the device, right? 15 00:00:59,640 --> 00:01:06,110 So this device ID could be found out from X parameter and this function will return the config structure. 16 00:01:06,120 --> 00:01:11,880 So once you have a conflict structure, you call CFD initialize, which required an instance structure, 17 00:01:12,150 --> 00:01:14,520 the structure and a separate state. 18 00:01:14,520 --> 00:01:21,330 So once you add this three argument to see if you initialize function that returns the status of initialization, 19 00:01:21,330 --> 00:01:28,410 right safe status is explicitly sexists, then if that case, we could see that WD and it is successful. 20 00:01:28,920 --> 00:01:30,740 Else we could see WTT. 21 00:01:30,760 --> 00:01:38,530 And then in a case of a complex, very perilous discourse, we will also be performing self-destruct. 22 00:01:38,550 --> 00:01:44,760 So we have EPA to perform a set of this, which required just a instance structure as an argument. 23 00:01:45,000 --> 00:01:49,860 So once you add that argument, this will return the status of our self again. 24 00:01:49,860 --> 00:01:52,520 We will be checking whether self-test is successful or not. 25 00:01:53,100 --> 00:01:55,230 This is equal to existing success. 26 00:01:55,800 --> 00:02:02,460 Then in that case, we could see that WD Self-Test is successful and we could just mention WD deserve 27 00:02:02,460 --> 00:02:02,660 this. 28 00:02:03,180 --> 00:02:09,550 So once boot, the thing and that is initialization is also successful and self test is also successful. 29 00:02:09,570 --> 00:02:16,580 We are ready to work it out with an EPA which provided for WD, right when we go to our main goal, 30 00:02:16,590 --> 00:02:19,980 the first thing that we do is after any black ops. 31 00:02:19,980 --> 00:02:26,760 So any platform you get when you use an halloway resin template based, this consist of all the initialization 32 00:02:26,760 --> 00:02:27,540 for and you what? 33 00:02:27,880 --> 00:02:33,120 So without configuration, we could just proceed writing or utilizing third printing, right? 34 00:02:33,120 --> 00:02:39,440 So need platform, cleaner platform and routine zero will be there when you invoke and halloway template. 35 00:02:39,570 --> 00:02:42,170 Great, we call WD in. 36 00:02:42,540 --> 00:02:46,560 This consist of all the initialization function for our washed off timer. 37 00:02:46,980 --> 00:02:50,690 The only thing that we need to do is just to stop a wash up. 38 00:02:51,000 --> 00:02:55,500 This will always be our strategy when we walk around with any of a time, right? 39 00:02:55,860 --> 00:02:59,260 So we stop our timer and then we are starting our time right. 40 00:02:59,280 --> 00:03:06,890 Then we have a function similar to what we have in any timer to check whether IWD gets fired or not 41 00:03:06,910 --> 00:03:07,510 right now. 42 00:03:07,530 --> 00:03:15,300 We already knew that we could not directly dynamically configure the fit of our count, right? 43 00:03:16,280 --> 00:03:19,640 So we will be waiting for a timer to expire. 44 00:03:20,810 --> 00:03:22,910 And then as our time expired. 45 00:03:24,010 --> 00:03:25,600 We will be coming out of this look. 46 00:03:26,540 --> 00:03:29,510 And we'll just be mentioning the politics by. 47 00:03:29,540 --> 00:03:29,840 Right? 48 00:03:30,080 --> 00:03:37,100 So if you just explode the functionality of this function, this returns to a five lost time has expired. 49 00:03:37,280 --> 00:03:44,610 So this will happen only when the least to the specified count as specified while configuring a ripe 50 00:03:44,650 --> 00:03:44,960 break. 51 00:03:44,990 --> 00:03:49,940 So as soon as we elapse a 10 seconds, we will be getting through. 52 00:03:50,180 --> 00:03:55,720 And for the first and second, when are counted as children will be always getting a false rate of sense, 53 00:03:55,730 --> 00:03:57,710 we need to wait for that instance. 54 00:03:58,100 --> 00:04:05,060 We have added the note operator, so this function will continuously retain the false for first and 55 00:04:05,060 --> 00:04:10,100 second OK, since our WTT won't be expiring for that duration. 56 00:04:10,340 --> 00:04:15,790 And as soon as it expired, it returns, do not approve, will be false and will be coming out of. 57 00:04:16,280 --> 00:04:20,110 Similar to what is happening with any excitement odds, right? 58 00:04:20,120 --> 00:04:24,960 And once that is done, we will just be sending WTT expired on. 59 00:04:25,700 --> 00:04:29,730 So this is an entire application code, which is very, very simple. 60 00:04:29,730 --> 00:04:31,420 That's compared to any time. 61 00:04:31,670 --> 00:04:37,370 So we do not need to configure the safe option, the different options that are available with any site 62 00:04:37,580 --> 00:04:41,630 or the risk value and all the things are not required to be. 63 00:04:42,640 --> 00:04:48,340 Added into an application, so you just need to make sure that the delay that you want, you correctly 64 00:04:48,400 --> 00:04:53,050 take them OK and while configuring WTT Time, right? 65 00:04:53,110 --> 00:04:58,690 So when you create your block, is there itself, you need to make sure that you correctly calculate 66 00:04:58,690 --> 00:05:04,630 the value off of it, depending on the day that you hit, and then you specify the week to write the 67 00:05:04,630 --> 00:05:08,860 valid range or allow ranges from me to 31, right? 68 00:05:09,070 --> 00:05:12,100 So with this, we will build up our application project. 69 00:05:12,120 --> 00:05:13,210 So just pest control. 70 00:05:13,720 --> 00:05:16,890 This will start the process of creating any left. 71 00:05:17,320 --> 00:05:18,940 So once file is ready. 72 00:05:19,330 --> 00:05:25,690 We could just go and select an application project, debug s launch and hide it right? 73 00:05:27,100 --> 00:05:31,480 So here we are, already connected via this terminal to a serial terminal. 74 00:05:31,900 --> 00:05:32,270 OK. 75 00:05:32,570 --> 00:05:38,430 Two com six And it is operating at the standard border route just 9.6, right? 76 00:05:39,400 --> 00:05:42,190 So we'll just need to click on this resume button. 77 00:05:42,400 --> 00:05:45,600 So you could clearly see we are getting WD D and it's successful. 78 00:05:45,610 --> 00:05:49,180 This means that initialization is successful also. 79 00:05:49,300 --> 00:05:51,450 So this is also success, right? 80 00:05:51,670 --> 00:05:57,670 And after an interval of the ticket, we will be getting WD expired, right? 81 00:05:58,150 --> 00:06:03,430 So this is how we utilize the watchdog timer to Genndy. 82 00:06:03,490 --> 00:06:10,990 This specific amount of the or it could be generating a specific event, depending on the time that 83 00:06:10,990 --> 00:06:11,710 you just specify.