数据搜索系统,热门电子元器件搜索
  Chinese  ▼
ALLDATASHEETCN.COM

X  

HT56RB27 数据表(PDF) 81 Page - Holtek Semiconductor Inc

部件名 HT56RB27
功能描述  TinyPowerTM A/D Type Smart Card OTP MCU with DAC, ISO 7816 and USB Interfaces
PDF  153 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
制造商  HOLTEK [Holtek Semiconductor Inc]
网页  http://www.holtek.com
标志 HOLTEK - Holtek Semiconductor Inc

HT56RB27 数据表(HTML) 81 Page - Holtek Semiconductor Inc

Back Button HT56RB27 Datasheet HTML 77Page - Holtek Semiconductor Inc HT56RB27 Datasheet HTML 78Page - Holtek Semiconductor Inc HT56RB27 Datasheet HTML 79Page - Holtek Semiconductor Inc HT56RB27 Datasheet HTML 80Page - Holtek Semiconductor Inc HT56RB27 Datasheet HTML 81Page - Holtek Semiconductor Inc HT56RB27 Datasheet HTML 82Page - Holtek Semiconductor Inc HT56RB27 Datasheet HTML 83Page - Holtek Semiconductor Inc HT56RB27 Datasheet HTML 84Page - Holtek Semiconductor Inc HT56RB27 Datasheet HTML 85Page - Holtek Semiconductor Inc Next Button
Zoom Inzoom in Zoom Outzoom out
 81 / 153 page
background image
Interrupt Operation
A Timer/Event Counter overflow, Time Base, RTC overflow, SPI/I2C data transfer complete, an end
of A/D conversion, USB event, Smart Card event, Smart Card insertion/removal or the external
interrupt line being triggered will all generate an interrupt request by setting their corresponding
request flag. When this happens and if their appropriate interrupt enable bit is set, the Program
Counter, which stores the address of the next instruction to be executed, will be transferred onto the
stack. The Program Counter will then be loaded with a new address which will be the value of the
corresponding interrupt vector. The microcontroller will then fetch its next instruction from this
interrupt vector. The instruction at this vector will usually be a JMP statement which will jump to
another section of program which is known as the interrupt service routine. Here is located the code to
control the appropriate interrupt. The interrupt service routine must be terminated with a RETI
statement, which retrieves the original Program Counter address from the stack and allows the
microcontroller to continue with normal execution at the point where the interrupt occurred.
The various interrupt enable bits, together with their associated request flags, are shown in the
accompanying diagram with their order of priority.
Once an interrupt subroutine is serviced, all the other interrupts will be blocked, as the EMI bit will be
cleared automatically. This will prevent any further interrupt nesting from occurring. However, if other
interrupt requests occur during this interval, although the interrupt will not be immediately serviced,
the request flag will still be recorded. If an interrupt requires immediate servicing while the program is
already in another interrupt service routine, the EMI bit should be set after entering the routine, to
allow interrupt nesting. If the stack is full, the interrupt request will not be acknowledged, even if the
related interrupt is enabled, until the Stack Pointer is decremented. If immediate service is desired, the
stack must be prevented from becoming full.
Interrupt Priority
Interrupts, occurring in the interval between the rising edges of two consecutive T2 pulses, will be
serviced on the latter of the two T2 pulses, if the corresponding interrupts are enabled. In case of
simultaneous requests, the following table shows the priority that is applied.
Interrupt Source
Priority
Vector
Smart Card Interrupt
1
04H
USB Interrupt
2
08H
External Interrupt 0
3
0CH
External Interrupt 1
4
10H
Timer/Event Counter 0 Overflow
5
14H
Timer/Event Counter 1 Overflow
6
18H
Smart Card Insertion/Removal Interrupt
7
1CH
A/D Converter Interrupt
8
20H
Multi-function 0 Interrupt
9
24H
Multi-function 1 Interrupt
10
28H
The SIM0 interrupt, Real Time clock interrupt, Time Base interrupt and External Peripheral inter-
rupt share the same interrupt vector which is 24H while the SIM1 interrupt, Timer/Event Counter 2
overflow and Timer/Event Counter 3 overflow interrupt share the same interrupt vector which is
28H. Each of these interrupts has their own individual interrupt flag but also share the same
multi-function interrupt flag named MF0F or MF1F respectively. The MF0F or MF1F flag will be
cleared by hardware once the corresponding Multi-function interrupt is serviced. However the indi-
vidual interrupts that have triggered the Multi-function interrupt need to be cleared by the applica-
tion program.
HT56RB27
TinyPowerTM A/D Type Smart Card OTP MCU
with DAC, ISO 7816 and USB Interfaces
Rev. 1.20
81
April 26, 2013



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 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100  ...More


数据表 下载

Go To PDF Page


链接网址



ALLDATASHEET是否为您带来帮助?  [ DONATE ] 

关于 Alldatasheet   |   广告服务   |   联系我们   |   隐私政策   |   数据表链接    |   链接交换   |   制造商名单
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com