MICROCHIP AVR-BLE (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 AVR-BLE (01) PDF MANUAL


PDF Content Summary: © 2020 Microchip Technology Inc. User Guide DS50002956A-page 1 AVR-BLE Hardware User Guide Preface The AVR-BLE Development Board is a small and easily expandable demonstration and development platform for Bluetooth® Low Energy (BLE) solutions based on the AVR® microcontroller architecture. It is designed to demonstrate that the design of a typical BLE application can be simplified by partitioning the task into three blocks: • Smart – represented by the ATmega3208 microcontroller • Secure – represented by the ATECC608A secure element • Connected – represented by the RN4870 BLE module In addition, the AVR-BLE Development Board features the following elements: • The on-board debugger (PKoB nano) supplies full programming and debugging support through Atmel Studio/ Microchip MPLAB® X IDE. It also provides access to a serial port interface (serial to USB bridge) and two logic analyzer channels (debug GPIO). • A mikroBUSTM socket enables the ability to expand the board capabilities with the selection from 450+ sensors and actuators options offered by MikroElektronika (www.mikroe.com) via a growing portfolio of Click boardTM. Table of Contents Preface...........................................................................................................................................................1 1. Introduction............................................................................................................................................. 3 1.1. Features....................................................................................................................................... 3 1.2. Board Overview............................................................................................................................3 2. Getting Started........................................................................................................................................6 2.1. Quick Start....................................................................................................................................6 2.2. Design Documentation and Relevant Links................................................................................. 7 3. Hardware User Guide............................................................................................................................. 8 3.1. On-Board Debugger Overview.....................................................................................................8 3.2. Power Supply.............................................................................................................................13 3.3. Low-Power Operation.................................................................................................................14 3.4. Target Current Measurement..................................................................................................... 14 3.5. Peripherals.................................................................................................................................15 4. Hardware Revision History and Known Issues..................................................................................... 22 4.1. Identifying Product ID and Revision........................................................................................... 22 4.2. Revision 3...................................................................................................................................22 4.3. Revision 2...................................................................................................................................22 5. Document Revision History...................................................................................................................23 6. Appendix............................................................................................................................................... 24 6.1. Schematics.................................................................................................................................24 6.2. Assembly Drawing......................................................................................................................27 The Microchip Website.................................................................................................................................28 Product Change Notification Service............................................................................................................28 Customer Support........................................................................................................................................ 28 Microchip Devices Code Protection Feature................................................................................................28 Legal Notice................................................................................................................................................. 28 Trademarks.................................................................................................................................................. 29 Quality Management System....................................................................................................................... 29 Worldwide Sales and Service.......................................................................................................................30 © 2020 Microchip Technology Inc. User Guide DS50002956A-page 2 Introduction 1. Introduction 1.1 Features • ATmega3208 AVR Microcontroller • Two User LEDs (Data and Error) • Mechanical Button • RN4870 Bluetooth Low Energy (BLE) Module • MCP9844 Temperature Sensor • BMA253 Acceleration Sensor • ATECC608A CryptoAuthenticationTM Device • SST25PF040CT 4Mb Serial Flash • mikroBUS Socket • On-board Debugger – Board identification in Atmel Studio/Microchip MPLAB® X IDE – Programming and debugging – Virtual serial port (USB CDC) – Two logic analyzer channels (DGI GPIO) • USB or Battery Powered 1.2 Board Overview The AVR-BLE development board is a hardware platform that is being used to evaluate the ATmega3208 AVR microcontroller and RN4870 BLE module. Figure 1-1. AVR-BLE Development Board Front Side Micro USB Connector Power/Status LED Debugger © 2020 Microchip Technology Inc. User Guide DS50002956A-page 3 BLE LED (Blue) MCP9844 Temp-sensor BMA253 ATmega3208 User Switch RN4870 Accelerometer MCU (SW0) BLE module USB/Battery MUX ATECC6080A Crypto SST25PF040CT Serial Flash Data LED (Green) Error LED (Red) Introduction Figure 1-2. AVR-BLE Development Board Back Side © 2020 Microchip Technology Inc. User Guide DS50002956A-page 4 CR2032 Battery Holder Additional RN4870 GPIO Introduction Figure 1-3. AVR-BLE Quick Reference Overview © 2020 Microchip Technology Inc. User Guide DS50002956A-page 5 Getting Started 2. Getting Started 2.1 Quick Start Demo Application Out of the box, the AVR-BLE board comes programmed with the avr-lightblue-explorer-demo. This application can be used to demonstrate a number of the board features using the LightBlue® app by Punch Through. 1. Download the LightBlue® app for iOS or Android. 2. Power the board through a Micro-USB cable or CR2032 battery. 3. Open the LightBlue® app and select the AVR-BLE peripheral. 4. Use the custom interface to explore the board. Info: The AVR-BLE will show up in the LightBlue® app as AVR-BLE_xxxx, where xxxx are the last two bytes of the RN4870 BLE module’s Bluetooth MAC address. This makes it possible to distinguish between multiple AVR-BLE boards. Communication between the demo application and the LightBlue® app is done by using a protocol based on ASCII packets. Refer to the protocol chapter on the avr-lightblue-explorer-demo page for a list of commands with examples, as well as the full source code for the project. Development Requirements MPLAB® X IDE: • MPLAB X IDE v5.30 or later • XC8 Compiler v2.10 or later For help with installation, view the MPLAB X installation guide. Build an Application View the default source code that is pre-loaded onto the development board. Explore, modify, and build off this source code to create a custom application. 1. View the source code at the avr-lightblue-explorer-demo GitHub page. 2. Read through the README.md to get more information on how to expand the solution. 3. Download the project from GitHub and open it in the latest version of MPLAB® X IDE. 4. Connect a USB cable (Standard-A to Micro-B or Micro-AB) between the Windows, Mac or Linux device, and the debug USB port on the AVR-BLE. The board will be identified in the kit window in MPLAB® X IDE. 5. Explore, modify, and build off the source code. 6. Make and program the device. Select the PKoB nano serial number as the debug tool when prompted. Driver Installation When the board is connected to the 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 ATmega3208 device on the AVR-BLE board is programmed and debugged by the on-board debugger, and therefore, no external programmer or debugger tool is required. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 6 Getting Started Tip: The Kit Window can be opened in MPLAB® X IDE through the menu bar Window > Kit Window 2.2 Design Documentation and Relevant Links The following list contains links to the most relevant documents and software for the AVR-BLE 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® Xpress Cloud-based IDE - MPLAB Xpress Cloud-Based IDE is an online development environment that contains the most popular features of our award-winning MPLAB X IDE. This simplified and distilled application is a faithful reproduction of our desktop-based program, which allows users to easily transition between the two environments. • 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. • AVR-BLE website - Board information, latest user guide and design documentation. • AVR-BLE on Microchip Direct - Purchase this board on Microchip Direct. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 7 Hardware User Guide 3. Hardware User Guide 3.1 On-Board Debugger Overview AVR-BLE 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 ATmega3208 in Atmel Studio/Microchip MPLAB® X IDE • A mass storage device that allows drag-and-drop programming of the ATmega3208 • A virtual serial port (CDC) that is connected to a Universal Asynchronous Receiver/Transmitter (UART) on the ATmega3208, 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 AVR-BLE 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 AVR-BLE 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 ATmega3208 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. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 8 Hardware User Guide 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 Receive Target UART TX © 2020 Microchip Technology Inc. User Guide DS50002956A-page 9 UART RX Terminal 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 Section 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. Hardware User Guide • 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 will 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. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 10 Hardware User Guide 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 • CLICK-ME.HTM – redirect to the AVR-BLE web demo application • 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. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 11 Hardware User Guide 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.) 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 time-stamped 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 AVR-BLE 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. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 12 Hardware User Guide 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 Power Supply The board can be powered through the USB port or by a CR2032 battery. It will automatically switch to the battery if USB power is not available. While powered through USB, the board generates 3.3V for the debugger, ATmega3208, and peripherals. During battery operation, the ATmega3208 and peripherals run directly on the battery voltage, while the debugger is not powered. Current drawn from the USB port is limited to 500 mA by a PTC resettable fuse. Important: When powering the AVR-BLE board with a CR2032 battery, it is important to leave the ATmega3208 pins that connect to the CDC UART in Tri-State (Input) mode. This is to prevent the debugger from getting powered through its GPIO. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 13 Hardware User Guide Figure 3-3. Power Supply Block Diagram VUSB USB MIC33050 VCC_P3V3 (buck) On-Board Debugger Power source MUX (MIC94050) Power converter(MIC94165) Power disconnect VBAT © 2020 Microchip Technology Inc. User Guide DS50002956A-page 14 0Ω resistor Power MUX P3V3_ENABLE VBAT_OUT0Ω resistor Target MCU Power consumer Peripherals Battery Holder mBUS RN4870 (CR2032) Info: On the mikroBUS socket, the +5V rail is powered from the USB port. Consequently, +5V will not be available when the board is powered from a battery. 3.3 Low-Power Operation To achieve the lowest power consumption of the board, the following considerations must be taken: • Set the MCP9844 in Shutdown mode – Set bit 8 (SHDN) in the 16-bit CONFIG register (address 0x01) • Set the BMA253 in Deep Suspend mode – Set bit 5 (deep suspend) in the 8-bit PMU_LPW register (address 0x11) • Set the RN4870 in Sleep mode – Set the RX_IND pin high (PD2 on the ATmega3208) – Send the "O,0\r" command to the RN4870 • Set unused ATmega3208 I/O pins as input and disable the digital input buffer Important: USART pins PF0 and PF1 are connected directly to the on-board debugger. It is important to tri-state the USART pins when the board is powered from a CR2032 battery to prevent powering the debugger through its I/O pins. Doing so will increase the power consumption and cause undefined behavior from the on-board debugger. Info: The load switch U300 in the power MUX can leak up to 1 μA when the board is powered from a battery. By modifying the board and removing resistor R303 (0Ω), U300 can be disconnected. Be warned that a board modified this way can no longer be powered from USB, and consequently, neither programmed nor debugged using the on-board debugger until the 0Ω resistor is reconnected. 3.4 Target Current Measurement Power to the ATmega3208 and its peripherals is connected from the on-board power supply through a 0Ω resistor (R301) in parallel with a 100-mil Current sense pin header footprint marked with “ISNS” in silkscreen (J301). To Hardware User Guide measure the power consumption of the ATmega3208 and other peripherals on the board, de-solder the 0Ω resistor and connect an ammeter over the Current sense footprint. Figure 3-4. Current sense footprint

Current sense footprint (J301) 0Ω resistor (R301)

Tip: A 100-mil pin header can be soldered into the Current sense (J301) footprint for easy connection of an ammeter. Once the ammeter is not needed anymore, place a jumper cap on the pin header. 3.5 Peripherals 3.5.1 ATmega3208 Microchip ATmega3208 is a microcontroller featuring the AVR® processor with hardware multiplier – running at up to 20 MHz and with 32 KB Flash, 4 KB SRAM, and 256 bytes of electrically erasable programmable read-only memory (EEPROM) in a 28- or 32-pin package. It uses the latest Core Independent Peripherals (CIPs) with low-power features, including Event System, accurate analog features, and advanced peripherals. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 15 PD7 Hardware User Guide 3.5.2 mikroBUS Socket Figure 3-5. mikroBUS Socket Pinout AN PWM PD1 PD5 RST INT PD6 PA7 CS RX PC1 PA6 SCK TX PC0 PA5 MISO SCL PA3 PA4 MOSI SDA PA2 VCC +3.3V +5V VBUS GND GND GND GND The AVR-BLE board features a mikroBUS socket for expanding the functionality of the development board using MikroElektronika Click Boards and other mikroBUS add-on boards. The socket is populated with two 1x8 2.54 mm pitch female headers and is ready to mount add-on boards. Table 3-3. mikroBUS Socket Pinout mikroBUS Socket Pin ATmega3208 Pin Function Shared Functionality AN PD7 ADC AIN7 — RST PD5 GPIO — CS PA7 SPI0 CS — SCK PA6 SPI0 SCK SST25PF040CT MISO PA5 SPI0 MISO SST25PF040CT MOSI PA4 SPI0 MOSI SST25PF040CT +3.3V VDD VCC_TARGET — GND GND Ground — PWM PD1 TCA0 WO1 — INT PD6 GPIO — RX PC1 UART1 RX — TX PC0 UART1 TX — SCL PA3 TWI0 SCL MCP9844, BMA253 and ATECC608A SDA PA2 TWI0 SDA MCP9844, BMA253 and ATECC608A +5V — VBUS — GND GND Ground — © 2020 Microchip Technology Inc. User Guide DS50002956A-page 16 Hardware User Guide Info: VBUS is powered from USB. Consequently, +5V will not be available while the board is powered from a battery. Info: VCC_TARGET will have the battery voltage when the board is powered from a battery, which can be less that +3.3V. 3.5.3 RN4870 BLE Module The RN4870 is a Bluetooth® Low Energy (BLE) module that integrates a Bluetooth® 5.0 baseband controller, on- board Bluetooth stack, digital and analog I/O, and RF power amplifier into one solution. Additional Features: • Range up to 50m • Operating Voltage Range: 1.9V to 3.6V • TX / RX Mode Peak Current: 10 mA (typical) • Low-Power Mode Current: 60 μA (typical) • Shutdown Current: 2.9 μA (max) The RN4870 BLE module is connected to the ATmega3208 through UART as well as three GPIOs for control and configuring of the module. The RST signals resets the module, while the RX_IND signal is used to wake the module from Low-Power mode. The MODE signal, available from the ATmega3208, the debugger as well as by a physical switch, allows the module to be put in a “Test Mode” where the RN4870 firmware can be updated. The module has one of its GPIO pins connected to an LED. By default, this will indicate connection status, but the user can configure it for a number of other functions. Many of the other RN4870 GPIO pins are available as pads around the label on the back side of the AVR-BLE board, as can be seen in Figure 1-2. Info: Some RN4870 settings have been changed during manufacturing of AVR-BLE. Using the S- command, the device name has been changed to “AVR-BLE”. In addition, the communication settings have been configured for ATmega3208 UART0 settings of 9600,8,N,1. Table 3-4. RN4870 Connections RN4870 Pin ATmega3208 Pin Function Shared Functionality RX PA0 UART0 TX — TX PA1 UART0 RX — RST PD3 GPIO — P2_0 / MODE PF3 GPIO SW0 and on-board debugger P3_3 / RX_IND PD3 GPIO — P1_1 / STATUS1 — BLE Connection LED BLE LED Info: The RST and MODE signals are pulled up by external resistors. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 17 Hardware User Guide 3.5.4 ATECC608A Secure Element The ATECC608A is a secure element from the Microchip CryptoAuthentication portfolio with advanced Elliptic Curve Cryptography (ECC) capabilities. With ECDH and ECDSA being built right in, this device is ideal for the rapidly growing Internet of Things (IoT) market by easily supplying the full range of security, such as confidentiality, data integrity, and authentication to systems with MCU or MPUs running encryption/decryption algorithms. Similar to all Microchip CryptoAuthentication products, the ATECC608A employs ultra-secure, hardware-based cryptographic key storage and cryptographic countermeasures that eliminate any potential backdoors linked to software weaknesses. The ATECC608A CryptoAuthentication device on the AVR-BLE board can be used to authenticate the board with other hardware for secure IoT communication. Info: 7-bit I2C address: 0x58. Table 3-5. ATECC608A Connections ATECC608A Pin ATmega3208 Pin Function Shared Functionality SDA PA2 TWI0 SDA MCP9844, BMA253 and mikroBUS SCL PA3 TWI0 SCL MCP9844, BMA253 and mikroBUS 3.5.5 SST25PF040CT Serial Flash The SST25PF040CT is a 4 Mbit Serial Flash with extended operating voltage range and low-power consumption. Additional Features: • Operating Voltage Range: 2.3V to 3.6V • Active Read Current: 5 mA (typical) • Power-Down Standby Current: 3 μA (typical) The SST25PF040CT Serial Flash is connected to the ATmega3208 through SPI and a GPIO for the HOLD signal. Info: The Flash is SPI Mode 0 and Mode 3 compatible, and supports clock speeds up to 40 MHz Table 3-6. SST25PF040CT Connections

SST25PF040CT Pin ATmega3208 Pin Function Shared Functionality

© 2020 Microchip Technology Inc. User Guide DS50002956A-page 18 CS PD0 GPIO — SCK PA6 SPI0 SCK mikroBUS MISO PA5 SPI0 MISO mikroBUS MOSI PA4 SPI0 MOSI mikroBUS HOLD# PD4 GPIO — 3.5.6 MCP9844 Temperature Sensor The MCP9844 digital temperature sensor converts circuit board temperatures between -40°C and +125°C to a digital word with ±1°C/±3°C (typical/maximum) accuracy. Additional features: Hardware User Guide • Accuracy: – ±0.2°C/±1°C (typical/maximum) from +75°C to +95°C – ±0.5°C/±2°C (typical/maximum) from +40°C to +125°C – ±1°C/±3°C (typical/maximum) from -40°C to +125°C • User Selectable Measurement Resolution: – 0.5°C, 0.25°C, 0.125°C, 0.0625°C • User Programmable Temperature Limits: – Temperature Window Limit – Critical Temperature Limit • User Programmable Temperature Alert Output • Operating Voltage Range: – 1.7V to 3.6V • Operating Current: – 100 μA (typical) • Shutdown Current: – 0.2 μA (typical) The MCP9844 temperature sensor is connected to the ATmega3208 through I2C and a GPIO for the user- configurable event output. Info: 7-bit I2C address: 0x18. Table 3-7. MCP9844 Connections MCP9844 Pin ATmega3208 Pin Function Shared Functionality SDA PA2 TWI0 SDA ATECC608A, BMA253 and mikroBUS SCL PA3 TWI0 SCL ATECC608A, BMA253 and mikroBUS Event PF2 ASYNC External Interrupt — 3.5.7 BMA253 Acceleration Sensor The Bosch BMA253 is a low-g acceleration sensor with digital output for measurements of acceleration in three perpendicular axes. Additional Features: • 12-Bit Sensitivity • User Selectable Acceleration Ranges: ±2g, ±4g, ±8g, ±16g • On-Chip 32 Frame First-In First-Out (FIFO) • Motion Triggered Interrupts: – New Data – Any Motion Detection – Single/Double Tap Sensing – Orientation Recognition – Flat Detection – Low/High-g Detection – Inactivity Detection • Operating Voltage Range: 1.62V to 3.6V © 2020 Microchip Technology Inc. User Guide DS50002956A-page 19 Hardware User Guide • Operating Current (Normal mode): 130 μA (typical) • Shutdown Current (Deep Suspend mode): 1 μA (typical) The BMA253 acceleration sensor is connected to the ATmega3208 through I2C and two GPIOs for the user configurable interrupt outputs. Info: 7-bit I2C address: 0x19 Table 3-8. BMA253 Connections BMA253 Pin ATmega3208 Pin Function Shared Functionality SDA PA2 TWI0 SDA MCP9844, ATECC608A and mikroBUS SCL PA3 TWI0 SCL MCP9844, ATECC608A and mikroBUS INT1 PC2 ASYNC External Interrupt — INT2 PC3 External Interrupt — 3.5.8 LEDs There are two user LEDs available on the AVR-BLE board that can be controlled by either GPIO or PWM. In addition, there is one LED connected directly to the BLE module. The LEDs can be activated by driving their connected I/O lines to GND. Table 3-9. LED Connections LED ATmega3208 Pin Function Shared Functionality Green Data LED PF4 TCA0 WO4 On-board debugger Red Error LED PF5 TCA0 WO5 — Blue BLE LED — Connected to BLE module RN4870 3.5.9 Mechanical Switch The AVR-BLE board has one mechanical switch. This is a generic user-configurable switch that will drive the connected I/O line to ground (GND) when it is pressed. An external resistor pulls the signal high when the switch is not pressed. Holding the switch during power-up can be used to put the Bluetooth module in Configuration mode. See 3.5.3 RN4870 BLE Module for more information. Table 3-10. Mechanical Switch Connection Switch ATmega3208 Pin Function Shared Functionality SW0 PF3 User switch RN4870 and on-board debugger Info: The SW0 signal is pulled up by an external resistor. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 20 Hardware User Guide 3.5.10 On-Board Debugger Implementation AVR-BLE features an on-board debugger that can be used to program and debug the ATmega3208 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. 3.5.10.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 3-11. On-Board Debugger Connections ATmega3208 Pin Debugger Pin Function Shared Functionality PF1 CDC TX UART2 RX (ATmega3208 RX line) — PF0 CDC RX UART2 TX (ATmega3208 TX line) — UPDI DBG0 UPDI — PF4 DBG1 DEBUG GPIO1 Data LED PF3 DBG2 DEBUG GPIO0 SW0 and RN4870 © 2020 Microchip Technology Inc. User Guide DS50002956A-page 21 Hardware Revision History and Known Issues 4. 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. 4.1 Identifying Product ID and Revision The revision and product identifier of the AVR-BLE 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 a AVR-BLE 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 AVR-BLE is A09-3314. 4.2 Revision 3 Revision 3 is functionally the same as revision 2, but features a RN4870 BLE module with firmware version 1.40 (part number RN4870-V/RM140). In the silkscreen, the part number of the serial flash chip is wrong. It should be SST25PF040C, but shows SST25P040C. 4.3 Revision 2 Revision 2 is the initial released revision of the board. It features a RN4870 BLE module with firmware version 1.30 (part number RN4870-I/RM130). © 2020 Microchip Technology Inc. User Guide DS50002956A-page 22 Document Revision History 5. Document Revision History Doc. rev. Date Comment A 03/2020 Initial document release © 2020 Microchip Technology Inc. User Guide DS50002956A-page 23 Appendix 6. Appendix 6.1 Schematics Figure 6-1. AVR-BLE Target schematic PA4_SPI_MOSI 30 31 32 PA6_SPI_SCK PD4_HOLD# PD0_SPI_CS PA5_SPI_MISO 2185-108SS0CYNP1 2185-108SS0CYNP1 9 100k R201 10k R212 10k R202 PA2_I2C_SDA PA3_I2C_SCL PF2_EVENT 11 PS INT2 6 PA3_I2C_SCL 12 SCx INT1 5 PA2_I2C_SDA PF5_ERR_LED 25 PF6_RST 26 UPDI 27 28 29 PF5 PF6 UPDI VDD GND (EXTCLK)PA0 PD6 PD5 PD4 16 15 PA0_BLE_UART0_TX PA1_BLE_UART0_RX PA2_I2C_SDA PA1 PA2 PD3 PD2 PD1 PD0 PC3 14 13 12 11 10 9 R205 4.7k 4.7k PA2_I2C_SDA R204 BLE_LED PF5_ERR_LED PF4_DATA_LED_DGI 10k 330R R207 SW0 4 23 1 R200 KMR221G © 2020 Microchip Technology Inc. User Guide DS50002956A-page 24 PA3_I2C_SCL PF3_SW0_DGI_FW 100n C206100n C207 Appendix Figure 6-2. AVR-BLE Power Schematic 12 0R R303 1kR306 3 1 5.6k R302 122 1 13 CH7410-2032LF 24.7uF C300 100k R305 1k R308 © 2020 Microchip Technology Inc. User Guide DS50002956A-page 25 Appendix Figure 6-3. AVR-BLE Debugger Schematic 100k 100k R106 R109 SRST 25 PA15 SRST 26 27 28 29 DBG2_GPIO 30 DBG2_CTRL 31 32 © 2020 Microchip Technology Inc. User Guide DS50002956A-page 26 PA27 RESETN PA28 GND VDDCORE VDDIN SWDCLK/PA30 SWDIO/PA31 16 DBG1_CTRL REG_ENABLE GND VDDANA 10 9 100k R101 PA14 PA11 15 DBG0_CTRL PA10 PA09 PA08 14 13 12 11 VBUS_ADC VTG_ADC 100k R102 100k 100k 100k R112 R115 R113 1 1 1 3 2 Appendix 6.2 Assembly Drawing Figure 6-4. AVR-BLE Assembly Drawing Top COD300 PAD30002 PAD30001 PAJ20100 PAJ20101 PAJ20102 PAJ20103 PAJ20104 COJ201 PAJ20105 PAJ20106 PAJ20107 PAJ20108 PAD20002 COD200 PAD20001 PAD20102 COD201 PAD20101 PAD20202 COD202 PAD20201 ® PAJ10001 COR305 PAR30501 PAR30502 COTP214 PATP21401 COTP213 PATP21301 COTP212 PATP21201 COTP211 PATP21101 COTP210 PATP21001 COTP209 PATP20901 COTP208 PATP20801 PAC30001 COC300 PAC30002 PAU30101 PAU30102 PAU30103 PAU30104 COLABEL1 PAU301013 COU301 PAU301012 PAU301011 PAU301010 PAU30109 COC301 PAC30102 PAC30101 PAJ30102 COJ301 PAJ30101 PAJ30100 COR208 PAR20801 PAR20802 PAR20901 COR209 PAR20902 COR210 PAR21001 PAR21002 PAC20202 COC202 PAC20201 PAC20101 COC201 PAC20102 PAJ10002 PAU30105 PAU30106 COR308 PAR30801 PAR30802 COR302 PAR30201 PAR30702 COR307 PAR30701 PAR30202 PAF10001 PAF10002 COF100 PAU30108 PAU30107 PAU3020C2 COC302 PAC30202 PAC30201 COR306 PAR30602 PAR30601 PAR30101 COR301 PAR30102 COC204 PAC20401 PAC20402 PAJ10106 PAJ10100 PAR30301 PAU3020C1 PAR20602 COR206 PAR20601 PAU20405 PAU20406 PAU20407 PAU2040 PAU20404 PAU20403 PAU20402 PAU20408 PAU20401 PAM2014 PAM200013 PAM200012 PAM200011 C-BLE PAM200010 PAM20009 PAM20008 PAM20007 ®COU300 PAU3000C2 PAU3000B2 PAU3000A2 PAU3000C1 COR303 PAR30302 PAU20502 COU205 PAU20501 PAU20101 PAU20102 PAU20103 COU201 PAU20109 PAU20108 PAU20107 PAU20106 PAR20401 COR204 PAR20402 PAR20501 COR205 PAR20502 COU204 PAM20006 PAM20005 PAM20004 PAM203 PAM20002 PAM20001 PAJ101010 PAJ10108 COU302 PAU3020A2 PAU3020A1 COJ101 PAU3020B2 PAU3000B1 PAU3020B1 PAU3000A1 PAU20503 PAU20104 PAU20105 COR304 PAR30401 PAR30402 PAQ30002 PAQ30003 PAJ30002 COJ300 PAC20002 COC200 PAC20001 PAJ30001 COR202 PAR20202 PAR20201 COC208 PAC20801 PAC20802 PAQ30001 PAQ30004 COR300 PAR30002 PAR30001 COM200 PAJ10107 PAJ101011 COQ100 PAQ10001 PAQ10002 PAQ10000 PAQ10003 PAD10002 COD100 PAD10001 COC205 PAC20501 PAC20502 PAM200020 PAM200021 PAU101 PAU102 PAU103 PAU104 PAU105 PAU10006 PAU107 PAU108 PAU10009 © 2020 Microchip Technology Inc. User Guide DS50002956A-page 27 COC209 PAC20902 PAC20901 PAU200025 PAU200024 PAU200033 PAU2023 PAU202 PAU200021 PAU2020 PAU2019 PAU200018 PAU2017 PAU200016 PAU200015 PAU200014 PAU200013 PAU200012 PAU200011 PAR21201 COR212 PAR21202 PAM200015 PAM200016 PAJ10101 PAJ10003 PAJ10005 COQ300 PAJ10004 PAJ10006 COC206 PAC20602 PAC20601 PAJ10102 PAU203010 PAU20309 PAU20308 PAU20307 PAU200026 PAU200027 PAM200017 PAU203011 PAU203012 COU203 PAU20301 PAU20302 COC207 PAC20702 PAC20701 PAU200010 PAU200032 PAU20001 PAU202 PAU203 PAU20004 PAU205 PAU206 PAU20007 PAU208 PAU20009 PAM200018 PAM200019 PAR10001 COR100 PAR10002 COTP100 PATP10001 COJ100 PAJ10103 PAJ10104 PAU20306 PAU20305 PAU200028 PAU200029 COU200 PAU20303 PAU20304 PAU200030 PAJ10105 PAJ10109 PAR11402 COR114 PAR11401 PAR10801 COR108 PAR10802 PAU20209 PAU20202 PAU20201 PAC20302 PAM202 PAM200023 PAM200024 PAM200025 PAM200026 PAM200027 PAM200028 PAM200029 PAM200030 PAM200031 PAM200032 PAM200033 PAC10101 COC101 PAC10102 PAC10201 COC102 PAC10202 PAR21301 COR213 PAR21302 PAC10301 COR102 PAR10202 PAR10201 COR101 PAR10101 PAR10102 COQ101 PAQ10101 PAQ10103 PAQ10102 PAQ10100 PAJ20000 PAJ20001 PAJ20002 PAJ20003 PAJ20004 COJ200 PAJ20005 PAJ20006 PAJ20007 PAJ20008 PAR20301 COR203 PAR20302 PAR21102 PAR20701 PASW20003 Figure 6-5. AVR-BLE Assembly Drawing Bottom PAC10102 COC101 PAC10101 PAC10202 COC102 PAC10201 PAC10301 PAU200031 PAU100025 PAU100026 PAU100027 PAU100028 PAU100029 PAU100030 PAU1024 PAU100033 PAU1023 PAU102 COU100 PAU1021 PAU1020 PAU100019 PAU1018 PAU1017 PAU100016 PAU100015 COR200 PAR20002 PAR10901 COR109 PAR20001 PAR10902 PAU20205 PAU20206 PAU20204 PAU20203 PAC20301 PAU20207 PAU20208 COR110 PAR11002 PAR11001 PAR10601 COR106 PAR10602 COU202 PAU20200 COR201 PAR20101 PAR20102 COC203 PAU100031 PAU100032 PAU100014 PAU100013 PAU100012 PAU100011 PAU100010 COC103 PAC10302 COQ102 COQ103 PAQ10201 PAQ10202 PAQ10200 PAR11301 COR113 PAQ10301 PAQ10302 PAQ10300 PAQ10203 PAR11302 PAQ10303 COR107 PAR10701 PAR10702 COR115 PAR11501 PAR11502 PAR10501 COR105 PAR10502 PAR10301 COR103 PAR10302 PAR11101 COR111 PAR11102 PAR10401 COR104 PAR10402 PAR11202 COR112 PAR11201 COTP201 PATP20101 COTP202 PATP20201 COTP203 PATP20301 COTP204 PATP20401 COR211 PAR21101 COTP205 COR207 PAR20702 PATP20501 PASW20004 COTP206 COSW200 PATP20601 PASW20005 COTP207 PASW20002 PASW20001 PATP20701 COTP208 PAC20201 COC202 PATP20801 PAC20202 COTP209 PATP20901 COD202 PAD20201 COTP210 PAR21002 COR210 PATP21001 PAD20202 PAR21001 PAJ20101 PAC20102 COC201 PAC20101 COTP211 PATP21101 PAD20101 COD201 PAR20902 COR209 PAD20102 PAR20901 COTP212 PATP21201 COD200 PAD20001 PAR20802 COR208 COTP213 PATP21301 PAD20002 PAR20801 COTP214 PATP21401 PAJ20108 PAJ20107 PAJ20106 PAJ20105 COJ201 PAJ20104 PAJ20103 PAJ20102 PAJ20100 PAJ30101 PAJ30100 COJ301 PAJ30102 COR305 PAR30502 PAR30501 PAD30002 PAD30001 COD300 COLABEL1 PAM20001 PAM20002 PAR30601 PAJ30001 COJ300 PAJ30002 PAF10001 PAF10002 COF100 PAJ10001 PAJ10002 PAM200033 PAM200032 PAM200023 PAM200022 PAC20302 PAU10009 PAU10008 PAU107 PAU10006 PAU10005 PAU104 PAU10003 PAU102 PAU101 PAR21102 PAC30001 PAR20601 COR206 PAR20602 PAM20003 PAM204 PAM20005 PAM20006 PAM20007 PAM20008 PAM20009 PAM2010 PAM200011 PAM200012 PAM200013 PAM200014 PAU20404 PAU20403 PAU20402 PAU2040 PAU20405 PAU20406 PAU20407 PAU20401 PAU20408 COC302 PAC30202 PAC30201 COC301 PAC30102 PAC30101 PAU301012 PAU301011 PAU301010 PAU30109 PAU30108 PAU30107 PAU301013 COU301 PAC30002 COC300 PAU30101 PAU30102 PAU30103 PAU30104 PAU30105 PAU30106 PAU3020C2 PAU3020C1 PAD10001 COD100 PAD10002 PAR20701 COR306 PAR30602 COR307 PAR30701 PAR30702 COR308 PAR30802 PAR30801 PASW20003 PAR30102 COR301 PAR30101 COU204 PAR20502 COR205 PAR20501 PAR20402 COR204 PAR20401 COC204 PAC20402 PAC20401 PAU20108 PAU20107 PAU20106 PAU20109 COU201 PAU20101 PAU20102 PAU20103 PAU20502 COR302 PAR30202 PAR30201 COC208 PAC20802 PAC20801 COR202 PAR20202 PAR20201 PAU20105 PAU20104 PAU20501 COU205 PAM200015 PAC20001 COC200 PAC20002 PAU20503 COR303 PAR30302 PAR30301 COU300 PAU3000C1 PAU3000B1 PAU3000A1 COM200 COC209 PAC20902 PAC20901 PAM200020 PAM200021 PAQ10003 COQ100 PAQ10001 PAQ10002 PAQ10000 PAM200031 PAM200030 PAM200029 PAM200028 PAM200024 COC205 PAC20501 PAC20502 COQ101 PAQ10103 PAQ10101 PAQ10102 PAQ10100 PAU3000C2 PAU3000B2 PAU3000A2 COU302 PAU3020B2 PAU3020B1 PAJ10106 PAJ10100 COR304 PAR30401 PAR30402 COJ101 PAU20202 PAU20209 PAJ10107 PAU20201 PAR20302 COR203 PAR20301 PAJ20008 PAJ20007 PAJ20006 PAJ20005 COJ200 PAJ20004 PAJ20003 PAJ20002 PAJ20000 PAJ20001 PAU3020A2 PAU3020A1 PAM200017 PAM200018 PAM200019 COR212 PAR21202 PAR21201 PAM200016 PAU2017 PAU2018 PAU200019 PAU2020 PAU2021 PAU202 PAU2023 PAU200024 PAU200016 PAU200025 PAQ30001 PAQ30002 PAJ10108 PAJ101010 PAU200015 PAU200014 PAU200013 PAQ30004 PAQ30003 PAU200012 PAU200011 PAU200010 PAU208 PAU207 PAU20006 PAU205 PAU204 PAU203 PAU202 PAU20001 PAJ101011 PAM200027 PAM2026 PAM200025 PAR21302 COR213 PAR21301 PAU200033 PAU200026 PAU200027 COC206 PAC20602 PAC20601 PAU20307 PAU20308 PAU20309 PAU203010 PAU200032 PAR30002 PAR30001 COR300 COQ300 COU200 PAU200028 PAU20306 PAU20305 COU203 PAU203011 PAU203012 PAU20304 PAU20303 PAU20302 PAU20301 PAJ10005 PAJ10006 PAJ10101 PAJ10102 COJ100 PAJ10003 PAJ10004 COC207 PAC20701 PAC20702 PAR10002 COR100 PAR10001 COR101 PAR10101 PAR10102 COR102 PAR10202 PAR10201 PAJ10103 COTP100 PATP10001 COTP207 PATP20701 COTP206 PATP20601 COTP205 PATP20501 COTP204 PATP20401 COTP203 PATP20301 COTP202 PATP20201 COTP201 PATP20101 PAU200029 PAU200030 PAJ10104 PAU200031 PAU20009 COC203 PAC20301 COR201 PAR20101 PAR20102 PAR11401 COR114 PAR11402 COR108 PAR10802 PAR10801 PAJ10105 PAJ10109 PAU20204 PAU20203 COU202 PAU20200 PAU20205 PAU20206 PAU20207 PAU20208 COR200 PAR20001 PAR20002 COR106 PAR10602 PAR10601 COR107 PAR10701 PAR10702 PAR11302 COR113 COQ103 COQ102 PAQ10303 PAQ10203 COR109 PAR10902 PAQ10301 PAQ10201 PAQ10202 PAQ10200 PAR11301 PAR10901 COC103 PAC10302 PAU100016 PAU100015 PAU100014 PAU100013 PAU100012 PAU100011 PAU100017 PAU100033 PAU1018 PAU100019 COU100 PAU100020 PAU1021 PAU100022 PAU1023 PAU1024 PAU100025 PAU100026 PAU100027 PAU100028 PAU100029 PAU100030 PAU100010 PAU100031 PAR20702 COR207 PAR10502 COR105 PAR10501 PAQ10302 PAQ10300 COR115 PAR11501 PAR11502 PAU100032 PASW20002 PASW20004 PASW20001 PASW20005 COR211 PAR21101 PAR11102 COR111 PAR11101 PAR11201 COR112 PAR11202 COR110 PAR11002 PAR11001 PAR10302 COR103 PAR10301 COSW200 PAR10402 COR104 PAR10401 The Microchip Website Microchip provides online support via our website at http://www.microchip.com/. This website is used to make files and information easily available to customers. Some of the content available includes: • Product Support – Data sheets and errata, application notes and sample programs, design resources, user’s guides and hardware support documents, latest software releases and archived software • General Technical Support – Frequently Asked Questions (FAQs), technical support requests, online discussion groups, Microchip design partner program member listing • Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of seminars and events, listings of Microchip sales offices, distributors and factory representatives Product Change Notification Service Microchip’s product change notification service helps keep customers current on Microchip products. Subscribers will receive email notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool of interest. To register, go to http://www.microchip.com/pcn and follow the registration instructions. Customer Support Users of Microchip products can receive assistance through several channels: • Distributor or Representative • Local Sales Office • Embedded Solutions Engineer (ESE) • Technical Support Customers should contact their distributor, representative or ESE for support. Local sales offices are also available to help customers. A listing of sales offices and locations is included in this document. Technical support is available through the website at: http://www.microchip.com/support Microchip Devices Code Protection Feature Note the following details of the code protection feature on Microchip devices: • Microchip products meet the specification contained in their particular Microchip Data Sheet. • Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the intended manner and under normal conditions. • There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft of intellectual property. • Microchip is willing to work with the customer who is concerned about the integrity of their code. • Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not mean that we are guaranteeing the product as “unbreakable.” Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act. Legal Notice Information contained in this publication regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with © 2020 Microchip Technology Inc. User Guide DS50002956A-page 28 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-5767-1 Quality Management System For information regarding Microchip’s Quality Management Systems, please visit http://www.microchip.com/quality. © 2020 Microchip Technology Inc. User Guide DS50002956A-page 29 Worldwide Sales and Service AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE

Corporate Office 2355 West Chandler Blvd. Chandler, AZ 85224-6199 Tel: 480-792-7200 Fax: 480-792-7277 Technical Support: http://www.microchip.com/support Web Address: http://www.microchip.com Atlanta Duluth, GA Tel: 678-957-9614 Fax: 678-957-1455 Austin, TX Tel: 512-257-3370 Boston Westborough, MA Tel: 774-760-0087 Fax: 774-760-0088 Chicago Itasca, IL Tel: 630-285-0071 Fax: 630-285-0075 Dallas Addison, TX Tel: 972-818-7423 Fax: 972-818-2924 Detroit Novi, MI Tel: 248-848-4000 Houston, TX Tel: 281-894-5983 Indianapolis Noblesville, IN Tel: 317-773-8323 Fax: 317-773-5453 Tel: 317-536-2380 Los Angeles Mission Viejo, CA Tel: 949-462-9523 Fax: 949-462-9608 Tel: 951-273-7800 Raleigh, NC Tel: 919-844-7510 New York, NY Tel: 631-435-6000 San Jose, CA Tel: 408-735-9110 Tel: 408-436-4270 Canada - Toronto Tel: 905-695-1980 Fax: 905-695-2078 Australia - Sydney Tel: 61-2-9868-6733 China - Beijing Tel: 86-10-8569-7000 China - Chengdu Tel: 86-28-8665-5511 China - Chongqing Tel: 86-23-8980-9588 China - Dongguan Tel: 86-769-8702-9880 China - Guangzhou Tel: 86-20-8755-8029 China - Hangzhou Tel: 86-571-8792-8115 China - Hong Kong SAR Tel: 852-2943-5100 China - Nanjing Tel: 86-25-8473-2460 China - Qingdao Tel: 86-532-8502-7355 China - Shanghai Tel: 86-21-3326-8000 China - Shenyang Tel: 86-24-2334-2829 China - Shenzhen Tel: 86-755-8864-2200 China - Suzhou Tel: 86-186-6233-1526 China - Wuhan Tel: 86-27-5980-5300 China - Xian Tel: 86-29-8833-7252 China - Xiamen Tel: 86-592-2388138 China - Zhuhai Tel: 86-756-3210040 India - Bangalore Tel: 91-80-3090-4444 India - New Delhi Tel: 91-11-4160-8631 India - Pune Tel: 91-20-4121-0141 Japan - Osaka Tel: 81-6-6152-7160 Japan - Tokyo Tel: 81-3-6880- 3770 Korea - Daegu Tel: 82-53-744-4301 Korea - Seoul Tel: 82-2-554-7200 Malaysia - Kuala Lumpur Tel: 60-3-7651-7906 Malaysia - Penang Tel: 60-4-227-8870 Philippines - Manila Tel: 63-2-634-9065 Singapore Tel: 65-6334-8870 Taiwan - Hsin Chu Tel: 886-3-577-8366 Taiwan - Kaohsiung Tel: 886-7-213-7830 Taiwan - Taipei Tel: 886-2-2508-8600 Thailand - Bangkok Tel: 66-2-694-1351 Vietnam - Ho Chi Minh Tel: 84-28-5448-2100 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 DS50002956A-page 30


FREE ENGLISH PDF

OPERATING INSTRUCTIONS

USER GUIDE - USER MANUAL

OWNER GUIDE - OWNER MANUAL

REFERENCE GUIDE - REFERENCE MANUAL

INSTRUCTION GUIDE - INSTRUCTION MANUAL

Leave a Reply