Attiny3217 Curiosity Nano Hardware User Guide

ATtiny3217 ATtiny3217 Curiosity Nano Hardware User Guide

Preface

The ATtiny3217 Curiosity Nano Evaluation Kit is a hardware platform to evaluate microcontrollers in the tinyAVR 1- series. This board has the ATtiny3217 microcontroller (MCU) mounted. Supported by Atmel Studio and Microchip MPLAB® X Integrated Development Environments (IDEs), the board provides easy access to the features of the ATtiny3217 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 ATtiny3217.

• MPLAB® X IDE and Atmel Studio - Software to discover, configure, develop, program, and debug Microchip microcontrollers. • ATtiny3217 website - Find documentation, sample, and purchase microcontrollers. • ATtiny3217 Curiosity Nano website - Kit information, latest user guide and design documentation.

Table of Contents

Preface...... 1

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

2. Getting Started...... 5 2.1. Quick Start...... 5 2.2. Design Documentation and Relevant Links...... 5

3. Curiosity Nano...... 7 3.1. On-Board Debugger Overview...... 7 3.1.1. Debugger...... 7 3.1.2. Virtual Serial Port (CDC)...... 8 3.1.2.1. Overview...... 8 3.1.2.2. Operating System Support...... 8 3.1.2.3. Limitations...... 9 3.1.2.4. Signaling...... 9 3.1.2.5. Advanced Use...... 9 3.1.3. Mass Storage Device...... 10 3.1.3.1. Mass Storage Device Implementation...... 10 3.1.3.2. Fuse Bytes...... 11 3.1.3.3. Limitations of Drag-and-Drop Programming...... 11 3.1.3.4. Special Commands...... 11 3.1.4. Data Gateway Interface (DGI)...... 12 3.1.4.1. Debug GPIO...... 12 3.1.4.2. Timestamping...... 12 3.2. Curiosity Nano Standard Pinout...... 13 3.3. Power Supply...... 13 3.3.1. Target Regulator...... 14 3.3.2. External Supply...... 15 3.3.3. VBUS Output Pin...... 16 3.3.4. Power Supply Exceptions...... 16 3.4. Low Power Measurement...... 17 3.5. Programming External Microcontrollers...... 18 3.5.1. Supported Devices...... 18 3.5.2. Software Configuration...... 18 3.5.3. Hardware Modifications...... 19 3.5.4. Connecting to External Microcontrollers...... 20 3.6. Connecting External Debuggers...... 21

4. Hardware User Guide...... 24 4.1. Connectors...... 24 4.1.1. ATtiny3217 Curiosity Nano Pinout...... 24 4.1.2. Using Pin Headers...... 24 4.2. Peripherals...... 25

4.2.1. LED...... 25 4.2.2. Mechanical Switch...... 25 4.2.3. Crystal...... 25 4.2.4. On-Board Debugger Implementation...... 26 4.2.4.1. On-Board Debugger Connections...... 26

5. Hardware Revision History and Known Issues...... 28 5.1. Identifying Product ID and Revision...... 28 5.2. Revision 2...... 28

6. Document Revision History...... 29

7. Appendix...... 30 7.1. Schematic...... 30 7.2. Assembly Drawing...... 32 7.3. Curiosity Nano Base for Click boards™...... 33 7.4. Disconnecting the On-board Debugger...... 34 7.5. Getting Started with IAR...... 35

The Microchip Website...... 38

Product Change Notification Service...... 38

Customer Support...... 38

Microchip Devices Code Protection Feature...... 38

Legal Notice...... 38

Trademarks...... 39

Quality Management System...... 39

Worldwide Sales and Service...... 40

1. Introduction

1.1 Features • ATTINY3217-MFR Microcontroller • One Yellow User LED • One Mechanical User Switch • Footprint for 32.768 kHz Crystal • On-Board Debugger: – Board identification in Atmel Studio/Microchip MPLAB® X IDE – One green power and status LED – Programming and debugging – Virtual serial port (CDC) – Two debug GPIO channels (DGI GPIO) • USB Powered • Adjustable Target Voltage: – MIC5353 LDO regulator controlled by the on-board debugger – 1.8-5.5V 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 ATtiny3217 Curiosity Nano Evaluation Kit is a hardware platform to evaluate the ATtiny3217 microcontroller. Figure 1-1. ATtiny3217 Curiosity Nano Evaluation Kit Overview

Micro USB Power/Status ATtiny3217 32.768 kHz User LED User Switch Debugger Connector LED MCU Crystal Footprint (LED0) (SW0)

2. Getting Started

2.1 Quick Start Steps to start exploring the ATtiny3217 Curiosity Nano Board: 1. Download Atmel Studio/Microchip MPLAB® X IDE. 2. Launch Atmel Studio/Microchip MPLAB® X IDE. 3. Optional: Use MPLAB® Code Configurator or Atmel START to generate drivers and examples. 4. Write your application code. 5. Connect a USB cable (Standard-A to Micro-B or Micro-AB) between the PC and the debug USB port on the board. Driver Installation When the board is connected to your computer for the first time, the operating system will perform a driver software installation. The driver file supports both 32- and 64-bit versions of Microsoft® Windows® XP, Windows Vista®, Windows 7, Windows 8, and Windows 10. The drivers for the board are included with Atmel Studio/Microchip MPLAB® X IDE. Kit Window Once the board is powered, the green status LED will be lit, and Atmel Studio/Microchip MPLAB® X IDE will auto- detect which boards are connected. Atmel Studio/Microchip MPLAB® X IDE will present relevant information like data sheets and board documentation. The ATtiny3217 device on the ATtiny3217 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.2 Design Documentation and Relevant Links The following list contains links to the most relevant documents and software for the ATtiny3217 Curiosity Nano Board:

• MPLAB® X IDE - MPLAB X IDE is a software program that runs on a PC (Windows®, Mac OS®, Linux®) to develop applications for Microchip microcontrollers and digital signal controllers. It is called an Integrated Development Environment (IDE) because it provides a single integrated “environment” to develop code for embedded microcontrollers. • Atmel Studio - Free IDE for the development of C/C++ and assembler code for microcontrollers. • IAR Embedded Workbench® for AVR® - This is a commercial C/C++ compiler that is available for AVR microcontrollers. There is a 30-day evaluation version as well as a 4 KB code-size-limited kick-start version available from their website. • MPLAB® Code Configurator - MPLAB Code Configurator (MCC) is a free software plug-in that provides a graphical interface to configure peripherals and functions specific to your application. • Atmel START - Atmel START is an online tool that 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. • ATtiny3217 Curiosity Nano website - Kit information, latest user guide and design documentation. • ATtiny3217 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. When plugged in, a Kit Window is displayed with links to key documentation, including relevant user guides, application notes, data sheets, and example code. Everything is easy to find. The on-board debugger features a virtual serial port (CDC) for serial communication to a host PC and a Data Gateway Interface (DGI) with debug GPIO pin(s).

3.1 On-Board Debugger Overview ATtiny3217 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 ATtiny3217 in Atmel Studio/Microchip MPLAB® X IDE • A mass storage device that allows drag-and-drop programming of the ATtiny3217 • A virtual serial port (CDC) that is connected to a Universal Asynchronous Receiver/Transmitter (UART) on the ATtiny3217, 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 ATtiny3217 Curiosity Nano Board. The table below shows how the LED is controlled in different operation modes. Table 3-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 Success: The LED blinks slowly for 2 sec. programming 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.

3.1.1 Debugger The on-board debugger on the ATtiny3217 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 ATtiny3217 using Atmel Studio/Microchip MPLAB® X IDE, as well as some third-party IDEs.

Remember: Keep the debugger’s firmware up-to-date. Firmware upgrades are done automatically when using Atmel Studio/Microchip MPLAB® X IDE.

3.1.2 Virtual Serial Port (CDC) The virtual serial port (CDC) is a general purpose serial bridge between a host PC and a target device. 3.1.2.1 Overview The on-board debugger implements a composite USB device that includes a standard Communications Device Class (CDC) interface, which appears on the host as a virtual serial port. The CDC can be used to stream arbitrary data in both directions between the host computer and the target: All characters sent through the virtual serial port on the host computer will be transmitted as UART on the debugger’s CDC TX pin, and UART characters captured on the debugger’s CDC RX pin will be returned to the host computer through the virtual serial port. Figure 3-1. CDC Connection

PC Terminal Debugger Target Target MCU Send Receive Terminal CDC TX UART RX USB CDC RX UART TX Software Terminal Target Receive Send

Info: As shown in Figure 3-1, the debugger’s CDC TX pin is connected to a UART RX pin on the target for receiving characters from the host computer. Similarly, the debugger’s CDC RX pin is connected to a UART TX pin on the target for transmitting characters to the host computer.

3.1.2.2 Operating System Support On Windows machines, the CDC will enumerate as Curiosity Virtual COM Port and appear in the Ports section of the Windows Device Manager. The COM port number can also be found there.

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

On Linux machines, the CDC will enumerate and appear as /dev/ttyACM#.

Info: tty* devices belong to the “dialout” group in Linux, so it may be necessary to become a member of that group to have permissions to access the CDC.

On MAC machines, the CDC will enumerate and appear as /dev/tty.usbmodem#. Depending on which terminal program is used, it will appear in the available list of modems as usbmodem#.

Info: For all operating systems: Be sure to use a terminal emulator that supports DTR signaling. See 3.1.2.4 Signaling.

3.1.2.3 Limitations Not all UART features are implemented in the on-board debugger CDC. The constraints are outlined here: • Baud rate: Must be in the range of 1200 bps to 500 kbps. Any baud rate outside this range will be set to the closest limit, without warning. Baud rate can be changed on-the-fly. • Character format: Only 8-bit characters are supported. • Parity: Can be odd, even, or none. • Hardware flow control: Not supported. • Stop bits: One or two bits are supported.

3.1.2.4 Signaling During USB enumeration, the host OS will start both communication and data pipes of the CDC interface. At this point, it is possible to set and read back the baud rate and other UART parameters of the CDC, but data sending and receiving will not be enabled. When a terminal connects on the host, it must assert the DTR signal. As this is a virtual control signal implemented on the USB interface, it is not physically present on the board. Asserting the DTR signal from the host will indicate to the on-board debugger that a CDC session is active. The debugger will then enable its level shifters (if available), and start the CDC data send and receive mechanisms. Deasserting the DTR signal will not disable the level shifters but disable the receiver so no further data will be streamed to the host. Data packets that are already queued up for sending to the target will continue to be sent out, but no further data will be accepted.

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

Tip: The on-board debugger’s CDC TX pin will not be driven until the CDC interface is enabled by the host computer. Also, there are no external pull-up resistors on the CDC lines connecting the debugger and the target, which means that during power-up, these lines are floating. To avoid any glitches resulting in unpredictable behavior like framing errors, the target device should enable the internal pull-up resistor on the pin connected to the debugger’s CDC TX pin.

3.1.2.5 Advanced Use

CDC Override Mode In normal operation, the on-board debugger is a true UART bridge between the host and the device. However, in certain use cases, the on-board debugger can override the basic operating mode and use the CDC TX and RX pins for other purposes. Dropping a text file into the on-board debugger’s mass storage drive can be used to send characters out of the debugger’s CDC TX pin. The filename and extension are trivial, but the text file must start with the characters: CMD:SEND_UART=

The maximum message length is 50 characters – all remaining data in the frame are ignored. The default baud rate used in this mode is 9600 bps, but if the CDC is already active or has been configured, the previously used baud rate still applies.

USB-Level Framing Considerations Sending data from the host to the CDC can be done byte-wise or in blocks, which will be chunked into 64-byte USB frames. Each such frame will be queued up for sending to the debugger’s CDC TX pin. Transferring a small amount of data per frame can be inefficient, particularly at low baud rates, because the on-board debugger buffers frames and not bytes. A maximum of four 64-byte frames can be active at any time. The on-board debugger will throttle the incoming frames accordingly. Sending full 64-byte frames containing data is the most efficient method. When receiving data on the debugger’s CDC RX pin, the on-board debugger will queue up the incoming bytes into 64-byte frames, which are sent to the USB queue for transmission to the host when they are full. Incomplete frames are also pushed to the USB queue at approximately 100 ms intervals, triggered by USB start-of-frame tokens. Up to eight 64-byte frames can be active at any time. If the host (or the software running on it) fails to receive data fast enough, an overrun will occur. When this happens, the last-filled buffer frame will be recycled instead of being sent to the USB queue, and a full frame of data will be lost. To prevent this occurrence, the user must ensure that the CDC data pipe is being read continuously, or the incoming data rate must be reduced.

3.1.3 Mass Storage Device The on-board debugger includes a simple Mass Storage Device implementation, which is accessible for read/write operations via the host operating system to which it is connected. It provides: • Read access to basic text and HTML files for detailed kit information and support • Write access for programming Intel® HEX formatted files into the target device’s memory • Write access for simple text files for utility purposes 3.1.3.1 Mass Storage Device Implementation The on-board debugger implements a highly optimized variant of the FAT12 file system that has several limitations, partly due to the nature of FAT12 itself and optimizations made to fulfill its purpose for its embedded application. The Curiosity Nano USB Device is USB Chapter 9-compliant as a mass storage device but does not, in any way, fulfill the expectations of a general purpose mass storage device. This behavior is intentional. When using the Windows operating system, the on-board debugger enumerates as a Curiosity Nano USB Device that can be found in the disk drives section of the device manager. The CURIOSITY drive appears in the file manager and claims the next available drive letter in the system. The CURIOSITY drive contains approximately one MB of free space. This does not reflect the size of the target device’s Flash in any way. When programming an Intel® HEX file, the binary data are encoded in ASCII with metadata providing a large overhead, so one MB is a trivially chosen value for disk size. It is not possible to format the CURIOSITY drive. When programming a file to the target, the filename may appear in the disk directory listing. This is merely the operating system’s view of the directory, which, in reality, has not been updated. It is not possible to read out the file contents. Removing and replugging the board will return the file system to its original state, but the target will still contain the application that has been previously programmed. To erase the target device, copy a text file starting with “CMD:ERASE” onto the disk. By default, the CURIOSITY drive contains several read-only files for generating icons as well as reporting status and linking to further information: • AUTORUN.ICO – icon file for the Microchip logo • AUTORUN.INF – system file required for Windows Explorer to show the icon file • KIT-INFO.HTM – redirect to the development board website • KIT-INFO.TXT – a text file containing details about the board’s debugger firmware version, board name, USB serial number, device, and drag-and-drop support • STATUS.TXT – a text file containing the programming status of the board

Info: STATUS.TXT is dynamically updated by the on-board debugger. The contents may be cached by the OS and, therefore, do not reflect the correct status.

3.1.3.2 Fuse Bytes

Fuse Bytes (AVR® MCU Targets) When doing drag-and-drop programming, the debugger masks out fuse bits that attempt to disable Unified Program and Debug Interface (UPDI). This means that the UPDI pin cannot be used in its reset or GPIO modes; selecting one of the alternative functions on the UPDI pin would render the device inaccessible without using an external debugger capable of high-voltage UPDI activation. 3.1.3.3 Limitations of Drag-and-Drop Programming

Lock Bits Lock bits included in the hex file will be ignored when using drag-and-drop programming. To program lock bits, use Atmel Studio/Microchip MPLAB® X IDE.

Enabling CRC Check in Fuses It is not advisable to enable the CRC check in the target device’s fuses when using drag-and-drop programming. This because a subsequent chip erase (which does not affect fuse bits) will effect a CRC mismatch, and the application will fail to boot. To recover a target from this state, a chip erase must be done using Atmel Studio/Microchip MPLAB® X IDE, which will automatically clear the CRC fuses after erasing. 3.1.3.4 Special Commands Several utility commands are supported by copying text files to the mass storage disk. The filename or extension is irrelevant – the command handler reacts to content only. Table 3-2. Special File Commands

Command Content Description CMD:ERASE Executes a chip erase of the target CMD:SEND_UART= Sends a string of characters to the CDC UART. See “CDC Override Mode”. 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: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.

3.1.4 Data Gateway Interface (DGI) Data Gateway Interface (DGI) is a USB interface for transporting raw and timestamped data between on-board debuggers and host computer-based visualization tools. MPLAB Data Visualizer is used on the host computer to display debug GPIO data. It is available as a plug-in for MPLAB® X IDE or a stand-alone application that can be used in parallel with Atmel Studio/Microchip MPLAB® X IDE. Although DGI encompasses several physical data interfaces, the ATtiny3217 Curiosity Nano implementation includes logic analyzer channels: • Two debug GPIO channels (also known as DGI GPIO)

3.1.4.1 Debug GPIO Debug GPIO channels are timestamped digital signal lines connecting the target application to a host computer visualization application. They are typically used to plot the occurrence of low-frequency events on a time-axis – for example, when certain application state transitions occur. The figure below shows the monitoring of the digital state of a mechanical switch connected to a debug GPIO in MPLAB Data Visualizer. Figure 3-2. Monitoring Debug GPIO with MPLAB® Data Visualizer

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.

3.1.4.2 Timestamping DGI sources are timestamped as they are captured by the debugger. The timestamp counter implemented in the Curiosity Nano debugger increments at 2 MHz frequency, providing a timestamp resolution of a half microsecond.

3.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 3-3. Curiosity Nano Standard Pinout

Debugger Signal Target MCU Description ID — ID line for extensions CDC TX UART RX USB CDC TX line CDC RX UART TX USB CDC RX line DBG0 UPDI Debug data line DBG1 GPIO1 debug GPIO1

DBG2 GPIO0 debug GPIO0 DBG3 RESET Reset line NC — No connect 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 3-3. Curiosity Nano Standard Pinout

USB

PS LED NC VBUS ID VOFF

CDC RX DEBUGGER DBG3 CDC TX DBG0 DBG1 GND

DBG2 CURIOSITY NANO VTG

3.3 Power Supply The board is powered through the USB port and contains two LDO regulators, one to generate 3.3V for the on-board debugger, and an adjustable LDO regulator for the target microcontroller ATtiny3217 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 ATtiny3217 Curiosity Nano.

Figure 3-4. 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 board target section by manipulating the MIC5353’s feedback voltage. The hardware implementation is limited to an approximate voltage range from 1.7V to 5.1V. Additional output voltage limits are configured in the debugger firmware to ensure that the output voltage never exceeds the hardware limits of the ATtiny3217 microcontroller. The voltage limits configured in the on-board debugger on ATtiny3217 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 device programming dialog. Any change to the target voltage is persistent, even through a power toggle. The resolution is less than 5 mV but may be limited to 10 mV by the adjustment program.

Info: Voltage settings that are set up in Atmel Studio/Microchip MPLAB® X IDE are not immediately applied to the board. The new voltage setting is applied to the board when the debugger is accessed in any way, like pushing the Refresh Debug Tool Status button in the project dashboard tab, or programming/ reading program memory.

Info: There is a simple option to adjust the target voltage with a drag and drop command text file to the board. This only supports settings of 0.0V, 3.3V, and 5.0V. See section 3.1.3.4 Special Commands for further details.

The MIC5353 supports a maximum current load of 500 mA. It is an LDO regulator in a small package, placed on a small printed circuit board (PCB), and the thermal shutdown condition can be reached at lower loads than 500 mA. The maximum current load depends on the input voltage, the selected output voltage, and the ambient temperature. The figure below shows the safe operating area for the regulator, with an input voltage of 5.1V and an ambient temperature of 23°C.

Figure 3-5. Target Regulator Safe Operation Area

The voltage output of the target regulator is continuously monitored (measured) by the on-board debugger. If it is more than 100 mV over/under the voltage setting value, an error condition will be flagged, and the target voltage regulator will be turned off. This will detect and handle any short-circuit conditions. It will also detect and handle if an external voltage which causes VCC_TARGET to move outside of the voltage setting monitoring window of ±100 mV is suddenly applied to the VTG pin, without setting the VOFF pin low.

Info: If the external voltage is lower than the monitoring window lower limit (target voltage setting - 100 mV), the on-board debugger status LED will blink rapidly. If the external voltage is higher than the monitoring window upper limit (target voltage setting + 100 mV), the on-board debugger status LED will continue to shine. If the external voltage is removed, the status LED will start to blink rapidly until the on- board debugger detects the new situation and turns the target voltage regulator back on.

3.3.2 External Supply ATtiny3217 Curiosity Nano can be powered by an external voltage instead of the on-board target regulator. When the Voltage Off (VOFF) pin is shorted to ground (GND), the on-board debugger firmware disables the target regulator, and it is safe to apply an external voltage to the VTG pin. It is also safe to apply an external voltage to the VTG pin when no USB cable is plugged into the DEBUG connector on the board. The VOFF pin can be tied low/let go at any time. This will be detected by a pin-change interrupt to the on-board debugger, which controls the target voltage regulator accordingly.

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

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 WARNING condition of the ATtiny3217 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 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 ATtiny3217 and its peripherals, approximately 100 µA will be drawn from any external power source to power the on-board level shifters and voltage monitor circuitry when a USB cable is plugged in the DEBUG connector on the board. When a USB cable is not plugged in, some current is used to supply the level shifters voltage pins, which have a worst-case current consumption of approximately 5 µA. Typical values may be as low as 100 nA.

3.3.3 VBUS Output Pin ATtiny3217 Curiosity Nano has a VBUS output pin that can be used to power external components that need a 5V supply. The VBUS output pin has a PTC fuse to protect the USB against short circuits. A side effect of the PTC fuse is a voltage drop on the VBUS output with higher current loads. The chart below shows the voltage versus the current load of the VBUS output. Figure 3-6. VBUS Output Voltage vs. Current

3.3.4 Power Supply Exceptions This is a summary of most exceptions that can occur with the power supply.

Target Voltage Shuts Down This can happen if the target section draws too much current at a given voltage. This will cause the thermal shutdown safety feature of the MIC5353 regulator to kick in. To avoid this, reduce the current load of the target section.

Target Voltage Setting is Not Reached The maximum output voltage is limited by the USB input voltage (specified to be between 4.4V to 5.25V), and the voltage drop over the MIC5353 regulator at a given voltage setting and current consumption. If a higher output voltage is needed, use a USB power source that can provide a higher input voltage or use an external voltage supply on the VTG pin.

Target Voltage is Different From Setting This can be caused by an externally applied voltage to the VTG pin, without setting the VOFF pin low. If the target voltage differ more than 100 mV over/under the voltage setting, it will be detected by the on-board debugger, and the internal voltage regulator will be shut down. To fix this issue, remove the applied voltage from the VTG pin, and the on-board debugger will enable the on-board voltage regulator when the new condition is detected. Note that the PS LED will be blinking rapidly if the target voltage is below 100 mV of the setting, but will be lit normally when it is higher than 100 mV above the setting.

No, Or Very Low Target Voltage, and PS LED is Blinking Rapidly This can be caused by a full or partial short-circuit and is really a special case of the issue mentioned above. Remove the short-circuit, and the on-board debugger will re-enable the on-board target voltage regulator.

No Target Voltage and PS LED is Lit 1 This occurs if the target voltage is set to 0.0V. To fix this, set the target voltage to a value within the specified voltage range for the target device.

No Target Voltage and PS LED is Lit 2 This can be the issue if power jumper J100 and/or J101 is cut, and the target voltage regulator is set to a value within the specified voltage range for the target device. To fix this, solder a wire/bridge between the pads for J100/J101, or add a jumper on J101 if a pin header is mounted.

VBUS Output Voltage is Low or Not Present This is most lightly caused by a high-current drain on VBUS, and the protection fuse (PTC) will reduce the current or cut off completely. Reduce the current consumption on the VBUS pin to fix this issue.

3.4 Low Power Measurement Power to the ATtiny3217 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 ATtiny3217 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 ATtiny3217.

Figure 3-7. 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 no longer needed, place a jumper cap on the pin header.

Info: The on-board level shifters will draw a small amount of current even when they are not in use. A maximum of 2 µA can be drawn from each I/O pin connected to a level shifter for a total of 10 µA. Keep any I/O pin connected to a level shifter are tri-state to prevent leakage. All I/Os connected to the on-board debugger are listed in 4.2.4.1 On-Board Debugger Connections. To prevent any leakage to the on-board level shifters, they can be disconnected completely, as described in 7.4 Disconnecting the On-board Debugger.

3.5 Programming External Microcontrollers The on-board debugger on ATtiny3217 Curiosity Nano can be used to program and debug microcontrollers on external hardware.

3.5.1 Supported Devices All external AVR microcontrollers with the UPDI interface can be programmed and debugged with the on-board debugger with Atmel Studio. External SAM microcontrollers that have a Curiosity Nano Board can be programmed and debugged with the on- board debugger with Atmel Studio. ATtiny3217 Curiosity Nano can program and debug external ATtiny3217 microcontrollers with MPLAB X IDE.

3.5.2 Software Configuration No software configuration is required to program and debug the same device that is mounted on the board.

To program and debug a different microcontroller than what is mounted on the board, Atmel Studio must be configured to allow free selection of devices and programming interfaces. 1. Navigate to Tools > Options through the menu system at the top of the application. 2. Select the Tools > Tool settings category in the options window. 3. Set the Hide unsupported devices option to False . Figure 3-8. Hide Unsupported Devices

Info: Atmel Studio allows any microcontroller and interface to be selected when Hide unsupported devices is set to False, also microcontrollers and interfaces which are not supported by the on-board debugger.

3.5.3 Hardware Modifications The on-board debugger is connected to the ATtiny3217 by default. These connections must be removed before any external microcontroller can be programmed or debugged. Cut the GPIO straps shown in the figure below with a sharp tool to disconnect the ATtiny3217 from the on-board debugger.

Figure 3-9. Programming and Debugging Connections to Debugger GPIO straps (bottom side)

Info: Cutting the connections to the debugger will disable programming, debugging, and data streaming from the ATtiny3217 mounted on the board.

Tip: Solder in 0Ω resistors across the footprints or short-circuit them with solder to reconnect the signals between the on-board debugger and the ATtiny3217.

3.5.4 Connecting to External Microcontrollers The figure and table below show where the programming and debugging signals must be connected to program and debug external microcontrollers. The on-board debugger can supply power to the external hardware, or use an external voltage as a reference for its level shifters. Read more about the power supply in 3.3 Power Supply. The on-board debugger and level shifters actively drive data and clock signals (DBG0, DBG1, and DBG2) used for programming and debugging, and in most cases, the external resistor on these signals can be ignored. Pull-down resistors are required on the ICSP™ data and clock signals to debug PIC® microcontrollers. DBG3 is an open-drain connection and requires a pull-up resistor to function.

Remember: • Connect GND and VTG to the external microcontroller • Tie the VOFF pin to GND if the external hardware has its own power supply • Make sure there are pull-down resistors on the ICSP data and clock signals (DBG0 and DBG1) to support the debugging of PIC microcontrollers

Figure 3-10. Curiosity Nano Standard Pinout

USB

PS LED NC VBUS ID VOFF

CDC RX DEBUGGER DBG3 CDC TX DBG0 DBG1 GND

DBG2 CURIOSITY NANO VTG

Table 3-4. Programming and Debugging Interfaces

Curiosity Nano Pin UPDI ICSP™ SWD DBG0 UPDI DATA SWDIO DBG1 - CLK SWCLK DBG2 - - - DBG3 - #MCLR #RESET

3.6 Connecting External Debuggers Even though there is an on-board debugger, external debuggers can be connected directly to the ATtiny3217 Curiosity Nano to program/debug the ATtiny3217. The on-board debugger keeps all the pins connected to the ATtiny3217 and board edge in tri-state when not actively used. Therefore, the on-board debugger will not interfere with any external debug tools.

Figure 3-11. Connecting the MPLAB® PICkit™ 4 In-Circuit Debugger/Programmer to ATtiny3217 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 3-12. Connecting the Atmel-ICE to ATtiny3217 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 IDE or mass storage programming while the external tool is active.

4. Hardware User Guide

4.1 Connectors

4.1.1 ATtiny3217 Curiosity Nano Pinout All the ATtiny3217 I/O pins are accessible at the edge connectors on the board. The image below shows the board pinout. Figure 4-1. ATtiny3217 Curiosity Nano Pinout Analog Port ATtiny3217 Debug PWM I2C Power Curiosity Nano SPI Ground UART Touch USB Peripheral Shared pin VBUS

NC PS LED NC VBUS VOFF ID ID VOFF CDCRX DBG3

USART0 TXPB2 CDC RX DEBUGGER DBG3 (PA0) CDCTX DBG0 USART0 RXPB3 CDC TX DBG0 PA0 UPDI DBG1 GND PA3LED0 DBG1 GND DBG2 VTG PB7SW0 DBG2 DEBUGGER VTG PA1 USART0 TX PA1 ATtiny3217 PC5 PC5 ADC1 AIN11 PTC XY11 PA2 USART0 RX PA2 PC4 PC4 ADC1 AIN10 PTC XY10 PA4 PB1 PTC XY4 I2C0 SDA PB1 ATtiny3217 PA4 ADC0 AIN4 PTC XY0 TCA0 WO4 PTC XY5 I2C0 SCL PB0 PB0 PB4 PB4 ADC0 AIN9 PTC XY13 TCA0 WO1 PA5 PTC XY8 SPI0 MOSI PC2 PC2 PA5 ADC0 AIN5 PTC XY1 TCA0 WO5 PA6 PTC XY7 SPI0 MISO PC1 PC1 PA6 ADC0 AIN6 PTC XY2 PA7 PTC XY6 SPI0 SCK PC0 PC0 PA7 ADC0 AIN7 PTC XY3 PTC XY9 SPI0 SS PC3 PC3 PB5 PB5 ADC0 AIN8 PTC XY12 GND GND GND GND USART0 TX(TOSC2) PB2 PB2 LED0 PB6 PB6 PB3 PB7 USART0 RX(TOSC1) PB3 SW0 PB7 SW0

4.1.2 Using Pin Headers The edge connector footprint on ATtiny3217 Curiosity Nano has a staggered design where each hole is shifted 8 mil (~0.2 mm) off-center. The hole shift allows the use of regular 100 mil pin headers on the board without soldering. Once the pin headers are firmly in place, they can be used in normal applications like pin sockets and prototyping boards without any issues.

Tip: Start at one end of the pin header and gradually insert the header along the length of the board. Once all the pins are in place, use a flat surface to push them in.

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

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 ATtiny3217 Curiosity Nano Board that can be controlled by either GPIO or PWM. The LED can be activated by driving the connected I/O line to GND. Table 4-1. LED Connection

ATtiny3217 Pin Function Shared Functionality PA3 Yellow LED0 Edge connector, On-board debugger

4.2.2 Mechanical Switch The ATtiny3217 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 PB7.

Table 4-2. Mechanical Switch

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

4.2.3 Crystal The ATtiny3217 Curiosity Nano Board has a 32.768 kHz crystal footprint made for standard 3.2mm by 1.5mm surface mount crystals with two terminals. The crystal footprint is not connected to the ATtiny3217 by default, as the GPIOs are routed out to the edge connector. To use the crystal, some hardware modifications are required. The two I/O lines routed to the edge connector must be disconnected to reduce the chance of contention to the crystal, and to remove excessive capacitance on the lines. This can be done by cutting the two straps on the bottom side of the board, marked PB2 and PB3 as shown in the figure below. Next, short circuit each of the circular solder points next to the crystal on the top side of the board, the easiest way is to solder a solder tin blob across the footprint.

Figure 4-2. Crystal Connection and Cut Straps

A crystal with 7pF equivalent load capacitance and 70kΩ ESR (XC200) and one 10pF external matching capacitor (C203), and one 13pF external matching capacitor (C204) have been tested to yield good results on this board. See the 7.2 Assembly Drawing for footprint locations. Table 4-3. Crystal Connections

ATtiny3217 Pin Function Shared Functionality PB3 TOSC1 (input) Edge connector PB2 TOSC2 (output) Edge connector

4.2.4 On-Board Debugger Implementation ATtiny3217 Curiosity Nano features an on-board debugger that can be used to program and debug the ATtiny3217 using UPDI. The on-board debugger also includes a virtual serial port (CDC) interface over UART and debug GPIO. Atmel Studio/Microchip MPLAB® X IDE can be used as a front-end for the on-board debugger for programming and debugging. MPLAB Data Visualizer can be used as a front-end for the CDC and debug GPIO. 4.2.4.1 On-Board Debugger Connections The table below shows the connections between the target and the debugger section. All connections between the target and the debugger are tri-stated as long as the debugger is not actively using the interface. Hence, since there are little contaminations of the signals, the pins can be configured to anything the user wants. For further information on how to use the capabilities of the on-board debugger, see 3.1 On-Board Debugger Overview. Table 4-4. On-Board Debugger Connections

ATtiny3217 Pin Debugger Pin Function Shared Functionality PB3 CDC TX UART0 RX (ATtiny3217 RX line) Edge connector PB2 CDC RX UART0 TX (ATtiny3217 TX line) Edge connector PA0 DBG0 UPDI Edge connector PA3 DBG1 GPIO1 Edge connector PB7 DBG2 GPIO0 Edge connector

...... continued ATtiny3217 Pin Debugger Pin Function Shared Functionality (PA0) DBG3 RESET (J202 not connected by Edge connector default)

5. Hardware Revision History and Known Issues This user guide is written to provide information about the latest available revision of the board. The following sections contain information about known issues, a revision history of older revisions, and how older revisions differ from the latest revision.

5.1 Identifying Product ID and Revision The revision and product identifier of the ATtiny3217 Curiosity Nano Board can be found in two ways: Either by utilizing the Atmel Studio/Microchip MPLAB® X IDE Kit Window or by looking at the sticker on the bottom side of the PCB. By connecting ATtiny3217 Curiosity Nano to a computer with Atmel Studio/Microchip MPLAB® X IDE running, the Kit Window will pop up. The first six digits of the serial number, which is listed under kit information, contain the product identifier and revision.

Tip: The Kit Window can be opened in MPLAB® X IDE through the menu bar Window > Kit Window.

The same information can be found on the sticker on the bottom side of the PCB. Most boards will have the identifier and revision printed in plain text as A09-nnnn\rr, where “nnnn” is the identifier, and “rr” is the revision. Boards with limited space have a sticker with only a data matrix code, containing the product identifier, revision, and serial number. The serial number string has the following format:

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

The product identifier for ATtiny3217 Curiosity Nano is A09-3333.

5.2 Revision 2 Revision 2 is the initially released revision.

6. Document Revision History

Doc. rev. Date Comment A 03/2020 Initial document release.

7. Appendix

7.1 Schematic Figure 7-1. ATtiny3217 Curiosity Nano Schematic A B C D 2 of 4 of 2 27/11/2019 Altium.com Designed with Date: Page: 8 8 PA0_UPDI PC5_ADC1_AIN11 PC4_ADC1_AIN10 PA4_ADC0_AIN4 PB4_TCA0_WO1 PA5_TCA0_WO5 PA6_ADC0_AIN6 PB5_ADC0_AIN8 PB6 PA7_ADC0_AIN7 PB7_SW0 C Revision: PCB

J202 J204

DBG0

DBG3 VOFF GND VCC_EDGE GND 0-332 2 A09-3333 A08-3055 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 Number: PCB 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 ATtiny3217_Curiosity_Nano_Target_MCU.SchDoc CNANO34-pin edge connector edge CNANO34-pin 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 M.LOPER Engineer: PB / TF Project Title ATtiny3217Sheet Title Curiosity NanoATtiny3217 Curiosity Nano Size File: Drawn By: Drawn

NC NOTE on 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 GND DBG2 J201 J203 J205 J206 TX RX 6 6 UART PB2_USART0_TX PB3_USART0_RX PA3_LED0_TCA0_WO3 PB7_SW0 PA1_USART0_TX PA2_USART0_RX PB1_I2C0_SDA PB0_I2C0_SCL PC2_SPI0_MOSI PC1_SPI0_MISO PC0_SPI0_SCK PC3_SPI0_SS PB2_USART0_TX PB3_USART0_RX CDC_UART DBG0 DBG3 DBG1 DBG2 VOFF D_SYSI DEBUGGER DEBUGGER CONNECTIONS NOTE on UART/CDC: RX/TX on the header denotes the denotes header the on RX/TX signal the of direction input/output source. it's to respective the from output is TX CDC DEBUGGER. DEBUGGER. the to input is RX CDC TX is output from the TARGET device. RX is input to the TARGET device. PB3 PB2 PA0 PA3 PB7 - 5 5 ATtiny3217 aePin Name USART0 RX USART0 TX UPDI GPIO1 GPIO0 NA Debugger CDC TX CDC RX DBG0 DBG1 DBG2 1.8V - 5.5V DBG3 VTG Crystal datasheet: Crystal 7pF = Ccrystal 70kOhm = ESR max ±20ppm Accuracy ATtiny3217 datasheet: 5.5pF = Cxin 5.5pF = Cxout 2.75pF ≈ ) (1/5.5pF) (1/5.5pF)+ 1/( ≈ Cl 40kOhm = 12.5pF @ ESR Maximum 80kOhm = 7.5pF @ ESR Maximum 0.5pF = Cpcb Estimated load Estimated Cpcb) - Cpara (Ccrystal- 2 = C 0.5pF) - 2.75pF - (7pF 2 = C 7.5pF = C verification after design in Selected 10/13pF C= PC1_SPI0_MISO PC0_SPI0_SCK PB0_I2C0_SCL PB1_I2C0_SDA PB2_USART0_TX PB3_USART0_RX PB2_TOSC2 PB3_TOSC1 C204 13pF J211

J212 J213 PB2_TOSC2 N.M GND 4 4 J209 GND N.M 14 13 18 17 16 15 25 XC200 32.768kHz C203 10p

J210 32kHz CRYSTAL PC1 PC0 PB0 PB1 PAD PB3_TOSC1 N.M GND

ATtiny3217-MFR

PC2 PB4

PC2_SPI0_MOSI PB4_TCA0_WO1 19 12

PC3

TOSC2)( PB2 TOSC1)( PB3 PB5 PB5_ADC0_AIN8 PC3_SPI0_SS 20 11

PC4 PB6

PC4_ADC1_AIN10 PB6 21 10

PC5 PB7

PC5_ADC1_AIN11 PB7_SW0 22 9

PI/RST PA0 RESET) / UPDI ( PA7

PA7_ADC0_AIN7 PA0_UPDI 23 8

PA1

PA6 2.2uF C205 PA1_USART0_TX PA6_ADC0_AIN6 24 7 3 3 GND VCC_EDGE PA2 ) CLKI PA3( GND VCC PA4 PA5 TARGET BULK TARGET U200

ATtiny3217

1 2 3 4 5 6

PA3_LED0_TCA0_WO3

SML-D12Y1WT86

ELWLED YELLOW

2 1

R203

PA2_USART0_RX PA3_LED0_TCA0_WO3 PA4_ADC0_AIN4 PA5_TCA0_WO5 D200 VCC_TARGET USER LED 2 2 C200 100n L200 BLM18PG471SN1 GND

VCC_TARGET

PB7_SW0 4 2

R202

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

© 2020 Microchip Technology Inc. User Guide DS40002193A-page 30 ATtiny3217 Appendix A B C D 3 of 4 of 3 27/11/2019 Altium.com Designed with Date: Page: 8 8 UARTRX UART TX - UPDI UPDI GPIO GPIO RESET D_SYSI VCC_P3V3 C101 2.2uF VBUS D- D+ D I GND SHI ELD1 SHI ELD2 SHI ELD3 SHI ELD4 J105 VCC_P3V3 GND MU-MB0142AB2-269 1 2 3 4 5 6 7 8 9 C Revision: PCB 2 DAT CLK GPIO MCLR AGTTARGET TARGET UARTRX UART TX PTC Resettable fuse: Resettable PTC 500mA current: Hold Trip 1000mA current: ICSP 5 1 2

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

SHIELD 1k

NC R112

GND

EP 2 2 A09-3333 A08-3055 VOUT VOUT Interface USBD_N USBD_P 7 D100 LED GREEN VCC_P3V3 SML-P12MTT86R CDC TX CDC RX - VCC Signal DBG0 DBG1 DBG2 DBG3

1 VCC_VBUS

GND GND MIC5528-3.3YMT 3 IN VI EN 7 7 ID_SYS U101 F100 MC36213 6 4 1k R107 C sebyNme:PCBA Revision: PCB Number: Assembly Number: PCB GND VBUS VCC_VBUS C100 4.7uF A3 ATtiny3217_Curiosity_Nano_Debugger.SchDoc M.LOPER Engineer: PB / TF Project Title ATtiny3217Sheet Title Curiosity NanoDebugger Size File: Drawn By: Drawn DEBUGGER REGULATOR DEBUGGER POWER/STATUS LED DEBUGGER USB MICRO-B CONNECTOR ID PIN 6 6 GND SRST USBD_P USBD_N ID_SYS CDC_TX_CTRL VOFF CDC_RX_CTRL VTG_EN DBG3_CTRL TP101 GND 22 21 20 19 18 17 24 23 33 STATUS_LED TP100 GND VCC_P3V3 PAD PA22 PA19 PA18 PA17 PA16 U100 SAMD21E18A-MUT

2 4 6 8 10

PA27

BOOT PA15 DBG1_CTRL 25 16

RESETN PA14

SRST DBG0_CTRL

26 15

USB_DP/ PA25 USB_DM/ PA24 PA28 PA11

USB_SOF/ PA23 VBUS_ADC 27 14

GND GND PA10 SRST

VTref TRST REG_ENABLE 28 13

VDDCORE

GND PA09

DBG2_GPIO 29 12

DIN VDDI PA08

DBG2_CTRL

TCK TDO TMS GND Vsup TDI 11

WCK PA30 SWDCLK/

J102 GND Testpoint Array 31 10

WIO PA31 O/ SWDI VDDANA

32 1 3 5 7 9 9 5 5 VCC_P3V3 100n C108 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 Programming of programming factory for Debugger GND DEBUGGER DEBUGGER TESTPOINTs S0_0_RX 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 using an measurements - For current 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: to the target microcontroller andthe the LED / Button. To use pin-header a mount and holes, the between track the Cut - MIC5353: Vin:6V to 2.6V Vout:5.1V to 1.25V 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 = (Vmax Vin dropout) - S1_0_TX S1_1_RX DAC VTG_ADC RESERVED S0_2_TX S0_3_CLK VCC_P3V3 1k the R113 pull to required is defined a to gate Q101 not is U100 the when value powered J101 R108 VCC_EDGE VCC_TARGET 4 4 J100 VCC_P3V3 GND VCC_P3V3 GND VCC_P3V3 GND VCC_P3V3 GND VCC_P3V3 GND DBG3_CTRL 47k 2 2 2 2 2 1 1 1 1 1 3 3 3 3 3 R113 Q101 DMN65D8LFB VCC_LEVEL 1 GND A1 B1 C1 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 VCCB R DI B VCCB R DI B VCCB R DI B VCCB R DI B VCCB R DI B U103 U104 U105 U106 U107 6 5 4 6 5 4 6 5 4 6 5 4 6 5 4 IN VI N VI EN U108 MIC94163 VTG_ADC DAC

A2 B2 C2 47k R110 R111

GND

3 3 VTG_EN VCC_LEVEL VCC_LEVEL VCC_LEVEL VCC_LEVEL VCC_LEVEL

DBG3 OPEN DRAIN

47k 47k

R102 R105 GND GND 33k CDC_TX_CTRL CDC_RX_CTRL DBG0_CTRL DBG1_CTRL DBG2_CTRL

R106

C103 2.2uF

47k 27k

R101 R104

GND REG_ADJUST 5 2 4 VCC_REGULATOR GND VOUT

NC/ ADJ MIC5353U102 7 2 2 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 - The 5.25V to 4.40V between vary can which (USB), input the by limited is output voltage The - the for allowed voltage operating minimum the limit will and 1.65V of level voltage a minimal have shifters level - The communication. target allow still to target. the to delivered voltage minimum the limit will and 1.70V of level volatege minimal a has MIC94163 - The specification. target the the within be to range voltage the limit will configuration Firmware - IN VI EN BYP 3 1 6 C102 100n

GND

47k R103 TX RX

REG_ENABLE

VBUS_ADC

UART

47k 47k

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

7.2 Assembly Drawing Figure 7-2. ATtiny3217 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 PAJ21101 PAJ21102 PAJ20901COJ209 PAJ20902 PAU10104 PAU10105 PAU10106 PAC10101 PAR10102 PAR10402 COJ101 PAJ21105COJ211 COU102 PAU1080B2 PAU1080B1 COF100 PAR11001COR110 PAR11002 PAU10202 PAU10207 PAU10205 COR101 COR104 COU108 PAC20502COC205 PAJ10101 COJ212PAJ21201 PAC20401 PAJ10506 PAF10002 PAU10203 PAU10204 PAR10101 PAR10401 PAU1080A2 PAU1080A1 PAJ10102 PAJ21202 PAXC20001 PAQ10103 PAQ10102 PAR10002 PAR10902 COC204PAC20402 COQ101PAQ10100PAQ10101 PAC10301COC103PAC10302 COJ202PAJ20201 PAR10001COR100 PAR10901COR109 PAU10701 PAU10706 PAJ20202 PAU200019 PAU200018 COJ213PAJ21302PAJ21301 PAC20301 PASW20003 PASW20001 PAJ10508 PAU10700PAU10702 PAU10705 COXC200 PAJ105010 PAR11301COR113 PAR11302 COU107 PAU200020 PAU200017 PAJ10501 PAC10802 PAU10703PAU10704 COJ206PAJ20601 PAU200021 PAU200016 PAJ20602 PAU200022 PAU200015 PAJ21001PAJ21005 PAJ21002 COC203PAC20302 PAXC20002 PAJ10201 PAJ10502PAJ10203 PAJ10205 PAR11102COR111 PAR11101 COC108 PAU10601 PAU10606 PAU200023 PAU200014 COJ210 PAD20001 PAR20302 PAR20201 PAU10602PAU10605 COJ102 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 PAR20202 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 PASW20004 PASW20002 PAU100024 PAU10001 PAR10501 COU104PAU10400PAU10402 PAU10405 COJ203PAJ20301 PAU10403 PAU10404 PAJ20302 PAJ10507 COTP100PATP10001PAU100025 PAU100026 PAU100027 PAU100028 PAU100029 PAU100030 PAU100031 PAU100032 COL200PAL20002 PAL20001 PAU10301 PAU10306 PAU10300PAU10302 PAU10305 C COU103 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. ATtiny3217 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 COJ209 PAJ20902 PAJ20901 COJ209 PAJ21102 PAJ21101 PAC20501 PAU1080C1 PAU1080C2 PAU10206 PAU10201 COC101 COU101 PAJ21105 COJ211 PAJ21105 COJ101 PAR10402 PAR10102 PAC10101 PAU10106 PAU10105 PAU10104 PAU1080B1 PAU1080B1 PAU1080B2 COU102 PAC20401 PAC20401 PAJ21201 COJ212 PAJ10101 PAC20502 COC205 COU108 COR104 COR101 PAU10205 PAU10207 PAU10202 PAR11002 PAR11001 COR110 COF100 PAXC20001 PAXC20001 PAJ21202 PAJ10102 PAU1080A1 PAU1080A2 PAR10401 PAR10101 PAU10204 PAU10203 PAF10002 PAJ10506 PAC20402 PAC20402 COC204 PAR10902 PAR10002 PAQ10102 PAQ10103 COJ202 PAJ20201 COJ202 PAC10302 PAC10301 COC103 PAQ10100 PAQ10101 COQ101 PASW20001 PASW20001 PASW20003 PAC20301 PAJ21301 COJ213 PAJ21302 PAU200018 PAU200019 PAJ20202 PAU10706 PAU10701 PAR10901 COR109 PAR10001 COR100 COXC200 COXC200 PAU10705 PAU10700 PAU10702 PAJ10508 PAU200017 PAU200017 PAU200020 COU107 PAR11302 PAR11301 COR113 PAJ105010 PAU200016 PAU200016 PAU200021 PAJ20601 COJ206 PAU10704 PAU10703 PAC10802 PAJ10501 PAXC20002 PAXC20002 PAC20302 COC203 PAJ21002 PAJ21001 PAJ21005 PAU200015 PAU200022 PAJ20602 PAR20201 PAR20201 PAR20302 PAD20001 COJ210 PAU200014 PAU200023 PAU10606 PAU10601 COC108 PAR11101 PAR11102 COR111 PAJ10205 PAJ10502 PAJ10203 PAJ10201 PAU200013 PAU200013 PAU200024 PAU10605 PAU10600 PAU10602 COU106 PAC10801 PAU10009 PAU100010 PAU100011 PAU100012 PAU100013 PAU100014 PAU100015 PAU100016 COJ205 PAJ20501 COJ205 PAU10604 PAU10603 PAJ10503 COJ102 COR202 COR202 COR203 COD200 PAU20000 COU200 PAJ20502 PAU10008 PAU100017 COJ105 PAR20202 PAR20202 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 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 PAU10406 PAU10401 COR105 PAU10002 PAU100023 PATP10101 COJ203 PAJ20301 COJ203 PAU10405 PAU10400 PAU10402 COU104 PAR10501 PAU10001 PAU100024 PAJ20302 PAJ20302 PAU10404 PAU10403 t R PAL20001 COL200 PAL20002 PAU100032 PAU100031 PAU100030 PAU100029 PAU100028 PAU100027 PAU100026 PAU100025 PATP10001 COTP100 PAJ10507 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. ATtiny3217 Curiosity Nano Pinout Mapping PA4 PA2 PA1 PB6 3 EXT1 2 1 920 19 DGND ID A PA6 PA4 PB0 PA7 PB2 PC2 PB4 PC0 +3.3V PB1 PB3 PB7 PC1 GND NPWM INT RX TX SCL AN SDA RST +5V CS GND SCK MISO MOSI +3.3V GND Xplained Pro Extension TM PA6 PB6 PC0 C PB0 PB1 PC1 PC2 N GND GND 33 +5V +3.3V PA5 PA2 PA1 PB4 PB3 PB2 for click boards Curiosity Nano Base 1 2 N GND GND NPWM INT RX TX SCL AN SDA RST +5V CS SCK MISO MOSI +3.3V N GND GND NPWM INT RX TX SCL AN SDA RST +5V CS SCK MISO MOSI +3.3V C PC4 PB0 PB1 PB5 PC5 PC3 PC0 PC1 PC2 N GND PB0 PB1 GND GND PA7 PB7 PC0 PC1 PC2 GND 33 +5V +3.3V 33 +5V +3.3V TCA0 WO4 TCA0 WO1 TCA0 WO5 UPDI Port PWM Power Ground Touch Shared pin PA0 SW0 (PA0) D0AN PTC XY0 PTC XY13 ADC0 AIN4 PTC XY1 ADC0 AIN9 PTC XY2 ADC0 AIN5 PTC XY3 ADC0 AIN6 PTC XY12 ADC0 AIN7 ADC0 AIN8 D1AN1PTC XY11 PTC XY10 ADC1 AIN11 ADC1 AIN10 GND PB4 PA5 PA6 PC4 PA4 PA7 PB5 GND VTG PC5 PB6 PB7 Analog Debug I2C SPI UART Peripheral VOFF DBG3 DBG0 VBUS

VBUS DBG3 GND PC5 PA4 PA5 PA7 GND PB7 VOFF DBG0 VTG PC4 PB4 PA6 PB5 PB6 USB SW0 ATtiny3217 LED0 ATtiny3217 DEBUGGER DEBUGGER PS LED PS ID CDCTX DBG2 PA2 PB0 PC1 PC3 PB2 NC CDCRX DBG1 PA1 PB1 PC2 PC0 GND PB3 NC ID GND PC1 PC0 PA1 PA2 PB1 PB0 PC2 PC3 PB2 PB3 DBG1 DBG2 CDC RX CDC TX Curiosity Nano PA3LED0PB7SW0 SPI0 SS ATtiny3217 I2C0 SDA I2C0 SCL SPI0 SCK USART0 TXPB2USART0 RXPB3USART0 TX USART0 RX SPI0 MOSI SPI0 MISO USART0 TX(TOSC2)USART0 RX(TOSC1) PTC XY8 PTC XY7 PTC XY9 PTC XY4 PTC XY5 PTC XY6

7.4 Disconnecting the On-board Debugger The on-board debugger and level shifters can be completely disconnected from the ATtiny3217. The block diagram below shows all connections between the debugger and the ATtiny3217. The rounded boxes represent connections to the board edge. The signal names shown are also printed in silkscreen on the bottom side of the board. To disconnect the debugger, cut the straps shown in Figure 7-6.

Attention: Cutting the GPIO straps to the on-board debugger will disable the virtual serial port, programming, debugging, and data streaming. Cutting the power supply strap will disconnect the on-board power supply.

Tip: Any connection that is cut can be reconnected using solder, alternatively, a 0Ω 0402 resistor can be mounted.

Tip: When the debugger is disconnected, an external debugger can be connected to holes shown in Figure 7-6. Details about connecting an external debugger are described in 3.6 Connecting External Debuggers.

Figure 7-5. On-Board Debugger Connections Block Diagram 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 UART RX

DEBUGGER PA01 CDC RX UART TX DIR x 5

CDC RX DBG0 CDC TX DBG1 DBG2 DBG3

Figure 7-6. On-Board Debugger Connection Cut Straps

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

7.5 Getting Started with IAR IAR Embedded Workbench® for AVR® is a proprietary high-efficiency compiler not based on GCC. Programming and debugging of ATtiny3217 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. © 2020, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved. ISBN: 978-1-5224-5817-3

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-4485-5910 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

Authorized Distributor

Click to View Pricing, Inventory, Delivery & Lifecycle Information:

Microchip : EV50J96A