AVR128DA48 Curiosity Nano
AVR128DA48 Curiosity Nano User Guide
Preface
The AVR128DA48 Curiosity Nano Evaluation Kit is a hardware platform to evaluate microcontrollers in the AVR-DA
family. This board has the AVR128DA48 microcontroller (MCU) mounted.
Supported by Atmel Studio and Microchip MPLAB® X Integrated Development Environments (IDEs), the board
provides easy access to the features of the AVR128DA48 to explore how to integrate the device into a custom
design.
The Curiosity Nano series of evaluation boards include an on-board debugger. No external tools are necessary to
program and debug the AVR128DA48.
• MPLAB® X IDE and Atmel Studio - Software to discover, configure, develop, program, and debug Microchip
microcontrollers.
• Code examples in Atmel START - Get started with code examples or generate drivers for a custom
application.
• Code examples on GitHub - Get started with code examples.
• AVR128DA48 website - Find documentation, datasheets, sample, and purchase microcontrollers.
• AVR128DA48 Curiosity Nano website - Kit information, latest user guide and design documentation.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 1
AVR128DA48 Curiosity Nano
Table of Contents
Preface........................................................................................................................................................... 1
1. Introduction............................................................................................................................................. 4
1.1. Features....................................................................................................................................... 4
1.2. Kit Overview................................................................................................................................. 4
2. Getting Started........................................................................................................................................ 5
2.1. Quick Start....................................................................................................................................5
2.2. Design Documentation and Relevant Links................................................................................. 5
3. Curiosity Nano.........................................................................................................................................7
3.1. On-Board Debugger Overview..................................................................................................... 7
3.1.1. Debugger.......................................................................................................................7
3.1.2. Virtual Serial Port (CDC)................................................................................................8
3.1.2.1. Overview..................................................................................................... 8
3.1.2.2. Operating System Support.......................................................................... 8
3.1.2.3. Limitations................................................................................................... 9
3.1.2.4. Signaling......................................................................................................9
3.1.2.5. Advanced Use............................................................................................. 9
3.1.3. Mass Storage Device...................................................................................................10
3.1.3.1. Mass Storage Device Implementation.......................................................10
3.1.3.2. Fuse Bytes.................................................................................................11
3.1.3.3. Limitations of Drag-and-Drop Programming..............................................11
3.1.3.4. Special Commands................................................................................... 11
3.1.4. Data Gateway Interface (DGI)..................................................................................... 12
3.1.4.1. Debug GPIO..............................................................................................12
3.1.4.2. Timestamping............................................................................................12
3.2. Curiosity Nano Standard Pinout................................................................................................. 13
3.3. Power Supply............................................................................................................................. 13
3.3.1. Target Regulator.......................................................................................................... 14
3.3.2. External Supply............................................................................................................15
3.3.3. VBUS Output Pin.........................................................................................................16
3.3.4. Power Supply Exceptions............................................................................................16
3.4. Low Power Measurement...........................................................................................................17
3.5. Programming External Microcontrollers..................................................................................... 18
3.5.1. Supported Devices...................................................................................................... 18
3.5.2. Software Configuration................................................................................................ 18
3.5.3. Hardware Modifications............................................................................................... 19
3.5.4. Connecting to External Microcontrollers...................................................................... 20
3.6. Connecting External Debuggers................................................................................................ 21
4. Hardware User Guide........................................................................................................................... 24
4.1. Connectors.................................................................................................................................24
4.1.1. AVR128DA48 Curiosity Nano Pinout...........................................................................24
4.1.2. Using Pin Headers.......................................................................................................24
4.2. Peripherals................................................................................................................................. 25
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 2
AVR128DA48 Curiosity Nano
4.2.1. LED..............................................................................................................................25
4.2.2. Mechanical Switch.......................................................................................................25
4.2.3. Crystal..........................................................................................................................25
4.2.4. On-Board Debugger Implementation...........................................................................26
4.2.4.1. On-Board Debugger Connections............................................................. 26
5. Hardware Revision History and Known Issues..................................................................................... 27
5.1. Identifying Product ID and Revision........................................................................................... 27
5.2. Revision 3...................................................................................................................................27
6. Document Revision History...................................................................................................................28
7. Appendix............................................................................................................................................... 29
7.1. Schematic...................................................................................................................................29
7.2. Assembly Drawing......................................................................................................................31
7.3. Curiosity Nano Base for Click boards™...................................................................................... 32
7.4. Disconnecting the On-board Debugger......................................................................................33
7.5. Getting Started with IAR.............................................................................................................34
The Microchip Website.................................................................................................................................37
Product Change Notification Service............................................................................................................37
Customer Support........................................................................................................................................ 37
Microchip Devices Code Protection Feature................................................................................................ 37
Legal Notice................................................................................................................................................. 37
Trademarks.................................................................................................................................................. 38
Quality Management System....................................................................................................................... 38
Worldwide Sales and Service.......................................................................................................................39
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 3
1. Introduction
Micro USB
Connector
Debugger
Power/Status
LED
32.768 kHz
Crystal
User LED
(LED0)
User Switch
(SW0)
AVR128DA48
MCU
1.1 Features
• AVR128DA48-I/PT Microcontroller
• One Yellow User LED
• One Mechanical User Switch
• One 32.768 kHz Crystal
• On-Board Debugger:
– Board identification in Atmel Studio/Microchip MPLAB® X IDE
– One green power and status LED
– Programming and debugging
– Virtual serial port (CDC)
– Two debug GPIO channels (DGI GPIO)
• USB Powered
• Adjustable Target Voltage:
– MIC5353 LDO regulator controlled by the on-board debugger
– 1.8-5.1V output voltage (limited by USB input voltage)
– 500 mA maximum output current (limited by ambient temperature and output voltage)
AVR128DA48 Curiosity Nano
Introduction
1.2 Kit Overview
The Microchip AVR128DA48 Curiosity Nano Evaluation Kit is a hardware platform to evaluate the AVR128DA48
microcontroller.
Figure 1-1. AVR128DA48 Curiosity Nano Evaluation Kit Overview
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 4
2. Getting Started
2.1 Quick Start
Steps to start exploring the AVR128DA48 Curiosity Nano Board:
1. Download Atmel Studio/Microchip MPLAB® X IDE.
2. Launch Atmel Studio/Microchip MPLAB® X IDE.
3. Optional: Use MPLAB® Code Configurator or Atmel START to generate drivers and examples.
4. Write your application code.
5. Connect a USB cable (Standard-A to Micro-B or Micro-AB) between the PC and the debug USB port on the
board.
Driver Installation
When the board is connected to your computer for the first time, the operating system will perform a driver software
installation. The driver file supports both 32- and 64-bit versions of Microsoft® Windows® XP, Windows Vista®,
Windows 7, Windows 8, and Windows 10. The drivers for the board are included with Atmel Studio/Microchip
MPLAB® X IDE.
Kit Window
Once the board is powered, the green status LED will be lit, and Atmel Studio/Microchip MPLAB® X IDE will autodetect which boards are connected. Atmel Studio/Microchip MPLAB® X IDE will present relevant information like data
sheets and board documentation. The AVR128DA48 device on the AVR128DA48 Curiosity Nano Board is
programmed and debugged by the on-board debugger and, therefore, no external programmer or debugger tool is
required.
AVR128DA48 Curiosity Nano
Getting Started
Tip: The Kit Window can be opened in MPLAB X IDE through the menu bar Window > Kit Window.
2.2 Design Documentation and Relevant Links
The following list contains links to the most relevant documents and software for the AVR128DA48 Curiosity Nano
Board:
• MPLAB® X IDE - MPLAB X IDE is a software program that runs on a PC (Windows®, Mac OS®, Linux®) to
develop applications for Microchip microcontrollers and digital signal controllers. It is called an Integrated
Development Environment (IDE) because it provides a single integrated “environment” to develop code for
embedded microcontrollers.
• Atmel Studio - Free IDE for the development of C/C++ and assembler code for microcontrollers.
• IAR Embedded Workbench® for AVR® - This is a commercial C/C++ compiler that is available for AVR
microcontrollers. There is a 30-day evaluation version as well as a 4 KB code-size-limited kick-start version
available from their website.
• MPLAB® Code Configurator - MPLAB Code Configurator (MCC) is a free software plug-in that provides a
graphical interface to configure peripherals and functions specific to your application.
• Atmel START - Atmel START is an online tool that hosts code examples, helps the user to select and configure
software components, and tailor your embedded application in a usable and optimized manner.
• Microchip Sample Store - Microchip sample store where you can order samples of devices.
• MPLAB Data Visualizer - MPLAB Data Visualizer is a program used for processing and visualizing data. The
Data Visualizer can receive data from various sources such as serial ports and on-board debugger’s Data
Gateway Interface, as found on Curiosity Nano and Xplained Pro boards.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 5
AVR128DA48 Curiosity Nano
Getting Started
• Studio Data Visualizer - Studio Data Visualizer is a program used for processing and visualizing data. The
Data Visualizer can receive data from various sources such as serial ports, on-board debugger’s Data Gateway
Interface as found on Curiosity Nano and Xplained Pro boards, and power data from the Power Debugger.
• Microchip PIC® and AVR Examples - Microchip PIC and AVR Device Examples is a collection of examples
and labs that use Microchip development boards to showcase the use of PIC and AVR device peripherals.
• Microchip PIC® and AVR Solutions - Microchip PIC and AVR Device Solutions contains complete applications
for use with Microchip development boards, ready to be adapted and extended.
• AVR128DA48 Curiosity Nano website - Kit information, latest user guide and design documentation.
• AVR128DA48 Curiosity Nano on microchipDIRECT - Purchase this kit on microchipDIRECT.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 6
3. Curiosity Nano
Curiosity Nano is an evaluation platform of small boards with access to most of the microcontrollers I/Os. The
platform consists of a series of low pin count microcontroller (MCU) boards with on-board debuggers, which are
integrated with Atmel Studio/Microchip MPLAB® X IDE. Each board is identified in the IDE. When plugged in, a Kit
Window is displayed with links to key documentation, including relevant user guides, application notes, data sheets,
and example code. Everything is easy to find. The on-board debugger features a virtual serial port (CDC) for serial
communication to a host PC and a Data Gateway Interface (DGI) with debug GPIO pin(s).
3.1 On-Board Debugger Overview
AVR128DA48 Curiosity Nano contains an on-board debugger for programming and debugging. The on-board
debugger is a composite USB device consisting of several interfaces:
• A debugger that can program and debug the AVR128DA48 in Atmel Studio/Microchip MPLAB® X IDE
• A mass storage device that allows drag-and-drop programming of the AVR128DA48
• A virtual serial port (CDC) that is connected to a Universal Asynchronous Receiver/Transmitter (UART) on the
AVR128DA48, and provides an easy way to communicate with the target application through terminal software
• 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 AVR128DA48 Curiosity Nano Board.
The table below shows how the LED is controlled in different operation modes.
Table 3-1. On-Board Debugger LED Control
AVR128DA48 Curiosity Nano
Curiosity Nano
Operation Mode Power and Status LED
Boot Loader mode The LED blinks slowly during power-up.
Power-up The LED is ON.
Normal operation The LED is ON.
Programming Activity indicator: The LED blinks slowly during programming/debugging.
Drag-and-drop
programming
Fault The LED blinks rapidly if a power fault is detected.
Sleep/Off The LED is OFF. The on-board debugger is either in a sleep mode or powered down.
3.1.1 Debugger
The on-board debugger on the AVR128DA48 Curiosity Nano Board appears as a Human Interface Device (HID) on
the host computer’s USB subsystem. The debugger supports full-featured programming and debugging of the
AVR128DA48 using Atmel Studio/Microchip MPLAB® X IDE, as well as some third-party IDEs.
Success: The LED blinks slowly for 2 sec.
Failure: The LED blinks rapidly for 2 sec.
This can occur if the board is externally powered.
Info: Slow blinking is approximately 1 Hz, and rapid blinking is approximately 5 Hz.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 7
Remember: Keep the debugger’s firmware up-to-date. Firmware upgrades are done automatically when
Target MCU
UART TX
UART RX
Debugger
USB
CDC RX
CDC TX
PC
Terminal
Software
Target
Receive
Target
Send
Terminal
Receive
Terminal
Send
using Atmel Studio/Microchip MPLAB® X IDE.
3.1.2 Virtual Serial Port (CDC)
The virtual serial port (CDC) is a general purpose serial bridge between a host PC and a target device.
3.1.2.1 Overview
The on-board debugger implements a composite USB device that includes a standard Communications Device Class
(CDC) interface, which appears on the host as a virtual serial port. The CDC can be used to stream arbitrary data in
both directions between the host computer and the target: All characters sent through the virtual serial port on the
host computer will be transmitted as UART on the debugger’s CDC TX pin, and UART characters captured on the
debugger’s CDC RX pin will be returned to the host computer through the virtual serial port.
Figure 3-1. CDC Connection
AVR128DA48 Curiosity Nano
Curiosity Nano
Info: As shown in Figure 3-1, the debugger’s CDC TX pin is connected to a UART RX pin on the target
for receiving characters from the host computer. Similarly, the debugger’s CDC RX pin is connected to a
UART TX pin on the target for transmitting characters to the host computer.
3.1.2.2 Operating System Support
On Windows machines, the CDC will enumerate as Curiosity Virtual COM Port and appear in the Ports section of the
Windows Device Manager. The COM port number can also be found there.
Info: On older Windows systems, a USB driver is required for CDC. This driver is included in installations
of Atmel Studio/Microchip MPLAB® X IDE.
On Linux machines, the CDC will enumerate and appear as /dev/ttyACM#.
Info: tty* devices belong to the “dialout” group in Linux, so it may be necessary to become a member of
that group to have permissions to access the CDC.
On MAC machines, the CDC will enumerate and appear as /dev/tty.usbmodem#. Depending on which terminal
program is used, it will appear in the available list of modems as usbmodem#.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 8
3.1.2.3 Limitations
Not all UART features are implemented in the on-board debugger CDC. The constraints are outlined here:
• Baud rate: Must be in the range of 1200 bps to 500 kbps. Any baud rate outside this range will be set to the
closest limit, without warning. Baud rate can be changed on-the-fly.
• Character format: Only 8-bit characters are supported.
• Parity: Can be odd, even, or none.
• Hardware flow control: Not supported.
• Stop bits: One or two bits are supported.
3.1.2.4 Signaling
During USB enumeration, the host OS will start both communication and data pipes of the CDC interface. At this
point, it is possible to set and read back the baud rate and other UART parameters of the CDC, but data sending and
receiving will not be enabled.
When a terminal connects on the host, it must assert the DTR signal. As this is a virtual control signal implemented
on the USB interface, it is not physically present on the board. Asserting the DTR signal from the host will indicate to
the on-board debugger that a CDC session is active. The debugger will then enable its level shifters (if available), and
start the CDC data send and receive mechanisms.
Deasserting the DTR signal will not disable the level shifters but disable the receiver so no further data will be
streamed to the host. Data packets that are already queued up for sending to the target will continue to be sent out,
but no further data will be accepted.
AVR128DA48 Curiosity Nano
Curiosity Nano
Info: For all operating systems: Be sure to use a terminal emulator that supports DTR signaling. See
3.1.2.4 Signaling.
Remember: Set up the terminal emulator to assert the DTR signal. Without the signal, the on-board
debugger will not send or receive any data through its UART.
Tip: The on-board debugger’s CDC TX pin will not be driven until the CDC interface is enabled by the
host computer. Also, there are no external pull-up resistors on the CDC lines connecting the debugger and
the target, which means that during power-up, these lines are floating. To avoid any glitches resulting in
unpredictable behavior like framing errors, the target device should enable the internal pull-up resistor on
the pin connected to the debugger’s CDC TX pin.
3.1.2.5 Advanced Use
CDC Override Mode
In normal operation, the on-board debugger is a true UART bridge between the host and the device. However, in
certain use cases, the on-board debugger can override the basic operating mode and use the CDC TX and RX pins
for other purposes.
Dropping a text file into the on-board debugger’s mass storage drive can be used to send characters out of the
debugger’s CDC TX pin. The filename and extension are trivial, but the text file must start with the characters:
CMD:SEND_UART=
The maximum message length is 50 characters – all remaining data in the frame are ignored.
The default baud rate used in this mode is 9600 bps, but if the CDC is already active or has been configured, the
previously used baud rate still applies.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 9
USB-Level Framing Considerations
Sending data from the host to the CDC can be done byte-wise or in blocks, which will be chunked into 64-byte USB
frames. Each such frame will be queued up for sending to the debugger’s CDC TX pin. Transferring a small amount
of data per frame can be inefficient, particularly at low baud rates, because the on-board debugger buffers frames
and not bytes. A maximum of four 64-byte frames can be active at any time. The on-board debugger will throttle the
incoming frames accordingly. Sending full 64-byte frames containing data is the most efficient method.
When receiving data on the debugger’s CDC RX pin, the on-board debugger will queue up the incoming bytes into
64-byte frames, which are sent to the USB queue for transmission to the host when they are full. Incomplete frames
are also pushed to the USB queue at approximately 100 ms intervals, triggered by USB start-of-frame tokens. Up to
eight 64-byte frames can be active at any time.
If the host (or the software running on it) fails to receive data fast enough, an overrun will occur. When this happens,
the last-filled buffer frame will be recycled instead of being sent to the USB queue, and a full frame of data will be
lost. To prevent this occurrence, the user must ensure that the CDC data pipe is being read continuously, or the
incoming data rate must be reduced.
3.1.3 Mass Storage Device
The on-board debugger includes a simple Mass Storage Device implementation, which is accessible for read/write
operations via the host operating system to which it is connected.
It provides:
• Read access to basic text and HTML files for detailed kit information and support
• Write access for programming Intel® HEX formatted files into the target device’s memory
• Write access for simple text files for utility purposes
AVR128DA48 Curiosity Nano
Curiosity Nano
3.1.3.1 Mass Storage Device Implementation
The on-board debugger implements a highly optimized variant of the FAT12 file system that has several limitations,
partly due to the nature of FAT12 itself and optimizations made to fulfill its purpose for its embedded application.
The Curiosity Nano USB Device is USB Chapter 9-compliant as a mass storage device but does not, in any way,
fulfill the expectations of a general purpose mass storage device. This behavior is intentional.
When using the Windows operating system, the on-board debugger enumerates as a Curiosity Nano USB Device
that can be found in the disk drives section of the device manager. The CURIOSITY drive appears in the file manager
and claims the next available drive letter in the system.
The CURIOSITY drive contains approximately one MB of free space. This does not reflect the size of the target
device’s Flash in any way. When programming an Intel® HEX file, the binary data are encoded in ASCII with
metadata providing a large overhead, so one MB is a trivially chosen value for disk size.
It is not possible to format the CURIOSITY drive. When programming a file to the target, the filename may appear in
the disk directory listing. This is merely the operating system’s view of the directory, which, in reality, has not been
updated. It is not possible to read out the file contents. Removing and replugging the board will return the file system
to its original state, but the target will still contain the application that has been previously programmed.
To erase the target device, copy a text file starting with “CMD:ERASE” onto the disk.
By default, the CURIOSITY drive contains several read-only files for generating icons as well as reporting status and
linking to further information:
• AUTORUN.ICO – icon file for the Microchip logo
• AUTORUN.INF – system file required for Windows Explorer to show the icon file
• KIT-INFO.HTM – redirect to the development board website
• KIT-INFO.TXT – a text file containing details about the board’s debugger firmware version, board name, USB
serial number, device, and drag-and-drop support
• STATUS.TXT – a text file containing the programming status of the board
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 10
Info: STATUS.TXT is dynamically updated by the on-board debugger. The contents may be cached by
the OS and, therefore, do not reflect the correct status.
3.1.3.2 Fuse Bytes
Fuse Bytes (AVR® MCU Targets)
When doing drag-and-drop programming, the debugger masks out fuse bits that attempt to disable Unified Program
and Debug Interface (UPDI). This means that the UPDI pin cannot be used in its reset or GPIO modes; selecting one
of the alternative functions on the UPDI pin would render the device inaccessible without using an external debugger
capable of high-voltage UPDI activation.
3.1.3.3 Limitations of Drag-and-Drop Programming
Lock Bits
Lock bits included in the hex file will be ignored when using drag-and-drop programming. To program lock bits, use
Atmel Studio/Microchip MPLAB® X IDE.
Enabling CRC Check in Fuses
It is not advisable to enable the CRC check in the target device’s fuses when using drag-and-drop programming. This
because a subsequent chip erase (which does not affect fuse bits) will effect a CRC mismatch, and the application
will fail to boot. To recover a target from this state, a chip erase must be done using Atmel Studio/Microchip MPLAB
X IDE, which will automatically clear the CRC fuses after erasing.
AVR128DA48 Curiosity Nano
Curiosity Nano
®
3.1.3.4 Special Commands
Several utility commands are supported by copying text files to the mass storage disk. The filename or extension is
irrelevant – the command handler reacts to content only.
Table 3-2. Special File Commands
Command Content Description
CMD:ERASE
CMD:SEND_UART=
CMD:RESET
CMD:POWERTOGGLE
CMD:0V
CMD:3V3
CMD:5V0
Executes a chip erase of the target
Sends a string of characters to the CDC UART. See “CDC Override Mode”.
Resets the target device by entering Programming mode and then exiting
Programming mode immediately thereafter. Exact timing can vary according to
the programming interface of the target device. (Debugger firmware v1.16 or
newer.)
Powers down the target and restores power after a 100 ms delay. If external
power is provided, this has no effect. (Debugger firmware v1.16 or newer.)
Powers down the target device by disabling the target supply regulator. If
external power is provided, this has no effect. (Debugger firmware v1.16 or
newer.)
Sets the target voltage to 3.3V. If external power is provided, this has no effect.
(Debugger firmware v1.16 or newer.)
Sets the target voltage to 5.0V. If external power is provided, this has no effect.
(Debugger firmware v1.16 or newer.)
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 11
Info: The commands listed here are triggered by the content being sent to the mass storage emulated
disk, and no feedback is provided in the case of either success or failure.
3.1.4 Data Gateway Interface (DGI)
Data Gateway Interface (DGI) is a USB interface for transporting raw and timestamped data between on-board
debuggers and host computer-based visualization tools. MPLAB Data Visualizer is used on the host computer to
display debug 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 Atmel Studio/Microchip MPLAB® X IDE.
Although DGI encompasses several physical data interfaces, the AVR128DA48 Curiosity Nano implementation
includes logic analyzer channels:
• Two debug GPIO channels (also known as DGI GPIO)
3.1.4.1 Debug GPIO
Debug GPIO channels are timestamped digital signal lines connecting the target application to a host computer
visualization application. They are typically used to plot the occurrence of low-frequency events on a time-axis – for
example, when certain application state transitions occur.
The figure below shows the monitoring of the digital state of a mechanical switch connected to a debug GPIO in
MPLAB Data Visualizer.
Figure 3-2. Monitoring Debug GPIO with MPLAB® Data Visualizer
AVR128DA48 Curiosity Nano
Curiosity Nano
Debug GPIO channels are timestamped, so the resolution of DGI GPIO events is determined by the resolution of the
DGI timestamp module.
3.1.4.2 Timestamping
DGI sources are timestamped as they are captured by the debugger. The timestamp counter implemented in the
Curiosity Nano debugger increments at 2 MHz frequency, providing a timestamp resolution of a half microsecond.
© 2020 Microchip Technology Inc.
Important: Although bursts of higher-frequency signals can be captured, the useful frequency range of
signals for which debug GPIO can be used is up to about 2 kHz. Attempting to capture signals above this
frequency will result in data saturation and overflow, which may cause the DGI session to be aborted.
User Guide
DS50002971A-page 12
3.2 Curiosity Nano Standard Pinout
USB
DEBUGGER
PS LED
NC
ID
CDC RX
CDC TX
DBG1
DBG2
VBUS
VOFF
DBG3
DBG0
GND
VTG
CURIOSITY NANO
The 12 edge connections closest to the USB connector on Curiosity Nano boards have a standardized pinout. The
program/debug pins have different functions depending on the target programming interface, as shown in the table
and figure below.
Table 3-3. Curiosity Nano Standard Pinout
Debugger Signal Target MCU Description
ID — ID line for extensions
CDC TX UART RX USB CDC TX line
CDC RX UART TX USB CDC RX line
DBG0 UPDI Debug data line
DBG1 GPIO1 debug GPIO1
DBG2 GPIO0 debug GPIO0
DBG3 RESET Reset line
NC — No connect
AVR128DA48 Curiosity Nano
Curiosity Nano
VBUS — VBUS voltage for external use
VOFF — Voltage Off input. Disables the target regulator and
VTG — Target voltage
GND — Common ground
Figure 3-3. Curiosity Nano Standard Pinout
3.3 Power Supply
The board is powered through the USB port and contains two LDO regulators, one to generate 3.3V for the on-board
debugger, and an adjustable LDO regulator for the target microcontroller AVR128DA48 and its peripherals. The
voltage from the USB connector can vary between 4.4V to 5.25V (according to the USB specification) and will limit
the maximum voltage to the target. The figure below shows the entire power supply system on AVR128DA48
Curiosity Nano.
target voltage when pulled low.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 13
Figure 3-4. Power Supply Block Diagram
USB
Target
MCU
Power source
Cut strap
Power consumer
P3V3
DEBUGGER
Power converter
DEBUGGER
Regulator
VUSB
Target
Regulator
Power
Supply
strap
Adjust
Level
shifter
VLVL
VREG
I/O
I/O
GPIO
straps
I/O
On/Off
Measure
On/Off
ID system
#VOFF
PTC
Fuse
Power protection
VBUS
Target
Power
strap
VTG
3.3.1 Target Regulator
The target voltage regulator is a MIC5353 variable output LDO. The on-board debugger can adjust the voltage output
supplied to the board target section by manipulating the MIC5353’s feedback voltage. The hardware implementation
is limited to an approximate voltage range from 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 AVR128DA48
microcontroller. The voltage limits configured in the on-board debugger on AVR128DA48 Curiosity Nano are
1.8-5.1V.
AVR128DA48 Curiosity Nano
Curiosity Nano
Info: The target voltage is set to 3.3V when the board is manufactured. It can be changed through
MPLAB X IDE project properties and in the Atmel Studio device programming dialog. Any change to the
target voltage is persistent, even through a power toggle. The resolution is less than 5 mV but may be
limited to 10 mV by the adjustment program.
Info: Voltage settings that are set up in Atmel Studio/Microchip MPLAB® X IDE are not immediately
applied to the board. The new voltage setting is applied to the board when the debugger is accessed in
any way, like pushing the Refresh Debug Tool Status button in the project dashboard tab, or programming/
reading program memory.
Info: There is a simple option to adjust the target voltage with a drag and drop command text file to the
board. This only supports settings of 0.0V, 3.3V, and 5.0V. See section 3.1.3.4 Special Commands for
further details.
The MIC5353 supports a maximum current load of 500 mA. It is an LDO regulator in a small package, placed on a
small printed circuit board (PCB), and the thermal shutdown condition can be reached at lower loads than 500 mA.
The maximum current load depends on the input voltage, the selected output voltage, and the ambient temperature.
The figure below shows the safe operating area for the regulator, with an input voltage of 5.1V and an ambient
temperature of 23°C.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 14
WARNING
WARNING
WARNING
AVR128DA48 Curiosity Nano
Curiosity Nano
Figure 3-5. Target Regulator Safe Operation Area
The voltage output of the target regulator is continuously monitored (measured) by the on-board debugger. If it is
more than 100 mV over/under the voltage setting value, an error condition will be flagged, and the target voltage
regulator will be turned off. This will detect and handle any short-circuit conditions. It will also detect and handle if an
external voltage which causes VCC_TARGET to move outside of the voltage setting monitoring window of ±100 mV
is suddenly applied to the VTG pin, without setting the VOFF pin low.
Info: If the external voltage is lower than the monitoring window lower limit (target voltage setting - 100
mV), the on-board debugger status LED will blink rapidly. If the external voltage is higher than the
monitoring window upper limit (target voltage setting + 100 mV), the on-board debugger status LED will
continue to shine. If the external voltage is removed, the status LED will start to blink rapidly until the onboard debugger detects the new situation and turns the target voltage regulator back on.
3.3.2 External Supply
AVR128DA48 Curiosity Nano can be powered by an external voltage instead of the on-board target regulator. When
the Voltage Off (VOFF) pin is shorted to ground (GND), the on-board debugger firmware disables the target regulator,
and it is safe to apply an external voltage to the VTG pin.
It is also safe to apply an external voltage to the VTG pin when no USB cable is plugged into the DEBUG connector
on the board.
The VOFF pin can be tied low/let go at any time. This will be detected by a pin-change interrupt to the on-board
debugger, which controls the target voltage regulator accordingly.
Applying an external voltage to the VTG pin without shorting VOFF to GND may cause permanent damage
to the board.
Do not apply any voltage to the VOFF pin. Let the pin float to enable the power supply.
Absolute maximum external voltage is 5.5V for the on-board level shifters, and the standard operating
condition of the AVR128DA48 is 1.8-5.5V. Applying a higher voltage may cause permanent damage to the
board.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 15
Info: If an external voltage is applied without pulling the VOFF pin low and an external supply pulls the
voltage lower than the monitoring window lower limit (target voltage setting - 100 mV), the on-board
debugger status LED will blink rapidly and shut the on-board regulator off. If an external voltage is
suddenly removed when the VOFF pin is not pulled low, the status LED will start to blink rapidly, until the
on-board debugger detects the new situation and switches the target voltage regulator back on.
Programming, debugging, and data streaming is still possible with an external power supply – the debugger and
signal level shifters will be powered from the USB cable. Both regulators, the debugger and the level shifters, are
powered down when the USB cable is removed.
Info: In addition to the power consumed by the AVR128DA48 and its peripherals, approximately 100 µA
will be drawn from any external power source to power the on-board level shifters and voltage monitor
circuitry when a USB cable is plugged in the DEBUG connector on the board. When a USB cable is not
plugged in, some current is used to supply the level shifters voltage pins, which have a worst-case current
consumption of approximately 5 µA. Typical values may be as low as 100 nA.
3.3.3 VBUS Output Pin
AVR128DA48 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. The chart below shows the voltage versus the current
load of the VBUS output.
Figure 3-6. VBUS Output Voltage vs. Current
AVR128DA48 Curiosity Nano
Curiosity Nano
3.3.4 Power Supply Exceptions
This is a summary of most exceptions that can occur with the power supply.
Target Voltage Shuts Down
This can happen if the target section draws too much current at a given voltage. This will cause the thermal shutdown
safety feature of the MIC5353 regulator to kick in. To avoid this, reduce the current load of the target section.
Target Voltage Setting is Not Reached
The maximum output voltage is limited by the USB input voltage (specified to be between 4.4V to 5.25V), and the
voltage drop over the MIC5353 regulator at a given voltage setting and current consumption. If a higher output
voltage is needed, use a USB power source that can provide a higher input voltage or use an external voltage supply
on the VTG pin.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 16
AVR128DA48 Curiosity Nano
Curiosity Nano
Target Voltage is Different From Setting
This can be caused by an externally applied voltage to the VTG pin, without setting the VOFF pin low. If the target
voltage differ more than 100 mV over/under the voltage setting, it will be detected by the on-board debugger, and the
internal voltage regulator will be shut down. To fix this issue, remove the applied voltage from the VTG pin, and the
on-board debugger will enable the on-board voltage regulator when the new condition is detected. Note that the PS
LED will be blinking rapidly if the target voltage is below 100 mV of the setting, but will be lit normally when it is higher
than 100 mV above the setting.
No, Or Very Low Target Voltage, and PS LED is Blinking Rapidly
This can be caused by a full or partial short-circuit and is really a special case of the issue mentioned above. Remove
the short-circuit, and the on-board debugger will re-enable the on-board target voltage regulator.
No Target Voltage and PS LED is Lit 1
This occurs if the target voltage is set to 0.0V. To fix this, set the target voltage to a value within the specified voltage
range for the target device.
No Target Voltage and PS LED is Lit 2
This can be the issue if power jumper J100 and/or J101 is cut, and the target voltage regulator is set to a value within
the specified voltage range for the target device. To fix this, solder a wire/bridge between the pads for J100/J101, or
add a jumper on J101 if a pin header is mounted.
VBUS Output Voltage is Low or Not Present
This is most lightly caused by a high-current drain on VBUS, and the protection fuse (PTC) will reduce the current or
cut off completely. Reduce the current consumption on the VBUS pin to fix this issue.
3.4 Low Power Measurement
Power to the AVR128DA48 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 AVR128DA48 and other
peripherals connected to the board, cut the Target Power strap and connect an ammeter over the strap.
To measure the lowest possible power consumption follow these steps:
1. Cut the POWER strap with a sharp tool.
2. Solder a 1x2 100 mil pin header in the footprint.
3. Connect an ammeter to the pin header.
4. Write firmware that.
4.1. Tri-states any I/O connected to the on-board debugger.
4.2. Sets the microcontroller in its lowest power Sleep state.
5. Program the firmware into the AVR128DA48.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 17
Figure 3-7. Target Power Strap
Target Power strap (top side)
AVR128DA48 Curiosity Nano
Curiosity Nano
Tip: A 100-mil pin header can be soldered into the Target Power strap (J101) footprint for easy
connection of an ammeter. Once the ammeter is no longer needed, place a jumper cap on the pin header.
Info: The on-board level shifters will draw a small amount of current even when they are not in use. A
maximum of 2 µA can be drawn from each I/O pin connected to a level shifter for a total of 10 µA. Keep
any I/O pin connected to a level shifter are tri-state to prevent leakage. All I/Os connected to the on-board
debugger are listed in 4.2.4.1 On-Board Debugger Connections. To prevent any leakage to the on-board
level shifters, they can be disconnected completely, as described in 7.4 Disconnecting the On-board
Debugger.
3.5 Programming External Microcontrollers
The on-board debugger on AVR128DA48 Curiosity Nano can be used 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 Atmel Studio.
External SAM microcontrollers that have a Curiosity Nano Board can be programmed and debugged with the onboard debugger with Atmel Studio.
AVR128DA48 Curiosity Nano can program and debug external AVR128DA48 microcontrollers with MPLAB X IDE.
3.5.2 Software Configuration
No software configuration is required to program and debug the same device that is mounted on the board.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 18
AVR128DA48 Curiosity Nano
Curiosity Nano
To program and debug a different microcontroller than what is mounted on the board, Atmel Studio must be
configured to allow free selection of devices and programming interfaces.
1. Navigate to Tools > Options through the menu system at the top of the application.
2. Select the Tools > Tool settings category in the options window.
3. Set the Hide unsupported devices option to False .
Figure 3-8. Hide Unsupported Devices
Info: Atmel Studio allows any microcontroller and interface to be selected when Hide unsupported
devices is set to False, also microcontrollers and interfaces which are not supported by the on-board
debugger.
3.5.3 Hardware Modifications
The on-board debugger is connected to the AVR128DA48 by default. These connections must be removed 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 AVR128DA48 from the on-board debugger.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 19
GPIO straps (bottom side)
AVR128DA48 Curiosity Nano
Figure 3-9. Programming and Debugging Connections to Debugger
Curiosity Nano
Info: Cutting the connections to the debugger will disable programming, debugging, and data streaming
from the AVR128DA48 mounted on the board.
Tip: Solder in 0Ω resistors across the footprints or short-circuit them with solder to reconnect the signals
between the on-board debugger and the AVR128DA48.
3.5.4 Connecting to External Microcontrollers
The figure and table below show where the programming and debugging signals must be connected to program and
debug external microcontrollers. The on-board debugger can supply power to the external hardware, or use an
external voltage as a reference for its level shifters. Read more about the power supply in 3.3 Power Supply.
The on-board debugger and level shifters actively drive data and clock signals (DBG0, DBG1, and DBG2) used for
programming and debugging, and in most cases, the external resistor on these signals can be ignored. Pull-down
resistors are required on the ICSP™ data and clock signals to debug PIC® microcontrollers.
DBG3 is an open-drain connection and requires a pull-up resistor to function.
AVR128DA48 Curiosity Nano has a pull-up resistor R200 connected to its #RESET signal (DBG3). The location of
the pull-up resistor is shown in the 7.2 Assembly Drawing in the appendix.
Remember:
• Connect GND and VTG to the external microcontroller
• Tie the VOFF pin to GND if the external hardware has its own power supply
• Make sure there are pull-down resistors on the ICSP data and clock signals (DBG0 and DBG1) to
support the debugging of PIC microcontrollers
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 20
Figure 3-10. Curiosity Nano Standard Pinout
USB
DEBUGGER
PS LED
NC
ID
CDC RX
CDC TX
DBG1
DBG2
VBUS
VOFF
DBG3
DBG0
GND
VTG
CURIOSITY NANO
Table 3-4. Programming and Debugging Interfaces
AVR128DA48 Curiosity Nano
Curiosity Nano
Curiosity Nano Pin UPDI ICSP
DBG0 UPDI DATA SWDIO
DBG1 - CLK SWCLK
DBG2 - - -
DBG3 - #MCLR #RESET
3.6 Connecting External Debuggers
Even though there is an on-board debugger, external debuggers can be connected directly to the AVR128DA48
Curiosity Nano to program/debug the AVR128DA48. The on-board debugger keeps all the pins connected to the
AVR128DA48 and board edge in tri-state when not actively used. Therefore, the on-board debugger will not interfere
with any external debug tools.
™
SWD
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 21
2
3
4
5
678
1
VDD
Ground
DATA
2 = VDD
3 = Ground
4 = PGD
5 = Unused
6 = Unused
7 = Unused
8 = Unused
1 = Unused
MPLAB® PICkit™ 4
USB
DEBUGGER
PS LED
NC
ID
CDC RX
CDC TX
DBG1
DBG2
VBUS
VOFF
DBG3
DBG0
GND
VTG
CURIOSITY NANO
AVR128DA48 Curiosity Nano
Curiosity Nano
Figure 3-11. Connecting the MPLAB® PICkit™ 4 In-Circuit Debugger/Programmer to AVR128DA48 Curiosity
Nano
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 22
VDD
Ground
DATA
AVR®
SAM
3 = UPDI
4 = VTG
5 = Unused
6 = Unused
7 = Unused
8 = Unused
1 = Unused
2 = GND
9 = Unused
10 = Unused
Atmel-ICE
2
1
9
10
USB
DEBUGGER
PS LED
NC
ID
CDC RX
CDC TX
DBG1
DBG2
VBUS
VOFF
DBG3
DBG0
GND
VTG
CURIOSITY NANO
CAUTION
AVR128DA48 Curiosity Nano
Figure 3-12. Connecting the Atmel-ICE to AVR128DA48 Curiosity Nano
Curiosity Nano
To avoid contention between the external debugger and the on-board debugger, do not start any
programming/debug operation with the on-board debugger through Atmel Studio/Microchip MPLAB® X
IDE or mass storage programming while the external tool is active.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 23
4. Hardware User Guide
USB
DEBUGGER
AVR128DA48
SW0
LED0
PS LED
NC
NC
ID
ID
CDC RX
CDCRX
USART1 TXPC0
CDC TX
CDCTX
USART1 RXPC1
DBG1
DBG1
PC6LED0
DBG2
DBG2
PC7SW0
PA0
PA0
USART0 TXPTC XY0
PA1
PA1
USART0 RXPTC XY1
PC2
PC2
TWI0 SDA
PC3
PC3
TWI0 SCL
PA4
PA4
SPI0 MOSIPTC XY4
PA5
PA5
SPI0 MISOPTC XY5
PA6
PA6
SPI0 SCKPTC XY6
PA7
PA7
SPI0 SSPTC XY7
GND
GND
PF4
PF4
USART2 TXPTC XY36
PF5
PF5
USART2 RXPTC XY37
PF2
PF2
PTC XY34
PF3
PF3
PTC XY35
PB0
PB0
PTC XY8
PB1
PB1
PTC XY9
PB2
PB2
PTC XY10
PB3
PB3
PTC XY11
GND
GND
PC0
PC0
USART1 TXCDC RX
PC1
PC1
USART1 RXCDC TX
PC6
PC6
LED0
PC7
PC7
SW0
VBUS
VBUS
VOFF
VOFF
DBG3
DBG3
PF6
DBG0
DBG0
UPDI
GND
GND
VTG
VTG
PD7
PD7
AIN7 PTC XY23
PD6
PD6
AIN6 PTC XY22
PD2
PD2
AIN2 PTC XY18 TCA0 WO2
PD1
PD1
AIN1 PTC XY17 TCA0 WO1
PD0
PD0
AIN0 PTC XY16 TCA0 WO0
PD5
PD5
AIN5 PTC XY21
PD4
PD4
AIN4 PTC XY20
PD3
PD3
AIN3 PTC XY19
GND
GND
PE3
PE3
PTC XY27
PE2
PE2
PTC XY26
PE1
PE1
PTC XY25
PE0
PE0
PTC XY24
PA3
PA3
PTC XY3
PA2
PA2
PTC XY2
PB5
PB5
PTC XY13
PB4
PB4
PTC XY12
GND
GND
PC5
PC5
PC4
PC4
(PF1)
(PF1)
(PTC XY33) XTAL32K2
(PF0)
(PF0)
(PTC XY32) XTAL32K1
DEBUGGER
AVR128DA48
Analog
Debug
I2C
SPI
UART
Peripheral
Port
PWM
Power
Ground
Touch
Shared pin
AVR128DA48
Curiosity Nano
4.1 Connectors
4.1.1 AVR128DA48 Curiosity Nano Pinout
All the AVR128DA48 I/O pins are accessible at the edge connectors on the board. The image below shows the board
pinout.
Figure 4-1. AVR128DA48 Curiosity Nano Pinout
AVR128DA48 Curiosity Nano
Hardware User Guide
4.1.2 Using Pin Headers
The edge connector footprint on AVR128DA48 Curiosity Nano has a staggered design where each hole is shifted 8
mil (~0.2 mm) off-center. The hole shift allows the use of regular 100 mil pin headers on the board without soldering.
Once the pin headers are firmly in place, they can be used in normal applications like pin sockets and prototyping
boards without any issues.
© 2020 Microchip Technology Inc.
Tip: Start at one end of the pin header and gradually insert the header along the length of the board.
Once all the pins are in place, use a flat surface to push them in.
Tip: For applications where the pin headers will be used permanently, it is still recommended to solder
them in place.
User Guide
DS50002971A-page 24
Important: Once the pin headers are in place, they are hard to remove by hand. Use a set of pliers and
carefully remove the pin headers to avoid damage to the pin headers and PCB.
4.2 Peripherals
4.2.1 LED
There is one yellow user LED available on the AVR128DA48 Curiosity Nano Board that can be controlled by either
GPIO or PWM. The LED can be activated by driving the connected I/O line to GND.
Table 4-1. LED Connection
AVR128DA48 Pin Function Shared Functionality
PC6 Yellow LED0 Edge connector, On-board debugger
4.2.2 Mechanical Switch
The AVR128DA48 Curiosity Nano has one mechanical switch. This is a generic user-configurable switch. When the
switch is pressed, it will drive the I/O line to ground (GND).
AVR128DA48 Curiosity Nano
Hardware User Guide
Table 4-2. Mechanical Switch
PC7 User switch (SW0) Edge connector, On-board debugger
4.2.3 Crystal
The AVR128DA48 Curiosity Nano board has a 32.768 kHz crystal mounted.
The AVR128DA48 is connected to the crystal by default, but the GPIOs are also routed to the edge connector
through two solder points. The two I/O lines routed to the edge connector are disconnected by default to reduce the
chance of an external signal causing contention with the crystal, and to remove excessive capacitance on the lines.
To use PF0 and PF1 as GPIO, some hardware modifications are required.
• Disconnect the crystal by cutting the two straps on the top side of the board next to the crystal (J210, J211). The
crystal should be disconnected when using the pin as GPIO, as this might harm the crystal.
• Connect the I/O lines to the edge connector by placing solder blobs on the circular solder points marked PF0
and PF1 on the bottom side of the board (J207, J208)
The cut straps and solder points can be seen in Figure 4-2.
Table 4-3. Crystal Connections
Tip: There is no externally connected pull-up resistor on the switch. To use the switch, make sure that an
internal pull-up resistor is enabled on pin PC7.
AVR128DA48 Pin Description Shared Functionality
AVR128DA48 Pin Function Shared Functionality
PF0 TOSC1 (Crystal input) Edge connector
PF1 TOSC2 (Crystal output) Edge connector
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 25
Figure 4-2. Crystal Connection and Cut Straps
4.2.4 On-Board Debugger Implementation
AVR128DA48 Curiosity Nano features an on-board debugger that can be used to program and debug the
AVR128DA48 using UPDI. The on-board debugger also includes a virtual serial port (CDC) interface over UART and
debug GPIO. Atmel Studio/Microchip MPLAB® X IDE can be used as a front-end for the on-board debugger for
programming and debugging. MPLAB Data Visualizer can be used as a front-end for the CDC and debug GPIO.
4.2.4.1 On-Board Debugger Connections
The table below shows the connections between the target and the debugger section. All connections between the
target and the debugger are tri-stated as long as the debugger is not actively using the interface. Hence, since there
are little contaminations of the signals, the pins can be configured to anything the user wants.
For further information on how to use the capabilities of the on-board debugger, see 3.1 On-Board Debugger
Overview.
Table 4-4. On-Board Debugger Connections
AVR128DA48 Curiosity Nano
Hardware User Guide
AVR128DA48
Pin
RF1 CDC TX UART RX (AVR128DA48 RX line) Edge connector
RF0 CDC RX UART TX (AVR128DA48 TX line) Edge connector
UPDI DBG0 UPDI Edge connector
PC6 DBG1 GPIO1 Edge connector, LED
PC7 DBG2 GPIO0 Edge connector, Mechanical Switch
PF6 DBG3 RESET Edge connector
Debugger Pin Function Shared Functionality
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 26
AVR128DA48 Curiosity Nano
Hardware Revision History and Known Issues
5. Hardware Revision History and Known Issues
This user guide is written to provide information about the latest available revision of the board. The following
sections contain information about known issues, a revision history of older revisions, and how older revisions differ
from the latest revision.
5.1 Identifying Product ID and Revision
The revision and product identifier of the AVR128DA48 Curiosity Nano Board can be found in two ways: Either by
utilizing the Atmel Studio/Microchip MPLAB® X IDE Kit Window or by looking at the sticker on the bottom side of the
PCB.
By connecting AVR128DA48 Curiosity Nano to a computer with Atmel Studio/Microchip MPLAB® X IDE running, the
Kit Window will pop up. The first six digits of the serial number, which is listed under kit information, contain the
product identifier and revision.
Tip: The Kit Window can be opened in MPLAB® X IDE through the menu bar Window > Kit Window.
The same information can be found on the sticker on the bottom side of the PCB. Most boards will have the identifier
and revision printed in plain text as A09-nnnn\rr, where “nnnn” is the identifier, and “rr” is the revision. Boards with
limited space have a sticker with only a data matrix code, containing the product identifier, revision, and serial
number.
The serial number string has the following format:
"nnnnrrssssssssss"
n = product identifier
r = revision
s = serial number
The product identifier for AVR128DA48 Curiosity Nano is A09-3280.
5.2 Revision 3
Revision 3 is the initially released revision. There are no known issues with this revision.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 27
6. Document Revision History
Doc. rev. Date Comment
A 03/2020 Initial document release.
AVR128DA48 Curiosity Nano
Document Revision History
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 28
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
D D
C C
B B
A A
2 of 4
AVR128DA48 Curiosity Nan o
10/23/2019
AVR128DA48_Curiosity_Nano_Target_MCU.SchDoc
Project Title
PCB Assembly Number: PCBA Revision:
File:
PCB Number: PCB Revision:
Designed with
Drawn By:
PB
Sheet Title
Target MCU
Engineer:
AH, TF
A08-3002 3
Size
A3
A09-3280 3
Page:
Date:
Altium.com
GNDVCC_TARGET
100n
C201
GND
PA5_SPI0_MISO
PA6_SPI0_SCK
PA7_SPI0_SS
PB0_UART3_TX
PB1_UART3_RX
PB2
PB3
PB4
PB5
PC0_UART1_TX
PC1_UART1_RX
PC2_I2C0_SDA
PC3_I2C0_SCL
PC4
PC5
PC6_LED0_GPIO1
PC7_SW0_GPIO0
PD0_AIN0_WO0
PD1_AIN1_WO1
PD2_AIN2_WO2
PD3_AIN3
PD4_AIN4
PA3
PA1_UART0_RX
UPDI
PF5_UART2_RX
PF3
PF2
PF1_TOSC2
PF0_TOSC1
PE3
PE2
PE1
PE0
PD5_AIN5
PD6_AIN6
PD7_AIN7
GND
VCC_TARGET
100n
C202
GND VCC_TARGET
100n
C200
PF1_TOSC2
PF0_TOSC1
PA2
PA0_UART0_TX
PF4_UART2_TX
PA4_SPI0_MOSI
GND
PA7_SPI0_SS
PA6_SPI0_SCK
PA5_SPI0_MISO
PA4_SPI0_MOSI
PA3
PA2
PA1_UART0_RX
PA0_UART0_TX
PB0_UART3_TX
PB1_UART3_RX
PB2
PB3 PB4
PB5
PD7_AIN7
PD6_AIN6
PF5_UART2_RX
PF4_UART2_TX
PF3
PF2
32kHz C rysta l
1k
R203
USER LE D
VCC_TARGET
PF6_RESET
PC7_SW0_GPIO0
PC6_LED0_GPIO1
GND
USER BUTT ON
PE3
PE2
PE1
PE0
PC0_UART1_TX
PC1_UART1_RX
PC2_I2C0_SDA
PC3_I2C0_SCL
PC4
PC5
PC6_LED0_GPIO1
PC7_SW0_GPIO0
1k
R202
YELLOW LED
SML-D12Y1WT86
21
D200
TS604VM1-035CR
1 3
42
SW200
GND
VCC_EDGE
GNDGND
GND GND
UPDI
PF6_RESET
J207
J208
J209
BLM18PG471SN1
L200
AVR128DA48
2.2uF
C205
VCC_EDGE
GND
DBG0
CDC_UART
TX
RX
UART
CDC_TX
CDC_RX
DBG2
DBG1
DBG3
DBG2
DEBUGG ER CONNE CTIO NS
DBG1
DBG3
DBG0
VOFF
ID_SYS
ID_SYS
VOFF
TARGET BULK
VCC_TARGET
RESET Pull
VBUS
CDC RX
3
CDC TX
4
DBG1
5
DBG2
6
0 TX
7
1 RX
8
2 SDA
9
3 SCL
10
4 MOSI
11
5 MISO
12
6 SCK
13
7 SS
14
GND
15
0 (TX)
16
1 (RX)
17
2
18
3
19
0
20
GND
24
DBG3
54
DBG0
53
GND
52
VCC
51
PWM 3
46
ADC 2
45
ADC 1
44
ADC 0
43
GND
42
4
38
4
34
GND
33
ADC 7
50
ADC 6
49
ADC 5
48
PWM 4
47
DEBUGGER
TARGET
ID
2
VOFF
55
1
21
2
22
3
23
0
25
1
26
2
27
3
28
4
29
5
30
6
31
7
32
5
35
6
36
7
37
5
39
6
40
7
41
RESERVED
1
VBUS
56
CNANO56-pin edge connector
J200
J201
J203
J205
J206
J202
J204
PF1
PF0
PF1_TOSC2
PF0_TOSC1
NC
J211
J210
XOUT
XIN
47k
R200
AVR128DA48
UPDI
GPIO1
GPIO0
RESET
DBG0
DBG1
DBG2
DBG3
Debugger
CDC TX
CDC RX
UART1 RX
UART1 TX
VTG 1.8V - 5.5V
PC6
PC7
PF6
UPDI
PC0
PC1
Name Pin
PA51PA62PA73PB04PB15PB26PB37PB48PB59PC010PC111PC2
12
PC3
13
VDD
14
GND
15
PC4
16
PC5
17
PC6
18
PC7
19
PD0
20
PD1
21
PD2
22
PD3
23
PD4
24
PD525PD626PD7
27
AVDD
28
GND29PE030PE131PE232PE3
33
XTAL32K1/PF0
34
XTAL32K2/PF1
35
PF2
36
PF3
37
PF4
38
PF5
39
PF6
40
UPDI
41
VDD
42
GND
43
EXTCLK/PA0
44
PA1
45
PA2
46
PA3
47
PA4
48
AVR128DA48 TQFPU200
PC0_UART1_TX
PC1_UART1_RX
PC6_LED0_GPIO1
PC7_SW0_GPIO0
AVDD
PD2_AIN2_WO2
PD1_AIN1_WO1
PD0_AIN0_WO0
PD5_AIN5
PD4_AIN4
PD3_AIN3
XC200
12p
C203
12p
C204
32.768 kHz
Crystal datasheet:
Ccrystal = 9pF
max ESR = 70kOhm
Accuracy ±20ppm
AVR128DA48 datasheet:
Cxin = 4.1pF
Cxout = 6.0pF
Cl ≈ 1/( (1/4.1pF)+ (1/6.0pF) ) ≈ 2.44pF
Maximum Load = 12.5pF
Maximum ESR = 80kOhm
Estimated Cpcb = 0.5pF
Estimated load
C = 2 (Ccrystal- Cpara - Cpcb)
C = 2 (9pF - 2.44pF - 0.5pF)
C = 12.12pF
Selected in design after verification
C= 12pF/12pF
RX/TX on the header denotes the
input/output direction of the signal
respective to it's source.
CDC TX is output from the
DEBUGGER.
CDC RX is input to the DEBUGGER.
TX is output from the TARGET device.
RX is input to the TARGET device.
AVR128DA48 Curiosity Nano
Appendix
7. Appendix
7.1 Schematic
Figure 7-1. AVR128DA48 Curiosity Nano Schematic
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 29
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
D D
C C
B B
A A
3 of 4
AVR128DA48 Curiosity Nan o
10/23/2019
AVR128DA48_Curiosity_Nano_Debugger.SchDoc
Project Title
PCB Assembly Number: PCBA Revision:
File:
PCB Number: PCB Revision:
Designed with
Drawn By:
PB
Sheet Title
Debugger
Engineer:
AH, TF
A08-3002 3
Size
A3
A09-3280 3
Page:
Date:
Altium.com
DEBUGG ER USB MIC RO-B CONNE CTOR
GND
USBD_P
USBD_N
100n
C107
100n
C108
RX
TX
UART
CDC_UART
1k
R107
VCC_P3V3
SRST
STATUS_LED
SHIELD
VBUS
VCC_P3V3
GND
TP100
Testpoint Array
1 2
3 4
5 6
7 8
9 10
TCK
TDO
TMS
Vsup
TDI GND
TRST
SRST
VTref
GND
J102
GND
4.7uF
C100
DBG0
DBG0
21
GREEN LED
SML-P12MTT86R
D100
VBUS1D-2D+3GND5SHIELD16SHIELD27ID4SHIELD38SHIELD4
9
MU-MB0142AB2-269
J105
PAD
33
PA001PA012PA023PA03
4
GND
10
VDDANA
9
PA045PA056PA067PA07
8
PA08
11
PA09
12
PA10
13
PA11
14
PA14
15
PA15
16
PA1617PA1718PA1819PA1920PA22
21
USB_SOF/PA23
22
USB_DM/PA2423USB_DP/PA25
24
PA27
25
RESETN
26
PA28
27
GND
28
VDDCORE
29
VDDIN
30
SWDCLK/PA30
31
SWDIO/PA31
32
SAMD21E18A-MUT
U100
VOUT1VOUT
2
GND
3
EN4VIN
6
NC
5
EP
7
MIC5528-3.3YMTU101 VCC_P3V3
GND
USBD_P
USBD_N
GND
1u
C106
VCC_MCU_CORE
VCC_P3V3
VCC_P3V3
2.2uF
C101
GND
74LVC1T45FW4-7
VCCA
1
VCCB
6
A
3
GND
2
DIR5B
4
U103
VCC_P3V3
GND
74LVC1T45FW4-7
VCCA
1
VCCB
6
A
3
GND
2
DIR5B
4
U104
VCC_P3V3
GND
74LVC1T45FW4-7
VCCA
1
VCCB
6
A
3
GND
2
DIR5B
4
U105
VCC_P3V3
GND
GND
GND
GND
VCC_EDGE
GND
74LVC1T45FW4-7
VCCA
1
VCCB
6
A
3
GND
2
DIR5B
4
U107
VCC_P3V3
GND
DBG2
DBG3_CTRL
S1_0_TX
S1_1_RX
S0_2_TX
DAC
VTG_ADC
RESERVED
S0_3_CLK
DBG0_CTRL
CDC_TX_CTRL
BOOT
DEBUGGE R POWE R/STATUS LED
EN
1
BYP
6
VOUT
4
GND
2
VIN
3
NC/ADJ
5
GND
7
MIC5353U102
100n
C102
GND
GND
47k
R101
27k
R104
GND
33k
R106
2.2uF
C103
GND
1k
R108
J100
VCC_LEVELVCC_REGULATOR
74LVC1T45FW4-7
VCCA
1
VCCB
6
A
3
GND
2
DIR5B
4
U106
VCC_P3V3
GND
DBG1
CDC_RX
CDC_TX
DBG3
DBG1_CTRL
DEBUGGE R REGUL ATOR
REG_ENABLE
REG_ENABLE
47k
R103
VCC_LEVEL
VCC_LEVEL
VCC_LEVEL
VCC_LEVEL
VCC_LEVEL
47k
R102
47k
R105
SWCLK
GND
47k
R100
GND
DBG2
S0_0_RX
DBG1_CTRL
DBG0_CTRL
DBG3 OP EN DRAIN
TARGET ADJUSTABLE RE GULATOR
SRST
DEBUGGE R TEST POINT
DBG2_CTRL
VOFF
CDC_RX_CTRL
47k
R109
DBG1
CDC_TX_CTRL
CDC_RX_CTRL
SWCLK
REG_ADJUST
DBG2_GPIO
DBG3_CTRL
DBG2_CTRL
UPDI
UPDI
GPIO
GPIO
RESET
Signal
DBG0
DBG1
DBG2
DBG3
ICSP
Interface
DAT
CLK
GPIO
MCLR
DBG3
CDC TX
CDC RX
UART RX
UART TX
UART RX
UART TX
TARGET TARGET
1k
R110
VBUS_ADC
1
2 3
DMN65D8LFB
Q101
VCC - -
ID_SYS
VOFF
1k
R112
VCC_P3V3
VTG_ADC
DAC
MIC94163
VIN
B2
VOUT
A1
VINA2EN
C2
GND
C1
VOUT
B1
U108
GND
ID_SYS
VTG_EN
VTG_EN
VBUS_ADC
SWDIO
ID_SYS
TP101
GND
SWDIO
VOFF
47k
R111
GND
ID PI N
MC36213
F100
VCC_VBUS
VCC_VBUS
VCC_VBUS
J101
VCC_TARGET
47k
R113
Programming connector for
factory programming of
DEBUGGER.
MIC5528:
Vin: 2.5V to 5.5V
Vout: Fixed 3.3V
Imax: 500mA
PTC Resettable fuse:
Hold current: 500mA
Adjustable output and limitations:
- The DEBUGGER can adjust the output voltage of the regulator between 1.25V and 5.1V to the target.
- The voltage output is limited by the input (USB), which can vary between 4.40V to 5.25V
- The level shifters have a minimal voltage level of 1.65V and will limit the minimum operating voltage allowed for the
target to still allow communication.
- The MIC94163 has a minimal voltage level of 1.70V and will limit the minimum voltage delivered to the target.
- Firmware configuration will limit the voltage range to be within the the target specification.
R113 is required to pull the
Q101 gate to a defined
value when the U100 is not
J100:
Cut-strap used for full separation of target power from the level shifters and on-board regulators.
- For current measurements using an external power supply, this strap could be cut for more
accurate measurements. Leakage back through the switch is in the micro ampere range.
J101:
This is footprint for a 1x2 100mil pitch pin-header that can be used for easy current measurement
to the target microcontroller and the LED / Button. To use the footprint:
- Cut the track between the holes, and mount a pin-header
MIC5353:
Vin: 2.6V to 6V
Vout: 1.25V to 5.1V
Imax: 500mA
Dropout (typical): 50mV@150mA, 160mV @ 500mA
Accuracy: 2% initial
Thermal shutdown and current limit
Maximum output voltage is limited by the input voltage and the dropout voltage in the regulator.
(Vmax = Vin - dropout)
AVR128DA48 Curiosity Nano
Appendix
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 30
7.2 Assembly Drawing
C
b
PAC10001
PAC10002
COC100
PAC10101
PAC10102
COC101
PAC10202
PAC10201
COC102
PAC10302
PAC10301
COC103
PAC10601
PAC10602
COC106
PAC10701
PAC10702
COC107
PAC10801
PAC10802
COC108
PAC20002
PAC20001
COC200
PAC20102
PAC20101
COC201
PAC20202
PAC20201
COC202
PAC20301
PAC20302
COC203
PAC20401
PAC20402
COC204
PAC20502
PAC20501
COC205
PAD10002
PAD10001
COD100
PAD20001
PAD20002
COD200
PAF10002
PAF10001
COF100
PAJ10002
PAJ10001
COJ100
PAJ10101
PAJ10102
COJ101
PAJ10201
PAJ10202
PAJ10203
PAJ10204
PAJ10205
PAJ10206
COJ102
PAJ10506
PAJ10507
PAJ10509
PAJ10508
PAJ105010
PAJ105011
PAJ10505
PAJ10504
PAJ10503
PAJ10502
PAJ10501
PAJ10500
COJ105
PAJ200056
PAJ200053
PAJ200028
PAJ20002
PAJ20001
PAJ200051
PAJ200050
PAJ200052
PAJ200049
PAJ200048
PAJ200047
PAJ200046
PAJ200045
PAJ200044
PAJ200043
PAJ200042
PAJ200041
PAJ200040
PAJ200039
PAJ200038
PAJ200037
PAJ200036
PAJ200035
PAJ200034
PAJ200033
PAJ200032
PAJ200031
PAJ200030
PAJ200029
PAJ20003
PAJ20004
PAJ20005
PAJ20006
PAJ20007
PAJ20008
PAJ20009
PAJ200010
PAJ200011
PAJ200012
PAJ200013
PAJ200014
PAJ200015
PAJ200016
PAJ200017
PAJ200018
PAJ200019
PAJ200020
PAJ200021
PAJ200022
PAJ200023
PAJ200026
PAJ200025
PAJ200024
PAJ200027
PAJ200054
PAJ200055
PAJ20000
COJ200
PAJ20102
PAJ20101
COJ201
PAJ20202
PAJ20201
COJ202
PAJ20302
PAJ20301
COJ203
PAJ20402
PAJ20401
COJ204
PAJ20502
PAJ20501
COJ205
PAJ20602
PAJ20601
COJ206
PAJ20701
PAJ20702
PAJ20705
COJ207
PAJ20801
PAJ20802
PAJ20805
COJ208
PAJ20901
PAJ20902
COJ209
PAJ21002
PAJ21001
COJ210
PAJ21102
PAJ21101
COJ211
PAL20002
PAL20001
COL200
COLABEL1
PAQ10101
PAQ10102
PAQ10103
PAQ10100
COQ101
PAR10002
PAR10001
COR100
PAR10101
PAR10102
COR101
PAR10202
PAR10201
COR102
PAR10302
PAR10301
COR103
PAR10401
PAR10402
COR104
PAR10502
PAR10501
COR105
PAR10601
PAR10602
COR106
PAR10702
PAR10701
COR107
PAR10801
PAR10802
COR108
PAR10901
PAR10902
COR109
PAR11001
PAR11002
COR110
PAR11101
PAR11102
COR111
PAR11201
PAR11202
COR112
PAR11302
PAR11301
COR113
PAR20002
PAR20001
COR200
PAR20201
PAR20202
COR202
PAR20301
PAR20302
COR203
PASW20003
PASW20004
PASW20002
PASW20001
COSW200
PATP10001
COTP100
PATP10101
COTP101
PAU100033
PAU100032
PAU100031
PAU100030
PAU100029
PAU100028
PAU100027
PAU100026
PAU100025
PAU100024
PAU100023
PAU100022
PAU100021
PAU100020
PAU100019
PAU100018
PAU100017
PAU100016
PAU100015
PAU100014
PAU100013
PAU100012
PAU100011
PAU100010
PAU10001
PAU10002
PAU10003
PAU10004
PAU10005
PAU10006
PAU10007
PAU10008
PAU10009
COU100
PAU10107
PAU10104
PAU10105
PAU10106
PAU10103
PAU10102
PAU10101
PAU10100
COU101
PAU10207
PAU10204
PAU10205
PAU10206
PAU10203
PAU10202
PAU10201
COU102
PAU10306
PAU10305
PAU10304
PAU10303
PAU10302
PAU10301
PAU10300
COU103
PAU10406
PAU10405
PAU10404
PAU10403
PAU10402
PAU10401
PAU10400
COU104
PAU10506
PAU10505
PAU10504
PAU10503
PAU10502
PAU10501
PAU10500
COU105
PAU10606
PAU10605
PAU10604
PAU10603
PAU10602
PAU10601
PAU10600
COU106
PAU10706
PAU10705
PAU10704
PAU10703
PAU10702
PAU10701
PAU10700
COU107
PAU1080A1
PAU1080A2
PAU1080B1
PAU1080B2
PAU1080C1
PAU1080C2
COU108
PAU200048
PAU200047
PAU200046
PAU200045
PAU200044
PAU200043
PAU200042
PAU200041
PAU200040
PAU200039
PAU200038
PAU200037
PAU200036
PAU200035
PAU200034
PAU200033
PAU200032
PAU200031
PAU200030
PAU200029
PAU200028
PAU200027
PAU200026
PAU200025
PAU200024
PAU200023
PAU200022
PAU200021
PAU200020
PAU200019
PAU200018
PAU200017
PAU200016
PAU200015
PAU200014
PAU200013
PAU200012
PAU200011
PAU200010
PAU20009
PAU20008
PAU20007
PAU20006
PAU20005
PAU20004
PAU20003
PAU20002
PAU20001
COU200
PAXC20001
PAXC20002
COXC200
c
t
R
PAC10001
PAC10002
COC100
PAC10101
PAC10102
COC101
PAC10202
PAC10201
COC102
PAC10302
PAC10301
COC103
PAC10601
PAC10602
COC106
PAC10701
PAC10702
COC107
PAC10801
PAC10802
COC108
PAC20002
PAC20001
COC200
PAC20102
PAC20101
COC201
PAC20202
PAC20201
COC202
PAC20301
PAC20302
COC203
PAC20401
PAC20402
COC204
PAC20502
PAC20501
COC205
PAD10002
PAD10001
COD100
PAD20001
PAD20002
COD200
PAF10002
PAF10001
COF100
PAJ10002
PAJ10001
COJ100
PAJ10101
PAJ10102
COJ101
PAJ10201
PAJ10202
PAJ10203
PAJ10204
PAJ10205
PAJ10206
COJ102
PAJ10506
PAJ10507
PAJ10509
PAJ10508
PAJ105010
PAJ105011
PAJ10505
PAJ10504
PAJ10503
PAJ10502
PAJ10501
PAJ10500
COJ105
PAJ200056
PAJ200053
PAJ200028
PAJ20002
PAJ20001
PAJ200051
PAJ200050
PAJ200052
PAJ200049
PAJ200048
PAJ200047
PAJ200046
PAJ200045
PAJ200044
PAJ200043
PAJ200042
PAJ200041
PAJ200040
PAJ200039
PAJ200038
PAJ200037
PAJ200036
PAJ200035
PAJ200034
PAJ200033
PAJ200032
PAJ200031
PAJ200030
PAJ200029
PAJ20003
PAJ20004
PAJ20005
PAJ20006
PAJ20007
PAJ20008
PAJ20009
PAJ200010
PAJ200011
PAJ200012
PAJ200013
PAJ200014
PAJ200015
PAJ200016
PAJ200017
PAJ200018
PAJ200019
PAJ200020
PAJ200021
PAJ200022
PAJ200023
PAJ200026
PAJ200025
PAJ200024
PAJ200027
PAJ200054
PAJ200055
PAJ20000
COJ200
PAJ20102
PAJ20101
COJ201
PAJ20202
PAJ20201
COJ202
PAJ20302
PAJ20301
COJ203
PAJ20402
PAJ20401
COJ204
PAJ20502
PAJ20501
COJ205
PAJ20602
PAJ20601
COJ206
PAJ20701
PAJ20702
PAJ20705
COJ207
PAJ20801
PAJ20802
PAJ20805
COJ208
PAJ20901
PAJ20902
COJ209
PAJ21002
PAJ21001
COJ210
PAJ21102
PAJ21101
COJ211
PAL20002
PAL20001
COL200
COLABEL1
PAQ10101
PAQ10102
PAQ10103
PAQ10100
COQ101
PAR10002
PAR10001
COR100
PAR10101
PAR10102
COR101
PAR10202
PAR10201
COR102
PAR10302
PAR10301
COR103
PAR10401
PAR10402
COR104
PAR10502
PAR10501
COR105
PAR10601
PAR10602
COR106
PAR10702
PAR10701
COR107
PAR10801
PAR10802
COR108
PAR10901
PAR10902
COR109
PAR11001
PAR11002
COR110
PAR11101
PAR11102
COR111
PAR11201
PAR11202
COR112
PAR11302
PAR11301
COR113
PAR20002
PAR20001
COR200
PAR20201
PAR20202
COR202
PAR20301
PAR20302
COR203
PASW20003
PASW20004
PASW20002
PASW20001
COSW200
PATP10001
COTP100
PATP10101
COTP101
PAU100033
PAU100032
PAU100031
PAU100030
PAU100029
PAU100028
PAU100027
PAU100026
PAU100025
PAU100024
PAU100023
PAU100022
PAU100021
PAU100020
PAU100019
PAU100018
PAU100017
PAU100016
PAU100015
PAU100014
PAU100013
PAU100012
PAU100011
PAU100010
PAU10001
PAU10002
PAU10003
PAU10004
PAU10005
PAU10006
PAU10007
PAU10008
PAU10009
COU100
PAU10107
PAU10104
PAU10105
PAU10106
PAU10103
PAU10102
PAU10101
PAU10100
COU101
PAU10207
PAU10204
PAU10205
PAU10206
PAU10203
PAU10202
PAU10201
COU102
PAU10306
PAU10305
PAU10304
PAU10303
PAU10302
PAU10301
PAU10300
COU103
PAU10406
PAU10405
PAU10404
PAU10403
PAU10402
PAU10401
PAU10400
COU104
PAU10506
PAU10505
PAU10504
PAU10503
PAU10502
PAU10501
PAU10500
COU105
PAU10606
PAU10605
PAU10604
PAU10603
PAU10602
PAU10601
PAU10600
COU106
PAU10706
PAU10705
PAU10704
PAU10703
PAU10702
PAU10701
PAU10700
COU107
PAU1080A1
PAU1080A2
PAU1080B1
PAU1080B2
PAU1080C1
PAU1080C2
COU108
PAU200048
PAU200047
PAU200046
PAU200045
PAU200044
PAU200043
PAU200042
PAU200041
PAU200040
PAU200039
PAU200038
PAU200037
PAU200036
PAU200035
PAU200034
PAU200033
PAU200032
PAU200031
PAU200030
PAU200029
PAU200028
PAU200027
PAU200026
PAU200025
PAU200024
PAU200023
PAU200022
PAU200021
PAU200020
PAU200019
PAU200018
PAU200017
PAU200016
PAU200015
PAU200014
PAU200013
PAU200012
PAU200011
PAU200010
PAU20009
PAU20008
PAU20007
PAU20006
PAU20005
PAU20004
PAU20003
PAU20002
PAU20001
COU200
PAXC20001
PAXC20002
COXC200
Figure 7-2. AVR128DA48 Curiosity Nano Assembly Drawing Top
Figure 7-3. AVR128DA48 Curiosity Nano Assembly Drawing Bottom
AVR128DA48 Curiosity Nano
Appendix
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 31
USB
DEBUGGER
AVR128DA48
SW0
LED0
PS LED
NC
NC
ID
ID
CDC RX
CDCRX
USART1 TXPC0
CDC TX
CDCTX
USART1 RXPC1
DBG1
DBG1
PC6LED0
DBG2
DBG2
PC7SW0
PA0
PA0
USART0 TXPTC XY0
PA1
PA1
USART0 RXPTC XY1
PC2
PC2
TWI0 SDA
PC3
PC3
TWI0 SCL
PA4
PA4
SPI0 MOSIPTC XY4
PA5
PA5
SPI0 MISOPTC XY5
PA6
PA6
SPI0 SCKPTC XY6
PA7
PA7
SPI0 SSPTC XY7
GND
GND
PF4
PF4
USART2 TXPTC XY36
PF5
PF5
USART2 RXPTC XY37
PF2
PF2
PTC XY34
PF3
PF3
PTC XY35
PB0
PB0
PTC XY8
PB1
PB1
PTC XY9
PB2
PB2
PTC XY10
PB3
PB3
PTC XY11
GND
GND
PC0
PC0
USART1 TXCDC RX
PC1
PC1
USART1 RXCDC TX
PC6
PC6
LED0
PC7
PC7
SW0
VBUS
VBUS
VOFF
VOFF
DBG3
DBG3
PF6
DBG0
DBG0
UPDI
GND
GND
VTG
VTG
PD7
PD7
AIN7 PTC XY23
PD6
PD6
AIN6 PTC XY22
PD2
PD2
AIN2 PTC XY18 TCA0 WO2
PD1
PD1
AIN1 PTC XY17 TCA0 WO1
PD0
PD0
AIN0 PTC XY16 TCA0 WO0
PD5
PD5
AIN5 PTC XY21
PD4
PD4
AIN4 PTC XY20
PD3
PD3
AIN3 PTC XY19
GND
GND
PE3
PE3
PTC XY27
PE2
PE2
PTC XY26
PE1
PE1
PTC XY25
PE0
PE0
PTC XY24
PA3
PA3
PTC XY3
PA2
PA2
PTC XY2
PB5
PB5
PTC XY13
PB4
PB4
PTC XY12
GND
GND
PC5
PC5
PC4
PC4
(PF1)
(PF1)
(PTC XY33) XTAL32K2
(PF0)
(PF0)
(PTC XY32) XTAL32K1
DEBUGGER
AVR128DA48
Analog
Debug
I2C
SPI
UART
Peripheral
Port
PWM
Power
Ground
Touch
Shared pin
AVR128DA48
Curiosity Nano
1
AN PWM
RST INT
CS RX
SCK TX
MISO SCL
MOSI SDA
+3.3V +5V
GND GND
2
AN PWM
RST INT
CS RX
SCK TX
MISO SCL
MOSI SDA
+3.3V +5V
GND GND
3
AN PWM
RST INT
CS RX
SCK TX
MISO SCL
MOSI SDA
+3.3V +5V
GND GND
Xplained Pro Extension
EXT1
1 2
19 20
Curiosity Nano Base
for click boards
TM
PD3 PD0
PD7 PD6
PA7 PA1
PA6 PA0
PA5 PC3
PA4 PC2
+3.3V +5V
GND GND
PD4 PD1
PF3 PF2
PE2 PF5
PA6 PF4
PA5 PC3
PA4 PC2
+3.3V +5V
GND GND
PD5 PD2
PE1 PE0
PE3 PA1
PA6 PA0
PA5 PC3
PA4 PC2
+3.3V +5V
GND GND
ID GND
PD4 PD5
PF3 PE1
PD1 PD2
PF2 PE3
PC2 PC3
PF5 PF4
PE2 PA4
PA5 PA6
GND +3.3V
AVR128DA48 Curiosity Nano
Appendix
7.3 Curiosity Nano Base for Click boards
Figure 7-4. AVR128DA48 Curiosity Nano Pinout Mapping
™
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 32
7.4 Disconnecting the On-board Debugger
The on-board debugger and level shifters can be completely disconnected from the AVR128DA48.
The block diagram below shows all connections between the debugger and the AVR128DA48. 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.
To disconnect the debugger, cut the straps shown in Figure 7-6.
Attention: Cutting the GPIO straps to the on-board debugger will disable the virtual serial port,
programming, debugging, and data streaming. Cutting the power supply strap will disconnect the on-board
power supply.
Tip: Any connection that is cut can be reconnected using solder, alternatively, a 0Ω 0402 resistor can be
mounted.
Tip: When the debugger is disconnected, an external debugger can be connected to holes shown in
Figure 7-6. Details about connecting an external debugger are described in 3.6 Connecting External
Debuggers.
AVR128DA48 Curiosity Nano
Appendix
Figure 7-5. On-Board Debugger Connections Block Diagram
USB
VBUS
VBUS
VOFF
Power Supply strap Target Power strap
LDO
LDO
VCC_LEVEL
DBG0
DBG1
DBG2
DBG3
CDC TX
CDC RX
PA04/PA06
PA07
PA08
PA16
PA00
DEBUGGER
PA01
VCC_P3V3
Level-Shift
DIR x 5
CDC RX
CDC TX
VTG
VCC_EDGE
VCC_TARGET
GPIO straps
TARGET
UART RX
UART TX
DBG0
DBG1
© 2020 Microchip Technology Inc.
User Guide
DBG2
DBG3
DS50002971A-page 33
Figure 7-6. On-Board Debugger Connection Cut Straps
GPIO straps (bottom side) Power Supply strap (top side)
AVR128DA48 Curiosity Nano
Appendix
7.5 Getting Started with IAR
IAR Embedded Workbench® for AVR® is a proprietary high-efficiency compiler not based on GCC. Programming and
debugging of AVR128DA48 Curiosity Nano is supported in IAR™ Embedded Workbench for AVR using the Atmel-ICE
interface. Some initial settings must be set up in the project to get the programming and debugging to work.
The following steps will explain how to get your project ready for programming and debugging:
1. Make sure you have opened the project you want to configure. Open the OPTIONS dialog for the project.
2. In the category General Options, select the Target tab. Select the device for the project, or if not listed, the
core of the device, as shown in Figure 7-7.
3. In the category Debugger, select the Setup tab. Select Atmel-ICE as the driver, as shown in Figure 7-8.
4. In the category
optionally, select the UPDI frequency, as shown in Figure 7-9.
Info: If the selection of Debug Port (mentioned in step 4) is grayed out, the interface is preselected, and
the user can skip this configuration step.
Debugger > Atmel-ICE, select the Atmel-ICE 1 tab. Select UPDI as the interface and,
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 34
Figure 7-7. Select Target Device
AVR128DA48 Curiosity Nano
Appendix
Figure 7-8. Select Debugger
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 35
Figure 7-9. Configure Interface
AVR128DA48 Curiosity Nano
Appendix
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 36
AVR128DA48 Curiosity Nano
The Microchip Website
Microchip provides online support via our website at http://www.microchip.com/. This website is used to make files
and information easily available to customers. Some of the content available includes:
• Product Support – Data sheets and errata, application notes and sample programs, design resources, user’s
guides and hardware support documents, latest software releases and archived software
• General Technical Support – Frequently Asked Questions (FAQs), technical support requests, online
discussion groups, Microchip design partner program member listing
• Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of
seminars and events, listings of Microchip sales offices, distributors and factory representatives
Product Change Notification Service
Microchip’s product change notification service helps keep customers current on Microchip products. Subscribers will
receive email notification whenever there are changes, updates, revisions or errata related to a specified product
family or development tool of interest.
To register, go to http://www.microchip.com/pcn and follow the registration instructions.
Customer Support
Users of Microchip products can receive assistance through several channels:
• Distributor or Representative
• Local Sales Office
• Embedded Solutions Engineer (ESE)
• Technical Support
Customers should contact their distributor, representative or ESE for support. Local sales offices are also available to
help customers. A listing of sales offices and locations is included in this document.
Technical support is available through the website at: http://www.microchip.com/support
Microchip Devices Code Protection Feature
Note the following details of the code protection feature on Microchip devices:
• Microchip products meet the specification contained in their particular Microchip Data Sheet.
• Microchip believes that its family of products is one of the most secure families of its kind on the market today,
when used in the intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these
methods, to our knowledge, require using the Microchip products in a manner outside the operating
specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft of
intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code
protection does not mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection
features of our products. Attempts to break Microchip’s code protection feature may be a violation of the Digital
Millennium Copyright Act. If such acts allow unauthorized access to your software or other copyrighted work, you
may have a right to sue for relief under that Act.
Legal Notice
Information contained in this publication regarding device applications and the like is provided only for your
convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 37
AVR128DA48 Curiosity Nano
your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER
EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION,
INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR
FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip
devices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend,
indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such
use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unless
otherwise stated.
Trademarks
The Microchip name and logo, the Microchip logo, Adaptec, AnyRate, AVR, AVR logo, AVR Freaks, BesTime,
BitCloud, chipKIT, chipKIT logo, CryptoMemory, CryptoRF, dsPIC, FlashFlex, flexPWR, HELDO, IGLOO, JukeBlox,
KeeLoq, Kleer, LANCheck, LinkMD, maXStylus, maXTouch, MediaLB, megaAVR, Microsemi, Microsemi logo, MOST,
MOST logo, MPLAB, OptoLyzer, PackeTime, PIC, picoPower, PICSTART, PIC32 logo, PolarFire, Prochip Designer,
QTouch, SAM-BA, SenGenuity, SpyNIC, SST, SST Logo, SuperFlash, Symmetricom, SyncServer, Tachyon,
TempTrackr, TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are registered trademarks of Microchip Technology
Incorporated in the U.S.A. and other countries.
APT, ClockWorks, The Embedded Control Solutions Company, EtherSynch, FlashTec, Hyper Speed Control,
HyperLight Load, IntelliMOS, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC, ProASIC Plus,
ProASIC Plus logo, Quiet-Wire, SmartFusion, SyncWorld, Temux, TimeCesium, TimeHub, TimePictra, TimeProvider,
Vite, WinPath, and ZL are registered trademarks of Microchip Technology Incorporated in the U.S.A.
Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, BlueSky, BodyCom,
CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController, dsPICDEM,
dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, EtherGREEN, In-Circuit Serial Programming, ICSP,
INICnet, Inter-Chip Connectivity, JitterBlocker, KleerNet, KleerNet logo, memBrain, Mindi, MiWi, MPASM, MPF,
MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM,
PICDEM.net, PICkit, PICtail, PowerSmart, PureSilicon, QMatrix, REAL ICE, Ripple Blocker, SAM-ICE, Serial Quad
I/O, SMART-I.S., SQI, SuperSwitcher, SuperSwitcher II, Total Endurance, TSHARC, USBCheck, VariSense,
ViewSpan, WiperLock, Wireless DNA, and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A.
and other countries.
SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.
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.
All other trademarks mentioned herein are property of their respective companies.
©
2020, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved.
ISBN: 978-1-5224-5760-2
Quality Management System
For information regarding Microchip’s Quality Management Systems, please visit http://www.microchip.com/quality.
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 38
Worldwide Sales and Service
AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE
Corporate Office
2355 West Chandler Blvd.
Chandler, AZ 85224-6199
Tel: 480-792-7200
Fax: 480-792-7277
Technical Support:
http://www.microchip.com/support
Web Address:
http://www.microchip.com
Atlanta
Duluth, GA
Tel: 678-957-9614
Fax: 678-957-1455
Austin, TX
Tel: 512-257-3370
Boston
Westborough, MA
Tel: 774-760-0087
Fax: 774-760-0088
Chicago
Itasca, IL
Tel: 630-285-0071
Fax: 630-285-0075
Dallas
Addison, TX
Tel: 972-818-7423
Fax: 972-818-2924
Detroit
Novi, MI
Tel: 248-848-4000
Houston, TX
Tel: 281-894-5983
Indianapolis
Noblesville, IN
Tel: 317-773-8323
Fax: 317-773-5453
Tel: 317-536-2380
Los Angeles
Mission Viejo, CA
Tel: 949-462-9523
Fax: 949-462-9608
Tel: 951-273-7800
Raleigh, NC
Tel: 919-844-7510
New York, NY
Tel: 631-435-6000
San Jose, CA
Tel: 408-735-9110
Tel: 408-436-4270
Canada - Toronto
Tel: 905-695-1980
Fax: 905-695-2078
Australia - Sydney
Tel: 61-2-9868-6733
China - Beijing
Tel: 86-10-8569-7000
China - Chengdu
Tel: 86-28-8665-5511
China - Chongqing
Tel: 86-23-8980-9588
China - Dongguan
Tel: 86-769-8702-9880
China - Guangzhou
Tel: 86-20-8755-8029
China - Hangzhou
Tel: 86-571-8792-8115
China - Hong Kong SAR
Tel: 852-2943-5100
China - Nanjing
Tel: 86-25-8473-2460
China - Qingdao
Tel: 86-532-8502-7355
China - Shanghai
Tel: 86-21-3326-8000
China - Shenyang
Tel: 86-24-2334-2829
China - Shenzhen
Tel: 86-755-8864-2200
China - Suzhou
Tel: 86-186-6233-1526
China - Wuhan
Tel: 86-27-5980-5300
China - Xian
Tel: 86-29-8833-7252
China - Xiamen
Tel: 86-592-2388138
China - Zhuhai
Tel: 86-756-3210040
India - Bangalore
Tel: 91-80-3090-4444
India - New Delhi
Tel: 91-11-4160-8631
India - Pune
Tel: 91-20-4121-0141
Japan - Osaka
Tel: 81-6-6152-7160
Japan - Tokyo
Tel: 81-3-6880- 3770
Korea - Daegu
Tel: 82-53-744-4301
Korea - Seoul
Tel: 82-2-554-7200
Malaysia - Kuala Lumpur
Tel: 60-3-7651-7906
Malaysia - Penang
Tel: 60-4-227-8870
Philippines - Manila
Tel: 63-2-634-9065
Singapore
Tel: 65-6334-8870
Taiwan - Hsin Chu
Tel: 886-3-577-8366
Taiwan - Kaohsiung
Tel: 886-7-213-7830
Taiwan - Taipei
Tel: 886-2-2508-8600
Thailand - Bangkok
Tel: 66-2-694-1351
Vietnam - Ho Chi Minh
Tel: 84-28-5448-2100
Austria - Wels
Tel: 43-7242-2244-39
Fax: 43-7242-2244-393
Denmark - Copenhagen
Tel: 45-4485-5910
Fax: 45-4485-2829
Finland - Espoo
Tel: 358-9-4520-820
France - Paris
Tel: 33-1-69-53-63-20
Fax: 33-1-69-30-90-79
Germany - Garching
Tel: 49-8931-9700
Germany - Haan
Tel: 49-2129-3766400
Germany - Heilbronn
Tel: 49-7131-72400
Germany - Karlsruhe
Tel: 49-721-625370
Germany - Munich
Tel: 49-89-627-144-0
Fax: 49-89-627-144-44
Germany - Rosenheim
Tel: 49-8031-354-560
Israel - Ra’anana
Tel: 972-9-744-7705
Italy - Milan
Tel: 39-0331-742611
Fax: 39-0331-466781
Italy - Padova
Tel: 39-049-7625286
Netherlands - Drunen
Tel: 31-416-690399
Fax: 31-416-690340
Norway - Trondheim
Tel: 47-72884388
Poland - Warsaw
Tel: 48-22-3325737
Romania - Bucharest
Tel: 40-21-407-87-50
Spain - Madrid
Tel: 34-91-708-08-90
Fax: 34-91-708-08-91
Sweden - Gothenberg
Tel: 46-31-704-60-40
Sweden - Stockholm
Tel: 46-8-5090-4654
UK - Wokingham
Tel: 44-118-921-5800
Fax: 44-118-921-5820
© 2020 Microchip Technology Inc.
User Guide
DS50002971A-page 39
Loading...