Microchip Technology AVR-BLE Manuel d'installation

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 mikroBUS™ 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 board™.

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

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

Debugger

Power/Status

LED

ATECC6080A

Crypto

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

Introduction

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

CR2032 Battery Holder

Additional RN4870 GPIO

Introduction

Figure 1-3. AVR-BLE Quick Reference Overview

AVR-BLE Development Board (DT100111)

CDC RX

CDC TX

DEBUG GPIO0

PF0 | USART2 TX

PF1 | USART2 RX

PF3

I2C SCL

I2C SDA

PA3

PA2

BLE MODE

BLE RST

BLE RX

PF3

PD3

PA0 | USART0 TX

BLE TX PA1 | USART0 RX

HOLD#

SPI CS

SPI SCK

PD4

PD0

PA6

SPI MISOPA5

I2C SCL

I2C SDA

BMA 253 INT1

PA3

PA2

PC2

I2C SCL

I2C SDA

PA3

PA2

DEBUG GPIO1 PF4

EVENT PF2

SPI MOSIPA4

BMA 253 INT2PC3

MIC33050 DC/DC Converter

BMA253 Acceleration Sensor

ATECC608A Secure Element

PD1

PD6

PC1

PC0

PA3

PA2

5.0V

GND

SST25PF040C 4MB FLASH

PF4

PF5

Micro USB Connector

PKoB Nano Debugger/ Programmer

MCP9844 Temperature Sensor

RST

SPI CS

SPI SCK

SPI MISO

SPI MOSI

3.3V

GND

ATmega3208 MCU

User Switch 0

RN4870 Bluetooth Low Energy Module

PD7

PD5

PA7

PA6

PA5

PA4

PF3

PWM

INT

USART1 RX

USART1 TX

I2C SCL

I2C SDA

DATA LED

ERROR LED

RN4870 P1_1 BLE STATUS

GREEN

RED

BLUE

Introduction

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.

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.

Getting Started

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.

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

Target MCU

UART TX

UART RX

Debugger

USB

CDC RX

CDC TX

Terminal

Software

Target

Receive

Target

Send

Terminal

Receive

Terminal

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.

Hardware User Guide

Table des matières

Autres manuels Microchip Technology Carte mère

Microchip Technology

Microchip Technology HV2916 Manuel utilisateur

Microchip Technology

Microchip Technology MCP19035 Manuel utilisateur

Microchip Technology

Microchip Technology EVB-USB3503 QFN Manuel utilisateur

Microchip Technology

Microchip Technology dm164136 Manuel utilisateur

Microchip Technology

Microchip Technology MIC28514 Manuel utilisateur

Microchip Technology

Microchip Technology EVB-LAN9252-SPI Manuel utilisateur

Microchip Technology

Microchip Technology dsPICDEM MCHV-3 Manuel utilisateur

Microchip Technology

Microchip Technology PIC18F47Q10 Curiosity Nano Manuel d'installation

Microchip Technology

Microchip Technology BM70 PICtail Manuel utilisateur

Microchip Technology

Microchip Technology MIC23656 Manuel utilisateur

Microchip Technology

Microchip Technology ATWINC15x0 Series Supplément

Microchip Technology

Microchip Technology ATtiny1607 Curiosity Nano Manuel utilisateur

Microchip Technology

Microchip Technology UCS2112 Manuel utilisateur

Microchip Technology

Microchip Technology 28-Pin LIN DM164120-3 Manuel utilisateur

Microchip Technology

Microchip Technology BM70 PICtail Manuel utilisateur

Microchip Technology

Microchip Technology dsPICDEM MCSM Manuel utilisateur

Microchip Technology

Microchip Technology Microsemi PolarFire MPF300T Manuel utilisateur

Microchip Technology

Microchip Technology RN-2483-PICtail Manuel utilisateur

Microchip Technology

Microchip Technology MCP1012 Manuel utilisateur

Microchip Technology

Microchip Technology BM71-XPro Manuel utilisateur

Microchip Technology

Microchip Technology MCP1643 Manuel utilisateur

Microchip Technology

Microchip Technology MIC24045 Manuel utilisateur

Microchip Technology

Microchip Technology MCP2150 Manuel utilisateur

Microchip Technology

Microchip Technology ATBTLC1000 Xplained Pro Manuel utilisateur

Manuels Carte mère populaires d'autres marques

DFI

DFI SD170 Manuel utilisateur

ASROCK

ASROCK ROMED8-2T Manuel utilisateur

Asus

Asus P2L97A Manuel utilisateur

Winmate

Winmate IC70 Manuel utilisateur

Asus

Asus MES-B Manuel utilisateur

Grantech

Grantech SYS8F377VGGA-3OMN Manuel utilisateur

Telit Wireless Solutions

Telit Wireless Solutions SL869-3DR Manuel utilisateur

Gigabyte

Gigabyte GA-9IVDT Manuel utilisateur

Texas Instruments

Texas Instruments ADS8372EVM Manuel utilisateur

Commell

Commell MS-C73 Manuel utilisateur

IBT Technologies

IBT Technologies MB860 Manuel utilisateur

Nvidia

Nvidia TEGRA DG-04927-001_V01 Manuel utilisateur

Biostar

Biostar M7VIT Bravo Instructions d'utilisation et d'installation

Intel

Intel D33217CK Manuel utilisateur

Asus

Asus F1A55-M LX PLUS R2.0 Manuel utilisateur

EPC

EPC EPC9147C Manuel utilisateur

Asus

Asus EX-B760M-V5 D4 Manuel utilisateur

EPOX

EPOX MU-8KHA0010 Manuel utilisateur