Bluetooth Low Energy 5.x Guide: GATT, Advertising & Diagnostics

Core Technical Specifications

center Freq 2.402–2.480 GHz (40 channels, 2 MHz spacing)

modulation GFSK (1 Mbps LE 1M / 2 Mbps LE 2M)

data Encoding LE 1M, LE 2M, LE Coded (S=2, S=8)

operating Range 30–100 m (BLE 5.0+), 200+ m (Coded PHY)

antenna PCB trace or ceramic chip

tx Power Up to 20 dBm (BLE 5.0)

bandwidth 2 MHz per channel

channel Spacing 2 MHz, 40 channels (37 data + 3 advertising)

Real-World Devices & Applications

Wearables & Health

Fitness trackers and smartwatches
Heart rate monitors and pulse oximeters
Continuous glucose monitors (CGM)
Hearing aids (LE Audio)

IoT & Beacons

iBeacon / Eddystone location beacons
Smart locks and access control
Temperature/humidity sensors (BTHome, Xiaomi)
Asset tracking tags (Apple AirTag, Tile)

Reference Circuits & Schematics

BLE Module — nRF52840 / ESP32

The Nordic nRF52840 and Espressif ESP32 are the most popular BLE 5.0 SoCs. Both support BLE + Thread/Zigbee and include ARM Cortex-M4/RISC-V processors.

Pin	Description
`VCC`	1.7–5.5V (nRF52) or 3.3V (ESP32)
`GND`	Ground
`SWD/JTAG`	Debug/programming interface
`GPIO`	General purpose I/O for sensors/actuators
`ANT`	PCB trace antenna or u.FL

Circuit Walk-Through

BLE operates differently from Classic: devices advertise on channels 37, 38, 39 (2.402, 2.426, 2.480 GHz). A central device scans these channels, then initiates a connection. Data exchange uses GATT (Generic Attribute Profile) with services and characteristics. BLE 5.0 adds 2M PHY for double throughput and Coded PHY (S=8) for 4× range.

Signal Structure & Waveform Analysis

BLE Advertising & Connection

BLE devices alternate between advertising and connected states.

ADV Channels

Ch 37, 38, 39

2.402, 2.426, 2.480 GHz

ADV Packet

6–37 bytes

Device address + AD structures (name, UUID, flags)

Connection

37 data channels

Connection interval: 7.5 ms – 4 s

GATT Exchange

ATT MTU 23–512 bytes

Read/Write/Notify operations on characteristics

Timing Notes: Advertising interval: 20 ms – 10.24 s. Connection interval affects latency and power. Shorter interval = faster response, higher power. BLE 5.0 extended advertising supports up to 255 bytes per packet.

Analysis & Capture Tips

Use nRF Connect app (mobile) to scan BLE advertisements and inspect GATT services
nRF Sniffer with Wireshark for packet-level BLE capture
Check connection interval and MTU for throughput issues
Monitor RSSI during connection for signal quality

Bench Troubleshooting & Repair Guide

1. Device Not Found

nRF Connect / BLE Scanner app

Check advertising interval and TX power. Very long intervals (>1 s) make scanning slow. Verify device is in advertising mode (not already connected to another central).

2. Connection Drops

nRF Connect / HCI logs

Check connection interval, slave latency, and supervision timeout. Too-aggressive power saving (long slave latency) can cause supervision timeout. Verify RSSI > −80 dBm.

3. Throughput Issues

BLE throughput benchmark / Wireshark

Negotiate higher MTU (247 or 512 bytes). Use LE 2M PHY if both devices support it. Check connection interval — 7.5 ms gives maximum throughput.

Bluetooth LE 5.x