Auracast MCU selection: nRF5340, STM32WBA, nRF52 and ESP32 compared

Auracast is one of the most interesting parts of Bluetooth LE Audio. It allows one transmitter to broadcast audio to many receivers, which makes it especially useful for public spaces, accessibility, hearing aids, museums, airports, railway stations, conference rooms and large-area assistive listening systems.

But there is one practical question that appears very early in every Auracast project:

Which MCU should we use?

The answer is not simply "any Bluetooth chip". Auracast depends on Bluetooth LE Audio, Broadcast Isochronous Streams, LC3 audio handling, timing, radio stability, SDK support and real-world interoperability with receivers. A chip that is great for BLE sensors may be a poor choice for Auracast audio.

In our current recommendation, the safest MCU family for a custom Auracast product is Nordic nRF53, especially nRF5340. ST STM32WBA is a strong fallback and a serious alternative. nRF52 can be used for experiments in some cases, but we would not treat it as a good production choice for Auracast. ESP32 is worth discussing because many teams search for "ESP32 Auracast", but the answer depends heavily on which ESP32 family you mean.

Auracast firmware development services

Evaluating Auracast MCU options for Nordic nRF5340, STM32WBA, or ESP32? Our Poland-based team builds proof-of-concept firmware and runs Auracast testing services with real receivers.

Explore embedded software development services

What makes Auracast different from normal BLE?

Classic BLE applications usually exchange small packets of data. Sensors, beacons, mobile app pairing, device configuration and firmware updates are typical examples.

Auracast is different. It is audio. That means the system must handle:

• Continuous audio data
• Predictable timing
• Low latency
• LC3 encoding or decoding
• Broadcast Isochronous Streams
• Periodic advertising
• Receiver discovery
• Metadata such as stream name and language
• Interoperability with phones, earbuds, hearing aids and assistants

This is why "Bluetooth 5.x support" alone is not enough. For LE Audio Auracast on MCU, the important question is whether the chip and SDK support the full audio path, not only generic BLE advertising.

Our default recommendation: Nordic nRF5340

For most custom Auracast transmitter prototypes and embedded products, we would start with Nordic nRF5340.

The reason is practical. nRF5340 was designed with Bluetooth LE Audio in mind. It has a dual-core architecture, strong Zephyr and nRF Connect SDK support, mature examples and a clear development path from evaluation kit to custom hardware.

For a software house or product team building an Auracast device, this matters more than a theoretical feature list. The biggest risk in Auracast development is not compiling a demo. The real risk is making the system stable with real receivers, real audio input, real power constraints and real product requirements.

nRF5340 is currently the best starting point when the goal is to reduce this risk.

Good use cases for nRF5340:

• Auracast broadcast source
• Assistive listening transmitter
• Public-space audio accessibility device
• Museum or guided-tour transmitter
• Airport or station announcement broadcaster
• Conference room audio streamer
• Prototype before custom hardware
• Interoperability testing platform

STM32WBA as a strong fallback

ST is also a valid option for Auracast development, but the right family is STM32WBA, not older STM32WB.

STM32WBA is interesting when the product already uses the STM32 ecosystem or when the team prefers STM32Cube tooling, STM32 security features and ST's MCU portfolio. ST provides LE Audio examples and Public Broadcast Profile support for STM32WBA boards.

For many companies, STM32WBA can be a good production path, especially if the rest of the product already fits the STM32 ecosystem.

Good use cases for STM32WBA:

• Auracast source prototypes
• STM32-based embedded products
• Public Broadcast Profile experiments
• USB audio to Auracast gateway concepts
• Products where STM32 supply chain and tooling are already preferred

Our practical recommendation is to evaluate STM32WBA early, but still compare SDK maturity, audio examples, receiver compatibility and debugging workflow against nRF5340 before making the final production decision.

What about nRF52?

This is where the answer needs nuance.

Can Bluetooth LE Audio be made to work on nRF52-class hardware in some situations?

Yes, in some cases and with third-party stacks or custom engineering effort.

Would we recommend nRF52 as the production MCU for a serious Auracast product?

Usually no.

The reason is not that nRF52 is a bad family. It is excellent for many BLE products. The problem is that Auracast needs more than standard BLE. You need isochronous audio support, LC3 handling, timing stability, memory headroom, SDK support and a realistic path to maintenance.

If the project is a lab experiment, a research prototype or a constrained proof of concept, nRF52 might be useful. If the project is a commercial Auracast transmitter or accessibility product, nRF5340 is the safer choice.

In other words:

nRF52 can be a clever experiment. nRF5340 is a production-oriented decision.

ESP32 Auracast: is it possible?

Many teams search for "ESP32 Auracast" or "Auracast ESP32" because ESP32 is affordable, popular and easy to source.

The important detail is that "ESP32" is not one chip anymore. It is a large family.

For classic ESP32 and many common ESP32 variants, we would not recommend planning a production Auracast product unless the exact chip and SDK version clearly support Bluetooth LE Audio, BIS/CIS and the required profile stack.

For newer Espressif chips such as ESP32-H4 and ESP32-S31, the situation is more interesting because Espressif has started positioning newer families around LE Audio and related Bluetooth features.

However, for client projects we would still validate:

• Is the exact chip available in production quantities
• Is LE Audio support available in the SDK version we can use now
• Are Broadcast Isochronous Streams supported and stable
• Is there a working Auracast source example
• Is LC3 included or easy to integrate
• Can it pass interoperability testing with real receivers
• Is there enough memory for the complete product
• Is certification risk acceptable

So the practical answer is:

ESP32 Auracast is not a safe generic statement. Some new ESP32 families are becoming relevant for LE Audio, but classic ESP32 should not be treated as an Auracast MCU.

Auracast MCU comparison

| MCU family | Auracast fit | Production recommendation | | -------------------------- | ------------------------- | --------------------------------------- | | Nordic nRF5340 | Very strong | Recommended default | | ST STM32WBA | Strong | Good fallback and alternative | | Nordic nRF52 | Possible in limited cases | Not recommended for production Auracast | | Classic ESP32 | Weak for Auracast | Not recommended | | Newer ESP32-H4 / ESP32-S31 | Promising | Evaluate carefully |

How we approach Auracast testing services

Choosing the MCU is only the first step. The harder part is proving that the system works outside the lab.

For Auracast testing services, we usually look at:

• Broadcast source stability
• Receiver discovery
• Audio quality
• Audio latency
• Stream naming and metadata
• Language and content selection
• Interoperability with phones
• Interoperability with earbuds
• Interoperability with hearing aids
• Performance in noisy 2.4 GHz environments
• Power consumption
• Antenna placement
• Audio input chain
• Firmware update strategy
• Certification readiness

This is especially important for large-area audio accessibility. A public-space Auracast installation must work reliably for many users, not only for one developer with one test receiver on a desk.

Auracast technology for large-area audio accessibility

Auracast has strong potential for accessibility because it can broadcast audio directly to compatible personal devices. This can include hearing aids, earbuds, headphones or dedicated receivers.

Possible use cases include:

• Railway station announcements
• Airport gate information
• Museum audio guides
• Conference translation channels
• Public TV audio in gyms and waiting rooms
• University lecture halls
• Churches and event venues
• Tourist information points
• Multilingual public announcements

For these applications, the technical challenge is not only "make audio play". The system must be understandable, stable and easy to join. Broadcast name, QR codes, NFC, audio levels, stream language, physical placement and receiver compatibility all matter.

Our recommendation

For a new Auracast product, we would start with nRF5340 unless there is a strong reason to choose another platform.

If the client already uses STM32 or wants to stay in the ST ecosystem, STM32WBA is a strong alternative.

We would mention nRF52 only as an experimental or legacy option, not as the main production path.

We would include ESP32 in the technical analysis because many teams ask about it, but we would be careful not to treat "ESP32" as one platform. Classic ESP32 is not a good Auracast choice. Newer ESP32 families may become relevant, but they need project-specific validation.

Need help with Auracast MCU selection or testing?

We help companies evaluate Bluetooth Auracast feasibility, select the right MCU, build proof-of-concept firmware and test real-world interoperability.

If you are considering Bluetooth Auracast, LE Audio on MCU or Auracast technology for large-area audio accessibility, we can help you validate the technical path before you commit to custom hardware.