Atmel AVR32025: AT32UC3L-EK User Guide

Atmel AVR32025: AT32UC3L-EK User Guide
Atmel AVR32025: AT32UC3L-EK User Guide
Features
•
•
•
•
•
Kit features overview
Kit content
Hardware description
Schematics
Errata
32-bit Atmel
Microcontrollers
Application Note
1 Introduction
The Atmel® AT32UC3L-EK is an evaluation kit and development system for the
Atmel AVR® UC3 AT32UC3L064 microcontroller.
As an evaluation kit, the board focus is towards Atmel QTouch® and QMatrix
support, and picoPower® technology.
As a development system, the board notably provides on-board memory, a USB
communication interface, an accelerometer, and the JTAG programming and
debugging interface. The AT32UC3L-EK also features expansion headers; one of
these is the wireless expansion header (named WLESS on the PCB), which is the
receptacle for one of the two Atmel RZ600 radio boards (not provided in the kit).
Figure 1-1. The AT32UC3L-EK evaluation kit.
Rev. 32150B-AVR-03/12
2 Kit overview
This chapter lists the features provided by the Atmel AT32UC3L-EK evaluation kit,
and describes the content of the box the kit is packaged in.
Figure 2-1. AT32UC3L-EK block diagram.
2
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
2.1 Features
The following is a list of the main components and interfaces on the Atmel
AT32UC3L-EK:
• Main MCU: 32-bit Atmel AVR UC3 AT32UC3L064 (TQFP48)
o 64KBytes internal flash, 16KBytes internal RAM
o Up to 50MHz operation
o Very low power consumption
o Capacitive touch module for support of QTouch and QMatrix capture
from capacitive touch sensors
o Peripheral event system
o FlashVault allows pre-programmed, secure library support for end
user applications
• One touch rotor and five touch sensors
• One 3-axis accelerometer (connected to channels 6, 7, and 8 of the ADCIFB
module)
• One serial data flash, 64Mbits
• One RTC 32kHz crystal
• Four LEDs
• One pushbutton
• One reset pushbutton
• Wireless expansion connector for the Atmel RZ600 AT86RF231 radio board
PCBA or for any SPI-based, TWI-based, or USART-based external
communication
• 36-pin raw expansion header for GPIO access
• JTAG connector for programming and debugging on the AT32UC3L064 MCU
• Powered through the USB connector, through an external power supply (header
J2), or through a 1.2V battery (header J3)
• USB (2.0 mini A-B receptacle) connected to the 32-bit Atmel AVR UC3
AT32UC3B1256
o AT32UC3L064 and AT32UC3B1256 are connected through two pins
o one of the pre-loaded firmware on the AT32UC3B1256 acts as a
UART-USB CDC virtual com port gateway
o one of the pre-loaded firmware on the AT32UC3B1256 acts as
UART-to-USB HID QTouch Debug interface to AVR QTouch Studio
o USB mode pushbutton: with the default pre-loaded firmware on the
AT32UC3B1256, the USB mode button is used to select between the
UART-USB CDC virtual com port gateway firmware (press the USB
mode upon power up of the board) and the UART-to-USB HID
QTouch Debug interface to AVR QTouch Studio
o the J12 jumper can be used to set the AT32UC3B1256 in boot loader
mode at power up
o JTAG
connector
for
programming
and debugging the
AT32UC3B1256 (J13)
3
32150B-AVR-03/12
2.2 Kit content
The Atmel AT32UC3L-EK toolbox contains the following items:
•
•
•
•
•
•
One AVR Technical Library DVD
One Atmel AT32UC3L-EK customer letter
One Atmel AT32UC3L-EK Getting Started Guide
One Atmel AT32UC3L-EK evaluation kit
One mini-B plug to std-A plug ~1.5m USB cable
One 1.2V NiMh rechargeable battery
Figure 2-2. Unpacked AT32UC3L-EK toolbox.
2.3 Power up and getting started
Refer to the AVR32777: AT32UC3L-EK Getting Started document.
2.4 References
2.4.1 The AVR UC3 L0 series datasheet
http://www.atmel.com/dyn/resources/prod_documents/doc32099.pdf
2.4.2 The AT32UC3L-EK schematics
http://www.atmel.com/Images/AT32UC3L-EK_Schematics.zip
2.4.3 The AVR32777: AT32UC3L-EK Getting Started document
http://www.atmel.com/Images/doc32149.pdf
4
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
2.4.4 The 32-bit AVR UC3 L series schematic checklist
http://www.atmel.com/dyn/resources/prod_documents/doc32129.pdf
2.4.5 The Atmel AVR Software Framework
http://www.atmel.com/asf
All pre-loaded firmware source code is available in the AVR Software Framework
version 2.0 or higher.
2.4.6 The Atmel AVR UC3 UART boot loader
The Atmel UC3L064/32/16 devices are all pre-loaded with a UART boot loader which
source code is available in the Atmel Software Framework.
2.4.7 The Atmel QTouch Library
http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4627
2.4.8 Atmel AVR QTouch Studio
http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4445
2.4.9 Debuggers
http://www.atmel.com/products/microcontrollers/avr/32-bitavruc3.aspx?tab=tools
5
32150B-AVR-03/12
3 Hardware description
This chapter presents the hardware blocks of the Atmel AT32UC3L-EK hardware
design. Each hardware block is described with:
•
•
•
•
An overview of the hardware block
A location in the schematics document
AT32UC3L-specific information (when relevant)
All possible hardware configurations of the block and available test points
3.1 Power supply
The power supply block of the AT32UC3L-EK is in charge of distributing power to all
components of the board.
3.1.1 Overview
Figure 3-1. AT32UC3L-EK power supply logical view.
The AT32UC3L-EK can be powered from three different sources: the USB mini AB
plug (5V input), an external power supply connected to the J2 header (DC 5V ±10%),
and a 1.2V NiMh battery (in the J3 socket on the bottom side of the board).
These inputs go through an external 3.3V switch mode regulator, which in turn
supplies the rest of the board with a 3.3V voltage.
The power indicator LED, D4, labeled POWER, indicates if the 3.3V from the external
regulator is present.
The pushbutton labeled SW2 is there to activate the use of the battery when one is
installed in the J3 socket.
The Atmel AT32UC3L064 firmware may read the battery current voltage with an
ADCIFB channel.
6
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
The “Power Off” signal from the Atmel AT32UC3L064 to the on-board power supply
block can be used to lower the power consumption by software.
To customize the hardware configuration of this block, see Section 3.1.4.1, Hardware
configurations, for a description of the possible hardware configurations of the power
supply block.
Figure 3-2. Atmel AT32UC3L-EK top view power supply location.
Figure 3-3. AT32UC3L-EK bottom view power supply location.
3.1.2 Schematics
The schematic of the power supply block is on page 2 of the schematic document
found in Section 2.4.2, The AT32UC3L-EK schematics.
3.1.3 UC3L-specific information
3.1.3.1 Atmel AT32UC3L064 power supply mode
Of the three power supply configurations supported by the AT32UC3L064, this board
implements the 3.3V single power supply mode configuration. Refer to the figure,
7
32150B-AVR-03/12
“3.3V Single Supply Mode,” in section 6.1.3.1 in the AVR UC3 L0 Series datasheet for
schematics of this mode: this is how it is implemented on this board.
3.1.3.2 Atmel AT32UC3L064 pinout for the power supply block
Table 3-1. The Atmel AVR UC3L pinout for the power supply block.
QFP48 pin
GPIO
GPIO alternate functions
Feature
1
N.A.
N.A.
GND
4
PA03
GPIO[3]
The Power-Off signal from the
AT32UC3L064 to the power supply
block
17
N.A.
N.A.
VDDIN
18
N.A.
N.A.
VDDCORE
19
N.A.
N.A.
GND
33
N.A.
N.A.
GNDANA
34
N.A.
N.A.
ADVREFP
35
N.A.
N.A.
VDDANA
42
N.A.
N.A.
VDDIO
48
N.A.
N.A.
VDDIO
3.1.4 Configurations and test points
3.1.4.1 Hardware configurations
The default hardware configuration of the power supply block implies that:
• The power supply sources are the battery or the USB plug (thus the dotted-lines
on the J2 plug in the block diagram, cf. Figure 3-1. AT32UC3L-EK power supply
logical view. and Figure 2-1. AT32UC3L-EK block diagram.)
• The power-off signal from the AT32UC3L064 is not connected to the on-board
power supply block (thus the dotted arrow in the block diagram)
To enable the power supply through the J2 connector, mount the R5 resistor (solder
patch) and remove the R6 resistor.
To activate the Power-Off signal, remove the R17 resistor and mount the R26 resistor
(solder patch).
To locate the resistors mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
8
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
3.1.4.2 Test points
A few test points covering the power supply block have been placed on the Atmel
AT32UC3L-EK for the verification of important signals.
Table 3-2. Power supply block test points.
Designation
Feature
TP7
Input voltage level after D1 when the J2 external power supply is used
TP8
Input voltage for all boards’ components except the Atmel AT32UC3L064.
Should be 3.3V nominal
TP9
Input voltage for the AT32UC3L064 VDDIO pin. Should be 3.3V nominal
TP10
Output voltage out of the external regulator
TP11
Input voltage for the AT32UC3L064 VDDIN pin. Should be 3.3V nominal
TP12
GND
To locate the test points mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
3.1.5 Power consumption measurement
To measure the power consumption of the overall board minus the AT32UC3L064,
remove the 0Ω R11 resistor and measure the current over the J4 2-pin header (not
mounted by default).
To measure the power consumption on the AT32UC3L064 VDDIO, remove the 0Ω
R14 resistor and measure the current over the J5 2-pin header (not mounted by
default).
To measure the power consumption on the AT32UC3L064 VDDIN, remove the 0Ω
R19 resistor and measure the current over the J6 2-pin header (not mounted by
default).
Figure 3-4. AT32UC3L-EK power consumption measurement headers location.
Figure 3-4. AT32UC3L-EK power consumption measurement headers location.,”
points to the location of the power consumption measurement area. To accurately
locate the components mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
9
32150B-AVR-03/12
3.2 User interface
The main user interface block of the Atmel AT32UC3L-EK covers all components
providing a direct interface [visual (output) or tactile (input)] to the user.
3.2.1 Overview
Figure 3-5. AT32UC3L-EK user interface logical view.
The main user interface offered by the kit is the touch user interface consisting of the
wheel sensor and the five button sensors. The touch sensors are implemented using
the QMatrix method (X=6, Y=2). The CAT IP of the Atmel AT32UC3L064 is used, as
is the ACIFB IP (implied by the use of the QMatrix method). Applications running on
the AT32UC3L064 need to use the QTouch library for optimal touch events
management.
Four general purpose LEDs (labeled LED0, LED1, LED2, LED3) are connected to the
AT32UC3L064.
The WAKE pushbutton can be used as a general purpose pushbutton, and is
connected to the special purpose WAKE_N pin.
The RST pushbutton is used to generate an external reset to the AT32UC3L064.
A three-axis accelerometer is connected to three channels of the AT32UC3L064’s
ADCIFB IP.
NOTE
There are other user interface components in the kit, and these are related to:
• The USB Interface, presented in this document in Section 3.7, USB interface
• The power supply interface, presented in this document in Section 3.1 Power
supply
10
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
Figure 3-6. Atmel AT32UC3L-EK top view user interface location.
Figure 3-7. AT32UC3L-EK bottom view user interface location.
UC3B
3.2.2 Schematics
In Section 2.4.2, The AT32UC3L-EK schematics, the components of the user
interface are found:
• On page 1 for the RST pushbutton
• On page 3 for the three-axis accelerometer
• On page 4 for the touch sensors, LEDs, and WAKE pushbutton
11
32150B-AVR-03/12
3.2.3 UC3L-specific information
3.2.3.1 Atmel AT32UC3L064 pinout for the user interface block
Table 3-3. UC3L pinout for the touch sensors interface.
QFP48 pin
GPIO
GPIO alternate functions
Feature
46
PA10
CAT-CSA[5]
QMatrix Y2
47
PA12
CAT-CSB[5]
QMatrix YK2
5
PB12
CAT-CSA[15]
QMatrix Y7
29
PB09
CAT-CSB[15]
QMatrix YK7
36
PA14
CAT-CSA[6]
QMatrix X6
37
PA15
CAT-CSB[6]
QMatrix X7
40
PA19
CAT-CSA[10]
QMatrix X10
9
PA22
CAT-CSB[10]
QMatrix X11
21
PB04
CAT-CSA[14]
QMatrix X14
20
PB05
CAT-CSB[14]
QMatrix X15
38
PA16
ACIFB-ACREFN
ACREFN, connected to GNDANA
39
PA17
CAT-SMP
SMP
Table 3-4. UC3L pinout for the LEDs and push-buttons interfaces.
QFP48 pin
GPIO
GPIO alternate functions
Feature
24
PA21
GPIO[21] or TC0-B1 or
PWMA[21] or SCIF-GCLK[0]
LED0
23
PB10
GPIO[42] or GLOC-OUT[1]
or PWMA[33]
LED1
7
PB02
GPIO[34] or TC0-A2 or
PWMA[25] or SCIF-GCLK[1]
LED2
8
PB03
GPIO[35] or TC0-B2 or
PWMA[26] or TC1-A2
LED3
27
PA11
GPIO[11] controls the pin
WAKE pushbutton
22
N.A.
N.A.
RST pushbutton, connected to the
RESET_N pin
Table 3-5. UC3L pinout for the accelerometer interface.
12
QFP48 pin
GPIO
GPIO alternate functions
Feature
30
PB06
ADCIFB-AD[6]
Output VoutX of the accelerometer
acquired by ADC channel 6
31
PB07
ADCIFB-AD[7]
Output VoutY of the accelerometer
acquired by ADC channel 7
32
PB08
ADCIFB-AD[8]
Output VoutZ of the accelerometer
acquired by ADC channel 8
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
3.2.4 Configuration and test points
3.2.4.1 Hardware configuration
The default hardware configuration of the user interface block implies that:
• There is no hardware to support debounce on the RST pushbutton: R36 is not
mounted, so C4 has no effect. This was done to support the aWire programming
and debugging interface (refer to Section 3.3 Programming and debugging
interface)
To enable the hardware debounce support on the RST pushbutton, mount the 0Ω
R36 resistor (solder patch).
To locate the R36 resistor mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
3.2.4.2 Test points
A few test points covering the user interface block have been placed on the
AT32UC3L-EK for the verification of important signals.
Table 3-6. User interface block test points.
Designation
Feature
TP1
Input voltage on the Atmel AT32UC3L064 RESET_N pin, depending on the
state of the RST pushbutton
TP18
Input voltage for the accelerometer. Should be 1.8V nominal
TP15
Output voltage on the accelerometer VoutZ pin
TP16
Output voltage on the accelerometer VoutY pin
TP17
Output voltage on the accelerometer VoutX pin
TP19
Input voltage on the AT32UC3L064 WAKE_N pin, depending on the state of
the WAKE pushbutton
TP20
Voltage level on LED0
TP21
Voltage level on LED1
TP22
Voltage level on LED2
TP23
Voltage level on LED3
To locate the test points mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
3.3 Programming and debugging interface
The programming and debugging interface block of the AT32UC3L-EK provides the
developer with a means to debug an application running on the AT32UC3L064.
13
32150B-AVR-03/12
3.3.1 Overview
Figure 3-8. Atmel AT32UC3L-EK programming and debugging interface logical view.
The main programming and debugging interface of the AT32UC3L-EK is meant to
program and debug the Atmel AT32UC3L064. There are two debug interfaces
available on the AT32UC3L064: the JTAG interface and the aWire interface (single
pin debug system), both accessible through the J9 connector.
NOTE
There is another programming and debugging interface block on the kit, but it is
related to the Atmel AT32UC3B1256 chip in charge of USB communication (refer to
Section 3.7, USB interface).
Figure 3-9. AT32UC3L-EK top view programming and debugging interface location.
3.3.2 Schematics
In Section 2.4.2, The AT32UC3L-EK schematics, the programming and debugging
interface is on page 5.
3.3.3 UC3L-specific information
3.3.3.1 AT32UC3L064 pinout for programming and debugging interface
Table 3-7. UC3L pinout for the programming and debugging interface.
14
QFP48 pin
GPIO
GPIO alternate functions
Feature
11
PA00
None
JTAG.TCK
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
QFP48 pin
GPIO
GPIO alternate functions
Feature
14
PA01
None
JTAG.TMS
13
PA02
None
JTAG.TDO
4
PA03
None
JTAG.TDI
22
N.A.
N.A.
RESET_N pin. Used when
enabling/disabling the JTAG or the
aWire interface. Also, the aWire data
is multiplexed on this pin
3.3.4 Configuration and test points
3.3.4.1 Special considerations for the RESET_N pin and the JTAG pins
On the Atmel AVR UC3 L0 series, the RESET_N pin is used to enable/disable the
JTAG interface or the aWire interface. For this reason, the RESET_N pin should not
be connected to an external reset circuit to avoid drive contention and speed
problems. To avoid this issue with the RST pushbutton, the 0Ω R36 resistor is not
mounted by default.
On the AVR UC3 L0 series, the JTAG TMS, TDI, TDO, and TCK pins are multiplexed
with I/O lines. While using these multiplexed JTAG lines, all normal peripheral activity
on these lines is disabled. The user must make sure that no external peripheral is
blocking the JTAG lines while debugging.
Table 3-8, Conflict conditions over the debugging pins, highlights the components on
the Atmel AT32UC3L-EK that might interfere with the multiplexed JTAG pins. These
components must not be used while debugging with the JTAG interface. Another way
to say this is that debugging over the JTAG interface will not work if there is any
external signal activity over these components.
Table 3-8. Conflict conditions over the debugging pins.
QFP48 pin
GPIO
Conflict conditions
11
PA00
If the WLESS J8 connector is configured with a jumper on J44.3-5,
signal activities over J8.1 will conflict with JTAG.TCK
14
PA01
If the WLESS J8 connector is configured with a jumper on J44.4-6,
signal activities over J8.2 will conflict with JTAG.TMS
13
PA02
No possible conflicts with JTAG.TDO
4
PA03
•
•
22
N.A.
If the 0Ω R36 resistor is mounted, the effect of C4 will conflict with
the RESET_N pin
Signal activities over J8.5 will conflict with JTAG.TDI
If the Power-Off signal is enabled (refer to Section 3.1.4.1,
Hardware configurations, in the Power supply interface
chapter), the power supply hardware block or any software
activity on the PA03 pin will conflict with JTAG.TDI
To summarize, debugging will not work if:
• The WLESS connector is used
• The Power-Off signal is enabled by hardware (refer to Section 3.1.4.1, Hardware
configurations) and the software running on the Atmel AT32UC3L064 toggles
PA03
15
32150B-AVR-03/12
3.3.4.2 Test points
A few test points covering the programming and debugging interface block have been
placed on the Atmel AT32UC3L-EK for the verification of important signals.
Table 3-9. Programming and debugging interface block test points.
Designation
Feature
TP24
JTAG.TCK
TP25
JTAG.TDO
TP26
JTAG.TMS
TP27
JTAG.TDI
TP28
GND
TP29
VCC3
TP30
RESET_N
To locate the test points mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
3.3.4.3 Using the aWire
The Atmel AVR ONE! and JTAGICE mkII tools can interface with the Atmel AVR UC3
L0 series using the single-wire aWire interface. Check the documentation of these
tools to know the recommended pinout to connect to an aWire target.
3.4 External memory
The external memory on the AT32UC3L-EK provides extra memory to the Atmel
AT32UC3L064.
3.4.1 Overview
Figure 3-10. AT32UC3L-EK external memory logical view.
The AT32UC3L-EK contains a 64Mbit Atmel DataFlash® device (AT45DB642D-CNU)
that is connected to the SPI0 interface of the AT32UC3L064.
16
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
Figure 3-11. Atmel AT32UC3L-EK bottom view external memory location.
3.4.2 Schematics
In Section 2.4.2, The AT32UC3L-EK schematics, the external memory is described
on page 3.
3.4.3 UC3L-specific information
3.4.3.1 Atmel AT32UC3L064 pinout for the Atmel DataFlash
Table 3-10. UC3L pinout for the external memory.
QFP48 pin
GPIO
GPIO alternate functions
Feature
28
PA04
SPI0.MISO
DataFlash SO
12
PA05
SPI0.MOSI
DataFlash SI
10
PA06
SPI0.SCK
DataFlash SCK
15
PA07
SPI0.NPCS
DataFlash #CS
22
N.A.
N.A. RESET_N pin
DataFlash #RESET
3.4.4 Configuration and test points
3.4.4.1 Special consideration when using the DataFlash
The pins PA05, PA06, and PA07 are multiplexed with other components on the
AT32UC3L-EK.
Table 3-11, Conflict conditions with the DataFlash, highlights the components on the
AT32UC3L-EK that might interfere with the DataFlash pins. These components must
not be used while using the DataFlash.
17
32150B-AVR-03/12
Table 3-11. Conflict conditions with the DataFlash.
QFP48 pin
GPIO
DataFlash signal
Conflict conditions
28
PA04
DataFlash SO
If the WLESS J8 connector is configured with
a jumper on J44.2-4, signal activities over J8.2
will conflict with the DataFlash SO signal
12
PA05
If the WLESS J8 connector is configured with
a jumper on J44.1-3, signal activities over J8.1
will conflict with the DataFlash SI signal
To summarize, the Atmel DataFlash cannot be used when using an external module
on the WLESS connector configured with a jumper on J44.2-4 and/or with a jumper
on J44.1-3.
3.4.4.2 Test points
Two test points covering the DataFlash have been placed on the Atmel AT32UC3LEK for the verification of important signals.
Table 3-12. DataFlash test points.
Designation
Feature
TP13
DataFlash #CS
TP14
DataFlash #WP
To locate the test points mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
3.5 RTC
The RTC block on the AT32UC3L-EK provides a 32kHz oscillating crystal to the
Atmel AT32UC3L064.
3.5.1 Overview
Figure 3-12. AT32UC3L-EK RTC logical view.
The AT32UC3L-EK contains a 32kHz crystal connected to the AT32UC3L064.
18
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
Figure 3-13. AT32UC3L-EK bottom view 32kHz crystal location.
3.5.2 Schematics
In Section 2.4.2, The AT32UC3L-EK schematics, the RTC block is described on page
1.
3.5.3 UC3L-specific information
3.5.3.1 Atmel AT32UC3L064 pinout for the RTC block
Table 3-13. UC3L pinout for the 32kHz crystal connections.
QFP48 pin
GPIO
GPIO alternate functions
Feature
26
PA13
N.A. XIN32_2
Crystal 32kHz input
25
PA20
N.A. XOUT32_2
Crystal 32kHz output
3.5.4 Configuration and test points
3.5.4.1 Configuration
Not applicable.
3.5.4.2 Test points
Two test points covering the RTC block have been placed on the Atmel AT32UC3LEK for the verification of important signals.
Table 3-14. RTC block test points.
Designation
Feature
TP2
Crystal 32kHz output
TP4
Crystal 32kHz input
To locate the test points mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
19
32150B-AVR-03/12
3.6 Expansion interface
The expansion interface on the AT32UC3L-EK offers the possibility to connect
various external devices to the AT32UC3L064.
3.6.1 Overview
Figure 3-14. Atmel AT32UC3L-EK expansion interface logical view.
There are two expansion headers on the AT32UC3L-EK:
• The J8 header (labeled WLESS on the PCB) connects the Atmel RZ600
AT86RF231 radio board to provide wireless communication capabilities to the kit.
Signals on J8.1 and J8.2 are configurable with the J44 header. The Atmel
AT32UC3L064 modules available on J8 are USART1 and SPI0. Depending on the
J44 configuration, TWI0 is available too
• The J14 and J15 headers provide access to the AT32UC3L064’s GPIOs, ground,
and VCC3. This offers the possibility to check signals and/or to expand the board
with additional hardware
20
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
Figure 3-15. AT32UC3L-EK top view expansion headers location.
3.6.2 Schematics
In Section 2.4.2, The AT32UC3L-EK schematics, the expansion headers are
described:
• On page 4 for the wireless J8+J44 headers
• On page 7 for the J14 and J15 headers
3.6.3 UC3L-specific information
3.6.3.1 Atmel AT32UC3L064 pinouts for the expansion headers
Table 3-15. UC3L pinouts for the J8 and J44 headers.
QFP48 pin
GPIO
GPIO alternate functions
Feature
11
PA00
USART1.RTS or GPIO[0]
Provides access to the USART1.RTS
signal or to the Atmel RZ600.RST
feature.
Available on J8.1 if J44 is configured
with a jumper connecting J44.3 to
J44.5
14
PA01
USART1.CTS or GPIO[1]
Provides access to the USART1.CTS
signal or to the RZ600.MISC feature.
Available on J8.2 if J44 is configured
with a jumper connecting J44.4 to
J44.6
4
PA03
SPI0.NPCS[1]
RZ600 SPI chip select. Available on
J8.5
28
PA04
SPI0.MISO
RZ600.MISO signal. Available on
J8.7
28
PA04
TWI0.TWCK
Provides access to the TWI0 TWCK
signal. Available on J8.2 if J44 is
configured with a jumper connecting
J44.2 to J44.4
12
PA05
SPI0.MOSI
RZ600.MOSI signal. Available on
J8.6
21
32150B-AVR-03/12
QFP48 pin
GPIO
GPIO alternate functions
Feature
12
PA05
TWI0.TWD
Provides access to the TWI0 TWD
signal. Available on J8.1 if J44 is
configured with a jumper connecting
J44.1 to J44.3
10
PA06
SPI0.SCK
RZ600 SPI clock. Available on J8.8
3
PA08
USART1.TX or GPIO[8]
Provides access to the
RZ600.SLP_TR feature or to the
USART1.TX signal. Available on J8.4
2
PA09
USART1.RX or GPIO[9]
Provides access to the RZ600.IRQ
feature or to the USART1.RX signal.
Available on J8.3
N.A.
N.A.
N.A.
GND. Available on J8.9
N.A.
N.A.
N.A.
VCC3. Available on J8.10
Table 3-16. UC3L pinout for the J14 header.
QFP48 pin
GPIO
GPIO alternate functions
Feature
11
PA00
Software-dependant
J14.1
14
PA01
Software-dependant
J14.3
13
PA02
Software-dependant
J14.5
4
PA03
Software-dependant
J14.7
28
PA04
Software-dependant
J14.9
12
PA05
Software-dependant
J14.11
10
PA06
Software-dependant
J14.13
15
PA07
Software-dependant
J14.15
3
PA08
Software-dependant
J14.17
-
-
-
GND on J14.19
-
-
-
VCC3 on J14.2
2
PA09
Software-dependant
J14.4
46
PA10
Software-dependant
J14.6
27
PA11
Software-dependant
J14.8
47
PA12
Software-dependant
J14.10
26
PA13
Software-dependant
J14.12
36
PA14
Software-dependant
J14.14
37
PA15
Software-dependant
J14.16
38
PA16
Software-dependant
J14.18
39
PA17
Software-dependant
J14.20
Table 3-17. UC3L pinout for the J15 header.
22
QFP48 pin
GPIO
GPIO alternate functions
Feature
41
PA18
Software-dependant
J15.1
40
PA19
Software-dependant
J15.3
25
PA20
Software-dependant
J15.5
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
QFP48 pin
GPIO
GPIO alternate functions
Feature
24
PA21
Software-dependant
J15.7
9
PA22
Software-dependant
J15.9
6
PB00
Software-dependant
J15.11
16
PB01
Software-dependant
J15.13
7
PB02
Software-dependant
J15.15
8
PB03
Software-dependant
J15.17
-
-
-
GND on J15.19
-
-
-
VCC3 on J15.2
21
PB04
Software-dependant
J15.4
20
PB05
Software-dependant
J15.6
30
PB06
Software-dependant
J15.8
31
PB07
Software-dependant
J15.10
32
PB08
Software-dependant
J15.12
29
PB09
Software-dependant
J15.14
23
PB10
Software-dependant
J15.16
44
PB11
Software-dependant
J15.18
5
PB12
Software-dependant
J15.20
3.6.4 Configuration and test points
3.6.4.1 Configuration
The J8.1 and J8.2 pins are configurable through the J44 header. Refer to Table 3-15.
UC3L pinouts for the J8 and J44 headers., for a description of the possible
configurations.
3.6.4.2 Test points
None.
3.6.4.3 Special consideration when using the expansion headers
The J8+J44 expansion headers gather signals multiplexed with the JTAG signals on
J8.1, J8.2, and J8.5. For this reason, JTAG debugging is not possible when an
external component is connected to these pins of the WLESS header. See also
Section 3.3.4.1, Special considerations for the RESET_N pin and the JTAG pins.
The J14 and J15 headers gather all GPIO signals of the Atmel AT32UC3L064.
Obvious care should be taken when accessing pins that are being used by another
component of the kit.
3.7 USB interface
The USB interface on the Atmel AT32UC3L-EK offers USB communication
capabilities to the AT32UC3L064 through the on-board Atmel AT32UC3B1256
device.
23
32150B-AVR-03/12
3.7.1 Overview
Figure 3-16. Atmel AT32UC3L-EK USB interface logical view.
The USB interface provides two features to the AT32UC3L-EK kit:
• USB communication
• Power supply (see Section 3.1, Power supply for a description of that feature)
The USB controller is the Atmel AT32UC3B1256.
The AT32UC3B1256 comes pre-loaded with several firmware components:
• A USB DFU boot loader [accessible upon power up when the J12 header is closed
(see Figure 3-17. Atmel AT32UC3L-EK top view USB interface location., for the
location of the J12 header)] to re-program the AT32UC3B1256
• A USB CDC-USART bridge (a USB CDC virtual com port) where every data
character received from the USB is sent to the Atmel AT32UC3L064’s USART3,
and every character received from the AT32UC3L064’s USART3 is sent to the
USB
• A HID QTouch Debug firmware acting as a USB HID-USART bridge between AVR
QTouch Studio (Section 2.4.8) and the AT32UC3L064’s USART3
• A tiny boot selector allowing the user to choose (using the USB MODE
pushbutton) upon power up between running the virtual com port firmware or the
HID QTouch Debug firmware. By default the HID QTouch Debug firmware will be
running. See also Section 2.4.3
The source code of this firmware is available in the Atmel AVR Software Framework
(Section 2.4.5).
The user interface of the USB interface block is made of:
24
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
• Two LEDs, D12 and D13, [with the default firmware (except the USB DFU boot
loader) these LEDs are blinking, depending on the activity over the USB]
• The USB MODE pushbutton on the PCB. With the default pre-loaded firmware,
this button is used at power up to choose between the virtual com port firmware or
the HID QTouch Debug firmware (see Section 3.7.4.1, AT32UC3LB1256 default
firmware configuration)
The Atmel AT32UC3B256 can be programmed:
• Through the JTAG interface J13 header (see Figure 3-18. Atmel AT32UC3L-EK
bottom view USB interface location. for the location of the J13 header)
• Through the USB DFU boot loader running on the Atmel AT32UC3B, accessible
upon power up when the J12 header is closed
IMPORTANT
Programming the Atmel AT32UC3B1256 will overwrite the default firmware.
The AT32UC3B1256 can be programmed and debugged through the JTAG interface
J13 header.
The AT32UC3B1256 is connected to the Atmel AT32UC3L064’s USART3 TX and RX
pins.
Figure 3-17. Atmel AT32UC3L-EK top view USB interface location.
25
32150B-AVR-03/12
Figure 3-18. Atmel AT32UC3L-EK bottom view USB interface location.
J13
UC3B
3.7.2 Schematics
In Section 2.4.2, The AT32UC3L-EK schematics, the USB interface block is
described on page 6.
3.7.3 UC3L-specific information
3.7.3.1 Atmel T32UC3L064 pinout for the USB interface block
Table 3-18. UC3L pinout for the USB interface block.
QFP48 pin
GPIO
GPIO alternate functions
Feature
6
PB00
USART3.TXD
USART3 TX line
16
PB01
USART3.RXD
USART3 RX line
3.7.4 Configuration and test points
3.7.4.1 AT32UC3LB1256 default firmware configuration
The default firmware pre-loaded on the Atmel AT32UC3B1256 is dynamically
configurable upon power up:
• The USB DFU boot loader can be enabled by closing the J12 jumper. Use
flip/batchisp to read/write resources on the AT32UC3B1256 through the boot
loader
IMPORTANT
Programming the AT32UC3B1256 will overwrite the default firmware.
• If the USB MODE pushbutton is pressed at power up, the USB virtual com port
firmware will execute. Otherwise, the USB HID QTouch Debug firmware will
execute
3.7.4.2 Test points
A few test points covering the USB interface block have been placed on the Atmel
AT32UC3L-EK for the verification of important signals.
26
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
Table 3-19. USB interface block test points.
Designation
Feature
TP31
VBUS
TP32
D-
TP33
D+
TP34
GND
TP35
JTAG.TCK.UC3B
TP36
JTAG.TDO.UC3B
TP37
JTAG.TMS.UC3B
TP38
JTAG.TDI.UC3B
TP39
RESET_N.UC3B
TP41
USB MODE pushbutton state
To locate the test points mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
3.8 Atmel AT32UC3L064
The AT32UC3L064 is the central point of the Atmel AT32UC3L-EK.
3.8.1 Overview
See Figure 2-1. AT32UC3L-EK block diagram., for a logical view of the
AT32UC3L064 in the kit.
The AT32UC3L064 is powered from the power supply block. It can read the current
battery voltage (through an ADCIFB channel), and may control the power supply
block through the Power-Off signal. For a detailed presentation of the power supply
block, see Section 3.1, Power supply.
The AT32UC3L064 is in charge of the main user interface block:
• The touch sensors
• The LEDs LED0-4
• The WAKE pushbutton
• The RST pushbutton
• The three-axis accelerometer
For a detailed presentation of the user interface block, see Section 3.2, User
interface.
The AT32UC3L064 can be programmed and debugged through the programming and
debugging interface block that provides JTAG or aWire access. For a detailed
presentation of the programming and debugging interface block, see Section 3.3,
Programming and debugging interface.
The AT32UC3L064 has access to one external on-board Atmel DataFlash 64Mbit
memory. For a detailed presentation of the external memory block, see Section 3.4,
External memory.
A 32kHz crystal is connected to the AT32UC3L064 to support the lowest sleep
modes, and to provide the RTC feature. For a detailed presentation of the RTC block,
see Section 3.5, RTC.
27
32150B-AVR-03/12
The expansion interface offers the possibility to connect various external devices to
the Atmel AT32UC3L064. The J8 header (labeled WLESS on the PCB) connects an
Atmel RZ600 AT86RF231 radio board (not provided with this board) to provide
wireless capabilities to the kit. Obviously, dedicated firmware must be running on the
AT32UC3L064 to support this feature. The J14 and J15 headers provide access to all
of the AT32UC3L064’s GPIOs. For a detailed presentation of the expansion interface
block, see Section 3.6, Expansion interface.
To provide USB communication capabilities to the kit, the AT32UC3L064 accesses
the USB interface block through the USART3 RX and TX signals. The USB interface
block main component is the Atmel AT32UC3B1256 device, pre-loaded with several
default firmware components providing added features to the kit. For a detailed
presentation of the USB interface block, see Section 3.7, USB interface.
Figure 3-19. Atmel AT32UC3L-EK top view AT32UC3L064.
3.8.2 Schematics
The schematic of the AT32UC3L064 is on page 1 in the document mentioned in
Section 2.4.2, The AT32UC3L-EK schematics.
3.8.3 AT32UC3L064 pinout
Table 3-20. UC3L pinout.
28
QFP48 Pin
GPIO
GPIO alternate functions
Feature
33
N.A.
N.A.
GNDANA
34
N.A.
N.A.
ADVREFP
1
N.A.
N.A.
GND
19
N.A.
N.A.
GND
43
N.A.
N.A.
GND
45
N.A.
N.A.
GND
22
N.A.
N.A.
RESET_N
35
N.A.
N.A.
VDDANA
17
N.A.
N.A.
VDDIN
18
N.A.
N.A.
VDDCORE
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
QFP48 Pin
GPIO
GPIO alternate functions
Feature
48
N.A.
N.A.
VDDIO
42
N.A.
N.A.
VDDIO
11
PA00
JTAG.TCK / USART1.RTS /
GPIO[0]
JTAG_TCK / WZ_U1_RTS /
WZ_RZ600_RST
14
PA01
JTAG.TMS / USART1.CTS /
GPIO[1]
JTAG_TMS / WZ_U1_CTS /
WZ_RZ600_MISC
13
PA02
JTAG.TDO
JTAG TDO
4
PA03
JTAG.TDI / GPIO[3] /
SPI.NPCS[1]
JTAG_TDI / POWER_OFF /
WZ_RZ600_CS
28
PA04
SPI.MISO / TWIMS0.TWCK
DF_MISO / WZ_MISO / WZ_TW0CK
12
PA05
SPI.MOSI / TWIMS0.TWD
DF_MOSI / WZ_MOSI / WZ_TW0D
10
PA06
SPI.SCK
DF_SCK / WZ_RZ600_SCK
15
PA07
SPI.NPCS[0]
DF_CS
3
PA08
USART1.TXD / GPIO[8]
WZ_U1_TX / WZ_RZ600_SLPTR
2
PA09
USART1.RXD / GPIO[9]
WZ_U1_RX / WZ_RZ600_IRQ
46
PA10
CAT.CSA[5]
TOUCH_Y2
27
PA11
GPIO[11]
WAKE push button
47
PA12
CAT.CSB[5]
TOUCH_YK2
26
PA13
XIN32_2
RTC
36
PA14
CAT.CSA[6]
TOUCH_X6
37
PA15
CAT.CSB[6]
TOUCH_X7
38
PA16
ACIFB.ACREFN
TOUCH_ACREFN
39
PA17
CAT.SMP
TOUCH_SMP
41
PA18
ADCIFB[4]
VBAT
40
PA19
CAT.CSA[10]
TOUCH_X10
25
PA20
XOUT32_2
RTC
24
PA21
GPIO[21] / TC0.B1 /
PWMA[21] / SCIF.GCLK0
LED_0
9
PA22
CAT.CSB[10]
TOUCH_X11
6
PB00
USART3.TXD
USBGW_UC3L_TX
16
PB01
USART3.RXD
USBGW_UC3L_RX
7
PB02
GPIO[34] / TC0.A2 /
PWMA[25] / SCIF.GCLK1
LED_2
8
PB03
GPIO[35] / TC0.B2 /
PWMA[26] / TC1.A2
LED_3
21
PB04
CAT.CSA[14]
TOUCH_X14
20
PB05
CAT.CSB[14]
TOUCH_X15
30
PB06
ADCIFB[6]
ACC_X
31
PB07
ADCIFB[7]
ACC_Y
32
PB08
ADCIFB[8]
ACC_Z
29
PB09
CAT.CSA[15]
TOUCH_YK7
29
32150B-AVR-03/12
NOTE
QFP48 Pin
GPIO
GPIO alternate functions
Feature
23
PB10
GPIO[42] / GLOC.OUT[1] /
PWAM[33]
LED_1
44
PB11
CAT.VDIVEN
CAT-VDIVEN
5
PB12
CAT.CSA[15]
TOUCH_Y7
Some pins offer multiple GPIO alternate function configuration, while others don’t. For
example, for LED1 (PB10), it is possible to drive the intensity of the LED through a
regular GPIO function or through the PWMA function multiplexed on this pin.
However, for TOUCH_Y7 (PB12), if the GPIO function configuration is different than
CAT.CSA[15], the touch interface of this board won’t be functional.
3.8.4 Configuration and test points
3.8.4.1 Configuration
A UART boot loader is pre-loaded on the Atmel AT32UC3L064. To enter this boot
loader mode, the WAKE pushbutton must be pressed upon reset and then released.
It is then possible to program the AT32UC3L064 through the UART boot loader. Note
also that if the Atmel AT32UC3B1256 is running the pre-loaded virtual com port
firmware, it is possible to program the AT32UC3L064 with the UART boot loader
through the USB. For detailed information on the AVR UC3 UART boot loader, see
Section 2.4.6.
3.8.4.2 Test points
A few test points covering the AT32UC3L064 have been placed on the Atmel
AT32UC3L-EK for the verification of important signals.
Table 3-21. AT32UC3L064 test points.
Designation
Feature
TP3
GNDANA
TP5
GND
TP6
VDDANA
To locate the test points mentioned here above, use the assembly top/bottom views
provided in Section 2.4.2, The AT32UC3L-EK schematics.
30
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
4 Schematics and assembly top/bottom views
See Section 2.4.2.
31
32150B-AVR-03/12
5 Errata
5.1 While using the touch sensors, if the bottom side is touched, the touch events are wrong
Workaround: when demonstrating the touch feature on the kit, the bottom side of the
PCB must not be in contact with fingers or any external object.
5.2 The pin-through holes near the touch sensors may cause spurious touch events
On some Atmel AT32UC3L-EK kits, the pin-through holes are not protected, causing
spurious touch events when the fingers are not exactly on the touch sensors.
Workaround: when demonstrating the touch feature on this kit, the user must make
sure to touch the sensor-delimited PCB areas only and nowhere else on the PCB.
5.3 The kit will not operate if power-hungry add-ons are connected to the expansion headers
Workaround: the kit must not be used with external add-ons consuming more than
100mA.
NOTE
The Atmel RZ600 radio board has very low power consumption and can be used with
this kit safely.
5.4 The RZ600 radio boards as well as RZ600 USB dongle are not more included in the kit
Workaround: Purchase the RZ600 kits separately.
32
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
6 Evaluation board/kit – important notice
This evaluation board/kit is intended for use for FURTHER ENGINEERING,
DEVELOPMENT, DEMONSTRATION, OR EVALUATION PURPOSES ONLY. It is
not a finished product and may not (yet) comply with some or any technical or legal
requirements that are applicable to finished products, including, without limitation,
directives regarding electromagnetic compatibility, recycling (WEEE), FCC, CE or UL
(except as may be otherwise noted on the board/kit). Atmel supplied this board/kit
“AS IS,” without any warranties, with all faults, at the buyer’s and further users’ sole
risk. The user assumes all responsibility and liability for proper and safe handling of
the goods. Further, the user indemnifies Atmel from all claims arising from the
handling or use of the goods. Due to the open construction of the product, it is the
user’s responsibility to take any and all appropriate precautions with regard to
electrostatic discharge and any other technical or legal concerns.
EXCEPT TO THE EXTENT OF THE INDEMNITY SET FORTH ABOVE, NEITHER
USER NOR ATMEL SHALL BE LIABLE TO EACH OTHER FOR ANY INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES.
No license is granted under any patent right or other intellectual property right of
Atmel covering or relating to any machine, process, or combination in which such
Atmel products or services might be or are used.
Mailing Address: Atmel Corporation, 2325 Orchard Parkway, San Jose, CA 95131.
33
32150B-AVR-03/12
7 Table of contents
Features ............................................................................................... 1
1 Introduction ...................................................................................... 1
2 Kit overview...................................................................................... 2
2.1 Features .............................................................................................................. 3
2.2 Kit content............................................................................................................ 4
2.3 Power up and getting started .............................................................................. 4
2.4 References .......................................................................................................... 4
2.4.1 The AVR UC3 L0 series datasheet ........................................................................... 4
2.4.2 The AT32UC3L-EK schematics................................................................................. 4
2.4.3 The AVR32777: AT32UC3L-EK Getting Started document....................................... 4
2.4.4 The 32-bit AVR UC3 L series schematic checklist .................................................... 5
2.4.5 The Atmel AVR Software Framework........................................................................ 5
2.4.6 The Atmel AVR UC3 UART boot loader .................................................................... 5
2.4.7 The Atmel QTouch Library ........................................................................................ 5
2.4.8 Atmel AVR QTouch Studio ........................................................................................ 5
2.4.9 Debuggers................................................................................................................. 5
3 Hardware description ...................................................................... 6
3.1 Power supply ....................................................................................................... 6
3.1.1 Overview ................................................................................................................... 6
3.1.2 Schematics................................................................................................................ 7
3.1.3 UC3L-specific information ......................................................................................... 7
3.1.4 Configurations and test points ................................................................................... 8
3.1.5 Power consumption measurement ............................................................................ 9
3.2 User interface .................................................................................................... 10
3.2.1 Overview ................................................................................................................. 10
3.2.2 Schematics.............................................................................................................. 11
3.2.3 UC3L-specific information ....................................................................................... 12
3.2.4 Configuration and test points................................................................................... 13
3.3 Programming and debugging interface ............................................................. 13
3.3.1 Overview ................................................................................................................. 14
3.3.2 Schematics.............................................................................................................. 14
3.3.3 UC3L-specific information ....................................................................................... 14
3.3.4 Configuration and test points................................................................................... 15
3.4 External memory ............................................................................................... 16
3.4.1 Overview ................................................................................................................. 16
3.4.2 Schematics.............................................................................................................. 17
3.4.3 UC3L-specific information ....................................................................................... 17
3.4.4 Configuration and test points................................................................................... 17
3.5 RTC ................................................................................................................... 18
3.5.1 Overview ................................................................................................................. 18
3.5.2 Schematics.............................................................................................................. 19
3.5.3 UC3L-specific information ....................................................................................... 19
3.5.4 Configuration and test points................................................................................... 19
3.6 Expansion interface........................................................................................... 20
34
Atmel AVR32025
32150B-AVR-03/12
Atmel AVR32025
3.6.1 Overview ................................................................................................................. 20
3.6.2 Schematics.............................................................................................................. 21
3.6.3 UC3L-specific information ....................................................................................... 21
3.6.4 Configuration and test points................................................................................... 23
3.7 USB interface .................................................................................................... 23
3.7.1 Overview ................................................................................................................. 24
3.7.2 Schematics.............................................................................................................. 26
3.7.3 UC3L-specific information ....................................................................................... 26
3.7.4 Configuration and test points................................................................................... 26
3.8 Atmel AT32UC3L064 ........................................................................................ 27
3.8.1 Overview ................................................................................................................. 27
3.8.2 Schematics.............................................................................................................. 28
3.8.3 AT32UC3L064 pinout .............................................................................................. 28
3.8.4 Configuration and test points................................................................................... 30
4 Schematics and assembly top/bottom views .............................. 31
5 Errata .............................................................................................. 32
5.1 While using the touch sensors, if the bottom side is touched, the touch events
are wrong................................................................................................................. 32
5.2 The pin-through holes near the touch sensors may cause spurious touch events
................................................................................................................................. 32
5.3 The kit will not operate if power-hungry add-ons are connected to the expansion
headers.................................................................................................................... 32
5.4 The RZ600 radio boards as well as RZ600 USB dongle are not more included
in the kit ................................................................................................................... 32
6 Evaluation board/kit – important notice....................................... 33
7 Table of contents ........................................................................... 34
35
32150B-AVR-03/12
Atmel Corporation
2325 Orchard Parkway
San Jose, CA 95131
USA
Tel: (+1)(408) 441-0311
Fax: (+1)(408) 487-2600
www.atmel.com
Atmel Asia Limited
Unit 01-5 & 16, 19F
BEA Tower, Milennium City 5
418 Kwun Tong Road
Kwun Tong, Kowloon
HONG KONG
Tel: (+852) 2245-6100
Fax: (+852) 2722-1369
Atmel Munich GmbH
Business Campus
Parkring 4
D-85748 Garching b. Munich
GERMANY
Tel: (+49) 89-31970-0
Fax: (+49) 89-3194621
Atmel Japan
16F, Shin Osaki Kangyo Bldg.
1-6-4 Osaki Shinagawa-ku
Tokyo 104-0032
JAPAN
Tel: (+81) 3-6417-0300
Fax: (+81) 3-6417-0370
© 2012 Atmel Corporation. All rights reserved.
®
®
®
®
®
®
Atmel , Atmel logo and combinations thereof, AVR , QTouch , picoPower , DataFlash , and others, are the registered trademarks or
trademarks of Atmel Corporation or its subsidiaries. Other terms and product names may be trademarks of others.
Disclaimer: The information in this document is provided in connection with Atmel products. No license, express or implied, by estoppel or otherwise, to
any intellectual property right is granted by this document or in connection with the sale of Atmel products. EXCEPT AS SET FORTH IN THE ATMEL
TERMS AND CONDITIONS OF SALES LOCATED ON THE ATMEL WEBSITE, ATMEL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS
ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL ATMEL BE
LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION,
DAMAGES FOR LOSS AND PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO
USE THIS DOCUMENT, EVEN IF ATMEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Atmel makes no representations or
warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and
product descriptions at any time without notice. Atmel does not make any commitment to update the information contained herein. Unless specifically
provided otherwise, Atmel products are not suitable for, and shall not be used in, automotive applications. Atmel products are not intended, authorized, or
warranted for use as components in applications intended to support or sustain life.
32150B-AVR-03/12
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising