Introduction
**************************** Introduction *********************************
- The Device Information Application allow the user to define and use the BLE Dévice Information Service(DIS). Any application discovering the database can access the DIS instance during discovery services.
- Supported Characteristics in Device Information Service:
- 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
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. Enable Bluetooth® from Settings page on BLE compatible Android phone or iPhone®. Use the Atmel Smart Connect mobile application to scan for peripheral devices. A device with name ‘ATMEL-DIS’ will appear among the list of scanned devices.
- 7. Click on 'ATMEL-DIS' device. A pop-up will appear requesting pass-key. Enter “123456” and click on ‘Pair’.
- 8. Once the Device Information service is clicked, User can see the DIS characteristics and device information.
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 Profile -
- The Device Information Service exposes manufacturer and/or vendor information about a device.
- This service exposes manufacturer information about a device.
- The Device Information Service is instantiated as a Primary Service.
- Only one instance of the Device Information Service is exposed on a device.
- Device Information service has nine characteristics:
- Manufacturer Name String:
- This characteristic represents the name of the manufacturer of the device.
- Model Number String:
- This characteristic represents the model number that is assigned by the device vendor.
- Serial Number String:
- This characteristic represents the serial number for a particular instance of the device.
- Hardware Revision String:
- This characteristic represents the hardware revision for the hardware within the device.
- Firmware Revision String:
- This characteristic represents the firmware revision for the firmware within the device.
- Software Revision String:
- This characteristic represents the software revision for the software within the device.
- System ID:
- This characteristic represents a structure containing an Organizationally Unique Identifier (OUI) followed by a manufacturer-defined identifier and is unique for each individual instance of the product.
- IEEE 11073-20601 Regulatory Certification Data List:
- This characteristic represents regulatory and certification information for the product in a list defined in IEEE 11073-20601..
- PnP ID:
- The PnP_ID characteristic is a set of values used to create a device ID value that is unique for this device.
- 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