IDEs to be used in conjunction with the ATSAMB11-MR/ZR evaluation boards (see Table 2-1). The part number of the ATSAMB11-MR Xplained Pro (XPro) board is ATSAMB11MR-XPRO and the part number of the ATSAMB11-ZR Xplained Pro board is ATSAMB11ZR-XPRO.
Notification Provider Incoming Call Notification ® The programmed ATSAMB11-MR/ZR (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.
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 ATSAMB11-MR/ZR board, the board can act as a mouse or a keyboard.
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 simulated values to the blood pressure monitor (Microchip SmartConnect mobile application).
• 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 Table 2-1). The example application utilizes the SW0 button on the supported hardware platform to demonstrate the notification use-cases.
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 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 Direct Test mode (DTM) application is used to establish performance of Tx and Rx tests between two ATSAMB11-MR/ZR modules. The BLE Performance Analyzer is a performance analysis tool that is part of the Wireless Composer tool in Atmel Studio. This tool will be used at both ends (one assuming the role of a transmitter and the other the role of a receiver) for execution of tests.
ATSAMB11 Supported Hardware Platforms and IDEs The following table provides the supported hardware platforms and IDEs for the ATSAMB11-MR/ZR. Table 2-1. BluSDK – Supported Hardware and IDEs Platform Supported IDEs SAMB11MR-XPRO ATSAMB11G18A Atmel Studio v7.0 and Keil SAMB11ZR-XPRO ATSAMB11-ZR210CA Atmel Studio v7.0 and Keil...
Page 22
– libs (driver_lib.lib, ble_api.lib) 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 For the Time Information Profile application, the user must select the compiler symbol based on the following: –...
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 as Supported by the ATSAMB11- Peripherals MR/ZR XPro board to act as an Observer application Proximity Reporter Application Supported by the Microchip...
ATSAMB11 Applications (Keywords) BLE Node 1 BLE Node 2 L2CAP Throughput Application Supported by the ATSAMB11- Supported by the ATSAMB11- MR/ZR XPro board to act as MR/ZR XPro board to act as L2CAP Central L2CAP Peripheral Health Thermometer Profile Supported by the Microchip...
Page 31
Device. Note: Observer Application Console Baudrate must be set to 921600. Press the Reset button on the ATSAMB11-MR/ZR XPro board. The device is now ready to be used as an Observer and starts to scan for nearby BLE devices. The following figure shows example logs from the Observer application.
Page 36
Connect one ATSAMB11-MR/ZR device loaded with Proximity Monitor example application code. Follow the steps (1 and 2) from Initializing the Device. Setup another ATSAMB11-MR/ZR device with Proximity Reporter application. Follow all the steps from Initializing the Device. The device starts advertising.
Page 47
ATSAMB11 Figure 5-37. Configuring the ATSAMB11 to Control ULP Mode Follow the steps (2 through 7) from Disabling ULP Mode. 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.
Page 51
ATSAMB11 Figure 5-43. Chat Text Received from ATSAMB11 Note: For more information on Custom Serial Chat service, refer to Custom Serial Chat Service Specification. 5.3.13 Heart Rate Profile Application Perform the following steps to run the Heart Rate Profile application demo.
Page 58
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 Set up another ATSAMB11-MR/ZR device with the Find Me application example loaded. Follow the steps (1 through 3) from Running the Demo.
Page 59
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 happens on all the links by the ATSAMB11-MR/ZR and even if one link gets disconnected, the data transfer happens on the other links.
Page 60
ATSAMB11 5.3.19 L2CAP Throughput Application This demonstration requires two ATSAMB11-MR/ZR devices. Program one ATSAMB11-MR/ZR device with the L2CAP Peripheral and another one with the L2CAP Central application example. Perform the following steps to run the Throughput application demo: Follow the steps (1 and 2) from Initializing the Device for both devices.
Page 69
Update the URL, Tx Power mode, beacon period, etc. and then save. Now, disconnect from the beacon and enter the ranging screen. Once disconnected, the beacon device (ATSAMB11-MR/ZR) enters into Beacon mode and start sending Eddystone URL frames with the updated values. The ranging console log screen shows the beacon with new URL value.
Page 70
Eddystone is the backbone of the Physical Web initiative from Google. For more information on the Physical Web, refer to https://google.github.io/physical-web/. The following demo shows how the Eddystone application running on an ATSAMB11-MR/ZR device works seamlessly with the Physical Web Android application.
Page 71
Figure 5-78. URL Configuration on Physical Web App 5.3.24 Direct Test Mode Application This demonstration requires two ATSAMB11-MR/ZR devices loaded with Direct Test Mode example application code. Perform the following steps to run the DTM with Performance Analyzer tool. Start the performance analyzer in the Atmel Studio.
Note: The chat text is sent as a notification from the sender (mobile app or ATSAMB11-MR/ZR based device). Hence, the client characteristic configuration descriptor is always configured for notifications (in the Custom Serial Chat service instance on the mobile application and host).
Page 92
ATSAMB11 To start the Debug session, perform the following: – Before starting the Debug session, erase the SPI Flash in the ATSAMB11-MR/ZR: • Open the file “<release_dir>\tools\EraseFlash.bat to run. An erase procedure starts. • After the erase is completed, the following output message is displayed.
ATSAMB11 Figure 9-2. ATSAMB11-MR/ZR RAM Partition Sample GCC Linker File The following is a sample GCC Linker file. ram - This defines the user application section as defined in Figure 9.2. The user application code and data resides on the same memory section. The ORIGIN and LENGTH of this section is limited as per Figure 9-2.
SQTP is a service mark of Microchip Technology Incorporated in the U.S.A. Silicon Storage Technology is a registered trademark of Microchip Technology Inc. in other countries. GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip Technology Inc., in other countries.
Need help?
Do you have a question about the ATSAMB11 and is the answer not in the manual?
Questions and answers