Attiny1607 Curiosity Nano Hardware User Guide

ATtiny1607 Curiosity Nano ATtiny1607 Curiosity Nano Hardware User Guide

Preface

The ATtiny1607 Curiosity Nano Evaluation Kit is a hardware platform to evaluate the ATtiny1607 microcontroller (MCU). Supported by Atmel Studio/Microchip MPLAB® X Integrated Development Environment (IDE), the kit provides easy access to the features of the ATtiny1607 to explore how to integrate the device into a custom design. The Curiosity Nano series of evaluation kits include an on-board debugger. No external tools are necessary to program and debug the ATtiny1607.

Table of Contents

Preface...... 1

1. Introduction...... 3 1.1. Features...... 3 1.2. Kit Overview...... 3

2. Getting Started...... 4 2.1. Curiosity Nano Quick Start...... 4 2.2. Design Documentation and Relevant Links...... 4

3. Curiosity Nano...... 5 3.1. On-board Debugger...... 5 3.2. Curiosity Nano Standard Pinout...... 8 3.3. Power Supply...... 9 3.4. Target Current Measurement...... 11 3.5. Disconnecting the On-Board Debugger...... 12

4. Hardware User Guide...... 14 4.1. Connectors...... 14 4.2. Peripherals...... 15

5. Hardware Revision History and Known Issues...... 17 5.1. Identifying Product ID and Revision...... 17 5.2. Chip Erase at Low Voltage...... 17 5.3. Revision 2...... 17 5.4. Revision 1...... 17

6. Document Revision History...... 19

7. Appendix...... 20 7.1. Schematic...... 20 7.2. Assembly Drawing...... 22 7.3. Curiosity Nano Base for Click boards™...... 23 7.4. Connecting External Debuggers...... 24 7.5. Getting Started with IAR...... 25

The Microchip Website...... 28

Product Change Notification Service...... 28

Customer Support...... 28

Microchip Devices Code Protection Feature...... 28

Legal Notice...... 28

Trademarks...... 29

Quality Management System...... 29

Worldwide Sales and Service...... 30

1. Introduction

1.1 Features • ATtiny1607-MNR Microcontroller • One Yellow User LED • One Mechanical User Switch • On-Board Debugger: – Board identification in Atmel Studio/Microchip MPLAB® X IDE – One green power and status LED – Programming and debugging – Virtual COM port (CDC) – Two logic analyzer 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 Kit Overview The Microchip ATtiny1607 Curiosity Nano Evaluation Kit is a hardware platform to evaluate the ATtiny1607 microcontroller. Figure 1-1. ATtiny1607 Curiosity Nano Evaluation Kit Overview

2. Getting Started

2.1 Curiosity Nano Quick Start Steps to start exploring the Curiosity Nano platform: 1. Download Atmel Studio/Microchip MPLAB® X IDE. 2. Launch Atmel Studio/Microchip MPLAB® X IDE. 3. Optional: Use 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 kit. When the Curiosity Nano kit 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 kit are included with Atmel Studio/ Microchip MPLAB® X IDE. Once the Curiosity Nano board is powered, the green status LED will be lit and Atmel Studio/Microchip MPLAB® X IDE will auto-detect which Curiosity Nano board is connected. Atmel Studio/Microchip MPLAB® X IDE will present relevant information like data sheets and kit documentation. The ATtiny1607 device is programmed and debugged by the on-board debugger and therefore no external programmer or debugger tool is required.

2.2 Design Documentation and Relevant Links The following list contains links to the most relevant documents and software for the ATtiny1607 Curiosity Nano:

• 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 8-bit AVR. There is a 30-day evaluation version as well as a 4 KB code-size-limited kick-start version available from their website. • Atmel START - Atmel START is an online tool that 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. • Data Visualizer - Data Visualizer is a program used for processing and visualizing data. The Data Visualizer can receive data from various sources such as the EDBG Data Gateway Interface found on Curiosity Nano and Xplained Pro boards and COM Ports. • ATtiny1607 Curiosity Nano website - Kit information, latest user guide and design documentation. • ATtiny1607 Curiosity Nano on Microchip Direct - Purchase this kit on Microchip Direct.

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, and relevant user guides, application notes, data sheets, and example code are easy to find. The on-board debugger features a Virtual COM port (CDC) for serial communication to a host PC, and a Data Gateway Interface (DGI) GPIO logic analyzer pin.

3.1 On-board Debugger The ATtiny1607 Curiosity Nano contains an on-board debugger for programming and debugging. The on-board debugger is a composite USB device of several interfaces: A debugger, a mass storage device, a data gateway, and a Virtual COM port (CDC). Together with Atmel Studio/Microchip MPLAB® X IDE, the on-board debugger can program and debug the ATtiny1607. A Data Gateway Interface (DGI) is available for use with the logic analyzer channels for code instrumentation to visualize the program flow. DGI GPIOs can be graphed using the Data Visualizer. The Virtual COM port (CDC) is connected to a Universal Asynchronous Receiver/Transmitter (UART) on the ATtiny1607 and provides an easy way to communicate with the target application through terminal software. The on-board debugger controls a Power and Status LED (marked PS) on the ATtiny1607 Curiosity Nano. The table below shows how the LED is controlled in different operation modes. Table 3-1. On-Board Debugger LED Control

Operation Mode Status LED Boot Loader mode LED blink at 1 Hz during power-up. Power-up LED is ON. Normal operation LED is ON. Programming Activity indicator: The LED flashes slowly during programming/debugging. Fault The LED flashes fast if a power fault is detected. Sleep/Off LED is OFF. The on-board debugger is either in Sleep mode or powered down. This can occur if the kit is externally powered.

3.1.1 Virtual COM Port (CDC) The Virtual COM port (CDC) is a general purpose serial bridge between a host PC and a target device. 3.1.1.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 COM port. The CDC can be used to stream arbitrary data in both directions between the host and the target: All characters sent from the host will be sent through a UART on the CDC TX pin, and UART characters sent into the CDC RX pin will be sent back to the host through the Virtual COM port. 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. On Linux machines, the CDC will enumerate and appear as /dev/ttyACM#. 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#.

Info: On older Windows systems, a USB driver is required for CDC. This driver is included in MPLAB X IDE and Atmel Studio installations.

3.1.1.2 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 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.1.3 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. This is a virtual control signal implemented on the USB interface, but not in hardware in the on-board debugger. Asserting DTR from the host will indicate to the on- board debugger that a CDC session is active, will 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.

Remember: Set up your terminal emulator to assert the DTR signal. Without it, the on-board debugger will not send or receive any data through its UART.

Tip: The on-board debugger will not drive the CDC TX pin until the CDC interface is enabled and data is being sent from the host to the target. In addition there are no external pull-up resistors on the CDC TX line. To avoid any glitches resulting in unpredictable behavior like framing errors etc. the target device should enable the internal pull-up on the CDC TX line.

3.1.1.4 Advanced Use

CDC Override Mode In normal operation, the on-board debugger is a true UART bridge between the host and the device. However, under certain use cases, the on-board debugger can override the basic operating mode and use the CDC pins for other purposes. Dropping a text file (with extension .txt) into the on-board debugger’s mass storage drive can be used to send characters out of the CDC TX pin. 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.

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 CDC TX pin. Transferring a small amount of data per frame can be inefficient, particularly at low baud rates, since the on-board debugger buffers frames and not bytes. A maximum of 4 x 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. When receiving data from the target, 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 8 x 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.2 Mass Storage Disk A simple way to program the target device is through drag and drop with .hex files. 3.1.2.1 Mass Storage Device The on-board debugger implements a highly optimized variant of the FAT12 file system that has a number of limitations, partly due to the nature of FAT12 itself and optimizations made to fulfill its purpose for its embedded application. The CURIOSITY drive 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. The on-board debugger enumerates as a Curiosity Nano USB device that can be found in the disk drives section of the Windows 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 a .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 kit 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 kit firmware, name, serial number, and device • 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 not reflect the correct status.

3.1.2.2 Fuse Bytes

Fuse Bytes (AVR® MCU Targets) The debugger does not mask any fuse bits or combinations when writing fuses. It is not possible to disable Unified Program and Debug Interface (UPDI) by fuse setting on devices with a dedicated UPDI pin. For devices with a shared/configurable UPDI pin, be sure not to select an alternate pin function for UPDI either by fuse setting in Programming mode or by using the I/O view or memory views to modify the memory-mapped fuse values. Disabling UPDI will render the debugger unable to contact the target device – an external programmer capable of 12V UPDI activation will be required.

3.2 Curiosity Nano Standard Pinout The 12 edge connections closest to the USB connector on Curiosity Nano kits 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-2. Curiosity Nano Standard Pinout

Debugger Signal UPDI Target 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 clock line/DGI GPIO DBG2 GPIO0 DGI GPIO DBG3 RESET Reset line NC — No connect VBUS — VBUS voltage for external use VOFF — Voltage Off input VTG — Target voltage GND — Common ground

Figure 3-1. Curiosity Nano Standard Pinout

USB VBUS

NC PS LED NC VBUS VOFF ID ID VOFF CDCRX DBG3

CDC RX DEBUGGER DBG3 CDCTX DBG0 CDC TX DBG0 DBG1 GND DBG1 GND DBG2 VTG DBG2 CURIOSITY NANO VTG

3.3 Power Supply The kit 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 ATtiny1607 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 ATtiny1607 Curiosity Nano. Figure 3-2. Power Supply Block Diagram VTG

Target VREG VLVL Power Target Supply Power Regulator strap strap

Measure On/Off VUSB On/Off Target USB Adjust MCU

Power consumer DEBUGGER P3V3 I/O Level I/O GPIO I/O DEBUGGER PTC Regulator shifter straps Power converter Fuse Power protection Power source Cut strap VBUS #VOFF ID system

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 kit 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 ATtiny1607 microcontroller. The voltage limits configured in the on-board debugger on ATtiny1607 Curiosity Nano are 1.8-5.1V.

Info: The target voltage is set to 3.3V in production. 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 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 3-3. Target Regulator Safe Operation Area

3.3.2 External Supply ATtiny1607 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.

Applying an external voltage to the VTG pin without shorting VOFF to GND may cause permanent damage WARNING to the kit.

Absolute maximum external voltage is 5.5V for the on-board level shifters, and the standard operating WARNING condition of the ATtiny1607 is 1.8-5.5V. Applying a higher voltage may cause permanent damage to the kit.

Programming, debugging, and data streaming are 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.

3.3.3 VBUS Output Pin ATtiny1607 Curiosity Nano has a VBUS output pin which 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-4. VBUS Output Voltage vs. Current

3.4 Target Current Measurement Power to the ATtiny1607 is connected from the on-board power supply and VTG pin through a 100-mil pin header cut Target Power strap marked with “POWER” in silkscreen (J101). To measure the power consumption of the ATtiny1607 and other peripherals connected to the board, cut the Target Power strap and connect an ammeter over the strap. Figure 3-5. Target Power Strap

Target Power strap (top side)

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 not needed anymore, 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 10 µA can be drawn from the target power net, and an additional 2 µA can be drawn from each I/O pin connected to a level shifter for a total of 20 µA. Disconnect the on-board debugger and level shifters as described in Section 3.5 Disconnecting the On-Board Debugger and keep any I/O pin connected to a level shifter in tri-state to prevent leakage.

3.5 Disconnecting the On-Board Debugger The block diagram below shows all connections between the debugger and the ATtiny1607 microcontroller. The rounded boxes represent connections to the board edge on ATtiny1607 Curiosity Nano. The signal names shown in Figure 3-1 are printed in silkscreen on the bottom side of the board. Figure 3-6. On-Board Debugger Connections to the ATtiny1607 VBUS VOFF VTG

VBUS Power Supply strap Target Power strap USB LDO VCC_EDGE

LDO VCC_TARGET

VCC_P3V3 VCC_LEVEL

GPIO straps PA04/PA06 DBG0 PA07 DBG1 PA08 DBG2 PA16 Level-Shift DBG3 TARGET PA00 CDC TX

DEBUGGER PA01 CDC RX DIR x 5

CDC RX DBG0 CDC TX DBG1 DBG2 DBG3 By cutting the GPIO straps with a sharp tool, as shown in Figure 3-7, all I/Os connected between the debugger and the ATtiny1607 are completely disconnected. To completely disconnect the target regulator and level shifter power from the target, cut the Power Supply strap (J100) as shown in Figure 3-7.

Info: Cutting the connections to the debugger will disable programming, debugging, data streaming, and the target power supply. The signals will also be disconnected from the board edge next to the on-board debugger section.

Tip: Solder in 0Ω resistors across the footprints or short-circuit them with tin solder to reconnect any cut signals.

Figure 3-7. Kit Modifications

GPIO straps (bottom side) Power Supply strap (top side)

4. Hardware User Guide

4.1 Connectors

4.1.1 ATtiny1607 Curiosity Nano Pinout All the ATtiny1607 I/O pins are accessible at the edge connectors on the board. The image below shows the kit pinout. Figure 4-1. ATtiny1607 Curiosity Nano Pinout

Analog Peripheral Debug Port I2C PWM SPI Power UART Ground USB Shared pinout VBUS

NC PS LED NC VBUS VOFF ID ID VOFF CDC DBG3

PB2 CDC RX RX DEBUGGER DBG3 CDC DBG0

PB3 CDC TX TX DBG0 PA0 UPDI DBG1 GND PB7LED0 DBG1 GND DBG2 ATtiny1607 VTG PC4SW0 DBG2 CURIOSITY NANO VTG PA1 TX0 PA1 PB6 PB6 PA2 RX0 PA2 PB5 PB5 AIN8 PB1 PB4 SDA PB1 ATtiny1607 PB4 AIN9 TCA0 WO1 PA3 SCL PB0 PB0 PA3 AIN3 TCA0 WO3 PA4 MOSI PC2 PC2 PA4 AIN4 TCA0 WO4 PA5 MISO PC1 PC1 PA5 AIN5 PA6 SCK PC0 PC0 PA6 AIN6 PA7 SS PC3 PC3 PA7 AIN7 GND GND GND GND (TX0) PB2 PB2 LED0 PC5 PC5 PB3 PC4 (RX0) PB3 SW0 PC4 SW0

4.1.2 Using Pin Headers The edge connector footprint on ATtiny1607 Curiosity Nano has a staggered design where each of the holes is shifted 8 mil (~0.2 mm) off center. The hole shift allows the use of regular 100-mil pin headers on the kit 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.

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 all the way in.

Tip: For applications where the pin headers will be used permanently, it is still recommended to solder them in place.

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 ATtiny1607 Curiosity Nano kit 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

ATtiny1607 Pin Function Shared Functionality PB7 Yellow LED0 Edge connector, On-board debugger

4.2.2 Mechanical Switch The ATtiny1607 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).

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 PC4.

Table 4-2. Mechanical Switch

ATtiny1607 Pin Description Shared Functionality PC4 User switch (SW0) Edge connector, On-board debugger

4.2.3 On-Board Debugger Implementation ATtiny1607 Curiosity Nano features an on-board debugger that can be used to program and debug the ATtiny1607 using UPDI. The on-board debugger also includes a Virtual COM port (CDC) interface over UART and DGI GPIO. Atmel Studio/Microchip MPLAB® X IDE can be used as a front-end for the on-board debugger for programming and debugging. Data Visualizer can be used as a front-end for the CDC and DGI GPIO. 4.2.3.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, there is little contamination 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. Curiosity Nano.

Table 4-3. On-Board Debugger Connections

ATtiny1607 Pin Debugger Pin Function Shared Functionality PB3 CDC TX UART RX (ATtiny1607 RX line) Edge connector PB2 CDC RX UART TX (ATtiny1607 TX line) Edge connector UPDI DBG0 UPDI Edge connector PB7 DBG1 GPIO Edge connector, LED PC4 DBG2 GPIO Edge connector, Switch UPDI DBG3 RESET (J202, not connected by Edge connector default)

5. Hardware Revision History and Known Issues This user guide provides the latest available revision of the kit. This section contains 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 ATtiny1607 Curiosity Nano can be found in two ways; either through Atmel Studio/Microchip MPLAB® X IDE or by looking at the sticker on the bottom side of the PCB. By connecting a ATtiny1607 Curiosity Nano to a computer with Atmel Studio/Microchip MPLAB® X IDE running, an information window will pop up. The first six digits of the serial number, which is listed under kit details, contain the product identifier and revision. The same information can be found on the sticker on the bottom side of the PCB. Most kits will print the identifier and revision in plain text as A09-nnnn\rr, where “nnnn” is the identifier and “rr” is the revision. The boards with limited space have a sticker with only a QR code, containing the product identifier, revision and the serial number. The serial number string has the following format:

"nnnnrrssssssssss" n = product identifier r = revision s = serial number

The product identifier for ATtiny1607 Curiosity Nano is A09-3252.

5.2 Chip Erase at Low Voltage This kit supports variable voltage from 1.8-5.1V. When a chip erase of the ATtiny1607 is started, the BOD is enabled and uses the BODLEVEL set in the FUSE.BODCFG fuse byte. If the BODLEVEL is set higher than the selected target voltage on the kit, chip erase will fail.

Info: BODLEVEL0 in the ATtiny1607 has a maximum trigger voltage of 2.0V, which means that chip erase is likely to fail if the kit voltage is set to 1.8V.

5.3 Revision 2 Revision 2 adds the Target Power strap and staggers the holes along the edge of the PCB for convenient use of pin headers without soldering.

5.4 Revision 1 Revision 1 is the initially released revision with limited distribution. The holes along the edge of revision 1 are not staggered as described in Using Pin Headers and requires that any pin headers must be soldered into the board for use. Revision 1 does not have the Target Power strap described in 3.4 Target Current Measurement. Instead, the current can be measured across the Power Supply strap, as described in 3.5 Disconnecting the On-Board Debugger.

Figure 5-1. ATtiny1607 Curiosity Nano Revision 1

6. Document Revision History

Doc. rev. Date Comment B 11/2019 Updated kit images A 06/2019 Initial document release

7. Appendix

7.1 Schematic Figure 7-1. ATtiny1607 Curiosity Nano Schematic A B C D 2 of 4 of 2 03/09/2019 Altium.com Designed with Designed Date: Page: 8 8 PB3 PB2 PA0 PB7 PC4 - ATtiny1607 PA0_UPDI PB6 PB5 PB4 PA3 PA4 PA5 PA6 PA7 PC5 PC4_SW0 aePin Name UART RX UART TX UPDI GPIO1 GPIO0 NA C Revision: PCB

Debugger TX CDC RX CDC DBG0 DBG1 5.5V - DBG2 1.8V DBG3 VTG

J202 J204

DBG0

DBG3 VOFF GND VCC_EDGE GND 0-222 2 A09-3252 A08-2979 VBUS 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 3 2 7 7 VCC GND GND VOFF DBG3 DBG0 VBUS ADC 7 ADC 6 ADC 5 ADC 2 ADC 1 ADC 0 ADC PWM 4 PWM 3 PWM TARGET C sebyNme:PCBA Revision: PCB Number: Assembly PCB Number: DEBUGGER RESERVED ID RX CDC CDC TX DBG1 DBG2 0 TX RX 1 SDA 2 SCL 3 MOSI 4 MISO 5 SCK 6 SS 7 GND (TX)0 (RX) 1 A3 J200 connector edge CNANO34-pin ATtiny1607_Curiosity_Nano_Target_MCU.SchDoc 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Microchip Norway Microchip Engineer: ML, TF Project Title Nano ATtiny1607Curiosity Sheet Title Target MCU Size File: Drawn By: Drawn NC

NOTE on UART/CDC: the denotes header the on RX/TX signal the of direction input/output source. it's to respective DEBUGGER. the from output is CDC TX DEBUGGER. the to input is RX CDC TX is output from the TARGET device. RX is input to the TARGET device. I2C: on NOTE be should Pull-ups board. on pull-ups No device(s). slave to close mounted ID_SYS

CDC_RX

CDC_TX

DBG1 DBG2 GND J201 J203 J205 J206 TX RX 6 6 UART PB2_TXD PB3_RXD PB7_LED0 PC4_SW0 PA1_TX1 PA2_RX1 PB1_SDA PB0_SCL PC2_MOSI PC1_MISO PC0_SCK PC3_SS PB2_TXD PB3_RXD CDC_UART DBG0 DBG3 DBG1 DBG2 VOFF ID_SYS DEBUGGER CONNECTIONS DEBUGGER 5 5 4 4 PC1_MISO PC0_SCK PB0_SCL PB1_SDA PB2_TXD PB3_RXD GND 18 17 16 15 14 13 25 PC1 PC0 PB0 PB1 PB2 PB3 PAD

ATtiny1607-MNR PC2 PB4

19 12 PC2_MOSI PB4

PC3 PB5

20 11 PC3_SS PB5

PC4 PB6

21 10 PB6 PC4_SW0

PC5 PB7

22 9 PC5 PB7_LED0

RESET/UPDI/PA0 PA7

23 8 PA7 PA0_UPDI

PA1 PA6

2.2uF C205 24 7 PA1_TX1 PA6 3 3 GND VCC_EDGE PA2 PA3/CLKI GND VCC PA4 PA5 U200 BULK TARGET

ATtiny1607

1 2 3 4 5 6

PB7_LED0

SML-D12Y1WT86

ELWLED YELLOW

PA2_RX1 PA3 PA4 PA5 2 1

R203 D200 VCC_TARGET USER LED USER 2 2 C200 100n L200 BLM18PG471SN1 GND

VCC_TARGET

4 2 PC4_SW0

R202

GND SW200 3 1 TS604VM1-035CR USER BUTTON USER 1 1 A B C D

© 2019 Microchip Technology Inc. User Guide DS50002897B-page 20 ATtiny1607 Curiosity Nano Appendix A B C D 3 of 4 of 3 09.05.2019 Altium.com Designed with Designed Date: Page: 8 8 - UART RX UART TX UART UPDI UPDI GPIO GPIO RESET ID_SYS VCC_P3V3 C101 2.2uF D- D+ ID GND SHIELD1 SHIELD2 SHIELD3 SHIELD4 VBUS C Revision: PCB J105 J105 VCC_P3V3 GND MU-MB0142AB2-269 1 2 3 4 5 6 7 8 9 2 3 4 5 6 7 8 9 1 2 AGTTARGET TARGET RX UART TX UART DAT CLK GPIO MCLR ICSP PTC Resettable fuse: Resettable PTC 500mA current: Hold 1000mA current: Trip 5 1 2 1 2 5

MIC5528: 5.5V to 2.5V Vin: 3.3V Fixed Vout: 500mA Imax: 500mA @ 260mV Dropout:

k 1 SHIELD 1k

0-222 2 A09-3252 A08-2979 2 1 1 R

NC R112

GND

P E

VOUT VOUT EP USBD_N USBD_N USBD_P Interface 7 7 D100 D100 LED GREEN VCC_P3V3

CDC TX CDC RX CDC - VCC SML-P12MTT86R Signal DBG0 DBG1 DBG2 DBG3 SML-P12MTT86R

1 VCC_VBUS

D N GND G G G

GND 3 3 MIC5528-3.3YMT 7 7 EN VIN U101 ID_SYS U101 F100 MC36213 6 6 4 4 1k PCB Assembly Number: PCBA Revision: PCBA Number: Assembly PCB Number: PCB R107 GND A3 ATtiny1607_Curiosity_Nano_Debugger.SchDoc VBUS VCC_VBUS C100 4.7uF Drawn By: Drawn Microchip Norway Microchip Engineer: TF, HN Title Project Title Sheet Debugger Size File: ATtiny1607 Curiosity Nano Curiosity ATtiny1607 DEBUGGER REGULATOR DEBUGGER POWER/STATUS LED DEBUGGER USB MICRO-B CONNECTOR ID PIN 6 6 GND SRST C104 100n USBD_P USBD_N ID_SYS CDC_TX_CTRL VOFF CDC_RX_CTRL VTG_EN DBG3_CTRL TP101 GND GND 21 20 19 18 17 33 22 24 23 STATUS_LED TP100 GND VCC_P3V3 PAD PA22 PA19 PA18 PA17 PA16 U100 SAMD21E18A-MUT

2 4 6 8 10

PA27 PA15

BOOT 25 16 DBG1_CTRL

RESETN PA14

26 15 SRST DBG0_CTRL

PA28 USB_DP/PA25 USB_DM/PA24 PA11

27 14 USB_SOF/PA23 VBUS_ADC

GND

GND GND PA10 GND SRST SRST

VTref TRST VTref TRST

28 13 REG_ENABLE

VDDCORE PA09

GND 29 12 DBG2_GPIO

VDDIN PA08

30 11

TCK TDO TDO TMS TMS GND Vsup Vsup TDI TDI DBG2_CTRL

SWDCLK/PA30 GND

J102 Array Testpoint Testpoint Array Testpoint 31 5 10 5

SWDIO/PA31 VDDANA

32 1 3 5 7 9 9 VCC_P3V3 C108 100n VCC_MCU_CORE PA00 PA01 PA02 PA03 PA04 PA05 PA06 PA07 1 2 3 4 5 6 7 8 1u C106 C107 100n SWCLK SWDIO SWCLK SWDIO GND Programming connector connector Programming of programming factory for Debugger GND DEBUGGER TESTPOINTs J100: regulators. on-board and shifters level the from power target of separation full for used Cut-strap more for cut be could strap this supply, power external an using measurements current For - range. ampere micro the in is switch the through back Leakage measurements. accurate J101: measurement current easy for used be can that pin-header pitch 100mil 1x2 a for footprint is This footprint: the use To Button. / LED the and microcontroller target the to pin-header a mount and holes, the between track the Cut - MIC5353: 6V to 2.6V Vin: 5.1V to 1.25V Vout: 500mA Imax: 500mA @ 160mV 50mV@150mA, (typical): Dropout initial 2% Accuracy: limit current and shutdown Thermal regulator. the in voltage dropout the and voltage input the by limited is voltage output Maximum dropout) - Vin = (Vmax S0_0_RX S1_0_TX S1_1_RX DAC VTG_ADC RESERVED S0_2_TX S0_3_CLK VCC_P3V3 1k J101 R108 4 4 VCC_EDGE VCC_TARGET J100 VCC_P3V3 GND VCC_P3V3 GND VCC_P3V3 GND VCC_P3V3 GND VCC_P3V3 GND DBG3_CTRL 3 3 3 3 3 2 2 2 2 2 1 1 1 1 1 Q101 DMN65D8LFB VCC_LEVEL 1 GND C1 B1 A1 A A A A A GND GND GND GND GND VCCA VCCA VCCA VCCA VCCA

GND

74LVC1T45FW4-7 74LVC1T45FW4-7 74LVC1T45FW4-7 74LVC1T45FW4-7 74LVC1T45FW4-7 3 VOUT VOUT 2 GND DIR B DIR B DIR B DIR B DIR B VCCB VCCB VCCB VCCB VCCB U103 U104 U105 U106 U107 6 6 6 6 6 5 4 5 4 5 4 5 4 5 4 EN VIN VIN U108 MIC94163 VTG_ADC DAC

1k 1k

k 7 4

3 47k 3 B2 C2 A2 R110

R111

GND VTG_EN VCC_LEVEL VCC_LEVEL VCC_LEVEL VCC_LEVEL VCC_LEVEL

DBG3 OPEN DRAIN OPEN DBG3

k 7 47k 4 k 7 47k 4

R102 R105 GND GND 33k DBG2_CTRL CDC_TX_CTRL CDC_RX_CTRL DBG0_CTRL DBG1_CTRL

R106

C103 2.2uF

k 7 47k 4 k 7 27k 2

1 0 1 R101 R 4 0 1 R104 R

GND REG_ADJUST 4 5 2 2 4 5 VCC_REGULATOR GND VOUT

2 2

NC/ADJ MIC5353U102MIC5353

7 7 GND GND CDC_TX CDC_RX DBG0 DBG1 DBG2 DBG3 VOFF Adjustable output and limitations: and output Adjustable target. the to 5.1V and 1.25V between regulator the of voltage output the adjust can debugger on-board The - target to still allow communication. allow still to target target. the to delivered voltage minimum the limit will and 1.70V of level volatege minimal a has switch output The - - Firmware configuration will limit the voltage range to be within the the target specification. target the the within be to range voltage the limit will configuration Firmware - 0.5%. within to accuracy voltage output the adjust will loop feedback Firmware - - The level shifters have a minimal voltage level of 1.65V and will limit the minimum operating voltage allowed for the the for allowed voltage operating minimum the limit will and 1.65V of level voltage minimal a have shifters level The - EN BYP VIN U102 1 6 3 1 6 3 C102 100n

GND

k 7 47k 4 R103 TX RX

REG_ENABLE

VBUS_ADC

UART

k 7 47k 4 k 7 47k 4

R109 R100 GND 1 1 VCC_VBUS TARGET ADJUSTABLE REGULATOR DBG0 DBG1 DBG2 DBG3 VOFF CDC_UART A B C D

7.2 Assembly Drawing Figure 7-2. ATtiny1607 Curiosity Nano Assembly Drawing Top PAJ20000 COJ200PAJ200034 PAJ200033 PAJ200032 PAJ200031 PAJ200030 PAJ200029 PAJ200028 PAJ200027 PAJ200026 PAJ200025 PAJ200024 PAJ200023 PAJ200022 PAJ200021 PAJ200020 PAJ200019 PAJ200018 PAJ10001COJ100 PAJ10002 PAU10100 PAC10002COC100 PAC10001 PAU10103 PAU10102 PAU10101 PAC10102 COR103PAR10301 PAR10302 PAC10201COC102 PAC10202 PAR10601COR106 PAR10602 PAF10001 PAU10107 COU101 COC101 PAU10201 PAU10206 PAU1080C2 PAU1080C1 PAC20501 PAU10104 PAU10105 PAU10106 PAC10101 PAR10102 PAR10402 COF100 PAU10202COU102 PAU10207 PAU10205 COR101 PAU1080B2 PAU1080B1 PAC20502COC205 PAJ10101COJ101 PAJ10506 PAR11001COR110 PAR11002 PAU10203 PAU10204 PAR10101 PAR10401COR104 PAU1080A2COU108 PAU1080A1 PAJ10102 PAF10002 PAQ10100PAQ10102 PAR10002 PAR10902 COQ101PAQ10103 PAQ10101 PAC10301COC103PAC10302 COJ202PAJ20201 PAR10001COR100 PAR10901COR109 PAU10701 PAU10706 PAJ20202 PAU200019 PAU200018 PASW20003 PASW20001 PAJ105010PAJ10508 COU107PAU10700PAU10702 PAU10705 PAU200020 PAU200017 PAU10703PAU10704 PAU200021 PAU200016 PAJ10501 PAC10402 PAR11102 PAC10802 COJ206PAJ20601 PAJ20602 PAU200022 PAU200015 PAU10601 PAU10606 C PAJ10201 PAJ10502PAJ10203 PAJ10205 COC108 PAU200023 PAU200014 PAD20001 PAR20302 PAR20202 COR111 PAU10602PAU10605 COJ102 PAC10401COC104 PAR11101 PAU100016 PAU100015 PAU100014 PAU100013 PAU100012 PAU100011 PAU100010 PAU10009 PAC10801 COU106PAU10600 COJ205PAJ20501 PAU200024 PAU200013 COJ105 PAJ10503 PAU100017 PAU10008 PAU10603PAU10604 PAJ20502 COU200 PAU20000 COD200 COR203 COR202 PAJ10504 PAU20001 PAU200012 PAR20301 PAR20201 PAJ10202 PAJ10204 PAJ10206 PAU100018 PAU10007 PAR10802 PAU10501 PAU10506 PAU20002PAU200025 PAU200011 PAD20002 COSW200 PAU100019 PAU10006 COU105PAU10500PAU10502 PAU10505 COJ204PAJ20401 PAU20003 PAU200010 PAJ10505 COR108 PAU10503PAU10504 PAJ20402 PAU20004 PAU20009 PAU100020 COU100 PAU10005 PAR10801 PAU20005 PAU20008 PAJ105011 PAJ10500 PAU100021 PAU10004 PAR10201COR102 PAR10202 PAJ20101COJ201 PAC20001 PAU20006 PAU20007 COLABEL1 PAJ10509 PAU100022 PAU100033 PAU10003 PAR10502 PAJ20102 COTP101 COC200PAC20002 PAU100023PATP10101 PAU10002 COR105 PAU10401 PAU10406 PAL20001 PASW20004 PASW20002 PAU100024 PAU10001 PAR10501 COU104PAU10400PAU10402 PAU10405 COJ203PAJ20301 PAU10403 PAU10404 PAJ20302 COL200 PAJ10507 COTP100PATP10001PAU100025 PAU100026 PAU100027 PAU100028 PAU100029 PAU100030 PAU100031 PAU100032 PAL20002 PAU10301 PAU10306 PAU10302PAU10305 COU103PAU10300 PAD10002COD100 PAD10001 PAR11201COR112 PAR11202 PAR10701COR107 PAR10702 COC106PAC10601 PAC10602 PAC10701COC107PAC10702 PAU10303PAU10304 PAJ20001 PAJ20002 PAJ20003 PAJ20004 PAJ20005 PAJ20006 PAJ20007 bPAJ20008 PAJ20009 PAJ200010 PAJ200011 PAJ200012 PAJ200013 PAJ200014 PAJ200015 PAJ200016 PAJ200017 Figure 7-3. ATtiny1607 Curiosity Nano Assembly Drawing Bottom PAJ20000 PAJ20000 PAJ200018 PAJ200018 PAJ200019 PAJ200020 PAJ200021 PAJ200022 PAJ200023 PAJ200024 PAJ200025 PAJ200026 PAJ200027 PAJ200028 PAJ200029 PAJ200030 PAJ200031 PAJ200032 PAJ200033 COJ200 PAJ200034 COJ100 PAJ10002 PAJ10001 COJ100 COR106 PAR10602 PAR10601 COR106 PAC10202 PAC10201 COC102 PAR10302 PAR10301 COR103 PAC10102 PAU10101 PAU10100 PAU10102 PAU10103 PAC10001 COC100 PAC10002 PAU10107 PAU10107 PAF10001 PAC20501 PAC20501 PAU1080C1 PAU1080C2 PAU10206 PAU10201 COC101 COU101 PAR10402 PAR10402 PAR10102 PAC10101 PAU10106 PAU10105 PAU10104 COJ101 COJ101 PAJ10101 PAC20502 COC205 PAU1080B1 PAU1080B2 COR101 PAU10205 PAU10207 PAU10202 COU102 COF100 PAJ10102 PAJ10102 PAU1080A1 COU108 PAU1080A2 PAR10401 COR104 PAR10101 PAU10204 PAU10203 PAR11002 PAR11001 COR110 PAJ10506 PAR10902 PAR10902 PAR10002 PAQ10100 PAQ10102 PAF10002 COJ202 PAJ20201 COJ202 PAC10302 PAC10301 COC103 PAQ10101 COQ101 PAQ10103 PASW20001 PASW20001 PASW20003 PAU200018 PAU200019 PAJ20202 PAU10706 PAU10701 PAR10901 COR109 PAR10001 COR100 PAU200017 PAU200017 PAU200020 PAU10705 PAU10700 PAU10702 COU107 PAJ10508 PAJ105010 PAU200016 PAU200016 PAU200021 PAU10704 PAU10703 PAU200015 PAU200015 PAU200022 PAJ20602 PAJ20601 COJ206 PAC10802 PAR11102 PAC10402 PAJ10501 PAR20202 PAR20202 PAR20302 PAD20001 PAU200014 PAU200023 PAU10606 PAU10601 COC108 PAJ10205 PAJ10502 PAJ10203 PAJ10201 PAU10605 PAU10605 PAU10602 COR111 PAU200013 PAU200013 PAU200024 PAU10600 COU106 PAC10801 PAU10009 PAU100010 PAU100011 PAU100012 PAU100013 PAU100014 PAU100015 PAU100016 PAR11101 PAC10401 COC104 COJ205 PAJ20501 COJ205 PAU10604 PAU10603 PAJ10503 COJ102 COR202 COR202 COR203 COD200 PAU20000 COU200 PAJ20502 PAU10008 PAU100017 COJ105 PAR20201 PAR20201 PAR20301 PAU200012 PAU20001 PAJ10504 COSW200 COSW200 PAD20002 PAU200011 PAU200025 PAU20002 PAU10506 PAU10501 PAR10802 PAU10007 PAU100018 PAJ10206 PAJ10204 PAJ10202 PAU10505 PAU10505 PAU10502 PAU200010 PAU200010 PAU20003 PAJ20401 COJ204 PAU10500 COU105 c PAU10006 PAU100019 PAJ10505 PAJ10505 PAU20009 PAU20009 PAU20004 PAJ20402 PAU10504 PAU10503 COR108 PAU20008 PAU20008 PAU20005 PAR10801 PAU10005 COU100 PAU100020 COLABEL1 COLABEL1 PAU20007 PAU20006 PAC20001 PAJ20101 COJ201 PAR10202 PAR10201 COR102 PAU10004 PAU100021 PAJ10500 PAJ105011 PAJ20102 PAJ20102 PAR10502 PAU10003 PAU100033 PAU100022 PAJ10509 COC200 PAC20002 COC200 COTP101 PASW20002 PASW20002 PASW20004 PAL20001 PAU10406 PAU10401 COR105 PAU10002 PAU100023 PATP10101 COJ203 PAJ20301 COJ203 PAU10405 PAU10400 PAU10402 COU104 PAR10501 PAU10001 PAU100024 COL200 COL200 PAJ20302 PAU10404 PAU10403 t R PAL20002 COTP100 PAJ10507 PAU100032 PAU100032 PAU100031 PAU100030 PAU100029 PAU100028 PAU100027 PAU100026 PAU100025 PATP10001 PAU10306 PAU10306 PAU10301 PAU10305 PAU10305 PAU10300 PAU10302 COU103 PAU10304 PAU10304 PAU10303 PAC10702 PAC10701 COC107 PAC10602 PAC10601 COC106 PAR10702 PAR10701 COR107 PAR11202 PAR11201 COR112 PAD10001 PAD10002 COD100 PAJ200017 PAJ200017 PAJ200016 PAJ200015 PAJ200014 PAJ200013 PAJ200012 PAJ200011 PAJ200010 PAJ20009 PAJ20008 PAJ20007 PAJ20006 PAJ20005 PAJ20004 PAJ20003 PAJ20002 PAJ20001

7.3 Curiosity Nano Base for Click boards™ Figure 7-4. ATtiny1607 Curiosity Nano Pinout Mapping PB4 PA2 PA1 PB0 PB1 PC5 +3.3V 3 EXT1 2 1 920 19 DGND ID A PA5 PB4 PB0 PA6 PB2 PC2 PA3 PC0 PC4 PB1 PB3 PC4 PC1 GND N GND GND NPWM INT RX TX SCL AN SDA RST +5V CS SCK MISO MOSI +3.3V Xplained Pro Extension TM PA5 PC5 PC0 PC1 PC2 N GND GND 33 +5V +3.3V PA3 PC4 PB3 PB2 PB0 PB1 PA4 PA2 PA1 PB0 PB1 for click boards Curiosity Nano Base 1 2 NPWM INT RX AN RST CS GND GND C TX SCL SDA +5V SCK MISO MOSI +3.3V NPWM AN S INT RX RST CS GND GND C TX SCL SDA +5V SCK MISO MOSI +3.3V N GND GND N GND GND PA6 PC4 PC0 PC1 PC2 B PB5 PA7 PB6 PC3 PC0 PC1 PC2 33 +5V +3.3V 33 +5V +3.3V UPDI TCA0 WO1 TCA0 WO4 TCA0 WO3 Peripheral Port PWM Power Ground PA0 SW0 AIN9 AIN4 AIN6 AIN8 AIN3 AIN5 AIN7 Analog Debug I2C SPI UART Shared pinout PA4 GND PB6 PB4 PA6 GND PC4 PA3 PA5 PA7 VTG PB5 PC5 VOFF DBG0 VBUS DBG3

VBUS DBG3 GND PB6 PB4 PA4 PA6 GND PC4 VOFF DBG0 VTG PB5 PA3 PA5 PA7 PC5 USB SW0 ATtiny1607 LED0 ATtiny1607 DEBUGGER PS LED PS CURIOSITY NANO

ID CDCTX DBG2 PA2 PB0 PC1 PC3 PB2 NC CDCRX DBG1 PA1 PB1 PC2 PC0 GND PB3 NC ID PA2 PB0 PC3 PC1 PB2 PA1 PB1 PC2 GND PC0 PB3 DBG1 DBG2 CDC TX CDC RX SS PB2 PB7LED0TX0 SDA SCK PB3 PC4SW0RX0 SCL MISO MOSI (RX0) (TX0)

7.4 Connecting External Debuggers Even though there is an on-board debugger, external debuggers can be connected directly to the ATtiny1607 Curiosity Nano to program/debug the ATtiny1607. The on-board debugger keeps all the pins connected to the ATtiny1607 and board edge in tri-state when not actively used. Therefore, the on-board debugger will not interfere with any external debug tools. Figure 7-5. Connecting the MPLAB PICkit™ 4 In-Circuit Debugger/Programmer to ATtiny1607 Curiosity Nano

1 = Unused MPLAB® PICkit™ 4 2 = VDD 3 = Ground 4 = PGD 5 = Unused 6 = Unused 7 = Unused 8 = Unused

678 5 4 3 2 1

VDD Ground DATA

USB

PS LED NC VBUS ID VOFF

CDC RX DEBUGGER DBG3 CDC TX DBG0 DBG1 GND

DBG2 CURIOSITY NANO VTG

Figure 7-6. Connecting the Atmel-ICE to ATtiny1607 Curiosity Nano SAM AVR®

Atmel-ICE

Ground VDD 1 = Unused 6 = Unused 2 = GND 7 = Unused 3 = UPDI 8 = Unused 2 10 4 = VTG 9 = Unused 1 9 5 = Unused 10 = Unused DATA

USB

PS LED NC VBUS ID VOFF

CDC RX DEBUGGER DBG3 CDC TX DBG0 DBG1 GND

DBG2 CURIOSITY NANO VTG

To avoid contention between the external debugger and the on-board debugger, do not start any CAUTION programming/debug operation with the on-board debugger through Atmel Studio/Microchip MPLAB® X or mass storage programming while the external tool is active.

7.5 Getting Started with IAR IAR Embedded Workbench® for AVR® is a proprietary high-efficiency compiler which is not based on GCC. Programming and debugging of ATtiny1607 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 Debugger > Atmel-ICE, select the Atmel-ICE 1 tab. Select UPDI as the interface and, 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.

Figure 7-7. Select Target Device

Figure 7-8. Select Debugger

Figure 7-9. Configure Interface

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

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. © 2019, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved. ISBN: 978-1-5224-5237-9

Quality Management System

For information regarding Microchip’s Quality Management Systems, please visit http://www.microchip.com/quality.

AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE Corporate Office Australia - Sydney India - Bangalore Austria - Wels 2355 West Chandler Blvd. Tel: 61-2-9868-6733 Tel: 91-80-3090-4444 Tel: 43-7242-2244-39 Chandler, AZ 85224-6199 China - Beijing India - New Delhi Fax: 43-7242-2244-393 Tel: 480-792-7200 Tel: 86-10-8569-7000 Tel: 91-11-4160-8631 Denmark - Copenhagen Fax: 480-792-7277 China - Chengdu India - Pune Tel: 45-4450-2828 Technical Support: Tel: 86-28-8665-5511 Tel: 91-20-4121-0141 Fax: 45-4485-2829 http://www.microchip.com/support China - Chongqing Japan - Osaka Finland - Espoo Web Address: Tel: 86-23-8980-9588 Tel: 81-6-6152-7160 Tel: 358-9-4520-820 http://www.microchip.com China - Dongguan Japan - Tokyo France - Paris Atlanta Tel: 86-769-8702-9880 Tel: 81-3-6880- 3770 Tel: 33-1-69-53-63-20 Duluth, GA China - Guangzhou Korea - Daegu Fax: 33-1-69-30-90-79 Tel: 678-957-9614 Tel: 86-20-8755-8029 Tel: 82-53-744-4301 Germany - Garching Fax: 678-957-1455 China - Hangzhou Korea - Seoul Tel: 49-8931-9700 Austin, TX Tel: 86-571-8792-8115 Tel: 82-2-554-7200 Germany - Haan Tel: 512-257-3370 China - Hong Kong SAR Malaysia - Kuala Lumpur Tel: 49-2129-3766400 Boston Tel: 852-2943-5100 Tel: 60-3-7651-7906 Germany - Heilbronn Westborough, MA China - Nanjing Malaysia - Penang Tel: 49-7131-72400 Tel: 774-760-0087 Tel: 86-25-8473-2460 Tel: 60-4-227-8870 Germany - Karlsruhe Fax: 774-760-0088 China - Qingdao Philippines - Manila Tel: 49-721-625370 Chicago Tel: 86-532-8502-7355 Tel: 63-2-634-9065 Germany - Munich Itasca, IL China - Shanghai Singapore Tel: 49-89-627-144-0 Tel: 630-285-0071 Tel: 86-21-3326-8000 Tel: 65-6334-8870 Fax: 49-89-627-144-44 Fax: 630-285-0075 China - Shenyang Taiwan - Hsin Chu Germany - Rosenheim Dallas Tel: 86-24-2334-2829 Tel: 886-3-577-8366 Tel: 49-8031-354-560 Addison, TX China - Shenzhen Taiwan - Kaohsiung Israel - Ra’anana Tel: 972-818-7423 Tel: 86-755-8864-2200 Tel: 886-7-213-7830 Tel: 972-9-744-7705 Fax: 972-818-2924 China - Suzhou Taiwan - Taipei Italy - Milan Detroit Tel: 86-186-6233-1526 Tel: 886-2-2508-8600 Tel: 39-0331-742611 Novi, MI China - Wuhan Thailand - Bangkok Fax: 39-0331-466781 Tel: 248-848-4000 Tel: 86-27-5980-5300 Tel: 66-2-694-1351 Italy - Padova Houston, TX China - Xian Vietnam - Ho Chi Minh Tel: 39-049-7625286 Tel: 281-894-5983 Tel: 86-29-8833-7252 Tel: 84-28-5448-2100 Netherlands - Drunen Indianapolis China - Xiamen Tel: 31-416-690399 Noblesville, IN Tel: 86-592-2388138 Fax: 31-416-690340 Tel: 317-773-8323 China - Zhuhai Norway - Trondheim Fax: 317-773-5453 Tel: 86-756-3210040 Tel: 47-72884388 Tel: 317-536-2380 Poland - Warsaw Los Angeles Tel: 48-22-3325737 Mission Viejo, CA Romania - Bucharest Tel: 949-462-9523 Tel: 40-21-407-87-50 Fax: 949-462-9608 Spain - Madrid Tel: 951-273-7800 Tel: 34-91-708-08-90 Raleigh, NC Fax: 34-91-708-08-91 Tel: 919-844-7510 Sweden - Gothenberg New York, NY Tel: 46-31-704-60-40 Tel: 631-435-6000 Sweden - Stockholm San Jose, CA Tel: 46-8-5090-4654 Tel: 408-735-9110 UK - Wokingham Tel: 408-436-4270 Tel: 44-118-921-5800 Canada - Toronto Fax: 44-118-921-5820 Tel: 905-695-1980 Fax: 905-695-2078