CC2640 And CC2650 SimpleLink™ Bluetooth® Low Energy Software Stack 2.2.1 (Rev. D) SWRU393 BLE Developer's Guide

• Table of Contents
• Preface
• 1 Overview
  • 1.1 Introduction
  • 1.2 Bluetooth low energy Protocol Stack Basics
• 2 TI Bluetooth low energy Software Development Platform
  • 2.1 Hardware and Software Architecture Overview
    • 2.1.1 ARM Cortex M0 (Radio Core)
    • 2.1.2 ARM Cortex M3 (System Core)
  • 2.2 Protocol Stack and Application Configurations
  • 2.3 Solution Platform
  • 2.4 Directory Structure
    • 2.4.1 Examples Folder
    • 2.4.2 Source Folder
  • 2.5 Sample Applications
  • 2.6 Setting up the Integrated Development Environment
    • 2.6.1 Installing the SDK
    • 2.6.2 IAR
      • 2.6.2.1 Configuring IAR Embedded Workbench for ARM
      • 2.6.2.2 Using IAR Embedded Workbench
        • 2.6.2.2.1 Open an Existing Project
        • 2.6.2.2.2 Compile and Download
    • 2.6.3 Code Composer Studio
      • 2.6.3.1 Configure CCS
      • 2.6.3.2 Installing a Specific TI ARM Compiler
      • 2.6.3.3 Using CCS
        • 2.6.3.3.1 Import an Existing Project
        • 2.6.3.3.2 Workspace Overview
        • 2.6.3.3.3 Compiling and Downloading
  • 2.7 Working With Hex Files
  • 2.8 Accessing Preprocessor Symbols
  • 2.9 Top-Level Software Architecture
    • 2.9.1 Standard Project Task Hierarchy
• 3 RTOS Overview
  • 3.1 RTOS Configuration
  • 3.2 Semaphores
    • 3.2.1 Initializing a Semaphore
    • 3.2.2 Pending a Semaphore
    • 3.2.3 Posting a Semaphore
  • 3.3 RTOS Tasks
    • 3.3.1 Creating a Task
    • 3.3.2 Creating the Task Function
  • 3.4 Clocks
    • 3.4.1 API
    • 3.4.2 Functional Example
  • 3.5 Queues
    • 3.5.1 API
    • 3.5.2 Functional Example
  • 3.6 Idle Task
  • 3.7 Power Management
  • 3.8 Hardware Interrupts
  • 3.9 Software Interrupts
  • 3.10 Flash
    • 3.10.1 Flash Memory Map
    • 3.10.2 Application and Stack Flash Boundary
    • 3.10.3 Using Simple NV for Flash Storage
    • 3.10.4 Customer Configuration Area
  • 3.11 Memory Management (RAM)
    • 3.11.1 RAM Memory Map
    • 3.11.2 Application and Stack RAM Boundary
    • 3.11.3 System Stack
    • 3.11.4 Dynamic Memory Allocation
    • 3.11.5 Initializing RTOS Objects
  • 3.12 Configuration of RAM and Flash Boundary Using the Frontier Tool
    • 3.12.1 Frontier Tool Operation
    • 3.12.2 Disabling the Frontier Tool
• 4 The Application
  • 4.1 Start-Up in main()
  • 4.2 ICall
    • 4.2.1 Introduction
    • 4.2.2 ICall Bluetooth low energy Protocol Stack Service
    • 4.2.3 ICall Primitive Service
      • 4.2.3.1 Messaging and Thread Synchronization
      • 4.2.3.2 Heap Allocation and Management
    • 4.2.4 ICall Initialization and Registration
    • 4.2.5 ICall Thread Synchronization
    • 4.2.6 Example ICall Usage
  • 4.3 General Application Architecture
    • 4.3.1 Application Initialization Function
    • 4.3.2 Event Processing in the Task Function
      • 4.3.2.1 Task Events
      • 4.3.2.2 Intertask Messages
      • 4.3.2.3 Messages Posted to the RTOS Queue of the Application Task
      • 4.3.2.4 Events Signaled Through the Internal Event Variable
      • 4.3.2.5 Events Signaled Using TI-RTOS Events Module
    • 4.3.3 Callbacks
• 5 The Bluetooth low energy Protocol Stack
  • 5.1 Generic Access Profile (GAP)
    • 5.1.1 Connection Parameters
    • 5.1.2 Effective Connection Interval
    • 5.1.3 Connection Parameter Considerations
    • 5.1.4 Connection Parameter Limitations with Multiple Connections
    • 5.1.5 Connection Parameter Update
    • 5.1.6 Connection Termination
    • 5.1.7 GAP Abstraction
    • 5.1.8 Configuring the GAP Layer
  • 5.2 GAPRole Task
    • 5.2.1 Peripheral Role
    • 5.2.2 Central Role
  • 5.3 Generic Attribute Profile (GATT)
    • 5.3.1 GATT Characteristics and Attributes
    • 5.3.2 GATT Services and Profile
      • 5.3.2.1 GAP GATT Service
        • 5.3.2.1.1 Using the GGS
      • 5.3.2.2 Generic Attribute Profile Service
        • 5.3.2.2.1 Using the GATT Service
    • 5.3.3 GATT Client Abstraction
      • 5.3.3.1 Using the GATT Layer Directly
    • 5.3.4 GATT Server Abstraction
      • 5.3.4.1 GATTServApp Module
        • 5.3.4.1.1 Building up the Attribute Table
      • 5.3.4.2 Profile Architecture
        • 5.3.4.2.1 Attribute Table Definition
        • 5.3.4.2.2 Add Service Function
        • 5.3.4.2.3 Register Application Callback Function
        • 5.3.4.2.4 Read and Write Callback Functions
        • 5.3.4.2.5 Get and Set Functions
      • 5.3.4.3 Queued Writes
    • 5.3.5 Allocating Memory for GATT Procedures
    • 5.3.6 Registering to Receive Additional GATT Events in the Application
    • 5.3.7 GATT Security
      • 5.3.7.1 Authentication
      • 5.3.7.2 Authorization
  • 5.4 GAP Bond Manager and LE Secure Connections
    • 5.4.1 Overview
    • 5.4.2 Selection of Pairing Mode
    • 5.4.3 Using GAPBondMgr
    • 5.4.4 GAPBondMgr Examples for Different Pairing Modes
      • 5.4.4.1 Pairing Disabled
      • 5.4.4.2 Just Works Pairing
      • 5.4.4.3 Passcode Entry
      • 5.4.4.4 Numeric Comparison
      • 5.4.4.5 GAPBondMgr Example With Bonding Enabled
      • 5.4.4.6 GAPBondMgr and SNV
    • 5.4.5 LE Privacy 1.2
      • 5.4.5.1 Summary
      • 5.4.5.2 Theory of Operation
      • 5.4.5.3 Enabling Privacy
      • 5.4.5.4 New HCI Commands
      • 5.4.5.5 Privacy and White List
        • 5.4.5.5.1 Enabling Auto Sync of White List
        • 5.4.5.5.2 Using Resolvable Private Addresses
        • 5.4.5.5.3 Testing Privacy with White List
  • 5.5 Logical Link Control and Adaptation Layer Protocol (L2CAP)
    • 5.5.1 General L2CAP Terminology
    • 5.5.2 Maximum Transmission Unit (MTU)
      • 5.5.2.1 Configuring for Larger MTU Values
    • 5.5.3 L2CAP Channels
    • 5.5.4 L2CAP Connection-Oriented Channel (CoC) Example
  • 5.6 LE Data Length Extension
    • 5.6.1 Summary
    • 5.6.2 Data Length Update Procedure
    • 5.6.3 Initial Values
    • 5.6.4 Data Length Extension HCI Commands and Events
    • 5.6.5 Enabling Extended Packet Length Feature
      • 5.6.5.1 Enabling the Feature in the BLE-Stack
      • 5.6.5.2 Enable the Feature at Run Time
      • 5.6.5.3 Set Packet Length in a Connection
  • 5.7  HCI
    • 5.7.1 Using HCI and HCI Vendor-Specific Commands in the Application
    • 5.7.2 Standard LE HCI Commands and Events
      • 5.7.2.1 Sending an HCI Command
      • 5.7.2.2 Receiving HCI Events
    • 5.7.3 HCI Vendor-Specific Commands
      • 5.7.3.1 Sending HCI Vendor-Specific Command
      • 5.7.3.2 Receiving HCI Vendor-Specific Events
  • 5.8 Run-Time Bluetooth low energy Protocol Stack Configuration
  • 5.9 Configuring Bluetooth low energy Protocol Stack Features
• 6 Peripherals and Drivers
  • 6.1 Adding a Driver
  • 6.2 Board File
  • 6.3 Board Level Drivers
  • 6.4 Creating a Custom Board File
  • 6.5 Available Drivers
    • 6.5.1 PIN
    • 6.5.2 UART and SPI
    • 6.5.3 Other Drivers
  • 6.6 Using 32-kHz Crystal-Less Mode
• 7 Sensor Controller
• 8 Startup Sequence
  • 8.1 Programming Internal Flash With the ROM Bootloader
  • 8.2 Resets
• 9 Development and Debugging
  • 9.1 Debug Interfaces
    • 9.1.1 Connecting to the XDS Debugger
      • 9.1.1.1 Debugging Using CCS
      • 9.1.1.2 Debugging Using IAR
  • 9.2 Breakpoints
    • 9.2.1 Breakpoints in CCS
    • 9.2.2 Breakpoints in IAR
    • 9.2.3 Considerations When Using Breakpoints With an Active Bluetooth low energy Connection
    • 9.2.4 Considerations no Breakpoints and Compiler Optimization
  • 9.3 Watching Variables and Registers
    • 9.3.1 Variables in CCS
    • 9.3.2 Variables in IAR
    • 9.3.3 Considerations When Viewing Variables
  • 9.4 Memory Watchpoints
    • 9.4.1 Watchpoints in CCS
    • 9.4.2 Watchpoints in IAR
  • 9.5 TI-RTOS Object Viewer
    • 9.5.1 Scanning the BIOS for Errors
    • 9.5.2 Viewing the State of Each Task
    • 9.5.3 Viewing the System Stack
    • 9.5.4 Viewing Power Manager Information
  • 9.6 Profiling the ICall Heap Manager (heapmgr.h)
    • 9.6.1 Determining the Auto Heap Size
  • 9.7 Optimizations
    • 9.7.1 Project-Wide Optimizations
    • 9.7.2 Single-File Optimizations
    • 9.7.3 Single-Function Optimizations
    • 9.7.4 Loading RTOS in ROM Symbols
  • 9.8 Deciphering CPU Exceptions
    • 9.8.1 Exception Cause
    • 9.8.2 Using TI-RTOS and ROV to Parse Exceptions
  • 9.9 Debugging a Program Exit
  • 9.10 Assert Handling
    • 9.10.1 Catching Stack Asserts in the Application
    • 9.10.2 Catching App Asserts in the Application
  • 9.11 Debugging Memory Problems
    • 9.11.1 Task and System Stack Overflow
    • 9.11.2 Dynamic Allocation Errors
  • 9.12 Preprocessor Options
    • 9.12.1 Modifying
    • 9.12.2 Options
  • 9.13 Check System Flash and RAM Usage With Map File
• 10 Creating a Custom Bluetooth low energy Application
  • 10.1 Adding a Board File
  • 10.2 Configuring Parameters for Custom Hardware
  • 10.3 Creating Additional Tasks
  • 10.4 Optimizing Bluetooth low energy Stack Memory Usage
    • 10.4.1 Additional Memory Configuration Options
  • 10.5 Defining Bluetooth low energy Behavior
• 11 Porting from CC254x to CC2640
  • 11.1 Introduction
  • 11.2 OSAL
  • 11.3 Application and Stack Separation With ICall
  • 11.4 Threads, Semaphores, and Queues
  • 11.5 Peripheral Drivers
  • 11.6 Event Processing
• 12 Sample Applications
  • 12.1 Blood Pressure Sensor
    • 12.1.1 Interface
    • 12.1.2 Operation
  • 12.2 Heart Rate Sensor
    • 12.2.1 Interface
    • 12.2.2 Operation
  • 12.3 Cycling Speed and Cadence (CSC) Sensor
    • 12.3.1 Interface
    • 12.3.2 Operation
    • 12.3.3 Neglect Timer
  • 12.4 Running Speed and Cadence (RSC) Sensor
    • 12.4.1 Interface
    • 12.4.2 Operation
    • 12.4.3 Neglect Timer
  • 12.5 Glucose Collector
    • 12.5.1 Interface
    • 12.5.2 Record Access Control Point
  • 12.6 Glucose Sensor
    • 12.6.1 Interface
    • 12.6.2 Operation
  • 12.7 HID–Emulated Keyboard
    • 12.7.1 Interface
    • 12.7.2 Operation
  • 12.8 HostTest–Bluetooth low energy Network Processor
  • 12.9 KeyFob
    • 12.9.1 Interface
    • 12.9.2 Battery Operation
    • 12.9.3 Accelerometer Operation
    • 12.9.4 Keys
    • 12.9.5 Proximity
  • 12.10 SensorTag
    • 12.10.1 Operation
    • 12.10.2 Sensors
  • 12.11 Simple BLE Central
    • 12.11.1 Interface
  • 12.12 Simple BLE Peripheral
  • 12.13 Simple Application Processor
  • 12.14 Simple Network Processor
  • 12.15 TimeApp
    • 12.15.1 Interface
    • 12.15.2 Operation
  • 12.16 Thermometer
    • 12.16.1 Interface
    • 12.16.2 Operation
• A GAP API
  • A.1 Commands
  • A.2 Configurable Parameters
  • A.3 Events
• B GAPRole Peripheral Role API
  • B.1 Commands
  • B.2 Configurable Parameters
  • B.3 Callbacks
    • B.3.1 State Change Callback (pfnStateChange)
• C GAPRole Central Role API
  • C.1 Commands
  • C.2 Configurable Parameters
  • C.3 Callbacks
    • C.3.1 Central Event Callback (eventCB)
• D GATT and ATT API
  • D.1 General Commands
  • D.2 Server Commands
  • D.3 Client Commands
  • D.4 Return Values
  • D.5 Events
  • D.6 GATT Commands and Corresponding ATT Events
  • D.7 ATT_ERROR_RSP errCodes
• E GATTServApp API
  • E.1 Commands
• F GAPBondMgr API
  • F.1 Commands
  • F.2 Configurable Parameters
  • F.3 Callbacks
    • F.3.1 Passcode Callback (passcodeCB)
    • F.3.2 Pairing State Callback (pairStateCB)
• G L2CAP API
  • G.1 Commands
• H HCI API
  • H.1 HCI Commands
  • H.2 Vendor-Specific HCI Commands
  • H.3 Host Error Codes
• I ICall API
  • I.1 Commands
  • I.2 Error Codes
• Revision History
• Revision History
• Revision History
• Important Notice