nRF5340 Audio application requirements
The nRF5340 Audio applications are designed to be used only with the following hardware:
Hardware platforms |
PCA |
Board name |
Build target |
|---|---|---|---|
PCA10121 revision 1.0.0 or above |
|
Note
The applications supports PCA10121 revisions 1.0.0 or above. The applications are also compatible with the following pre-launch revisions:
Revisions 0.8.0 and above.
You need at least two nRF5340 Audio development kits (one with the gateway firmware and one with headset firmware) to test each of the applications. For CIS with TWS in mind, three kits are required.
If you want to test with other hardware (for example, a mobile phone or PC), it is highly recommended to test with Audio DKs on both the gateway and headset side first to verify basic functionality before moving on to testing with other vendors.
Software codec requirements
The nRF5340 Audio applications only support the LC3 software codec, developed specifically for use with LE Audio.
The applications can be configured for other alternative codecs, but this integration is beyond the scope of this documentation.
nRF5340 Audio development kit
The nRF5340 Audio development kit is a hardware development platform that demonstrates the nRF5340 Audio applications. Read the nRF5340 Audio DK Hardware documentation on Nordic Semiconductor Infocenter for more information about this development kit.
You can test the DK out of the box before you program it.
nRF5340 Audio configuration files
All applications use the Kconfig.defaults located in the nrf5340_audio directory.
Additionally, each nRF5340 Audio application uses its own, application-specific Kconfig.defaults file from the application directory, which includes configuration specific to the given application.
These files change the configuration defaults automatically, based on the different application versions and device types.
For each application, only one of the following .conf files is included when building:
prj.confis the default configuration file and it implements the debug application version.prj_release.confis the optional configuration file and it implements the release application version. No debug features are enabled in the release application version. When building using the command line, you must explicitly specify ifprj_release.confis going to be included instead ofprj.conf. See Building and running nRF5340 Audio applications for details.
In addition, the application features the child_image directory with hci_ipc.conf.
This file contains the necessary configurations for nRF5340 Audio applications to run the Bluetooth: HCI IPC sample with SoftDevice Controller for LE Isochronous Channels support.