ST6253BM3 datasheet(28/75 Pages) STMICROELECTRONICS

28 / 75 page

28/75

ST62T53B/T60B/T63B ST62E60B

IINTERRUPTS (Cont’d)

3.4.2 Interrupt Procedure

The interrupt procedure is very similar to a call pro-

cedure, indeed the user can consider the interrupt

as an asynchronous call procedure. As this is an

asynchronous event, the user cannot know the

context and the time at which it occurred. As a re-

sult, the user should save all Data space registers

which may be used within the interrupt routines.

There are separate sets of processor flags for nor-

mal, interrupt and non-maskable interrupt modes,

which are automatically switched and so do not

need to be saved.

The following list summarizes the interrupt proce-

dure:

MCU

– The interrupt is detected.

– The C and Z flags are replaced by the interrupt

flags (or by the NMI flags).

– The PC contents are stored in the first level of

the stack.

– The normal interrupt lines are inhibited (NMI still

active).

– The first internal latch is cleared.

– The associated interrupt vector is loaded inthe PC.

WARNING: In some circumstances, when a

maskable interrupt occurs while the ST6 core is in

NORMAL mode and especially during the execu-

tion of an ”ldi IOR, 00h” instruction (disabling all

maskable interrupts): if the interrupt arrives during

the first 3 cycles of the ”ldi” instruction (which is a

4-cycle instruction) the core will switch to interrupt

mode BUT the flags CN and ZN will NOT switch to

the interrupt pair CI and ZI.

User

– User selected registers are saved within the in-

terrupt service routine (normally on a software

stack).

– The source of the interrupt is found by polling the

interrupt flags (if more than one source is associ-

ated with the same vector).

– The interrupt is serviced.

– Return from interrupt (RETI)

MCU

– Automatically the MCU switches back to the nor-

mal flag set (or the interrupt flag set) and pops

the previous PC value from the stack.

The interrupt routine usually begins by the identify-

ing the device which generated the interrupt re-

quest (by polling). The user should save the regis-

ters which are used within the interrupt routine in a

software stack. After the RETI instruction is exe-

cuted, the MCU returns to the main routine.

Figure 17. Interrupt Processing Flow Chart

INS TRUC TION

FETC H

INS TRUCT ION

EXEC UTE

I NS TRUCTIO N

WAS

THE INS TRUCTI ON

ARE TI

C LEAR

INT ER RU PT MASK

SELECT

PR OGRAM FLAGS

”POP”

THE STACK ED PC

C HE CK I F THE RE IS

AN IN TERR UP T RE QUEST

AN D INTE RR UPT MASK

SELECT

IN TERN AL MODE FLAG

PUS H THE

PC INTO THE STAC K

LOAD PC FROM

INT ERR UP T VECT OR

(FFC/F FD)

SET

INT ER RU PT MASK

YES

IS THE C ORE

ALRE ADY IN

NOR MAL MODE?

VA000014

YES

ST6253BM3 データシート(PDF) 28 Page - STMicroelectronics

ST6253BM3 データシート(HTML) 28 Page - STMicroelectronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75

データシートダウンロード