วีดีโอ

Glad it helped!

I'm sorry for the inconvenience caused, actually, I made this video for my students in the local language and shared it on TH-cam.

hello sir im a big fan but i have to tell you, your computer has virus

@@manuelalbus2374 o No what schud I do

+923064996601

This video is part of playlist on MIPS data path, control path and Pipelining hazards. Next part of the course is shared as a separate Playlist.

Share your circuit link/ details

yea but its files are stored here. just like google drive stores the google docs,slides,spreadsheets you make

Absolutely. One will have to pop the pushed parameter once the printing is done. It can be done either using RET 2 instead of RET in subroutine or use one pop instruction once the subroutine call is end.

That's correct. We can load SI with string offset and use it within the subroutine. It would save us two instructions but we will have to attach si with it (always), whenever we would have to call subroutine to print some string.

@@IrfanAnjummThe *push* and *pop* instruction are executing much slower than *mov mem,reg* and *mov reg,mem* intructions on x86 CPU before Pentium 4 was build. And with move instructions we do not have to care about the stack pointer, so we can use move instructions within or outside nested subroutines without using push and pop. To use the calling convention is not needed.

@@maxmuster7003 yes you are right. In simple problems, like discussed here, we don't have to use push/pop instructions for parameter passing/retrieving to the subroutine. Push and pop might take more clock cycles as compared with simple move instructions. The reason we are using stack to save/retrieve parameters is that number of registers available to the programmer are limited. If we start using registers for parameters passing, we might run short of registers for complex problems where several parameters need to be passed to the subroutine. Therefore, we try to make it a habit and use stack to pass parameters to subroutines.

@@IrfanAnjumm I store all values in the data segment only. In both cases we have a memory access if there is no free register and we need some more. But it is much easier to read/write to a known memory location in the data segment from inside and outside nested subroutines.

But accessing all values directly from data segment is not right approach because we wouldn't be able to use subroutines repeatedly for different set of variables/strings. As in this case for example, we can use same routine for any string. We will have to just push the offset to the stack and call the same subroutine.

Hi, Motor driver, usually, is used to control the direction of motors (forward, reverse) and to provide sufficient current to motors to work.

@@IrfanAnjumm ok and without dc motor temperature sensor can show temperature then why we have use dc motor?the title of project clearly shows that we are making temperature sensor whose values will be show on lcd display so in temperature sensor what is the purpose of dc motor?

Yes you are right. Temperature sensor would work without the motor. Actually, the project was made according to following requirements; 1: When the Temperature reading is above 90' F, the motor is turned ON. "Motor is ON" status and Temperature value is displayed on the LCD screen. 2: When the Temperature reading is less than 90' F, the motor is turned OFF. "Motor is OFF" status and Temperature value is displayed on the LCD screen.

@@IrfanAnjumm okay thanks

Use circuit details given in this blog: arduinouno0.blogspot.com/2020/06/control-dc-motor-using-temperature.html

@@IrfanAnjumm Same issue , motor isn't working even though circuit as per this blog only

😅✌️

Nice comment 🤭😅