CSR蓝牙应用程序编程手册（中文版）

1 General

1 概述

BlueLab

TM

SDKs provide developers with a series of libraries that support the

implementation of Bluetooth applications that run on

Bluetooth○

R

chips.

BlueLab

TM

This approach has the additional benefit of allowing the underlying BlueCore

firmware to be considered as a pre-qualified component of the final product.

This document illustrates at a conceptual level how the source code and supplied

libraries are used to build Bluetooth applications to run on BlueCore chips.

This document introduces the fundamental concepts employed when developing

applications designed to run on CSR’s BlueCore chips.

The document covers:

The basic concepts and simple coding examples in this document are intended to

illustrate good practice when writing code to run on BlueCore’s Virtual Machine

and to help engineers gain a clearer understanding of using BlueLab SDKs to

develop applications.

The VM Memory Mapping and Memory Usage application note is also

recommended reading for engineers embarking on the process of developing

BlueCore applications.

Tasks are the basic architectural building blocks used to construct an application

and to provide an interface with the BlueCore firmware.

Tasks provide functionality to the application i.e. an instance of the appropriate

task must be initialized by the code in order for the functionality it supports to be

concurrently.

The tasks that make up the application include a top level task known as the

application task. The application task responds to messages and controls the

behavior of the application.

Messages pass information between the tasks and are constructed in the form:

message to identify the appropriate function within the handler code.

Message Id with a suffix of _T.

For example, the structure of the message CL_INIT_CFM is

enumerated as Type CL_INIT_CFM_T.

the handler function to correctly react to the message. The payload is

In some cases, the message id alone may be sufficient. Therefore, the

payload field is optional and can be Null.

values e.g. the connection library messages start at base 0x7000 and the SPP

library messages start at 0x6f00. See Appendix B.