AVR64EA48 AVR64EA48 Curiosity Nano Hardware User Guide Preface ® The AVR64EA48 Curiosity Nano evaluation kit (EV66E56A) is a hardware platform to evaluate the AVR EA Family microcontrollers. This board has the AVR64EA48 microcontroller (MCU) mounted. ® Supported by both MPLAB X IDE and Microchip Studio, the board provides easy access to the features of the AVR64EA48 to explore how to integrate the device into a custom design.
– 1.8–5.1V output voltage (limited by USB input voltage) – 500 mA maximum output current (limited by ambient temperature and output voltage) Board Overview The Microchip AVR64EA48 Curiosity Nano evaluation kit is a hardware platform to evaluate the AVR64EA48 microcontroller. Figure 1-1. AVR64EA48 Curiosity Nano Board Overview...
Connect a USB cable (Standard-A to Micro-B or Micro-AB) between the PC and the debug USB port on the board. Program your application onto the device. The AVR64EA48 device on the AVR64EA48 Curiosity Nano board is programmed and debugged by the on-board debugger. Therefore, no external programmer or debugger tool is required. Info: ...
Tip: The latest device family packs are available through Tools > Device Pack Manager in Microchip Studio or online at Microchip Studio Packs Repository. Design Documentation and Relevant Links The following list contains links to the most relevant documents and software for the AVR64EA48 Curiosity Nano board: ® ® ®...
A Data Gateway Interface (DGI) for code instrumentation with logic analyzer channels (debug GPIO) to visualize program flow The on-board debugger controls a Power and Status LED (marked PS) on the AVR64EA48 Curiosity Nano board. The table below shows how the different operation modes control the LED.
Page 13
GPIO data. It is available as a plug-in for MPLAB X IDE or a stand-alone application that can be used in parallel with MPLAB X IDE or Microchip Studio. Although DGI encompasses several physical data interfaces, the AVR64EA48 Curiosity Nano implementation includes logic analyzer channels: •...
The USB port powers the board. It contains two LDO regulators, one to generate 3.3V for the on-board debugger and an adjustable LDO regulator for the target AVR64EA48 microcontroller and its peripherals. The voltage from a USB connector can vary between 4.4V and 5.25V (according to the USB specification) and will limit the maximum voltage supplied to the target.
Page 15
1.7V to 5.1V. Additional output voltage limits are configured in the debugger firmware to ensure that the output voltage never exceeds the hardware limits of the AVR64EA48 microcontroller. The voltage limits configured in the on-board debugger on AVR64EA48 Curiosity Nano are 1.8–5.5V.
Page 16
3.3.2 External Supply Instead of the on-board target regulator, an external voltage can power the AVR64EA48 Curiosity Nano. When shorting the Voltage Off (VOFF) pin to the ground (GND) pin, the on-board debugger firmware disables the target regulator, and it is safe to apply an external voltage to the VTG pin.
Page 17
VBUS Output Pin AVR64EA48 Curiosity Nano has a VBUS output pin that can be used to power external components that need a 5V supply. The VBUS output pin has a PTC fuse to protect the USB against short circuits. A side effect of the PTC fuse is a voltage drop on the VBUS output with higher current loads.
Low-Power Measurement Power to the AVR64EA48 is connected from the on-board power supply and VTG pin through a 100 mil pin-header marked with “POWER” in silkscreen (J101). To measure the power consumption of the AVR64EA48 and other peripherals connected to the board, cut the Target Power strap and connect an ammeter over it.
Connections. The on-board level shifters can be completely disconnected to prevent leakage, as described 7.4. Disconnecting the On-Board Debugger. Programming External Microcontrollers Use the on-board debugger on AVR64EA48 Curiosity Nano to program and debug microcontrollers on external hardware. 3.5.1 Supported Devices All external AVR microcontrollers with the UPDI interface can be programmed and debugged with the on-board debugger with Microchip Studio.
Page 20
3.5.3 Hardware Modifications The on-board debugger is connected to the AVR64EA48 by default. Remove these connections before any external microcontroller can be programmed or debugged. Cut the GPIO straps shown in the figure below with a sharp tool to disconnect the AVR64EA48 from the on-board debugger.
Page 21
GPIO straps(bottom side) Info: Cutting the connections to the debugger will disable programming, debugging, and data streaming from the AVR64EA48 mounted on the board. Tip: Solder 0Ω resistors across the footprints or short circuit them with solder to reconnect the signals between the on-board debugger and the AVR64EA48.
Even though there is an on-board debugger, external debuggers can be connected directly to the AVR64EA48 Curiosity Nano to program/debug the AVR64EA48. When not actively used, the on-board debugger keeps all the pins connected to the AVR64EA48 and board edge in tri-state. Therefore, the on-board debugger will not interfere with any external debug tools.
AVR64EA48 Curiosity Nano Pinout All the AVR64EA48 I/O pins are accessible at the edge connectors on the board. The image below shows the board pinout. Refer to the I/O Multiplexing and Considerations section in the AVR64EA48 data sheet for all available functions on each pin.
Page 27
Hardware Description 4.2.1 One yellow user LED is available on the AVR64EA48 Curiosity Nano board. It can be controlled by either GPIO or PWM. Driving the connected I/O line to GND can also activate the LED. Table 4-1. LED Connection...
Page 28
Hardware Description The 20.00 MHz crystal is connected to AVR64EA48 on PA0 and PA1, which are also routed to the edge connector through two solder points. PA0 and PA1 are disconnected from the edge connector by default to reduce the chance of an external signal causing contention with the crystal and to remove excessive capacitance on the lines.
Identifying Product ID and Revision There are two ways to find the revision and product identifier of the AVR64EA48 Curiosity Nano: Either by utilizing the MPLAB X IDE or Microchip Studio Kit Window or by looking at the sticker on the bottom of the PCB.
Schematic rotatethispage90 Figure 7-1. AVR64EA48 Curiosity Nano MCU Schematic rotatethispage90 AVR64EA48 DEBUGGER CONNECTIONS NOTE on UART/CDC: CDC_RX AVR64EA48 CDC_RX CDC_TX RX/TX on the header denotes the CDC_TX Debugger Name C200 input/output direction of the signal DBG0 respective to it's source.
Page 34
Schematic rotatethispage90 Figure 7-2. AVR64EA48 Curiosity Nano Debugger Schematic rotatethispage90 Interface ICSP UPDI TARGET ADJUSTABLE REGULATOR TARGET TARGET Signal VCC_VBUS J100: VCC_REGULATOR VCC_LEVEL VCC_EDGE CDC TX UART RX UART RX - Cut-strap used for full separation of target power from the level shifters and on-board regulators.
The on-board debugger and level shifters can be completely disconnected from the AVR64EA48. The block diagram below shows all connections between the debugger and the AVR64EA48. The rounded boxes represent connections to the board edge. The signal names shown are also printed in silkscreen on the bottom side of the board.
GCC. Programming and ™ debugging of AVR64EA48 Curiosity Nano is supported in IAR Embedded Workbench for AVR using the Atmel-ICE interface. To get the programming and debugging to work, some initial settings must be set up in the project.
The Adaptec logo, Frequency on Demand, Silicon Storage Technology, and Symmcom are registered trademarks of Microchip Technology Inc. in other countries. GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip Technology Inc., in other countries.
Need help?
Do you have a question about the AVR64EA48 and is the answer not in the manual?
Questions and answers