1 00:00:00,120 --> 00:00:07,200 The primary use for a watchdog timer, besides a meeting in event at a regular interval is to reset 2 00:00:07,200 --> 00:00:11,160 our roster or to bring back our roster out of a deadlock, right? 3 00:00:11,370 --> 00:00:17,340 So let's assume we already know that we have a max time that could be consumed by our application rate. 4 00:00:17,340 --> 00:00:21,000 So we specified that amount in stock. 5 00:00:21,000 --> 00:00:24,750 Daimler and as a counter insider, was Dr. Murray. 6 00:00:24,750 --> 00:00:33,360 Just to zero basically indicate that we consume more time as expected from an application, right? 7 00:00:33,370 --> 00:00:38,550 So what we're going to do is if our application runs perfectly well, then in that case, at the end 8 00:00:38,550 --> 00:00:43,500 of our application, we'll just be restarting a watch dog name or in that case, was docked time or 9 00:00:43,500 --> 00:00:45,180 won't be generating a reset signal. 10 00:00:45,420 --> 00:00:52,080 But later do we consume the time that we specify the watchdog Daimler for running an application? 11 00:00:52,080 --> 00:00:56,490 In that case, we basically mean that our application is stuck somewhere, right? 12 00:00:56,490 --> 00:01:01,110 So to bring it out of a deadlock, what we do is we reset our system, right? 13 00:01:01,440 --> 00:01:05,430 This is what we're going to do this now since we already connected a watch dog timer. 14 00:01:06,630 --> 00:01:12,300 We will be bringing back our pointer to the first location, right? 15 00:01:12,900 --> 00:01:15,030 This is what we're going to implement over here, right? 16 00:01:15,330 --> 00:01:20,550 So only modification that we're going to do it here, we will be acknowledging and in shock will be 17 00:01:20,550 --> 00:01:21,180 disabling. 18 00:01:21,310 --> 00:01:21,620 OK. 19 00:01:21,640 --> 00:01:23,490 And then we go ahead. 20 00:01:24,120 --> 00:01:25,980 We will be. 21 00:01:27,180 --> 00:01:29,490 Reminders, wristwatch, watchdog, timer also. 22 00:01:29,610 --> 00:01:35,250 OK, we'll just be adding this school over here right now, what this does is it automatically bring 23 00:01:35,250 --> 00:01:37,740 our pointer back to the first address, right? 24 00:01:37,750 --> 00:01:41,250 So this will be bringing out our Rosseter out of date. 25 00:01:41,490 --> 00:01:41,710 Right. 26 00:01:41,730 --> 00:01:42,810 That is what we're going to do. 27 00:01:43,030 --> 00:01:50,850 They'll be displaying the Doppler on the console and the same time you need to observe their pointer. 28 00:01:51,240 --> 00:01:55,410 So the pointer is highlighted by a green color when we perform debugging. 29 00:01:55,980 --> 00:02:02,340 So let me just go ahead and try to try to build an application that is the first thing that we do as 30 00:02:02,340 --> 00:02:05,700 we update our application, then we'll select a configuration. 31 00:02:05,700 --> 00:02:10,920 So this is a configuration that we are running right click and then we have a relaunch button, right? 32 00:02:11,130 --> 00:02:17,660 So will be again programming RPG and we'll be running this application on to an FPGA, right? 33 00:02:17,670 --> 00:02:23,940 So we go to and why this terminology right now here you could really see our pointer is shown with a 34 00:02:23,940 --> 00:02:24,730 green color, right? 35 00:02:24,750 --> 00:02:30,420 So our process, Ithaca is currently at this point, and as we resume our application, it we start 36 00:02:30,420 --> 00:02:32,160 executing from this instance, right? 37 00:02:32,160 --> 00:02:39,030 So let me just say that I took with this, you know, our application is so clear after an interval 38 00:02:39,030 --> 00:02:40,500 of 10 second, OK. 39 00:02:40,770 --> 00:02:43,500 So in this case, we are not restarting our washed up time. 40 00:02:43,500 --> 00:02:43,800 All right. 41 00:02:43,800 --> 00:02:49,830 So as soon as we rule out, you will clearly see we bring our pointer back to any flat, right? 42 00:02:49,830 --> 00:02:55,980 So this could be when we are bringing our application back from the deadlock to the first location and 43 00:02:55,980 --> 00:03:01,770 again, start executing right so that we that we have this, we could use the word timeout, reset our 44 00:03:01,770 --> 00:03:08,880 microbes so that the application that is 249 flash memory of an effigy could be loaded and we again 45 00:03:08,880 --> 00:03:12,320 start application on any right.