avr-ble hardware user guide · 2020. 10. 27. · avr-ble hardware avr-ble hardware user guide...

AVR-BLE Hardware AVR-BLE Hardware User Guide

Preface

The AVR-BLE Development Board is a small and easily expandable demonstration and development platform forBluetooth® Low Energy (BLE) solutions based on the AVR® microcontroller architecture. It is designed todemonstrate 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 logicanalyzer channels (debug GPIO).

• A mikroBUS™ socket enables the ability to expand the board capabilities with the selection from 450+ sensorsand actuators options offered by MikroElektronika (www.mikroe.com) via a growing portfolio of Click board™.

© 2020 Microchip Technology Inc. User Guide DS50002956B-page 1

http://www.mikroe.com

Table of Contents

Preface...........................................................................................................................................................1

1. Introduction............................................................................................................................................. 3

1.1. Features....................................................................................................................................... 31.2. Board Overview............................................................................................................................3

2. Getting Started........................................................................................................................................ 6

2.1. Quick Start....................................................................................................................................62.2. Design Documentation and Relevant Links................................................................................. 7

3. Hardware User Guide............................................................................................................................. 8

3.1. On-Board Debugger Overview.....................................................................................................83.2. Power Supply............................................................................................................................. 143.3. Low-Power Operation.................................................................................................................143.4. Target Current Measurement..................................................................................................... 153.5. Peripherals................................................................................................................................. 15

4. Hardware Revision History and Known Issues..................................................................................... 22

4.1. Identifying Product ID and Revision........................................................................................... 224.2. Revision 3...................................................................................................................................224.3. Revision 2...................................................................................................................................22

5. Document Revision History...................................................................................................................23

6. Appendix............................................................................................................................................... 24

6.1. Schematics.................................................................................................................................246.2. Assembly Drawing......................................................................................................................27

The Microchip Website.................................................................................................................................28

Product Change Notification Service............................................................................................................28

Customer Support........................................................................................................................................ 28

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

Legal Notice................................................................................................................................................. 29

Trademarks.................................................................................................................................................. 29

Quality Management System....................................................................................................................... 30

Worldwide Sales and Service.......................................................................................................................31

AVR-BLE Hardware


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 CryptoAuthentication™ 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 OverviewThe AVR-BLE development board is a hardware platform that is being used to evaluate the ATmega3208 AVRmicrocontroller and RN4870 BLE module.

Figure 1-1. AVR-BLE Development Board Front Side

Micro-USBConnector

DebuggerPower/Status LED

ATECC6080ACrypto

Data LED (Green)

Error LED(Red)

SST25PF040CT Serial Flash

USB/Battery MUX

BLE LED (Blue)

MCP9844 Temp-sensor

BMA253 Accelerometer

ATmega3208 MCU

User Switch (SW0)

RN4870 BLE module

AVR-BLE HardwareIntroduction


Figure 1-2. AVR-BLE Development Board Back Side

CR2032 Battery Holder

Additional RN4870 GPIO



Figure 1-3. AVR-BLE Quick Reference Overview

AVR-

BLE

Deve

lopm

ent B

oard

(DT1

0011

1)

CD

C R

X

CD

C T

X

DEB

UG

GPI

O0

PF0

| USA

RT2

TX

PF1

| USA

RT2

RX

PF3

I2 C S

CL

I2 C S

DA

PA3

PA2

BLE

MO

DE

BLE

RST

BLE

RX

PF3

PD3

PA0

| USA

RT0

TX

BLE

TX

PA1

| USA

RT0

RX

HO

LD#

SPI C

S

SPI S

CK

PD4

PD0

PA6

SPI M

ISO

PA5

I2 C S

CL

I2 C S

DA

BM

A 2

53 IN

T1

PA3

PA2

PC2

I2 C S

CL

I2 C S

DA

PA3

PA2

DEB

UG

GPI

O1

PF4

EVEN

TPF

2

SPI M

OSI

PA4

BM

A 2

53 IN

T2PC

3

MIC

3305

0 D

C/D

C C

onve

rter

BM

A25

3 A

ccel

erat

ion

Sens

or

ATE

CC

608A

Sec

ure

Elem

ent

PD1

PD6

PC1

PC0

PA3

PA2

5.0V

GN

D

SST2

5PF0

40C

4M

B F

LASH

PF4

PF5

Mic

ro U

SB C

onne

ctor

PKoB

Nan

o D

ebug

ger/

Prog

ram

mer

MC

P984

4 Te

mpe

ratu

re S

enso

r

AN

RST

SPI C

S

SPI S

CK

SPI M

ISO

SPI M

OSI

3.3V

GN

D

ATm

ega3

208

MC

U

Use

r Sw

itch

0

RN

4870

Blu

etoo

th L

ow E

nerg

y M

odul

e

PD7

PD5

PA7

PA6

PA5

PA4

PF3

PWM

INT

USA

RT1

RX

USA

RT1

TX

I2 C S

CL

I2 C S

DA

DA

TA L

ED

ERRO

R LE

D

RN

4870

P1_

1BL

E ST

ATU

S

GR

EEN

RED

BLUE



2. Getting Started

2.1 Quick StartDemo Application

Out of the box, the AVR-BLE board comes programmed with the avr-lightblue-explorer-demo. This application can beused to demonstrate a number of the board features using the LightBlue® app by Punch Through.

1. Download the latest demo firmware from the releases section on avr-lightblue-explorer-demo GitHub page.2. Connect a USB cable (Standard-A to Micro-B or Micro-AB) between the PC and the debug USB port on the

board.3. Program the AVR-BLE with the downloaded .hex file through the drag-and-drop feature.4. Download the LightBlue® app for iOS or Android.5. Power the board through a Micro-USB cable or CR2032 battery.6. Open the LightBlue® app and select the AVR-BLE peripheral.7. 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 twobytes of the RN4870 BLE module’s Bluetooth MAC address. This makes it possible to distinguish betweenmultiple AVR-BLE boards.

Communication between the demo application and the LightBlue® app is done by using a protocol based on ASCIIpackets. 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 thissource 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 InstallationWhen the board connects to your computer for the first time, the operating system will perform a driver softwareinstallation. The driver file supports both 32- and 64-bit versions of Microsoft® Windows® XP, Windows Vista®,Windows 7, Windows 8, and Windows 10. The drivers for the board are included with both MPLAB® X IDE and AtmelStudio 7.

Kit WindowOnce the board is powered, the green status LED will lit, and both MPLAB® X IDE and Atmel Studio 7 will auto-detectwhich boards are connected. The Kit Window in MPLAB® X IDE and Atmel Studio 7 will present relevant information

AVR-BLE HardwareGetting Started


https://github.com/microchip-pic-avr-solutions/avr-lightblue-explorer-demohttps://punchthrough.com/https://github.com/microchip-pic-avr-solutions/avr-lightblue-explorer-demohttps://apps.apple.com/us/app/lightblue-explorer/id557428110https://play.google.com/store/apps/details?id=com.punchthrough.lightblueexplorerhttps://github.com/microchip-pic-avr-solutions/avr-lightblue-explorer-demohttps://www.microchip.com/mplab/mplab-x-idehttps://www.microchip.com/mplab/compilershttps://microchipdeveloper.com/mplabx:installationhttps://github.com/microchip-pic-avr-solutions/avr-lightblue-explorer-demo

like data sheets and board documentation. The ATmega3208 device on the AVR-BLE board is programmed anddebugged by the on-board debugger and, therefore, no external programmer or debugger tool is required.

Tip: If closed the Kit Window in MPLAB® X IDE can be reopened through the menu bar Window > KitWindow.

2.2 Design Documentation and Relevant LinksThe 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®) todevelop applications for Microchip microcontrollers and digital signal controllers. It is called an IntegratedDevelopment Environment (IDE) because it provides a single integrated “environment” to develop code forembedded 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 versionavailable from their website.

• MPLAB® XC Compilers - MPLAB® XC8 C Compiler is available as a free, unrestricted-use download.Microchips MPLAB® XC8 C Compiler is a comprehensive solution for your project’s software development onWindows®, macOS® or Linux®. MPLAB® XC8 supports all 8-bit PIC® and AVR® microcontrollers (MCUs).

• MPLAB® Xpress Cloud-based IDE - MPLAB Xpress Cloud-Based IDE is an online development environmentthat contains the most popular features of our award-winning MPLAB X IDE. This simplified and distilledapplication is a faithful reproduction of our desktop-based program, which allows users to easily transitionbetween the two environments.

• MPLAB® Code Configurator - MPLAB Code Configurator (MCC) is a free software plug-in that provides agraphical 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 configuresoftware 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 DataGateway 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. TheData Visualizer can receive data from various sources such as serial ports, on-board debugger’s Data GatewayInterface 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 examplesand 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 completeapplications 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.

AVR-BLE HardwareGetting Started


https://www.microchip.com/mplab/mplab-x-idehttps://www.microchip.com/development-tools/atmel-studio-7https://www.microchip.com/DevelopmentTools/ProductDetails/PartNO/IAR%20EW%20for%20AVRhttps://www.microchip.com/mplab/compilershttps://www.microchip.com/mplab/mplab-xpresshttps://www.microchip.com/mplab/mplab-code-configuratorhttps://www.microchip.com/starthttps://www.microchip.com/samples/default.aspxhttps://gallery.microchip.com/packages?q=MPLAB-Data-Visualizerhttps://www.microchip.com/mplab/avr-support/data-visualizerhttps://github.com/microchip-pic-avr-exampleshttps://github.com/microchip-pic-avr-solutionshttp://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=DT100111http://www.microchipdirect.com/ProductSearch.aspx?Keywords=DT100111

3. Hardware User Guide

3.1 On-Board Debugger OverviewAVR-BLE contains an on-board debugger for programming and debugging. The on-board debugger is a compositeUSB device consisting of several interfaces:

• A debugger that can program and debug the ATmega3208 in both MPLAB® X IDE and Atmel Studio 7• 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 belowshows 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-dropprogramming 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 DebuggerThe on-board debugger on the AVR-BLE board appears as a Human Interface Device (HID) on the host computer’sUSB subsystem. The debugger supports full-featured programming and debugging of the ATmega3208 using bothMPLAB® X IDE and Atmel Studio 7, as well as some third-party IDEs.

Remember: Keep the debugger’s firmware up-to-date. Firmware upgrades automatically when usingMPLAB® X IDE or Atmel Studio 7.

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.

AVR-BLE HardwareHardware User Guide


3.1.2.1 OverviewThe 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 inboth directions between the host computer and the target: All characters sent through the virtual serial port on thehost computer will be transmitted as UART on the debugger’s CDC TX pin, and UART characters captured on thedebugger’s CDC RX pin will be returned to the host computer through the virtual serial port.

Figure 3-1. CDC Connection

Target MCU

UART TX

UART RX

Debugger

USBCDC RX

CDC TX

PCTerminalSoftware

TargetReceive

TargetSend

TerminalReceive

TerminalSend

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

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

Info: On older Windows systems, the CDC requires a USB. This driver is included in installations of bothMPLAB® X IDE and Atmel Studio 7.

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

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

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

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

3.1.2.3 LimitationsNot 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 theclosest 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 SignalingDuring USB enumeration, the host OS will start both communication and data pipes of the CDC interface. At thispoint, it is possible to set and read back the baud rate and other UART parameters of the CDC, but data sending andreceiving will not be enabled.

When a terminal connects on the host, it must assert the DTR signal. As this is a virtual control signal implementedon the USB interface, it is not physically present on the board. Asserting the DTR signal from the host will indicate tothe on-board debugger that a CDC session is active. The debugger will then enable its level shifters (if available) andstart the CDC data send and receive mechanisms.

Deasserting DTR in debugger firmware version 1.20 or earlier has the following behavior:• Debugger UART receiver is disabled, so no further data will be transferred to the host computer• Debugger UART transmitter will continue to send data that is queued for sending, but no new data is accepted

from the host computer• Level shifters (if available) are not disabled, so the debugger CDC TX line remains driven

Deasserting DTR in debugger firmware version 1.21 or later has the following behavior:• Debugger UART receiver is disabled, so no further data will be transferred to the host computer• Debugger UART transmitter will continue to send data that is queued for sending, but no new data is accepted

from the host computer• Once the ongoing transmission is complete, level shifters (if available) are disabled, so the debugger CDC TX

line will become high-impedance

Remember: Set up the terminal emulator to assert the DTR signal. Without the signal, the on-boarddebugger 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 thehost computer. Also, there are no external pull-up resistors on the CDC lines connecting the debugger andthe target, which means that during power-up, these lines are floating. To avoid any glitches resulting inunpredictable behavior like framing errors, the target device should enable the internal pull-up resistor onthe pin connected to the debugger’s CDC TX pin.

3.1.2.5 Advanced Use

CDC Override ModeIn normal operation, the on-board debugger is a true UART bridge between the host and the device. However, incertain use cases, the on-board debugger can override the basic operating mode and use the CDC TX and RX pinsfor other purposes.

Dropping a text file into the on-board debugger’s mass storage drive can be used to send characters out of thedebugger’s CDC TX pin. The filename and extension are trivial, but the text file must start with the characters:CMD:SEND_UART=

Debugger firmware version 1.20 or earlier has the following limitations:• The maximum message length is 50 characters – all remaining data in the frame are ignored• The default baud rate used in this mode is 9600 bps, but if the CDC is already active or has been configured,

the previously used baud rate still applies

Debugger firmware version 1.21 and later has the following limitations/features:



• The maximum message length may vary depending on the MSC/SCSI layer timeouts on the host computerand/or operating system. A single SCSI frame of 512 bytes (498 characters of payload) is ensured, and files ofup to 4 KB will work on most systems. The transfer will complete on the first NULL character encountered in thefile.

• The baud rate used is always 9600 bps for the default command:CMD:SEND_UART=

• The CDC override mode should not be used simultaneously with data transfer over the CDC/terminal. If a CDCterminal session is active at the time a file is received via CDC override mode, it will be suspended for theduration 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 ConsiderationsSending data from the host to the CDC can be done byte-wise or in blocks, which will be chunked into 64-byte USBframes. Each such frame will be queued up for sending to the debugger’s CDC TX pin. Transferring a small amountof data per frame can be inefficient, particularly at low baud rates, as the on-board debugger buffers frames and notbytes. A maximum of four 64-byte frames can be active at any time. The on-board debugger will throttle the incomingframes 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 into64-byte frames, which are sent to the USB queue for transmission to the host when they are full. Incomplete framesare also pushed to the USB queue at approximately 100 ms intervals, triggered by USB start-of-frame tokens. Up toeight 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 data frame will be lost.To prevent this occurrence, the user must ensure that the CDC data pipe is being read continuously, or the incomingdata rate must be reduced.

3.1.3 Mass Storage DeviceThe on-board debugger includes a simple Mass Storage Device implementation, which is accessible for read/writeoperations 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 ImplementationThe 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, fulfillthe 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 Devicethat can be found in the disk drives section of the device manager. The CURIOSITY drive appears in the file managerand claims the next available drive letter in the system.

The CURIOSITY drive contains approximately one MB of free space, and this does not reflect the size of the targetdevice’s Flash in any way. When programming an Intel® HEX file, the binary data are encoded in ASCII withmetadata 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 inthe disk directory listing. This is merely the operating system’s view of the directory, which in reality, has not beenupdated. It is not possible to read out the file contents. Removing and replugging the board will return the file systemto 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 andlinking 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 bythe OS and, therefore, do not reflect the correct status.

3.1.3.2 Limitations of Drag-and-Drop Programming

Lock BitsLock bits included in the hex file will be ignored when using drag-and-drop programming. To program lock bits, useMPLAB® X IDE or Atmel Studio 7.

Enabling CRC Check in FusesIt is not advisable to enable the CRC check in the target device’s fuses when using drag-and-drop programming. Thisbecause a subsequent chip erase (which does not affect fuse bits) will effect a CRC mismatch, and the applicationwill fail to boot. To recover a target from this state, a chip erase must be done using MPLAB® X IDE orAtmel Studio 7, which will automatically clear the CRC fuses after erasing.

3.1.3.3 Special CommandsSeveral utility commands are supported by copying text files to the mass storage disk. The filename or extension isirrelevant – the command handler reacts to content only.

Table 3-2. Special File Commands

Command Content Description

CMD:ERASE Executes a chip erase of the targetCMD:SEND_UART= Sends a string of characters to the CDC UART. See “CDC

Override Mode.”

CMD:SEND_9600=CMD:SEND_115200=CMD:SEND_460800=

Sends a string of characters to the CDC UART at the baud ratespecified. Note that only the baud rates explicitly specified hereare supported! See “CDC Override Mode” (Debugger firmwarev1.21 or newer.)

CMD:RESET Resets the target device by entering Programming mode andthen exiting Programming mode immediately afterward. Exacttiming can vary according to the programming interface of thetarget device. (Debugger firmware v1.16 or newer.)



Info: The commands listed here are triggered by the content sent to the mass storage emulated disk, andno 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-boarddebuggers and host computer-based visualization tools. MPLAB Data Visualizer is used on the host computer todisplay debug GPIO data. It is available as a plug-in for MPLAB® X IDE or a stand-alone application that can be usedin parallel with MPLAB® X IDE or Atmel Studio 7.

Although DGI encompasses several physical data interfaces, the AVR-BLE implementation includes logic analyzerchannels:

• Two debug GPIO channels (also known as DGI GPIO)

3.1.4.1 Debug GPIODebug GPIO channels are timestamped digital signal lines connecting the target application to a host computervisualization application. They are typically used to plot the occurrence of low-frequency events on a time-axis – forexample, 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 inMPLAB 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 theDGI timestamp module.

Important: Although bursts of higher-frequency signals can be captured, the useful frequency range ofsignals for which debug GPIO can be used is up to about 2 kHz. Attempting to capture signals above thisfrequency will result in data saturation and overflow, which may cause the DGI session to be aborted.

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



https://gallery.microchip.com/packages?q=MPLAB-Data-Visualizer

3.2 Power SupplyThe board can be powered through the USB port or by a CR2032 battery. It will automatically switch to the battery ifUSB 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, whilethe 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 theATmega3208 pins that connect to the CDC UART in Tri-State (Input) mode. This is to prevent thedebugger from getting powered through its GPIO.

Figure 3-3. Power Supply Block Diagram

USB On-BoardDebugger

Power source

Power disconnect

Power consumer

Power converter

VUSBMIC33050

(buck)

MUX(MIC94050)(MIC94165)

Power MUX

Battery Holder

(CR2032)

VCC_P3V3

VBAT

VBAT_OUT

0Ω resistor

Target MCU

Peripherals mBUS

RN4870

0Ω resistorP3V3_ENABLE

Info: On the mikroBUS socket, the +5V rail is powered from the USB port. Consequently, +5V will not beavailable when the board is powered from a battery.

3.3 Low-Power OperationTo 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 totri-state the USART pins when the board is powered from a CR2032 battery to prevent powering thedebugger through its I/O pins. Doing so will increase the power consumption and cause undefinedbehavior 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 abattery. By modifying the board and removing resistor R303 (0Ω), U300 can be disconnected. Be warnedthat a board modified this way can no longer be powered from USB, and consequently, neitherprogrammed nor debugged using the on-board debugger until the 0Ω resistor is reconnected.

3.4 Target Current MeasurementPower 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). Tomeasure the power consumption of the ATmega3208 and other peripherals on the board, de-solder the 0Ω resistorand connect an ammeter over the Current sense footprint.

Figure 3-4. Current sense footprint

0Ω resistor(R301)

Current sense footprint(J301)

Tip: A 100-mil pin header can be soldered into the Current sense (J301) footprint for easy connection ofan ammeter. Once the ammeter is not needed anymore, place a jumper cap on the pin header.

3.5 Peripherals

3.5.1 ATmega3208Microchip ATmega3208 is a microcontroller featuring the AVR® processor with hardware multiplier – running at up to20 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-powerfeatures, including Event System, accurate analog features, and advanced peripherals.



3.5.2 mikroBUS SocketFigure 3-5. mikroBUS Socket Pinout

AN PWMRST INTCS RXSCK TXMISO SCLMOSI SDA+3.3V +5VGND GND

PD7 PD1

PD5 PD6

PA7 PC1

PA6 PC0

PA5 PA3

PA4 PA2

VCC VBUS

GND GND

The AVR-BLE board features a mikroBUS socket for expanding the functionality of the development board usingMikroElektronika Click Boards and other mikroBUS add-on boards. The socket is populated with two 1x8 2.54 mmpitch 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 —



Info: VBUS is powered from USB. Consequently, +5V will not be available while the board is poweredfrom a battery.

Info: VCC_TARGET will have the battery voltage when the board is powered from a battery, which canbe less that +3.3V.

3.5.3 RN4870 BLE ModuleThe 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 andconfiguring of the module. The RST signals resets the module, while the RX_IND signal is used to wake the modulefrom Low-Power mode. The MODE signal, available from the ATmega3208, the debugger as well as by a physicalswitch, 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 theuser can configure it for a number of other functions. Many of the other RN4870 GPIO pins are available as padsaround 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 settingshave 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.



3.5.4 ATECC608A Secure ElementThe ATECC608A is a secure element from the Microchip CryptoAuthentication portfolio with advanced Elliptic CurveCryptography (ECC) capabilities. With ECDH and ECDSA being built right in, this device is ideal for the rapidlygrowing Internet of Things (IoT) market by easily supplying the full range of security, such as confidentiality, dataintegrity, and authentication to systems with MCU or MPUs running encryption/decryption algorithms. Similar to allMicrochip CryptoAuthentication products, the ATECC608A employs ultra-secure, hardware-based cryptographic keystorage 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 withother 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 FlashThe 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

SST25PF040CTPin

ATmega3208 Pin Function Shared Functionality

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 SensorThe MCP9844 digital temperature sensor converts circuit board temperatures between -40°C and +125°C to a digitalword with ±1°C/±3°C (typical/maximum) accuracy.

Additional features:



• 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 SensorThe Bosch BMA253 is a low-g acceleration sensor with digital output for measurements of acceleration in threeperpendicular 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



• 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 userconfigurable 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 LEDsThere 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/Olines 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 SwitchThe AVR-BLE board has one mechanical switch. This is a generic user-configurable switch that will drive theconnected I/O line to ground (GND) when it is pressed. An external resistor pulls the signal high when the switch isnot 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-boarddebugger

Info: The SW0 signal is pulled up by an external resistor.



3.5.10 On-Board Debugger ImplementationAVR-BLE features an on-board debugger that can be used to program and debug the ATmega3208 using UPDI. Theon-board debugger also includes a virtual serial port (CDC) interface over UART and debug GPIO. Both MPLAB® XIDE and Atmel Studio 7 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 ConnectionsThe table below shows the connections between the target and the debugger section. All connections between thetarget and the debugger are tri-stated as long as the debugger is not actively using the interface. Hence, since thereare 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 DebuggerOverview.

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



https://gallery.microchip.com/packages?q=MPLAB-Data-Visualizer

4. Hardware Revision History and Known IssuesThis user guide is provides information about the latest available revision of the board. The following sections containinformation about known issues, a revision history of older revisions, and how older revisions differ from the latestrevision.

4.1 Identifying Product ID and RevisionThere are two ways to find the revision and product identifier of the AVR-BLE: Either by utilizing the MPLAB® X IDEor Atmel Studio 7 Kit Window or by looking at the sticker on the bottom side of the PCB.

By connecting AVR-BLE to a computer with MPLAB® X IDE or Atmel Studio 7 running, the Kit Window will pop up.The first six digits of the serial number, listed under kit information, contain the product identifier and revision.

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

The same information is found on the sticker on the bottom side of the PCB. Most boards will have the identifier andrevision printed in plain text as A09-nnnn\rr, where “nnnn” is the identifier, and “rr” is the revision. Boards with limitedspace 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 3Revision 3 is functionally the same as revision 2, but features a RN4870 BLE module with firmware version 1.40 (partnumber RN4870-V/RM140).

In the silkscreen, the part number of the serial flash chip is wrong. It should be SST25PF040C, but showsSST25P040C.

4.3 Revision 2Revision 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).

AVR-BLE HardwareHardware Revision History and Known Issues


5. Document Revision HistoryRevision Date Description

B 10/2020 Document updated with the latest information. Steps describing how to downloadand install the latest demonstration firmware added to the Quick Start section.

A 03/2020 Initial document release

AVR-BLE HardwareDocument Revision History


6. Appendix

6.1 SchematicsFigure 6-1. AVR-BLE Target schematic

11

22

33

44

55

66

77

88

DD

CC

BB

AA

2 of

5

AVR-

BLE

2020

-01-

09AV

R-BL

E_Ta

rget

_MCU

.Sch

Doc

Proj

ect T

itle

PCB

Ass

embl

y N

umbe

r:PC

BA R

evisi

on:

File

:PC

B N

umbe

r:PC

B Re

visio

n:

Des

igne

d wi

th

Dra

wn

By:

Mic

roch

ip N

orw

ay

Shee

t Titl

eTa

rget

MCU

Engi

neer

:TF

A08

-303

82

Size

A3

A09

-331

43

Page

:D

ate:A

ltium

.com

GN

D10

0nC2

00

1kR2

10

USE

R L

EDS

VCC

_TA

RGET

PF3_SW0_DGI_FW

USE

R B

UTT

ON

DBG0

CDC_

UART

TX RXU

ART

DBG1

DBG2

2185-108SS0CYNP1

1 2 3 4 5 6 7 8

J200

2185-108SS0CYNP1

1 2 3 4 5 6 7 8

J201

mik

roBU

S

GN

DG

ND

AN

RST

CS SCK

MIS

OM

OSI

+3.3

VG

ND

PWM

INT

RX TX SCL

SDA

+5V

GN

D

Hea

der (

Fem

ale)

TMRN48

7010

uF/1

0VC2

0210

nFC2

01

330RR207 12

4 3

5

KMR221G

SW20

01k

R2091k

R208

GN

D

SDA

5SC

L6

GND

4

VCC

8

PAD

9

NC1

NC2

NC3

NC7

U20

1

GN

D

GN

D

100kR201

VCC

_TA

RGET

VCC

_TA

RGET

PA3_

I2C_

SCL

PA2_

I2C_

SDA

VCC

_TA

RGET

GN

D

100n

C204

Cry

ptoA

uthe

ntic

atio

nTM

Tem

pera

ture

Sen

sor

GN

D

VCC

_TA

RGET

4.7kR204

4.7kR205

VCC

_TA

RGET

VCC

_TA

RGET

TP21

1

TP20

3

TP21

0

TP21

2

TP20

8

21

GRE

EN L

EDSM

L-P1

2MTT

86R

D20

0 RED

LED

SML-

P12V

TT86

R

21

D20

1

Def

ault

I2C

addr

ess:

0x18

PD5_

MBU

S_RS

T

PA3_I2C_SCLPA2_I2C_SDA

PD7_

MBU

S_A

INPD

6_M

BUS_

INT

Def

ault

I2C

addr

ess:

0x58

21

BLU

E LE

DSM

LP13

BC8T

T86

D20

2

VCC

_TA

RGET

GN

D

PC0_

UA

RT1_

TXPC

1_U

ART

1_RX

TP21

4

100n

C205

SW0

VBU

S0R R2

06+5

V

TP21

3

TP20

9

DATA

ATEC

C608

A

DBG3

PA3_I2C_SCLPA2_I2C_SDA

VCC

_TA

RGET

PD2_

BLE_

RX_I

ND

10kR200 N

.M.

3-ax

ial A

ccel

erat

ion

Sens

or

VCC

_TA

RGET

GN

D 100n

C206 GN

D

100nC207

GN

D

Alte

rnat

e I2

C ad

dres

s: 0x

19

VCC

_TA

RGET

PA3_I2C_SCL

PA2_I2C_SDA

1uF

C203

GN

D

ATm

ega3

208

PC2_

ACC

L_IN

T1

MCP

9844

SDA

5SC

L6

EVEN

T7

GND

4A2

3A1

2A0

1VD

D8

EP 9

U20

2

PA5_

SPI_

MIS

OPA

6_SP

I_SC

K

PA4_

SPI_

MO

SI

PA7_

SPI_

CS

SDO/

ASEL

1

SDx

2

VDDI

O3

NC4

INT1 5

INT2 6

VDD

7GN

DIO

8GN

D9

CSB

10

PS11SCx12

BMA

253

U20

3

512k

x 8

Ser

ial F

lash

VCC

_TA

RGET

GN

D

100n

C208

GN

D

VCC

_TA

RGET

PF5_ERR_LED

PD1_

MBU

S_PW

M

PF4_DATA_LED_DGI

BLE

ERR

PF3_

SW0_

DG

I_FW

TP20

1

PD0_SPI_CSPA5_SPI_MISO

PA6_SPI_SCKPA4_SPI_MOSI

VCC

_TA

RGET

TP20

7TP

206

TP20

2TP

204

TP20

5PA

31

(EXTCLK)PA030 PA131 PA232

PA4

2PA

53

PA6

4PA

75

PC0

6PC

17

PC2

8

PC3 9PD0 10PD1 11PD2 12PD3 13PD4 14PD5 15PD6 16

PD7

17AV

DD18

GND

19(T

OSC1

) PF

020

(TOS

C2)

PF1

21PF

222

PF3

23PF

424

PF525 PF626 UPDI27 VDD28 GND29

PAD

33

ATm

ega3

208-

MFR

U20

0

10kR212

PF6_RST

PA7_

SPI_

CSPA

6_SP

I_SC

KPA

5_SP

I_M

ISO

PA4_

SPI_

MO

SI

GN

D

PF1_

CDC_

UA

RT2_

RX

PF4_

DA

TA_L

ED_D

GI

PD7_

MBU

S_A

IN

PF0_

CDC_

UA

RT2_

TX

PA3_

I2C_

SCL

PF3_

SW0_

DG

I_FW

PD5_

MBU

S_RS

TPD

4_H

OLD

#PD

3_BL

E_RS

TPD

0_SP

I_CS

PD2_

BLE_

RX_I

ND

PD6_

MBU

S_IN

T

PA2_I2C_SDA

PA0_BLE_UART0_TXPA1_BLE_UART0_RX

PA1_

BLE_

UA

RT0_

RXPA

0_BL

E_U

ART

0_TX

UPDI

PF5_ERR_LED

BLE_LED

BLE_

LED

PF2_

EVEN

T

PF2_EVENT

PC0_

UA

RT1_

TXPC

1_U

ART

1_RX

PC2_

ACC

L_IN

T1

PD3_

BLE_

RST

VCC

_TA

RGET

PC3_

ACC

L_IN

T2

PC3_

ACC

L_IN

T2

PD4_HOLD#

PD1_

MBU

S_PW

M

10kR202

CE#

1SO

/SIO

12

WP#

3VS

S4

VDD

8HO

LD#

7SC

K6

SI/S

IO0

5

SST2

5PF0

40CT

-40I

/NP

U20

4

P2_0

/MO

DE

pin

has a

n in

tern

al p

ull-u

p of

abo

ut

50ko

hm.

UPD

IPF

6_RS

T

10k

R211

VCC

_TA

RGET

PC2_

ACC

L_IN

T1

0RR203 0R R213

VDD

3VO

UT1

VSS

2

MCP

111T

-195

U20

5 N.M

.

GN

D

VCC

_TA

RGET

RTS

CTS

P02

P07

P12

P13

P27

P35

PCO

BKO

PF3_

SW0_

DG

I_FW

PF4_

DA

TA_L

ED_D

GI

RN48

70_T

XRN

4870

_RX

Cros

sing

RX/T

X h

ere!

RN48

70_R

XRN

4870

_TX

PF3_

SW0_

DG

I_FW

100n

C209

GN

D GN

D

Mak

e su

re th

at th

e CD

C U

ART

pin

s are

not

use

d (d

riven

hig

h) w

hen

oper

atin

g in

bat

tery

mod

e to

av

oid

pow

erin

g th

e de

bugg

er th

roug

h its

I/O

pin

s (c

ausin

g le

akag

e fro

m V

CC_T

ARG

ET to

V

CC_D

EBU

GG

ER).

GN

D1

GN

D2

GN

D3

VBA

T4

P2_2

5

VD

D_I

O6

VD

D_I

O7

ULP

C_O

8

P2_3

9

BK_O

10

P1_1

12P1

_016

P3_6

/RTS

17

P2_0

/MO

DE

18

P2_4

19

NC

20

RST

21

UA

RT_R

X22

UA

RT_T

X23

P3_1

24

P3_2

25

P3_3

26

P3_4

27

P3_5

28

P0_7

29P0

_230

GN

D31

GN

D32

GN

D33

P2_7

/TX

_IN

D11

P1_2

/SCL

13

P1_3

/SD

A14

P0_0

/CTS

15

RN48

70-V

/RM

140

M20

0

AVR-BLE HardwareAppendix


Figure 6-2. AVR-BLE Power Schematic

11

22

33

44

55

66

77

88

DD

CC

BB

AA

3 of

5

AVR-

BLE

2020

-01-

09AV

R-BL

E_Po

wer

.Sch

Doc

Proj

ect T

itle

PCB

Ass

embl

y N

umbe

r:PC

BA R

evisi

on:

File

:PC

B N

umbe

r:PC

B Re

visio

n:

Des

igne

d wi

th

Dra

wn

By:

Mic

roch

ip N

orw

ay

Shee

t Titl

ePo

wer

Engi

neer

:TF

A08

-303

82

Size

A3

A09

-331

43

Page

:D

ate:A

ltium

.com

VCC

_P3V

3

GN

D

4.7uF

C300

GN

D

560p

C301

SW4

PGND 2

VOUT

7

SNS

10EN

9VO

UT8

SW5

VIN

1

AGND 12

EP 13

SW3

SW6

FB/C

FF11

MIC

3305

0-SY

HL

U30

1

100kR305

10uF

/10V

C302

GN

D

GN

D

VCC

_DEB

UG

GER

VCC

_TA

RGET

12CH7410-2032LF

J300

VBU

S

MIC

9416

5

VIN

B2VO

UTA1

VIN

A2

ENC2

GND

C1VO

UTB1

U30

0

MIC

9416

5

VIN

B2VO

UTA1

VIN

A2

ENC2

GND

C1VO

UTB1

U30

2

GN

D

GN

D

GN

D

GN

D

2MR3

00

VBA

T0R

R301 0R

R304

12

1125

-110

2S0S

113R

1J3

01

N.M

.

2

1

4SS

G

DS

3

MIC

9405

0Q

300

0RR303

1kR306

P3V

3_EN

ABL

EVBA

T_O

UT

21

NSR

20F3

0NX

T5G

D30

0

GN

D1kR308

2.2k

R307

5.6kR302

VBU

Smin

= 4

.4V

-> P

3V3_

ENA

BLE

= 3.

16V

, V

BUSm

ax =

5.2

5V ->

P3V

3_EN

ABL

E =

3.77

V

POW

ER

MIC

3305

0:Vi

n: 2

.5V

to 5

.5V

Vout

: Fix

ed 3

.3V

Imax

: 600

mA



Figure 6-3. AVR-BLE Debugger Schematic

11

22

33

44

55

66

77

88

DD

CC

BB

AA

4 of

5

AVR-

BLE

2020

-01-

09AV

R-BL

E_D

ebug

ger.S

chD

oc

Proj

ect T

itle

PCB

Ass

embl

y N

umbe

r:PC

BA R

evisi

on:

File

:PC

B N

umbe

r:PC

B Re

visio

n:

Des

igne

d wi

th

Dra

wn

By:

Mic

roch

ip N

orw

ay

Shee

t Titl

eD

ebug

ger

Engi

neer

:TF

A08

-303

82

Size

A3

A09

-331

43

Page

:D

ate:A

ltium

.com

DEB

UG

GER

USB

MIC

RO

-B C

ON

NEC

TOR

GN

D

USB

D_P

USB

D_N

100n

C102

100n

C103

RX TXU

ART

CDC_

UART

1kR1

00V

CC_D

EBU

GG

ER

SRST

STAT

US_

LED

SHIE

LD

VBU

S

VCC

_DEB

UG

GER

GN

D

TP10

0

Testp

oint

Arra

y

12

34

56

78

910

TCK

TDO

TMS

Vsu

pTD

IG

ND

TRST

SRST

VTr

efG

ND

J100

DBG0

21

GRE

EN L

EDSM

L-P1

2MTT

86R

D10

0

VBUS

1D-

2D+

3

GND

5SH

IELD

16

SHIE

LD2

7

ID4

SHIE

LD3

8SH

IELD

49 M

U-M

B014

2AB2

-269

J101

PAD

33

PA00

1PA

012

PA02

3PA

034

GND 10VDDANA 9

PA04

5PA

056

PA06

7PA

078

PA08 11PA09 12PA10 13PA11 14PA14 15PA15 16

PA16

17PA

1718

PA18

19PA

1920

PA22

21US

B_SO

F/PA

2322

USB_

DM/P

A24

23US

B_DP

/PA2

524

PA2725 RESETN26 PA2827 GND28 VDDCORE29 VDDIN30 SWDCLK/PA3031 SWDIO/PA3132

SAM

D21

E18A

-MU

TU

100

USB

D_P

USB

D_N

1uC101

VCC

_MCU

_CO

RE

VCC

_DEB

UG

GER

VCC

_DEB

UG

GER

GN

D GN

D

GN

DG

ND

DBG2

S1_0

_TX

S0_2

_TX

DA

CV

TG_A

DC

RESE

RVED

S0_3

_CLK

DBG0_CTRL

CDC_

TX_C

TRL

BOO

T

DEB

UG

GER

PO

WER

/STA

TUS

LED

1kR1

04

DBG1

DBG1_CTRL

REG_ENABLE

100kR101

100kR102

SWCL

K

100kR109 G

ND

SRST

DEB

UG

GER

TES

TPO

INT DBG2_CTRL

CDC_

RX_C

TRL

100kR106

SWCL

K

DBG2_GPIO

VBUS_ADC

VTG_ADC

ID_S

YS

VTG

_EN

VBU

S_A

DC

SWD

IO

SWD

IO

GN

DV

OFF

VCC

_DEB

UG

GER

330R

R107330R

R105330R

R103

Cros

sing

RX/T

X h

ere!

DBG

0

DBG

2

S1_1

_RX

S0_0

_RX

DBG

1

DBG3

GN

D

DBG

3_CT

RL1

23

DM

N65

D8L

FBQ

100

N.M

.

1kR1

08 N.M

.

DBG

3_CT

RL

DBG

3 O

PEN

DR

AIN

Sign

al

DBG

0

DBG

1

DBG

2

DBG

3

UPD

IIn

terfa

ce

UPD

I

GPI

O

GPI

O

(RES

ET)

CD

C T

X

CD

C R

X

UA

RT R

X

UA

RT T

X

TAR

GET

VC

C-

MC3

6213

F100

VCC

_VBU

S

Targ

et a

nd d

ebug

ger

VCC

is th

e sa

me.

330R

R110 330R

R111

1

23

DM

N65

D8L

FBQ

102

1

23

DM

N65

D8L

FBQ

101

VCC

_DEB

UG

GER

VCC

_DEB

UG

GER

100kR112

VCC

_DEB

UG

GER

VCC

_DEB

UG

GER

100kR113

100k

R114 N.M

.

1

23

DM

N65

D8L

FBQ

103

VCC

_DEB

UG

GER

VCC

_DEB

UG

GER

100kR115

GN

D

DEB

UG

GER

Prog

ram

min

g co

nnec

tor

for f

acto

ry p

rogr

amm

ing

of th

e D

ebug

ger



6.2 Assembly DrawingFigure 6-4. AVR-BLE Assembly Drawing Top

®®

E

C-BLE

PAC10101 PAC10102 COC101

PAC10201 PAC10202 COC102

PAC10301

PAC10302 COC103

PAC20001 PAC20002 COC200

PAC20102 PAC20101 COC201

PAC20202 PAC20201 COC202

PAC20302 PAC20301 COC203

PAC20401 PAC20402 COC204

PAC20501 PAC20502 COC205

PAC20602 PAC20601 COC206

PAC20702 PAC20701 COC207

PAC20802 PAC20801 COC208

PAC20902

PAC20901 COC209

PAC30001 PAC30002 COC300 PAC30102 PAC30101 COC301 PAC30202

PAC30201 COC302

PAD10001 PAD10002 COD100

PAD20001 PAD20002 COD200 PAD20102 PAD20101 COD201 PAD20201 PAD20202 COD202

PAD30001 PAD30002 COD300

PAF10001

PAF10002 COF100

PAJ10001

PAJ10002

PAJ10003

PAJ10004

PAJ10005

PAJ10006 COJ100

PAJ10106

PAJ10107 PAJ10109

PAJ10108 PAJ101010

PAJ101011 PAJ10105

PAJ10104

PAJ10103

PAJ10102

PAJ10101

PAJ10100

COJ101

PAJ20001 PAJ20002 PAJ20004 PAJ20003 PAJ20007 PAJ20008 PAJ20006 PAJ20005 PAJ20000 COJ200


PAJ30001 PAJ30002 COJ300

PAJ30102 PAJ30101 PAJ30100 COJ301 COLABEL1

PAM20001 PAM20002

PAM200033 PAM200032 PAM200022 PAM200023

PAM200015

PAM200017 PAM200018 PAM200019

PAM200016

PAM200027 PAM200026 PAM200025

PAM200012

PAM200029 PAM200028 PAM200024

PAM20009 PAM200011 PAM20005

PAM200030

PAM20004 PAM200010

PAM200020

PAM200021

PAM20006 PAM200013 PAM200014 PAM20007 PAM20008

PAM200031

PAM20003

COM200

PAQ10001 PAQ10002 PAQ10003 PAQ10000 COQ100

PAQ10101 PAQ10102

PAQ10103 PAQ10100

COQ101

PAQ10201 PAQ10202

PAQ10203 PAQ10200

COQ102

PAQ10301

PAQ10302 PAQ10303 PAQ10300 COQ103

PAQ30001 PAQ30002

PAQ30003 PAQ30004 COQ300

PAR10002 PAR10001 COR100

PAR10101

PAR10102 COR101 PAR10202

PAR10201 COR102 PAR10302 PAR10301 COR103

PAR10402 PAR10401 COR104

PAR10502 PAR10501 COR105

PAR10601 PAR10602 COR106

PAR10701

PAR10702 COR107

PAR10802 PAR10801 COR108

PAR10902 PAR10901 COR109

PAR11002


PAR11202 PAR11201 COR112

PAR11302 PAR11301 COR113

PAR11402 PAR11401 COR114

PAR11502 PAR11501 COR115

PAR20002 PAR20001 COR200 PAR20101

PAR20102 COR201

PAR20202

PAR20201 COR202

PAR20302 PAR20301 COR203

PAR20401 PAR20402 COR204 PAR20502 PAR20501 COR205

PAR20602 PAR20601 COR206

PAR20701 PAR20702 COR207

PAR20802 PAR20801 COR208 PAR20901 PAR20902 COR209 PAR21002 PAR21001 COR210

PAR21102

PAR21101 COR211

PAR21202 PAR21201 COR212

PAR21302 PAR21301 COR213

PAR30002

PAR30001 COR300

PAR30101 PAR30102 COR301

PAR30202 PAR30201 COR302

PAR30301 PAR30302 COR303

PAR30401

PAR30402 COR304

PAR30501 PAR30502 COR305

PAR30601

PAR30602 COR306 PAR30702 PAR30701 COR307 PAR30802 PAR30801 COR308

PASW20003 PASW20004

PASW20001 PASW20002

PASW20005 COSW200

PATP10001 COTP100

PATP20101 COTP201 PATP20201 COTP202 PATP20301 COTP203 PATP20401 COTP204 PATP20501 COTP205 PATP20601 COTP206 PATP20701 COTP207


PAU10009

PAU10008 PAU10007 PAU10006 PAU10005 PAU10004 PAU10003 PAU10002 PAU10001

PAU100010

PAU100011

PAU100012

PAU100013

PAU100014

PAU100015 PAU100016

PAU100017 PAU100018 PAU100019 PAU100020 PAU100021 PAU100022 PAU100023 PAU100024 PAU100025 PAU100026

PAU100027

PAU100028 PAU100029

PAU100030

PAU100031 PAU100032

PAU100033 COU100

PAU200033 PAU200032

PAU200031

PAU200030

PAU200029

PAU200028

PAU200027

PAU200026

PAU200025 PAU200024 PAU200023 PAU200022 PAU200021 PAU200020 PAU200019 PAU200018 PAU200017

PAU200016

PAU200015

PAU200014

PAU200013 PAU200012

PAU200011

PAU200010


COU200

PAU20109 PAU20101 PAU20102

PAU20103 PAU20104 PAU20105

PAU20106

PAU20107

PAU20108

COU201

PAU20209 PAU20201 PAU20202

PAU20204 PAU20203 PAU20206

PAU20205

PAU20207 PAU20208

PAU20200

COU202

PAU20306 PAU20305

PAU20303 PAU20304

PAU20307 PAU20308 PAU20309

PAU20302 PAU20301

PAU203010

PAU203011 PAU203012 COU203

PAU20400 PAU20408

PAU20407 PAU20406 PAU20405 PAU20404

PAU20403 PAU20402

PAU20401

COU204

PAU20503

PAU20502 PAU20501 COU205 PAU3000C2 PAU3000C1 PAU3000B2 PAU3000B1

PAU3000A2 PAU3000A1 COU300

PAU30101

PAU30102 PAU30103 PAU30104

PAU30105 PAU30106

PAU301012

PAU301011 PAU301010 PAU30109

PAU30108 PAU30107

PAU301013 COU301

PAU3020C2 PAU3020C1

PAU3020B2 PAU3020B1

PAU3020A2 PAU3020A1

COU302

Figure 6-5. AVR-BLE Assembly Drawing Bottom

LAB

EL

PC

BAc

t

b

R

PAC10101 PAC10102 COC101

PAC10201 PAC10202 COC102

PAC10301

PAC10302 COC103

PAC20001 PAC20002 COC200

PAC20102 PAC20101 COC201

PAC20202 PAC20201 COC202

PAC20302 PAC20301 COC203

PAC20401 PAC20402 COC204

PAC20501 PAC20502 COC205

PAC20602 PAC20601 COC206

PAC20702 PAC20701 COC207

PAC20802 PAC20801 COC208

PAC20902

PAC20901 COC209

PAC30001 PAC30002 COC300 PAC30102 PAC30101 COC301

PAC30202

PAC30201 COC302

PAD10001 PAD10002 COD100

PAD20001 PAD20002 COD200 PAD20102 PAD20101 COD201 PAD20201 PAD20202 COD202

PAD30001 PAD30002 COD300

PAF10001

PAF10002 COF100

PAJ10001

PAJ10002

PAJ10003

PAJ10004

PAJ10005

PAJ10006 COJ100

PAJ10106

PAJ10107 PAJ10109

PAJ10108 PAJ101010

PAJ101011 PAJ10105

PAJ10104

PAJ10103

PAJ10102

PAJ10101

PAJ10100

COJ101



PAJ30001 PAJ30002 COJ300

PAJ30102 PAJ30101 PAJ30100 COJ301 COLABEL1

PAM20001 PAM20002

PAM200033 PAM200032 PAM200022 PAM200023

PAM200015

PAM200017 PAM200018 PAM200019

PAM200016

PAM200027 PAM200026 PAM200025

PAM200012

PAM200029 PAM200028 PAM200024

PAM20009 PAM200011 PAM20005

PAM200030

PAM20004 PAM200010

PAM200020

PAM200021

PAM20006 PAM200013 PAM200014 PAM20007 PAM20008

PAM200031

PAM20003

COM200

PAQ10001 PAQ10002 PAQ10003 PAQ10000 COQ100

PAQ10101 PAQ10102

PAQ10103 PAQ10100

COQ101

PAQ10201 PAQ10202

PAQ10203 PAQ10200 COQ102

PAQ10301

PAQ10302 PAQ10303 PAQ10300 COQ103

PAQ30001 PAQ30002

PAQ30003 PAQ30004 COQ300

PAR10002 PAR10001 COR100

PAR10101

PAR10102 COR101 PAR10202


PAR10402 PAR10401 COR104

PAR10502 PAR10501 COR105

PAR10601 PAR10602 COR106

PAR10701

PAR10702 COR107

PAR10802 PAR10801 COR108

PAR10902 PAR10901 COR109

PAR11002


PAR11202 PAR11201 COR112

PAR11302 PAR11301 COR113

PAR11402 PAR11401 COR114

PAR11502 PAR11501 COR115

PAR20002 PAR20001 COR200 PAR20101

PAR20102 COR201

PAR20202

PAR20201 COR202

PAR20302 PAR20301 COR203

PAR20401 PAR20402 COR204 PAR20502 PAR20501 COR205

PAR20602 PAR20601 COR206

PAR20701 PAR20702 COR207

PAR20802 PAR20801 COR208 PAR20901 PAR20902 COR209 PAR21002 PAR21001 COR210

PAR21102

PAR21101 COR211

PAR21202 PAR21201 COR212

PAR21302 PAR21301 COR213

PAR30002

PAR30001 COR300

PAR30101 PAR30102 COR301

PAR30202 PAR30201 COR302

PAR30301 PAR30302 COR303

PAR30401

PAR30402 COR304

PAR30501 PAR30502 COR305

PAR30601

PAR30602 COR306 PAR30702 PAR30701 COR307 PAR30802 PAR30801 COR308

PASW20003 PASW20004

PASW20001 PASW20002

PASW20005 COSW200

PATP10001 COTP100



PAU10009

PAU10008 PAU10007 PAU10006 PAU10005 PAU10004 PAU10003 PAU10002 PAU10001

PAU100010

PAU100011

PAU100012

PAU100013

PAU100014

PAU100015 PAU100016

PAU100017 PAU100018 PAU100019 PAU100020 PAU100021 PAU100022 PAU100023 PAU100024 PAU100025 PAU100026

PAU100027

PAU100028 PAU100029

PAU100030

PAU100031 PAU100032

PAU100033 COU100

PAU200033 PAU200032

PAU200031

PAU200030

PAU200029

PAU200028

PAU200027

PAU200026


PAU200016

PAU200015

PAU200014

PAU200013 PAU200012

PAU200011

PAU200010


COU200

PAU20109 PAU20101 PAU20102

PAU20103 PAU20104 PAU20105

PAU20106

PAU20107

PAU20108

COU201

PAU20209 PAU20201 PAU20202

PAU20204 PAU20203 PAU20206

PAU20205

PAU20207 PAU20208

PAU20200

COU202

PAU20306 PAU20305

PAU20303 PAU20304

PAU20307 PAU20308 PAU20309

PAU20302 PAU20301

PAU203010

PAU203011 PAU203012 COU203

PAU20400 PAU20408

PAU20407 PAU20406 PAU20405 PAU20404

PAU20403 PAU20402

PAU20401

COU204

PAU20503

PAU20502 PAU20501 COU205 PAU3000C2 PAU3000C1 PAU3000B2 PAU3000B1


PAU30101

PAU30102 PAU30103 PAU30104

PAU30105 PAU30106

PAU301012

PAU301011 PAU301010 PAU30109

PAU30108 PAU30107

PAU301013 COU301

PAU3020C2 PAU3020C1

PAU3020B2 PAU3020B1




The Microchip Website

Microchip provides online support via our website at www.microchip.com/. This website is used to make files andinformation easily available to customers. Some of the content available includes:

• Product Support – Data sheets and errata, application notes and sample programs, design resources, user’sguides and hardware support documents, latest software releases and archived software

• General Technical Support – Frequently Asked Questions (FAQs), technical support requests, onlinediscussion groups, Microchip design partner program member listing

• Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing ofseminars 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 willreceive email notification whenever there are changes, updates, revisions or errata related to a specified productfamily or development tool of interest.

To register, go to 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 tohelp customers. A listing of sales offices and locations is included in this document.

Technical support is available through the website at: 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 specifications contained in their particular Microchip Data Sheet.• Microchip believes that its family of products is secure when used in the intended manner and under normal

conditions.• There are dishonest and possibly illegal methods being used in attempts to breach the code protection features

of the Microchip devices. We believe that these methods require using the Microchip products in a manneroutside the operating specifications contained in Microchip’s Data Sheets. Attempts to breach these codeprotection features, most likely, cannot be accomplished without violating Microchip’s intellectual property rights.

• Microchip is willing to work with any customer who is concerned about the integrity of its code.• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of its code. Code

protection does not mean that we are guaranteeing the product is “unbreakable.” Code protection is constantlyevolving. 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 suefor relief under that Act.

AVR-BLE Hardware


http://www.microchip.com/http://www.microchip.com/pcnhttp://www.microchip.com/support

Legal Notice

Information contained in this publication is provided for the sole purpose of designing with and using Microchipproducts. Information regarding device applications and the like is provided only for your convenience and may besuperseded by updates. It is your responsibility to ensure that your application meets with your specifications.

THIS INFORMATION IS PROVIDED BY MICROCHIP “AS IS”. MICROCHIP MAKES NO REPRESENTATIONS ORWARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OROTHERWISE, RELATED TO THE INFORMATION INCLUDING BUT NOT LIMITED TO ANY IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSEOR WARRANTIES RELATED TO ITS CONDITION, QUALITY, OR PERFORMANCE.

IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL ORCONSEQUENTIAL LOSS, DAMAGE, COST OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THEINFORMATION OR ITS USE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THEPOSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW,MICROCHIP'S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THE INFORMATION OR ITS USEWILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FORTHE INFORMATION. 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, orexpenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectualproperty 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,TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are registered trademarks of Microchip Technology Incorporatedin the U.S.A. and other countries.

AgileSwitch, APT, ClockWorks, The Embedded Control Solutions Company, EtherSynch, FlashTec, Hyper SpeedControl, HyperLight Load, IntelliMOS, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC, ProASICPlus, ProASIC Plus logo, Quiet-Wire, SmartFusion, SyncWorld, Temux, TimeCesium, TimeHub, TimePictra,TimeProvider, 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, Augmented Switching,BlueSky, BodyCom, CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController,dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, Espresso T1S, EtherGREEN, IdealBridge, In-Circuit Serial Programming, ICSP, INICnet, Intelligent Paralleling, Inter-Chip Connectivity, JitterBlocker, maxCrypto,maxView, 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, RTAX, RTG4, SAM-ICE, Serial Quad I/O, simpleMAP, SimpliPHY, SmartBuffer, SMART-I.S., storClad,SQI, SuperSwitcher, SuperSwitcher II, Switchtec, SynchroPHY, Total Endurance, TSHARC, USBCheck, VariSense,VectorBlox, VeriPHY, ViewSpan, WiperLock, XpressConnect, and ZENA are trademarks of Microchip TechnologyIncorporated 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 ofMicrochip Technology Inc. in other countries.

GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of MicrochipTechnology 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-7032-8

AVR-BLE Hardware


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

AVR-BLE Hardware


http://www.microchip.com/quality

AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPECorporate Office2355 West Chandler Blvd.Chandler, AZ 85224-6199Tel: 480-792-7200Fax: 480-792-7277Technical Support:www.microchip.com/supportWeb Address:www.microchip.comAtlantaDuluth, GATel: 678-957-9614Fax: 678-957-1455Austin, TXTel: 512-257-3370BostonWestborough, MATel: 774-760-0087Fax: 774-760-0088ChicagoItasca, ILTel: 630-285-0071Fax: 630-285-0075DallasAddison, TXTel: 972-818-7423Fax: 972-818-2924DetroitNovi, MITel: 248-848-4000Houston, TXTel: 281-894-5983IndianapolisNoblesville, INTel: 317-773-8323Fax: 317-773-5453Tel: 317-

avr-ble hardware user guide · 2020. 10. 27. · avr-ble hardware avr-ble hardware user guide...

Documents