1 00:00:00,060 --> 00:00:05,790 So now we'll discuss what the different reporting mechanism that we have with this when we consider 2 00:00:06,060 --> 00:00:13,500 sending a at concentrate, so to demonstrate we will utilize again the same hardware design that we 3 00:00:13,500 --> 00:00:18,060 utilized to verify that the toolchain is successfully configured. 4 00:00:18,450 --> 00:00:23,940 So we have a micro place, which is configured to have a local memory of 128GB. 5 00:00:24,390 --> 00:00:29,730 And then you work like Typekit because utilizing it will be sending the reader to up until the rest 6 00:00:29,730 --> 00:00:31,290 of the things-I as it is. 7 00:00:31,320 --> 00:00:36,660 OK, so the clock is connected to the assist dropping and reads it is again connected to ready for a 8 00:00:36,700 --> 00:00:37,280 recipient. 9 00:00:37,350 --> 00:00:37,620 Right? 10 00:00:38,100 --> 00:00:40,950 And we also invoke the Halloway. 11 00:00:41,370 --> 00:00:49,030 Right now we have a three situation which you could find frequently when you are designing an application. 12 00:00:49,080 --> 00:00:53,310 OK, so you want to send the constant string on to a concert. 13 00:00:53,550 --> 00:00:59,530 So this include, for example, you have a paper and you read a function to initialize the peripheral 14 00:00:59,530 --> 00:01:02,220 to whether initialization is successful or not. 15 00:01:02,830 --> 00:01:07,130 Okay, so this represents the constant string that we want to send to a user, right? 16 00:01:07,140 --> 00:01:14,190 So this is one of the situation that other situation that we have is to debug the value of a variable 17 00:01:14,280 --> 00:01:14,520 rate. 18 00:01:14,520 --> 00:01:21,930 So you handle this situation now variable could take of 6.2 value, or it could also take a the rate. 19 00:01:21,930 --> 00:01:26,160 So we have a three situations which you frequently find out great. 20 00:01:26,400 --> 00:01:34,200 So either it may be a constant that we want to send to the console, or it may be fixed by an integer 21 00:01:34,200 --> 00:01:37,620 value that we want to send to a user our floating point, right? 22 00:01:38,250 --> 00:01:44,520 So in all the three cases, we'll be profiling the three reporting mechanism that we have to either 23 00:01:44,850 --> 00:01:47,240 print or print or print, right? 24 00:01:47,580 --> 00:01:54,940 So whenever you have that, is you a requirement to send the constant string right that gives you? 25 00:01:55,150 --> 00:01:57,920 We utilize first upgrade, right? 26 00:01:57,930 --> 00:02:06,550 So brain function and then we will just be mentioning that this is a constant string and along with 27 00:02:06,550 --> 00:02:07,650 the new line character. 28 00:02:08,400 --> 00:02:14,030 So that this we will just be receiving our code and building up our entire core right. 29 00:02:14,040 --> 00:02:18,900 So this will generate and will fight which we will be sending on tokens. 30 00:02:18,900 --> 00:02:21,150 And so I've already collected the. 31 00:02:22,200 --> 00:02:23,490 Instigator of to. 32 00:02:23,910 --> 00:02:27,120 Six, OK, which works at nine six zero zero. 33 00:02:27,510 --> 00:02:33,260 So let it just go ahead and try to execute our application to run this launch on hard, right? 34 00:02:34,480 --> 00:02:38,950 So now you could clearly be able to send a constant stream utilizing. 35 00:02:39,700 --> 00:02:45,590 And when you go to the a sticky day, you have an application folder. 36 00:02:45,610 --> 00:02:50,320 So I have named my application as I look and inside the debug, you see nearly five. 37 00:02:50,600 --> 00:02:55,560 So this represents executable file size, which will be utilizing for profiling. 38 00:02:55,570 --> 00:03:02,770 So when we use a print and saying the constant stream, two of them, so the size of your file is 82. 39 00:03:03,100 --> 00:03:05,380 So that is what we want to mention with you. 40 00:03:05,380 --> 00:03:13,060 So with print and constant stream, we get the size of 80 to keep right now will modify our code and 41 00:03:13,060 --> 00:03:14,760 utilize print, right? 42 00:03:15,130 --> 00:03:19,150 So this is the second we all conveying the message to any user. 43 00:03:19,160 --> 00:03:26,580 So let's just see what works and then again, relaunch the session on and hide it right? 44 00:03:26,590 --> 00:03:29,950 So we should be able to see the similar result. 45 00:03:29,970 --> 00:03:33,940 What we are getting in the previous case, we do able to see a constant stream. 46 00:03:34,240 --> 00:03:40,630 And now if you analyze the debug folder to the sides of any file is one one one key, right? 47 00:03:40,630 --> 00:03:45,040 So which is greater than what we are getting in the case of, right? 48 00:03:45,060 --> 00:03:50,830 So one one, one last week that we have it is utilizing a deliberate effort. 49 00:03:50,830 --> 00:03:55,060 So we'll just be adding that sleeping, therefore here will be saving the. 50 00:03:55,430 --> 00:03:59,230 And again, we will be relaunching I debug session. 51 00:03:59,240 --> 00:04:03,000 So right click on a full brightness launch on high, right? 52 00:04:03,670 --> 00:04:05,980 So here also we are expecting the same result. 53 00:04:06,010 --> 00:04:12,040 And then if you analyze any fight, so it is giving us around A.D. 70, right? 54 00:04:12,520 --> 00:04:17,000 So all the three mechanism supports sending the constants. 55 00:04:17,000 --> 00:04:17,860 Do you want to consult? 56 00:04:18,070 --> 00:04:22,650 And you can clearly see that print is consuming the least amount of memory, right? 57 00:04:22,660 --> 00:04:28,540 So this helps to build a complex application because when we consider an embedded system, so we have 58 00:04:28,540 --> 00:04:31,940 a limited amount of memory which is available to us. 59 00:04:32,120 --> 00:04:41,250 So we always try to use an API which consumes less amount of memory so that as we modifier hardware 60 00:04:41,260 --> 00:04:49,510 to include a complex paper, we could have a spare amount of memory for our building and application 61 00:04:49,510 --> 00:04:50,540 with that benefit. 62 00:04:50,840 --> 00:04:56,920 So whenever you have a situation to send the constant stream the most efficient way to use a print, 63 00:04:57,040 --> 00:04:57,340 right? 64 00:04:57,580 --> 00:05:00,090 Are you good prosecutors helping to write? 65 00:05:00,400 --> 00:05:07,780 The next scenario that you could probably find is sending a variable value that is just declared one 66 00:05:07,780 --> 00:05:10,630 fixed point where you call for an integer type. 67 00:05:11,740 --> 00:05:12,130 OK. 68 00:05:12,430 --> 00:05:19,330 And we'll just be naming this data and the value that you have is to right now, our agenda is to send 69 00:05:19,330 --> 00:05:22,750 this value utilizing the three mechanism that we have, right? 70 00:05:22,770 --> 00:05:25,960 So again, we start with the brain statement, so OK. 71 00:05:26,350 --> 00:05:36,190 And then we will be adding a value, just try to format specified to the 0d and variable, which is 72 00:05:36,190 --> 00:05:37,750 holding the value of this, right? 73 00:05:37,750 --> 00:05:44,680 So if you add this code, you could clearly see we get an error indicating that there are more argument 74 00:05:44,680 --> 00:05:47,770 than is expecting to print. 75 00:05:47,770 --> 00:05:54,070 Simply do not support sending the values of available on open source, so you could not add any argument 76 00:05:54,100 --> 00:05:55,910 OK for printing the variable value. 77 00:05:55,930 --> 00:06:02,110 So here in the first case, if you consider sending variable values on your console utilizing print, 78 00:06:02,530 --> 00:06:04,440 it is simply not applicable, right? 79 00:06:05,290 --> 00:06:12,220 The next mechanism that we have is a print app, so let it just include printed CEVA code and allow 80 00:06:12,220 --> 00:06:19,570 the code to build up OK, and then right click Run as launch on superintending support and variable 81 00:06:19,780 --> 00:06:20,380 argument. 82 00:06:20,380 --> 00:06:27,350 So you could bring the values of the label and you could see that we could bring the fixed point number. 83 00:06:27,460 --> 00:06:33,910 OK of integer type, whose value is real on the concept and the size that we are getting, is it down 84 00:06:33,910 --> 00:06:34,810 to fifty nine? 85 00:06:35,260 --> 00:06:35,530 Right. 86 00:06:35,540 --> 00:06:42,790 So we'll just be writing with the print we are able to send the value and the size of any file is around 87 00:06:42,790 --> 00:06:43,740 250 90. 88 00:06:44,560 --> 00:06:51,370 Next, we will consider taking that so easily printed to allow us to send a fixed point number on tokens. 89 00:06:51,520 --> 00:06:56,980 So we'll just modify our code and relaunch debug session, right? 90 00:06:57,370 --> 00:07:01,660 So let me just go ahead and try to execute the code so you could clearly see we are gaining. 91 00:07:01,660 --> 00:07:08,950 But to see the value to it as we are getting in the previous case, just need to add a new line character. 92 00:07:09,130 --> 00:07:14,220 OK, so that we could see the value printed in the next slide. 93 00:07:14,240 --> 00:07:18,340 So let's just go ahead and again, try to relaunch the feedback session. 94 00:07:18,430 --> 00:07:24,400 OK, and now you could clearly see that we are able to get the result what we are getting in a previous 95 00:07:24,790 --> 00:07:26,140 its value and to it. 96 00:07:26,660 --> 00:07:31,630 In this case, though, yeah, let's say that we are getting is around eighty seven kb, which is much 97 00:07:32,020 --> 00:07:35,380 less that's compared to the print state. 98 00:07:35,440 --> 00:07:43,180 So whenever you are in a situation where you want to send the variable value, OK, specifically a fixed 99 00:07:43,180 --> 00:07:48,040 point value, or you can so that the preferred method is to print, right? 100 00:07:48,310 --> 00:07:52,720 Now remember, I sprint do not support sending the variable value. 101 00:07:52,720 --> 00:07:56,740 We are not allowed to utilize it, sending the variable values on a console. 102 00:07:56,770 --> 00:08:03,450 Similarly, select Braindead do not support sending the floating point values on to open, right? 103 00:08:03,460 --> 00:08:06,160 So we'll just be demonstrating this with an example again. 104 00:08:06,580 --> 00:08:06,980 Great. 105 00:08:07,090 --> 00:08:13,060 Do not support sending the variable values on a console, so we could not simply saying the floating 106 00:08:13,060 --> 00:08:15,460 point number utilizing print on the console. 107 00:08:15,500 --> 00:08:15,730 Right? 108 00:08:16,330 --> 00:08:20,470 Let it just declared data and we will be modifying it. 109 00:08:20,680 --> 00:08:21,520 So float. 110 00:08:22,590 --> 00:08:26,030 Greta, OK, and the value that you have is to a point. 111 00:08:26,340 --> 00:08:31,830 OK, now let me just go ahead and try to celebrate the value by saying zero. 112 00:08:32,200 --> 00:08:37,950 OK, this is the format specified that you use for sending the starting by number and again, those 113 00:08:37,950 --> 00:08:39,090 sorts of details. 114 00:08:39,860 --> 00:08:40,140 Right? 115 00:08:40,470 --> 00:08:41,940 So let me just see what could. 116 00:08:42,450 --> 00:08:44,730 So our bill is successful. 117 00:08:45,030 --> 00:08:46,530 We are not getting any error. 118 00:08:46,800 --> 00:08:51,450 Now, if you just try to run an application on you and there. 119 00:08:52,530 --> 00:08:57,690 So you could clearly see we won't be able to send the floating point number right, so they would render 120 00:08:57,690 --> 00:09:00,900 this simply incapable of sending a floating point number. 121 00:09:00,930 --> 00:09:03,320 So they're just be adding anywhere here. 122 00:09:03,330 --> 00:09:06,060 So we are elected only one option that is printed. 123 00:09:06,090 --> 00:09:15,030 So if you just modify our code to include printer and let it just save our code and try to execute an 124 00:09:15,030 --> 00:09:21,840 application again on to an FPGA so that this modification now you could really see that we are able 125 00:09:21,840 --> 00:09:25,470 to send a floating going number utilizing a printer function, right? 126 00:09:25,920 --> 00:09:33,000 So this is so and easily find that we get is our size 266 key, right? 127 00:09:33,270 --> 00:09:40,350 So we have three mechanism of sending the values on to so so whenever you are in a situation the same, 128 00:09:40,350 --> 00:09:48,570 the constant string pressure to go with 0.8 or whenever you are sending the fixed point variable values 129 00:09:48,570 --> 00:09:55,860 on your so prefer to go with self-branded and whenever you are planning to send the floating by number 130 00:09:55,860 --> 00:09:56,460 on tokens. 131 00:09:56,460 --> 00:09:59,850 So prefer to go with bring them right. 132 00:10:00,210 --> 00:10:04,890 There's either three either narratives that we have and we already discussed what are the situation 133 00:10:04,890 --> 00:10:07,800 in which you will be using one or at right?