1 00:00:00,060 --> 00:00:07,460 So our generation is completed successfully now, and next step will be to first export and hardware, 2 00:00:07,480 --> 00:00:08,610 including a big step. 3 00:00:09,090 --> 00:00:12,120 And then we will be launching in SD, right? 4 00:00:13,570 --> 00:00:17,140 So let us proceed by creating a new application project. 5 00:00:17,500 --> 00:00:19,690 We'll just be naming this as TDCi. 6 00:00:20,290 --> 00:00:20,680 OK? 7 00:00:20,710 --> 00:00:23,710 And we'll be invoking an alcohol template. 8 00:00:24,820 --> 00:00:31,540 Now, once we create an application project, we get an idea about what should be the recommended try 9 00:00:31,720 --> 00:00:33,560 for the specific benefit, right? 10 00:00:33,580 --> 00:00:37,330 So here if you consider digits zero, which we enable. 11 00:00:37,690 --> 00:00:47,050 So the most recommended trigger for us is DCP said, I will go ahead to the Helloworld or see right 12 00:00:47,290 --> 00:00:50,930 here now we need to do additional two things. 13 00:00:51,280 --> 00:00:58,330 First one is the exact parameter date, which will give us an idea about what are the different values 14 00:00:58,330 --> 00:01:00,450 we have for our target parameters. 15 00:01:00,460 --> 00:01:04,980 And then the next one is the trial specific to the TDCi, right? 16 00:01:04,990 --> 00:01:05,800 So we'll go ahead. 17 00:01:06,790 --> 00:01:12,460 With adding to you, OK, and here, the driver for us is ditsy. 18 00:01:12,550 --> 00:01:14,230 Yes, start right? 19 00:01:14,980 --> 00:01:22,270 And one more driver file that will be adding is X parameters start, right? 20 00:01:22,330 --> 00:01:28,510 This will give us and enough information required for configuring a variable as well as running. 21 00:01:28,570 --> 00:01:34,000 Right now, we'll go ahead and try to analyze the API that we have for a driver right again. 22 00:01:34,450 --> 00:01:36,850 This will be initialized by considering the scene. 23 00:01:37,790 --> 00:01:43,370 To structure, one of them is instant structure, and another one is on fixed rate, so we'll go ahead 24 00:01:43,640 --> 00:01:45,380 and try to add them both in. 25 00:01:45,380 --> 00:01:49,730 Our main rate to convict structure should be pointed. 26 00:01:49,790 --> 00:01:54,290 OK, so we'll just be naming this GTC config. 27 00:01:54,830 --> 00:01:58,960 The next one is an instance such the that we have, right? 28 00:01:59,050 --> 00:02:02,680 So we'll just be going ahead and will naming it as GTC. 29 00:02:03,270 --> 00:02:08,720 OK, so let's proceed with creation of an initialize function, right? 30 00:02:08,720 --> 00:02:11,120 So we'll just be naming this as GTC in it. 31 00:02:12,050 --> 00:02:18,560 We will require see this variable that will be useful in verifying whether we are getting existing success 32 00:02:18,560 --> 00:02:18,890 or not. 33 00:02:18,920 --> 00:02:19,190 Right. 34 00:02:19,190 --> 00:02:27,170 So the first API that we have that will look for the device, OK, in that and type people is look up 35 00:02:27,170 --> 00:02:27,620 config. 36 00:02:27,620 --> 00:02:34,280 So if we just go to a driver you haven't look upon right here, you just need to pass the device. 37 00:02:35,060 --> 00:02:37,010 So did you see? 38 00:02:37,920 --> 00:02:44,940 Can't think this should be worse to look up on fake, and then here we need to pass a device I.D. So 39 00:02:44,940 --> 00:02:50,430 if you just go to the experimental dot and look for Etsy. 40 00:02:51,180 --> 00:02:53,820 OK, so here we have it. 41 00:02:54,660 --> 00:02:56,940 So here we have our device. 42 00:02:57,180 --> 00:02:58,410 So we just copy this. 43 00:02:59,370 --> 00:03:00,830 Rely on it here, right? 44 00:03:00,840 --> 00:03:08,040 So this will return the DTC config structure, which will be utilizing to initialize our DDCA. 45 00:03:08,400 --> 00:03:15,270 So to perform an initialization, the API that we have is CFD initialized. 46 00:03:15,510 --> 00:03:18,840 So here we have this API, this basically written instead. 47 00:03:19,110 --> 00:03:20,880 So we'll just be going ahead. 48 00:03:21,630 --> 00:03:24,750 First thing it required is an instant structure, which we need less. 49 00:03:25,380 --> 00:03:29,010 Then the config structure to UTC on fake. 50 00:03:29,100 --> 00:03:31,810 OK, and finally then effectively be set. 51 00:03:31,970 --> 00:03:37,590 So that could also be accessed from D.D.S. config so that this conflict can. 52 00:03:37,590 --> 00:03:40,620 Then this operator and we have a visitors rate. 53 00:03:41,220 --> 00:03:42,570 So this complete this step. 54 00:03:42,750 --> 00:03:50,490 Now we will just be verifying whether the students return is existing sets and state so students should 55 00:03:50,490 --> 00:03:56,460 be close to SSD success or it should be close to a single rate. 56 00:03:57,530 --> 00:04:09,210 And if that is the case, we will just be mentioning in and its success rate and we'll just be mentioning 57 00:04:09,210 --> 00:04:10,340 UTC net. 58 00:04:11,540 --> 00:04:12,310 Fee, right? 59 00:04:12,590 --> 00:04:17,450 This is going nowhere near where we are working with an intermediate that you could have, as discussed, 60 00:04:17,450 --> 00:04:19,720 will also be performing a self-test, right? 61 00:04:20,510 --> 00:04:24,620 So that will basically give us an idea where the heart rate is configured correctly. 62 00:04:24,650 --> 00:04:24,950 Right. 63 00:04:25,250 --> 00:04:30,080 So let me just go ahead and try to find out the API that we have for us at this rate. 64 00:04:30,140 --> 00:04:33,650 Those ingredients that you do, we just need to pass an instill structure. 65 00:04:33,760 --> 00:04:33,980 Right? 66 00:04:34,430 --> 00:04:35,850 So we'll updating. 67 00:04:35,870 --> 00:04:41,890 We will be updating the just value, OK, by the value that is written by our self dysfunction here 68 00:04:41,900 --> 00:04:42,250 also. 69 00:04:42,660 --> 00:04:48,380 We just need to pass an instance structure and then will again be performing a comparison. 70 00:04:48,380 --> 00:04:55,580 But this time the message that we'll be sending is self test success rate down here. 71 00:04:56,390 --> 00:05:00,470 We'll just be mentioning cell test fee, right? 72 00:05:00,920 --> 00:05:06,100 So these are the kinds of things that we do to perform an initialization of benefit, right? 73 00:05:06,110 --> 00:05:09,860 So we declare to structure, we utilize lookup config. 74 00:05:09,890 --> 00:05:10,280 OK. 75 00:05:10,430 --> 00:05:12,890 This will lead to the config structure for us. 76 00:05:12,890 --> 00:05:19,020 And then utilizing that, we use CFG initialize API to initialize our benefit. 77 00:05:19,100 --> 00:05:19,320 Right? 78 00:05:19,340 --> 00:05:21,890 Then we are checking whether initialization is successful. 79 00:05:22,670 --> 00:05:28,820 So once the initialization is successful, we are performing a set of this should work OK, and then 80 00:05:28,820 --> 00:05:30,800 we could proceed for development of any. 81 00:05:31,040 --> 00:05:35,200 So let me just go and try to see what code and programming SPG. 82 00:05:37,120 --> 00:05:42,460 So when programming is successful, we'll just be collecting and to get dominance to come for, OK? 83 00:05:42,880 --> 00:05:47,050 And then we'll be running our configuration on an FPGA. 84 00:05:47,060 --> 00:05:49,450 OK, so right click released launch on Hideaway. 85 00:05:50,740 --> 00:05:57,130 So now we'll just be calling after the platform, I didn't see any great. 86 00:05:58,250 --> 00:06:03,770 And this a is not required, so we could just come and do so right, so let's just go ahead and just 87 00:06:03,890 --> 00:06:05,510 relaunch in session. 88 00:06:06,840 --> 00:06:14,280 And no, you could notice that D.C. and they did successful as well as circuit test is also successful. 89 00:06:14,520 --> 00:06:20,220 So this complete step one now will proceed for writing an application, so our agenda will basically 90 00:06:20,220 --> 00:06:21,620 be to generate a fixed fix. 91 00:06:22,200 --> 00:06:22,620 OK? 92 00:06:23,430 --> 00:06:32,070 Later on will be considering some of the examples, such as how we could provide utilizing PPC or utilizing 93 00:06:32,880 --> 00:06:37,640 the DDC to create the fix and then triggering another verification, right? 94 00:06:37,650 --> 00:06:41,070 So first, we'll just be proceeding for creating a fix. 95 00:06:41,370 --> 00:06:48,030 So you have a fundamental idea of utilizing various functions, and then we could just modify this example 96 00:06:48,030 --> 00:06:53,250 a bit so that you would understand the different scenarios where we could utilize that EDC, right?