Platforms (that is, OSAL for the CC254x) to TI-RTOS of the CC13x0.
BLUE SHELL BLUETOOTH SOFTWARE SOFTWARE
BLUE SHELL BLUETOOTH SOFTWARE CODE
The ICall module source code is provided in the ICall and ICallīLE IDE folders in the application project. To operate properly in the multithreaded RTOS environment.
Understand the underlying architecture for the BLE-Stack The dual-image boundary as well as in Library configuration.Ībstracted within the BLE-Stack APIs (forĮxample, GAP, HCI, and so forth), the application developer must Which facilitates the application program interface between theĪpplication and the BLE-Stack task across The central component of the ICall architecture is the dispatcher, Resources in a unified TI-RTOS environment. ICall allows the applicationĪnd protocol stack to operate efficiently, communicate, and share Mechanism for the application to interface with the Bluetooth lowĮnergy protocol stack services (that is, BLE-StackĪPIs) as well as certain primitive services provided by TI-RTOS Indirect Call Framework (ICall) is a module that provides a DataĬommunications that occur between two devices in a Bluetooth low energyĬonnection are handled through GATT sub-procedures. The Generic Attribute Profile (GATT) layer is a serviceįramework that defines the sub-procedures for using ATT. The ATT layer allows a device to expose certain pieces of data The Generic Access Profile (GAP) layer directly interfaces with theĪpplication and/or profiles, to handle device discovery andĬonnection-related services for the device. The protocol stack to securely connect and exchange data with another device. Key distribution, and provides functions for the other layers of The Security Manager layer defines the methods for pairing and Layers, allowing for logical end-to-end communication of data. The Logical Link Control and Adaptation Layer Protocol (L2CAP) layer provides data encapsulation services to the upper TI’s proprietary commands and events are specified in the The Specification of the Bluetooth System describes Standard HCI commands and events. Hardware interface such as UART, SPI, or USB.
This layer can be implemented either through a software API or by a Provides communication between the host and controller through a standardized See the BLE-Stack API Reference for HCI layer API. Master and the device accepting the request becomes the slave. The device initiating the connection becomes the When a device is connected, it connects as either If the advertiser accepts theĬonnection request, both the advertiser and initiator enter aĬonnected state. An initiator is a device that responds to anĪdvertiser with a request to connect. The Generic Access Profile (GAP) controls the RF state of the device, with the device in one ofĪdvertisers transmit data without connecting, while scanners scanįor advertisers. (Gaussian frequency-shift keying) radio operating in the unlicensedĢ.4-GHz ISM (industrial, scientific, and medical) band. The physical layer (PHY) is a 1-Mbps adaptive frequency-hopping GFSK Profiles and applications sit on top of the GAP and GATT layers of Host derives from the implementation of classic Bluetooth BR/EDRĭevices, where the two sections are implemented separately. The Bluetooth low energy protocol stack (or protocol stack) consists shows the Bluetooth low energy protocol stack architecture. Bluetooth low energy Protocol Stack.įigure 26.