《移动信息工程导论》第11章MSP430中断.ppt

MSP430 Interrupt Introduction When MSP430 processor executes the following code, it will loop forever Question: How can it execute other codes that handle external events, e.g. I/O, timer? Option 1 Put codes that handle external events in your main program ? polling Option 2 Keep your program unchanged and force the processor to jump to the code handling the external event when that event occurs Requirements: Must let the processor know when the event occurs Must let the processor know where to jump to execute the handling code Must not allow your program know!! ? you program must execute as if nothing happens ? must store and restore your program state Interrupt: Processor’s Perspective How does the processor know when there is an interrupt? Usually when it receives a signal from one of the IRQ (interrupt request) pins Interrupt: Processor’s Perspective What does the processor do in handling an interrupt? When receiving an interrupt signal, the processor stops at the next instruction and saves the address of the next instruction on the stack and jumps to a specific interrupt service routine (ISR) ISR is basically a subroutine to perform operations to handle the interrupt with a RETURN at the end How to be transparent to the running prog.? The processor has to save the “state” of the program onto the stack and restoring them at the end of ISR Interrupt Service Routine The following shows an example of an ISR Task Code ISR ... MOVE R1, R7 MUL R1, 5 PUSH R1 ADD R1, R2 PUSH R2 DIV R1, 2 ... JCOND ZERO, END ;ISR code comes here SUBTRACT R1, R3 ... ... POP R2 ... POP R1 END: MOVE R7, R1 RETURN ... ... Interrupt: Program’s Perspective To a running program, an ISR is like a subroutine, but is invoked by the hardware at an unpredictable time Not by the control of the program’s logic Subroutine: Program has total control of when to call and jump to a subroutine Disabling Interrupts Programs may disable interrupts In most cases the program can selec