1 00:00:00,150 --> 00:00:06,450 Let us try to understand the next category of periphery, OK, which include you what this could be 2 00:00:06,450 --> 00:00:12,570 considered as an intermediate complexity paper, he goes along with the data handling. 3 00:00:12,570 --> 00:00:19,830 We also need to work around it in operating modes, then handling at different parameters which help 4 00:00:19,920 --> 00:00:24,420 the communication between the two devices could be at synchronously. 5 00:00:24,510 --> 00:00:24,810 Right. 6 00:00:25,050 --> 00:00:25,440 So. 7 00:00:26,960 --> 00:00:34,550 This is a bit difficult as compared to a Tupaea excited UPI or paper that we have considered this a 8 00:00:34,550 --> 00:00:37,440 bit difficult as compared to previous. 9 00:00:38,240 --> 00:00:38,580 OK. 10 00:00:39,020 --> 00:00:43,820 And this will give us an opportunity to understand more complex benefit rates will be prosecuted. 11 00:00:43,820 --> 00:00:44,450 The simple. 12 00:00:45,430 --> 00:00:51,560 Block design that we been utilizing from the beginning, right to here, we will first proceed with 13 00:00:51,560 --> 00:00:58,780 then working it down with you, what we choose statically connected to a processing system with an might, 14 00:00:58,810 --> 00:00:59,110 right? 15 00:00:59,410 --> 00:01:01,730 We already know there are three different ways. 16 00:01:01,750 --> 00:01:02,140 OK. 17 00:01:02,210 --> 00:01:05,140 Whereby which you could communicate to the benefit. 18 00:01:05,140 --> 00:01:10,480 And here we are considering the first we where we have a processing system connected directly to and 19 00:01:10,480 --> 00:01:19,180 you want great neutron will also be considering what should be your strategy when you have peripheral 20 00:01:19,180 --> 00:01:26,440 IP situated in an FPGA fabric and then utilize the standard interface such as the IXI to communicate 21 00:01:26,440 --> 00:01:29,200 the data to Typekit, right? 22 00:01:29,470 --> 00:01:33,660 So if you just double click to reconfigure an IP, you would clearly understand that. 23 00:01:33,670 --> 00:01:39,150 Are you what is directly connected to a crossing system where they my open number 48 and 49? 24 00:01:39,160 --> 00:01:45,040 So if you just go to page, if they rely upon get here, you will see we only enable one paper, which 25 00:01:45,040 --> 00:01:45,880 is you white one. 26 00:01:46,180 --> 00:01:55,910 And this is connected to the actual hardware, with an open number 48 and 49 to 48 disconnected and 27 00:01:55,930 --> 00:01:57,980 49 is connected to state. 28 00:01:58,360 --> 00:02:01,120 So we will understand how we work around with. 29 00:02:02,360 --> 00:02:07,740 A situation when we have a paper connected with an email suggests you are right. 30 00:02:08,060 --> 00:02:11,140 So we will go ahead and will launch it and stick it. 31 00:02:11,150 --> 00:02:17,900 So I have what really generated a breakthrough which could be easily guessed by looking into the status 32 00:02:17,900 --> 00:02:18,320 quo here. 33 00:02:19,130 --> 00:02:22,490 And I have already due to hardware. 34 00:02:23,730 --> 00:02:25,830 Into NSW, right, so including a. 35 00:02:26,730 --> 00:02:33,870 We could proceed with launching an SDK that will try to build up our application to be first. 36 00:02:34,980 --> 00:02:41,640 No first will take the simple steps such as wearing the birth rate is sending a simple data, and this 37 00:02:41,640 --> 00:02:45,090 will help us to understand whether it's working correctly or not. 38 00:02:45,090 --> 00:02:45,390 Great. 39 00:02:45,720 --> 00:02:51,950 So I've already created a new application project, and they all are already adding you just to see 40 00:02:51,960 --> 00:02:57,460 what time, so you find out the driver which will work with you, what they said. 41 00:02:57,690 --> 00:03:01,260 So you just need to go to a MRS file and then look for you. 42 00:03:01,260 --> 00:03:02,520 What went right? 43 00:03:02,550 --> 00:03:06,410 So here you have you are one and the recommended driver is, you are. 44 00:03:06,750 --> 00:03:08,730 So that is what we included over here. 45 00:03:08,730 --> 00:03:10,350 Ex, you like the storage. 46 00:03:10,680 --> 00:03:12,540 You also include an experimental drug. 47 00:03:12,720 --> 00:03:16,740 So this will give us all the information related to our heart rate. 48 00:03:17,130 --> 00:03:18,630 Again, we are required to structure. 49 00:03:18,630 --> 00:03:20,190 One is an instant structure. 50 00:03:20,370 --> 00:03:27,340 OK, you are saying if you go to you, like start storage, that is a device for you. 51 00:03:27,900 --> 00:03:30,790 You could see we have multiple structure, right? 52 00:03:30,810 --> 00:03:34,710 So to structure, which will be targeting is the conflict structure. 53 00:03:34,800 --> 00:03:35,160 OK. 54 00:03:35,550 --> 00:03:39,120 And then the next one that we have is an instance D.D.S.. 55 00:03:39,150 --> 00:03:47,820 Now if you compare this with the structure that we have for our simple Tupaea essay, you'll be fine. 56 00:03:47,850 --> 00:03:53,700 Here we have a lot of other data which are not present in a previous case right now. 57 00:03:53,820 --> 00:03:57,780 This is the first instance structure and then we have a config structure, right? 58 00:03:57,780 --> 00:04:02,790 So we will be clearing the config structure as a pointer and the instance structure, as you write, 59 00:04:03,410 --> 00:04:09,300 will go to you walked in function that will be handling an entire process of initializing up very, 60 00:04:09,300 --> 00:04:10,220 very right. 61 00:04:10,410 --> 00:04:14,790 We declared one variable which will be holding the value of KFC initialize, right? 62 00:04:15,090 --> 00:04:18,090 So first, which ended the reader for a config structure. 63 00:04:18,090 --> 00:04:19,950 So you are config will be lost. 64 00:04:19,950 --> 00:04:23,310 You just need to look for a lookup config keyword. 65 00:04:23,460 --> 00:04:23,850 OK. 66 00:04:24,300 --> 00:04:29,520 So here we have a look upon which required a device idea, and this will return the config structure. 67 00:04:29,530 --> 00:04:31,410 So this is what we are doing over here. 68 00:04:31,770 --> 00:04:35,310 We specify the you what one device ID lookup config function. 69 00:04:35,580 --> 00:04:42,960 Then this will return the UI config structure, which will be adding to the structure that we declare 70 00:04:42,960 --> 00:04:43,340 over here. 71 00:04:43,350 --> 00:04:46,020 The next step is to utilise initialize function. 72 00:04:46,350 --> 00:04:48,210 Again, it requires the argument. 73 00:04:48,210 --> 00:04:54,120 First one is an instance structure, then the config structure and then the effect to be set right. 74 00:04:55,020 --> 00:04:59,960 So this will retain the status where there are initialization is successful or not. 75 00:05:00,030 --> 00:05:05,040 So if it is successful, OK, we'll just be comparing it with an existing see this. 76 00:05:05,040 --> 00:05:11,160 And if that is true, we will be displaying the message that device initialization is sexist. 77 00:05:11,280 --> 00:05:11,580 Right? 78 00:05:11,840 --> 00:05:15,280 Else we will just be mentioning that device initialization. 79 00:05:15,700 --> 00:05:21,330 We know when we are utilising you are in a previous case, so we are waiting to. 80 00:05:22,330 --> 00:05:25,180 Function to initialize, are you OK? 81 00:05:25,450 --> 00:05:28,900 One of them is an IT platform in Durban, is clean platform. 82 00:05:28,900 --> 00:05:31,000 Now we are ourself initiating. 83 00:05:31,000 --> 00:05:31,450 You are. 84 00:05:31,720 --> 00:05:35,530 So we do not need to utilise that function, right? 85 00:05:36,190 --> 00:05:41,270 We could proceed calling just you walked in it and this will automatically initialize, Are you OK? 86 00:05:41,300 --> 00:05:43,550 So we'll just be calling you walked in. 87 00:05:43,570 --> 00:05:48,160 So the rest of the functions are not required, which we have in a previous case when we are working 88 00:05:48,160 --> 00:05:48,790 with GPI. 89 00:05:48,880 --> 00:05:53,860 So we have a neat platform and clean up platform that we do not require now.