Microchip Technology AVR128DB48 Curiosity Nano Installation manual

AVR128DB48 Curiosity Nano
AVR128DB48 Curiosity Nano Hardware User Guide
Preface
The AVR128DB48 Curiosity Nano Evaluation Kit is a hardware platform to evaluate microcontrollers in the AVR® DB
Family. This board has the AVR128DB48 microcontroller (MCU) mounted.
Supported by both MPLAB® X IDE and Atmel Studio 7, the board provides easy access to the features of the
AVR128DB48 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 AVR128DB48.
•MPLAB® X IDE and Atmel Studio - Software to discover, configure, develop, program, and debug Microchip
microcontrollers.
•Code examples on GitHub - Get started with code examples.
•AVR128DB48 website - Find documentation, data sheets, sample, and purchase microcontrollers.
•AVR128DB48 Curiosity Nano website - Kit information, latest user guide, and design documentation.
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 1

Table of Contents
Preface........................................................................................................................................................... 1
1. Introduction............................................................................................................................................. 4
1.1. Features....................................................................................................................................... 4
1.2. Board Overview............................................................................................................................4
2. Getting Started........................................................................................................................................ 5
2.1. Quick Start....................................................................................................................................5
2.1.1. Driver Installation...........................................................................................................5
2.1.2. Kit Window.....................................................................................................................5
2.1.3. MPLAB® X IDE Device Family Packs............................................................................5
2.1.4. Atmel Studio 7 Device Family Pack...............................................................................6
2.2. Design Documentation and Relevant Links................................................................................. 6
3. Preprogrammed Application....................................................................................................................7
4. Curiosity Nano.........................................................................................................................................8
4.1. On-Board Debugger Overview..................................................................................................... 8
4.1.1. Debugger.......................................................................................................................8
4.1.2. Virtual Serial Port (CDC)................................................................................................9
4.1.2.1. Overview..................................................................................................... 9
4.1.2.2. Operating System Support.......................................................................... 9
4.1.2.3. Limitations................................................................................................. 10
4.1.2.4. Signaling....................................................................................................10
4.1.2.5. Advanced Use........................................................................................... 11
4.1.3. Mass Storage Device...................................................................................................11
4.1.3.1. Mass Storage Device Implementation.......................................................12
4.1.3.2. Limitations of Drag-and-Drop Programming..............................................12
4.1.3.3. Special Commands................................................................................... 12
4.1.4. Data Gateway Interface (DGI)..................................................................................... 13
4.1.4.1. Debug GPIO..............................................................................................13
4.1.4.2. Timestamping............................................................................................14
4.2. Curiosity Nano Standard Pinout................................................................................................. 14
4.3. Power Supply............................................................................................................................. 15
4.3.1. Target Regulator.......................................................................................................... 15
4.3.2. External Supply............................................................................................................17
4.3.3. VBUS Output Pin.........................................................................................................17
4.3.4. Power Supply Exceptions............................................................................................18
4.4. Low-Power Measurement.......................................................................................................... 19
4.5. Programming External Microcontrollers..................................................................................... 20
4.5.1. Supported Devices...................................................................................................... 20
4.5.2. Software Configuration................................................................................................ 20
4.5.3. Hardware Modifications............................................................................................... 21
4.5.4. Connecting to External Microcontrollers...................................................................... 22
4.6. Connecting External Debuggers................................................................................................ 23
5. Hardware User Guide........................................................................................................................... 26
AVR128DB48 Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 2

5.1. Connectors.................................................................................................................................26
5.1.1. AVR128DB48 Curiosity Nano Pinout...........................................................................26
5.1.2. Using Pin Headers.......................................................................................................26
5.1.3. Multi-Voltage I/O.......................................................................................................... 27
5.1.4. Operational Amplifiers................................................................................................. 28
5.2. Peripherals................................................................................................................................. 29
5.2.1. LED..............................................................................................................................29
5.2.2. Mechanical Switch.......................................................................................................29
5.2.3. 32.768 kHz Crystal...................................................................................................... 29
5.2.4. 16.00 MHz Crystal....................................................................................................... 30
5.2.5. On-Board Debugger Implementation...........................................................................31
5.2.5.1. On-Board Debugger Connections............................................................. 31
6. Hardware Revision History and Known Issues..................................................................................... 32
6.1. Identifying Product ID and Revision........................................................................................... 32
6.2. Revision 3...................................................................................................................................32
6.3. Revision 2...................................................................................................................................32
7. Document Revision History...................................................................................................................33
8. Appendix............................................................................................................................................... 34
8.1. Schematic...................................................................................................................................34
8.2. Assembly Drawing......................................................................................................................36
8.3. Curiosity Nano Base for Click boards™...................................................................................... 37
8.4. Disconnecting the On-board Debugger......................................................................................38
8.5. Getting Started with IAR.............................................................................................................39
The Microchip Website.................................................................................................................................42
Product Change Notification Service............................................................................................................42
Customer Support........................................................................................................................................ 42
Microchip Devices Code Protection Feature................................................................................................ 42
Legal Notice................................................................................................................................................. 43
Trademarks.................................................................................................................................................. 43
Quality Management System....................................................................................................................... 44
Worldwide Sales and Service.......................................................................................................................45
AVR128DB48 Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 3

1. Introduction
1.1 Features
• AVR128DB48 Microcontroller
• One Yellow User LED
• One Mechanical User Switch
• One 32.768 kHz Crystal
• One 16.00 MHz Crystal
• On-Board Debugger:
– Board identification in Microchip MPLAB® X IDE and Atmel Studio 7
– 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)
1.2 Board Overview
The Microchip AVR128DB48 Curiosity Nano Evaluation Kit is a hardware platform to evaluate the AVR128DB48
microcontroller.
Figure 1-1. AVR128DB48 Curiosity Nano Board Overview
User
Switch
User LED
(LED0)
AVR128DB48
MCU
32.768 kHz
Crystal
16.00 MHz
Crystal
Debugger
Power/
Status
Micro-USB
Connector
VDDIO2 MVIO
Pins
AVR128DB48 Curiosity Nano
Introduction
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 4

2. Getting Started
2.1 Quick Start
Steps to start exploring the AVR128DB48 Curiosity Nano board:
1. Download Microchip MPLAB® X IDE and MPLAB® XC C Compiler, or download Atmel Studio 7.
2. Launch MPLAB® X IDE or Atmel Studio 7.
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.
Info:
• MPLAB® X IDE supports XC C compilers and the AVR® and Arm® Toolchains (GCC Compilers)
• Microchip’s XC8 C Compiler supports all 8-bit PIC® and AVR® microcontrollers
• Included in the Atmel Studio 7 download are the AVR® and Arm® Toolchains (GCC Compilers)
2.1.1 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 both MPLAB® X IDE and Atmel
Studio 7.
2.1.2 Kit Window
Once the board is powered, the green status LED will be lit, and both MPLAB® X IDE and Atmel Studio 7 will auto-
detect which boards are connected. The Kit Window in MPLAB® X IDE and Atmel Studio 7 will present relevant
information like data sheets and board documentation. The AVR128DB48 device on the AVR128DB48 Curiosity
Nano board is programmed and debugged by the on-board debugger and, therefore, no external programmer or
debugger tool is required.
Tip: The Kit Window can be opened in MPLAB® X IDE through the menu bar Window > Kit Window.
2.1.3 MPLAB® X IDE Device Family Packs
Microchip MPLAB® X IDE requires specific information to support devices and tools. This information is contained in
versioned packs. For the AVR128DB48 Curiosity Nano, board MPLAB® X version 5.40 with device family pack “AVR-
Dx_DFP” version 1.2 and tool pack “nEDBG_TP” version 1.1 or newer are required. For more information on packs
and how to upgrade them, refer to the MPLAB® X IDE User’s guide - Work with Device Packs.
Tip: The latest device family packs are available through Tools > Packs in MPLAB® X IDE or online at
Microchip MPLAB® X Packs Repository.
AVR128DB48 Curiosity Nano
Getting Started
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 5

2.1.4 Atmel Studio 7 Device Family Pack
Atmel Studio 7 requires specific information to support devices. This information is contained in versioned packs. For
the AVR128DB48 Curiosity Nano board, Atmel Studio 7 version 7.0.2397 with device family pack “AVR-Dx_DFP”
version 1.1 or newer are required. For more information on packs and how to upgrade them, refer to the Atmel Studio
7 User Guide - Device Pack Manager.
Tip: The latest device family packs are available through Tools > Device Pack Manager in Atmel Studio 7
or online at Atmel Studio Packs Repository.
2.2 Design Documentation and Relevant Links
The following list contains links to the most relevant documents and software for the AVR128DB48 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® XC Compilers - MPLAB® XC8 C Compiler is available as a free, unrestricted-use download.
Microchips MPLAB® XC8 C Compiler is a comprehensive solution for your project’s software development on
Windows®, macOS® or Linux®. MPLAB® XC8 supports all 8-bit PIC® and AVR® microcontrollers (MCUs).
•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.
•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.
•AVR128DB48 Curiosity Nano website - Kit information, latest user guide, and design documentation.
•AVR128DB48 Curiosity Nano on Microchip Direct - Purchase this kit on Microchip Direct.
AVR128DB48 Curiosity Nano
Getting Started
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 6

3. Preprogrammed Application
The AVR128DB48 mounted on the Curiosity Nano Evaluation Kit is preprogrammed with an application ready to
utilize the integrated operational amplifiers.
To get started with the application, you can find the user guide, code, and hex files for this application available online
on GitHub:
•MPLAB X® IDE
•Atmel Studio 7
AVR128DB48 Curiosity Nano
Preprogrammed Application
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 7

4. 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 MPLAB® X IDE and Atmel Studio 7. 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).
4.1 On-Board Debugger Overview
AVR128DB48 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 AVR128DB48 in both MPLAB® X IDE and Atmel Studio 7
• A mass storage device that allows drag-and-drop programming of the AVR128DB48
• A virtual serial port (CDC) that is connected to a Universal Asynchronous Receiver/Transmitter (UART) on the
AVR128DB48, 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 AVR128DB48 Curiosity Nano Board.
The table below shows how the LED is controlled in different operation modes.
Table 4-1. On-Board Debugger LED Control
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 Success: The LED blinks slowly for 2 sec
Failure: The LED blinks rapidly for 2 sec
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.
This can occur if the board is externally powered.
Info: Slow blinking is approximately 1 Hz, and rapid blinking is approximately 5 Hz.
4.1.1 Debugger
The on-board debugger on the AVR128DB48 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
AVR128DB48 using both MPLAB® X IDE and Atmel Studio 7, as well as some third-party IDEs.
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 8

Remember: Keep the debugger’s firmware up-to-date. Firmware upgrades are done automatically when
using MPLAB® X IDE or Atmel Studio 7.
4.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.
4.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 4-1. CDC Connection
Target MCU
UART TX
UART RX
Debugger
USB
CDC RX
CDC TX
PC
Terminal
Software
Target
Receive
Target
Send
Terminal
Receive
Terminal
Send
Info: As shown in Figure 4-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.
4.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 both MPLAB® X IDE and Atmel Studio 7.
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#.
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 9

Info: For all operating systems: Be sure to use a terminal emulator that supports DTR signaling. See
4.1.2.4 Signaling.
4.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.
4.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 DTR in debugger firmware version 1.20 or earlier has the following behavior:
• Debugger UART receiver is disabled, so no further data will be transferred to the host computer
• Debugger UART transmitter will continue to send data that is queued for sending, but no new data is accepted
from the host computer
• Level shifters (if available) are not disabled, so the debugger CDC TX line remains driven
Deasserting DTR in debugger firmware version 1.21 or later has the following behavior:
• Debugger UART receiver is disabled, so no further data will be transferred to the host computer
• Debugger UART transmitter will continue to send data that is queued for sending, but no new data is accepted
from the host computer
• Once the ongoing transmission is complete, level shifters (if available) are disabled, so the debugger CDC TX
line will become high-impedance
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.
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 10

4.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=
Debugger firmware version 1.20 or earlier has the following limitations:
• 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
Debugger firmware version 1.21 and later has the following limitations/features:
• The maximum message length may vary depending on the MSC/SCSI layer timeouts on the host computer
and/or operating system. A single SCSI frame of 512 bytes (498 characters of payload) is guaranteed, and files
of up to 4 KB will work on most systems. The transfer will complete on the first NULL character encountered in
the file.
• The baud rate used is always 9600 bps for the default command:
CMD:SEND_UART=
The CDC Override Mode should not be used simultaneously with data transfer over CDC/terminal. If a CDC
terminal session is active at the time a file is received via CDC Override Mode, it will be suspended for the
duration of the operation and resumed once complete.
• Additional commands are supported with explicit baud rates:
CMD:SEND_9600=
CMD:SEND_115200=
CMD:SEND_460800=
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, as 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.
4.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
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 11

• Write access for programming Intel® HEX formatted files into the target device’s memory
• Write access for simple text files for utility purposes
4.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
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.
4.1.3.2 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
MPLAB® X IDE or Atmel Studio 7.
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
is 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 MPLAB® X IDE or
Atmel Studio 7, which will automatically clear the CRC fuses after erasing.
4.1.3.3 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.
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 12

Table 4-2. Special File Commands
Command Content Description
CMD:ERASE Executes a chip erase of the target
CMD:SEND_UART= Sends a string of characters to the CDC UART. See “CDC
Override Mode”.
CMD:SEND_9600=
CMD:SEND_115200=
CMD:SEND_460800=
Sends a string of characters to the CDC UART at the baud rate
specified. Note that only the baud rates explicitly specified here
are supported! See “CDC Override Mode” (Debugger firmware
v1.21 or newer.)
CMD:RESET 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.)
CMD:POWERTOGGLE 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.)
CMD:0V 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.)
CMD:1V8 Sets the target voltage to 1.8V. If external power is provided,
this has no effect. (Debugger firmware v1.21 or newer.)
CMD:3V3 Sets the target voltage to 3.3V. If external power is provided,
this has no effect. (Debugger firmware v1.16 or newer.)
CMD:5V0 Sets the target voltage to 5.0V. If external power is provided,
this has no effect. (Debugger firmware v1.16 or newer.)
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.
4.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 MPLAB® X IDE or Atmel Studio 7.
Although DGI encompasses several physical data interfaces, the AVR128DB48 Curiosity Nano implementation
includes logic analyzer channels:
• Two debug GPIO channels (also known as DGI GPIO)
4.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.
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 13

Figure 4-2. Monitoring Debug GPIO with MPLAB® Data Visualizer
Debug GPIO channels are timestamped, so the resolution of DGI GPIO events is determined by the resolution of the
DGI timestamp module.
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.
4.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.
4.2 Curiosity Nano Standard Pinout
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 4-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
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 14

...........continued
Debugger Signal Target MCU Description
VBUS — VBUS voltage for external use
VOFF — Voltage Off input. Disables the target regulator and
target voltage when pulled low.
VTG — Target voltage
GND — Common ground
Figure 4-3. Curiosity Nano Standard Pinout
USB
DEBUGGER
PS LED
NC
ID
CDC RX
CDC TX
DBG1
DBG2
VBUS
VOFF
DBG3
DBG0
GND
VTG
CURIOSITY NANO
4.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 AVR128DB48 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 AVR128DB48
Curiosity Nano.
Figure 4-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
4.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
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 15

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 AVR128DB48
microcontroller. The voltage limits configured in the on-board debugger on AVR128DB48 Curiosity Nano are 1.8–
5.5V.
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 7 device programming dialog. Any change to
the target voltage is persistent, even after 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 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 supports a set of common target voltages. See section 4.1.3.3 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.
Figure 4-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.
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 16

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 on-
board debugger detects the new situation and turns the target voltage regulator back on.
4.3.2 External Supply
AVR128DB48 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.
WARNING
Applying an external voltage to the VTG pin without shorting VOFF to GND may cause permanent damage
to the board.
WARNING
Do not apply any voltage to the VOFF pin. Let the pin float to enable the power supply.
WARNING
Absolute maximum external voltage is 5.5V for the on-board level shifters, and the standard operating
condition of the AVR128DB48 is 1.8–5.5V. Applying a higher voltage may cause permanent damage to the
board.
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’s 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 AVR128DB48 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.
4.3.3 VBUS Output Pin
AVR128DB48 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.
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 17

Figure 4-6. VBUS Output Voltage vs. Current
4.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 4.4-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.
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 differs 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 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.
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 18

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.
4.4 Low-Power Measurement
Power to the AVR128DB48 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 AVR128DB48 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 AVR128DB48.
Figure 4-7. Target Power Strap
Target Power strap (top side)
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 19

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 in tri-state to prevent leakage. All I/Os connected to the on-board
debugger are listed in 5.2.5.1 On-Board Debugger Connections. To prevent any leakage to the on-board
level shifters, they can be disconnected completely, as described in 8.4 Disconnecting the On-board
Debugger.
4.5 Programming External Microcontrollers
The on-board debugger on AVR128DB48 Curiosity Nano can be used to program and debug microcontrollers on
external hardware.
4.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 on-
board debugger with Atmel Studio.
AVR128DB48 Curiosity Nano can program and debug external AVR128DB48 microcontrollers with MPLAB X IDE.
4.5.2 Software Configuration
No software configuration is required to program and debug the same device that is mounted on the board.
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.
AVR128DB48 Curiosity Nano
Curiosity Nano
© 2020 Microchip Technology Inc. User Guide DS50003037A-page 20