AT32UC3A464 Atmel Corporation, AT32UC3A464 Datasheet - Page 33

• Manufacturer Part Number: AT32UC3A464
• Manufacturer: Atmel Corporation

Specifications of AT32UC3A464

• Flash (kbytes): 64 Kbytes
• Pin Count: 100
• Max. Operating Frequency: 66 MHz
• Cpu: 32-bit AVR
• Hardware Qtouch Acquisition: No
• Usb Transceiver: 1
• Usb Speed: Hi-Speed
• Usb Interface: Device + OTG
• Spi: 6
• Twi (i2c): 2
• Uart: 4
• Ssc: 1
• Sd / Emmc: 2
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Adc Channels: 8
• Adc Resolution (bits): 10
• Resistive Touch Screen: No
• Temp. Sensor: No
• Crypto Engine: No
• Sram (kbytes): 128
• Self Program Memory: YES
• Dram Memory: No
• Nand Interface: Yes
• Picopower: No
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 3.0 to 3.6
• Operating Voltage (vcc): 3.0 to 3.6
• Fpu: No
• Timers: 6
• Output Compare Channels: 6
• Input Capture Channels: 6
• 32khz Rtc: Yes
• Calibrated Rc Oscillator: Yes

3.9.1.12
3.9.1.13
3.9.1.14
3.9.1.15
32002F–03/2010
ITLB Miss Exception
Instruction Address Exception
ITLB Protection Exception
Breakpoint Exception
The Instruction Address Error exception is generated if the generated instruction memory
address has an illegal alignment.
The ITLB Miss exception is generated when the MPU is enabled and the instruction memory
access does not hit in any regions. Used only if an MPU is present.
The ITLB Protection exception is generated when the instruction memory access violates the
access rights specified by the protection region in which the address lies. Used only if an MPU is
present.
The Breakpoint exception is issued when the OCD breakpoint input line to the CPU is aseerted,
and SREG[DM] is cleared.
When entering the exception routine, RAR_DBG points to the breakpoint instruction, and the
CPU will enter Debug mode. An external debugger can optionally assume control of the CPU
when the Breakpoint Exception is executed. The debugger can then issue individual instructions
to be executed in Debug mode. Debug mode is exited with the retd instruction. This passes con-
trol from the debugger back to the CPU, resuming normal execution.
*(--SP
*(--SP
SR[M2:M0] = B’110;
SR[EM] = 1;
SR[GM] = 1;
PC = EVBA | 0x14;
*(--SP
*(--SP
SR[M2:M0] = B’110;
SR[EM] = 1;
SR[GM] = 1;
PC = EVBA | 0x50;
*(--SP
*(--SP
SR[M2:M0] = B’110;
SR[EM] = 1;
SR[GM] = 1;
PC = EVBA | 0x18;
RSR_DBG = SR;
RAR_DBG = PC;
SR[M2:M0] = B’110;
SR[D] = 1;
SR[DM] = 1;
SR[EM] = 1;
SR[GM] = 1;
SYS
SYS
SYS
SYS
SYS
SYS
) = PC;
) = SR;
) = PC;
) = SR;
) = PC;
) = SR;
AVR32
33