SDK
Software Development Kit -- the vendor-provided toolchain for developing BLE firmware (e.g. nRF Connect SDK, ESP-IDF).
SDK (Software Development Kit)
A BLE SDK (Software Development Kit) is the vendor-provided software toolchain used to develop firmware for a BLE SoC or Module. It includes the BLE protocol stack, hardware abstraction layers, example applications, build system, and debugging tools -- everything needed to go from silicon to working BLE product.
SDK Components
A complete BLE SDK typically includes:
- BLE host stack: Implementation of L2CAP, ATT, GATT, SMP, and GAP
- BLE controller: Link Layer, PHY management, HCI transport
- HAL (Hardware Abstraction Layer): GPIO, UART, SPI, I2C, ADC drivers
- RTOS integration: Zephyr, FreeRTOS, or bare-metal scheduler
- Profiles and services: Heart Rate, Battery, DFU/OTA, and custom service templates
- Build system: CMake, Make, or IDE-based (Segger Embedded Studio, VS Code)
- Examples: Beacon, peripheral, central, mesh, LC3 codec and Auracast." data-category="LE Audio">LE Audio sample applications
Major BLE SDKs
| SDK | Vendor | SoC Family | RTOS |
|---|---|---|---|
| nRF Connect SDK | Nordic | nRF52, nRF53, nRF54 | Zephyr |
| nRF5 SDK (legacy) | Nordic | nRF51, nRF52 | Bare-metal / FreeRTOS |
| ESP-IDF | Espressif | ESP32, ESP32-C3/C6/S3/H2 | FreeRTOS |
| SimpleLink SDK | Texas Instruments | CC26x2, CC13x2 | TI-RTOS / FreeRTOS |
| Gecko SDK | Silicon Labs | EFR32BG | Micrium OS |
| STM32CubeWB | STMicro | STM32WB | FreeRTOS |
Choosing an SDK
SDK quality often matters more than raw silicon performance for product development velocity. Key evaluation criteria include:
- Documentation depth: API reference, tutorials, migration guides
- Example coverage: Does the SDK include examples for your target profile (LE Audio, Mesh, Direction Finding)?
- Community and support: Forums, GitHub issues, DevZone (Nordic), ESP-IDF community
- Toolchain compatibility: GCC ARM, IAR, Segger, VS Code extension quality
- OTA update support: Built-in DFU bootloader and mobile libraries
Development Workflow
A typical BLE firmware development workflow involves: selecting a sample application, configuring GATT services and characteristics, implementing application logic in callbacks, testing with a mobile tool (nRF Connect, LightBlue), and then optimizing power consumption by tuning Connection Interval, Slave Latency, and TX Power.
Related Terms
Related Content
Getting Started with nRF Connect SDK and Zephyr
DevelopmentnRF Connect SDK Development The nRF Connect SDK (NCS) is Nordic…
BLE Chip Selection Guide: How to Choose the Right SoC
Hardware & Design…locks you into a sub-optimal power budget, an immature SDK , or a supply chain risk that haunts production. This…
Frequently Asked Questions
Our glossary covers 90+ BLE technical terms organized by category. Each term includes a definition, related terms, and links to relevant chips and guides.