WEBVTT 00:00.060 --> 00:02.100 So we took away some of the. 00:02.980 --> 00:07.010 Implementation strategies to help improve our design. 00:07.030 --> 00:14.730 So, for example, some it becomes necessary that we need to meet the paperwork on scene to match the 00:14.740 --> 00:16.690 power budget that we have for a system. 00:16.700 --> 00:17.020 Right. 00:17.230 --> 00:18.760 Or if we want to. 00:20.400 --> 00:23.340 Improve your utilization or timing. 00:25.360 --> 00:31.060 Performers, then inductees, and the standing and implementation strategies which are provided by everybody 00:31.100 --> 00:32.360 plays a very crucial. 00:32.740 --> 00:39.280 So our agenda will be to discuss how you basically utilize the step. 00:40.360 --> 00:45.370 To perform or to use an implementation, strategies are available inside. 00:45.400 --> 00:52.300 We want to know there are a lot of implementation strategy that you have inside of and discussing every. 00:53.820 --> 00:56.910 Strategy is not at all possible. 00:56.940 --> 01:00.630 So what we'll do is we'll consider a few examples where we get a. 01:01.500 --> 01:10.980 Basic idea about the the steps that you need to follow to have an implementation strategy, invoke insight 01:11.070 --> 01:17.340 design and then later on you can explore the whole lot of implementation strategies which are available 01:17.340 --> 01:17.910 by default. 01:18.960 --> 01:21.070 OK, so we'll follow an entire procedure. 01:21.090 --> 01:22.640 We'll start with the CREATE Project. 01:27.840 --> 01:34.710 We'll stick to the foiled project location, as well as the Ford Project Click Next will select an actual 01:34.710 --> 01:35.130 project. 01:35.460 --> 01:45.510 Since we are preparing to supply the text messages and we have not created a design yet to stick to 01:45.510 --> 01:46.450 an actual project. 01:46.710 --> 01:51.480 Next will create a file that I just named as top. 01:52.710 --> 02:01.130 OK, next, and then we'll head finally select the board, the board that will be operating as a nexus 02:01.130 --> 02:01.790 for the year. 02:02.360 --> 02:11.130 OK, and then we'll just to finish so we have 11 schools fight where we will be specifying our usual 02:11.210 --> 02:13.640 group and then we'll proceed with an implementation. 02:13.700 --> 02:17.770 OK, so I have already created a code for our design. 02:17.780 --> 02:23.870 So we'll just take a year since we are interested with a complete rate now, since we already have a 02:23.870 --> 02:24.740 code with a straight. 02:25.070 --> 02:27.340 So I just go in there where we have our suits. 02:27.350 --> 02:27.610 Fine. 02:27.650 --> 02:30.380 And then I'll just be stockwood that I have created. 02:30.640 --> 02:33.980 OK, so just to summarize, what is inside the code. 02:34.160 --> 02:40.060 So this is a simple remedy that we have implemented out of and we will do OK here. 02:40.070 --> 02:41.000 You'll be noticing. 02:43.710 --> 02:47.850 That what we are doing is the size of military that we have is. 02:50.240 --> 02:55.780 We can still around one zero two four and each element can have a size of 232. 02:56.870 --> 03:00.220 So this is the two sides that are Ramiz capable of handling. 03:00.590 --> 03:05.180 And we have certain control points to just block the draping output. 03:05.800 --> 03:10.700 And the in and out is having the size of 32 and addresses also. 03:11.780 --> 03:16.800 Having the size of Gilbertson's, the depth that you are targeting is one zero two, right? 03:17.060 --> 03:18.530 And then we have certain logic. 03:18.540 --> 03:24.470 So do not worry about the logic right now, because you yourself will be designing this kind of war 03:24.710 --> 03:28.260 when we have a discussion on the memory elements. 03:28.280 --> 03:28.480 Right. 03:28.530 --> 03:37.160 So we'll just go ahead and will add a constitution, because when we are measuring the power, specifying 03:37.160 --> 03:39.950 the typical block, it becomes mandatory. 03:39.980 --> 03:43.760 So either you specify the frequency or you specify the. 03:46.820 --> 03:52.440 So remember, this thing when we are reporting about it becomes mandatory that you specify the clock. 03:53.110 --> 03:58.850 So only one thing that will be adding right now is since school is already begun to work on scene five. 03:59.210 --> 04:05.620 OK, well, click on the plus button will select out of the country, will create a consistent file. 04:05.660 --> 04:07.990 Will just need to stop TotEx D.C.. 04:08.240 --> 04:10.130 OK, and we'll finish. 04:12.540 --> 04:19.680 Now, if you go to the doctor here, you need to write a statement that will allow and Revital to identify 04:19.680 --> 04:21.470 the spirit that they're targeting. 04:21.510 --> 04:23.510 OK, so the treatment is very simple. 04:23.850 --> 04:26.640 We select three o'clock, then hyphae. 04:27.120 --> 04:29.810 We specify the period in nanosecond. 04:30.090 --> 04:36.420 So the number that you are inputting is taken in a nanosecond spiritist, a nanosecond, which basically 04:36.750 --> 04:42.180 means that we are working one hundred meters, which is standard clock in most of our projects that 04:42.180 --> 04:45.120 we'll be discussing in the course and for us. 04:46.340 --> 04:47.570 The clock borders. 04:48.700 --> 04:55.090 Named Astrachan, that can actually be verified by just going into our visual source and it will be 04:55.090 --> 04:59.670 noticing the Lakeport we named inside our design is club. 05:01.210 --> 05:01.590 They. 05:03.450 --> 05:07.570 OK, so this is an extra thing that we need to add and we'll just see rock on screen. 05:07.890 --> 05:12.090 So once consumed file is Israeli, what we'll do is we'll perform a synthesis. 05:12.120 --> 05:15.050 OK, so the first step is to perform a synthesis. 05:17.340 --> 05:22.980 So here, one step we have not far from that is checking the functional behavior in most of the cases 05:22.980 --> 05:27.120 since we are targeting here to understand an implementation strategy. 05:27.130 --> 05:32.880 But you in general, when you will be working on a project, you already have computed the functional 05:32.880 --> 05:38.670 behavior of your design and then you have to offset checking often synthesis. 05:38.670 --> 05:38.950 Right. 05:38.970 --> 05:39.360 So. 05:40.420 --> 05:46.450 We have we assume that we have already completed a functional behavior check by performing a run simulation, 05:46.690 --> 05:52.940 and we are now interested to understand only an implementation strategies that we get right. 05:56.830 --> 05:58.580 So our implementation is complete. 05:58.610 --> 06:04.600 Now, what we'll do is we'll just close this window, will go to open syntheses design and then you 06:04.600 --> 06:06.200 have an option to report. 06:06.620 --> 06:08.220 So we'll just click on that option. 06:09.420 --> 06:16.650 So this will open and do whatever we need to input certain parameters for the vital to calculate. 06:20.700 --> 06:26.220 OK, the only thing that will be specified is that rest of the thing will be keeping as it is the only 06:26.220 --> 06:33.490 thing that we will verify whether the report by our option actually will understand our flock of sheep. 06:33.960 --> 06:37.750 So you just go to a switching and you check a constraint. 06:37.980 --> 06:42.700 So here should be a nanosecond, which we specify and the proof should be Klok, right. 06:42.750 --> 06:44.970 That is what we have utilized in our design. 06:45.000 --> 06:46.180 So we just click, OK? 06:47.550 --> 06:51.900 I know you'll be finding that even though the confidence level is low. 06:52.140 --> 06:58.520 OK, but still we will get a rough estimate out of the power that our design is going to like. 06:58.770 --> 07:03.210 So the clock is going to doing seven percent of power. 07:03.240 --> 07:05.190 OK, what we'll do is we'll just. 07:06.380 --> 07:08.980 Stole the snapshot of this. 07:09.390 --> 07:12.040 OK, so this will help us to actually compare. 07:13.240 --> 07:21.070 When we adopt certain vital strategies and say that isn't right, so now we have a rough estimate about 07:21.070 --> 07:27.340 the power consumption that we that our design is consumed right now, you go to settings, so you'll 07:27.340 --> 07:29.340 be finding you have a setting goal here. 07:29.750 --> 07:35.790 So you just go in there and you select an implementation because we already completed this is now will 07:35.800 --> 07:37.380 be going to an implementation. 07:37.780 --> 07:40.670 So we vido implementation before. 07:41.910 --> 07:47.860 Is the strategy that has been selected right now, so we'll be finding the design is enabled, OK, 07:48.270 --> 07:55.020 and then you have physical design, boost is also enabled. 07:55.020 --> 08:00.190 And the rest of the things that now we want to optimize our power requirement right. 08:00.240 --> 08:05.070 To what will do is you will just be checking post, please, power of design. 08:05.880 --> 08:14.630 OK, so here you have an option to enable you power of design and then you can just hit the play, OK? 08:14.790 --> 08:17.000 And you can actually read the description. 08:17.010 --> 08:17.970 So this option. 08:19.130 --> 08:23.860 Designed to see power and resolve timing posts, please. 08:23.900 --> 08:32.480 OK, so we'll just hit play and we will take to right now we have specified our implementation strategies. 08:32.510 --> 08:34.400 OK, so the process is very simple. 08:34.400 --> 08:41.120 You go in there, you go to a setting you can walk around with and auto implementation default and then 08:41.120 --> 08:46.540 you can choose the different options that we have or else what you can do is OK. 08:46.850 --> 08:52.960 And what you can do is you have a different other type of strategy also available. 08:53.000 --> 08:53.250 Right. 08:53.270 --> 08:57.020 So it's purely your choice what you want to implement. 08:57.040 --> 08:57.240 Right. 08:57.260 --> 09:02.670 So it'll be finding the options that are available is to have a performance explorer. 09:02.690 --> 09:05.060 We also have something like. 09:06.550 --> 09:13.810 And area explorer revamp and that basically help us to if you're just worried it, you'll be finding 09:13.810 --> 09:15.760 a Akst the map. 09:17.010 --> 09:20.070 Optimization to reduce the logic and so on and so forth. 09:20.270 --> 09:27.300 So there are various strategies which are available to revert the default implementation and we have 09:27.300 --> 09:28.060 a nibbler. 09:29.630 --> 09:30.770 Power optimization. 09:30.860 --> 09:36.540 OK, so will it apply and will click, OK, now we are ready to perform an implementation. 09:36.560 --> 09:38.420 So just click on implementation. 09:40.680 --> 09:47.250 So this will take some fraction of a second to perform and implementation and here also you can observe 09:47.520 --> 09:56.550 that now you can actually see that the are applying of our design rules onto our design. 09:56.610 --> 09:59.830 OK, so we like to observe that optional. 10:00.030 --> 10:04.530 So you just observe the street as all of you on the top right corner. 10:06.610 --> 10:13.020 So we are running a of design, which is the first strategy that we have in and we will do implementation 10:13.030 --> 10:16.480 default, OK, then we have a police design. 10:19.180 --> 10:21.340 And boost policemen. 10:23.990 --> 10:31.820 OK, so our implementation is completed now, what we do is we just lose this passport and we go to. 10:32.840 --> 10:36.260 Open implemented design and will report again. 10:36.320 --> 10:41.560 One thing, we'll make sure that the window also identify are constrained. 10:41.930 --> 10:49.110 OK, so we'll just go to a switching and we'll see whether we still are able to identify the consumer. 10:49.470 --> 10:57.500 OK, so once you find your clock in there with the specified but you just said OK, and then. 10:58.400 --> 11:00.620 You can just have a comparison. 11:01.070 --> 11:08.930 OK, so the power of design, basically the user dynamic blocking the power that you dissipate when 11:08.930 --> 11:10.410 you perform undynamic block. 11:10.490 --> 11:11.450 OK, so usually. 11:13.570 --> 11:18.700 It is finitude with the help of a clocking automated clock that the. 11:19.690 --> 11:20.790 Can add to this. 11:21.280 --> 11:24.730 So we basically reduce the dynamic power that we. 11:27.880 --> 11:28.660 Get out of. 11:29.020 --> 11:33.630 So we'll be finding that this is our previous report, right? 11:34.120 --> 11:36.790 Four o'clock, we are consuming around seven percent. 11:36.940 --> 11:40.930 OK, and here you'll be finding that we are consuming our own fiber. 11:41.140 --> 11:49.840 OK, so this leads to by just adding and simple fiber optic strategy will be able to see a reduction 11:49.840 --> 11:52.210 in clocking, in fact, finding. 11:52.480 --> 11:55.540 We have just a single ramble here. 11:55.540 --> 12:02.290 When you have a complex designed to clock dynamics, switching will be consuming a good amount of power. 12:02.590 --> 12:04.870 OK, in that case, the. 12:06.510 --> 12:14.070 Adopting the power optimization strategy greatly reduces the power and the typical power saving that 12:14.070 --> 12:16.890 we get is around 15 percent to 30 percent. 12:17.190 --> 12:20.080 OK, and that is a huge amount of power that we can see. 12:20.100 --> 12:21.690 So this is how you. 12:22.610 --> 12:29.660 Can utilize the implementation strategies that we have, in fact, we do have the synthesis strategies 12:29.660 --> 12:33.780 also to achieve a better performance out of design.