View detail for Xplained Pro Hardware Development Kit (HDK) User Guide

Atmel MCUs
Xplained Pro Hardware Development Kit (HDK)
USER GUIDE
Hardware Development Kit
®
The Atmel Hardware Development Kit (HDK) provides all necessary
information for a developer to make hardware that is compatible with Atmel
Xplained Pro products, integrate it with Atmel Studio and add example
firmware.
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
Table of Contents
Hardware Development Kit..............................................................................................1
1. Introduction................................................................................................................ 4
1.1.
1.2.
1.3.
Compatible Xplained Pro Hardware............................................................................................. 4
Studio Integration......................................................................................................................... 5
Example Code..............................................................................................................................5
2. Xplained Pro Hardware Platform............................................................................... 6
2.1.
2.2.
2.3.
2.4.
2.5.
2.6.
2.7.
Naming Convention......................................................................................................................6
2.1.1.
Product Hierarchy.......................................................................................................... 6
2.1.2.
Xplained Pro Main Board Naming Convention.............................................................. 6
2.1.3.
Xplained Pro Extension Naming Convention.................................................................6
2.1.4.
Silkscreen Text...............................................................................................................7
Embedded Debugger................................................................................................................... 8
Xplained Pro Analog Module (XAM).............................................................................................8
2.3.1.
Overview........................................................................................................................8
2.3.2.
EDBG Interface..............................................................................................................9
2.3.3.
Sample Rate................................................................................................................ 10
2.3.4.
Measurement Ranges and Accuracy...........................................................................10
Xplained Pro ID System............................................................................................................. 10
2.4.1.
Overview......................................................................................................................10
2.4.2.
ID System Implementation on Extensions................................................................... 11
2.4.3.
ID Device Data.............................................................................................................12
2.4.4.
Data Encoding............................................................................................................. 12
2.4.5.
Creating Your Own ID Data......................................................................................... 13
2.4.6.
Programming the ID Device.........................................................................................13
Xplained Pro Connectors............................................................................................................14
2.5.1.
Extension Header Numbering......................................................................................14
2.5.2.
Xplained Pro Standard Extension Header................................................................... 15
2.5.3.
Xplained Pro Power Header........................................................................................ 20
2.5.4.
Current Measurement Header..................................................................................... 21
2.5.5.
Xplained Pro Segment LCD Connector....................................................................... 21
2.5.6.
Xplained Pro LCD Extension Connector......................................................................22
Power Specifications.................................................................................................................. 24
2.6.1.
Typical Power Supply Implementations....................................................................... 25
Board Stacking Options..............................................................................................................26
3. Xplained Pro MCU Boards.......................................................................................31
3.1.
3.2.
Standard On-board Features..................................................................................................... 31
3.1.1.
Embedded Debugger (EDBG)..................................................................................... 31
3.1.2.
Reset Button................................................................................................................ 32
3.1.3.
Wake-up/Bootloader/User Button................................................................................ 32
3.1.4.
Current Measurement Header..................................................................................... 32
Mechanical Dimensions and Component Placement.................................................................32
3.2.1.
Plastic Isolation Bumpers............................................................................................ 32
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
2
3.2.2.
Component Height.......................................................................................................32
3.2.3.
3.2.4.
3.2.5.
Mounting Holes............................................................................................................33
Board Sizes................................................................................................................. 33
Connector and Header Placement.............................................................................. 35
4. Xplained Pro Extensions..........................................................................................39
4.1.
Extension Board Templates........................................................................................................39
4.1.1.
Designing a Board with the Standard Extension Header.............................................39
4.1.2.
Designing a Board with the Segment LCD Connector.................................................52
4.1.3.
Designing a Board with the LCD connector.................................................................53
5. Xplained Pro Extensions in Atmel Studio................................................................ 63
5.1.
Xplained Pro Landing Page........................................................................................................63
6. Appendix..................................................................................................................64
6.1.
6.2.
Xplained Pro I2C Address List.................................................................................................... 64
id_tool Version History................................................................................................................65
6.2.1.
Version 1.0...................................................................................................................65
6.2.2.
Version 0.5...................................................................................................................65
7. Document Revision History..................................................................................... 66
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
3
1.
Introduction
The Hardware Development Kit (HDK) describes how to integrate an Xplained Pro design seamlessly into
the Atmel tools and software offering. Three requirements must be fulfilled in order to accomplish this
task:
1.
2.
3.
Compatible hardware.
Atmel Studio integration.
Example code.
When all these requirements are fulfilled a good user experience is achieved because each step in the
evaluation process is covered and the user has easy access to everything needed.
1.1.
Compatible Xplained Pro Hardware
The Xplained Pro platform consists of several standardized building blocks that need to work together for
the system to work. Otherwise interoperability issues may occur where extensions cannot be connected
due to incompatible pinout or the hardware identification system does not work. Typical hardware building
blocks on the Xplained Pro platform are:
•
Standardized pinout and position for extension headers
•
Standardized board sizes
•
Embedded Debugger (EDBG)
•
Hardware identification system
•
Xplained Pro Analog Module (XAM)
The Hardware Development Kit provides all information that is necessary to create an Xplained Pro
product that is compatible with the Xplained Pro platform. The above building blocks are described in this
document.
Figure 1-1 Typical Xplained Pro Hardware
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
4
1.2.
Studio Integration
When Atmel Studio detects Xplained Pro compatible hardware it will search for a landing page for it and
present it to the user. The landing page contains:
•
Short description of the kit
•
Picture of the kit
•
Links to kit documentation
•
Links to relevant datasheets
•
Link that opens a list with relevant applications for this kit (filtered ASF examples list)
•
Link to places where the kit can be bought
Other information on the landing page is obtained directly from the connected hardware via the kit
identification system e.g. revision, capabilities, serial number, etc.
If no landing page is found the user will be requested to update the Atmel Kits extension from the Atmel
Gallery.
Related Links
Xplained Pro Landing Page on page 63
1.3.
Example Code
The final step of the integration is addition of example code for the hardware. This is described in detail in
the Software Development Kit (SDK). The SDK is available at the Atmel Gallery Partner site.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
5
2.
Xplained Pro Hardware Platform
2.1.
Naming Convention
2.1.1.
Product Hierarchy
The Xplained Pro platform consists of several boards, kits, and bundles. It is important to be accurate and
consistent in all documentation when describing a physical Xplained Pro product.
The assembled PCB with components is an Xplained Pro board where:
•
The microcontroller (MCU) board can be referred to as an Xplained Pro MCU board or Xplained Pro
main board.
•
The extension can be referred to as an Xplained Pro extension or Xplained Pro extension board
A (cardboard) box containing one Xplained Pro board is called an Xplained Pro kit. A kit always contains
at least one Xplained Pro board, and may also contain additional components such as cables, storage
media, or a display module. There are three types of Xplained Pro kits:
•
A kit containing one MCU Xplained Pro board should be referred to as an Xplained Pro Evaluation
Kit
•
A kit containing one Xplained Pro extension should be referred to as an Xplained Pro Extension kit
•
A kit containing several kits including cables and everything a new user needs to get started is
called an Xplained Pro Starter Kit
Examples:
•
SAM4L Xplained Pro MCU board
•
SAM4L Xplained Pro Evaluation Kit
•
SAM4L Xplained Pro Starter Kit
•
OLED1 Xplained Pro Extension
•
OLED1 Xplained Pro Extension Kit
2.1.2.
Xplained Pro Main Board Naming Convention
All boards of the product family are named based on the following scheme:
[device_series_name] Xplained Pro
Examples:
•
•
•
UC3 L Xplained Pro
SAM4L Xplained Pro
®
XMEGA A1U Xplained Pro
The above suggestions only work if only one product for the MCU family exists. When sub family products
are made it is required to add the sub-series part of the MCU name (or the memory size indicator for kits
that have a new memory size derivate).
Examples:
•
UC3 A3 Xplained Pro
•
SAM4LC Xplained Pro
•
SAM4L8 Xplained Pro
2.1.3.
Xplained Pro Extension Naming Convention
All boards of the product family are named based on the following scheme:
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
6
[device/technology] Xplained Pro
In addition it is possible to extend the name with a sub-part that is used to differentiate products within a
product line.
•
•
•
Sensors Xplained Pro Inertial
Sensors Xplained Pro Pressure
Security Xplained Pro Authentication
When several extensions exist with the same name and sub-naming, these can be distinguished by
adding a number:
•
•
•
2.1.4.
Sensors Xplained Pro Inertial One
OLED1 Xplained Pro
I/O1 Xplained Pro
Silkscreen Text
The board name on the PCB itself is all in capital letters, where the X in Xplained is the double font size
than the rest of the letters. The “PRO” is attached at the end with half the font size. For example 2mm
height for standard text, 4mm height for the X, and 1mm height for the “PRO”. The font size used in the
below example is Verdana with a 0.5mm inverted border.
Figure 2-1 MCU Board Silkscreen Naming Example 1
Figure 2-2 MCU Board Silkscreen Naming Example 2
Figure 2-3 Extension Silkscreen Naming Example 1
Figure 2-4 Extension Silkscreen Naming Example 2
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
7
2.2.
Embedded Debugger
The Xplained Pro contains the Atmel Embedded Debugger (EDBG) for on-board debugging. The EDBG
is a composite USB device of three interfaces; a debugger, Virtual COM Port, and a Data Gateway
Interface (DGI).
Together with Atmel Studio, the EDBG debugger interface can program and debug the target device. On
Xplained Pro, the programming interface is connected between the EDBG and the target device.
The Virtual COM Port is connected to a UART on the target device and provides an easy way to
communicate with the target application through terminal software. It offers variable baud rate, parity, and
stop bit settings. Note that the settings on the target device must match the settings given in the terminal
software.
Info: If not set automatically, data terminal ready (DTR) must be set in the terminal software.
The DGI consists of several physical interfaces for communication with the host computer.
Communication over the interfaces is bidirectional. It can be used to send events and values from the
target device or as a generic printf-style data channel. Traffic over the interfaces can be timestamped on
the EDBG for more accurate tracing of events. Note that timestamping imposes an overhead that reduces
maximal throughput. Atmel Data Visualizer is used to send and receive data through DGI.
The EDBG controls two LEDs on Xplained Pro; a power LED and a status LED. Table 2-1 EDBG LED
Control on page 8 shows how the LEDs are controlled in different operation modes.
Table 2-1 EDBG LED Control
Operation mode
Power LED
Status LED
Normal operation
Power LED is lit when power is
applied to the board.
Activity indicator, LED flashes
when any communication
happens to the EDBG.
Bootloader mode (idle)
The power LED and the status LED blinks simultaneously.
Bootloader mode (firmware
upgrade)
The power LED and the status LED blinks in an alternating pattern.
For further documentation on the EDBG, see the EDBG User Guide.
2.3.
Xplained Pro Analog Module (XAM)
2.3.1.
Overview
The Xplained Pro Analog Module (XAM) extends the embedded debugger with high dynamic range
current measurement. This enables power profiling of the target system.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
8
Current output
Calibration
circuitry
GPIO(s)
Control MCU
Sync
GPIO
I2C
Calibration ON/OFF
GPIO
SPI
EDBG
Clock sync
Range selection
voltage
reference
2.7V
SWD
AREF
100 Ohm
100 mOhm
Pre-amplifier
2x
ADC0
ADC1
20x20x
S&H
ADC
16x
GND
Active filter with
gain
Current input
GPIO
Xplained Pro Analog Module (XAM)
The XAM consists of:
•
•
•
•
Calibration circuitry
Voltage reference
Analog frontend
– Shunt resistors with a range selection switch
– Pre-amplifier
– Two active filters with gain
Control MCU
– Analog to digital converter
– Signal processing
– Control/communication interface to the EDBG
The current measurement frontend is a high side shunt measurement with a pre-amplifier and a second
active filter stage with gain. The wide dynamic range is achieved by four measurement ranges which are
defined by two shunts and the two parallel second stage active filters with gain.
2.3.2.
EDBG Interface
The Xplained Pro Analog Module (XAM) is connected to the EDBG with the following interfaces:
•
•
•
•
•
•
I2C: This is used to control and configure the XAM
SPI: Current measurement data is streamed to the EDBG via this interface. This is a one-way data
transfer channel from the XAM to the EDBG
SWD: The MCU in the XAM is programmed via SWD from the EDBG
GPIO: At least one GPIO that is connected to the EDBG from the target MCU is also connected to
the current measurement unit to enable the user to sync current measurements with his application
Clock sync: Synchronization signal to synchronize ADC measurements with EDBG
Reference clock: Reference clock for the XAM
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
9
2.3.3.
Sample Rate
The raw sampling rate of the Xplained Pro analog module (XAM) is up to 250kHz and with the default
averaging configuration (average of 16 samples) the actual output of the XAM is 16.67kSPS (note that
the XAM output sample rate is not an integer fraction of the raw sampling).
2.3.4.
Measurement Ranges and Accuracy
The Xplained Pro analog module has four measurement ranges. These are defined by two shunt resistors
and two gain stages.
Measurement
range
Hardware
Resolution Accuracy
Comments
Range 1
Low current shunt and
high gain stage
20nA
1 LSB ±1% Below 1μA the error will
increase. Typical error for
300nA is 1 LSB ± 10%
Range 2
Low current shunt and
low gain stage
150nA
1 LSB ±1%
Range 3
High current shunt and
high gain stage
10μA
1 LSB ±1%
Range 4
High current shunt and
low gain stage
100μA
1 LSB ±1% Above 100mA the error will
increase to 1 LSB ±5% at
400mA. Maximum current is
400mA
The ranges are switched automatically by the XAM to achieve best measurement results and the
currently active range is visualized in the Atmel Data Visualizer frontend tool. The maximum voltage drop
over the shunt resistor is 100mV and the XAM will switch the range automatically before this limit is
reached.
2.4.
Xplained Pro ID System
2.4.1.
Overview
Identification of extensions for the Xplained Pro platform is required in order to leverage the ease of use
for Atmel products. The intention of the identification is not to protect the hardware from being copied.
Identified extensions are reported through the Embedded Debugger to the host PC software, which is
Atmel Studio. Based on the detected hardware Atmel Studio will then provide additional information to the
user such as:
•
•
•
Link to user guides and relevant datasheets
Available Atmel Software Framework (ASF) applications for the extension
Extension revision and features
This chapter is important for all developers that want to implement the ID system in a design e.g. on
extensions for Xplained Pro.
The Embedded Debugger (EDBG) is the central part in the overall system as it serves as a gateway
between the hardware and the host PC software. The system block diagram shows the main components
of the system and how they connect to each other. Each extension connector on an Xplained Pro MCU
board has a unique ID channel which is connected to the EDBG and to an ID device on a connected
extension. When the EDBG is powered it will check all ID channels for ID devices, read out the product
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
10
information and store it internally. Once a connection to the host PC software is established the
information can be retrieved and presented to the user.
Figure 2-5 ID System Overview
Xplained Pro extension
ID device
EXT1
Atmel Studio
Embedded
debugger
EXT2
Xplained Pro extension
ID device
Xplained Pro MCU board
2.4.2.
ID System Implementation on Extensions
The ID device that must be mounted on Xplained Pro extensions is the Atmel ATSHA204A in a singlewire configuration where the device is powered through the communication line. On the Atmel Xplained
Pro extensions the device with the ordering code ATSHA204A-MAHCZ-T is used. Relevant features of
the device are:
•
Operation voltage from 2.0V to 5.5V
•
Single wire interface
•
8-lead UDFN (one wire)
•
Data area with 512 bytes
•
Configuration area with 88 bytes
•
One time programmable (OTP) area with 64 bytes
The example in Figure 2-6 ID Device Circuitry on page 12 shows the implemented ID circuitry on the
Xplained Pro extension boards. The ID_DATA signal is routed to the Embedded Debugger where this
signal is pulled-up. The ID chip is powered through the ID_DATA line through an internal diode between
pin 5 and pin 8. R100 acts as a bleeding resistor to discharge C100 when the extension is unplugged, this
is necessary in order to get the ID device in a safe state within a reasonable time before the board is
plugged in again. The ID_DATA line is connected to a dedicated pin on the extension header your
Xplained Pro board implements.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
11
Figure 2-6 ID Device Circuitry
2.4.3.
ID Device Data
The following data must be programmed into the ID device so that the most vital information can be
presented to the user in Atmel Studio.
1.
2.
3.
4.
5.
6.
7.
Manufacturer name.
Product name.
Product revision.
Product serial number.
Minimum supported voltage for the extension board [mV].
Maximum supported voltage for the extension board [mV].
Minimum current that is required to support the extension board [mA].
The product name is the key for a lookup in the available kits list in Atmel Studio and it is therefore vital
that this information is unique and always present. If a kit name cannot be resolved in Atmel Studio it will
be suggested to the user that he or she should update or install the required Atmel Studio extension for
the extension kit. All Atmel extension kits will be identified by the Atmel Studio extension Atmel Kits.
The above data is placed in the OTP (One Time Program) zone, which means once it is programmed into
the ID device memory it can’t be erased or re-written.
2.4.4.
Data Encoding
The data in the ATSHA204 is encoded in the following way. Manufacturer name, product name, product
revision, and serial number are stored as 0 terminated ASCII strings. This allows all the strings to have
variable length. Minimum voltage, maximum voltage, and required current are stored as unsigned 16-bit
integer values at the last six bytes of the OTP memory zone. The byte ordering is big endian.
It is required to know the entire content of the OTP zone before locking it. All unused bytes in the OTP
memory have to be written to a known value. All unused area of the OTP memory, meaning all bytes
between the last ASCII string (terminated with the ‘\0’ character) and the six bytes for the max./min.
values are filled with 0xFF. These bytes are marked as DUMMY BYTES in the example table below.
It is also required to know the entire content of the data memory prior to locking the OTP zone, thus the
entire data memory is filled with 0x00. The data zones are not locked for writing so it is possible, if
desirable, to write updated information about the kit in the data memory. The table below shows an
example of a preprogrammed memory for a fictional extension board called "Sensor Xplained".
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
12
Table 2-2 Exampled Content for the ID Device
Data field
Example content
Data type
Byte position
Manufacturer
Atmel’\0’
ASCII string
OTP[0:5]
Product name
Sensor Xplained’\0’
ASCII string
OTP[6:21]
Product revision
01’\0’
ASCII string
OTP[22:24]
Product serial number
0200000002’\0’
ASCII string
OTP[25:35]
DUMMY BYTES
0xFF, 0xFF, 0xFF...
Byte
OTP[36:57]
Minimum Voltage [mV]
1600
Unsigned 16-bit integer
OTP[58:59]
Maximum Voltage [mV]
3300
Unsigned 16-bit integer
OTP[60:61]
Required Current [mA]
50
Unsigned 16-bit integer
OTP[62:63]
Info: All ASCII strings are terminated with the value 0x00 (‘\0’)
Info: Four bytes are used for string terminations (‘\0’), six bytes are used for max./min. values
storage. That leaves 54 bytes for ASCII characters. This means that the combination of
manufacturer, product name, revision, and serial number cannot exceed 54 characters.
Info: The minimum and maximum voltage parameters is used if the Xplained Pro boards supports
other target voltages than 3.3V and switching of power (VCC) to the Extension connectors. The
Extension kits voltage range can be read from the ID chip without applying power to the
Extension kit, if the target voltage is within the valid voltage range of the Extension kit power will
be switched on.
2.4.5.
Creating Your Own ID Data
All extensions must have a unique product name and manufacturer so that they can be associated with
available documentation and firmware in Atmel Studio in the future. This means all products must be
registered so that the uniqueness of the name is ensured. To register an Xplained Pro extension module
id send an e-mail to [email protected] with the manufacturer name and product name.
2.4.6.
Programming the ID Device
The ID device can be programmed via the Embedded Debugger that is mounted on Xplained Pro MCU
boards. That means all Xplained Pro MCU boards can act as a programmer for the ID device by
connecting one of the ID signals.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
13
®
Atmel provides a Python CLI for reading and programming ID devices called id_tool. The CLI is tested
with Python 2.7.101. The latest version of the id_tool package can be downloaded from the Atmel
Gallery developer page.
The Python CLI is distributed as source and split in two files; edbg_driver and id_tool. edbg_driver
interfaces cmsis_dap.dll to communicate with an embedded debugger and provides the required
functions to read and program Xplained Pro ID devices. id_tool contains the CLI and that interfaces the
edbg_driver. To get started, run the following command:
C:\Python27\python.exe id_tool.py -h
Info: The id_tool is provided as a CLI that can be used to read and program Xplained Pro ID devices.
The code may be altered to fit a specific manufacturing setup.
Questions or issues regarding Xplained Pro ID programming can be directed to [email protected].
Related Links
id_tool Version History on page 65
2.5.
Xplained Pro Connectors
2.5.1.
Extension Header Numbering
The extension headers are given names EXTn where n ϵ [1…7], n is determined by which ID pin is
connected to the embedded debugger. A header with ID7 signal from the embedded debugger connected
should be called EXT7. PWR, EXT1, EXT2 and EXT3 are standard extension headers that have a
predfined position according to the list below:
•
PWR is right angled at the top right hand side of the board. This header must always be
implemented.
EXT1 is right angled at the top right hand side of the board, located below the PWR header. This
header must always be present.
EXT2 is right angled and at the bottom right hand side of the board. This header is mandatory for
medium and large boards and should not be implemented on small boards.
EXT3 is right angled pointing downwards
•
•
•
All MCU boards have to implement at least PWR, EXT1, EXT2 (on medium and large boards), and EXT3.
EXT4 to EXT7 can be placed differently depending on the board design. EXT4 to EXT7 can either be
standard extension headers or application specific headers.
1
The module should be compatible with other 2.7.x versions of Python too.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
14
Figure 2-7 Example Extension Header Numbering and Placement
2.5.2.
Xplained Pro Standard Extension Header
All Xplained Pro kits have one or more dual row, 20-pin, 100mil extension header. Xplained Pro MCU
boards have male headers, while Xplained Pro extensions have their female counterparts. Note that all
pins are not always connected. All connected pins follow the defined pin-out description in Table 2-3 Xplained Pro Standard Extension Header on page 16.
The extension headers can be used to connect a variety of Xplained Pro extensions to Xplained Pro MCU
boards or to access the pins of the target MCU on Xplained Pro MCU boards directly.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
15
Table 2-3 Xplained Pro Standard Extension Header
2.5.2.1.
Pin number
Name
Description
1
ID
Communication line to the ID chip on an extension board
2
GND
Ground
3
ADC(+)
Analog to digital converter, alternatively positive part of differential
ADC
4
ADC(-)
Analog to digital converter, alternatively negative part of differential
ADC
5
GPIO1
General purpose I/O
6
GPIO2
General purpose I/O
7
PWM(+)
Pulse width modulation, alternatively positive part of differential
PWM
8
PWM(-)
Pulse width modulation, alternatively negative part of differential
PWM
9
IRQ/GPIO
Interrupt request line and/or general purpose I/O
10
SPI_SS_B/
GPIO
Slave select for SPI and/or general purpose I/O
11
I2C_SDA
Data line for I2C interface. Always implemented, bus type.
12
I2C_SCL
Clock line for I2C interface. Always implemented, bus type.
13
UART_RX
Receiver line of target device UART
14
UART_TX
Transmitter line of target device UART
15
SPI_SS_A
Slave select for SPI. Should preferably be unique.
16
SPI_MOSI
Master out slave in line of serial peripheral interface. Always
implemented, bus type.
17
SPI_MISO
Master in slave out line of serial peripheral interface. Always
implemented, bus type.
18
SPI_SCK
Clock for serial peripheral interface. Always implemented, bus type.
19
GND
Ground
20
VCC
Power for extension board
Populating Extension Headers
The number of extension headers and how they are populated will greatly affect the Xplained Pro
platform as a whole. Since there are 20 pins per standard extension header some pins from the target
MCU will be shared between several extension headers. If the pin-out is not done thoroughly there will be
many compatibility issues when several extension modules are connected at the same time. There has to
be some sharing of MCU pins on the extension headers, if not too few headers will be available for the
user.
EXT1 should be a golden extension header meaning this header should not share any of its MCU pins
with other extension headers. Demo code for a specific extension module should always run on EXT1
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
16
without the need to modify the code. For low pin-count devices it might be difficult to achieve this but in all
cases this should be at least attempted.
EXT3 is intended for user interface boards containing displays, buttons etc, and these boards will most
likely be used a lot. For all other standard extension connectors a lower number should have priority over
a connector with a higher number, e.g. EXT2 > EXT4.
Table 2-4 Recommended Priority for the Standard Xplained Pro Extension Header Population
Pin number
Name
Recommendation
1
ID
Always connect to a unique ID line on the embedded
debugger
2
GND
3
ADC(+)
First priority for ADC
4
ADC(-)
Second priority for ADC
5
GPIO1
First priority for GPIO (devices that have USART RTS
hardware support should route this function to this pin)
6
GPIO2
Second priority GPIO (for devices that have USART CTS
hardware support should route this function to this pin)
7
PWM(+)
First priority for PWM
8
PWM(-)
Second priority for PWM
9
IRQ/GPIO
Should be unique if possible, priority 2
10
SPI_SS_B/GPIO
Should be unique if possible, priority 3
11
TWI_SDA
Always implemented
12
TWI_SCL
Always implemented
13
USART_RX
14
USART_TX
15
SPI_SS_A
Should be unique if possible, priority 1
16
SPI_MOSI
Always implemented
17
SPI_MISO
Always implemented
18
SPI_SCK
Always implemented
19
GND
20
VCC
Signals with unique priority should be populated first e.g. SPI_SS_A, then IRQ/GPIO, and lastly
SPI_SS_B/GPIO. After Unique priorities have been filled other signals with the lowest number have the
highest priority e.g. PWM(+), GPIO1 and ADC(+) must be populated before ADC(-), GPIO2 and PWM(-).
SPI, TWI, and UART should always be implemented. SPI and TWI can always be implemented because
they are bus types.
It is not allowed to connect two (or more) MCU signals to one extension connector pin, as this will make
the not used MCU pin unavailable to the designer for alternative use. It is however an option to connect
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
17
one MCU signal to two or more extension connector pins, to ensure that we can make standard
functionality available on all extension connectors.
For devices with hardware flow control for the UART it is beneficial to route these signals to the EXT1
header GPIO pins because these would most likely also be used for this purpose on extension boards
that require these signals. RTS should be routed to GPIO0 and CTS should be routed to GPIO1.
Connecting the flow control signals is not a requirement but it is obvious that following this suggestion will
offer better support for this functionality.
All I/O pins of the target device that are not connected to extension headers should be made easily
accessible. Exceptions for this rule are:
•
•
•
2.5.2.2.
USB differential data signals to improve signal integrity and to prevent the users from directly
touching the signals which can lead to data loss. We have seen that this can lead to a bad user
experience if the USB connection is suddenly reset due to a touch of the user e.g. when he holds
the board in his hand to show a demo.
Crystal oscillator connections: The reason behind this is a possible disturbance of the oscillation
and additional load capacitance.
Any critical signal that would have degraded performance by this additional routing e.g. clock lines
QTouch on MCU and Extension Boards
Xplained boards with devices containing a build-in PTC module should try to overload the Table 2-3 ®
Xplained Pro Standard Extension Header on page 16 functions with QTouch lines to make it compatible
with the QTouch extension boards.
QTouch Design of Small Boards
For small extensions with only one header (EXT1), four Y- and four X-lines are the maximum of touchlines
that can be expected to be available for compatibility for the series of small MCU boards. Both the MCU
and the extension board should be designed with this rule set.
For compatibility with some of the first extension boards Y-lines noted in parentheses might optionally be
implemented on the MCU board, but this should only be done with XY-capable QTouch lines for (Y-line 5
and 6).
Table 2-5 Recommended Priority for PTC Signals on One Header Boards (EXT1)
Pin
number
EXT1
MCU board
Extension board
Recommendation
3
Y-line 1
Y-line 1
1st priority for QTouch Y-lines
4
Y-line 2
Y-line 2
2nd priority for QTouch Y-lines
5
Y-line 3
Y-line 3
3rd priority for QTouch Y-lines
6
Y-line 4
Y-line 4
4th priority for QTouch Y-lines
7
X-line 1
X-line 1
1st priority for QTouch X-lines
8
X-line 2
X-line 2
2nd priority for QTouch X-lines
9
X-line 3 (Y-line 5)
X-line 3
3rd priority for QTouch X-lines
10
X-line 4 (Y-line 6)
X-line 4
4th priority for QTouch X-lines
11
12
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
18
Pin
number
EXT1
MCU board
Extension board
Recommendation
13
14
15
16
(Y-line 7)
17
18
(Y-line 8)
QTouch Design of Medium and Large Boards
For medium QTouch extension boards with header EXT1 and EXT2, only the four first lines on each
header should be used to ensure compatibility with most MCU boards.
If more than four Y-lines are required on the extension kit, use the ones marked in the table with the loss
of compatibility with one or more MCU board. If four or less Y-lines are required, duplicate the four first Xlines from the EXT2 header on the EXT1 header to make it compatible with small MCU boards.
MCU boards should be designed with the minimum of four Y-lines on EXT1 and four X-lines on EXT2. For
compatibility with the QT1 Xplained Pro board, Y-lines 5-8 can optionally be designed in. For compatibility
to small extension boards, XY-lines should be designed in on pin 7-10.
Table 2-6 Recommended Priority for PTC Signals on Two Header Boards (EXT1)
Pin
number
on EXT1
MCU board
Extension board
Recommendation
3
Y-line 1
Y-line 1
1st priority for QTouch Y-lines
4
Y-line 2
Y-line 2
2nd priority for QTouch Y-lines
5
Y-line 3
Y-line 3
3rd priority for QTouch Y-lines
6
Y-line 4
Y-line 4
4th priority for QTouch Y-lines
7
(X-line 5)
X-line 1 duplicated
5th priority for QTouch X-lines
8
(X-line 6)
X-line 2 duplicated
6th priority for QTouch X-lines
9
Y-line 5 (X-line 7)
Y-line 5 or X-line 3
duplicated
5th priority for QTouch Y-lines (Use XY
capable lines if possible for supporting one
header boards)
10
Y-line 6 (X-line 8)
Y-line 6 or X-line 4
duplicated
6th priority for QTouch Y-lines (Use XY
capable lines if possible for supporting one
header boards)
11
12
13
14
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
19
Pin
number
on EXT1
MCU board
Extension board
Recommendation
Y-line 7
Y-line 7
7th priority for QTouch Y-lines
Y-line 8
Y-line 8
8th priority for QTouch X-lines
15
16
17
18
Table 2-7 Recommended Priority for PTC Signals on Two Header Boards (EXT2)
Pin
number
on EXT2
MCU board
Extension board
Recommendation
3
X-line 1
X-line 1
1st priority for QTouch X-lines
4
X-line 2
X-line 2
2nd priority for QTouch X-lines
5
X-line 3
X-line 3
3rd priority for QTouch X-lines
6
X-line 4
X-line 4
4th priority for QTouch X-lines
7
X-line 9
X-line 5
9th priority for QTouch X-lines
8
X-line 10
X-line 6
10th priority for QTouch X-lines
9
X-line 11
X-line 7
11th priority for QTouch X-lines
10
X-line 12
X-line 8
12th priority for QTouch X-lines
11
12
13
14
15
16
17
18
2.5.3.
Xplained Pro Power Header
The power header can be used to connect external power to the Xplained Pro kit. The kit will
automatically detect and switch to any external power if supplied. The power header can also be used as
supply for external peripherals or extension boards. Care must be taken not to exceed the total current
limitation of the on-board regulator when using the target voltage pin.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
20
Table 2-8 Xplained Pro Power Header
2.5.4.
Pin number
Pin name
Description
1
VEXT_P5V0
External 5V input
2
GND
Ground
3
VCC_P5V0
Unregulated 5V (output, derived from one of the input sources)
4
Target VTG
Regulated target voltage (output, used as main power supply for the
kit)
Current Measurement Header
All Xplained Pro MCU boards feature an angled 1x2, 100mil pin-header marked with MCU current
measurement that is located at the upper edge of the board. All power to the target device is routed
through this header. The header is populated with a jumper cap. The purpose of this header is to enable
power consumption measurements of the target device with external equipment.
2.5.5.
Xplained Pro Segment LCD Connector
Xplained Pro MCU boards that have a microcontroller that supports segment LCDs can implement a 51pin segment LCD extension connector. This connector is implemented with HIROSE DF-9 series.
Xplained Pro MCU boards use the male version DF9-51P-1V(69) and Xplained Pro extension boards use
the female counterpart DF9-51S-1V(69). The connector has a standardized pin-out as shown in Table
2-9 Xplained Pro Segment LCD Connector on page 21.
Info: All pins are not connected on all Xplained Pro MCU boards, it depends on how many segments
and common terminals the target MCU supports.
Pin 37, 38, 39, 40, 41 and 42 can alternatively be used for QTouch signals. When they are used
for touch they should not be used for display segments.
Table 2-9 Xplained Pro Segment LCD Connector
Description
Function
Pin
Pin
Function
Description
Common terminal 3
COM3
1
2
COM2
Common terminal 2
Common terminal 1
COM1
3
4
COM0
Common terminal 0
Segment 0
SEG0
5
6
SEG1
Segment 1
Segment 2
SEG2
7
8
SEG3
Segment 3
Segment 4
SEG4
9
10
SEG5
Segment 5
Segment 6
SEG6
11
12
SEG7
Segment 7
Segment 8
SEG8
13
14
SEG9
Segment 9
Segment 10
SEG10
15
16
SEG11
Segment 11
Segment 12
SEG12
17
18
SEG13
Segment 13
Segment 14
SEG14
19
20
SEG15
Segment 15
Segment 16
SEG16
21
22
SEG17
Segment 17
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
21
2.5.6.
Description
Function
Pin
Pin
Function
Description
Segment 18
SEG18
23
24
SEG19
Segment 19
Segment 20
SEG20
25
26
SEG21
Segment 21
Segment 22
SEG22
27
28
SEG23
Segment 23
Segment 24
SEG24
29
30
SEG25
Segment 25
Segment 26
SEG26
31
32
SEG27
Segment 27
Segment 28
SEG28
33
34
SEG29
Segment 29
Segment 30
SEG30
35
36
SEG31
Segment 31
Segment 32 /
QTouch X-line 2
SEG32 / QT_X2
37
38
SEG33 / QT_Y2
Segment 33 /
QTouch Y-line 2
Segment 34 /
QTouch X-line 1
SEG34 / QT_X1
39
40
SEG35 / QT_Y1
Segment 35 /
QTouch Y-line 1
Segment 36 /
QTouch X-line 0
SEG36 / QT_X0
41
42
SEG37 / QT_Y0
Segment 37 /
QTouch Y-line 0
Common terminal 4
COM4
43
44
COM5
Common terminal 5
Common terminal 6
COM6
45
46
COM7
Common terminal 6
Backlight anode
Backlight V+
47
48
Backlight V-
Backlight Cathode
Backlight control
Backlight CTRL
49
50
ID
Xplained Pro ID
Ground
GND
51
Xplained Pro LCD Extension Connector
The LCD connector provides the ability to connect to display extensions that have a parallel interface.
The connector implements signals for a MCU parallel bus interface and a LCD controller interface as well
as signals for a touch controller. The connector pin-out definition is shown in Table 2-10 Xplained Pro
LCD Connector on page 22. Note that usually only one display interface is implemented, either the LCD
controller or the MCU bus interface.
A FPC/FFC connector with 50 pins and 0.5mm pitch is used for the LCD connector. The connector
XF2M-5015-1A from Omron is used on several Xplained Pro designs and can be used as a reference.
Table 2-10 Xplained Pro LCD Connector
Pin number Name
RGB interface description
MCU interface description
1
ID
Communication line to the ID chip on an extension board
2
GND
Ground
3
D0
Data line
4
D1
Data line
5
D2
Data line
6
D3
Data line
7
GND
Ground
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
22
Pin number Name
RGB interface description
MCU interface description
8
D4
Data line
9
D5
Data line
10
D6
Data line
11
D7
Data line
12
GND
Ground
13
D8
Data line
14
D9
Data line
15
D10
Data line
16
D11
Data line
17
GND
Ground
18
D12
Data line
19
D13
Data line
20
D14
Data line
21
D15
Data line
22
GND
Ground
23
D16
Data line
24
D17
Data line
25
D18
Data line
26
D19
Data line
27
GND
Ground
28
D20
Data line
29
D21
Data line
30
D22
Data line
31
D23
Data line
32
GND
Ground
33
PCLK / CMD DATA Pixel clock
SEL
Display RAM select. One
address line of the MCU for
displays where it is possible to
select either register or data
interface.
34
VSYNC / CS
Vertical Synchronization
Chip select
35
HSYNC / WE
Horizontal Synchronization
Write enable signal
36
DATA ENABLE /
RE
Data enable signal
Read enable signal
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
23
2.6.
Pin number Name
RGB interface description
MCU interface description
37
SPI SCK
Clock for serial peripheral interface
38
SPI MOSI
Master out slave in of serial peripheral interface
39
SPI MISO
Master in slave out of serial peripheral interface
40
SPI SS
Slave select for serial peripheral interface. Preferably a dedicated
pin.
41
ENABLE
Display enable
42
I2C SDA
I2C data
43
I2C SCL
I2C clock
44
IRQ1
Interrupt 1
45
IRQ2
Interrupt 2
46
PWM
Backlight control
47
RESET
Extension reset
48
VCC
3.3V power supply for extension board
49
VCC
3.3V power supply for extension board
50
GND
Ground
Power Specifications
The Xplained Pro kit can be powered either by USB or by an external power source through the 4-pin
power header, marked PWR. The available power sources and specifications are listed in the table below.
Table 2-11 Power Sources for Xplained Pro
Power input
Voltage requirements
Current requirements
External power
5V ±2% (±100mV) for USB
host operation.
Recommended minimum is 1A to be PWR
able to provide enough current for
connected USB devices and the
board itself. Recommended
maximum is 2A due to the input
protection maximum current
specification.
4.3V to 5.5V if USB host
operation is not required
Connector
marking
Embedded
debugger USB
4.4V to 5.25V (according to
USB spec.)
500mA (according to USB spec.)
DEBUG USB
Target USB
4.4V to 5.25V (according to
USB spec.)
500mA (according to USB spec.)
TARGET USB
The kit will automatically detect which power sources are available and choose which one to use
according to the following priority:
1. External power.
2. Embedded debugger USB.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
24
3.
Target USB.
Info: External power is required when the 500mA through the USB connector is not enough to power
a connected USB device in a USB host application.
Xplained Pro MCU kits are generally powered by 5.0V input that is regulated to a 3.3V power supply for
the EDBG, MCU, and extension headers/connectors.
Some Xplained Pro MCU kits implements a separate 3.3V regulator for the EDBG.
Some Xplained Pro MCU kits have support for 5.0V for the target MCU, and extension headers/
connector. These kits implements full level shift between the EDBG and target MCU.
Figure 2-8 Typical Xplained Pro Power Connections
2.6.1.
2.6.1.1.
Typical Power Supply Implementations
No Target USB
When the target MCU does not offer a USB interface the power supply system can be reduced to the
configuration shown below.
Figure 2-9 Power Supply Block Diagram for Boards with no Target USB
EDBG USB
Target
peripherals
EDBG
2.6.1.2.
Regulator
3.3V
Switch
disable
5V
MCU current
measurement
External 5V
input
Ta
rg
et
bo
ar
d
Target MCU
Ta
rg
et
bo
ar
d
3.
3V
Switch with
current limit
Target USB
When a target MCU offers a USB device interface it is mandatory to implement this interface and hook it
up to the power supply system.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
25
Figure 2-10 Power Supply Block Diagram for Boards with Target USB
EDBG USB
Target
peripherals
Regulator
3.3V
EDBG
2.6.1.3.
5V
MCU current
measurement
Auto mux
disable
Target USB
External 5V
input
Ta
rg
et
bo
ar
d
Target MCU
Ta
rg
et
bo
ar
d
3.
3V
Auto mux with
current limit
USB Host
Target devices with USB host require an additional switch in the power supply system that turns on/off the
power supply that is connected to USB devices in USB host mode of the target MCU. USB host mode
requires the connection of an external power supply to be able to meet the USB specifications. For most
cases the power input via the EDBG USB interface will be sufficient but is not recommended since it will
only work if the input voltage is not at the lower end of the USB specifications and if the USB device does
not require a lot of power.
Figure 2-11 Power Supply Block Diagram for Boards with USB Host
EDBG USB
Target
peripherals
EDBG
2.7.
Regulator
3.3V
Auto mux
disable
5V
MCU current
measurement
Ta
rg
et
bo
ar
d
Target MCU
Ta
rg
et
bo
ar
d
3.
3V
Auto mux with
current limit
Target USB
External 5V
input
Target
controlled
USB host
switch
Board Stacking Options
Xplained Pro LCD boards are intended to be mountable on top, on the bottom or placed sideways to an
Xplained Pro MCU board as shown in the following illustrations.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
26
Figure 2-12 Side By Side Connection Option
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
27
Figure 2-13 Top Side Mounting
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
28
Figure 2-14 Bottom Side Mounting
The stacking is supported by spacers and screws. Figure 2-15 LCD Board Top-stacked on page 29
shows an LCD board stacked on top of a MCU board. Figure 2-16 LCD Board Bottom-stacked on page
30 shows an LCD board stacked on the bottom side of a MCU board. Note that the MCU board has
been flipped up-side down in this drawing. Both of these mounting configurations requires four long
spacers (M2.5, 20mm, female/male), four short spacers (M2.5, 7.5mm, female/female), and four screws
(M2.5, 5mm).
Figure 2-15 LCD Board Top-stacked
Screw
Display
LCD Board
Spacer
MCU Board
Spacer
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
29
Figure 2-16 LCD Board Bottom-stacked
Screw
Display
LCD Board
Spacer
MCU Board
Spacer
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
30
3.
Xplained Pro MCU Boards
3.1.
Standard On-board Features
3.1.1.
Embedded Debugger (EDBG)
The EDBG offers a wide range of features that can be implemented in a design and all these are
documented in the EDBG datasheet. The Xplained Pro however, requires only a reduced set of features
to minimize cost and remove some complexity from the design. The following list shows the required
features but it is up to the designer to decide if additional features must be added for a design.
Related Links
Embedded Debugger on page 8
3.1.1.1.
Status LEDs
The EDBG controls two LEDs; the power LED and the status LED. These are required on all Xplained
Pro MCU board.
Related Links
Table 2-1 EDBG LED Control on page 8
3.1.1.2.
Target Reset
The reset pin of the target device must always be connected to the EDBG. In most designs the reset is
already covered by the debugging/programming interface (e.g. PDI interface on XMEGA uses RESET as
clock line) but in others it may be necessary to connect the reset separately because the interface is
located on other pins or reset is not required for programming/debugging.
3.1.1.3.
EDBG DGI (Data Gateway Interface)
This is the default serial interface that is used for the Atmel Data Protocol (ADP), which can transport a lot
of different data like measurement values, printf style text messages, or other application information.
This interface can be based on several different hardware implementations, such as (highest priority first):
•
•
•
•
•
Synchronous UART (target is the master and generates the clock)
SPI (target is master)
UART
I2C
GPIO
•
Signal a change of power save mode of the target
•
•
Code profiling by either counting e.g. function calls or by measuring execution time of a code
sequence
General purpose trigger for a user application
A resistor should be placed between the EDBG and the target on each GPIO line to limit the current that
can flow when the user drives the signal from both sides. The resistor value must be selected according
to the maximum allowed drive/sink currents on EDBG and target. On the EDBG a typical pad can source/
sink around 20mA (at 25°C and 3.3V). The recommended resistor value is 330Ω, which reduces the
current to 10mA. In practice it will be less due to resistance within the drivers in EDBG and target.
It is mandatory to implement at least one of the interfaces on an Xplained Pro MCU board and I2C should
always be implemented because it can be used to get board information from the EDBG like currently
connected extensions.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
31
3.1.1.4.
Virtual COM-port Interface
This interface is based on a UART and is used to provide a generic way to transport data to and from the
target to a PC without the need for using Atmel Studio. On the PC side this interface will show up as a
USB CDC class. The EDBG TX pin of this interface will only be enabled when the virtual COM port is
connected by a host PC application. The virtual COM port is implemented on all Xplained Pro MCU
boards.
3.1.2.
Reset Button
This button is required to:
•
Reset the target without resetting the embedded debugger. This is necessary when the target
application should be reset while still maintaining the connection to the PC via the embedded
debugger. Otherwise the embedded debugger would need to re-enumerate and most likely the host
PC application would need to be re-started or re-configured.
•
Reset the target without unplugging the power to the board (would be quite tiresome when
developing)
The EDBG is also connected to this signal to monitor user interaction as well as controlling it. Therefore it
is possible to report a reset that was triggered by the reset button and to recover from a debug session
that was terminated due to the reset.
3.1.3.
Wake-up/Bootloader/User Button
This button is required for:
•
Wake-up of the device from low power sleep modes as most devices offer a special pin(s) for this
purpose
•
Entering bootloader mode of the target
•
Other user interaction, this is not the main reason why we have the button but when we have it we
can use it for other purposes as well
It is important that the above functions are covered by corresponding pins on the target that offer these
features because then the user experience is the same across the whole Xplained Pro platform.
3.1.4.
Current Measurement Header
A header must be placed into the supply path to the target MCU, which is used to connect external
measurement equipment for power consumption measurements.
3.2.
Mechanical Dimensions and Component Placement
3.2.1.
Plastic Isolation Bumpers
Plastic isolation bumpers are used on the bottom side of the board to isolate it from the surface on which
it is mounted. The height of the isolation bumpers on the bottom side is 2.8mm and the recommended
part is SJ-5076 from 3M. Other adhesive feet might work as well but it is very important to have the same
height because otherwise extensions will not align well when connected.
3.2.2.
Component Height
To allow stacking of extension on the top side and on the bottom side of the board as well as using
isolation bumpers it is required to follow the maximum component height recommendations.
•
All components on the top side should not exceed 15mm in height. Exceeding this limit will affect
stacking of the board because different spacing between the boards might be required which can't
be done with the spacers that are defined for Xplained Pro board stacking.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
32
•
All components on the bottom side of the board should not exceed 2.8mm in height. Using taller
components on the bottom side will prevent the use of the default isolation bumpers and might
affect the required spacers for board stacking.
3.2.3.
Mounting Holes
The mounting holes on Xplained Pro should be designed to fit a M2.5 screw, the recommended hole
diameter is 2.7mm. The clearance to other components should be 3mm from the hole center to allow the
mounting of screws and/or spacers. A typical hexagonal spacer for M2.5 screws has a diameter of 4.5mm
when measured from side to side (5.2mm when measured from edge to edge) so a 3mm clearance works
well. The hole center should be placed 2.35mm from the board edges. All mounting holes should be
plated and connected to GND. The pads around the mounting hole must be large enough to provide a
good ground connection if a grounding cable or metal post is connected to the hole. More information
about mounting hole placement is available in the board design templates.
3.2.4.
Board Sizes
There are three standard Xplained Pro MCU board sizes; small, medium and large. The most commonly
used sizes are medium and small.
Figure 3-1 Small MCU Board Mechanical Dimensions
54.209mm
42.659mm
21.375mm
9.825mm
60.000mm
2.70mm
2.350mm
2.350mm
60.000mm
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
33
Figure 3-2 Medium MCU Board Mechanical Dimensions
54.209mm
42.659mm
21.375mm
2.70mm
100.000mm
9.825mm
2.350mm
2.350mm
60.000mm
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
34
Figure 3-3 Large MCU Board Mechanical Dimension
54.209mm
42.659mm
21.375mm
2.70mm
100.000mm
9.825mm
2.350mm
2.350mm
3.2.5.
115.300mm
57.650mm
Connector and Header Placement
Several connectors have standardized locations on Xplained Pro MCU boards, including USB,
connectors for external debuggers, standard extension headers, and application specific extension
connectors. Each connectors' position is referenced from one of the PCB corners.
Info: The placement of the standard connectors are relative to a PCB corner. Each connector
is placed with the same rules on small, medium, and large Xplained Pro MCU boards.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
35
TARGET US B
14.760mm
48.434mm
15.600mm
DEBUG US B
1
2
1
2
1
2
1
P owe r He a de r
1
2
24.280mm
LCD Conne ctor
20.650mm
Exte ns ion He a de r 3
5.700mm
30.000mm
32.000mm
4.000mm
3.2.5.1.
Exte ns ion He a de r 2
S e gme nt LCD Conne ctor
5.700mm
Exte ns ion He a de r 1
75.720mm
2
De bug He a de r
22.375mm
40.160mm
1.675mm
Figure 3-4 Standard Connector and Header Placement
Standard Xplained Pro Header Placement
The 20-pin standard extension headers that are always found on Xplained Pro MCU boards are named
and located at fixed positions around the board edge. Extension header EXT1, EXT2, and EXT3 are
reserved for standard Xplained Pro extension headers The tables below shows standard header
placement and which connectors are commonly found on the different board sizes. Additional 20-pin
extension headers can be placed at other locations on the board.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
36
Table 3-1 Standard Header Placement
Header
Placement
PWR
Referenced to the upper right corner of the PCB
EXT1
Referenced to the upper right corner of the PCB
EXT2
Referenced to the upper right corner of the PCB
(EXT2 is never implemented on small boards)
EXT3
Referenced to the lower right corner of the PCB
Table 3-2 Xplained Pro Board Sizes and Standard Headers
Board Size
Standard Connectors
Small
PWR, EXT1, and EXT3
Medium
PWR, EXT1, EXT2, and EXT3
Large
PWR, EXT1, EXT2, and EXT3
Related Links
Xplained Pro Power Header on page 20
Xplained Pro Standard Extension Header on page 15
3.2.5.2.
USB Connector Placement
All Xplained Pro MCU boards have at least one USB connector for the EDBG, boards with a target
microcontroller that supports USB have an additional connector. Both connectors have standardized
placements on the kit referenced from the upper right corner of the PCB.
3.2.5.3.
Current Measurement Header Placement
The current measurement header is always placed at the upper edge of the PCB. The header is placed
so the attached jumper cap does not extend outside the board edge.
Related Links
Current Measurement Header on page 21
3.2.5.4.
Debug Header Placement
Standard 6-pin and 10-pin 50-mil debug headers have a predefined placement between the PWR header
and EXT1 header. If other and/or larger debug headers with for example trace support are required, this
header can be placed freely on the board.
3.2.5.5.
Segment LCD Connector Placement
The segment LCD connector's placement is referenced from the lower right corner of the PCB. Note that
this location is not necessarily the best location on small and large MCU boards. If this connector is
moved, make sure to at least support segment LCD extensions within the size constrain defined in the
extension section of this document.
Related Links
Xplained Pro Segment LCD Connector on page 21
Board Size Constraint on page 52
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
37
3.2.5.6.
LCD Connector Placement
The connector is always placed above the lower left mounting hole, this also applies for the large
Xplained Pro MCU boards. The consistent connector placement allows all LCD boards to be mounted the
same way as described in Board Stacking Options on page 26.
Related Links
Xplained Pro LCD Extension Connector on page 22
Board Stacking Options on page 26
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
38
4.
4.1.
Xplained Pro Extensions
Extension Board Templates
Extensions enable demonstration of MCU features that are not placed on the MCU board, e.g. sensors,
displays, LEDs, and push buttons. Various standard and kit specific extensions are presented in the
following sections. All holes designated for mounting are 2.7mm in diameter, plated, and connected to
GND.
4.1.1.
Designing a Board with the Standard Extension Header
The following sections contain information about standard extension sizes used by Atmel. The holes
referred to as "test jig holes" are used by Atmel during manufacturing to align the board in a test fixture.
These holes can safely be removed if they are not needed. These holes are not plated. The circles shown
in the component placement drawings are rubber feet placed on the bottom side of the boards. Atmel
uses 3M SJ-5076, which are 8mm in diameter and 2.8mm thick. Keep in mind that following these
templates will ensure that the boards will physically fit on all Xplained Pro MCU kits.
Each template topic provides links to example products using the template if there are any.
Related Links
Xplained Pro Standard Extension Header on page 15
4.1.1.1.
Extension Template 1
This is the most basic extension module and will fit all MCU boards. This means that this extension is the
preferred module when starting a design.
Features:
•
•
•
•
•
•
30mm x 50mm
One female standard extension header
ID system
Two mounting holes with GND
Two test jig holes
Two rubber feet
Figure 4-1 Standard Extension 1 3D View
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
39
Figure 4-2 Standard Extension 1 Component Placement
4.40mm
15.00mm
Exte ns ion Conne ctor
3.80mm
8.60mm
Figure 4-3 Standard Extension 1 Mechanical Dimensions
2.70mm
6.50mm
2.35mm
30.00mm
3.50mm
2.00mm
22.62mm
13.25mm
7.38mm
8.00mm
2.35mm
50.00mm
4.1.1.2.
Extension Template 2
Compared to the basic default extension, this extension adds a power connector to the design. The
extension type can be used if access to the power inputs/outputs of the MCU board is required.
•
•
•
•
•
•
•
45mm x 50mm
One female standard expansion header
One female power header
ID system
Two mounting holes with GND
Two test jig holes
Two rubber feet
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
40
Figure 4-4 Standard Extension 2 3D View
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
41
Figure 4-5 Standard Extension 2 Component Placement
3.80mm
40.40mm
P owe r Conne ctor
15.00mm
Exte ns ion Conne ctor
3.80mm
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
42
Figure 4-6 Standard Extension 2 Mechanical Dimensions
2.70mm
6.50mm
45.00mm
2.35mm
42.65mm
3.50mm
2.00mm
22.62mm
13.25mm
7.38mm
8.00mm
2.35mm
50.00mm
4.1.1.3.
Extension Template 3
This extension is targeted for applications that require more signals than are available on one standard
header e.g. when more than two ADC or PWM signals are needed. Note that this extension might not fit
all MCU boards since smaller boards will not have two extension headers on one side.
•
•
•
•
•
•
65.55mm x 50mm
Two female Standard extension headers
ID system
Two mounting holes with GND
Two test jig holes
Two rubber feet
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
43
Figure 4-7 Standard Extension 3 3D View
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
44
Figure 4-8 Standard Extension 3 Component Placement
3.80mm
50.56mm
Exte ns ion Conne ctor 1
15.00mm
Exte ns ion Conne ctor 2
3.80mm
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
45
Figure 4-9 Standard Extension 3 Mechanical Dimensions
2.70mm
2.00mm
48.81mm
58.18mm
65.55mm
63.20mm
6.50mm
13.25mm
2.35mm
3.50mm
42.94mm
8.00mm
2.35mm
50.00mm
4.1.1.4.
Extension Template 4
This extension is the same as Extension 3 except for the additional power header.
•
•
•
•
•
•
80.55mm x 50mm
Two female standard extension headers
One female power header
ID system
Two mounting holes with GND
Two test jig holes
•
Two rubber feet
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
46
Figure 4-10 Standard Extension 4 3D View
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
47
Figure 4-11 Standard Extension 4 Component Placement
3.80mm
P owe r Conne ctor
50.56mm
75.96mm
Exte ns ion Conne ctor 1
15.00mm
Exte ns ion Conne ctor 2
3.80mm
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
48
Figure 4-12 Standard Extension 4 Mechanical Dimensions
6.50mm
2.70mm
80.55mm
78.20mm
2.00mm
48.81mm
58.18mm
13.25mm
2.35mm
3.50mm
42.94mm
8.00mm
2.35mm
50.00mm
4.1.1.5.
Extension Template 5
This board size is designed to fit on all Xplained Pro MCU boards, but with an orientation for the header
at the bottom of the Xplained Pro MCU board. Note that the board is too wide to be connected next to
another extension board on the right hand side.
Features:
•
•
•
•
•
•
60mm x 60mm
One female standard extension header
ID system
Four mounting holes with GND
Two test jig holes
Four rubber feet
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
49
Figure 4-13 Standard Extension 5 3D View
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
50
Figure 4-14 Standard Extension 5 Component Placement
3.80mm
30.00mm
Exte ns ion Conne ctor
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
51
Figure 4-15 Standard Extension 5 Mechanical Dimensions
3.50mm
6.50mm
28.25mm
37.62mm
22.38mm
8.00mm
2.70mm
60.00mm
4.1.2.
4.1.2.1.
2.35mm
2.35mm
60.00mm
2.00mm
Designing a Board with the Segment LCD Connector
Board Size Constraint
Xplained Pro MCU boards will support segment LCD boards up to 50.5mm x 42mm with the Hirose
DF9-51S-1V(69) connector placed as in the drawing below. The constraints are introduced to avoid
collision with other on-board peripherals on Xplained Pro MCU boards. When the Hirose connectors on a
MCU board and segment LCD board is stacked the total height is 4.3mm, any through hole pins on a
segment LCD should not be too long as they may collide with resistors/capacitors on the MCU board.
Important: Segment LCD boards should not be larger than 50.5mm x 42mm with the Hirose connector
located as in the picture below. Boards larger than this may collide with components on an
Xplained Pro MCU board.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
52
Figure 4-16 Segment LCD Board Size Constraint
Related Links
Xplained Pro Segment LCD Connector on page 21
4.1.3.
4.1.3.1.
Designing a Board with the LCD connector
Recommended LCD Connector Implementation
The best way to implement the LCD interface is to use a setup as shown in Figure 4-17 Recommended
Connector Implementation and Cabling on page 53 as it is not possible to damage anything when the
connection is made in a wrong way e.g. by inserting the cable upside down. On the MCU board a FFC
connector with contacts on the top is placed on the top side of the MCU board while on the extension
board a connector with contacts on the bottom side is placed on the bottom side of the extension.
Recommended connectors are 5-17344592-0 (extension) and 5-1734839-0 (MCU board) from TE
Connectivity. The cable itself has the contacts on the same side as indicated in Figure 4-17 Recommended Connector Implementation and Cabling on page 53.
Figure 4-17 Recommended Connector Implementation and Cabling
Xplained Pro LCD board
Connector with contacts
on the bottom
(TE-5-1734592-0)
Connector with
contacts on the top
(TE-5-1734839-0)
Xplained Pro MCU board
FFC cable with
contacts on the same
side
Contacts on the cable
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
53
In order to place the LCD board sideways or mount it on top/bottom it is necessary to use a set of screws
and spacers. Board Stacking Options on page 26 provides the required information to properly stack the
board.
Related Links
Xplained Pro LCD Extension Connector on page 22
4.1.3.2.
Extension Template 6, Medium LCD Board
This board template is designed for boards with large displays. It is the exact same size as a medium
Xplained Pro MCU board with mounting hole locations at the exact same place for board stacking
purposes. More information on board stacking options can be read about in Board Stacking Options on
page 26.
Features:
•
•
•
•
•
•
100mm x 60mm
One male standard extension header
One LCD extension connector
ID system
Four mounting holes with GND
Ideal for 2.8" to 3.5" displays
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
54
Figure 4-18 Extension Template 6, Medium LCD Board Bottom 3D View
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
55
Figure 4-19 Extension Template 6, Medium LCD Board Component Placement
94.25mm
Exte ns ion He a de r
20.65mm
LCD Conne ctor
4.00mm
30.00mm
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
56
Figure 4-20 Extension Template 6, Medium LCD Board Display Size Estimates
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
57
Figure 4-21 Extension Template 6, Medium LCD Board Mechanical Dimensions
2.35mm
100.00mm
2.70mm
2.35mm
60.00mm
4.1.3.3.
Extension Template 7, Large LCD Board
This board template is designed for boards with large displays. It is the exact same size as a large
Xplained Pro MCU board with mounting hole locations at the exact same place for board stacking
purposes. More information on board stacking options can be read about in Board Stacking Options on
page 26.
Features:
•
•
100mm x 115.3mm
One male standard extension header
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
58
•
•
•
•
One LCD extension connector
ID system
Six mounting holes with GND
Ideal for 4.3" to 5.0" displays
Figure 4-22 Extension template 7, Large LCD Board Bottom 3D View
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
59
Figure 4-23 Extension Template 7, Large LCD board Component Placement
94.25mm
Exte ns ion He a de r
20.65mm
LCD Conne ctor
4.00mm
30.00mm
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
60
Figure 4-24 Extension Template 7, Large LCD Board Display Size Estimates
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
61
Figure 4-25 Extension Template 7, Large LCD Board Mechanical Dimensions
2.35mm
100.00mm
2.70mm
115.30mm
57.65mm
2.35mm
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
62
5.
5.1.
Xplained Pro Extensions in Atmel Studio
Xplained Pro Landing Page
When an Xplained Pro MCU kit is connected to a computer running Atmel Studio, a landing page for the
kit is shown. Figure 5-1 Xplained Pro Landing Page in Atmel Studio on page 63 shows a landing page
for SAM4S Xplained Pro with PROTO1-, I/O1-, and OLED1 Xplained Pro connected. The landing page
provides information like the connected kits name, a picture of the kit, a description of the kit, links to
relevant documentation/websites, and all the information stored in the Xplained Pro ID chip, located on
the extension modules.
Figure 5-1 Xplained Pro Landing Page in Atmel Studio
Any developer that would like to add information about an Xplained Pro extension to Atmel Studio has to
contact Atmel via e-mail [email protected] with landing page information and a picture of the kit as shown
in the figure above. The landing page uses the name of the kit stored in the ID chip as a key to display the
correct information, it is therefore important that Atmel knows the exact name that will be programmed
into the chip.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
63
6.
Appendix
6.1.
Xplained Pro I2C Address List
The Table 6-2 Xplained Pro I2C Address List on page 64 lists the used I2C addresses on the Xplained
Pro platform. Register an I2C address via [email protected] so that this can be added to the list which will
avoid conflicts on the I2C bus. The I2C compatible device adresses in Table 6-2 Xplained Pro I2C
Address List on page 64 must be shifted left to form the SLA+W or SLA+R address when transmitted
over the I2C compatible interface as show in Table 6-1 Format of SLA+W and SLA+R on page 64.
Table 6-1 Format of SLA+W and SLA+R
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
I2C address e.g. 0x4A
Bit 1
Bit 0
Read/Write
Table 6-2 Xplained Pro I2C Address List
I2C address
Products using this
address
Configuration option
0x28
All Xplained Pro MCU
boards (I2C interface to the
embedded debugger)
Cannot be changed permanently so each reboot of the
EDBG resets this to the default address. Configuration can
be done via Atmel Data Visualizer.
0x29
BNO055 Xplained Pro
Last bit is configurable by pull-up/down.
0x4A
maXTouch Xplained Pro
(mXT112S touchscreen
controller)
Not configurable
0x4B
ATMEGA256RFR2 Xplained Last three bits can be configured by soldering. This will
Pro (temp. sensor)
also change the last three bits of the EEPROM address on
this board because both are within the same device.
0x4F
I/O1 Xplained Pro (temp.
sensor)
Last three bits can be configured by soldering. This will
also change the last three bits of the EEPROM address on
this board because both are within the same device.
0x50
SAM L22 Xplained Pro
(ATAES132A crypto device)
Default device address. Can be changed in internal config
register.
0x53
ATMEGA256RFR2 Xplained Last three bits can be configured by soldering. This will
Pro (EEPROM)
also change the last three bits of the temp sensor address
on this board because both are within the same device.
0x57
I/O1 Xplained Pro
(EEPROM)
Last three bits can be configured by soldering. This will
also change the last three bits of the temp sensor address
on this board because both are within the same device.
0x70
SHTC1 Xplained Pro
Not configurable
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
64
6.2.
id_tool Version History
This chapter contains the changelog for the id_tool python CLI used to program/read Xplained Pro ID
devices.
6.2.1.
Version 1.0
Renamed python package from xpro_id to id_tool
Rewrote the CLI with better error reporting and bugfixes to the EDBG HID driver.
Changed distribution type to pip compatible source distribution, previous versions were released as a
®
Windows executable.
6.2.2.
Version 0.5
Version 0.5 is the initial released version.
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
65
7.
Document Revision History
Doc. rev.
Date
Comment
42091D
10/2015
Updated information. Added information about XAM and QTouch.
42091C
06/2013
Restructured the document. Added information about Xplained Pro ID
device programming and integration to Atmel Studio
42091B
03/2013
Added a new chapter about Atmel Studio integration
42091A
02/2013
First release
Atmel Xplained Pro Hardware Development Kit (HDK) [USER GUIDE]
Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
66
Atmel Corporation
©
1600 Technology Drive, San Jose, CA 95110 USA
T: (+1)(408) 441.0311
F: (+1)(408) 436.4200
|
www.atmel.com
2015 Atmel Corporation. / Rev.: Atmel-42091D-Atmel-Xplained-Pro-Hardware-Development-Kit_User Guide-10/2015
®
®
®
®
Atmel , Atmel logo and combinations thereof, Enabling Unlimited Possibilities , QTouch , XMEGA and others are registered trademarks or trademarks of Atmel
®
Corporation in U.S. and other countries. Windows is a registered trademark of Microsoft Corporation in U.S. and or other countries. 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 products 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.
SAFETY-CRITICAL, MILITARY, AND AUTOMOTIVE APPLICATIONS DISCLAIMER: Atmel products are not designed for and will not be used in connection with any
applications where the failure of such products would reasonably be expected to result in significant personal injury or death (“Safety-Critical Applications”) without
an Atmel officer's specific written consent. Safety-Critical Applications include, without limitation, life support devices and systems, equipment or systems for the
operation of nuclear facilities and weapons systems. Atmel products are not designed nor intended for use in military or aerospace applications or environments
unless specifically designated by Atmel as military-grade. Atmel products are not designed nor intended for use in automotive applications unless specifically
designated by Atmel as automotive-grade.