MICROCHIP ATTINY1627 (01) PDF MANUAL


Post questions, comments, reviews or errors in the comment box below.

Your File is Ready … Download PDF

CLICK HERE TO DOWNLOAD MICROCHIP ATTINY1627 (01) PDF MANUAL


PDF Content Summary: • MPLAB® X IDE and Atmel Studio - Software to discover, configure, develop, program, and debug Microchip microcontrollers. • ATtiny1627 website - Find documentation, sample, and purchase microcontrollers. • ATtiny1627 Curiosity Nano website - Kit information, latest user guide and design documentation. • Code examples on GitHub - Get started with code examples. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 1 ATtiny1627 ATtiny1627 Curiosity Nano Hardware User Guide Preface The ATtiny1627 Curiosity Nano Evaluation Kit is a hardware platform to evaluate microcontrollers in the tinyAVR® 2- series. This board has the ATtiny1627 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 ATtiny1627 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 ATtiny1627. ATtiny1627 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...........................................................................................10 3.1.3. Mass Storage Device...................................................................................................10 3.1.3.1. Mass Storage Device Implementation.......................................................11 3.1.3.2. Fuse Bytes.................................................................................................11 3.1.3.3. Limitations of Drag-and-Drop Programming..............................................11 3.1.3.4. Special Commands................................................................................... 12 3.1.4. Data Gateway Interface (DGI).....................................................................................12 3.1.4.1. Debug GPIO..............................................................................................12 3.1.4.2. Timestamping............................................................................................13 3.2. Curiosity Nano Standard Pinout.................................................................................................13 3.3. Power Supply.............................................................................................................................14 3.3.1. Target Regulator..........................................................................................................15 3.3.2. External Supply............................................................................................................16 3.3.3. VBUS Output Pin.........................................................................................................16 3.3.4. Power Supply Exceptions............................................................................................17 3.4. Low Power Measurement...........................................................................................................18 3.5. Programming External Microcontrollers..................................................................................... 19 3.5.1. Supported Devices...................................................................................................... 19 3.5.2. Software Configuration................................................................................................19 3.5.3. Hardware Modifications...............................................................................................20 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. ATtiny1627 Curiosity Nano Pinout...............................................................................24 4.1.2. Using Pin Headers.......................................................................................................24 4.2. Peripherals.................................................................................................................................25 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 2 ATtiny1627 4.2.1. LED..............................................................................................................................25 4.2.2. Mechanical Switch.......................................................................................................25 4.2.3. Crystal..........................................................................................................................25 4.2.4. On-Board Debugger Implementation...........................................................................26 4.2.4.1. On-Board Debugger Connections.............................................................26 5. Hardware Revision History and Known Issues..................................................................................... 27 5.1. Identifying Product ID and Revision...........................................................................................27 5.2. Revision 3...................................................................................................................................27 5.3. Revision 2...................................................................................................................................27 6. Document Revision History...................................................................................................................28 7. Appendix............................................................................................................................................... 29 7.1. Schematic...................................................................................................................................29 7.2. Assembly Drawing......................................................................................................................31 7.3. Curiosity Nano Base for Click boardsTM...................................................................................... 32 7.4. Disconnecting the On-board Debugger......................................................................................33 7.5. Getting Started with IAR.............................................................................................................34 The Microchip Website.................................................................................................................................37 Product Change Notification Service............................................................................................................37 Customer Support........................................................................................................................................ 37 Microchip Devices Code Protection Feature................................................................................................37 Legal Notice................................................................................................................................................. 37 Trademarks.................................................................................................................................................. 38 Quality Management System....................................................................................................................... 38 Worldwide Sales and Service.......................................................................................................................39 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 3 ATtiny1627 Introduction 1. Introduction 1.1 Features • ATtiny1627 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.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 ATtiny1627 Curiosity Nano Evaluation Kit is a hardware platform to evaluate the ATtiny1627 microcontroller. Figure 1-1. ATtiny1627 Curiosity Nano Evaluation Kit Overview Micro USB Power/Status Connector LED Debugger ATtiny1627 32.768 kHz MCU Crystal footprint User LED (LED0) © 2020 Microchip Technology Inc. User Guide DS40002199A-page 4 User Switch (SW0) ATtiny1627 Getting Started 2. Getting Started 2.1 Quick Start Steps to start exploring the ATtiny1627 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 ATtiny1627 device on the ATtiny1627 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 ATtiny1627 Curiosity Nano Board: • MPLAB® X IDE - MPLAB X IDE is a software program that runs on a PC (Windows®, Mac OS®, Linux®) to develop applications for Microchip microcontrollers and digital signal controllers. It is called an Integrated Development Environment (IDE) because it provides a single integrated “environment” to develop code for embedded microcontrollers. • Atmel Studio - Free IDE for the development of C/C++ and assembler code for microcontrollers. • IAR Embedded Workbench® for AVR® - This is a commercial C/C++ compiler that is available for AVR microcontrollers. There is a 30-day evaluation version as well as a 4 KB code-size-limited kick-start version available from their website. • MPLAB® Code Configurator - MPLAB Code Configurator (MCC) is a free software plug-in that provides a graphical interface to configure peripherals and functions specific to your application. • Atmel START - Atmel START is an online tool that hosts code examples, helps the user to select and configure software components, and tailor your embedded application in a usable and optimized manner. • Microchip Sample Store - Microchip sample store where you can order samples of devices. • MPLAB Data Visualizer - MPLAB Data Visualizer is a program used for processing and visualizing data. The Data Visualizer can receive data from various sources such as serial ports and on-board debugger’s Data Gateway Interface, as found on Curiosity Nano and Xplained Pro boards. • 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 5 ATtiny1627 Getting Started • 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. • ATtiny1627 Curiosity Nano website - Kit information, latest user guide and design documentation. • ATtiny1627 Curiosity Nano on Microchip Direct - Purchase this kit on Microchip Direct. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 6 ATtiny1627 Curiosity Nano 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 ATtiny1627 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 ATtiny1627 in Atmel Studio/Microchip MPLAB® X IDE • A mass storage device that allows drag-and-drop programming of the ATtiny1627 • A virtual serial port (CDC) that is connected to a Universal Asynchronous Receiver/Transmitter (UART) on the ATtiny1627, 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 ATtiny1627 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 programming Success: The LED blinks slowly for 2 sec. Failure: The LED blinks rapidly for 2 sec. Fault The LED blinks rapidly if a power fault is detected Sleep/Off The LED is OFF. The on-board debugger is either in a sleep mode or powered down. This can occur if the board is externally powered. Info: Slow blinking is approximately 1 Hz, and rapid blinking is approximately 5 Hz. 3.1.1 Debugger The on-board debugger on the ATtiny1627 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 ATtiny1627 using Atmel Studio/Microchip MPLAB® X IDE, as well as some third-party IDEs. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 7 ATtiny1627 Curiosity Nano 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 Terminal Software Send USB CDC TX CDC RX © 2020 Microchip Technology Inc. User Guide DS40002199A-page 8 Receive Target UART RX Terminal UART TX 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#. ATtiny1627 Curiosity Nano 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 DTR in debugger firmware version 1.20 or earlier has the following behaviour: • Debugger UART receiver is disabled, so no further data will be transferred to the host computer • Debugger UART transmitter will continue to send data that is queued for sending, but no new data is accepted from the host computer • Level shifters (if available) are not disabled, so the debugger CDC TX line remains driven. Deasserting DTR in debugger firmware version 1.21 or later has the following behaviour: • Debugger UART receiver is disabled, so no further data will be transferred to the host computer • Debugger UART transmitter will continue to send data that is queued for sending, but no new data is accepted from the host computer • Once the ongoing transmission is complete, level shifters (if available) are disabled so the debugger CDC TX line will become high-impedence. 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 9 ATtiny1627 Curiosity Nano 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= Debugger firmware version 1.20 or earlier has the following limitations: • The maximum message length is 50 characters – all remaining data in the frame are ignored. • The default baud rate used in this mode is 9600 bps, but if the CDC is already active or has been configured, the previously used baud rate still applies. Debugger firmware version 1.21 and later has the following limitations/features: • The maximum message length may vary depending on MSC/SCSI layer timeouts on the host computer and/or operating system. A single SCSI frame of 512b (498 characters of payload) is guaranteed, and files of up to 4k will work on most systems. The transfer will complete on the first NULL character encountered in the file. • The baud rate used is always 9600 bps for the default command CMD:SEND_UART= CDC Override Mode should not be used simultaneously with data transfer over CDC / terminal. If a CDC terminal session is active at the time a file is received via CDC Override Mode, it will be suspended for the duration of the operation and resumed once complete. • Additional commands are supported with explicit baud rates: CMD:SEND_9600= CMD:SEND_115200= CMD:SEND_460800= USB-Level Framing Considerations Sending data from the host to the CDC can be done byte-wise or in blocks, which will be chunked into 64-byte USB frames. Each such frame will be queued up for sending to the debugger’s CDC TX pin. Transferring a small amount of data per frame can be inefficient, particularly at low baud rates, 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 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 10 ATtiny1627 Curiosity Nano • 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 is because a subsequent chip erase (which does not affect fuse bits) will effect a CRC mismatch, and the application will fail to boot. To recover a target from this state, a chip erase must be done using Atmel Studio/Microchip MPLAB® X IDE, which will automatically clear the CRC fuses after erasing. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 11 ATtiny1627 Curiosity Nano 3.1.3.4 Special Commands Several utility commands are supported by copying text files to the mass storage disk. The filename or extension is irrelevant – the command handler reacts to content only. Table 3-2. Special File Commands Command Content Description CMD:ERASE Executes a chip erase of the target CMD:SEND_UART= Sends a string of characters to the CDC UART. See “CDC Override Mode”.

CMD:SEND_9600=CMD:SEND_115200=CMD:SE ND_460800= Sends a string of characters to the CDC UART at the baud rate specified. Note that only the baud rates explicitly specified here are supported! See “CDC Override Mode” (Debugger firmware v1.21 or newer.)

© 2020 Microchip Technology Inc. User Guide DS40002199A-page 12 CMD:RESET Resets the target device by entering Programming mode and then exiting Programming mode immediately thereafter. Exact timing can vary according to the programming interface of the target device. (Debugger firmware v1.16 or newer.) CMD:POWERTOGGLE Powers down the target and restores power after a 100 ms delay. If external power is provided, this has no effect. (Debugger firmware v1.16 or newer.) CMD:0V Powers down the target device by disabling the target supply regulator. If external power is provided, this has no effect. (Debugger firmware v1.16 or newer.) CMD:1V8 Sets the target voltage to 1.8V. If external power is provided, this has no effect. (Debugger firmware v1.21 or newer.) CMD:3V3 Sets the target voltage to 3.3V. If external power is provided, this has no effect. (Debugger firmware v1.16 or newer.) CMD:5V0 Sets the target voltage to 5.0V. If external power is provided, this has no effect. (Debugger firmware v1.16 or newer.) Info: The commands listed here are triggered by the content being sent to the mass storage emulated disk, and no feedback is provided in the case of either success or failure. 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 ATtiny1627 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. ATtiny1627 Curiosity Nano 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 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 13 VTG ATtiny1627 Curiosity Nano ...........continued Debugger Signal Target MCU Description 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 NCPS LED 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 ATtiny1627 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 ATtiny1627 Curiosity Nano. Figure 3-4. Power Supply Block Diagram Target VREG Regulator VLVL Power Supply Target Power strap strap Measure On/Off USB Adjust I/O Level I/O GPIO shifter straps #VOFF ID system © 2020 Microchip Technology Inc. User Guide DS40002199A-page 14 Target MCU Power source Cut strap VUSB On/Off Power consumer P3V3 DEBUGGER I/O Power converter DEBUGGER PTC Regulator Fuse Power protection VBUS ATtiny1627 Curiosity Nano 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 ATtiny1627 microcontroller. The voltage limits configured in the on-board debugger on ATtiny1627 Curiosity Nano are 1.8-5.1V. 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 15 ATtiny1627 Curiosity Nano 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 ATtiny1627 Curiosity Nano can be powered by an external voltage instead of the on-board target regulator. When the Voltage Off (VOFF) pin is shorted to ground (GND), the on-board debugger firmware disables the target regulator, and it is safe to apply an external voltage to the VTG pin. It is also safe to apply an external voltage to the VTG pin when no USB cable is plugged into the DEBUG connector on the board. The VOFF pin can be tied low/let go at any time. This will be detected by a pin-change interrupt to the on-board debugger, which controls the target voltage regulator accordingly. WARNING Applying an external voltage to the VTG pin without shorting VOFF to GND may cause permanent damage to the board. WARNING Do not apply any voltage to the VOFF pin. Let the pin float to enable the power supply. WARNING Absolute maximum external voltage is 5.5V for the on-board level shifters, and the standard operating condition of the ATtiny1627 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 ATtiny1627 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 ATtiny1627 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 16 ATtiny1627 Curiosity Nano 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 4.4V-5.25V), and the voltage drop over the MIC5353 regulator at a given voltage setting and current consumption. If a higher output voltage is needed, use a USB power source that can provide a higher input voltage or use an external voltage supply on the VTG pin. Target Voltage is Different From Setting This can be caused by an externally applied voltage to the VTG pin, without setting the VOFF pin low. If the target voltage differs more than 100 mV over/under the voltage setting, it will be detected by the on-board debugger, and the internal voltage regulator will be shut down. To fix this issue, remove the applied voltage from the VTG pin, and the on-board debugger will enable the on-board voltage regulator when the new condition is detected. Note that the PS LED will be blinking rapidly if the target voltage is below 100 mV of the setting, but will be lit normally when it is higher than 100 mV above the setting. No, Or Very Low Target Voltage, and PS LED is Blinking Rapidly This can be caused by a full or partial short-circuit and is a special case of the issue mentioned above. Remove the short-circuit, and the on-board debugger will re-enable the on-board target voltage regulator. 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 17 ATtiny1627 Curiosity Nano 3.4 Low Power Measurement Power to the ATtiny1627 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 ATtiny1627 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 ATtiny1627. 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 in 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 18 ATtiny1627 Curiosity Nano 3.5 Programming External Microcontrollers The on-board debugger on ATtiny1627 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. ATtiny1627 Curiosity Nano can program and debug external ATtiny1627 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 19 ATtiny1627 Curiosity Nano 3.5.3 Hardware Modifications The on-board debugger is connected to the ATtiny1627 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 ATtiny1627 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 ATtiny1627 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 ATtiny1627. 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 ICSPTM 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 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 20 ATtiny1627 Curiosity Nano Figure 3-10. Curiosity Nano Standard Pinout USB NCPS LED ID CDC RX DEBUGGER CDC TX DBG1 DBG2 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 21 VBUS VOFF DBG3 DBG0 GND CURIOSITY NANO VTG Table 3-4. Programming and Debugging Interfaces Curiosity Nano Pin UPDI ICSPTM 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 ATtiny1627 Curiosity Nano to program/debug the ATtiny1627. The on-board debugger keeps all the pins connected to the ATtiny1627 and board edge in tri-state when not actively used. Therefore, the on-board debugger will not interfere with any external debug tools. ATtiny1627 Curiosity Nano Figure 3-11. Connecting the MPLAB® PICkitTM 4 In-Circuit Debugger/Programmer to ATtiny1627 Curiosity Nano 1 = Unused MPLAB® PICkitTM 4 2 = VDD 3 = Ground 4 = PGD 5 = Unused 6 = Unused 7 = Unused 8 = Unused 2345678 1 VDD Ground DATAUSB NCPS LED ID CDC RX DEBUGGER CDC TX DBG1 DBG2 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 22 VBUS VOFF DBG3 DBG0 GND CURIOSITY NANO VTG ATtiny1627 Curiosity Nano Figure 3-12. Connecting the Atmel-ICE to ATtiny1627 Curiosity NanoSAM AVR® Atmel-ICE Ground 1 = Unused 6 = Unused VDD 2 = GND 7 = Unused 3 = UPDI 8 = Unused 210 4 = VTG 9 = Unused 1 95 = Unused 10 = Unused DATA USB NCPS LED ID CDC RX DEBUGGER CDC TX DBG1 DBG2 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 23 VBUS VOFF DBG3 DBG0 GND CURIOSITY NANO VTG CAUTION To programming/debug avoid contention between operation the with external the on-board debugger debugger and the through on-board Atmel debugger, Studio/Microchip do not start MPLABany ® X IDE or mass storage programming while the external tool is active. ATtiny1627 Hardware User Guide 4. Hardware User Guide 4.1 Connectors 4.1.1 ATtiny1627 Curiosity Nano Pinout All the ATtiny1627 I/O pins are accessible at the edge connectors on the board. The image below shows the board pinout. For all available functions on each pin, refer to the I/O Multiplexing and Considerations section in the ATtiny1627 data sheet. Figure 4-1. ATtiny1627 Curiosity Nano Pinout ATtiny1627 Analog Port Debug PWM Curiosity Nano I2C Power SPI Ground USB UART Shared pin Peripheral NCPS LED VBUS ID VOFF PB2 USART0 TX CDC RX DEBUGGER DBG3 PB3 USART0 RX CDC TX DBG0 PA0 UPDI LED0 PB7 DBG1 GND SW0 PC4 DBG2 DEBUGGER VTG USART[0/1] TX PA1 ATtiny1627 PB6 USART[0/1] RX PA2 PB5 AIN8 TWI0 SDA PB1 ATtiny1627 PB4 AIN9 TCA0 WO1 TWI0 SCL PB0 PA3 AIN3 TCA0 WO3 SPI0 MOSI PC2 PA4 AIN4 TCA0 WO4 SPI0 MISO PC1 PA5 AIN5 SPI0 SCK PC0 PA6 AIN6 SPI0 SS PC3 PA7 AIN7 GND GND (TOSC2) USART0 TX PB2 LED0 PC5 (TOSC1) USART0 RX PB3 SW0 PC4 SW0 4.1.2 Using Pin Headers The edge connector footprint on ATtiny1627 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 24 ATtiny1627 Hardware User Guide 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 ATtiny1627 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 ATtiny1627 Pin Function Shared Functionality PB7 Yellow LED0 Edge connector, On-board debugger 4.2.2 Mechanical Switch The ATtiny1627 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 ATtiny1627 Pin Description Shared Functionality PC4 User switch (SW0) Edge connector, On-board debugger 4.2.3 Crystal The ATtiny1627 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 ATtiny1627 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 25 ATtiny1627 Hardware User Guide Figure 4-2. Crystal Connection and Cut Straps A crystal with 7pF equivalent load capacitance and 70kΩ ESR (XC200) and two 4.7pF external matching capacitors for C203 and 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 ATtiny1627 Pin Function Shared Functionality PB3 TOSC1 (input) Edge connector PB2 TOSC2 (output) Edge connector 4.2.4 On-Board Debugger Implementation ATtiny1627 Curiosity Nano features an on-board debugger that can be used to program and debug the ATtiny1627 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 ATtiny1627 Pin Debugger Pin Function Shared Functionality PB3 CDC TX UART RX (ATtiny1627 RX line) Edge connector PB2 CDC RX UART TX (ATtiny1627 TX line) Edge connector PA0 DBG0 UPDI Edge connector PB7 DBG1 GPIO1 Edge connector and LED PC4 DBG2 GPIO0 Edge connector and SW0 (PA0) DBG3 RESET/GPIO Edge connector © 2020 Microchip Technology Inc. User Guide DS40002199A-page 26 ATtiny1627 Hardware Revision History and Known Issues 5. Hardware Revision History and Known Issues This user guide is written to provide information about the latest available revision of the board. The following sections contain information about known issues, a revision history of older revisions, and how older revisions differ from the latest revision. 5.1 Identifying Product ID and Revision The revision and product identifier of the ATtiny1627 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 ATtiny1627 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 ATtiny1627 Curiosity Nano is A09-3258. 5.2 Revision 3 Revision 3 is the same as revision 2, but is mounted with production samples of ATtiny1627. 5.3 Revision 2 Revision 2 is the initial prototype revision, with a limited distribution. This revision is mounted with engineering samples of ATtiny1627. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 27 ATtiny1627 Document Revision History 6. Document Revision History Doc. rev. Date Comment A 04/2020 Initial document release. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 28 ATtiny1627 Appendix 7. Appendix 7.1 Schematic Figure 7-1. ATtiny1627 Curiosity Nano Schematic 6 BP8 NIA_0CDA_5BP9 NIA_0CDA_4BP3 OW_0ACT_3AP4 OW_0ACT_4AP5 NIA_0CDA_5AP6 NIA_0CDA_6AP7 NIA_0CDA_7APm oc.muitlA:etaD: egaP: CDC/TRAUn oE TONe hts etonedr edaehe htn oX T/XRPPA6_ADC0_AIN6 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 29 l angise htf on oitceridt uptuo/tupni. ecruoss 'tio te vitcepser. REGGUBEDe htm orft uptuos iX TC DC. REGGUBEDe hto tt upnis iX RC DC. ecivedT EGRATe htm orft uptuos iX T. ecivedT EGRATe hto tt upnis iX R: C2In oE TONIDPU_0APe bd luohss pu-lluP. draobn os pu-llupo N. )s(ecivede valso te solcd etnuomXT_1TRASU_1APX R_1TRASU_2APA DS_0IWT_1BPL CS_0IWT_0BPI SOM_0IPS_2CPO SIM_0IPS_1CP0 5 CPWS_4CP2 02J1 02J4 02JE GDE_CCV3 02J5 02J6 02JK CS_0IPS_0CPS S_0IPS_3C7 261ynitTA3 BP2 BP0 AP2 12J7 BP312JT EGRAT_CCV4 CP- V 5.5- V 8.1X TC DC1k R203 X RC DC0 GBD1 GBD2 GBD3 GBDR FM-7261ynitTA2AP1 1k R202 GTVDBG0 DBG3 S UBVVOFF 0 02Jr otcennoce gden ip-43ONANCC NID_SYS CDC_RX CDC_TX DBG1 DBG2 XRX TT RAUX T_0TRASU_2BPX R_0TRASU_3BP1 CSOT_3BP402C. M.Np 7.4302C. M.Np 7.4PC5 PA0_UPDI PA1_USART1_TX E GDE_CCVX R_1TRASU_2AP3 OW_0ACT_3AP4 OW_0ACT_4APX T_0TRASU_2BPX R_0TRASU_3BPO SIM_0IPS_1CPK CS_0IPS_0CPL CS_0IA DS_0IWT_0BPWT_1BPX T_0TRASU_2BP5 NIA_0CDA_5APPC4_SW0 X R_0TRASU_3BP2 CSOT_2BP1 12JPB2_TOSC2 012J0 02CX. M.Nz Hk867.23D NG0 02Cn 001T EGRAT_CCV9 02J5 2D NGDAPPB3_TOSC1 0 02U8 17161514131PC2_SPI0_MOSI PB4 PC3_SPI0_SS 19 20 21 22 23 24 PC2 PC3 PC4 PC5 RESET/UPDI/PA0 PA1 1CP0CP0BP1BP2BP/2CSOT3BP/1CSOTPB5 12 11 PB4_ADC0_AIN9 PC4_SW0 PB6 10 PB5_ADC0_AIN8 PB7 9 PB6 PA7 8 PB7_LED0 PA6 7 PA7_ADC0_AIN7 IKLC/3APDNGCCV2 D NG4AP5AP3 4 5 6 PB7_LED0 SML-D12Y1WT86YELLOWLED 2 1 D200 4 2 31 TS604VM1-035CR Designed with Drawn By: Sheet Title Engineer: GNDGND A08-29862 SizeA09-32582 ATtiny1627 Appendix D WST EGRATX RT RAUX TT RAUT ADWSK LCWSO IPG/OWST ESER- A m005: 8255CIMV 5.5o tV 5.2: niVV 3.3d exiF: tuoV© 2020 Microchip Technology Inc. User Guide DS40002199A-page 30 @ I DPUUA m005: xamIV m062: tuoporDr otcennocg nimmargorPg nimmargorpy rotcafr ofr eggubeDf o. tegrate hto tV 1.5d naV 52.5o t: snoitatimild nat uptuoe lbatsujdAV 52.1n eewtebr otalugere htf oe gatlovt uptuoe htt sujdan acR EGGUBEDe hT- V 04.4n eewteby ravn ach cihw, )BSU(t upnie hty bd etimils it uptuoe gatlove hT- e htr ofd ewollae gatlovg nitarepom uminime htt imill liwd naV 56.1f ol evele gatlovl aminima e vahs retfihsl evele hT- . noitacinummocw ollal litso tt egrat. tegrate hto td erevilede gatlovm uminime htt imill liwd naV 07.1f ol evele getalovl aminima s ah3 6149CIMe hT- : esufe lbatteseRC TP. noitacificepst egrate hte htn ihtiwe bo te gnare gatlove htt imill liwn oitarugifnoce rawmriF- A m005: tnerrucd loHA m0001: tnerrucp irT: 001J. srotalugerd raob-nod nas retfihsl evele htm orfr ewopt egratf on oitarapesl lufr ofd esup arts-tuCe romr oft uce bd luocp artss iht, ylppusr ewopl anretxen ag nisus tnemerusaemt nerrucr oF- . egnare repmao rcime htn is ih ctiwse hth guorhtk cabe gakaeL. stnemerusaeme taruccaT EGRAT: 101JX RT RAX TT RAUI DPUt nemerusaemt nerrucy saer ofd esue bn act ahtr edaeh-niph ctipl im0012 x1a r oft nirptoofs is ihT: tnirptoofe hte suo T. nottuB/ D ELe htd nar ellortnocorcimt egrate hto tr edaeh-nipa t nuomd na, selohe htn eewtebk carte htt uC- O IPGA m005@ : 3535CIMO IPGT ESER- TEGRAT-l angiS0 GBDV 6o tV 6.2: niVV 1.5o tV 52.1: tuoVA m005: xamI1 GBDV m061, Am051@Vm05: )lacipyt(t uoporD2 GBD3 GBDCCVl aitini% 2: ycaruccAt imilt nerrucd nan wodtuhsl amrehT. rotalugere htn ie gatlovt uoporde htd nae gatlovt upnie hty bd etimils ie gatlovt uptuom umixaM) tuopord- n iV= x amV(1 2 5X RT RAUTUOVTUOVEP CN7 GND 3 NE4 L RTC_3GBDX T_0_1SX R_1_1SC ADC DA_GTVD EVRESERX T_2_0SK LC_3_0S3 V3P_CCV1k P SCIR112 8 01UX TT RAU3 6149CIMC DA_GTVS UBV_CCVE GDE_CCVT ADK LCO IPG1 01JR LCMe cafretnIX TX RC DCC DCT EGRAT_CCV3 11Rk 74C ADNIVS YS_DI6 1 01PT0 01F3 1263CMS UBVF FOVL RTC_XR_CDC47k R109 L RTC_XT_CDCT OOBNE1 DNGS YS_DIN E_GTVO IDWSVTG_EN F FOVVBUS_ADC 4 2322212029181713 3PDAP25 26 27 PA27 RESETN PA28 52AP/PD_BSU28 29 30 31 32 GND VDDCORE VDDIN SWDCLK/PA30 SWDIO/PA31 00AP1 42AP/MD_BSU32AP/FOS_BSU22AP91AP81AP71AP61APA15 16 DBG1_CTRL REG_ENABLE E LBANE_GER47k R103 SRST PA14 PA11 15 DBG0_CTRL PA10 PA09 PA08 GND DBG2_CTRL VDDANA 14 13 12 11 10 9 VBUS_ADC DBG2_GPIO 10AP20AP30AP40AP50AP60AP70APK LCWSK LCWS2 3 4 5 6 7 8 B FL8D56NMDL RTC_3GBD1 3 2 D NG0 11Rk 1L RTC_2GBDREG_ADJUST 3GBD47k R100 D NGO IDWSX R_0_0SL RTC_0GBD8 01Rk 1LEVEL_CCV0 01JL RTC_1GBDR OTALUGER_CCVD NG7 -4WF54T1CVL47L EVEL_CCVL EVEL_CCVL EVEL_CCVL EVEL_CCVL EVEL_CCV47k R102 47k R111 D NG47k R105 3 01CF u2.2D NG6 01Rk 33L RTC_XT_CDCL RTC_XR_CDC47k 27k R101 R104 D NG5 3535CIMJDA/CND NG7 2 01US UBV_CCV4 2 TUOVDNGNIV3 D NGPYB1 GBD2 GBD6 2 01Cn 001D NG ATtiny1627 Appendix 7.2 Assembly Drawing Figure 7-2. ATtiny1627 PAJ200034 COJ200 PAJ200033 Curiosity PAJ20000 PAJ200032 PAJ200031 Nano PAJ200030 Assembly PAJ200029 PAJ200028 PAJ200027 Drawing PAJ200026 PAJ200025 Top PAJ200024 PAJ200023 PAJ200022 PAJ200021 PAJ200020 PAJ200019 PAJ200018 PAJ10506 PAF10001 PAF10002 COF100 PAC10002 COC100 PAC10001 PAU10103 PAU10104 COU101 PAU10102 PAU10105 PAU10100 PAU10101 PAU10107 PAU10106 COC101 PAC10102 PAC10101 PAR11001 COR110 PAR11002 PAQ10103 COQ101 PAQ10102 PAQ10101 PAQ10100 PAR11301 COR113 PAR11302 COR100 PAR10002 PAR10001 COR109 PAR10902 PAR10901 COR103 PAU10201 COU102 PAU10202 PAU10203 PAR10301 PAU10207 PAR10302 PAU10206 PAU10205 PAU10204 PAC10201 COC102 COR101 PAR10102 PAR10101 PAC10202 COR104 PAR10402 PAR10401 PAC10301 COC103 PAC10302 PAR10601 COR106 PAU1080C2 PAU1080B2 PAU1080A2 COU108 PAR10602 PAU1080C1 PAU1080B1 PAU1080A1 PAJ105010 PAJ10508 PAJ10501 PAJ10502 PAR11101 COR111 PAR11102 PAJ10503 PAJ10504 PAJ10206 PAJ10507 PAJ10505 PAJ10509 PAJ10500 COTP100 PATP10001 PAJ10001 COJ100 PAJ10002 COC205 PAC20501 PAC20502 PAJ10101 COJ101 PAJ10102 COJ105 PAJ10201 PAJ10202 COJ102 PAJ10203 PAJ10204 COC108 PAC10802 PAC10801 COU107 PAU10701 PAU10702 PAU10700 PAU10703 PAU10706 PAU10705 PAU10704 PAJ10205 PAJ105011 PAU100017 PAU100018 PAU100019 PAU100020 PAU100021 PAU100022 PAU1016 PAU100033 PAU100015 PAU1014 COU100 PAU100013 PAU1012 PAU101 PAU100010 PAU109 PAU10008 PAU10007 PAU10006 PAU10005 PAU10004 PAU10003 PAR10201 COR102 PAR10202 PAR10501 COJ202 PAJ20201 PAJ20202 COJ206 PAJ20601 PAJ20602 COJ205 PAJ20501 PAJ20502 COJ204 PAJ20401 PAJ20402 PAJ20101 COJ201 PAJ20102 COJ203 PAJ20301 PAJ20302 b PAU200024 PAU20001 PAU200023 PAU20002 PAU200022 PAU20003 PAU200025 PAU200021 PAU20004 PAU200020 PAU20005 PAU200019 PAU20006 PAU20000 COU200 PAU200018 PAU20007 PAU200017 PAU20008 PAU200016 PAU20009 PAU200015 PAU200010 PAU200014 PAU200011 PAU200013 PAU200012 PAJ21202 PAJ21302 COJ212 COJ213 C COJ211 COJ210 PAJ21105 PAJ21101 PAJ21201 PAJ21301 PAJ21005 PAJ21001 PAJ21102 PAJ21002 COJ209 PAJ20901 COC204 PAC20401 PAC20402 COC203 PAC20301 PAC20302 PAU100023 PAU10002 COR108 PAR10802 PAR10801 COR105 PAR10502 COU106 PAU10601 PAU10602 PAU10600 PAU10603 PAU10606 PAU10605 PAU10604 COU105 PAU10501 PAU10502 PAU10500 PAU10503 PAU10506 PAU10505 PAU10504 COTP101 PATP10101 PAU100024 PAU10001 PAU1025 PAU1026 PAU1027 PAU100028 PAU1029 PAU1030 PAU100031 PAU1032 COU104 PAU10401 PAU10402 PAU10400 PAU10403 PAU10406 PAU10405 PAU10404 COC200 PAC20001 PAC20002 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 31 PAJ20902 PAXC20001 PAXC20002 COXC20 PASW20003 PASW20001 COD200 PAD20001 PAD20002 COR203 PAR20302 PAR20301 COR202 PAR20202 PAR20201 COSW20 PASW204 PASW202 PAL20002 COL200 PAL20001 PAD10002 COD100 PAJ20001 PAD10001 PAR11201 COR112 PAR11202 PAJ20002 PAR10701 COR107 PAR10702 COC106 PAJ20003 PAC10601 PAC10602 PAC10701 COC107 PAJ20004 PAC10702 PAU10301 PAU10302 PAU10305 PAJ20005 PAU10303 PAU10304 PAJ20006 PAJ20007 PAJ20008 PAJ20009 PAJ2010 PAJ200011 PAJ2012 PAJ200013 PAJ2014 PAJ200015 PAJ200016 PAJ200017 Figure 7-3. ATtiny1627 Curiosity Nano Assembly Drawing Bottom R COLABEL1 COU103 PAU10300 PAU10306 ct PAJ200018 PAJ200019 PAJ200020 PAJ200021 PAJ200022 PAJ200023 PAJ200024 PAJ200025 PAJ200026 PAJ200027 PAJ200028 PAJ200029 PAJ200030 PAJ200031 PAJ20000 PAJ200032 PAJ200033 PAJ200034 COJ200 PASW20001 PASW20003 PAJ10102 COJ101 PAJ10101 COC205 PAC20501 PAC20502 COJ100 PAJ10002 PAJ10001 COR106 PAR10602 COU108 PAU1080C1 PAU1080B1 PAU1080A1 PAU1080C2 PAU1080B2 PAU1080A2 PAR10601 COC102 COR104 PAR10402 PAR10401 PAC10202 PAC10201 COR101 PAR10102 PAR10101 PAR10302 COR103 PAR10301 PAU10201 COC101 PAC10102 PAC10101 PAU10100 PAU10101 PAU10106 COU101 PAU10102 PAU10105 PAU10202 PAU10203 COSW20 COJ209 PAJ20902 PAJ20901 COC204 PAC20401 PAC20402 PAJ21105 COJ211 PAJ21102 PAJ21005 COJ210 PAJ21002 PAJ21201 COJ212 PAJ21301 COJ213 PAJ21101 PAJ21001 PAJ21202 PAJ21302 PAU200013 PAU200012 PAU200014 PAU200011 PAU200025 PAU200015 PAU200010 PAU200016 PAU20009 PAU200017 PAU20008 PAU200018 PAU20007 PAU20000 COU200 PAU200019 PAU20006 PAU200020 PAU20005 PAU200021 PAU20004 PAU200022 PAU20003 PAU200023 PAU20002 PAU200024 PAU20001 PAU10206 PAU10205 PAU10204 COU102 PAU10207 PAU10103 PAU10107 PAC10001 COC100 PAC10002 PAU10104 COR110 PAR11002 PAR11001 PAF10001 PAF10002 COF100 PAJ10506 PAC10302 COC103 PAC10301 COR202 PAR20202 PAR20201 COR203 PAR20302 PAR20301 PAD20001 COD200 PASW202 PASW204 PAXC20001 PAXC20002 COXC20 COC203 PAC20301 PAC20302 PAD20002 PAJ20202 COJ202 PAJ20201 PAJ20602 COJ206 PAJ20601 PAJ20502 COJ205 PAJ20501 PAU10706 COU107 PAU10705 PAU10704 PAU10701 PAU10702 PAU10703 PAU10700 COC108 PAC10802 PAC10801 COR109 PAR10902 PAR10901 COR100 PAR10002 PAR10001 COQ101 PAQ10102 PAQ10101 PAQ10100 PAQ10103 PAR11302 COR113 PAR11301 PAJ10508 PAJ105010 PAR11102 COR111 PAR11101 PAJ10501 PAJ10502 COC200 PAC20002 PAC20001 PAL20001 COL200 PAL20002 PAJ20402 COJ204 PAJ20401 PAJ20102 COJ201 PAJ20101 PAU10606 COU106 PAU10605 PAU10604 PAU10601 PAU10602 PAU10603 PAU10600 PAU10506 COU105 PAU10505 PAU10504 PAU10501 PAU10502 PAU10503 PAU10500 COR108 PAR10802 PAR10801 PAR10202 COR102 PAR10201 PAU10008 PAU10007 PAU10006 PAU10005 PAU10004 PAU10003 PAU109 PAU100033 PAU100010 COU100 PAU101 PAU1012 PAU100013 PAU1014 PAU100015 PAU1016 PAU100017 PAU100018 PAU100019 PAU100020 PAU100021 PAU100022 PAJ20302 COJ203 PAJ20301 PAR10501 COTP100 PATP10001 PAJ10205 PAJ10206 PAJ10503 PAJ10504 COJ102 PAJ10203 PAJ10204 PAJ10505 PAJ10509 PAJ10500 PAJ10507 PAU10305 PAU10301 PAU10302 PAJ200017 PAJ200016 PAJ200015 PAJ2014 PAJ200013 PAJ2012 PAJ200011 PAJ2010 PAJ20009 PAJ20008 PAJ20007 PAJ20006 PAU10304 PAJ20005 PAU10303 PAJ20004 PAC10702 COC107 PAC10701 PAC10602 COC106 PAJ20003 PAC10601 PAR10702 COR107 PAJ20002 PAR10701 PAR11202 COR112 PAR11201 PAJ20001 COD100 PAD10001 PAD10002 PAJ10201 PAJ10202 COJ105 COLABEL1 COR105 PAR10502 PAU10002 COTP101 PATP10101 PAU100023 PAJ105011 PAU10406 COU104 PAU10405 PAU10404 PAU10401 PAU10402 PAU10403 PAU10400 PAU10306 COU103 PAU10300 PAU10001 PAU100024 PAU1032 PAU100031 PAU1030 PAU1029 PAU100028 PAU1027 PAU1026 PAU1025 ATtiny1627 Appendix 7.3 Curiosity Nano Base for Click boardsTM Figure 7-4. ATtiny1627 Curiosity Nano Pinout Mapping VBUS VOFF DBG3 DBG0 GND VTG PB6 PB5 PB4 PA3 PA4 PA5 PA6 PA7 GND PC5 PC4 NC ID CDCRX CDCTX DBG1 DBG2 PA1 PA2 PB1 PB0 PC2 PC1 PC0 PC3 GND PB2 PB3 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 32 Power Supply strap Target Power strap UART RX UART TX ATtiny1627 Appendix 7.4 Disconnecting the On-board Debugger The on-board debugger and level shifters can be completely disconnected from the ATtiny1627. The block diagram below shows all connections between the debugger and the ATtiny1627. 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 USB VBUS LDO VCC_EDGE LDO VCC_P3V3 DBG0 R EGGUBEDPA04/PA06 GPIO straps PA07 DBG1 PA08 DBG2 PA16 Level-Shift DBG3 TARGET PA00 CDC TX PA01 CDC RX DIR x 5CDC RX DBG0 CDC TX DBG1 DBG2 DBG3 © 2020 Microchip Technology Inc. User Guide DS40002199A-page 33 ATtiny1627 Appendix 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 ATtiny1627 Curiosity Nano is supported in IARTM 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. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 34 ATtiny1627 Appendix Figure 7-7. Select Target Device Figure 7-8. Select Debugger © 2020 Microchip Technology Inc. User Guide DS40002199A-page 35 ATtiny1627 Appendix Figure 7-9. Configure Interface © 2020 Microchip Technology Inc. User Guide DS40002199A-page 36 ATtiny1627 The Microchip Website Microchip provides online support via our website at 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 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: microchip.com/support Microchip Devices Code Protection Feature Note the following details of the code protection feature on Microchip devices: • Microchip products meet the specification contained in their particular Microchip Data Sheet. • Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the intended manner and under normal conditions. • There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft of intellectual property. • Microchip is willing to work with the customer who is concerned about the integrity of their code. • Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not mean that we are guaranteeing the product as “unbreakable.” Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act. Legal Notice Information contained in this publication regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with © 2020 Microchip Technology Inc. User Guide DS40002199A-page 37 ATtiny1627 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-6308-5 Quality Management System For information regarding Microchip’s Quality Management Systems, please visit microchip.com/quality. © 2020 Microchip Technology Inc. User Guide DS40002199A-page 38 Worldwide Sales and Service AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE

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

© 2020 Microchip Technology Inc. User Guide DS40002199A-page 39


FREE ENGLISH PDF

OPERATING INSTRUCTIONS

USER GUIDE - USER MANUAL

OWNER GUIDE - OWNER MANUAL

REFERENCE GUIDE - REFERENCE MANUAL

INSTRUCTION GUIDE - INSTRUCTION MANUAL

Leave a Reply