Introduction
**************************** Introduction *********************************
- The Alert Notification example application bring-up the Alert Notification profile defined by the Bluetooth SIG.
- The Alert Notification profile allows a device like a watch to obtain information from a cellphone about incoming calls, missed calls, and SMS/MMS messages.
- The information may include the caller ID for an incoming call or the sender's ID for email/SMS/MMS but not the message. This profile also enables the client device to get information about the number of unread messages on the server device.
- The Alert Notification example application supports the following Features:
- Device Discovery and Disconnection
- Pairing / Bonding
- Alert Notification Service
- Alert on incoming call
Supported Evolution Kit -
- ATSAML21-XPRO-B + ATBTLC1000 XPRO
- ATSAMD21-XPRO + ATBTLC1000 XPRO
- ATSAMG55-XPRO + ATBTLC1000 XPRO
- ATSAM4S-XPRO + ATBTLC1000 XPRO
Running the Demo -
- 1. Build and flash the binary into supported evaluation board.
- 2. Open the console using TeraTerm or any serial port monitor.
- 3. Press the Reset button.
- 4. Wait for around 10 seconds for the patches to be downloaded device will initialize and start-up.
- 5. The device is now in advertising mode.
- 6. On a BLE compatible Android phone, enable Bluetooth in the Settings page. Start the 'Atmel Smart Connect' App and scan for devices. ATMEL-ANS will be appear among the devices scanned. Click on ATMEL-ANS to connect to supported platform.
- 7. Once connected, the client side will request for the pairing procedure . The console log provides a guidance for the user to enter the pass-key.
- 8. After connection gets established, 'Alert Notification Service' page appears on foreground and then click on the same page.
- 9. Enable the notifications by using the SW0 button as described in Chapter 4. The mobile app should reflect the status
- 10. The user can trigger a missed call/send an SMS to Android phone. The corresponding notification gets displayed at ATBTLC1000 side console logs.
Modules
***************************** Modules **************************************
- BLE Manger -
- The Event Manager is responsible for handling the following:
- Generic BLE Event Handling:-
- BLE Event Manager handles the events triggered by BLE stack and also responsible for invoking all registered callbacks for respective events. BLE Manager handles all GAP related functionality. In addition to that handles multiple connection instances, Pairing, Encryption, Scanning.
- Handling Multi-role/multi-connection:-
- BLE Event Manager is responsible for handling multiple connection instances and stores bonding information and Keys to retain the bonded device. BLE Manager is able to identify and remove the device information when pairing/encryption gets failed. In case of multi-role, it handles the state/event handling of both central and peripheral in multiple contexts.
- Controlling the Advertisement data:-
- BLE Event Manager is responsible for generating the advertisement and scan response data for BLE profiles/services that are attached with BLE Manager.
- BLE Services -
- The Alert Notification service exposes alert information in a device.
- This information includes the following:
- Type of alert occurring in a device
- Additional text information such as caller ID or sender ID
- Count of new alerts
- Count of unread alert items
- Alert Notification service has five characteristics
- Supported New Alert Category
- This characteristic exposes what categories of new alert is supported in the server.
- New Alert:
- This characteristic exposes information about the count of new alerts.
- Supported Unread Alert Category.
- This characteristic exposes what categories of unread alerts are supported in the server
- Unread Alert Status:
- This characteristic exposes the count of unread alert events existing in the server
- Alert Notification Control Point
- This characteristic allows the peer device to enable/disable the alert notification of new alert and unread event more selectively done by setting or clearing the notification bit in the Client Characteristic Configuration for each alert characteristic.
- BLE Platform Services -
- Interface Settings -
- Connect ATBTLC1000 XPRO to SAML21-XPRO-B -> EXT1
- Connect ATBTLC1000 XPRO to SAMD21-XPRO -> EXT1
- Connect ATBTLC1000 XPRO to SAMG55-XPRO -> EXT1
- Connect ATBTLC1000 XPRO to SAM4S-XPRO -> EXT1
- Serial Console COM port settings -
- Baudrate 115200
- Parity None, Stop Bit 1, Start Bit 1
- No Hardware Handshake
6-Wire Mode Connection Setup -
- Pins are 1:1 match with SAML21/D21 Xpro EXT1 Header to BTLC1000 XPro Header
- UART(No Flow Control)-SAM L21/D21 XPro Pins (Rx-Pin13, Tx-Pin14)
- UART(With Flow Control)-SAM G55 Xpro Pins (Rx-Pin13, Tx-Pin14, RTS-Pin5, CTS-Pin6, Rx-Pin16, Tx-Pin17)
- BTLC1000 Wakeup Pin-SAM G55 XPro Pins(Pin4)
- BTLC1000 Chip Enable Pin-SAM G55 XPro Pins(Pin10)
- BTLC1000 Vcc Pin-SAM L21/D21/G55 Xpro Pins(Pin20)
- BTLC1000 GND Pin-SAM L21/D21/G55 Xpro Pins(Pin19)
4-Wire Mode Connection setup -
- UART(With Flow Control)-SAM L21/D21 XPro Pins (Rx-Pin15, Tx-Pin17, RTS-Pin16, CTS-Pin18)
- BTLC1000 Wakeup Pin-SAM L21/D21 XPro Pins (Rx-Pin6)
- BTLC1000 Chip Enable Pin-SAM L21/D21 XPro Pins (Rx-Pin4)
- UART(With Flow Control)-SAM G55/4S Xpro Pins (Rx-Pin13, Tx-Pin14, RTS-Pin5, CTS-Pin6)
- BTLC1000 Wakeup Pin-SAM G55/4S XPro Pins(Pin4)
- BTLC1000 Chip Enable Pin-SAM G55/4S XPro Pins(Pin10)
- BTLC1000 Vcc Pin-SAM L21/D21/G55/4S Xpro Pins(Pin20)
- BTLC1000 GND Pin-SAM L21/D21/G55/4S Xpro Pins(Pin19)
SDK Package
***************************** BLE SDK Package ******************************************
- Links for BluSDK -
- Links for ATBTLC1000 -
- Development Kit -
- SAM L21 + BTLC1000 XPro -
- BTLC1000 XPro -
- Applications -
- Support and FAQ - visit
1.8.5