The difference between RETI and RET in MCU assembly instructions

Publisher:心动代码Latest update time:2014-08-26 Source: 21icKeywords:MCU Reading articles on mobile phones Scan QR code
Read articles on your mobile phone anytime, anywhere

Normally, RET is used to return in ordinary assembly subroutines, and RETI is used to return from interrupts in interrupt service subroutines. Both instructions can pop the breakpoint address from the stack and load it into the PC, allowing the CPU to return to the original breakpoint of the main program and continue running.

However, RET and RETI have essential differences: when an interrupt source is responded, one of the flag registers flag H and flag L in the microcontroller will be automatically set to prevent the triggering of interrupts of lower or same level than it. RETI can clear the "priority activation trigger" (i.e., flag register) to ensure timely response to subsequent interrupt sources.

So, when RETI is replaced by RET, the program may not fail the first time it is run, but it will fail the second time!

Keywords:MCU Reference address:The difference between RETI and RET in MCU assembly instructions

Previous article:Introduction to MCU
Next article:What aspects should be considered in the design of anti-interference measures for single-chip microcomputer systems?

Latest Microcontroller Articles
  • Download from the Internet--ARM Getting Started Notes
    A brief introduction: From today on, the ARM notebook of the rookie is open, and it can be regarded as a place to store these notes. Why publish it? Maybe you are interested in it. In fact, the reason for these notes is ...
  • Learn ARM development(22)
    Turning off and on interrupts Interrupts are an efficient dialogue mechanism, but sometimes you don't want to interrupt the program while it is running. For example, when you are printing something, the program suddenly interrupts and another ...
  • Learn ARM development(21)
    First, declare the task pointer, because it will be used later. Task pointer volatile TASK_TCB* volatile g_pCurrentTask = NULL;volatile TASK_TCB* vol ...
  • Learn ARM development(20)
    With the previous Tick interrupt, the basic task switching conditions are ready. However, this "easterly" is also difficult to understand. Only through continuous practice can we understand it. ...
  • Learn ARM development(19)
    After many days of hard work, I finally got the interrupt working. But in order to allow RTOS to use timer interrupts, what kind of interrupts can be implemented in S3C44B0? There are two methods in S3C44B0. ...
  • Learn ARM development(14)
  • Learn ARM development(15)
  • Learn ARM development(16)
  • Learn ARM development(17)
Change More Related Popular Components

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews


Room 1530, 15th Floor, Building B, No.18 Zhongguancun Street, Haidian District, Beijing, Postal Code: 100190 China Telephone: 008610 8235 0740

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京ICP证060456号 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号