Texas Instruments CC2540/41 Bluetooth低能软件开发指南

需积分: 9 188 浏览量更新于2024-07-22 收藏 2.34MB PDF 举报

"TI_BLE_Software_Developer's_Guide v1.3.2" 这篇文档是德州仪器（Texas Instruments）针对CC2540/41蓝牙低能量（BLE）软件开发工具包的综合指南。它旨在介绍如何使用这个工具包进行BLE应用的开发，并对BLE标准提供基础介绍，但不作为完整规范的替代品。对于更详细的信息，读者可以参考引用文献[7]。在文档的5.1节中，你可以找到BLE软件开发工具包的发布历史，包括变更详情、增强功能、错误修复和已知问题。该文档涵盖了多个关键主题： 1. **概述**： - **介绍**：这部分简要介绍BLE技术的基本概念和开发环境。 - **BLE协议栈基础**：解释BLE协议栈的基本结构和功能。 2. **德州仪器BLE软件开发平台**： - **配置**：详述了不同配置选项，以适应不同的项目需求。 - **项目**：描述了如何管理和使用开发工具包中的项目文件。 3. **软件概览**： - **操作系统抽象层（OSAL）**：这是软件架构的关键部分，负责任务初始化、事件处理、堆管理以及消息机制。 - **硬件抽象层（HAL）**：提供了与硬件设备交互的接口，独立于具体的硬件实现。 - **BLE协议栈**：详述了BLE协议栈的组件，如GAP（Generic Access Profile）和GATT（Generic Attribute Profile）。 - **使用GAP和GATT堆栈API**：指导开发者如何调用API进行应用开发。 - **GATT服务器应用API**：介绍如何构建和管理GATT服务器。 - **库文件**：列举了开发过程中会用到的库文件及其功能。 4. **配置文件**： - **GAP外围角色配置文件**：描述了作为BLE设备外围角色的配置。 - **GAP外围/广播者多角色配置文件**：支持设备同时扮演外围设备和广播者的角色。 - **GAP中心角色配置文件**：说明了设备作为BLE连接中心时的设置。文档的其余部分可能包括更多关于配置、示例代码、调试技巧以及其他BLE特定功能的详细信息。通过这份指南，开发者可以学习如何利用Texas Instruments的CC2540/41芯片及相关的BLE软件开发工具包，有效地设计和实现BLE应用。

TI CC254x Bluetooth Low Energy Software Developer’s Guide SWRU271F Version 1.3.1

Note: The OSAL is capable of providing many more services than are covered in this guide,

including message management, timer management, and more; however for many applications

this level of depth is not required. This guide should serve as an introduction to the basic

framework of the OSAL.

Additional information on the OSAL can be found in [1]:

3.1.1 Task Initialization

In order to use the OSAL, at the end of the main function there should be a call to

osal_start_system. This is the OSAL routine that starts the system, and which will call the

osalInitTasks function that is defined by the application. In the SimpleBLEPeripheral project, this

function can be found in the file OSAL_SimpleBLEPeripheral.c.

Each layer of software that is using the OSAL must have an initialization routine that is called from

the function osalInitTasks. Within this function, the initialization routine for every layer of software

is called. As each task initialization routine is called, an 8-bit “task ID” value is assigned to the

task. Note that when creating an application, it is very important that it be added to the end of the

list, such that it has a higher task ID than the others. This is because the priority of tasks is

determined by the task ID, with a lower value meaning higher priority. It is important that the

protocol stack tasks have the highest priority in order to function properly. Such is the case with

the SimpleBLEPeripheral application: its initialization function is SimpleBLEPeripheral_Init, and

it has the highest task ID and therefore the lowest priority.

3.1.2 Task Events and Event Processing

After the OSAL completes initialization, it runs the executive loop checking for task events. This

loop can be found in the function osal_start_system in the file OSAL.c. Task events are

implemented as a 16-bit variable (one for each task) where each bit corresponds to a unique

event. The definition and use of these event flags is completely up to the application.

For example, the SimpleBLEPeripheral application defines a flag in simpleBLEPeripheral.h:

SBP_START_DEVICE_EVT (0x0001), which indicates that the initial start has completed, and

the application should begin. The only flag value which is reserved and cannot be defined by the

application is 0x8000, which corresponds to the event SYS_EVENT_MSG (this event is used for

messaging between tasks, which is covered in section 3.1.3).

When the OSAL detects an event for a task, it will call that task’s event processing routine. The

layer must add its event processing routine to the table formed by the array of function pointers

called tasksArr (located in OSAL_SimpleBLEPeripheral.c in the example). You will notice that

the order of the event processing routines in tasksArr is identical to the order of task ID’s in the

osalInitTasks function. This is required in order for events to be processed by the correct

software layer.

In the case of the SimpleBLEPeripheral application, the function is called

SimpleBLEPeripheral_ProcessEvent. Note that once the event is handled and if it is not

removed from the event flag, the OSAL will continue to call the task’s process event handler. As

can be seen in the SimpleBLEPeripheral application function

SimpleBLEPeripheral_ProcessEvent, after the START_DEVICE_EVT event occurs, it returns

the 16-bit events variable with the SBP_START_DEVICE_EVT flag cleared.

It is possible for any layer of the software to set an OSAL event for any other layer, as well as for

itself. The simplest way to set up an OSAL event is to use the osal_set_event function (prototype

in OSAL.h), which immediately schedules a new event. With this function, you specify the task ID

(of the task that will be processing the event) and the event flag as parameters.

Another way to set an OSAL event for any layer is to use the osal_start_timerEx function

(prototype in OSAL_Timers.h). This function operates just like the osal_set_event function. You

select task ID of the task that will be processing the event and the event flag as parameters;

however for a third parameter in osal_start_timerEx you input a timeout value in milliseconds.

The OSAL will set a timer, and the specified event will not get set until the timer expires.

3.1.3 Heap Manager

TI CC254x Bluetooth Low Energy Software Developer’s Guide SWRU271F Version 1.3.1

OSAL provides basic memory management functions. The osal_mem_alloc function serves as a

basic memory allocation function similar to the standard C malloc function, taking a single

parameter determining the number of bytes to allocate, and returning a void pointer. If no memory

is available, a NULL pointer will be returned. Similarly, the osal_mem_free function works similar

to the standard C free function, freeing up memory that was previously allocated using

osal_mem_alloc.

The pre-processor define INT_HEAP_LEN is used to reserve memory for dynamic allocation.

To see how much memory you typically need, you can set the pre-processor define

OSALMEM_METRICS=TRUE in the project options. After a stress test of the application where

you send as many messages, have as many clients as you will in the worst case, remembering to

use bonding and encryption during the test if that’s applicable, you can look at the value of the

variable memMax in OSAL_Memory.c to see how much memory was ever allocated at the same

time. This figure could be used as a guideline for lowering INT_HEAP_LEN if necessary, but

thorough testing is needed, as the heap is used by the BLE stack.

3.1.4 OSAL Messages

OSAL also provides a system for different subsystems of the software to communicate with each

other by sending or receiving messages. Messages can contain any type of data and can be any

size. To send an OSAL message, first the memory must be allocated by calling the

osal_msg_allocate function, passing in the length of the message as the only parameter. A

pointer to a buffer containing the allocated space will be returned (you do not need to use

osal_mem_alloc when using osal_msg_allocate). If no memory is available, a NULL pointer will

be returned. You can then copy the data into the buffer. To send the message, the

osal_msg_send should be called, with the destination task for the message indicated as a

parameter.

The OSAL will then signal the receiving task that a message is arriving by setting the

SYS_EVENT_MSG flag for that task. This causes the receiving task’s event handler function to

be called. The receiving task can then retrieve the data by calling osal_msg_receive, and can

process accordingly based on the data received. It is recommended that every OSAL task have a

local message processing function (the simpleBLEPeripheral application’s message processing

function is simpleBLEPeripheral_ProcessOSALMsg) that decides what action to take based on

the type of message received. Once the receiving task has completed processing the message, it

must deallocate the memory using the function osal_msg_deallocate (you do not need to use

osal_mem_free when using osal_msg_deallocate).

3.2 Hardware Abstraction Layer (HAL)

The Hardware Abstraction Layer (HAL) of the CC2540/41 software provides an interface of

abstraction between the physical hardware to and the application and protocol stack. This allows

for the development of new hardware (such as a new PCB) without making changes to the

protocol stack or application source code. The HAL includes software for the SPI and UART

communication interfaces, ADC, keys, and LED’s etc. The HAL drivers that are provided support

the following hardware platforms:

 SmartRF05EB + CC2540EM

 SmartRF05EB + CC2541EM

 CC2540 Keyfob

 CC2541 Keyfob

 CC2541 SensorTag

 CC2540 USB Dongle

When developing with a different hardware platform, it might be necessary to modify the HAL

source for compatibility.

More information on the HAL API can be found in [2].

TI CC254x Bluetooth Low Energy Software Developer’s Guide SWRU271F Version 1.3.1

3.3 BLE Protocol Stack

The entire BLE protocol stack is provided as object code in a single library file (Texas Instruments

does not provide the protocol stack source code as a matter of policy). The functionality of the

GAP and GATT layers should be understood as they interact directly with the application and

profiles.

3.3.1 Generic Access Profile (GAP)

The GAP layer of the BLE Protocol Stack is responsible for handling the device’s access modes

and procedures, including device discovery, link establishment, link termination, initiation of

security features, and device configuration.

The GAP layer is always operating in one of four roles:

 Broadcaster – an advertiser that is non-connectable

 Observer – scans for advertisements, but cannot initiate connections

 Peripheral – an advertiser that is connectable, and operates as a slave in a single link-layer

connection.

 Central – scans for advertisements and initiates connections; operates as a master in a

single or multiple link-layer connections. Currently, the BLE central stack supports up to three

simultaneous connections.

The BLE specification allows for certain combinations of multiple-roles. The default setup of the

sample application is to only support the peripheral role, though source code is provided to run a

combination peripheral and broadcaster role.

In a typical Bluetooth Low Energy system, the peripheral device advertises with specific data

letting any central device know that it is a connectable device. This advertisement contains the

device address, and can contain some additional data as well, such as the device name. The

central device, upon receiving the advertisement, sends a “scan request” to the peripheral. The

peripheral responds with a “scan response”. This is the process of device discovery, in that the

central device is now aware of the peripheral device, and knows that it can form a connection with

it. The central device can then send out a request to establish a link with the peripheral device. A

connection request contains a few connection parameters:

 Connection Interval – In a BLE connection between two devices, a frequency-hopping

scheme is used, in that the two devices each send and receive data from one another on a

specific channel, then “meet” at a new channel (the link layer of the BLE stack handles the

channel switching) at a specific amount of time later. This “meeting” where the two devices

send and receive data is known as a “connection event”. Even if there is no application data

to be sent or received, the two devices will still exchange link layer data to maintain the

connection. The connection interval is the amount of time between two connection events, in

units of 1.25ms. The connection interval can range from a minimum value of 6 (7.5ms) to a

maximum of 3200 (4.0s).

Different applications may require different connection intervals. The advantage of having a

very long connection interval is that significant power is saved, since the device can sleep

most of the time between connection events. The disadvantage is that if a device has data

that it needs to send, it must wait until the next connection event.

The advantage of having a very short connection interval is that there is more opportunity for

data to be sent or received, as the two devices will connect more frequently. The

disadvantage is that more power will be consumed, since the device is frequently waking up

for connection events.

 Slave Latency – This parameter gives the slave (peripheral) device the option of skipping a

number of connection events. This gives the peripheral device some flexibility, in that if it does

not have any data to send it can choose to skip connection events and stay asleep, thus

providing some power savings. The decision is up to the peripheral device.

剩余55页未读，继续阅读

beyondanytj

粉丝: 0
资源: 4

Texas Instruments CC2540/41 Bluetooth低能软件开发指南

TI CC2540_41 Bluetooth Low Energy Software Developer's Guide V1.2

CC2640_BLE_Software_Developer's_Guide.pdf

SWRU393_CC2640_BLE_Software_Developer's_Guide_中文翻译

Texas Instruments CC2540/41 BLE Software Developer’s Guide v1.3.2

CC2540 Bluetooth Low Energy Software Developer’s Guide

Texas Instruments CC254041 Bluetooth® Low Energy Software Developer’s Guide V1.4

cc2530_user_guide

ＢＬＥ细讲

BLE4.0 蓝牙概述

BLE协议栈实验教程

最新资源