Table of Contents
LE Audio Code Migration Need tools
Current experimental platform and environment
Test platform: BT631D (NRF5340)
SDK version: NCS2.3.0
|Bluetooth Module Model||FSC-BT631D|
|Bluetooth version||Bluetooth 5.3|
|Dimension||12mm x 15mm x 2.2mm|
|Transmit Power||nRF5340 :+3 dBm|
|CSR8811:+5 dBm(Basic Data Rate)|
|Profiles||GAP, ATT, GATT, SMP, L2CAP|
|Frequency||2.402 - 2.480 GHz|
Need to implement LE audio content
- LC3 encoding and decoding
- LE transmission encoding data
- Support for multiple streaming functions
- Support CIS unicast audio function
- Support BIS broadcast audio function
Embed protocol stack contents
The execution sequence and flowchart are shown below
- The gateway receives audio data from the audio source.
- The gateway processes audio data in its application core and transmits data through the application layer:
- The host sends the encoded audio data to the network kernel subsystem (controller).
- The subsystem forwards audio data LE to the hardware radio and sends it to the headphone device.
- The headphone receives encoded audio data on the network core.
- The network kernel subsystem (controller) sends encoded audio data to the LE host on the headphone application core.
- Headphones process audio data in their application cores, which transmit data through the application layer:
- The decoded audio data is sent to the hardware audio output through I2S.
Le audio is currently a new technology with few mature product solutions on the market, complex engineering, and many problems that need to be solved!
The LE audio code migration process is a very complex , but the BT631D module testing results are relatively good after migration. Users who need this function can contact the Feasycom team!