Bluetooth Low Energy SoCs for Wireless Sensor Nodes
Product Specifications
Product Overview
A Bluetooth Low Energy SoC integrates a 2.4 GHz radio, the link layer, the host stack and an application core in one package, so a sensor node runs from a single chip and a 32 MHz crystal. That is the reason these parts replaced the two chip route of a transceiver plus a host MCU on most battery products: the stack lives in the same flash as the application, the radio timing is handled in hardware, and the sleep current is one number instead of a budget split across two devices.
The first decision is memory, and it is driven by the update path rather than by the application code. A BLE 5 stack from Nordic, TI or Silicon Labs takes roughly 100 to 160 KB of flash for the link layer, the host and the sample application, which leaves a 192 KB part tight once a bootloader and a second image slot are added. A one MB part such as the nRF52840 or the STM32WB55RG carries the stack, the application, a bootloader and two image slots without an external flash chip, and that is the difference between an over the air update that can roll back and one that cannot.
The second decision is radio capability. BLE 5 added the 2M PHY, which doubles the symbol rate and shortens the time the radio is on for the same payload, and the coded PHY, which sends each bit four or eight times and gives roughly four times the range at 125 kbps. On a sensor node that has to reach a gateway through two walls, the coded PHY at 125 kbps is often the only way to close the link at the allowed transmit power, and a part without it will need a higher gain antenna or a repeater. Direction finding, used for indoor location, needs the constant tone extension and an antenna array at the receiver end, so the part and the board change together.
The third decision is the power path. Peak current during a transmit burst is 5 to 15 mA depending on the part and the output power, while the sleep current with the RTC running is 1 to 3 uA on the better parts and 5 to 10 uA on older ones. A CR2032 coin cell gives about 220 mAh, so a node that wakes every minute, transmits for 3 ms and sleeps in between lives for years on the 1 uA figure and for months on the 10 uA one. The DC to DC converter inside the chip is worth enabling for this reason: it holds efficiency while the cell voltage falls from 3.0 V to 2.0 V, where a linear regulator would simply burn the difference.
Supply range decides whether the cell can connect directly. Parts rated 1.7 V to 3.6 V need a boost stage once the cell falls below 1.8 V, which is early in a lithium cell life, while the nRF52840, the nRF52833 and the nRF5340 accept 1.7 V to 5.5 V and run from a coin cell or a 5 V rail without a converter. The 32 MHz crystal tolerance of 10 ppm and the 32.768 kHz crystal for the low power clock are part of the same budget: a 20 ppm crystal can be compensated in firmware, a sloppy load capacitance cannot, so both values go on the quotation with the chip.
Key Specifications
| Parameter | nRF52840 | EFR32BG22 | STM32WB55RG |
|---|---|---|---|
| Core | Cortex-M4F at 64 MHz | Cortex-M33 at 76.8 MHz | Cortex-M4 at 64 MHz plus Cortex-M0+ at 32 MHz |
| Flash and RAM | 1 MB flash, 256 KB RAM | 512 KB flash, 32 KB RAM | 1 MB flash, 256 KB RAM |
| Radio | BLE 5.2, 802.15.4, NFC tag | BLE 5.2 with direction finding | BLE 5.0 and 802.15.4 on the network core |
| Transmit power | Up to +8 dBm, configurable in 4 dB steps | Up to +6 dBm | Up to +6 dBm |
| Receive sensitivity | -95 dBm at 1M PHY, -103 dBm at 125 kbps coded | -96 dBm at 1M PHY, -106 dBm at 125 kbps | -95 dBm at 1M PHY |
| Supply range | 1.7 V to 5.5 V | 1.71 V to 3.8 V | 1.71 V to 3.6 V |
| Sleep current | 1.5 uA with RTC and full RAM | 1.4 uA with RTC and 32 KB RAM | 2.1 uA with RTC and 64 KB RAM |
| Package | aQFN73 7 x 7 mm, QFN48 6 x 6 mm | QFN32 4 x 4 mm, QFN40 5 x 5 mm | LQFP64, UFQFPN48 |
| Host interface | USB 2.0 full speed, QSPI, 2 x SPI, 2 x I2C | 2 x USART, 2 x I2C, I2S | USB 2.0 full speed, 3 x SPI, 3 x I2C |
Included Models and Order Codes
The table lists the order codes quoted most often for sensor nodes, trackers and medical patches. Core, memory and radio come from the maker data sheet for that code; the last column carries the point that usually decides the choice. Nordic codes read as family, memory and package, so the suffix after the dash tells you the package and the temperature grade.
| Part Number | Core | Flash / RAM | Radio | Transmit power | Supply | Package |
|---|---|---|---|---|---|---|
| nRF52840-QIAA | Cortex-M4F, 64 MHz | 1 MB / 256 KB | BLE 5.2, 802.15.4, NFC, USB | +8 dBm | 1.7 to 5.5 V | aQFN73, 7 x 7 mm |
| nRF52840-QFAA | Cortex-M4F, 64 MHz | 1 MB / 256 KB | BLE 5.2, 802.15.4, NFC | +8 dBm | 1.7 to 5.5 V | QFN48, 6 x 6 mm |
| nRF52833-QIAA | Cortex-M4F, 64 MHz | 512 KB / 128 KB | BLE 5.2, 802.15.4, USB | +8 dBm | 1.7 to 5.5 V | aQFN73, 7 x 7 mm |
| nRF52833-QDAA | Cortex-M4F, 64 MHz | 512 KB / 128 KB | BLE 5.2, 802.15.4 | +8 dBm | 1.7 to 5.5 V | QFN40, 5 x 5 mm |
| nRF52832-QFAA | Cortex-M4F, 64 MHz | 512 KB / 64 KB | BLE 5.0, NFC | +4 dBm | 1.7 to 3.6 V | QFN48, 6 x 6 mm |
| nRF52811-QFAA | Cortex-M4, 64 MHz | 192 KB / 24 KB | BLE 5.1, 802.15.4, direction finding | +4 dBm | 1.7 to 3.6 V | QFN48, 6 x 6 mm |
| nRF52810-QFAA | Cortex-M4, 64 MHz | 192 KB / 24 KB | BLE 5.0 | +4 dBm | 1.7 to 3.6 V | QFN48, 6 x 6 mm |
| nRF5340-QKAA | Cortex-M33, 128 MHz and 64 MHz | 1 MB / 512 KB | BLE 5.3, 802.15.4, USB | +3 dBm | 2.9 to 5.5 V | aQFN94, 7 x 7 mm |
| EFR32BG22C224F512GM32 | Cortex-M33, 76.8 MHz | 512 KB / 32 KB | BLE 5.2, direction finding | +6 dBm | 1.71 to 3.8 V | QFN32, 4 x 4 mm |
| EFR32BG22C224F512GM40 | Cortex-M33, 76.8 MHz | 512 KB / 32 KB | BLE 5.2, direction finding | +6 dBm | 1.71 to 3.8 V | QFN40, 5 x 5 mm |
| EFR32BG22C112F352GM32 | Cortex-M33, 76.8 MHz | 352 KB / 32 KB | BLE 5.2 | +6 dBm | 1.71 to 3.8 V | QFN32, 4 x 4 mm |
| CC2640R2FRHBR | Cortex-M3, 48 MHz plus sensor controller | 128 KB / 20 KB | BLE 4.2 and 5 | +5 dBm | 1.8 to 3.8 V | VQFN32, 5 x 5 mm |
| CC2640R2FRSMR | Cortex-M3, 48 MHz plus sensor controller | 128 KB / 20 KB | BLE 4.2 and 5 | +5 dBm | 1.8 to 3.8 V | VQFN32, 4 x 4 mm |
| CC2652R1FRGZR | Cortex-M4F, 48 MHz | 352 KB / 80 KB | BLE 5.2, Zigbee, Thread | +5 dBm | 1.8 to 3.8 V | VQFN48, 7 x 7 mm |
| CC2652P1FRGZR | Cortex-M4F, 48 MHz | 352 KB / 80 KB | BLE 5.2, Zigbee, Thread | +20 dBm | 1.8 to 3.8 V | VQFN48, 7 x 7 mm |
| STM32WB55RGV6 | Cortex-M4, 64 MHz plus Cortex-M0+ | 1 MB / 256 KB | BLE 5.0, 802.15.4, USB | +6 dBm | 1.71 to 3.6 V | LQFP64, 10 x 10 mm |
| STM32WB55CGU6 | Cortex-M4, 64 MHz plus Cortex-M0+ | 1 MB / 256 KB | BLE 5.0, 802.15.4, USB | +6 dBm | 1.71 to 3.6 V | UFQFPN48, 7 x 7 mm |
| BLUENRG-355AC | Cortex-M0+, 64 MHz | 256 KB / 64 KB | BLE 5.2, direction finding | +8 dBm | 1.7 to 3.6 V | QFN32, 5 x 5 mm |
| DA14531-00000FX2 | Cortex-M0+, 16 MHz | 32 KB OTP, 48 KB RAM | BLE 5.1 | +2.5 dBm | 1.1 to 3.6 V | WLCSP17, 2.5 x 2.5 mm |
| CYBLE-416045-02 | Cortex-M4F plus Cortex-M0+, module | 1 MB / 288 KB | BLE 5.0, pre-certified module | +4 dBm | 1.7 to 3.6 V | Module, 14 x 18.5 mm |
Key Features
Flash for the stack and the update – a BLE 5 stack takes 100 to 160 KB before the application starts, and an over the air update needs a second image slot, which is why a 192 KB part runs out and a 1 MB part does not.
Coded PHY buys range instead of antenna gain – the 125 kbps coded PHY repeats each bit and closes a link 4 times further than the 1M PHY at the same transmit power, which is usually cheaper than a bigger antenna and a higher gain front end.
The 32 MHz crystal is part of the radio spec – 10 ppm at 25 degrees centigrade with 8 pF load is what the stack assumes, and a 20 ppm part needs the offset written into the calibration table before the link will hold at 2M PHY.
DC to DC inside the chip holds the rail – with the converter enabled a node keeps its efficiency down to 2.0 V cell voltage, while a linear regulator simply dissipates the difference and halves the life of a CR2032.
Antenna keep out decides the range you get – the matching network is a three element pi section plus a keep out under the antenna, and a ground plane or a battery holder under it costs more range than a lower loss balun gains.
Dual core splits the stack from the application – on the nRF5340 and the STM32WB55 the network core runs the stack in its own flash, so a timing sensitive radio task cannot be delayed by the application loop.
Direction finding needs the array, not just the chip – the constant tone extension is sampled on several antennas, so the receiver board carries an antenna switch and a known spacing, and the accuracy comes from the array geometry.
Pre-certified modules vs chip down – a certified module such as CYBLE-416045-02 carries the radio approval, which removes a test cycle, at the cost of a fixed antenna and a higher unit price.
Applications
These parts are quoted for products that send a small amount of data on a battery, typically where:
Wireless sensor nodes and machine condition monitoring – a node wakes on a timer, reads a sensor over I2C or SPI and sends a few bytes, so the 1 uA sleep current and the +8 dBm transmit power decide how often it can report on one cell.
Wearables and medical patches – a small package such as WLCSP17 or QFN32 with a 1.1 V supply floor lets a single silver oxide cell run a patch, and the coded PHY keeps the link to the phone at a low duty cycle.
Asset trackers and electronic shelf labels – a tag that is awake for a few milliseconds per minute needs the RTC to run at 1 uA and the radio to hold a link through a shelf, which is the case the 125 kbps coded PHY was added for.
Smart locks and access control – the lock is asleep for months and must answer in under 200 ms, so the part has to wake from an interrupt, advertise and accept a connection without a firmware re-init.
Metering and sub metering – a meter reads a pulse counter and reports once a minute, and the 1.7 V to 5.5 V parts run from the same rail as the metering front end without a second converter.
Building automation and lighting control – a luminaire controller or a room sensor joins a mesh over 802.15.4 as well as a phone over BLE, which is why the multi protocol parts such as CC2652R and nRF52840 are quoted.
The SoC sits on the same board as the sensor front end and the antenna, so it is quoted with the SUPERB PCB and the assembly of that radio section.
Sourcing and Cross-Reference
Sourcing starts with the memory and update path rather than the core, because flash decides whether the product can be updated in the field. A 192 KB part is enough for a fixed function sensor with a wired programming header, and a 1 MB part is the practical minimum once a bootloader, a stack and two image slots have to coexist. On the SUPERB PCBA builds we quote, the flash figure is checked against the stack version actually being used, because a stack upgrade can add 20 KB and turn a working part into a tight one.
The second check is the radio bill of materials around the chip. Every one of these parts needs a 32 MHz crystal with the load capacitance the data sheet states, most need a 32.768 kHz crystal or an internal RC for the low power clock, and the single ended parts need a balun or a discrete matching network. The 32.768 kHz choice has a firmware cost: an internal RC saves two pins and a part but needs calibration against the radio clock, and the drift shows up as a timing error in the connection interval.
The third check is lifecycle and second source. The BLE families move quickly, and a code that is active today can go to not recommended for new products within two years, which matters on a meter with a ten year field life. We quote the recommended replacement at the same time as the active code, keep the data sheet revision on file, and confirm the package drawing before the board is released, because a change from QFN48 6 x 6 to QFN40 5 x 5 is a new land pattern and a new stencil.
For volume builds, SUPERB Assembly support covers the 32 MHz crystal placement, the matching network, the antenna keep out and the shield can footprint.
Q: Can you quote nRF52840-QIAA with the 32 MHz crystal and the matching balun, and send the aQFN73 land pattern with the package drawing?
A: Yes. Send the stack version, the update path and the antenna drawing, and the SUPERB Tech team will confirm the order code, the crystal load capacitance and the matching values from the maker data sheet before quoting.
Why Buyers Source BLE SoCs Through SUPERB
- Order code read back before quoting: the package and temperature suffix changes the land pattern and the price, so the full code is confirmed against the data sheet instead of being quoted from the family name.
- Flash checked against the stack version: the memory figure is compared with the stack the project actually uses, because a stack upgrade of 20 KB is enough to break an update path that was sized a year earlier.
- Crystal and matching named in the quote: the 32 MHz tolerance, the load capacitance and the balun are listed with the chip, so the radio bill of materials is complete at the first quotation.
- Lifecycle watched per code: each code is checked for a not recommended for new products notice, and the replacement is offered with the active part before a ten year product commits to it.
- Module or chip down argued both ways: a certified module removes a radio approval cycle and a chip down route gives the antenna and the cost, and the quotation states which one fits the volume and the schedule.
- Radio section quoted with the board: the antenna keep out, the shield can and the crystal placement are quoted with the assembly, because those are the parts that decide the range in production.
Related Product Families
This page is part of the component range we supply for industrial, telecom, medical and defence builds. Continue with: MCU and embedded processors, STM32F103 mainstream MCUs, Flight controller MCUs, Crystal units and TCXO oscillators, SPI NOR flash for firmware storage, Sourcing obsolete components.