WEBVTT 00:00.580 --> 00:07.320 We begin with a new strategy by targeting some of the real world projects that will help us to build 00:07.590 --> 00:14.520 fundamental understanding and also to understand so the strategies that we seek when we are working 00:14.520 --> 00:15.390 on a new project. 00:15.720 --> 00:21.750 So whenever you are starting with a new project that is always recommended that you looked into some 00:21.750 --> 00:29.150 reference designs, if they are available and then you proceed for a modification of that site. 00:29.370 --> 00:31.990 So in this video, we'll probably target. 00:32.000 --> 00:33.320 Then you walk into this. 00:33.330 --> 00:34.220 So you walk. 00:34.970 --> 00:46.180 Is going to be so will be transporting big and then it is usually used at a lower rate, so. 00:47.590 --> 00:54.550 Whenever you have a scenario where you want to communicate that Greene to tools and the distance is 00:54.550 --> 01:05.260 not much, and in fact the rate is also better when you have a requirement where lead also plays a significant 01:06.400 --> 01:12.730 role in that scenario, you prefer to go with the other side, one stage that you are provided for white 01:12.850 --> 01:17.470 communication or for data with a very low income. 01:17.500 --> 01:23.930 So if we compare it with the NBA, which is much faster, that's compared to us. 01:24.220 --> 01:31.780 But as you increase the number of devices, you'll be finding that the size of device goes on increasing 01:32.050 --> 01:33.680 due to the presence of US troops. 01:34.960 --> 01:37.540 But this doesn't happen with you. 01:37.540 --> 01:42.170 Watch and see what is being used only for point to point communication. 01:42.190 --> 01:47.480 So we'll be finding if you remove the VCR and a ground level. 01:47.530 --> 01:56.710 The two important points which are used for data communication is not so since there is no handshaking 01:56.710 --> 01:58.210 pins available to. 01:59.450 --> 02:07.670 Check whether the receiver is alive or not or the transmitter wants to send or where the receiver is 02:08.120 --> 02:15.800 having a dedicated Vaudrey, which transmitter has been configured for and so on and so forth, we usually 02:15.830 --> 02:17.300 use the software. 02:18.660 --> 02:28.760 So inside the data, we manage it in such a form that it conveys to a receiver that the transmitter 02:28.760 --> 02:35.690 is now want to transmit and then receiver can start collecting that. 02:36.170 --> 02:44.450 OK, so we'll be finding that in an ideal situation to expand or let us assume that we are targeting 02:44.480 --> 02:50.690 on or transmitting data from the big to the serial. 02:50.900 --> 02:51.210 Correct. 02:51.470 --> 02:53.760 So it will be utilizing only a single pin. 02:53.960 --> 02:54.230 Right. 02:55.160 --> 03:02.060 So in that case, what will be finding is the line that is going from an RPG to the. 03:03.400 --> 03:10.630 Cereal consumed or cereal will always be at an active high school tautologically or logic, one level 03:10.990 --> 03:13.550 that indicate an ideal condition of life. 03:14.100 --> 03:22.060 So whenever a user or you want to transmit the data, the first thing that it will do is it will pull 03:22.060 --> 03:25.900 that line so that indicate static condition. 03:25.970 --> 03:35.470 So as soon as you pull Lionello, that can be the message to the receiver that now we are transmitting 03:35.470 --> 03:39.470 the data and then you transmit the data one by one. 03:39.520 --> 03:45.340 Now you must be having an idea that you work at a time and we need to be comforted. 03:46.960 --> 03:52.290 And then finally, you can also write about it if you want to have a better control strategy. 03:52.420 --> 03:56.080 But then usually we do not ask for a small distance. 03:56.860 --> 04:05.200 It rarely happens that you are dealing there do exist some of the exceptions, but then in most of the 04:05.200 --> 04:07.300 cases, we try to avoid it. 04:07.380 --> 04:09.220 And then finally through. 04:10.580 --> 04:13.730 Stop a communication, we further make our line. 04:14.240 --> 04:22.040 OK, so this is how we convey the message to a receiver that we want to start the communication and 04:22.040 --> 04:24.640 then decide the leader that we are transmitting. 04:24.650 --> 04:26.290 And then finally, we are to stop. 04:26.470 --> 04:26.750 Right. 04:27.300 --> 04:28.850 And then subsequently we cannot. 04:28.850 --> 04:31.520 And you, if you wish to further transmitted. 04:31.990 --> 04:38.510 OK, so this is how you communicate that you ideally will be having your line and high street or not 04:39.230 --> 04:44.800 one state then whenever you want to transmit it, first line zero. 04:45.200 --> 04:47.360 OK, so this would be a start condition. 04:47.750 --> 04:50.510 Then we'll be transmitting a data aid data. 04:50.930 --> 04:59.720 Then finally, as we complete our data transmission or in fact a single data will be stopping or will 04:59.720 --> 05:03.100 be further pulling our line high, which is a strong condition. 05:03.110 --> 05:08.320 And then you can add a subsequent sense of what you want to wish to continue our transmission. 05:08.750 --> 05:12.370 Now, whenever you are designing a new project, always, it is a good choice. 05:12.380 --> 05:17.020 That understanding of the or the standing of you form you create a the future. 05:17.780 --> 05:20.860 So just looking at a new form, I have created this project. 05:20.870 --> 05:23.660 This will be pretty handy when you're writing a deficit. 05:23.990 --> 05:26.540 So in most of the cases when you are working on an. 05:29.380 --> 05:36.840 So you'll be finding you need to write officiants, finite state machine, and if you have a reference 05:37.050 --> 05:40.770 chart in your handwriting, this becomes very, very easy. 05:41.280 --> 05:42.750 So ideal condition. 05:42.750 --> 05:52.130 I'll be naming that state that I am not naming at the start because on the board I'll be using an iReport 05:52.140 --> 05:56.190 whose name will be a struct which indicate that you want to do this. 05:56.430 --> 06:00.070 So for that reason, I mean, this does very big. 06:00.300 --> 06:07.080 And if, you know, in the next date will be or in fact in that state itself will be checking whether 06:07.080 --> 06:08.330 you want to transmit. 06:09.120 --> 06:13.700 So a whole user will be coming to terms with it or not. 06:13.750 --> 06:20.820 So will be assigning one of the input two letters in one of the vibes which will be connected to Stockmann. 06:21.030 --> 06:27.860 And if you don't want to transfer data and simply make start being high or the IP switching in high 06:27.870 --> 06:34.830 position so that we can read information given to you that use it through dance with the data and then. 06:35.950 --> 06:43.540 If you do not want to transmit into details, simply keep the IP switching and lose. 06:43.910 --> 06:49.940 OK, so if you pressed the switch, it will basically indicate that you the work transmitted data. 06:50.290 --> 06:53.200 So it will move into the send data here. 06:54.350 --> 07:02.660 We'll basically transmit a single bit, OK, and then probably this flag will understand this, this 07:02.660 --> 07:08.990 is this data just to maturity, because you can communicate at a specific rate. 07:09.000 --> 07:11.330 So we need to match the rate. 07:11.330 --> 07:16.580 So for that reason, that a few methods actually you can follow a blocking method so you can generate 07:16.580 --> 07:24.470 a slower growth and then you can operate on data on this block, or you can either make a counter which 07:24.470 --> 07:25.460 will continuously go. 07:25.640 --> 07:31.550 And as soon as it reaches to account, which matches the rate at which you are transmitting, the data 07:31.550 --> 07:32.840 will simply be the flag. 07:32.870 --> 07:38.200 So here we are targeting one in check method, probably in the next place. 07:38.240 --> 07:43.800 Then we'll understand how you can use method to actually transmit. 07:44.000 --> 07:46.540 Seemed that you can do this method. 07:47.090 --> 07:48.770 So there can be two method. 07:48.800 --> 07:53.120 Some of the cases utilizing 3:00 is pretty easy. 07:53.480 --> 07:53.800 Right? 07:53.840 --> 07:58.430 And in other cases, using a flag can be pretty easy. 07:58.610 --> 08:00.630 It really depends on your choice. 08:01.130 --> 08:06.130 And since both the results are both the methods and to the same degree. 08:07.970 --> 08:11.550 So here will be checking whether it is magic. 08:11.750 --> 08:19.550 So as soon as we match read, the next thing is to check whether we have transmitted all the if not, 08:19.940 --> 08:21.860 we will transfer to the next day. 08:21.890 --> 08:24.680 So this is the street that will be doing that thing. 08:24.920 --> 08:32.690 So it will check whether all the data transmitted and if so, then it will again check whether you still 08:32.690 --> 08:34.920 want to transfer to a new data. 08:35.810 --> 08:40.360 Then it will again be done then for the data transmission. 08:40.370 --> 08:41.960 If it is if. 08:42.750 --> 08:50.610 All the data is not transmitted will again move back to send data that will basically transmit the new 08:51.420 --> 08:52.380 big data. 08:52.470 --> 08:59.370 So you have a buffer which will hold an entire data and then will probably increment the Bitcoin and 08:59.370 --> 09:01.320 then will transmit the next. 09:01.530 --> 09:10.380 So this is no simple solution that we've been able to create from this data frame that we are getting 09:10.380 --> 09:11.280 from other fishermen. 09:11.430 --> 09:14.990 OK, so start before start before the start. 09:14.990 --> 09:16.270 Days are ideal conditions. 09:16.500 --> 09:19.410 So for that, we look one street ready. 09:19.950 --> 09:23.280 So before we'll start, we'll be having an idea value of one. 09:23.290 --> 09:26.300 So it will be setting value as one. 09:26.730 --> 09:33.790 And if you press the switch, it will basically create a condition by pulling the line loop. 09:33.810 --> 09:42.210 So as you said, the switch will force me to explain low will also follow the data that we need to transmit 09:42.210 --> 09:46.950 on there and then we move on transmission of raw data. 09:47.730 --> 09:50.330 Then we transmit that one by one. 09:50.400 --> 09:51.450 And then finally. 09:52.630 --> 10:00.330 As soon as we transfer all the data, we basically, again, check whether the still wish to continue 10:00.580 --> 10:06.310 the transportation or whether a user do not want to continue on that transmission. 10:06.340 --> 10:11.200 OK, so this is how a simple flowchart will help us convey them in an easier way. 10:11.560 --> 10:17.890 So now what we'll do is we'll try to replicate this flowchart and an. 10:19.860 --> 10:27.620 OK, so we'll use this as a reference and then probably will be writing code in the window. 10:28.350 --> 10:36.960 OK, so here we'll be requiring a new regulator since will be frequently performing the automatic operation 10:37.170 --> 10:39.160 just to have an exact for. 10:39.570 --> 10:46.260 So along with the numeric library's building to use of unsane since will not be targeting getting in 10:46.300 --> 10:53.520 the same name, but will be requiring accountability just to keep track of the content to match and 10:53.520 --> 10:54.090 exactly. 10:54.090 --> 10:54.570 Derivs. 10:54.900 --> 10:59.220 So we'll probably be working you on an them. 10:59.300 --> 11:00.690 So it is always a good idea. 11:00.690 --> 11:08.120 Then when you have a new extended, you explicitly, explicitly specify whether you are working on Sindy 11:08.490 --> 11:08.760 and then. 11:09.500 --> 11:12.210 OK, so this too will be pretty new for us. 11:12.930 --> 11:21.150 And then from forgood itself you can get start is the switch order provision by which you can specify 11:21.150 --> 11:26.270 whether he want to start a new transmission or whether you want to continue the transmission. 11:26.310 --> 11:31.320 And the clock is a workload which will be used to synchronize an entire FSM. 11:31.320 --> 11:39.260 And then this is the that would be going out to the console for BCB. 11:40.140 --> 11:40.590 So. 11:41.680 --> 11:46.960 From here, you can guess all of them have a sizable single, but the oil belongs to. 11:46.990 --> 11:51.460 Since our data point that is have a sizable single bit. 11:51.480 --> 11:59.560 So basically belongs to a Citilink with no further will understand how it specifically differed itself 11:59.830 --> 12:01.090 from a parallel interface. 12:01.120 --> 12:10.520 Then we looked at and said, so let's just try to watch the clock for synchronization. 12:10.870 --> 12:14.200 So we will assume that will be operating on the. 12:15.940 --> 12:16.990 Bloodroot of. 12:19.490 --> 12:26.810 Board rate of four nine six zero zero, so which is the lowest birth rate, in fact, that we commonly 12:26.810 --> 12:33.470 used with, you know, let us assume that the board that I'm using is an nexus for the year, which 12:33.470 --> 12:41.820 have an on board frequency of hundred megahertz, which basically is a hundred, and then into the six 12:41.830 --> 12:42.140 rate. 12:42.410 --> 12:45.330 And I want the board rate of nineteen sixty two. 12:45.400 --> 12:51.470 So if you can just compute, this will result in two one zero four one six. 12:52.130 --> 13:00.770 So if you are using flag method, so whether you'll be keeping track of growth until it reaches the 13:00.770 --> 13:08.690 discount and then you will raise the black flag method, you'll be finding you required a variable that 13:08.690 --> 13:11.030 can at least hold the current value. 13:11.180 --> 13:19.610 This and if you are working on 10 km, will be requiring at least half of the for four o'clock metal 13:19.610 --> 13:26.040 for half of discount will be keeping our value high and then next block will be keeping it. 13:26.270 --> 13:33.920 So it'll be finding four o'clock metter Cotsakos adequate or half of that is required to come back to 13:34.460 --> 13:34.560 it. 13:34.780 --> 13:39.220 OK, so in this probably in this video will target on doing a flag Mitic. 13:40.780 --> 13:48.000 So let us suppose declared this was declared a signal and that is capable of holding this. 13:48.610 --> 13:57.760 OK, so it will have a tape of it and then it will range from zero to one zero four one seven. 13:57.760 --> 14:05.440 Pull-Back is always a good idea that you have one more call as the minimum contact is required for your 14:05.440 --> 14:07.680 process since you'll be performing in addition. 14:07.900 --> 14:14.950 So when we will last, the next deed will result in a count that is one zero four one seven. 14:14.980 --> 14:18.450 So your variable should be capable of holding back. 14:18.820 --> 14:27.190 OK, so whatever called you targeting Aggie's you declare a variable that have one count greater than 14:27.190 --> 14:28.840 the count that you are to make. 14:29.980 --> 14:37.410 And then the flag that will be required is in the disciples will just mean with us, like, OK. 14:37.640 --> 14:43.390 And since it is a single big flag, so we'll use a standard, it's for logic and a just initialize. 14:45.010 --> 14:45.270 OK. 14:46.800 --> 14:48.450 So let us start writing. 14:49.620 --> 14:51.850 A routine or an API for. 14:53.710 --> 15:03.520 Slower generation or basically this will be used to synchronize a body will name this as board. 15:06.760 --> 15:07.450 Read. 15:09.850 --> 15:13.360 Generation and then process. 15:13.450 --> 15:21.800 OK, so this will be Baudry generation process and will be making it sensitive to four o'clock. 15:21.810 --> 15:32.000 So we just heard the clock begin and then if rising without using a clock. 15:32.690 --> 15:36.250 OK, and now we tend to usually squeeze intends to do it. 15:36.260 --> 15:41.100 Doesn't matter whether you rate the case or lower case you idiot. 15:41.270 --> 15:51.530 OK, so if rising age of a clock then we know that is if counties count is less than one zero four one 15:51.530 --> 15:59.510 six, which is the count that we are targeting, then we will simply simply increment the phone. 16:00.880 --> 16:06.910 Now here, if we can observe, we are using an automatic operator to have an access to this operator. 16:06.920 --> 16:14.200 We'd like to have this ability like this should be in the bottom of our compiler. 16:14.600 --> 16:17.870 And since we are targeting or using an unsigned number. 16:17.880 --> 16:21.930 So this second library is our second package is also mandated. 16:22.110 --> 16:22.400 Right. 16:22.850 --> 16:30.110 And the flag will have a flag, will have a value of zero else. 16:30.110 --> 16:38.420 And as soon as it reaches or goes about that count, you'll be finding flag will be equal. 16:39.740 --> 16:45.230 OK, so this will indicate that now we can transmit our new beat. 16:45.620 --> 16:53.930 So this indicates that this is the maximum before we have a for a single vote to hold its data. 16:53.960 --> 17:01.970 And as soon as this spirit overflows, we can actually transfer to the next and allow the desk to reuse 17:01.970 --> 17:02.550 discount. 17:02.630 --> 17:04.490 But it will begin again. 17:04.490 --> 17:05.420 We could see it. 17:05.690 --> 17:13.300 OK, so this will basically allow us to use our outlook for transmission from next data on here. 17:13.400 --> 17:17.170 This is our first step and then this second. 17:17.670 --> 17:26.810 So this completes that process of translation of a clock or basically hand ticking signal that will 17:26.810 --> 17:30.530 handle all the processing related to a broader agenda. 17:30.860 --> 17:35.420 OK, so we have started with the board, the dedicated board that we wish to conduct. 17:35.810 --> 17:40.880 We have our board frequency or the development board that you are using. 17:42.980 --> 17:47.780 And then we basically divided it with the board and then we get certain. 17:48.350 --> 17:55.430 OK, so we need to wait till the counter to that value and then we can be done. 17:56.520 --> 18:02.220 Now, this process will continuously go on independent of what the process does. 18:02.570 --> 18:07.760 So we need to further modify this process as we as we like and data. 18:09.070 --> 18:17.990 Data transmission rate, so let's just start getting data trance nation. 18:20.200 --> 18:20.840 Crisis. 18:22.480 --> 18:25.830 So let's just start writing this process. 18:31.440 --> 18:39.600 Now, the difference between the cloth that you use and the flag method is if you are targeting a flag 18:39.600 --> 18:45.840 method, you'll be operating that would the processes, that is the slower growth generation order synchronizing 18:45.840 --> 18:50.490 process and the defensive process would operate on a global clock. 18:50.670 --> 18:52.650 That is an ongoing problem that we have. 18:52.940 --> 18:59.730 But target on enforcement there will be finding that you are slower or the synchronization process or 18:59.730 --> 19:05.160 the slower growth process will operate at 10 o'clock as the data transmission process will actually 19:05.160 --> 19:06.300 operate slower. 19:06.570 --> 19:08.490 So this is a primary difference activity. 19:09.630 --> 19:14.250 So as we take an example with that, we'll be understanding that materials. 19:15.970 --> 19:26.890 OK, I know the very first thing that we do is we will basically specify some of the states that that 19:26.890 --> 19:35.440 can be easily distinguishable and then help us to actually achieve an entire implementation of our future. 19:35.530 --> 19:38.920 OK, again, we'll start with the rising age of the clock. 19:40.860 --> 19:42.580 OK, and then. 19:43.810 --> 19:53.950 Then let us now work on in case we haven't declared anything at the state, it probably will declare 19:53.950 --> 19:54.820 it very soon. 19:55.340 --> 19:57.070 Case status. 19:57.700 --> 20:05.560 And then probably since we have started a statement, we learned a statement will and if and then we'll 20:05.560 --> 20:06.910 end the process. 20:08.410 --> 20:10.870 OK, so this is a typical damply. 20:10.900 --> 20:12.700 So whatever we have serger, we have haven't. 20:16.280 --> 20:17.800 Now, here we can actually. 20:19.100 --> 20:22.970 Distinguish the variable required for different process. 20:23.030 --> 20:29.840 OK, so here we can name it as a signal for slower. 20:31.460 --> 20:35.730 The order basically barred three. 20:37.720 --> 20:39.360 Kintisch think. 20:41.810 --> 20:46.310 So this is the other variables which are required for a broad agenda. 20:46.710 --> 20:56.350 Now we can add two more hyphens and then we can specify a signal for data transmission. 20:59.020 --> 21:06.800 And they decided to move here very first thing is we need to have a seat. 21:07.750 --> 21:15.940 And right now I can guess that there must be a ready state, there must be a single state, and then 21:15.940 --> 21:19.940 there must be something called in to check whether all the data is transferred. 21:20.410 --> 21:25.980 So with this difficult idea, let us know it is always easy to increase or decrease the number of seats. 21:25.980 --> 21:32.320 So just 10 or so from the chart itself, I can guess I could see my nudity. 21:32.320 --> 21:42.700 So let's say a little declared a user defined tape and let us numata signal tape or in fact, instead 21:42.700 --> 21:49.030 of signal tape, we can mean with that tape and then you can specify what will be inside that tape. 21:49.060 --> 21:50.870 So one of the states will be ready. 21:51.610 --> 21:57.100 There will be send data and then the last stage will be. 21:59.770 --> 22:09.980 Let's just name it does Congress and then you declare a variable state which will basically have this 22:09.980 --> 22:10.420 type of. 22:10.670 --> 22:19.250 So when we declared when we use that key state to so the values are very same, which are very easy 22:19.250 --> 22:19.800 to understand. 22:19.820 --> 22:23.880 OK, and the initial value for the state will be like. 22:25.310 --> 22:30.200 So this does two lines basically remove data that we are getting right now. 22:30.390 --> 22:36.450 OK, so now when we are in when we are in, ready. 22:37.070 --> 22:40.940 So what we need to do is here we will basically check. 22:42.160 --> 22:42.730 Wethered. 22:44.280 --> 22:51.600 Whether they user want to transmit it or whether you just want to simply sit ID, right. 22:51.930 --> 23:05.310 So if if stutt focus is the input from that user can specify whether they need to transmit to whatever 23:05.340 --> 23:07.620 it wants to set idea. 23:07.920 --> 23:15.790 So starting with two one, OK, then starting with two one, then we need to move. 23:15.850 --> 23:27.750 The next else is we need to enter this these great to let us let us just use if starting to zero then 23:27.760 --> 23:29.430 speed will be good. 23:29.940 --> 23:32.330 This indicate that user want to see didit. 23:32.840 --> 23:38.550 It will be simply rolling through the streets and as and. 23:39.470 --> 23:43.440 The state will be with us to send data. 23:44.280 --> 23:50.950 This is the next thing that we have and what you do and next, it is always a choice that if we get 23:51.480 --> 23:57.500 the data in, in and of itself so that you will be feasting a classic. 23:57.610 --> 24:06.500 OK, so let's assume that the data is an individual which consists which contain all the data that we 24:06.510 --> 24:07.100 can transmit. 24:08.130 --> 24:13.680 So let us assume that we want to transmit a capital E.. 24:13.980 --> 24:15.990 OK, so whose value is 40? 24:16.680 --> 24:20.610 OK, so we'll start with the zero says this is our stock condition. 24:20.850 --> 24:26.990 So from here also you can guess that for the stock condition, the value on the line should be zero. 24:27.750 --> 24:30.210 And then we want to transmit reader. 24:30.740 --> 24:38.610 So we have 41, which is an hexadecimal value for the uppercase E and the kind of data that we have 24:38.610 --> 24:44.330 in an it is a nine percent since forty one is a multiple value. 24:44.340 --> 24:50.580 So we need to attack the Valco and along with that and X, which indicates that it is in hexadecimal 24:50.580 --> 24:50.860 value. 24:51.390 --> 24:57.840 And finally, a stock condition is sort of is of logic. 24:58.080 --> 24:58.500 Correct. 24:58.530 --> 25:04.290 So here will give you the single best single code and then one final numbers. 25:04.660 --> 25:07.290 OK, so this will be added value then. 25:07.980 --> 25:09.440 Forty one and finally. 25:09.910 --> 25:12.750 OK, and then we can add some. 25:14.480 --> 25:17.260 Parenthesis to simplify the thing. 25:17.360 --> 25:19.670 OK, so this is a pretty important step. 25:19.720 --> 25:28.610 So before you actually send data, we like to do deal that you have do the data and then you basically 25:28.610 --> 25:30.040 wish to transfer data here. 25:30.050 --> 25:36.200 You can use another state where you can load your data and then you can proceed to assign data. 25:36.470 --> 25:38.410 So that will be easy to understand. 25:38.840 --> 25:41.660 But I prefer to go with this. 25:41.990 --> 25:42.240 Right. 25:42.320 --> 25:42.980 And then. 25:45.400 --> 25:53.140 Since we have started and will basically and you know, here we are getting Arabs into haven't declared 25:53.500 --> 25:54.010 anything. 25:55.090 --> 26:02.470 OK, so this is having a series of ten tricks for this single bit for this single group and for this 26:02.470 --> 26:05.800 stupid decimal number three. 26:06.190 --> 26:08.410 So this is all required. 26:09.220 --> 26:13.780 So let's just a clear signal de de de. 26:15.490 --> 26:25.700 And then standard and this whole logic on this Victor and nine down to see, which indicates a Democrat 26:26.050 --> 26:26.380 like. 26:29.330 --> 26:37.440 So now this will be decision will be gone and will probably be completed at four straight. 26:37.460 --> 26:42.200 So just a few blank spaces, so it will be very easy to understand. 26:42.650 --> 26:43.610 OK, so ready. 26:43.990 --> 26:44.530 No, no. 26:44.540 --> 26:48.580 We probably have included disrobing also inside. 26:49.700 --> 26:55.880 OK, so in that district we are checking whether users have pressed stocks which are not. 26:55.910 --> 27:02.930 So if it is not, this will be waiting in under the state, will remain as ready as states will move 27:02.930 --> 27:07.390 to ascended it before going to the state. 27:07.430 --> 27:12.560 We have actually now let us just move on to Sandy district rate. 27:12.590 --> 27:16.170 So when we have the same data, right. 27:16.430 --> 27:24.480 So here what we want is whatever the spin or whatever the spin that we've been allocated for transmitting 27:24.920 --> 27:32.420 from an consumers will be transporting a single bit of this data and. 27:33.560 --> 27:38.400 Then we'll probably check whether all the data is transferred. 27:38.420 --> 27:42.770 You're doing great, so let us just just saying our physics. 27:43.940 --> 27:46.210 OK, so DS 10. 27:48.340 --> 27:57.760 Will be equal to the X data, which is a 10 bit variable, and whose and less value will be transferred, 27:57.780 --> 27:58.180 correct. 27:58.210 --> 27:59.380 So who's eligible? 27:59.380 --> 28:03.050 Who can be easily transmitted by using certain variables? 28:03.100 --> 28:07.450 Let's assume that we are using nobody will become. 28:08.630 --> 28:11.030 Which is having a value of seating. 28:11.450 --> 28:19.720 So this reposing that the extended does, you or the eldest daughter, Lakeway, will also increment 28:20.150 --> 28:20.800 Mittagong. 28:22.120 --> 28:29.840 By one, Bitcoin by one, and then we can move on to the next. 28:30.460 --> 28:37.450 So there will be checking whether we actually do the count of ten, which is the maximum number of data 28:37.480 --> 28:40.020 that can be transmitted in a single transaction. 28:40.540 --> 28:48.190 So we rename that status within that discount, but they will be using that. 28:49.060 --> 28:53.570 OK, so this completes our second seat now to the extent we haven't declared. 28:53.590 --> 29:02.890 So we just go in here wherever we have our signals for our data transmission and then will declare signal. 29:04.310 --> 29:06.160 Deakes Demps. 29:07.310 --> 29:14.930 And then it will be having a of single district, so we will be having this single bit and one more 29:14.930 --> 29:24.320 thing required is a contest to track the values of the big that is being transmitted to signal Bitcoin 29:25.160 --> 29:27.690 and then integer range. 29:27.740 --> 29:31.150 Now we know that the maximum value that we are targeting is a 10. 29:31.850 --> 29:35.970 They, too, will be using zero 11 as our age. 29:36.410 --> 29:39.200 They and then will be probably initialized with. 29:39.860 --> 29:45.380 So this will basically start the value of the controversy and then. 29:46.380 --> 29:51.790 Then we move on to check your account a bit. 29:52.370 --> 29:57.080 OK, so what we'll be doing here is first thing that we do is Fedor. 29:59.290 --> 30:06.180 Whether the the the waiting period that we have or the minimum period that we need to order minimum 30:06.250 --> 30:13.150 growth cycle, that we need to wait before we can proceed with that is being completed or not. 30:13.180 --> 30:14.800 So how do we know that if. 30:15.970 --> 30:25.270 If he had redeclared a flex or if flag is one, flag is one, so this will be our first check, that 30:25.270 --> 30:31.270 is this will signify that this completes a minimum period required for the transmission of a single 30:31.540 --> 30:31.870 right. 30:32.680 --> 30:42.010 Then we can check, then we can check whether or a Bitcoin Bitcoin, which is a counter variable that 30:42.010 --> 30:46.690 we are using to keep track of the number of Bendat somebody. 30:47.010 --> 30:50.020 OK, so this probably is a bit confusing from. 30:51.250 --> 30:52.720 But then become a local. 30:52.780 --> 31:00.250 So this is confusing, I would hit on here instead of calling, but we can make this change right. 31:00.820 --> 31:03.210 This will basically reduce the confusion. 31:03.250 --> 31:04.780 So this would be chick. 31:06.280 --> 31:13.330 And this state represent basically the state in which we'll be counting how many we've been transferred 31:13.350 --> 31:14.210 to, right. 31:14.680 --> 31:21.330 OK, so if Bitcoin is less than less than 10 cents, a 029 will indicate that we will. 31:21.340 --> 31:22.120 Because we do. 31:22.510 --> 31:25.330 Then then then OK. 31:25.410 --> 31:27.160 So if this two conditions are met. 31:28.210 --> 31:37.350 So if a flag is one and a flag is one, then you check if bitcoin is less than 10, if that is the case, 31:37.360 --> 31:43.780 if that is the case, then we transmit the next time since we already incremented Bitcoin, potentially 31:43.780 --> 31:45.800 not incremental to Bitcoin by one. 31:46.420 --> 31:47.950 OK, so we'll just. 31:50.000 --> 32:01.030 State we will send you to so this will basically turn to the next data rate ends and here else ends. 32:02.400 --> 32:09.120 L's indicate that we've been able to successfully complete the transformation of diet and sort of stream, 32:09.660 --> 32:15.150 then we'll simply jump into any state which will check whether you want to continue a transformation 32:15.150 --> 32:19.500 or whether he or she wants to go after he or she wish to. 32:21.320 --> 32:25.850 Complete the transmission or stop the transmission, OK, so it will simply be. 32:29.260 --> 32:35.290 And if and do and if we will be declaring all of it ls ls is the. 32:35.520 --> 32:42.670 So if let us assume that we would use in the checkbook and our flag is not one, so we want to read 32:42.700 --> 32:43.880 in this state. 32:45.370 --> 32:47.080 So this is the minimum buffer period. 32:47.080 --> 32:52.950 We get to redo it, hear end as will simply be in the same state. 32:52.990 --> 32:53.260 OK. 32:53.290 --> 32:54.490 That is a check. 32:56.240 --> 32:56.460 Right. 32:57.250 --> 33:00.280 And finally, no we can not force. 33:02.160 --> 33:10.710 OK, so this completer this two conditions, so we check whether flaggers one and then again. 33:11.830 --> 33:17.590 We check whether we are able to transmit all the data transmitted or not, and then accordingly we make 33:17.590 --> 33:19.720 our jumps through the subsequent steps. 33:20.320 --> 33:26.980 So finally, for all the families, always the idea that you will add and this since this will eliminate 33:27.220 --> 33:28.360 the creation of. 33:31.380 --> 33:39.200 Creation of a Lecia, so so when others when this that will represent their default condition, so state 33:39.720 --> 33:45.570 will basically be ready, which is our default rate and since we already and get out of. 33:45.820 --> 33:47.990 So we need not have indicted. 33:49.640 --> 33:58.810 So this completes or an article or an future that we have implemented from a level and two of the right 33:58.880 --> 34:06.920 to know, since we are getting an indication so this indicates that we haven't completed or we haven't. 34:07.850 --> 34:09.990 Committed any syntax. 34:10.250 --> 34:19.310 OK, so what I'll do is I simply take this back to a word that will perform a simulation, so if simulation 34:19.310 --> 34:25.380 goes fine, I will basically do a fourth mapping and then finally download our on. 34:29.410 --> 34:37.030 One important thing before we actually cross the we is if you observe due process, the they do not 34:37.030 --> 34:39.870 have any any synchronization between them. 34:40.390 --> 34:45.700 So only the data that is going is the flag, the. 34:47.500 --> 34:57.550 But let us assume that here we are not checking whether we are in any state or in a sense that we are 34:57.550 --> 35:03.580 in that state, then also the founder or since this process is sensitive to block it will continue. 35:04.450 --> 35:09.530 And let us assume that just before a single Psychon, we reach to a registry. 35:09.790 --> 35:17.680 So that will indicate within a single cycle, this flag will be one within a single cycle will be will 35:17.680 --> 35:20.110 be getting a valid data, which we do not for. 35:20.440 --> 35:25.030 So just to synchronize this due process, we actually need to modify this. 35:25.030 --> 35:25.520 Correct. 35:25.960 --> 35:34.330 So if everything is OK, then then let us assume that we want that discussion to begin when we move 35:34.330 --> 35:37.210 from the registry to a sense to. 35:37.240 --> 35:43.730 So whenever we are in the same state, we want that culture back in record time. 35:43.750 --> 35:45.900 It should begin to indicate an exact. 35:46.340 --> 35:47.890 So let us assume that if. 35:48.850 --> 35:57.730 If the state was to, but in any case, a state was too ready, then, then then then what we'll be 35:57.730 --> 36:03.010 doing is will be continuously making zero else else. 36:03.010 --> 36:06.460 No, we and this entire thing will hear so elusive. 36:07.840 --> 36:11.860 Then this value will be flag else Flagler's. 36:14.440 --> 36:17.210 So this will synchronize with of us. 36:17.410 --> 36:24.970 OK, so whenever we are ready, even though if we consider this process, all of this process will hear 36:24.970 --> 36:25.900 me come to you. 36:26.180 --> 36:33.110 And when here we, when we are in the ready will basically can add default. 36:33.190 --> 36:43.750 The value of these statistics data to the extent is the value that will be attaching to the slate that 36:43.750 --> 36:45.190 will be having an added value. 36:46.300 --> 36:50.680 So whenever we aren't ready to extend, we'll have an ideal value of one. 36:50.950 --> 36:58.630 And yet whenever we are in a registry, as soon as we move to a next year, then we are going to be 36:58.630 --> 37:04.150 stuck and that we will be achieving an exact count or the behavior that we rate. 37:04.180 --> 37:07.290 So this completes and then at the end, probably both. 37:07.300 --> 37:08.970 The pluses are quite synchronising. 37:08.980 --> 37:11.440 So we'll perform a simulation once. 37:11.440 --> 37:17.960 And if it matches what we are expecting out of this will basically download our code on in the speech. 37:20.080 --> 37:23.080 OK, so let's just click on Run Simulation. 37:23.320 --> 37:25.120 OK, so then in simulation. 37:27.470 --> 37:34.550 Here we are not writing it, does it, since we just need to apply stimulus to a clock and a starting 37:34.550 --> 37:37.520 point, which is pretty easy instead of writing. 37:38.960 --> 37:45.800 So whenever we need to frequently change it, like testing in Wal-Mart or Ice, Christine Tiffy's or 37:45.800 --> 37:54.340 an and so on and so forth, we can to actually generate random stimulus rate. 37:54.380 --> 38:02.450 So in this simple scenario, simply for Starkloff, OK, so one to zero, let's let us stick to the 38:02.740 --> 38:06.300 put it in a nanosecond and we'll make our stock values. 38:07.190 --> 38:13.910 So this will indicate that you want to continue send submissions so it'll be getting an infinitely limited 38:13.910 --> 38:17.240 just run out of food and then try to figure it out. 38:17.300 --> 38:21.600 So we'll be finding things to match the rate of nine six zero zero. 38:21.620 --> 38:28.930 We need to read for a long time in this scenario instead of using this option as an oven. 38:28.940 --> 38:31.700 Four hundred microseconds, we need to prosecute that or not. 38:32.060 --> 38:38.840 So we'll simply go with an unknown and now we'll be finding that it automatically brings. 38:40.470 --> 38:45.660 Pointed to this position, which indicated that there might be something that is going wrong. 38:46.590 --> 38:54.130 So here you'll be finding that index 10 out of bond nine down to zero. 38:54.150 --> 38:58.950 So de de de can have a maxi's of nine down to zero, which is a ten. 38:58.950 --> 39:00.240 But that we have declared. 39:00.660 --> 39:01.500 And he is. 39:02.530 --> 39:04.060 It is going beyond that. 39:04.090 --> 39:06.160 OK, so that is what it is complete. 39:06.550 --> 39:07.720 OK, so. 39:09.060 --> 39:11.370 Here, what we can do, actually, is. 39:16.580 --> 39:25.120 What what we can do is if we can just analyze this to see to be finding it is continuously going up. 39:25.400 --> 39:30.770 So as soon as it reaches a dead end, that's another dirigiste of this value. 39:30.920 --> 39:38.580 What we can do is whenever we move on to Elstein, we should have now reached to a value of ten will 39:39.160 --> 39:42.000 be Bitcoin equals Z. 39:42.350 --> 39:45.520 OK, so this is what we haven't added enough. 39:45.540 --> 39:50.000 You know, we'll just see our design and we just simply launch our simulation. 39:50.030 --> 39:50.320 Right. 39:51.670 --> 39:54.300 Let's see whether it is working fine or not. 39:54.320 --> 39:56.100 So this is how you debug your work. 39:56.220 --> 40:03.770 So first we will be finding that a new syntax error, but then you'll be finding some of them are logical 40:03.770 --> 40:07.940 error like this and then for the political reform. 40:07.970 --> 40:09.940 So this is how you get a good look. 40:09.980 --> 40:12.740 So, again, we'll be using a full scale option. 40:13.720 --> 40:21.460 And, of course, concern option no, let us just try to run on hold for the duration. 40:22.060 --> 40:24.080 OK, now I know we can cause article. 40:24.370 --> 40:24.620 Great. 40:25.620 --> 40:33.180 Now, if we can just fit dad and dad, we form a single window, it would be finding the flag is actually 40:33.210 --> 40:35.630 used to match it, so. 40:40.070 --> 40:45.530 So here we have our flag and let us just try to target our. 40:49.760 --> 40:58.460 And then this is the very conservative look, here it is, so we're just doing a bit, OK, so we'll 40:58.460 --> 40:59.910 be finding that. 41:01.390 --> 41:07.690 The first value in the first cycle that we are transporting is zero, which is a stock condition, then 41:07.690 --> 41:13.610 we are expecting some series of data and then finally we have our condition, which is in what? 41:14.860 --> 41:17.890 So this is a present that I guess everything is going fine. 41:18.910 --> 41:24.570 The only problem is the actual fact that we have used in an entity is not being connected to anything. 41:24.580 --> 41:27.820 So that is the reason it is showing a default value. 41:28.540 --> 41:30.760 So probably can go into a code. 41:30.940 --> 41:40.270 And the last line that you can that is close to the temp variable, which is a single variable which 41:40.270 --> 41:42.220 we have used for the x ray. 41:42.700 --> 41:44.070 So just see you out of code. 41:44.080 --> 41:49.470 We look in the simulation and let's see whether we are getting the one doing Deakes. 41:51.120 --> 41:53.370 So, again, we'll be using a false clock. 41:54.910 --> 42:01.220 OK, and what a stunt will be using a false constant to just try to run out of food. 42:02.780 --> 42:12.230 For some big duration Will Pausa simulation, and then we'll probably all be finding the to haven't 42:12.230 --> 42:17.450 exactly the same which we have, we'll get to this completely out in time for. 42:17.870 --> 42:21.260 The next thing is you go to run synthesis. 42:21.300 --> 42:29.570 OK, so this will basically convert your angel food into the produce, which can be downloaded on. 42:29.570 --> 42:34.070 And this will take a bit of time to complete a synthesis. 42:34.280 --> 42:41.900 Also, after the synthesis you get in a region where you can do a new plan so that you can specify that 42:41.900 --> 42:49.430 you can connect a stock where you can connect lock and where you can connect to the inside and have 42:49.430 --> 42:50.480 only three groups. 42:51.440 --> 43:01.200 So after synthesis, you'll be getting the option whereby you can specify the exact eye open on the 43:01.280 --> 43:02.680 connecting this tree. 43:04.040 --> 43:07.800 So we'll just simply open our synthesis design. 43:08.390 --> 43:14.600 So this will give us a device view as well as our planning where you can actually. 43:15.620 --> 43:19.050 And put the exact pin number of an. 43:20.860 --> 43:22.460 For a specific skill output. 43:22.600 --> 43:29.560 OK, so here you have our scalable to be finding that are three or four o'clock on a nexus for yet I 43:29.560 --> 43:32.330 have been numbered as 80. 43:32.380 --> 43:36.720 So I'll simply add that for a start I'll be using a switch. 43:36.730 --> 43:41.680 So for the Switchy helping them G 15 and then 43:44.410 --> 43:54.130 we need to actually go to the station and then the pin that I found or for transmitting the data and 43:54.130 --> 43:56.420 then it is always a good idea that you change. 43:57.760 --> 44:03.790 So we see more thirty three the level that we'll be using, then we'll simply see this entire quantity 44:05.140 --> 44:07.460 and will give a good name to for. 44:08.860 --> 44:11.260 Constrained fight, so we'll just need to stop. 44:12.060 --> 44:15.740 Just click, OK, and then you can proceed with transition or forward. 44:16.320 --> 44:23.150 OK, so we haven't utilized any of the implementation strategies since we just went through an application. 44:23.160 --> 44:29.810 We need not one to optimize output, but in an application that you are consuming a lot of resources, 44:29.820 --> 44:36.480 it is always a good idea that you also include some of the implementation strategies in your report 44:37.020 --> 44:39.570 which can be held to use your. 44:40.470 --> 44:46.070 Amount of area that you are consuming on, it can also be used to reduce poverty consumption. 44:52.860 --> 44:55.470 So our bid generation is successful. 44:56.040 --> 45:02.780 So what we can do is we can go to one target and then we can do great. 45:02.950 --> 45:06.870 So this will provide us an option to go with our device. 45:07.310 --> 45:14.300 OK, so before programming, in fact, we can actually set up our system. 45:14.950 --> 45:22.950 So here I'm using a data to analyze the data that we are transmitting and we already know that the value 45:22.950 --> 45:27.570 that we have inputted is a constant 41, which is a value for the capital. 45:28.020 --> 45:32.430 OK, so I have my work connected to this. 45:34.200 --> 45:40.650 Basically signify that we are reading the data from a competition, we can program our device program 45:40.650 --> 45:48.270 device and then decide, OK, so no, I haven't turned on my switch. 45:48.930 --> 45:55.080 So as soon as I turn on message and be finding it continuously and the value of a computer, which is 45:55.080 --> 45:59.850 what we've been programmed on, you are correct. 45:59.880 --> 46:07.410 So this is how you can implement a simple interface to transmit the data between two nodes at the rate 46:07.410 --> 46:08.750 that has been specified by.