nRF Audio application requirements

The nRF Audio applications are designed to be used only with the following hardware:

Hardware platforms

PCA

Board name

Board target

nRF5340 Audio DK

PCA10121 revision 1.0.0 or above

nrf5340_audio_dk

nrf5340_audio_dk/nrf5340/cpuapp

nRF5340 DK

PCA10095

nrf5340dk

nrf5340dk/nrf5340/cpuapp

You need at least two nRF5340 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 nRF 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 nRF Audio applications. Read the nRF5340 Audio DK Hardware documentation for more information about this development kit.

You can test the DK out of the box before you program it.

nRF Audio configuration files

The applications use the same Source file architecture and the same Kconfig.defaults file in the nrf_audio directory. You can however select different *.conf files to build them as either debug or release. Each nRF Audio application also uses its own, application-specific overlay file.

You need the following configuration files to build the application:

  • Application version configuration file: prj.conf or prj_release.conf.

  • Application-specific overlay file (overlay-<app_name>.conf) from the application directory.

When building using the command line, you must explicitly specify the *.conf files that are going to be included. See Building and programming using standard methods for more information.

When building using the script, you specify parameters for building instead of the file names.