欢迎访问ic37.com |
会员登录 免费注册
发布采购

MEGA128CAN 参数 Datasheet PDF下载

MEGA128CAN图片预览
型号: MEGA128CAN
PDF下载: 下载PDF文件 查看货源
内容描述: 微控制器,带有ISP功能的Flash和CAN控制器128K字节 [Microcontroller WITH 128K BYTES OF ISP FLASH AND CAN CONTROLLER]
分类和应用: 微控制器
文件页数/大小: 413 页 / 5507 K
品牌: ATMEL [ ATMEL ]
 浏览型号MEGA128CAN的Datasheet PDF文件第10页浏览型号MEGA128CAN的Datasheet PDF文件第11页浏览型号MEGA128CAN的Datasheet PDF文件第12页浏览型号MEGA128CAN的Datasheet PDF文件第13页浏览型号MEGA128CAN的Datasheet PDF文件第15页浏览型号MEGA128CAN的Datasheet PDF文件第16页浏览型号MEGA128CAN的Datasheet PDF文件第17页浏览型号MEGA128CAN的Datasheet PDF文件第18页  
with the Global Interrupt Enable bit in the Status Register in order to enable the interrupt.  
Depending on the Program Counter value, interrupts may be automatically disabled  
when Boot Lock bits BLB02 or BLB12 are programmed. This feature improves software  
security. See the section “Memory Programming” on page 325 for details.  
The lowest addresses in the program memory space are by default defined as the Reset  
and Interrupt Vectors. The complete list of vectors is shown in “Interrupts” on page 56.  
The list also determines the priority levels of the different interrupts. The lower the  
address the higher is the priority level. RESET has the highest priority, and next is INT0  
– the External Interrupt Request 0. The Interrupt Vectors can be moved to the start of  
the Boot Flash section by setting the IVSEL bit in the MCU Control Register (MCUCR).  
Refer to “Interrupts” on page 56 for more information. The Reset Vector can also be  
moved to the start of the Boot Flash section by programming the BOOTRST Fuse, see  
“Boot Loader Support – Read-While-Write Self-Programming” on page 311.  
Interrupt Behavior  
When an interrupt occurs, the Global Interrupt Enable I-bit is cleared and all interrupts  
are disabled. The user software can write logic one to the I-bit to enable nested inter-  
rupts. All enabled interrupts can then interrupt the current interrupt routine. The I-bit is  
automatically set when a Return from Interrupt instruction – RETI – is executed.  
There are basically two types of interrupts. The first type is triggered by an event that  
sets the interrupt flag. For these interrupts, the Program Counter is vectored to the  
actual Interrupt Vector in order to execute the interrupt handling routine, and hardware  
clears the corresponding interrupt flag. Interrupt flags can also be cleared by writing a  
logic one to the flag bit position(s) to be cleared. If an interrupt condition occurs while the  
corresponding interrupt enable bit is cleared, the interrupt flag will be set and remem-  
bered until the interrupt is enabled, or the flag is cleared by software. Similarly, if one or  
more interrupt conditions occur while the Global Interrupt Enable bit is cleared, the cor-  
responding interrupt flag(s) will be set and remembered until the Global Interrupt Enable  
bit is set, and will then be executed by order of priority.  
The second type of interrupts will trigger as long as the interrupt condition is present.  
These interrupts do not necessarily have interrupt flags. If the interrupt condition disap-  
pears before the interrupt is enabled, the interrupt will not be triggered.  
When the AVR exits from an interrupt, it will always return to the main program and exe-  
cute one more instruction before any pending interrupt is served.  
Note that the Status Register is not automatically stored when entering an interrupt rou-  
tine, nor restored when returning from an interrupt routine. This must be handled by  
software.  
When using the CLI instruction to disable interrupts, the interrupts will be immediately  
disabled. No interrupt will be executed after the CLI instruction, even if it occurs simulta-  
neously with the CLI instruction. The following example shows how this can be used to  
avoid interrupts during the timed EEPROM write sequence.  
14  
AT90CAN128  
4250E–CAN–12/04  
 复制成功!