1 00:00:00,060 --> 00:00:04,620 The next IP that we're going to use is an exact time based watchdog name, right? 2 00:00:04,650 --> 00:00:09,300 So we just click on this plus button, right, and look for the timer. 3 00:00:09,480 --> 00:00:10,650 You have to eyepiece right. 4 00:00:10,650 --> 00:00:15,390 So the exciting mode, which we previously discussed now, will be discussing the exciting based version 5 00:00:15,390 --> 00:00:21,510 of that right now, if you just go through the leadership of the exciting based virtual timer. 6 00:00:21,520 --> 00:00:28,260 And since we are focusing primarily on the full mode of our timer, right, we want to upgrade our time 7 00:00:28,260 --> 00:00:30,630 based watchdog timer in a WTT mode, Rachel. 8 00:00:31,260 --> 00:00:38,400 The double time interval is configured by a parameter to tools to offer WTT clock correct. 9 00:00:38,400 --> 00:00:40,590 So this this will be the delay that you'll be getting. 10 00:00:40,590 --> 00:00:41,570 So once you set up the. 11 00:00:42,120 --> 00:00:50,670 OK, so whatever clock you feed to the WTT, OK, that will be multiply it to rise to the fit of a WTT, 12 00:00:50,670 --> 00:00:54,670 and that is the delay that you get out of the time based watchdog, right? 13 00:00:55,200 --> 00:01:01,200 The weight of the parameter is an integer ranging from eight to 13 right to decide the valid range, 14 00:01:01,200 --> 00:01:03,150 which are allowed to utilizing an IP. 15 00:01:03,660 --> 00:01:10,590 That interval is set at co-generation time and cannot be modified dynamically through a controlled register, 16 00:01:10,590 --> 00:01:10,770 right? 17 00:01:10,770 --> 00:01:17,430 So this is something which is important point to note that as we configured our IP there with this fixed 18 00:01:17,430 --> 00:01:22,540 and later on when we developed our application, we are not allowed to change the OK. 19 00:01:22,590 --> 00:01:27,960 And you'll be finding that when we explore the driver of our time based washed off timer, you won't 20 00:01:27,960 --> 00:01:31,810 be finding any API that allows us to change the control we take. 21 00:01:31,830 --> 00:01:32,640 So we need to. 22 00:01:33,730 --> 00:01:36,610 Sector with depending on the dealer that we are targeting next. 23 00:01:37,000 --> 00:01:44,470 So let's assume we feed a clock of 100 meters, 600 megawatts is equal to 10 nanosecond and we set up 24 00:01:44,470 --> 00:01:46,040 the WTT to be 30. 25 00:01:46,080 --> 00:01:46,270 Right. 26 00:01:46,270 --> 00:01:49,120 So the deal that we'll be getting is around 11 second rate. 27 00:01:49,120 --> 00:01:55,300 So how we calculate delays due to the weight of WTT, which is 30 that we set up and the clock that 28 00:01:55,300 --> 00:01:58,870 we are feeding is having a block period of 10 nanosecond breaks. 29 00:01:58,870 --> 00:02:00,760 So how do you calculate the property? 30 00:02:00,970 --> 00:02:04,030 You simply take an inverse of the clock frequency, right? 31 00:02:04,030 --> 00:02:08,620 So we will be configuring f clock to be operating at 100 megawatt. 32 00:02:08,620 --> 00:02:12,460 So if you take an inverse of it, it will be giving us 10 nanoseconds, right? 33 00:02:12,970 --> 00:02:17,730 Let us see how we configure this and whether we are able to get the delay of 11 Typekit, right? 34 00:02:17,740 --> 00:02:20,910 So we go to every model right now to interface this IP. 35 00:02:20,920 --> 00:02:28,210 Since this have us leave Levitsky interface, look at that and say we need to enable the zero put on 36 00:02:28,210 --> 00:02:29,240 and sync processes. 37 00:02:29,250 --> 00:02:36,780 So and that will allow us to interface zinc processing system to a time based director will just reconfigure 38 00:02:36,940 --> 00:02:38,020 zinc processing system. 39 00:02:38,530 --> 00:02:42,550 So three things that we need to add OK, so we need to add risk. 40 00:02:43,640 --> 00:02:46,510 OK, so we go to a general that we enable a reset. 41 00:02:46,840 --> 00:02:55,030 We also enable Master ex-KGB zero interface and the clock that we are targeting for the yield fabric 42 00:02:55,030 --> 00:02:56,580 is 100 meters, right? 43 00:02:56,590 --> 00:02:58,290 So this is what we're going to have. 44 00:02:58,300 --> 00:03:00,430 So you need to consider this to be handed me that. 45 00:03:00,460 --> 00:03:04,750 So now we get the period of 10 second, so click OK. 46 00:03:04,960 --> 00:03:09,470 Once you do this, we will automatically show us collection automation right now. 47 00:03:09,490 --> 00:03:16,690 We are allowed to collect this and make zero to a slew of interviews of time with the right to perform 48 00:03:16,690 --> 00:03:17,650 collection automation. 49 00:03:18,670 --> 00:03:23,350 So once you perform an action automation now, you could clearly analyze we have a signal processing 50 00:03:23,350 --> 00:03:30,130 system utilizing any exciting technique to be able to connect zinc processing system to a time base 51 00:03:30,160 --> 00:03:31,450 Vostok time. 52 00:03:31,690 --> 00:03:36,550 So we won't be utilizing any of this output, but we will keep them floating, right? 53 00:03:36,550 --> 00:03:41,530 So we'll just perform our validation of the site and was validation is successful. 54 00:03:43,040 --> 00:03:45,320 OK, we will just be generating an. 55 00:03:46,500 --> 00:03:48,190 It's likely going to be blog design. 56 00:03:49,280 --> 00:03:51,320 And create an elaborate. 57 00:03:52,710 --> 00:03:58,620 So I design just consist of two pools, which are DDR and fixed air, and we already know that these 58 00:03:58,620 --> 00:04:00,690 are already matched to their respective hardware. 59 00:04:01,230 --> 00:04:04,590 So we kinetic need proceed for generation off of it, right?