AT32UC3B0512AU Atmel Corporation, AT32UC3B0512AU Datasheet - Page 27

no-image

AT32UC3B0512AU

Manufacturer Part Number
AT32UC3B0512AU
Description
Manufacturer
Atmel Corporation

Specifications of AT32UC3B0512AU

Flash (kbytes)
512 Kbytes
Pin Count
64
Max. Operating Frequency
60 MHz
Cpu
32-bit AVR
# Of Touch Channels
32
Hardware Qtouch Acquisition
No
Max I/o Pins
44
Ext Interrupts
44
Usb Transceiver
1
Usb Speed
Full Speed
Usb Interface
Device + OTG
Spi
4
Twi (i2c)
1
Uart
3
Ssc
1
Graphic Lcd
No
Video Decoder
No
Camera Interface
No
Adc Channels
8
Adc Resolution (bits)
10
Adc Speed (ksps)
384
Resistive Touch Screen
No
Dac Channels
2
Dac Resolution (bits)
16
Temp. Sensor
No
Crypto Engine
No
Sram (kbytes)
96
Self Program Memory
YES
Dram Memory
No
Nand Interface
No
Picopower
No
Temp. Range (deg C)
-40 to 85
I/o Supply Class
3.0-3.6 or (1.65-1.95+3.0-3.6)
Operating Voltage (vcc)
3.0-3.6 or (1.65-1.95+3.0-3.6)
Fpu
No
Mpu / Mmu
Yes / No
Timers
10
Output Compare Channels
16
Input Capture Channels
6
Pwm Channels
13
32khz Rtc
Yes
Calibrated Rc Oscillator
Yes

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
AT32UC3B0512AU-Z2U
Manufacturer:
ATMEL/爱特梅尔
Quantity:
20 000
3. Java Extension Module
3.1
32000D–04/2011
The AVR32 Java Virtual Machine
The AVR32 architecture can optionally support execution of Java bytecodes by including a Java
Extension Module (JEM). This support is included with minimal hardware overhead.
Comparing Java bytecode instructions with native AVR32 instructions, we see that a large part
of the instructions overlap as illustrated in
hardware resources by adding a separate Java instruction decoder and control module that exe-
cutes in Java state. The processor keeps track of its execution state through the status register
and changes execution mode seamlessly.
In a larger runtime system, an operating system keeps track of and dispatches different pro-
cesses. A Java program will typically be one, or several, of these processes.
The Java state is not to be confused with the security modes “system” and “application”, as the
JEM can execute in both modes. When the processor switches instruction decoder and enters
Java state, it does not affect the security level set by the system. A Java program could also be
executed from the different interrupt levels without interfering with the mode settings of the pro-
cessor, although it is not recommended that interrupt routines are written in Java due to latency.
The Java binary instructions are called bytecodes. These bytecodes are one or more bytes long.
A bytecode consists of an opcode and optional arguments. The bytecodes include some instruc-
tions with a high semantic content. In order to reduce the hardware overhead, these instructions
are trapped and executed as small RISC programs. These programs are stored in the program
memory and can be changed by the programmer (part of the Java VM implementation). This
gives full flexibility with regards to future extensions of the Java instruction set. Performance is
ensured through an efficient trapping mechanism and “Java tailored” RISC instructions.
Figure 3-1.
The AVR32 Java Virtual machine consists of two parts, the Java Extension Module in hardware
and the AVR32 specific Java Virtual Machine software, see
the two modules comply with the Java Virtual Machine specification.
High level instructions
A large part of the instruction set is shared between the AVR RISC and the Java
Virtual Machine. The Java instruction set includes instructions with high semantic
contents while the AVR RISC instruction set complements Java’s set with tradi-
tional hardware near RISC instructions
Ja va
Ja va
additions
Figure 3-1 on page
Common
Low level instructions
Figure 3-2 on page
27. The idea is thus to reuse the
AVR RIS C
additions
AVR
28. Together,
AVR32
27

Related parts for AT32UC3B0512AU