1 00:00:00,180 --> 00:00:03,490 So let us try to consider how we use this in a pool. 2 00:00:04,350 --> 00:00:10,620 So immediately when we work around with the EDC, we try to use and ensure because they have we get 3 00:00:10,620 --> 00:00:17,010 few more capability that's compatible more, but will also be demonstrating it so that you have a fundamental 4 00:00:17,010 --> 00:00:22,460 idea about what you see and what are the different updates that are available in the drivers. 5 00:00:23,280 --> 00:00:30,150 And as we progress and just goes on and into there, we will be covering some of the concept which are 6 00:00:30,150 --> 00:00:31,350 not covered here, right? 7 00:00:31,830 --> 00:00:39,690 So by default, UDC's locked in a bill similar to what we have with the private CPO timer and washed 8 00:00:39,840 --> 00:00:40,460 time right? 9 00:00:40,710 --> 00:00:44,230 So we need to purposefully we need to manually enable them. 10 00:00:44,290 --> 00:00:51,450 OK, so we'll just go with the basic block to say OK that we've been doing from the beginning by utilizing 11 00:00:51,450 --> 00:00:55,970 a teaser script, and then we will be adding the DTC. 12 00:00:56,220 --> 00:01:01,500 So here you see it, block, but you just double click and will enable time with you. 13 00:01:01,530 --> 00:01:01,800 Right? 14 00:01:01,830 --> 00:01:03,270 This is the first step that we do. 15 00:01:04,200 --> 00:01:08,190 And then we will be selecting an interface type to be EMI. 16 00:01:08,230 --> 00:01:11,610 Rachel, if you can see that email. 17 00:01:11,730 --> 00:01:17,190 So if you go to a very, very low and analyse to zero. 18 00:01:18,330 --> 00:01:28,860 So we have zero here with no in 90, but that you would clearly see cross with Dennis de 0£ as well 19 00:01:28,860 --> 00:01:36,680 as any to make this up part party pain for us, so we will not be utilizing zero. 20 00:01:36,720 --> 00:01:37,860 Am I 18, 19? 21 00:01:37,860 --> 00:01:40,190 Because there we have learned anything. 22 00:01:40,650 --> 00:01:43,660 If you consider the next one to, we have 30 and 31. 23 00:01:43,680 --> 00:01:45,180 So again is zero. 24 00:01:45,780 --> 00:01:51,650 And you also have and you be zero and zero on the same at my rate. 25 00:01:51,930 --> 00:01:54,310 So the good idea would always be to go over. 26 00:01:54,360 --> 00:01:55,230 10 Am I open? 27 00:01:55,710 --> 00:01:56,910 OK, yeah, my open. 28 00:01:58,610 --> 00:02:02,260 And then next thing that we required is to specify that. 29 00:02:02,450 --> 00:02:06,260 So if you just go to a clock configuration there you have an option timer. 30 00:02:06,270 --> 00:02:10,960 So it's zero, which is the timer zero that we are utilizing IDAG. 31 00:02:10,970 --> 00:02:15,740 This clock frequency, OK, so it is operating at one one one Makaha tonight. 32 00:02:16,010 --> 00:02:23,400 This data will also be by a note from the driver x parameter which tribe right will be on this journey? 33 00:02:23,420 --> 00:02:27,740 Just remember that this is the frequency at which RTC is operating again. 34 00:02:27,740 --> 00:02:30,020 Clock sources the CPU 1x. 35 00:02:30,380 --> 00:02:31,700 We could also specify an. 36 00:02:32,690 --> 00:02:37,100 So if you have a requirement right now, let just go ahead and click OK. 37 00:02:37,190 --> 00:02:40,810 So as we consider the e-mail, so we have a three output, right? 38 00:02:40,820 --> 00:02:47,150 So we will be least concerned about an output because we want to understand fundamental operations with 39 00:02:47,210 --> 00:02:54,680 ADC as we progress that in and try to utilize this output right will not be making any one of them external. 40 00:02:54,740 --> 00:02:56,510 We'll just be validating our design. 41 00:02:56,520 --> 00:03:03,110 So there's an automatic data connection and that you could actually verify by noting that validation 42 00:03:03,110 --> 00:03:03,980 is successful. 43 00:03:04,220 --> 00:03:10,540 So once this process is done well, go ahead to block design and create a wrapper, right? 44 00:03:10,550 --> 00:03:14,540 So this is the next thing that we do as we complete that wrong design. 45 00:03:14,780 --> 00:03:20,870 So what has happened is really that we already know that DDR and fixed air already connected to their 46 00:03:20,870 --> 00:03:21,680 respective open. 47 00:03:22,070 --> 00:03:28,430 And we do not consider these external things for connection to a base. 48 00:03:28,640 --> 00:03:30,890 So we could just proceed to the generation of objects. 49 00:03:31,340 --> 00:03:34,330 So we'll go ahead and click on each and need to. 50 00:03:35,700 --> 00:03:43,680 Right now, the modification that we did in the case of previous example, where we consider 32 bit 51 00:03:43,860 --> 00:03:46,200 washed off timer and that you do the. 52 00:03:47,380 --> 00:03:53,160 The only modification that we did in as compared to our previous case, when we are discussing that 53 00:03:53,170 --> 00:03:59,050 little bit timer which are private to keep CPU as well as they do to get washed up is they need to manually 54 00:03:59,050 --> 00:03:59,960 enable GDZIE. 55 00:04:00,130 --> 00:04:05,980 OK, then block searches again a CPA and it is operating at one one one megawatt.