WEBVTT 00:00.060 --> 00:06.150 One of the popular resorts that we frequently required to perform a temporary amputation or temporary 00:06.150 --> 00:09.570 storage of oddities or internal RAM that we have right. 00:09.720 --> 00:13.520 Or usually we refer to it as an extra right. 00:14.070 --> 00:16.590 So be finding in most of the microcontroller. 00:17.070 --> 00:20.840 We have a limited amount of the size for it. 00:21.090 --> 00:24.180 In fact, on an average, which also we have a limited size of whereat. 00:24.360 --> 00:27.440 But if you compare the size, you'll be finding a notable difference. 00:27.520 --> 00:34.680 Usually if you see General-Purpose Microcontroller, we can have up to one M.B of RAM. 00:34.860 --> 00:40.380 OK, but if you consider or compare it with an FPGA, we usually have an. 00:40.980 --> 00:47.250 So for example, if you consider to block RAM, so depending on the varying size, we have a different 00:47.520 --> 00:50.450 amount being present on a specific FPGA chip. 00:50.460 --> 00:55.660 So we usually range from two M.B to 12 to 15 and we also block them. 00:56.040 --> 01:00.500 Other than that, we can also utilize a logic resource to implement a memory. 01:00.660 --> 01:06.300 So that also gives us a further extension in the memory capability. 01:06.660 --> 01:09.330 OK, so those are the two resources that we have. 01:09.470 --> 01:18.330 The other key advantage, other than the size, the extra size or the higher size that we get for IBM 01:18.510 --> 01:20.100 is the flexibility. 01:20.130 --> 01:27.570 So, for example, in most of the microcontroller, we are finding that the size of the size of element 01:27.570 --> 01:30.050 that we are storing have a fixed rate. 01:30.070 --> 01:35.760 So, for example, depending on the architecture, it may have a 16 bit element storage capability or 01:35.760 --> 01:37.680 32 bit element storage capability. 01:37.680 --> 01:40.500 But this is not at all a case with an FPGA. 01:40.500 --> 01:46.560 So it'll be finding if you just go to a ram, OK, it'll be finding you can choose to read and write 01:46.800 --> 01:48.850 from one to four six zero eight. 01:48.870 --> 01:52.970 So we do not have any constraint on the vict. 01:53.860 --> 02:00.370 Of the element that you want to store inside that is there, you can see the first difference if you 02:00.370 --> 02:07.210 compare the RAM that you get out of an FPGA to the RAM that you have in a tender because microcontroller, 02:07.210 --> 02:10.720 in fact, it'll be finding that depth is also configurable. 02:10.750 --> 02:16.520 Okay, so that is also not fixed, which is in the case of most of the general purpose microcontroller. 02:16.570 --> 02:24.500 OK, so we can vary the depth and this allows us to control the amount of resources that we are consuming. 02:24.530 --> 02:32.050 We have an unused ram inside and microcontroller, so we cannot utilize it for another purpose. 02:32.050 --> 02:40.450 But in an FPGA we can configure the DEP so that the resources, the remaining resources can be utilized 02:40.780 --> 02:43.060 to implement certain other functionality. 02:43.110 --> 02:49.630 OK, so you have a configurable read and write it within RAM that we have into an FPGA. 02:49.840 --> 02:53.740 We also have a configurable depth size in hand. 02:54.220 --> 02:57.640 And along with that you can also add the. 02:58.620 --> 03:02.110 Popular communication interface to it. 03:02.130 --> 03:05.490 So, for example, right now we'll be finding it, have a knack of interface. 03:06.000 --> 03:07.230 OK, if you just add. 03:08.340 --> 03:16.500 And so for now, now, it will automatically configure itself to operate with a device that can understand 03:16.500 --> 03:17.790 NASA protocol. 03:17.820 --> 03:18.150 Right. 03:18.210 --> 03:26.010 This gives us an advantage of our flexibility of choosing the element size, choosing the depth as well 03:26.010 --> 03:26.970 as the. 03:27.880 --> 03:32.650 Communication interface, which can be used to send and receive the data from Obaida.