What Problem This Class of Device Solves
Audio/wearable BLE ICs target TWS earbuds, smartwatches, and Bluetooth speakers, integrating a Bluetooth baseband, audio codec, and MCU/peripheral interfaces onto a single chip. This lets a design handle wireless connectivity and audio/sensor data processing together in a small board footprint, cutting the number of external codec chips and discrete components needed.
How to Read the Key Parameters
Bluetooth spec (BT Spec): catalog parts cover Bluetooth 5.0 and 5.2, both supporting BR/EDR/BLE + 2.4G proprietary multi-mode. A newer version generally means richer protocol features, but actual connection performance still depends on the stack implementation — pick based on the target product's positioning (a new-generation TWS earbud vs. a simple remote-control link).
Supply voltage range (VCC Range): catalog parts are rated 1.8V–5.5V, matching a typical wearable's direct lithium-battery supply or an LDO-stepped-down rail, simplifying the surrounding power circuit.
GPIO count: catalog parts offer 5–32 GPIOs. Check this against the number of peripheral sensors, buttons, and indicators needed — more GPIOs mean more integration headroom, but also a larger package.
Audio spec: catalog parts build in a 16-bit ADC and dual 16-bit stereo DAC/CODEC, letting the design drop an external standalone audio codec chip and simplify the BOM for earbud/speaker products.
Co-packaged Flash capacity: catalog parts offer 1/2/4/8/16/32Mb co-packaged Flash options. Pick a capacity that fits firmware size, audio-effect algorithms, and voice-prompt data — the same part number is often offered in several package sizes, including QFN20/32/40/48/56 and SOP16.
Three Steps to Select
- Bound the BT Spec candidates by the end product's Bluetooth version and multi-mode protocol requirements.
- Check GPIO count and audio spec against the peripheral and audio needs of the design (a built-in ADC/DAC can remove an external codec chip).
- Pick a co-packaged Flash capacity that fits firmware and voice-data storage needs, and confirm package size fits the wearable's mechanical space.
Common Pitfalls
- Judging only by the Bluetooth version number without checking multi-mode protocol support — some use cases need the 2.4G proprietary protocol for low-latency transparent transmission, which a "5.2" label alone doesn't confirm.
- Overlooking the match between co-packaged Flash capacity and firmware size — voice-prompt data and audio-effect algorithms grow quickly, and an undersized part limits future upgrade headroom.
- Reusing an old PCB footprint without checking pinout differences across the same part's package options (QFN20/32/40/48/56, SOP16, KGD).
To filter parts by specific parameter ranges, use the online selection tool on this site. For further technical questions, contact our engineers.