Microchip Technology ATBTLC1000, ATBTLC1000-ZR, ATBTLC1000-MR User Manual

ATBTLC1000

ATBTLC1000 BluSDK Example Profiles Application User's

Guide

Introduction

This document describes how to set the ATBTLC1000-MR/ZR evaluation boards for various example applications supported by the Advanced Software Framework (ASF). This also provides the list of supported hardware platforms and IDEs to be used in conjunction with the ATBTLC1000-MR/ZR evaluation boards (see Table 2-1). The part number of the BTLC1000-ZR Xplained Pro (XPro) board is ATBTLC1000ZR-XPRO, and the part number of the BTLC1000-MR Xplained Pro board is ATBTLC1000MR-XPRO.

Note: All the example applications are included in BluSDK software package.

Figure 1. ATBTLC1000 Extension Boards

Features

• Observer Application

• Proximity Monitor Application: – Device discovery and disconnection

User Guide

DS50002640B-page 1

– 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

• 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

ATBTLC1000

User Guide

DS50002640B-page 2

• L2CAP Throughput Application: – L2CAP central – 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

™

ATBTLC1000

User Guide

DS50002640B-page 3

ATBTLC1000

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

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

1. Functional Overview................................................................................................................................6

1.1. Observer Application.................................................................................................................... 6

1.2. Proximity Reporter Application..................................................................................................... 6

1.3. Proximity Monitor Application....................................................................................................... 7

1.4. ANCS Profile Application..............................................................................................................7

1.5. Scan Parameters Service Application.......................................................................................... 7

1.6. Time Information Profile Application.............................................................................................7

1.7. HID Mouse Device or HID Keyboard Device Application............................................................. 7

1.8. Battery Service Application.......................................................................................................... 8

1.9. Simple Broadcaster Application................................................................................................... 8

1.10. Device Information Service Application........................................................................................8

1.11. Custom Serial Chat Profile Application........................................................................................ 9

1.12. Heart Rate Profile Application......................................................................................................9

1.13. Blood Pressure Profile Application...............................................................................................9

1.14. Find Me Profile Application.........................................................................................................10

1.15. Phone Alert Status Profile Application........................................................................................10

1.16. Alert Notification Profile Application........................................................................................... 10

1.17. Multi-Role Peripheral Multi-Connect Application........................................................................ 11

1.18. L2CAP Throughput Application.................................................................................................. 11

1.19. Health Thermometer Profile Application.....................................................................................11

1.20. iBeacon Application....................................................................................................................12

1.21. AltBeacon Application................................................................................................................ 12

1.22. Eddystone Beacon Application...................................................................................................12

1.23. Direct Test Mode Application......................................................................................................12

2. Supported Hardware Platforms and IDEs............................................................................................. 13

3. Hardware Setup.................................................................................................................................... 14

3.1. ATBTLC1000 Board Types.........................................................................................................14

3.2. SAM L21 Xplained Pro Setup.....................................................................................................14

3.3. SAM D21 Xplained Pro Setup.................................................................................................... 15

3.4. SAM G55 Xplained Pro Setup....................................................................................................16

3.5. SAM 4S Xplained Pro Setup...................................................................................................... 17

3.6. SAM R34 Xplained Pro Setup.................................................................................................... 18

4. Software Setup......................................................................................................................................20

4.1. Installation Steps........................................................................................................................ 20

4.2. Build Procedure..........................................................................................................................20

5. Application Demo.................................................................................................................................. 28

5.1. Demo Setup............................................................................................................................... 28

5.2. Console Logging........................................................................................................................ 30

5.3. Running the Demo..................................................................................................................... 30

User Guide

DS50002640B-page 4

ATBTLC1000

6. Adding a BLE Standard Service............................................................................................................72

7. Custom Serial Chat Service Specification.............................................................................................75

7.1. Service Declaration.................................................................................................................... 75

7.2. Service Characteristic................................................................................................................ 75

7.3. Endpoint..................................................................................................................................... 75

7.4. Characteristic Descriptors.......................................................................................................... 75

7.5. Sequence Flow Diagram............................................................................................................ 76

8. BluSDK Software Architecture.............................................................................................................. 77

9. Hardware Flow Control for 4-Wire Mode eFuse Write Procedure.........................................................78

10. Document Revision History...................................................................................................................81

The Microchip Website.................................................................................................................................82

Product Change Notification Service............................................................................................................82

Customer Support........................................................................................................................................ 82

Microchip Devices Code Protection Feature................................................................................................ 82

Legal Notice................................................................................................................................................. 82

Trademarks.................................................................................................................................................. 83

Quality Management System....................................................................................................................... 83

Worldwide Sales and Service.......................................................................................................................84

User Guide

DS50002640B-page 5

1. Functional Overview

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

1.1 Observer Application

The Observer application is used for continuously listening to the advertisement data over the air. This application 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

ATBTLC1000

Functional Overview

1.2 Proximity Reporter Application

The Proximity profile is defined by the Bluetooth® SIG to enable proximity monitoring between two Bluetooth 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 link conditions. The configuration includes setting the alert level, which triggers on the Link Loss or based on a different threshold of the Path Loss. The Path Loss determines the quality of the connection and it is derived out of the Received Signal Strength Indicator (RSSI) and transmits the power. The Proximity Monitor continuously evaluates the Path Loss and creates an immediate alert in the Proximity Reporter device when the Path Loss crosses threshold values.

On-Board LED Status

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

Link Loss

On the Link Loss, the LED blinks according to the alert level set by the Proximity Monitor. The alert levels are:

• 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

Alert on Path Loss (Immediate Alert)

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

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

User Guide

DS50002640B-page 6

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

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

1.4 ANCS Profile Application

The Apple® Notification Center Service (ANCS) is used to enable a device to access notifications from an iOS 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

ATBTLC1000

Functional Overview

Incoming Call Notification

The programmed SAM L21 or the other supported hardware platforms (Notification Consumer) must be paired with an iPhone® to display the 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 Alert Notification, refer to the Alert

Notification Profile Application.

1.5 Scan Parameters Service Application

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

1.6 Time Information Profile Application

The Time Information Profile is an example application for a compatible Android/iPhone® device for implementing 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 has the Microchip SmartConnect mobile application installed.

1.7 HID Mouse Device or HID Keyboard Device Application

The HID Over GATT Profile (HOGP) is defined by the Bluetooth SIG to enable HID services support over a BLE protocol stack using the GATT profile. This allows devices like a keyboard or mouse to implement HOGP and to connect with a compatible HOGP/BLE host device, such as mobile phone, tablet, TV, and so on.

The HID Mouse device or HID Keyboard device application supports the following characteristics:

User Guide

DS50002640B-page 7

• 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 is implemented between a mobile phone and the ATBTLC1000-MR/ZR board, the board can act as a mouse or a keyboard.

In the case of a HID Mouse device application, a mouse cursor, visible in the mobile screen, can be moved 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 by pressing the SW0 button on the board. This can be viewed in any standard text editor in the mobile phone.

1.8 Battery Service Application

The Battery Service application is used for reporting the battery level of the device using the battery characteristics. Any application discovering the database can access the battery service instance during discovery services. This example application simulates the device battery level from 0% to 100%, with the step of 1% every second.

ATBTLC1000

Functional Overview

1.9 Simple Broadcaster Application

The Simple Broadcaster application is used for continuously broadcasting the advertisement data over the air. This application 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

1.10 Device Information Service Application

The Device Information Service (DIS) application is used for providing a setup for the user to define and use the BLE DIS service. Any application discovering the database can access the DIS service instance during 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

User Guide

DS50002640B-page 8

• PnP ID

1.11 Custom Serial Chat Profile Application

The 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 example application implemented over GATT. The user can send the information to the mobile phone using the console terminal that is configured with the board and vice versa.

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

1.12 Heart Rate Profile Application

The Heart Rate Profile application is used for enabling the collector device (GATT client) to connect and interact with a heart rate sensor (GATT server) to be used in fitness applications. The heart rate sensor 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 the Device 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 heart rate parameters between the sensor and monitor. The characteristics of the profile are used to transfer heart rate parameters like bpm, R-R interval measurements, and other parameters like body sensor location and energy expended values. The optional “Heart Rate Control Point characteristic” is used by the 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 measurement values to the heart rate monitor:

• The heart rate, R-R interval, and energy expended are sent using the heart rate measurement characteristics.

• The heart rate measurements are sent to the monitor on a value change if the monitor has enabled the

notifications.

• The body sensor location is read by the monitor via its body sensor location characteristic. The energy

expended sent in the heart rate measurement can be reset by the monitor by writing to the heart rate control point characteristic.

Note: The example application simulates the sensor measurements and sends them to the heart rate collector.

ATBTLC1000

Functional Overview

1.13 Blood Pressure Profile Application

The Blood Pressure Profile (BLP) application is used for connecting to and interacting with a device with a blood pressure sensor device to be used in consumer and professional health care applications. This application enables the device to obtain blood pressure measurement and other data from a non-invasive blood pressure sensor that exposes the Blood Pressure service. For example, a nurse or doctor could use a non-invasive blood pressure sensor on a patient that sends blood pressure measurements to a laptop or other hand held device.

Blood Pressure Measurements

The blood pressure measurement characteristic can be used to send blood pressure measurements.

• Flags field (containing units of blood pressure and used to show the presence of optional fields)

• Blood pressure measurement compound value field and, 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 sent frequently during the course of a measurement, so that a receiving device can effectively update the display on its user interface during the measurement process.

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

User Guide

DS50002640B-page 9

configuration descriptor is configured for indications and a blood pressure measurement is available, 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 ATBTLC1000-MR/ZR together with the host MCU simulates a blood pressure sensor (GATT server role) and sends simulated values to the blood pressure monitor (Microchip SmartConnect mobile application).

1.14 Find Me Profile Application

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

Find Me Target

The FMP defines the behavior when a button is pressed on a device to cause an immediate alert on a peer 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 waits for 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 writes the specific

alert level (High, Mild and No alert) in the alert level characteristic.

ATBTLC1000

Functional Overview

1.15 Phone Alert Status Profile Application

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

Phone Alert Status Notifications

This 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 ATBTLC1000-MR/ZR along with a few other supported hardware platforms and IDEs (see Table 2-1). The example application utilizes the SW0 button on the supported hardware platform to demonstrate the notification use-cases. A BLE compatible Android device that contains the Microchip SmartConnect mobile application provides the phone alert server functionality in this example. On the application, once the service is discovered and the user can click on the PAS service to enable the notifications.

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

2. In the second SW0 button press, the device is set to “Mute” mode.

3. In the third SW0 button press, the device is returns to “Normal” mode.

4. In 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 BLE compatible Android devices that contain the Microchip SmartConnect mobile application.

1.16 Alert Notification Profile Application

The Alert Notification Profile allows a device to obtain information from a mobile phone about incoming calls, missed calls, and SMS/MMS messages. The information includes the caller ID for an incoming call or the sender ID for an

User Guide

DS50002640B-page 10

email/SMS/MMS, but not the message text. This profile also enables the client device 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 the Microchip SmartConnect mobile application.

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

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

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

Note: The SAM L21 or supported platforms (see Table 2-1) + ATBTLC1000-MR/ZR is referred as “device”.

1.17 Multi-Role Peripheral Multi-Connect Application

The Multi-Role Peripheral Multi-Connect application demonstrates the ATBTLC1000-MR/ZR to have eight simultaneous active connections. The ATBTLC1000-MR/ZR supports multiple roles such as GAP peripheral device with battery service and GAP central device with a Find Me locator profile at the same time. It also supports multiple connection such as a GAP peripheral device with battery service that can connect with seven GAP central devices simultaneously.

The Multi-Role Peripheral Multi-Connect application initially starts advertising using connectable advertisement packets as a GAP peripheral and if any device sends a connection request, the application gets connected to the remote device and exchanges the data on the link established. If the connection request from the device is not sent within a minute, then the application scans the devices and initiates a connection to the peripheral device, which advertises using connectable advertisement packets. The ATBTLC1000-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 a GAP peripheral and gets connected to the remote device, which sends a connection request, and exchanges the data on the new link established. The process continues until the Multi-Connection application reaches eight connections.

ATBTLC1000

Functional Overview

1.18 L2CAP Throughput Application

The L2CAP Throughput example application supports the L2CAP central feature and the L2CAP peripheral feature.

1.19 Health Thermometer Profile Application

The Health Thermometer Profile (HTP) enables the data collection device to obtain data from a thermometer 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 Information Service to display the information about the thermometer device. The current HTP application implements the following characteristics:

• Temperature measurement

• Intermediate temperature

• Measurement interval

User Guide

DS50002640B-page 11

1.20 iBeacon Application

The iBeacon application is used to advertise iBeacon specific packets that include UUID, major and minor numbers. Any beacon scanner application can be used for finding the beacon device. The iOS Microchip SmartConnect 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 Application

The AltBeacon application advertises packets that include MFG ID, Beacon code, Beacon ID, Reference RSSI, and MFG reserved value. Any AltBeacon scanner application can be used to find the AltBeacon device based on the beacon code. The supplied iOS demo app can be used to find the AltBeacon devices 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

ATBTLC1000

Functional Overview

1.22 Eddystone Beacon Application

The Eddystone™ is an open Bluetooth Smart beacon format from Google that works across Android and iOS devices. The Microchip SmartConnect BLE BluSDK software solution provides full support for this beacon format on the ATBTLC1000-MR/ZR devices.

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

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

• Set APP_TYPE to EDDYSTONE_URL_APP to send URL and TLM frames. This also supports the URL

configuration service that enables the beacon to be configured dynamically from a mobile application

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

1.23 Direct Test Mode Application

The Direct Test Mode (DTM) application is used to establish and test the Direct Test mode between two ATBTLC1000-MR/ZR modules. Windows-based ATBTLC1000-MR/ZR characterization software is used at both ends. The ATBTLC1000-MR/ZR Xplained Pro extensions are connected to a compatible MCU host device such as the SAM L21, SAM D21, SAM G55 or SAM 4S. The Performance Analyzer (PC tool) communicates with the ATBTLC1000 using a serial bridge application running on the MCU.

Serial Bridge Application

Sends the DTM commands to the ATBTLC1000-MR/ZR to enable the DTM performance analyzer application. The supported hardware platforms (see Table 2-1) can act as a serial bridge between the ATBTLC1000-MR/ZR and Atmel Studio performance analyzer tool. Once the SAM L21 (or other supported hardware platforms) is powered on or Reset, it initializes the Wake-up and Chip Enable to download the patch file into the ATBTLC1000-MR/ZR and completes the initialization procedure of the BLE module. After the ATBTLC1000-MR/ZR initialization, the application initializes the SAM L21 to act as a serial bridge.

User Guide

DS50002640B-page 12

Supported Hardware Platforms and IDEs

2. Supported Hardware Platforms and IDEs

The following table provides the supported hardware platforms and IDEs for the ATBTLC1000-MR/ZR.

Table 2-1. BluSDK – Supported Hardware and IDEs

ATBTLC1000

Platform MCU Supported BLE

Device

SAM L21 ATSAML21J18B ATBTLC1000-MR,

ATBTLC1000-ZR

SAM L21 ATSAML21J18A ATBTLC1000-MR,

ATBTLC1000-ZR

SAM D21 ATSAMD21J18A ATBTLC1000-MR,

ATBTLC1000-ZR

SAM G55 ATSAMG55J19 ATBTLC1000-MR,

ATBTLC1000-ZR

SAM 4S ATSAM4SD32C ATBTLC1000-MR,

ATBTLC1000-ZR

Supported Evaluation Kits Supported IDEs

ATBTLC1000-XSTK (ATSAML21-XPRO-B + ATBTLC1000-XPRO) or ATBTLC1000ZR-XSTK (ATSAML21-XPRO-B + ATBTLC1000ZR-XPRO)

ATSAML21-XPRO + ATBTLC1000-XPRO or ATSAML21-XPRO + ATBTLC1000ZR-XPRO

ATSAMD21-XPRO + ATBTLC1000-XPRO or ATSAMD21-XPRO + ATBTLC1000ZR-XPRO

ATSAMG55-XPRO + ATBTLC1000-XPRO or ATSAMG55-XPRO + ATBTLC1000ZR-XPRO

ATSAM4S-XPRO + ATBTLC1000-XPRO or ATSAM4S-XPRO + ATBTLC1000ZR-XPRO

Atmel Studio v7.0 and IAR

SAM R34 ATSAMR34J18B ATBTLC1000-MR,

ATBTLC1000-ZR

ATSAMR34-XPRO + ATBTLC1000-XPRO or ATSAMR34-XPRO + ATBTLC1000ZR-XPRO

Atmel Studio v7.0

User Guide

DS50002640B-page 13

3. Hardware Setup

3.1 ATBTLC1000 Board Types

The ATBTLC1000 supports the following extension boards:

1. ATBTLC1000-MR

2. ATBTLC1000-ZR

– Supports from BluSDK 6.0 release and later

The following figures illustrate samples of ATBTLC1000-MR and ATBTLC1000-ZR kit details displayed in the Atmel Studio.

Figure 3-1. ATBTLC1000-MR

ATBTLC1000

Hardware Setup

Figure 3-2. ATBTLC1000-ZR

3.2 SAM L21 Xplained Pro Setup

The following figure illustrates the connection between the ATBTLC1000-MR Xplained Pro Extension Board connected to the SAM L21 Xplained Pro Board.

User Guide

DS50002640B-page 14

ATBTLC1000

Hardware Setup

Figure 3-3. ATBTLC1000-MR Xplained Pro Extension Connected to the SAM L21 Xplained Pro

Note: Refer to the following section for the ATBTLC1000-ZR Xplained Pro Extension Board configuration.

3.3 SAM D21 Xplained Pro Setup

The following figures illustrate the connection between the ATBTLC1000-MR and ATBTLC1000-ZR Xplained Pro Extension Boards connected to the SAM D21 Xplained Pro.

Figure 3-4. ATBTLC1000-MR Xplained Pro Extension Connected to the SAM D21 Xplained Pro

User Guide

DS50002640B-page 15

ATBTLC1000

Hardware Setup

Figure 3-5. ATBTLC1000-ZR Xplained Pro Extension Connected to the SAM D21 Xplained Pro

Note: The connection for the SAM L21 Xplained Pro with the ATBTLC1000-ZR Xplained Pro Extension Board is

similar to the preceding figure.

3.4 SAM G55 Xplained Pro Setup

The following figures illustrate the connection between the ATBTLC1000-MR and ATBTLC1000-ZR Xplained Pro Extension Boards connected to the SAM G55 Xplained Pro Board.

Figure 3-6. ATBTLC1000-MR Xplained Pro Extension Connected to the SAM G55 Xplained Pro

User Guide

DS50002640B-page 16

ATBTLC1000

Hardware Setup

Note:

1. The SAM G55 Xplained Pro is connected to the ATBTLC1000-MR Xplained Pro through the ATBTLC1000 XPRO adapter board.

2. For a jumper connection on 4-wire and 6-wire connections, refer to the ATBTLC1000-XPRO-ADAPTER marking label.

Figure 3-7. ATBTLC1000-ZR Xplained Pro Extension Connected to the SAM G55 Xplained Pro

Note: The connection for the SAM 4S Xplained Pro with the ATBTLC1000-ZR Xplained Pro Extension Board is

similar to the preceding figure.

3.5 SAM 4S Xplained Pro Setup

The following figure illustrates the connection between the ATBTLC1000-MR Xplained Pro Extension Board and the SAM 4S Xplained Pro Board. These two devices are connected using the ATBTLC1000-XPRO-ADAPTER Board.

User Guide

DS50002640B-page 17

ATBTLC1000

Hardware Setup

Figure 3-8. ATBTLC1000-MR Xplained Pro Extension Connected to the SAM 4S Xplained Pro

Note: For a jumper connection on 4-wire and 6-wire connections, refer to the ATBTLC1000-XPRO-ADAPTER

marking label.

3.6 SAM R34 Xplained Pro Setup

The SAM R34 SERCOM5 is used for the UART connection to the EXT1 header. This UART port does not support CTS/RTS hardware flow-control needed for BTLC1000 operation. To connect SAMR34-XPRO to BTLC1000ZRXPRO, use SERCOM 5 for the console UART and SERCOM 0 to connect to BTLC1000. The connection mapping is shown in the following table.

Table 3-1. SAMR34-XPRO to BTLC1000ZR-XPRO Connection Mapping

SAMR34-XPRO

PIN SIGNAL

J200.3 PA06 (S0 UART RTS) J100.16 16 (UART CTS) BLE UART

J200.4 PA07 (S0 UART CTS) J100.18 18 (UART RTS) BLE UART

J200.13 PA05 (S0 UART RXD) J100.15 15 (UART TXD) BLE UART

J200.14 PA04 (S0 UART TXD) J100.17 17 (UART RXD) BLE UART

J200.5 PA08 J100.3 3 GPIO - WAKEUP

FTDI

TTL-232R-3V3

PLUG

RECEPTICAL

BTLC1000ZR-XPRO

J100 PIN SIGNAL

RTS/CTS

J200.7 PA18 J100.7 7 GPIO - CHIP EN

User Guide

DS50002640B-page 18

...........continued

SAMR34-XPRO

FTDI

TTL-232R-3V3

ATBTLC1000

Hardware Setup

BTLC1000ZR-XPRO

PIN SIGNAL

J200.9 PA22 J100.9 9 IRQ

J200.15 PB02 S5 CONSOLE TXD 5 (Yellow) FTDI Yellow Cable

J200.17 PA23 S5 CONSOLE RXD 4 (Orange) FTDI Orange Cable

J200.19 GND 1 (Black) J100.19 GND

J200.20 VCC J100.20 Power

1. SERCOM 5 is used for console UART.

2. SERCOM 0 is used for BTLC1000 connection.

PLUG

RECEPTICAL

J100 PIN SIGNAL

Console UART

RXD

Console UART

TXD

User Guide

DS50002640B-page 19

4. Software Setup

4.1 Installation Steps

1. Download and install the Atmel Studio software.

2. Install the standalone Advanced Software Framework (ASF) package.

3. 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 L21, SAM D21, SAM G55 and SAM 4S extension boards.

Note: For more information on the previous releases, refer to the Atmel Studio Release Notes available on the

Microchip web page.

4.2 Build Procedure

Perform the following steps to build an example project. This example build procedure is developed using the SAM L21 Xplained Pro Board, which is also valid for the other supported hardware platforms and IDEs (see Table 2-1).

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

Figure 4-1. Creating a New Project

ATBTLC1000

Software Setup

2. In the New Example Project from ASF or the Extensions window:

2.1. Enter the application specific keyword in the search box; for example, Scan Parameter, Battery

Service Application, Blood Pressure, etc.

User Guide

DS50002640B-page 20

ATBTLC1000

Software Setup

2.2. Select the respective example application of theSAM L21 by expanding the “Atmel - Atmel Corp.” in

the All Projects tab. This selection automatically populates the Project Name, Location, Solution, Solution Name, and Device.

2.3. Click OK.

Figure 4-2. Searching for a Specific Application Example

3. Select the “Accept the License Agreement” checkbox and then click Finish.

4. Atmel Studio generates the project files for the selected application example that can be used in the SAM L21 Xplained Pro board.

5. Go to Project > Properties to choose the hardware configuration switches and number of wires:

5.1. Set the appropriate build symbols (see following figure):

• For ATBTLC1000-MR: “BLE_MODULE = BTLC1000_MR”

• For ATBTLC1000-ZR: “BLE_MODULE = BTLC1000_ZR”

User Guide

DS50002640B-page 21

ATBTLC1000

Software Setup

Figure 4-3. Selecting the ATBTLC1000 Board Type

5.2. Choose between the 4-wire or 6-wire modes:

• ATBTLC1000-MR – supports both 4-wire and 6-wire UART modes. The ATBTLC1000-XPROADPTR must be with this board in 4-wire mode.

• ATBTLC1000-ZR – supports only 4-wire mode.

Note: For more information on 4-wire mode, refer to Hardware Flow Control for 4-wire Mode eFuse

Write Procedure.

The configurations for 4-wire and 6-wire are as follows:

• 6-wire: – UART_FLOWCONTROL_4WIRE_MODE=false – UART_FLOWCONTROL_6WIRE_MODE=true

• 4-wire: – UART_FLOWCONTROL_4WIRE_MODE=true – UART_FLOWCONTROL_6WIRE_MODE=false

Configure UART_FLOWCONTROL_4WIRE_MODE and UART_FLOWCONTROL_6WIRE_MODE symbols in the project properties as shown in the following figure.

User Guide

DS50002640B-page 22

Figure 4-4. Configuring the UART Flow Compiler Symbols

ATBTLC1000

Software Setup

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

Figure 4-5. Configuring the UART Flow Compiler Symbols for the Time Information Profile

User Guide

DS50002640B-page 23

ATBTLC1000

Software Setup

Note: iOS requires a device supporting the Time Information Profile to include the service solicitation

advertisement type in the advertisement data. The above setting provides the configuration to build the Time Information Profile for iOS or Android. The iOS natively supports Time Server and does not require a specific mobile application. To enable the devices that are displayed on the iOS BLE devices page, the service solicitation advertisement data type configuration is necessary.

7. To build the solution, go to Build > Build Solution.

Figure 4-6. Building Solution for Selected Application Example

8. The generated solution is downloaded into the SAM L21 XPro board through the USB cable. To program the

board, go to Tools > Device Programming.

Figure 4-7. Selecting Device Programming

9. In the EDBG (XXXXXXXX) Device Programming window, perform the following steps:

9.1. Select EDBG in Tool.

9.2. Click Apply and then click Read to read the Device Signature.

9.3. After reading the Device, click Program to program the device.

User Guide

DS50002640B-page 24

Figure 4-8. Embedded Debugger Device Programming Window

ATBTLC1000

Software Setup

10. After flashing the example application into the SAM L21 Xpro board, it is ready to be used as a BLE device

that supports the selected application example.

Note:

1. To run the profile application, refer to Running the Demo.

2. In the case of HID and Broadcaster applications, refer to the following configuration sections.

4.2.1 HID Mouse and HID Keyboard Application Configuration

The user needs to modify a few macros in hid_device.h (HID profile) for configuring the profile for HID Mouse and HID Keyboard applications as per the desired application use case.

User Guide

DS50002640B-page 25

Figure 4-9. HID Mouse Code Hierarchy

ATBTLC1000

Software Setup

Note: Similar to HID Mouse, the hid_device.h file for the HID Keyboard is available in the following directory:

\asf\thirdparty\wireless\ble_sdk\ble_profiles\hid_device\

The list of macros that must be modified by the user are:

1. By default, the application supports Report mode. If the application requires only Boot mode support, the user

can add the macro BOOT_MODE in the Compiler/Symbols tab, as shown in the following screen.

User Guide

DS50002640B-page 26

+ 58 hidden pages

Microchip Technology ATBTLC1000, ATBTLC1000-ZR, ATBTLC1000-MR User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Introduction

Features

Table of Contents

1. Functional Overview

1.1 Observer Application

1.2 Proximity Reporter Application

1.3 Proximity Monitor Application

1.4 ANCS Profile Application

1.5 Scan Parameters Service Application

1.6 Time Information Profile Application

1.7 HID Mouse Device or HID Keyboard Device Application

1.8 Battery Service Application

1.9 Simple Broadcaster Application

1.10 Device Information Service Application

1.11 Custom Serial Chat Profile Application

1.12 Heart Rate Profile Application

1.13 Blood Pressure Profile Application

1.14 Find Me Profile Application

1.15 Phone Alert Status Profile Application

1.16 Alert Notification Profile Application

1.17 Multi-Role Peripheral Multi-Connect Application

1.18 L2CAP Throughput Application

1.19 Health Thermometer Profile Application

1.20 iBeacon Application

1.21 AltBeacon Application

1.22 Eddystone Beacon Application

1.23 Direct Test Mode Application

2. Supported Hardware Platforms and IDEs

3. Hardware Setup

3.1 ATBTLC1000 Board Types

3.2 SAM L21 Xplained Pro Setup

3.3 SAM D21 Xplained Pro Setup

3.4 SAM G55 Xplained Pro Setup

3.5 SAM 4S Xplained Pro Setup

3.6 SAM R34 Xplained Pro Setup

4. Software Setup

4.1 Installation Steps

4.2 Build Procedure

4.2.1 HID Mouse and HID Keyboard Application Configuration