atsamb11 blusdk smart example profiles application user's...

ATSAMB11 ATSAMB11 BluSDK SMART Example Profiles Application

User's Guide

Introduction

This document describes how to set the ATSAMB11-MR/ZR evaluation boards for various exampleapplications supported by the Advanced Software Framework (ASF). This document also provides the listof supported IDEs to be used in conjunction with the ATSAMB11-MR/ZR evaluation boards (see Table2-1). The part number of the ATSAMB11-MR Xplained Pro (XPro) board is ATSAMB11MR-XPRO and thepart number of the ATSAMB11-ZR Xplained Pro board is ATSAMB11ZR-XPRO.Note: All example applications are included in the BluSDK SMART software package.

Figure 1. ATSAMB11 Xplained Pro Boards

Features

• Observer Application• Proximity Monitor Application:

– Device discovery and disconnection– Services and characteristics discovery– Services – Link Loss service, Immediate Alert service, and Tx Power service– Setting up Path Loss and Link Loss– Received Signal Strength Indicator (RSSI) sampling

• Proximity Reporter Application:– Advertisement– Pairing/bonding– Services – Link Loss service (mandatory), Immediate Alert service, and Tx Power service

© 2017 Microchip Technology Inc. User Guide DS70005335A-page 1

• Apple® Notification Center Service (ANCS) Application• Scan Parameters Service Application• Time Information Profile Application:

– Device discovery and disconnection– Pairing/bonding– BLE time client

• HID Mouse Device and HID Keyboard Device Applications:– Advertisement– Pairing– Services: HID service and Device Information service– Report mode (mouse)/Report mode (keyboard)

• Battery Service Application• Simple Broadcaster Application• Device Information Service• Custom Serial Chat (CSC) Profile Application:

– Device discovery and disconnection– Pairing/bonding– Send and receive messages

• Heart Rate Profile Application:– Advertisement– Pairing/bonding– Heart rate sensor measurements– Console display

• Blood Pressure Profile Application:– Advertisement– Pairing/bonding– Blood pressure measurements

• Find Me Profile Application:– Advertisement– Pairing/bonding– Find Me alerts

• Phone Alert Status Profile Application:– Advertisement– Pairing/bonding– Phone alert status

• Alert Notification Profile Application:– Device discovery and disconnection– Pairing/bonding– Alert notification service– Alert on incoming call

• Multi-Role Peripheral Multi-Connect Application:– Supports eight connections

• L2CAP Throughput Application:– L2CAP central

ATSAMB11


– L2CAP peripheral– Used LE L2CAP connection oriented channel for data communication

• Health Thermometer Profile (HTP) Application:– Advertisement– Pairing/bonding– RSSI sampling– Health thermometer service– Health thermometer profile app for iOS/Android™

• iBeacon Application:– RSSI sampling– Beacon advertising– iBeacon demo app for iOS/Android

• AltBeacon Application:– AltBeacon advertising– AltBeacon demo app for iOS/Android

• Eddystone Beacon Application:– Eddystone UID, URL, and TLM frame types– URL configuration service with optional lock– Beacon demo application for Android and iOS

• Direct Test Mode (DTM) Application:– DTM setup procedure– Downloading DTM firmware

• AT Command Application– Reset the link layer– Set device configuration– Start scan– Stop scan

ATSAMB11


Table of Contents

Introduction......................................................................................................................1

Features.......................................................................................................................... 1

1. Functional Overview.................................................................................................. 61.1. Observer Application....................................................................................................................61.2. Proximity Reporter Application.....................................................................................................61.3. Proximity Monitor Application.......................................................................................................71.4. ANCS Profile Application..............................................................................................................71.5. Scan Parameters Service Application..........................................................................................71.6. Time Information Profile Application.............................................................................................81.7. HID Mouse Device or HID Keyboard Device Application.............................................................81.8. Battery Service Application.......................................................................................................... 81.9. Simple Broadcaster Application................................................................................................... 81.10. Device Information Service Application........................................................................................91.11. Custom Serial Chat Profile Application........................................................................................ 91.12. Heart Rate Profile Application...................................................................................................... 91.13. Blood Pressure Profile Application.............................................................................................101.14. Find Me Profile Application.........................................................................................................111.15. Phone Alert Status Profile Application........................................................................................111.16. Alert Notification Profile Application............................................................................................111.17. Multi-Role Peripheral Multi-Connect Application........................................................................121.18. L2CAP Throughput Application..................................................................................................121.19. Health Thermometer Profile Application.....................................................................................121.20. iBeacon Application....................................................................................................................131.21. AltBeacon Application................................................................................................................ 131.22. Eddystone Beacon Application...................................................................................................131.23. Direct Test Mode Application......................................................................................................131.24. AT Command Application...........................................................................................................13

2. Supported Hardware Platforms and IDEs............................................................... 15

3. Hardware Setup.......................................................................................................16

4. Software Setup........................................................................................................ 174.1. Installation Steps........................................................................................................................174.2. Build Procedure..........................................................................................................................174.3. Application Configuration........................................................................................................... 24

5. Application Demo.................................................................................................... 265.1. Demo Setup............................................................................................................................... 265.2. Console Logging........................................................................................................................ 285.3. Running the Demo..................................................................................................................... 28

6. Adding a BLE Standard Service.............................................................................. 77

ATSAMB11


7. Custom Serial Chat Service Specification............................................................... 807.1. Service Declaration.................................................................................................................... 807.2. Service Characteristic................................................................................................................ 807.3. Endpoint..................................................................................................................................... 807.4. Characteristic Descriptors.......................................................................................................... 817.5. Sequence Flow Diagram............................................................................................................81

8. Customization of Keil Project...................................................................................82

9. Memory Map............................................................................................................939.1. RAM Partition............................................................................................................................. 939.2. Sample GCC Linker File.............................................................................................................949.3. Sample Keil Scatter File.............................................................................................................96

10. BluSDK SMART Software Architecture................................................................... 97

11. Document Revision History..................................................................................... 98

The Microchip Web Site................................................................................................ 99

Customer Change Notification Service..........................................................................99

Customer Support......................................................................................................... 99

Microchip Devices Code Protection Feature................................................................. 99

Legal Notice.................................................................................................................100

Trademarks................................................................................................................. 100

Quality Management System Certified by DNV...........................................................101

Worldwide Sales and Service......................................................................................102

ATSAMB11


1. Functional OverviewThis chapter describes the functional overview of all the applications that are pre-defined in Atmel Studio.

1.1 Observer ApplicationThe Observer application is used for continuously listening to the advertisement data over the air. Thisapplication supports the following advertisement data types:

• Incomplete list of 16-bit service class UUIDs• Complete list of 16-bit service class UUIDs• Incomplete list of 32-bit service class UUIDs• Complete list of 32-bit service class UUIDs• Incomplete list of 128-bit service class UUIDs• Complete list of 128-bit service class UUIDs• Shortened local name• Complete local name• Appearance• Manufacturer specific data• Tx Power• Advertisement interval

1.2 Proximity Reporter ApplicationThe Proximity profile is defined by the Bluetooth® SIG to enable proximity monitoring between twoBluetooth Low Energy (BLE) devices. The Proximity Monitor (a Generic Attribute (GATT) client)configures the behavior of the peer Proximity Reporter device (a GATT server) based on the linkconditions. The configuration includes setting the alert level, which triggers on the Link Loss or based ona different threshold of the Path Loss. The Path Loss determines the quality of the connection and it isderived out of the Received Signal Strength Indicator (RSSI) and transmits the power. The ProximityMonitor continuously evaluates the Path Loss and creates an immediate alert in the Proximity Reporterdevice when the Path Loss crosses threshold values.

On-Board LED StatusThe on-board LED is configured to notify the user about the alerts received. The different alerts for theLink Loss and Immediate Alert services are explained in the following subsections.

Link LossOn the Link Loss, the LED blinks according to the alert level set by the Proximity Monitor. The alert levelsare:

• NO_ALERT for No alert level• MILD_ALERT for Mild alert level• HIGH_ALERT for High alert level

Based on the alert level configuration set by the Proximity Monitor, the LED blinks at different rates:• If the alert level is “HIGH_ALERT” then the LED blinks faster (1 second interval)• If the alert level is “MILD_ALERT” then the LED blinks moderately (2 second interval)• If the alert level is “NO_ALERT” the LED must be off

ATSAMB11


Alert on Path Loss (Immediate Alert)This alert is applicable when the “Immediate Alert” service is implemented. The example application relieson the Path Loss configuration done by the Proximity Monitor and notifies accordingly. The alert levelsare:

• NO_ALERT for No alert level• MILD_ALERT for Mild alert level• HIGH_ALERT for High alert level

Based on the alert level configuration set by the Proximity Monitor, the LED blinks at different rates:• If the alert level is “HIGH_ALERT” then the LED blinks faster (3 second interval)• If the alert level is “MILD_ALERT” then the LED blinks moderately (5 second interval)• If the alert level is “NO_ALERT” the LED must be off

1.3 Proximity Monitor ApplicationThe Proximity profile is defined by the Bluetooth SIG to enable proximity monitoring between two BLEdevices. The Proximity Monitor (a GATT client) configures the behavior of a peer Proximity Reporterdevice (a GATT server) based on the link conditions. The Proximity Monitor configures the desiredbehavior of the peer device through setting alert levels on the Link Loss and the Path Loss. In addition, italso maintains the connection with the Proximity Reporter and monitors the link quality of the connectionbased on RSSI reporting from the peer device.

1.4 ANCS Profile ApplicationThe Apple Notification Center Service (ANCS) is used to enable a device to access notifications from aniOS device that exposes ANCS.

The ANCS profile defines the following roles:• Notification Provider (NP) is a device that provides the iOS notification• Notification Consumer (NC) is a device that receives the iOS notifications and notification- related

data from Notification Provider

Incoming Call NotificationThe programmed ATSAMB11-MR/ZR (Notification Consumer) must be paired with an iPhone® to displaythe received incoming call notification on a console.

The Bluetooth SIG defined Alert Notification profile provides similar functionality for Android devices.ANCS is a variant of the Alert Notification profile customized by Apple. For more details on AlertNotification, refer to the Alert Notification Profile Application.

1.5 Scan Parameters Service ApplicationThe Scan Parameter service is an example application that demonstrates how to retrieve scan intervalwindow information from a peer device. The Scan Parameter service must be implemented on a peerdevice to retrieve scan interval information. This application implements a GATT server role. Thisapplication can be used for obtaining the updated scan interval window value by configuring the scanrefresh characteristic for notification.

ATSAMB11


1.6 Time Information Profile ApplicationThe Time Information Profile is an example application for a compatible Android/iPhone device forimplementing the BLE time service, such as current time, date and day, and displaying it on the console.

The profile defines the following roles:• Time client, a device in a peripheral role to read the time, date, and day information• Time server, a device to provide the time-related information

Note: This application is supported in iOS 7.0 and above or a BLE compatible Android device which hasthe Microchip SmartConnect mobile application installed.

1.7 HID Mouse Device or HID Keyboard Device ApplicationThe HID Over GATT Profile (HOGP) is defined by the Bluetooth SIG to enable HID services support overa BLE protocol stack using the GATT profile. This allows devices like a keyboard or mouse to implementHOGP and to connect with a compatible HOGP/BLE host device, such as mobile phone, tablet, TV, andso on.

The HID Mouse device or HID Keyboard device application supports the following characteristics:• Protocol mode (mouse/keyboard)• Report (mouse/keyboard)• Report map (mouse/keyboard)• HID information (mouse/keyboard)• HID control point (mouse/keyboard)• Boot mouse input report (mouse only)• Boot keyboard input report (keyboard only)• Boot keyboard output report (keyboard only)

This example application simulates a function of a mouse or keyboard. Once the connection procedure isimplemented between a mobile phone and the ATSAMB11-MR/ZR board, the board can act as a mouseor a keyboard.

In the case of a HID Mouse device application, a mouse cursor, visible in the mobile screen, can bemoved as per the predefined pattern by pressing the SW0 button on the board.

In the case of a HID keyboard device application, the predetermined text is sent to the mobile phone bypressing the SW0 button on the board. This can be viewed in any standard text editor in the mobilephone.

1.8 Battery Service ApplicationThe Battery Service application is used for reporting the battery level of the device using the batterycharacteristics. Any application discovering the database can access the battery service instance duringdiscovery services. This example application simulates the device battery level from 0% to 100%, with thestep of 1% every second.

1.9 Simple Broadcaster ApplicationThe Simple Broadcaster application is used for continuously broadcasting the advertisement data overthe air. This application supports the following advertisement data types:

ATSAMB11


• Incomplete list of 16-bit service class UUIDs• Complete list of 16-bit service class UUIDs• Incomplete list of 32-bit service class UUIDs• Complete list of 32-bit service class UUIDs• Incomplete list of 128-bit service class UUIDs• Complete list of 128-bit service class UUIDs• Shortened local name• Complete local name• Appearance• Manufacturer specific data

1.10 Device Information Service ApplicationThe Device Information Service (DIS) application is used for providing a setup for the user to define anduse the BLE DIS service. Any application discovering the database can access the DIS service instanceduring discovery services. This application supports the following characteristics:

• Manufacturer name string• Model number string• Serial number string• Hardware revision string• Firmware revision string• Software revision string• System ID• IEEE® 11073-20601 regulatory certification data list• PnP ID

1.11 Custom Serial Chat Profile ApplicationThe Custom Serial Chat application is used for sending and receiving data between the boards (see, Table 2-1) and the Microchip SmartConnect mobile application. This is a custom profile exampleapplication, implemented over GATT. The user can send the information to the mobile phone using theconsole terminal that is configured with the board and vice versa.

Note: For more information on Custom Serial Chat service, refer to Custom Serial Chat ServiceSpecification.

1.12 Heart Rate Profile ApplicationThe Heart Rate Profile application is used for enabling the collector device (GATT client) to connect andinteract with a Heart Rate sensor (GATT server) to be used in the fitness applications. The Heart Ratesensor sends the heart rate measurement in bpm (beats per minute), energy expended in kJ (kilojoules),and R-R intervals in seconds. In addition to the Heart Rate service, this profile also implements theDevice Information Service, which provides information about the Heart Rate sensor device.

The Heart Rate profile provided by Bluetooth SIG defines three characteristics for the exchange of heartrate parameters between the sensor and monitor. The characteristics of the profile are used to transferheart rate parameters like bpm, R-R interval measurements, and other parameters like body sensor

ATSAMB11


location and energy expended values. The optional “Heart Rate Control Point characteristic” is used bythe Heart Rate monitor to reset the energy expended in the Heart Rate sensor.

The Heart Rate sensor, which is the GATT server, holds the characteristics and sends the measurementvalues to the Heart Rate monitor.

• The Heart Rate, R-R interval, and energy expended are sent using the Heart Rate measurementcharacteristics

• The Heart Rate measurements are sent to the monitor on a value change if the monitor hasenabled the notifications

• The body sensor location is read by the monitor by its body sensor location characteristic. Theenergy expended sent in the heart rate measurement can be reset by the monitor by writing to theHeart Rate control point characteristic

Note: The example application simulates the sensor measurements and sends them to the Heart Ratecollector.

1.13 Blood Pressure Profile ApplicationThe Blood Pressure Profile (BLP) application is used for connecting and interacting with a device with ablood pressure sensor to be used in a consumer and professional health care applications. Thisapplication enables the device to obtain blood pressure measurement and other data from a non-invasiveblood pressure sensor that exposes the Blood Pressure service. For example, a nurse or doctor coulduse a non-invasive blood pressure sensor on a patient that sends blood pressure measurements to alaptop or other handheld device.

Blood Pressure MeasurementsThe blood pressure measurement characteristic can be used to send blood pressure measurementscontaining the following information:

• Flags field (containing units of blood pressure and used to show the presence of optional fields)• Blood pressure measurement compound value field, depending upon the contents of the Flags field• Timestamp (time of the measurement)• Pulse Rate• User ID• Measurement status fields

The intermediate cuff pressure characteristic may be notified frequently during the course of ameasurement, so that a receiving device can effectively update the display on its user interface during themeasurement process.

When the client characteristic configuration descriptor is configured for indications and a blood pressuremeasurement is available, this characteristic is indicated while in a connection. When the clientcharacteristic configuration descriptor is configured for indications and a blood pressure measurement isavailable, this characteristic is indicated while in a connection.

• The blood pressure measurement characteristic is used to send blood pressure measurements• The intermediate cuff pressure characteristic is used to send current cuff pressure values to a

device to display, while the measurement is in progress• The blood pressure feature characteristic is used to describe the supported features of the blood

pressure sensor

The ATSAMB11-MR/ZR simulates a blood pressure sensor (GATT server role) and sends simulatedvalues to the blood pressure monitor (Microchip SmartConnect mobile application).

ATSAMB11


1.14 Find Me Profile ApplicationThe Find Me Profile (FMP) application is used to define the device to create an alert signal behavior whena button is pressed on one device to cause an alerting signal on a peer device.

Find Me TargetThe FMP defines the behavior when a button is pressed on a device to cause an immediate alert on apeer device. This can be used to allow users to find devices that have been misplaced.

The Find Me Target application, which is the GATT server, holds the alert level characteristics and waitsfor the Find Me locators alert and performs the following alert level characteristic:

• When the Find Me locator device wishes to cause an alert on the Find Me Target device, it writesthe specific alert level (High, Mild and No alert) in the alert level characteristic.

1.15 Phone Alert Status Profile ApplicationThe Phone Alert Status (PAS) profile is used to obtain the phone alert status exposed by the phone alertstatus service on a mobile phone. The alert status and ringer setting information of a mobile phone canbe received and modified by the phone alert status service. The device can also use this profile toconfigure the ringer status on the mobile phone.

Phone Alert Status NotificationsThis profile defines two roles:

• Phone alert server – device that originates the alerts• Phone alert client – device that receives the alerts and alerts the user

The phone alert client (a GATT client) configuration is implemented on the ATSAMB11-MR/ZR (see Table2-1). The example application utilizes the SW0 button on the supported hardware platform todemonstrate the notification use-cases. A BLE compatible Android device that contains the MicrochipSmartConnect mobile application provides the phone alert server functionality in this example. On theapplication, once the service is discovered and the user can click on the PAS service to enable thenotifications.

1. After connecting with the mobile phone, press the SW0 button once to set the PAS server to“Silent” mode.

2. With the second SW0 button press, the device is set to “Mute” mode.3. With the third SW0 button press, the device is return back to the “Normal” mode.4. With the fourth SW0 button press, a “Read Characteristic” request is issued, that reads the

characteristics of “Alert Status”, “Ringer Settings”, and “Ringer Control Point”.

Note: The PAS profile application is not supported in iOS devices. This example works only with BLEcompatible Android devices that contain the Microchip SmartConnect mobile application.

1.16 Alert Notification Profile ApplicationThe Alert Notification Profile allows a device to obtain information from a mobile phone about incomingcalls, missed calls, and SMS/MMS messages. The information includes the caller ID for an incoming callor the sender ID for an email/SMS/MMS, but not the message text. This profile also enables the clientdevice to get information about the number of unread messages on the server device.

Note: This example application only works with BLE compatible Android devices that contain theMicrochip SmartConnect mobile application.

ATSAMB11


The Microchip SmartConnect mobile application is used for implementing the Alert Notification serviceand can be used for demonstrating an example application. This example application supports missedcall alert notification and SMS alert notification.

The device implements the GATT client, which reads (or notifies) about the characteristic values receivedfrom the GATT server (the mobile phone). The device must be paired with an Android phone. A missedcall or SMS alert notifications can be enabled/disabled, once connection is established. The MicrochipSmartConnect application notifies a missed call or SMS alert, which are then displayed on the terminalconsole on the device side.

The “SW0” user button on the supported platform is programmed in such a way that each successivebutton press either enables or disables the notifications.

1.17 Multi-Role Peripheral Multi-Connect ApplicationThe Multi-Role Peripheral Multi-Connect application demonstrates the ATSAMB11-MR/ZR to have eightsimultaneous active connections. The ATSAMB11-MR/ZR supports multiple roles, such as GAPperipheral device with battery service and GAP central device with Find Me locator profile at the sametime. It also supports multiple connections, such as GAP peripheral device with battery service that canconnect with seven GAP central devices simultaneously.

The Multi-Role Peripheral Multi-Connect application initially starts advertising using connectableadvertisement packets as a GAP peripheral and if any device sends a connection request, applicationgets connected to the remote device and exchanges the data on the established link. If the connectionrequest from the device is not sent within a minute, then the application initiates to scan the devices andinitiates a connection to the peripheral device, which advertises using connectable advertisementpackets. The ATSAMB11-MR/ZR is exchanging the data as a GAP central once the link is established.Again, the Multi-Role application is started to advertise using connectable advertisement packets as aGAP peripheral and gets connected to the remote device, which sends a connection request andexchanges the data on the new link established. The process continues until the Multi-Connectionapplication reaches eight connections.

1.18 L2CAP Throughput ApplicationThe L2CAP Throughput example application supports the L2CAP central feature and the L2CAPperipheral feature.

1.19 Health Thermometer Profile ApplicationThe Health Thermometer Profile (HTP) enables the data collection device to obtain data from athermometer sensor that exposes the health thermometer service. The profile defines the following roles:

• Thermometer – Device to measure temperature• Collector – Device to receive temperature measurement and other data from a thermometer

The thermometer implements only one Health Thermometer service in addition to the Device InformationService to display the information about the thermometer device. The current HTP application implementsthe following characteristics:

• Temperature measurement• Intermediate temperature• Measurement interval

ATSAMB11


1.20 iBeacon ApplicationThe iBeacon application is used to advertise iBeacon specific packets that include UUID, major and minornumbers. Any beacon scanner application can be used for finding the beacon device. The iOS MicrochipSmartConnect app can be used to find the beacon devices in the vicinity.

This profile defines the following roles:• Monitor – Device (iOS/Android) to search for beacon packets• Reporter – Device that continuously advertises the beacon packet as a part of advertisement data

1.21 AltBeacon ApplicationThe AltBeacon application advertises packets that include MFG ID, Beacon code, Beacon ID, ReferenceRSSI, and MFG reserved value. Any AltBeacon scanner application can be used to find the AltBeacondevice based on the beacon code. The supplied iOS demo app can be used to find the AltBeacondevices in the vicinity. The profile defines the following roles:

• Monitor – Device (iOS/Android) to search for AltBeacon packets• Reporter – Device that continuously advertises the AltBeacon packet as part of advertisement data

1.22 Eddystone Beacon ApplicationEddystone is an open Bluetooth Smart beacon format from Google that works across Android and iOSdevices. The Microchip SmartConnect BLE BluSDK Smart software solution provides full support for thisbeacon format on the ATSAMB11-MR/ZR devices.

The Eddystone beacon application supports UID, URL, and TLM frame types. The application can beconfigured as follows using the APP_TYPE define:

• Set APP_TYPE to EDDYSTONE_UID_APP to send UID and TLM beacon frames at regular beaconintervals

• Set APP_TYPE to EDDYSTONE_URL_APP to send URL and TLM frames. This also supports theURL configuration service that enables the beacon to be configured dynamically from a mobileapplication

The Eddystone application is completely configurable using the conf_eddystone.h file. The #definespresent in the conf_eddystone.h file are supplied with default values, which can be changed by theuser to meet the requirements. In addition to this compile time configuration, frame fields like the UIDvalue, URL, transmit power at 0 meters, and so on can be changed using the APIs provided in theeddystone.h file.

1.23 Direct Test Mode ApplicationThe Direct Test mode (DTM) application is used to establish performance of Tx and Rx tests between twoATSAMB11-MR/ZR modules. The BLE Performance Analyzer is a performance analysis tool that is partof the Wireless Composer tool in Atmel Studio. This tool will be used at both ends (one assuming the roleof a transmitter and the other the role of a receiver) for execution of tests. The BLE Performance Analyzercommunicates to ATSAMB11-MR/ZR by using the DTM application running on the MCU.

1.24 AT Command ApplicationThe following table provides the list of AT commands used.

ATSAMB11


Table 1-1. AT Command Set

Command Description Syntax

Reset Reset the link layer AT+RESET

Configuration Set device configuration AT+CFG_DEF

Start Scan Start scan operation AT+SCAN

Stop Scan Stop an ongoing scan operation AT+STOP

ATSAMB11


2. Supported Hardware Platforms and IDEsThe following table provides the supported hardware platforms and IDEs for the ATSAMB11-MR/ZR.

Table 2-1. BluSDK – Supported Hardware and IDEs

Platform MCU Supported IDEs

SAMB11MR-XPRO ATSAMB11G18A Atmel Studio v7.0 and Keil

SAMB11ZR-XPRO ATSAMB11-ZR210CA Atmel Studio v7.0 and Keil

ATSAMB11


3. Hardware SetupThe following figure illustrates the connection of the ATSAMB11-MR/ZR XPro board to the host PC usinga micro-USB cable.Figure 3-1. EDBG USB Port

ATSAMB11


4. Software Setup

4.1 Installation Steps1. Download and install the Atmel Studio software.2. Install the standalone Advanced Software Framework (ASF) package.3. Keil IDE Installation – To use Keil IDE instead of Atmel Studio, perform the following:

3.1. Download and install Keil MDK-ARM from https://www.keil.com/download/product/.3.2. Download and install Python from https://www.python.org/downloads/.

Note: When installing the Atmel Studio, the driver for SAMB11-MR/ZR XPRO is installed.Therefore, Atmel Studio must be installed to use the Keil compiler.

4. On the mobile phone, download and install the Microchip SmartConnect App on the mobile phone,available in the Apple Store for iPhone and in the Google Play™ Store for Android.

Note: Atmel Studio offers predefined example projects for the SAM B11 and SAM B11ZR XPro boards.

Note: For more information on the previous releases, refer to the Atmel Studio Release Notes availableon the Microchip web page.

4.2 Build Procedure

4.2.1 Build Procedure for Atmel StudioPerform the following steps to build an example project using Atmel Studio IDE. This example buildprocedure is developed using the SAMB11-MR/ZR Xplained Pro board, which is also valid for the othersupported hardware platforms (see Table 2-1).

1. Open the Atmel Studio and select File > New > Example Project.

ATSAMB11


http://www.microchip.com/development-tools/atmel-studio-7https://www.keil.com/download/product/https://www.python.org/downloads/http://atmel-studio.s3-website-us-west-2.amazonaws.com/7.0.1417/as-installer-7.0.1417-readme.pdf

Figure 4-1. Creating a New Project

2. In the New Example Project from ASF or Extensions window:2.1. Enter “SAMB11” keyword in the search box, which lists all the supported examples for

SAMB11-MR and SAMB11-ZR.2.2. Select the respective example application of the SAMB11-MR/ZR by expanding the “Atmel

- Atmel Corp.” in the All Projects tab. This selection automatically populates the ProjectName, Location, Solution, Solution Name, and Device.

2.3. Click OK.

ATSAMB11


Figure 4-2. Searching for a Specific Application Example

3. Select the “Accept the License Agreement” check box and then click Finish.4. The Atmel Studio generates the project files for the selected application example that can be used

in the SAMB11-MR/ZR Xplained Pro board.5. For the Time Information Profile application, the user must select the compiler symbol based on the

following:– For Android devices: TP_ANDROID– For iOS devices: NTP_ANDROID

Note: This step is applicable only for the Time Information Profile application.

ATSAMB11


Figure 4-3. Configuring the UART Flow Compiler Symbols for the Time InformationProfile

Note: iOS requires a device supporting the Time Information Profile to include the servicesolicitation advertisement type in the advertisement data. The above setting provides configurationto build the Time Information Profile for iOS or Android. The iOS natively supports Time Server anddoes not require a specific mobile application. To enable the devices that are displayed in the iOSBLE devices page, the service solicitation advertisement data type configuration is necessary.

6. To build the solution, go to Build > Build Solution.Figure 4-4. Building Solution for Selected Application Example

7. The generated solution is downloaded into the SAMB11-MR/ZR XPro board through the USBcable. To program the board, go to Tools > Device Programming.

ATSAMB11


Figure 4-5. Selecting Device Programming

8. In the EDBG (XXXXXXXX) Device Programming window, perform the following steps:8.1. Select EDBG in Tool.8.2. Click Apply and then click Read to read the Device Signature.8.3. After reading the Device, click Program to program the device.

Figure 4-6. Embedded Debugger Device Programming Window

9. After flashing the example application into the SAMB11-MR/ZR Xpro board, it is ready to be usedas a BLE device that supports the selected application example.

ATSAMB11


Note: 1. To run the profile application, refer to Running the Demo.2. In the case of Device Information, Simple Broadcaster and Observer application, refer to

Application Configuration.

4.2.2 Build Procedure for KeilPerform the following steps to build an example project using Keil IDE. This example build procedure isdeveloped using the SAMB11-MR/ZR Xplained Pro board. Applications for Keil IDE are available in theBluSDKSmart release package under \SDK. After unzipping the package, the example applications areavailable in the \apps folder.

1. Open an intended sample application Keil project (*.uvprojx) from Keil IDE.2. After opening the project, the following files are available in the Project tab:

– xxxx_app.c (xxxx is replaced with the specific application name)– app_startup.s– ble_services– ble_profiles– services– libs (driver_lib.lib, ble_api.lib)

3. Set the appropriate build symbols (see the following figure):– For ATSAMB11-MR – BLE_MODULE=SAMB11_MR– For ATSAMB11-ZR: BLE_MODULE=SAMB11_ZR

Figure 4-7. Selecting SAMB11 Board Type

4. For the Time Information Profile application, the user must select the compiler symbol based on thefollowing:

– For Android devices: TP_ANDROID– For iOS devices: NTP_ANDROID

Note: This step is applicable only for the Time Information Profile application.

ATSAMB11


Figure 4-8. Compiler Symbol for Time Information Profile

Note: iOS requires the device supporting Time Profile to include service solicitation advertisementtype in the advertisement data. The above setting provides configurability to build the Time Profilefor iOS or for Android. iOS natively supports Time Server and does not require a specific mobileapplication. To enable devices to be displayed in the iOS BLE devices page, the service solicitationadvertisement data type configuration is necessary.

5. Select Project > Rebuild all target files to compile the project.Figure 4-9. Compiling the Project

6. Go to Flash > Download to download the application via the USB onto the SAMB11-MR/ZRXPro board.

7. After flashing the following messages are displayed in the build output section.Wrote page 94 of 96 pages ....Wrote page 95 of 96 pages ....Wrote page 96 of 96 pages....Writing Done...Starting target application...O.K.0x1001008f

8. Now the demo application is running on the SAMB11-MR/ZR XPro board.

Note: 1. To run the profile application, refer to Running the Demo.2. In the case of Device Information, Simple Broadcaster and Observer application, refer to

Application Configuration.3. To create a custom project using Keil IDE, refer to Customization of Keil Project.

ATSAMB11


4.3 Application Configuration

4.3.1 Configuration of Device Information Service ApplicationThe list of macros that must be modified by user is as follows:

1. Before Connection:The user must configure the default characteristics for the Device Information Service by modifyingthe following macros in device_info.h, as shown in the following figure.Figure 4-10. Device Information Service Header File for Atmel Studio

Figure 4-11. Device Information Service Header File for Keil

DEFAULT_MANUFACTURER_NAMEDEFAULT_MODEL_NUMBERDEFAULT_SERIAL_NUMBERDEFAULT_HARDWARE_REVISIONDEFAULT_SOFTWARE_REVISIONDEFAULT_FIRMWARE_REIVSION

ATSAMB11


PNP_ID_VENDOR_ID_SOURCEPNP_ID_VENDOR_IDPNP_ID_PRODUCT_IDPNP_ID_PRODUCT_VERSIONSYSTEM_ID_MANUFACTURER_IDSYSTEM_ID_ORG_UNIQUE_ID

2. After connection:The user can configure the values of characteristics for the Device Information Service using thefollowing macros inside device_info.h.

UPDATE_MANUFACTURER_STRINGUPDATE_MODEL_NUMBERUPDATE_SERIAL_NUMBERUPDATE_HARDWARE_REVISIONUPDATE_FIRMWARE_REVISIONUPDATE_SOFTWARE_REVISIONUPDATE_SYSTEM_IDUPDATE_PNP_IDUPDATE_IEEE_REG_CERT_DATA_LIST

Note: After configuring the profile for Device Information Service, follow the steps mentioned in DeviceInformation Service Application.

4.3.2 Configuration of Simple Broadcaster Application• Simple Broadcaster application advertises the default configuration provided as follows:

– Non-connectable undirected advertisement event– Broadcasts data in advertisement data packets only– Broadcasts the following advertisement data types:

• Complete list of 16-bit service class UUIDs• Complete local name• Appearance

• The configuration and advertisement data types listed above can be changed by using the macrosprovided in the simple_broadcaster_app.h file that is available in the \src\config\directory.

Note: After configuration, follow the steps mentioned in Simple Broadcaster Application.

4.3.3 Configuration of Observer ApplicationThe default scanning parameters of Observer application are:MAX_SCAN_DEVICE (10)SCAN_INTERVAL (96)SCAN_WINDOW (96)SCAN_TIMEOUT (0x0000)SCAN_TYPE (AT_BLE_SCAN_ACTIVE)

These parameters can be modified as per the user requirement. They can be updated in theble_manager.h file, which is available in the following directory: \asf\thirdparty\wireless\ble_smart_sdk\ble_services\ble_mgrNote: After configuration, follow the steps in Observer Application.

ATSAMB11


5. Application Demo

5.1 Demo SetupThe following figure shows how to setup the board and the Microchip SmartConnect App for demopurposes.

Figure 5-1. Demo Setup

Table 5-1. Demo Setup Details for Various Applications

Applications (Keywords) BLE Node 1 BLE Node 2

Observer Application Any BLE device can be used asPeripherals

Supported by the ATSAMB11-MR/ZR XPro board to act as anObserver application

Proximity Reporter Application Supported by the MicrochipSmartConnect application foriPhone/Android devices to act as aProximity Monitor

Supported by the ATSAMB11-MR/ZR XPro board to act as aProximity Reporter

Proximity Monitor Application Supported by the ATSAMB11-MR/ZR XPro board to act as aProximity Monitor

Supported by the ATSAMB11-MR/ZR XPro board to acts as aProximity Reporter

ANCS Profile Application Supported by the MicrochipSmartConnect application foriPhone devices only, to act as aNotification Provider

Supported by the ATSAMB11-MR/ZR XPro board to act as aNotification Consumer

Scan Parameters ServiceApplication

Supported by the MicrochipSmartConnect application foriPhone/Android devices

Supported by the ATSAMB11-MR/ZR XPro board to act asScan Parameter Service

Time Information ProfileApplication

Supported by the MicrochipSmartConnect application foriPhone/Android devices to act as aTime server

Supported by the ATSAMB11-MR/ZR XPro board to act asTime client

HID Mouse Device Application Supported by the MicrochipSmartConnect application forAndroid devices only, to act asHOGP host

Supported by the ATSAMB11-MR/ZR XPro board to act as HIDMouse Device application

ATSAMB11



HID Keyboard DeviceApplication

Supported by the MicrochipSmartConnect application forAndroid devices only, to act asNotepad text editor app (HOGPHost role)

Supported by the ATSAMB11-MR/ZR XPro board to act as HIDKeyboard Device application

Battery Service Application Supported by the MicrochipSmartConnect application foriPhone/Android devices

Supported by the ATSAMB11-MR/ZR XPro board to act asBattery Service application

Simple Broadcaster Application Supported by the ATSAMB11-MR/ZR XPro board to act as SimpleBroadcaster application

Supported by Scannerapplication on a mobile phone

Device Information Service Supported by the MicrochipSmartConnect application foriPhone/Android devices

Supported by the ATSAMB11-MR/ZR XPro board to act asDevice Information Serviceapplication

Custom Serial Chat ProfileApplication

Supported by Custom Serial Chat(CSC) application for iPhone/Android to send and receive data

Supported by the ATSAMB11-MR/ZR XPro board with CSCapplication to send and receivedata

Heart Rate Profile Application Supported by the MicrochipSmartConnect application foriPhone/Android devices to act as aHeart Rate Data Collector

Supported by the ATSAMB11-MR/ZR XPro board to act asHeart Rate Sensor

Blood Pressure ProfileApplication

Supported by the MicrochipSmartConnect application foriPhone/Android devices to act as aBlood Pressure Monitor

Supported by the ATSAMB11-MR/ZR XPro board to act asBlood Pressure Sensor

Find Me Profile Application Supported by the MicrochipSmartConnect application foriPhone/Android devices to act as aFind Me Locator

Supported by the ATSAMB11-MR/ZR XPro board to act as FindMe Target

Phone Alert Status ProfileApplication

Supported by the MicrochipSmartConnect application Androiddevices only, to act as a PhoneAlert Status server

Supported by the ATSAMB11-MR/ZR XPro board to act asPhone Alert Status client

Alert Notification ProfileApplication

Supported by the MicrochipSmartConnect applicationforAndroid devices only, to act as aNotification Provider

Supported by the ATSAMB11-MR/ZR XPro board to act asNotification Consumer

Multi-Role Peripheral Multi-Connect Application

Supported by the ATSAMB11-MR/ZR XPro board and MicrochipSmartConnect application to act as Peripheral or Central

ATSAMB11



L2CAP Throughput Application Supported by the ATSAMB11-MR/ZR XPro board to act asL2CAP Central

Supported by the ATSAMB11-MR/ZR XPro board to act asL2CAP Peripheral

Health Thermometer Profile(HTP) Application

Supported by the MicrochipSmartConnect application foriPhone/Android devices to act as aHealth Thermometer Collector

Supported by the ATSAMB11-MR/ZR XPro board to act as HTPapplication

iBeacon Application Supported by the MicrochipSmartConnect application foriPhone/Android devices to act asBeacon Monitor

Supported by the ATSAMB11-MR/ZR XPro board to act asBeacon Reporter

AltBeacon Application Supported by the MicrochipSmartConnect application foriPhone/Android devices act as aAltBeacon App (Monitor)

Supported by the ATSAMB11-MR/ZR XPro board to act asReporter

Eddystone Beacon Application Supported by the MicrochipSmartConnect application foriPhone/Android devices

Supported by the ATSAMB11-MR/ZR XPro board to act asEddystone Beacon Application

Direct Test Mode (DTM)Application

Supported by the ATSAMB11-MR/ZR XPro board to act as aTransmitter (Tx) Test Board. BLEperformance analyzer toolconnected with target board usingCOM port

Supported by the ATSAMB11-MR/ZR XPro board to act as aReceiver (Rx) Test Board. BLEperformance analyzer toolconnected with target boardusing COM port

AT Command Application Supported by the ATSAMB11-MR/ZR XPro board connected withserial port monitor application (forexample, TeraTerm) to act as ATCommand Application.

Any BLE device can be used asPeripherals

5.2 Console LoggingFor the purpose of debugging, a logging interface can be implemented in the applications.

The logging interface utilizes the same EDBG port that connects to a supported Xplained Pro (XPro)platform. A serial port monitor application (for example, TeraTerm) is opened and attached to theappropriate COM port enumerated by the device on the PC.

5.3 Running the Demo

Initializing the DevicePerform the following steps to initialize the device:

1. Open any Terminal Application (for example, TeraTerm). Select the COM port enumerated on thePC and set the following parameters:

ATSAMB11


– Baudrate 115200– Parity None– One Stop bit– One Start bit– No Hardware Handshake

2. Press the Reset button on the supported Xplained Pro (XPro) platforms (see Table 2-1).Note: The device is now ready to be used as selected application and starts to scan or advertiseon the button press. This button must be pressed only when the “Press button” is displayed on theconsole log window. The same button is pressed to stop the device scan or advertise.

3. The device is in advertising mode and the device initialization message is displayed on the consolewindow.Initializing ApplicationInitializing SAMB11BD Address:0xF8F005F23FFF, Address Type:0BLE Started Advertisement

Pairing ProcedurePerform the following steps to pair the device with the mobile phone application:

1. Open the Microchip SmartConnect application and click Bluetooth Smart in an applicationdashboard as illustrated in the following figure.Note: With a Android mobile phone, ensure that the location service is enabled.

Figure 5-2. Dashboard of Microchip SmartConnect Application

2. To scan for the peripheral devices, click the START SCAN option available in scanning page. Thedevice name (for example, ATMEL-PXP) is displayed among the list of scanned devices.

ATSAMB11


Figure 5-3. Scanning for Devices

3. Select the device name in the scan results, which initiates the pairing procedure. Enter the pass-key “123456” on the Bluetooth Pairing Request window and click Pair. The mobile app displays“Successful connection” upon successful completion of pairing.Figure 5-4. Pairing Request

4. On the device side, the console displays the successful completion of the pairing procedure.5. On the Microchip SmartConnect app, the supported services are displayed for the device.

ATSAMB11


Figure 5-5. Display of Services Supported by the Application

5.3.1 Observer ApplicationPerform the following steps to run the Observer application demo:

1. Follow the steps (1 and 2) from Initializing the Device.Note: Observer Application Console Baudrate must be set to 921600.

2. Press the Reset button on the ATSAMB11-MR/ZR XPro board.3. The device is now ready to be used as an Observer and starts to scan for nearby BLE devices.4. The following figure shows example logs from the Observer application.

ATSAMB11


Figure 5-6. Observer Console Output

5.3.2 Proximity Reporter ApplicationPerform the following steps to run the Proximity Reporter application demo:

1. Establish the connection between the device and mobile phone using the procedure listed in Running the Demo.

2. Select the desired service (Link Loss or Immediate Alert) for alert level characteristics configuration.Choose a value from the following:

– HIGH ALERT– MILD ALERT– NO ALERT

ATSAMB11


Figure 5-7. Configuring Alert Level Settings

3. After configuration of desired alert levels, click Immediate Alert service and then move the mobilephone away from the Proximity reporter. Based on the separation distance, Path Loss is plotted onthe zone radar (using RSSI values received from the Proximity Reporter). Based on the zone, theProximity Monitor sends the corresponding alert level. The console log on the Proximity Reporterdisplays the corresponding alerts and on-board status LED behavior.Figure 5-8. Proximity Reporter Path Loss Plot Across Safe, Mid, and Danger Zone

ATSAMB11


Figure 5-9. Proximity Reporter Path Loss Console Log Alerts Notification

4. After configuration of desired alert levels, click on the Link Loss service and then move the mobilephone away from the reporter. Based on the separation distance, the Proximity Reporter receivesthe path loss notifications based on alert settings. Keep moving until the “Link Loss” pop-upappears. The console log on the Proximity Reporter displays the corresponding alerts and whenLink Loss occurs, it reports disconnection and the on-board status LED behavior. The lock screenemulates a common use-case application where this Link Loss service is used (for example, KeyFob). When the user is in close proximity, the lock remains open. Subsequently, the user movingout of range can be triggered to close the lock.

ATSAMB11


Figure 5-10. Link Loss Pop-up on Proximity Monitor

Figure 5-11. Proximity Reporter Console Log for Link Loss

5. After Link Loss, the mobile application attempts to reconnect to the Proximity Reporter. Theconnection is re-established by moving the mobile phone closer to the reporter.

ATSAMB11


6. The Tx Power service is used to retrieve the Tx Power of the Proximity Reporter. Click the TxPower service icon in the services screen. The Proximity Monitor reads the Tx Power value fromthe Proximity Reporter and displays the TX POWER LEVEL as shown in the following figure.Figure 5-12. Proximity Monitor – Reading Tx Power Service

5.3.3 Proximity Monitor ApplicationPerform the following steps to run the Proximity Monitor application demo:

1. Connect one ATSAMB11-MR/ZR device loaded with Proximity Monitor example application code.Follow the steps (1 and 2) from Initializing the Device.

2. Setup another ATSAMB11-MR/ZR device with Proximity Reporter application. Follow all the stepsfrom Initializing the Device. The device starts advertising.

3. Then the Proximity Monitor device starts scanning for available devices in the vicinity and displaystheir Bluetooth Device Address (BD) in the console window. The Proximity Reporter device foundduring the scan is displayed in the console log window (refer to the following figure). Select theindex number of that device to establish connection with it.

ATSAMB11


Figure 5-13. Proximity Monitor Connection with a Proximity Reporter

4. When the connection is established, the Proximity Monitor sets the link loss alert value to “HIGHALERT” at the Proximity Reporter device. The Proximity Monitor also monitors the path loss, if theProximity Reporter device supports the optional “Immediate Alert” service and “Tx Power” service.The Proximity Reporter example application supports both of these optional services.The default alert settings are as follows:

– For HIGH ALERT, set high alert RSSI to -91dBm and above. Alert status is indicated by LED,which must be ON.

– For MILD ALERT, set RSSI to -70dBm to -90dBm. Alert status is indicated by LED, whichmust be toggling.

– For NO ALERT, set RSSI to -69dBm and below. Alert status is indicated by LED, which mustbe OFF.

If the reporter device moves out of the proximity of the monitor device, the path loss crosses thethreshold values and the corresponding alert value is set. The alert notification is displayed on theconsole as shown below.

ATSAMB11


Figure 5-14. Proximity Monitor Setting Alert Levels

5.3.4 ANCS ApplicationPerform the following steps to run the ANCS application demo:

1. Follow the steps from Initializing the Device.2. From the Settings page of the iPhone, enable Bluetooth. The phone starts to scan for the devices.

ATMEL-ANCS appears among the list of devices scanned. Click the ATMEL-ANCS to connect tothe device.Figure 5-15. ANCS Device Discovery in iPhone

3. When connected, the client side initiates the pairing request with the iPhone. The console logprovides guidance for the user to enter the pass-key on the iPhone.Figure 5-16. Console Display for Pairing in ANCS

4. In the Bluetooth Pairing Request window of the iPhone, enter the pass-key displayed in the consolelog and click Pair. After the device is connected, “ATMEL-ANCS” appears in the MY DEVICESsection on the iPhone.

ATSAMB11


Figure 5-17. Pairing and Connecting iPhone to ATMEL-ANCS

5. Now, the user can initiate a mobile terminated call to the iPhone. When the iPhone receives a call,the corresponding incoming call alert is indicated on the device side console log window. Once thecall is terminated, the device waits for a new alert to occur, as shown in the following screen.Figure 5-18. Console Display for Notification Received as Incoming Call Alert

5.3.5 Scan Parameters ApplicationPerform the following steps to run the Scan Parameters application demo:


2. When paired, the application displays the Scan Parameters and the Generic Information service.3. Click the Scan Parameters service. The user receives notification for scan refresh characteristic

value. The user can disable the notification in the Scan Parameters page, as shown in the followingfigure.Figure 5-19. Scan Refresh Characteristic Notification Options

4. The user can set appropriate values for Scan Interval and Scan Window characteristics.5. The newly updated value of Scan Interval and Scan Window must be displayed on the console log

of the device side as shown in the following figure.

ATSAMB11


Figure 5-20. Updated Scan Interval/Window Characteristic Value on Device

5.3.6 Time Information Profile ApplicationPerform the following steps to run the Time Information Profile application demo:

1. Follow the steps (1 through 4) from the ANCS Application.2. Press the SW0 button on the device to read the internally supported characteristic values from the

iPhone.3. The console log on the device side displays the values for all characteristics supported by iPhone

internally.Figure 5-21. Console Display – Date, Time, and Day Information

5.3.6.1 Running the Demo for Android devicesPerform the following steps to run the Time Information Profile application demo for Android devices:


2. After the device is connected, the application displays Continuous Time Service, Next DST ChangeService, and Reference Time Update Service.

3. Click on the services to read the characteristic values.4. Press the SW0 button on the supported platform device to read the internally supported

characteristic values from the Android device.5. The console log on the device side displays the values for all the characteristics supported by the

device.

ATSAMB11


Figure 5-22. Console Display - All Supported Characteristic Values

5.3.7 HID Mouse Device ApplicationPerform the following steps to run the HID Mouse Device application demo:

1. Follow the steps from Initializing the Device.2. In this demonstration, Android device supporting HOGP is used. The HOGP profile is natively

supported in Android version 4.4 (Android KitKat) and higher. The mobile phone must include aBluetooth chipset supporting Bluetooth 4.0 or higher. On the mobile phone, enable Bluetooth in theSettings page to scan for the devices. “ATMEL-HID” appears among the list of scanned devices.Select ATMEL-HID to connect to the supported platform device.Figure 5-23. HID (Mouse) Device Discovery on Bluetooth Settings Page

3. Click ATMEL-HID to start the pairing procedure. A pop-up requesting for the pass-key appears.Enter the pass-key “123456” and click Pair.Figure 5-24. Bluetooth Pairing Request

4. After the pairing is completed, the connected device is listed under Paired devices, as shown in thefollowing figure.

ATSAMB11


Figure 5-25. Paired Devices

5. The HID device side for pairing and connection procedure is shown in the console log.Figure 5-26. HID Mouse Device Console Log

6. After the device is connected to the mobile phone, click on the SW0 button for simulating mousemovement.

7. For every button press, corresponding cursor movement is shown on the HID host as describedbelow:

– First 5 button presses – cursor moves right– Next 5 button presses – cursor moved down– Next 5 button presses – cursor moves left– Next 5 button presses – cursor moved up

The same sequence is repeated based on the user input. The console log is shown in the followingscreen.

ATSAMB11


Figure 5-27. HID Device Console Log for Movement

Figure 5-28. Mouse Movement Simulation

5.3.8 HID Keyboard Device Application

5.3.8.1 Disabling ULP ModePerform the following steps to disable the ULP mode for HID Keyboard device application.

1. Before building the project, ensure that the “NENABLE_ULP” symbol is used, as shown in thefollowing figure.

ATSAMB11


Figure 5-29. Selecting NENABLE_ULP Symbol to Disable ULP Mode

2. Follow the steps from Initializing the Device.3. In this demonstration, an Android device supporting HOGP is used. The HOGP profile is natively

supported in Android version 4.4 (Android KitKat) and higher. The mobile phone must include aBluetooth chip-set supporting Bluetooth 4.0 or higher. On the mobile phone, enable Bluetooth in theSettings page to scan for the devices. “ATMEL-HID” appears among the list of scanned devices.Select ATMEL-HID to connect to the supported platform device.Figure 5-30. HID (Keyboard) Device Discovery on Bluetooth Settings Page

4. Click ATMEL-HID to initiate the pairing procedure.Figure 5-31. Pairing Procedure with HID Device

ATSAMB11


5. After the pairing is completed, the connected device is listed under Paired devices.Figure 5-32. Paired Devices

6. The HID device side for pairing and connection procedure is shown in the console log.Figure 5-33. HID Keyboard Device Console Log

7. After the device connected, start any notepad application on the mobile phone.8. Click SW0 button on the supported platform device.9. A letter for each press is shown in the application “Fast notepad”.10. The user can see a complete “Hello Atmel” in the application as shown in the following screen.

Figure 5-34. Message Displayed in the Application

5.3.8.2 Enabling ULP ModePerform the following steps to enable the ULP mode for HID Keyboard device application.

ATSAMB11


Note: Entering into ULP mode with the following hardware changes is required only for SAMB11-MRXplained Pro. For SAMB11-ZR Xplained Pro AON_GPIO0 is pulled down by default and connected to theSW0 button. Once the device is entered into ULP mode, use AON_GPIO to wake-up the device or useother wake-up sources (BLE Events, AON Timer).

1. Before building the project, ensure that the “ENABLE_ULP” symbol is used, as shown in thefollowing figure.Figure 5-35. Selecting ENABLE_ULP Symbol for ULP mode

2. Configure the device using cables and a switch, as shown in the following figure.Figure 5-36. Cables and Switch

ATSAMB11


Figure 5-37. Configuring the ATSAMB11 to Control ULP Mode

3. Follow the steps (2 through 7) from Disabling ULP Mode.4. Adjust the switch to connect pin 9 (AON_GPIO_0) to pin 20 (VCC) to disable ULP mode.

Important: This step must be performed to proceed with the next steps.

5. Click SW0 button on the supported platform device.6. A letter for each press shows in the application “Fast notepad”.7. The user can see a complete “Hello Atmel” in the application, as shown in Figure 5-34.8. To enable the ULP mode again, adjust the switch to connect pin 9 (AON_GPIO_0) to pin 19 (GND).

5.3.9 Battery Service ApplicationPerform the following steps to run the Battery Service Application demo:


2. When paired, the application displays the Battery Service and the Generic Information service.3. Select “Battery Service” to receive notifications for the battery level characteristic. The user can

stop receiving the notifications by disabling notifications, as shown in the following figure.

ATSAMB11


Figure 5-38. Battery Level Characteristic Notification Options

4. On the device side, the console log displays the periodic battery level updates.Battery Level:0%Battery Level:1%Battery Level:2%Battery Level:3%Battery Level:4%Battery Level:5%

5.3.10 Simple Broadcaster ApplicationPerform the following steps to run the Simple Broadcaster application demo:

1. Follow the steps (1 and 2) from Initializing the Device.2. The device is in advertising mode.3. The following figure shows example logs from the Simple Broadcaster application.

Figure 5-39. Simple Broadcaster Console Display

5.3.11 Device Information Service ApplicationPerform the following steps to run the Device Information Service application demo:


2. When paired, the application displays the Device Information Service.

ATSAMB11


3. When the Device Information Service is selected, the device information service characteristics canbe viewed, as shown in the following screen.Figure 5-40. Display of Device Information Service Characteristics

4. The page can be refreshed to get the updated characteristic value of all characteristics.

5.3.12 Custom Serial Chat Profile ApplicationPerform the following steps to run the Custom Serial Chat Profile application demo.


2. Once pairing is complete, the Custom Serial Chat icon appears on service list page.3. Click the Custom Serial Chat icon. The chat screen appears where the text that is to be sent to the

remote device is to be entered, and the text coming from the remote device can be seen.4. Chat text “Hello Atmel” and send to the remote device.

ATSAMB11


Figure 5-41. Sending Data to Device

5. The user can also write the text on the console for the device and press the ENTER key to transmitthe chat text to the mobile application.Figure 5-42. Console Log for Sending Data to Remote Device

ATSAMB11


Figure 5-43. Chat Text Received from ATSAMB11

Note: For more information on Custom Serial Chat service, refer to Custom Serial Chat ServiceSpecification.

5.3.13 Heart Rate Profile ApplicationPerform the following steps to run the Heart Rate Profile application demo.


2. After the device is connected, the application displays the Heart Rate and the Device InformationService.

3. When the notifications are enabled the HRM values are displayed, as shown in the console and thecorresponding mobile app, the LED on SAMB11-MR/ZR board starts blinking while sendingnotifications.Notification EnabledHeart Rate: 50 bpm RR Values:msec User Status:IdleHeart Rate: 51 bpm RR Values:msec User Status:IdleHeart Rate: 52 bpm RR Values:msec User Status:IdleHeart Rate: 53 bpm RR Values:msec User Status:IdleHeart Rate: 54 bpm RR Values:msec User Status:IdleHeart Rate: 55 bpm RR Values:msec User Status:IdleHeart Rate: 56 bpm RR Values:msec User Status:IdleHeart Rate: 57 bpm RR Values:msec User Status:IdleHeart Rate: 58 bpm RR Values:msec User Status:IdleHeart Rate: 59 bpm RR Values:msec User Status:IdleEnergy Expended :3KJ

ATSAMB11


Figure 5-44. Displaying Heart Rate Measurements

4. When Stop Notify is disabled, the console logs display the notifications display as:Notification Disabled

5. During the connection, the SW0 button is used to disconnect the connection. If no connectionexists, the SW0 button is used to start advertisement.

5.3.14 Blood Pressure Profile ApplicationPerform the following steps to run the Blood Pressure Profile application demo.


2. When the device is connected, the application displays Blood Pressure, Device Information Serviceand Generic Information.

3. Upon entering the Blood Pressure service page, the mobile application enables the notificationsand indications for interim cuff pressure and blood pressure characteristics respectively. The bloodpressure sensor device simulated by the device sends the current blood pressure values afterreceiving the indications enabling the request. The corresponding console logs and mobileapplication screen are shown in the following figure.

ATSAMB11


Figure 5-45. Console Log for Blood Pressure Measurements

Figure 5-46. Blood Pressure Service Page after Receiving BP Indications

ATSAMB11


4. The SW0 button can be used on SAMB11-MR/ZR to receive updated blood pressuremeasurements. The blood pressure sensor first sends the interim cuff pressure values asnotifications and then sends the final blood pressure measurements as indication. The bloodpressure measurements sent by the blood pressure sensor are simulated values. The followingfigures demonstrate the scenario after the SW0 button press.Figure 5-47. Console Log for Blood Pressure Values after Button Press

Figure 5-48. Blood Pressure Service Pages after Receiving Measurement Data on ButtonPress

5.3.15 Find Me Profile ApplicationPerform the following steps to run the Find Me Profile application demo.


2. After the device is connected, the application displays a service page that includes Immediate AlertService and Generic Information.

3. Since the service level connection is established, notifications are shown based on the alert levelsettings as depicted in the following figures.

ATSAMB11


Figure 5-49. Sending Alerts to Find Me Target ATMEL-FMP

4. On the device side, the console log is displayed as:Find Me : Mild AlertFind Me : High AlertFind Me : No Alert

5.3.16 Phone Alert Status ApplicationPerform the following steps to run the Phone Alert Status application demo.


2. After connection, the application displays the Phone Alert Status Service page.3. The notifications are automatically enabled and the application reads the values of “Alert Status”,

“Ringer Settings”, and “Ringer Control Point” characteristics. These are updated on the mobileapplication, as illustrated in the following figure.

ATSAMB11


Figure 5-50. Displaying the Characteristics of the Phone Alert Service

4. Press the SW0 button. The device is set to different modes (see Phone Alert Status ProfileApplication) by using the notifications and the corresponding console logs are displayed.Figure 5-51. Phone Alert Status Console Log

5.3.17 Alert Notification Profile ApplicationPerform the following steps to run the Alert Notification Profile application demo:


ATSAMB11


2. When connected, the application displays the Alert Notification service page. The console logdisplays the new and unread alert categories.Figure 5-52. Alert Notification Categories

3. Enable the notifications by using the SW0 button. The mobile application reflects the status asshown.Figure 5-53. Alert Notification Screen on Microchip SmartConnect Application

4. The user can trigger a missed call to the Android device or send an SMS. The correspondingnotification then gets displayed on the device side in the console logs.

ATSAMB11


Figure 5-54. Console Display for Missed Call Alert and SMS Alert Notifications

5.3.18 Multi-Role Peripheral Multi-Connect ApplicationPerform the following steps to run the Multi-Role Peripheral Multi-Connect application demo.

1. Establish the connection between the device and mobile phone using the procedure listed in Running the Demo. The device initially acts as a GAP Peripheral and starts advertisement withBattery Service UUID in the advertisement data. Perform all the steps from Battery ServiceApplication.

2. The device starts scanning and displays the devices found, as shown in the following figure.Figure 5-55. Multi-Role Peripheral Multi-Connect Application – Scanning Devices

3. Set up another ATSAMB11-MR/ZR device with the Find Me application example loaded. Follow thesteps (1 through 3) from Running the Demo. The device starts advertising.

4. The GAP Central (Find Me Locator) scans and then displays the list of all BLE devices that areadvertising. Find Me Target devices (GATT server role) are indicated with tag “---FMP”. Select theappropriate index number for the Find Me Target. The GAP Central (Find Me Locator) connects tothe selected peer device.

ATSAMB11


Figure 5-56. Connecting GAP Central (Find Me Locator) with GAP Peripheral (Find MeTarget)

5. The ATSAMB11 as a GAP Central pairs with the connected peripheral. Then the ATSAMB11-MR/ZR acts as a GAP Peripheral by advertising with Battery Service UUID in the advertisementdata. Now the ATSAMB11-MR/ZR sends alert levels as a GAP Central, sends battery levelnotifications to the device connected as a GAP Peripheral, and also starts advertising withConnectable advertisement packets.Figure 5-57. GAP Peripheral (ATSAMB11) Connected to GAP Central (Mobile) andTransferring the Data

6. The ATSAMB11-MR/ZR acting as a GAP Peripheral (BAS) can connect to seven GAP centraldevices (mobile devices through the Microchip SmartConnect application). Now, the ATSAMB11-MR/ZR continues to behave as Find Me Locator (GAP Central) and Battery Service Application(GAP Peripheral) simultaneously with eight active connections. Continuous data transfer happenson all the links by the ATSAMB11-MR/ZR and even if one link gets disconnected, the data transferhappens on the other links.

ATSAMB11


5.3.19 L2CAP Throughput ApplicationThis demonstration requires two ATSAMB11-MR/ZR devices. Program one ATSAMB11-MR/ZR devicewith the L2CAP Peripheral and another one with the L2CAP Central application example. Perform thefollowing steps to run the Throughput application demo:

1. Follow the steps (1 and 2) from Initializing the Device for both devices.2. The device initializes start-up.3. The Central device starts scanning and subsequently connects with the desired peripheral device.

The following log shows that both devices connected to confirm the connection status.Figure 5-58. L2CAP Central Connection with L2CAP Peripheral

Figure 5-59. L2CAP Peripheral Connection with a L2CAP Central

4. Once the connection is established, the peripheral device keeps sending the specified data and thecentral device receives the same data in a given time. Eventually, calculated Throughput isdisplayed on the console for both central and peripheral.

ATSAMB11


Figure 5-60. L2CAP Peripheral Final Throughput Value

Figure 5-61. L2CAP Central Final Throughput Value

5.3.20 Health Thermometer Profile ApplicationPerform the following steps to run the Health Thermometer Profile application demo.


2. When paired, the application displays the Health Thermometer Service and the Generic Informationservice.

ATSAMB11


Figure 5-62. Health Thermometer Connected Services

3. The temperature value, RSSI and the device name are displayed on the mobile application.Console log is shown in the following screen.Figure 5-63. Console Log after Connection, Pairing, and with Notifications

4. To change the body measurement location, press the user button (SW0) on the SAMB11-MR/ZR.The new value is updated in the application.

5. Going back to the scanning screen on the Microchip SmartConnect application disconnects thedevice with the mobile application.

5.3.21 iBeacon ApplicationPerform the following steps to run the iBeacon application demo.

1. Follow the steps (1 and 2) from Initializing the Device.2. Start the Microchip SmartConnect application on the iPhone/Android.

ATSAMB11


Figure 5-64. Beacon Radar Profile App Launch Screen

3. Click Beacon Ranging. The beacon application is launched to show the positioning of beacondevice with respect to mobile phones and support following modes:

– Proximity – used to display beacon specific information when the mobile device comes inclose proximity to a given beacon. This mode also shows the corresponding product-relatedinformation configured for this particular beacon device.

– Distance – used to indicate the distance between beacon device and the mobile.

Figure 5-65. Beacon Radar Application Initial Screen

4. Click iBeacon to check the Major, Minor and RSSI value. The RSSI value is automatically updatedbased on the movement of the scanner device, as shown in the following figure.

ATSAMB11


Figure 5-66. Beacon Radar Application in Distance Mode

5. Inside the proximity mode, if the scanner device is very near to the beacon the product informationcan be seen when the user is in close proximity to a given beacon device. When the user movesaway from the beacon device information content is no longer shown, indicating that the user hasmoved away from the beacon device. Optionally, the message can be closed by clicking on close.Figure 5-67. Beacon Radar Application in Proximity Mode

5.3.22 AltBeacon ApplicationPerform the following steps to run the AltBeacon application demo.

1. Follow the steps (1 and 2) from Initializing the Device.2. The beacon application initialization is displayed in the console.

Initializing AltBeacon ApplicationBLE AltBeacon Advertisement started

ATSAMB11


3. Start the Microchip SmartConnect application and click Beacon Ranging from the mobile phone(see Figure 5-64). In this demonstration, an iPhone is used to run the application.

4. Tap on the AltBeacon icon for Major, Minor and UUID Value. The RSSI values are automaticallyupdated based on the movement of the scanner device. For more details about the AltBeacondevice, tap on the pop-up message (which shows UUID, ID1 and ID2 values), as shown in thefollowing figures.Figure 5-68. AltBeacon Radar Application in Distance Mode

5. In proximity mode, the application opens the configured URL whenever the user comes in closeproximity to the configured beacon device. When the user moves away from the beacon device theconfigured beacon is not shown, indicating the user moved away from the beacon device.Figure 5-69. AltBeacon Radar Application in Proximity Mode

ATSAMB11


6. A new AltBeacon can be added to the Beacon list using the add button, as illustrated in thefollowing figure.Figure 5-70. Adding new beacon

7. A new AltBeacon can be added into the Region monitoring list using the add button, as illustrated inthe following figure.Figure 5-71. Adding new beacon in Region Monitoring List

Note: The Region Monitoring List is supported on iOS, and not on Android devices.

5.3.23 Eddystone Beacon ApplicationPerform the following steps to run the Eddystone Beacon application demo:

1. Follow the steps (1 and 2) from Initializing the Device.2. The beacon application initialization is displayed on the console.

SAMB11 XPro Module:MR SAMB11-MRInitializing SAMB11SAMB11 Chip ID: 0x2000B1BD Address:0xF8F005F36701, Address Type:0BluSmartSDK Firmware Version:6.1.6991SAMB11 RF Version:0x10000000Eddystone beacon started

ATSAMB11


Adv count: 1Tx URL

3. Start the Microchip SmartConnect application and click Beacon Ranging from the mobile phone(see Figure 5-64). In this demonstration, an iPhone is used to run the application.

4. Open the Beacons navigation tab to view the ranging screen. The Eddystone beacon device isshown on the ranging screen with the Eddystone icon. The position of the beacon is based on thestrength of the signal received from RSSI. Click the Beacon icon to see a pop-up window showingthe identity of the frame; in the case of the EDDYSTONE_URL_APP, the shortened URL value isshown and in the case of the EDDYSTONE_UID_APP, Namespace ID and Instance ID is shown.Figure 5-72. Eddystone Beacons (both UID and URL beacons) ranged by MicrochipSmartConnect Application

5. Click the beacon pop-up window to view detailed information. The detailed view shows UID/URLand telemetric information like battery voltage, beacon temperature, time since power-on, and soon. This telemetric information is obtained from the Eddystone-TLM frames which are interleavedwith Eddystone identifying frames (UID/URL).

ATSAMB11


atsamb11 blusdk smart example profiles application user's...

Documents