nRF audio DK reference application not visible to smartphone scan

RE: nRF audio DK reference application not visible to smartphone scan

dejans — Thu, 01 Aug 2024 13:34:19 GMT

Hi Ermal,

If this issue does not get resolved in the next NCS version, please let me know.

Best regards,
Dejan

RE: nRF audio DK reference application not visible to smartphone scan

dejans — Tue, 16 Jul 2024 08:41:11 GMT

Hi Ermal,

As a short update, this issue might get fixed in the next NCS version.

Thank you for your patience.

Best regards,
Dejan

RE: nRF audio DK reference application not visible to smartphone scan

dejans — Fri, 31 May 2024 10:43:38 GMT

Hi Ermal,

The issue is under investigation. I will get back to you, but at the moment I cannot provide estimate on when this issue might get resolved.

Best regards,
Dejan

RE: nRF audio DK reference application not visible to smartphone scan

ermalh — Wed, 29 May 2024 20:00:22 GMT

The model and iOS version are: iPhone13Pro iOS 17.4.1.

(Please note that I tried with my Dell laptop and with an iPhone15ProMax as well without success)

Thank you!

-Ermal

RE: nRF audio DK reference application not visible to smartphone scan

dejans — Wed, 29 May 2024 17:24:19 GMT

Hi,

Thank you for sharing your project.

I have reported your issue internally. The issue seems to be already known on iOS devices.

Could you provide your iPhone product details such as model number and iOS version?

Best regards,
Dejan

RE: nRF audio DK reference application not visible to smartphone scan

ermalh — Tue, 28 May 2024 15:14:02 GMT

Hi Dejan, being able to test the EVK is vital for our project. I am not sure what exactly you are looking for and I can share the full zipped project with you.

As I told you already I simply created a copy of the sample project. I tried to execute with two different SDK versions 2.6.1 and 2.4.0. I tried to build and flash from VScode and from command line as described in your online documentation. When I connect to my iphone using the nRFconnect APP we experience this issue where the unit gets disconnected cyclically 160-170ms after connecting (see the data log that I already attached) (that's why my phone does not find the unit I guess).

devzone.nordicsemi.com/.../8623.nrf5340_5F00_audio.zip

RE: nRF audio DK reference application not visible to smartphone scan

dejans — Thu, 23 May 2024 14:42:53 GMT

Hi ermalh ,

I am sorry for a delayed reply. I was out of the office.

Could you please provide all necessary steps (including code and configuration changes, and build command) which I could follow when trying to replicate the issue?

Best regards,
Dejan

RE: nRF audio DK reference application not visible to smartphone scan

Kenneth — Tue, 21 May 2024 11:29:26 GMT

Hello,

There have been a few public holidays here due to National day among other. Dejan should be able to look into your follow up end of this week.

Kenneth

RE: nRF audio DK reference application not visible to smartphone scan

ermalh — Sat, 18 May 2024 13:03:16 GMT

Hi Dejan, as we can see in the log, the unit disconnects regularly about 160-170ms after connecting.

Do you have any recommendations?

RE: nRF audio DK reference application not visible to smartphone scan

ermalh — Mon, 13 May 2024 15:01:06 GMT

Hi Dejan,

[quote userid="111786" url="~/f/nordic-q-a/110933/nrf-audio-dk-reference-application-not-visible-to-smartphone-scan/482749"]How did you perform the scan? Which application did you use on the laptop and iPhones? Did you try with Android phone?[/quote]

I don't use any application, I am scanning for available bluetooth devices using my iphone or my windows laptop. I did not try an android phone.

[quote userid="111786" url="~/f/nordic-q-a/110933/nrf-audio-dk-reference-application-not-visible-to-smartphone-scan/482749"]Are you using 2 different devices that you programmed as headset and gateway, or do you have only one device which you previously programmed as headset and now as gateway?[/quote]

I am using a single device. The purpose is to evaluate the LE audio DK and the possibility to use this platform for the development of a headset.

[quote userid="111786" url="~/f/nordic-q-a/110933/nrf-audio-dk-reference-application-not-visible-to-smartphone-scan/482749"]Can you show this "connecting ..." status?[/quote]

When I use my laptop or iphone, the NRF5340_AUDIO device is not discoverable. However, when I use the nRF connect mobile app, I am able to see the device NRF5340_AUDIO. When connecting to it, the app seems to hang in the "Connecting" state for a minute. The serial log of the device looks like this:

HL [00:15:59.873,474] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:01.154,357] <inf> bt_mgmt: Directed adv timed out with no connection, reverting to normal adv
HL [00:16:01.157,287] <inf> bt_mgmt_adv: Local addr: 73:7D:73:4E:07:29 (random)
HL [00:16:01.158,203] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:02.850,494] <inf> bt_mgmt: Connected: F8:C3:CC:16:E3:ED (public)
HL [00:16:02.850,524] <inf> main: Connected
HL [00:16:03.021,087] <inf> bt_mgmt: Disconnected: F8:C3:CC:16:E3:ED (public) (reason 0x3e)
HL [00:16:03.021,087] <inf> main: Disconnected
HL [00:16:03.021,118] <wrn> bt_content_ctrl_media: Unable to look up conn pointer: -3
HL [00:16:03.021,118] <err> bt_content_ctrl: bt_content_ctrl_media_conn_disconnected failed with -3
HL [00:16:03.022,735] <inf> bt_mgmt_adv: Local addr: 73:7D:73:4E:07:29 (random)
HL [00:16:03.022,827] <inf> bt_mgmt_adv: Adv directed to: F8:C3:CC:16:E3:ED (public).
HL [00:16:03.023,437] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:04.304,321] <inf> bt_mgmt: Directed adv timed out with no connection, reverting to normal adv
HL [00:16:04.307,250] <inf> bt_mgmt_adv: Local addr: 76:05:04:36:2E:D3 (random)
HL [00:16:04.308,166] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:09.780,120] <inf> bt_mgmt: Connected: F8:C3:CC:16:E3:ED (public)
HL [00:16:09.780,151] <inf> main: Connected
HL [00:16:09.951,904] <inf> bt_mgmt: Disconnected: F8:C3:CC:16:E3:ED (public) (reason 0x3e)
HL [00:16:09.951,934] <inf> main: Disconnected
HL [00:16:09.951,934] <wrn> bt_content_ctrl_media: Unable to look up conn pointer: -3
HL [00:16:09.951,965] <err> bt_content_ctrl: bt_content_ctrl_media_conn_disconnected failed with -3
HL [00:16:09.953,582] <inf> bt_mgmt_adv: Local addr: 76:05:04:36:2E:D3 (random)
HL [00:16:09.953,643] <inf> bt_mgmt_adv: Adv directed to: F8:C3:CC:16:E3:ED (public).
HL [00:16:09.954,284] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:11.235,168] <inf> bt_mgmt: Directed adv timed out with no connection, reverting to normal adv
HL [00:16:11.238,098] <inf> bt_mgmt_adv: Local addr: 76:D0:4D:1F:15:D8 (random)
HL [00:16:11.239,013] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:13.352,355] <inf> bt_mgmt: Connected: F8:C3:CC:16:E3:ED (public)
HL [00:16:13.352,386] <inf> main: Connected
HL [00:16:13.521,667] <inf> bt_mgmt: Disconnected: F8:C3:CC:16:E3:ED (public) (reason 0x3e)
HL [00:16:13.521,667] <inf> main: Disconnected
HL [00:16:13.521,697] <wrn> bt_content_ctrl_media: Unable to look up conn pointer: -3
HL [00:16:13.521,697] <err> bt_content_ctrl: bt_content_ctrl_media_conn_disconnected failed with -3
HL [00:16:13.523,315] <inf> bt_mgmt_adv: Local addr: 76:D0:4D:1F:15:D8 (random)
HL [00:16:13.523,406] <inf> bt_mgmt_adv: Adv directed to: F8:C3:CC:16:E3:ED (public).
HL [00:16:13.524,017] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:14.804,901] <inf> bt_mgmt: Directed adv timed out with no connection, reverting to normal adv
HL [00:16:14.807,830] <inf> bt_mgmt_adv: Local addr: 71:C8:74:03:0A:A2 (random)
HL [00:16:14.808,746] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:16.065,765] <inf> bt_mgmt: Connected: F8:C3:CC:16:E3:ED (public)
HL [00:16:16.065,795] <inf> main: Connected
HL [00:16:16.222,595] <inf> bt_mgmt: Disconnected: F8:C3:CC:16:E3:ED (public) (reason 0x3e)
HL [00:16:16.222,625] <inf> main: Disconnected
HL [00:16:16.222,625] <wrn> bt_content_ctrl_media: Unable to look up conn pointer: -3
HL [00:16:16.222,625] <err> bt_content_ctrl: bt_content_ctrl_media_conn_disconnected failed with -3
HL [00:16:16.224,243] <inf> bt_mgmt_adv: Local addr: 71:C8:74:03:0A:A2 (random)
HL [00:16:16.224,334] <inf> bt_mgmt_adv: Adv directed to: F8:C3:CC:16:E3:ED (public).
HL [00:16:16.224,945] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:17.505,828] <inf> bt_mgmt: Directed adv timed out with no connection, reverting to normal adv
HL [00:16:17.508,789] <inf> bt_mgmt_adv: Local addr: 57:01:2A:0E:98:CF (random)
HL [00:16:17.509,704] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:20.258,697] <inf> bt_mgmt: Connected: F8:C3:CC:16:E3:ED (public)
HL [00:16:20.258,728] <inf> main: Connected
HL [00:16:20.421,783] <inf> bt_mgmt: Disconnected: F8:C3:CC:16:E3:ED (public) (reason 0x3e)
HL [00:16:20.421,783] <inf> main: Disconnected
HL [00:16:20.421,813] <wrn> bt_content_ctrl_media: Unable to look up conn pointer: -3
HL [00:16:20.421,813] <err> bt_content_ctrl: bt_content_ctrl_media_conn_disconnected failed with -3
HL [00:16:20.423,431] <inf> bt_mgmt_adv: Local addr: 57:01:2A:0E:98:CF (random)
HL [00:16:20.423,522] <inf> bt_mgmt_adv: Adv directed to: F8:C3:CC:16:E3:ED (public).
HL [00:16:20.424,133] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:21.705,017] <inf> bt_mgmt: Directed adv timed out with no connection, reverting to normal adv
HL [00:16:21.707,946] <inf> bt_mgmt_adv: Local addr: 4E:A6:8A:D7:DF:6D (random)
HL [00:16:21.708,862] <inf> bt_mgmt_adv: Advertising successfully started
HL [00:16:23.193,054] <inf> bt_mgmt: Connected: F8:C3:CC:16:E3:ED (public)
HL [00:16:23.193,084] <inf> main: Connected
HL [00:16:23.569,244] <inf> main: Security changed
HL [00:16:23.629,211] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
HL [00:16:23.718,963] <err> bt_content_ctrl_media: Discovery of MCS failed (-61)

It seems like it connects and tries cyclically to establish a connection until it eventually stops with the following message:

<err> bt_content_ctrl_media: Discovery of MCS failed (-61)

At this point the nRF mobile connect app shows as in the "Connected" state. I am able to see all the services through the app. But I am unable to connect it as an audio device to my laptop or iphone.

Is this behavior normal and expected or could it be the reason that my audio DK is not discoverable and cannot connect to my iphone/laptop?

RE: nRF audio DK reference application not visible to smartphone scan

dejans — Fri, 10 May 2024 09:24:23 GMT

Hi,

Are you using 2 different devices that you programmed as headset and gateway, or do you have only one device which you previously programmed as headset and now as gateway?

[quote user="ermalh"]I tried to connect to the device but without success (connecting...)[/quote]

Can you show this "connecting ..." status?

[quote user="ermalh"]I used various devices (laptop and iphones) to scan for the nrf5340. I was able to detect it only once after so many different tries.[/quote]

How did you perform the scan? Which application did you use on the laptop and iPhones? Did you try with Android phone?

[quote user="ermalh"]I used the nRF Kconfig GUI to change the configuration and I was able to see the device once after scanning for bluetooth devices with my laptop. [/quote]

Which configuration changes have you made? Have you tried editing the configuration without using Kconfig GUI?

Best regards,
Dejan

RE: nRF audio DK reference application not visible to smartphone scan

ermalh — Thu, 09 May 2024 03:22:28 GMT

Hi Dejan,

I tried to program it as gateway from VScode, I used the nRF Kconfig GUI to change the configuration and I was able to see the device once after scanning for bluetooth devices with my laptop. I tried to connect to the device but without success (connecting...)

I used various devices (laptop and iphones) to scan for the nrf5340. I was able to detect it only once after so many different tries.

I have no clue if there is anything I am doing wrong or if there is a bug somewhere in the example code.

RE: nRF audio DK reference application not visible to smartphone scan

dejans — Wed, 08 May 2024 14:09:25 GMT

Hi,

[quote user="ermalh"]I am able to program the unit to right channel or left channel (the LED color updates) but the unit is never discoverable via bluetooth scan.[/quote]

You could test if the application works as expected when you use both headset and gateway devices. You could also try to build the application only for headset device using "-d headset" option in your buildprog command. What are the results?

How did you do Bluetooth scanning?

Best regards,
Dejan

RE: nRF audio DK reference application not visible to smartphone scan

ermalh — Tue, 07 May 2024 22:29:42 GMT

Hi Dejan,

I first tried the NCS version 2.6.1 in VScode. The only change was to the config file to enable BIS (CONFIG_TRANSPORT_BIS=y).

Later I tried a fresh new installation of version 2.6.1 and then 2.4.0. through the nRF desktop Toolchain Manager. I ran the build and programming from bash command (no changes to any file other than the *.json file) using the script as shown here https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/nrf5340_audio/doc/building.html#nrf53-audio-app-building-script. I am able to program the unit to right channel or left channel (the LED color updates) but the unit is never discoverable via bluetooth scan.

Thank you!

Below is the build and programming log as well as the unit log after reset:

$ python buildprog.py -c both -b debug -d both --pristine -p
+------------+----------+---------+--------------+---------------------+---------------------+
|    snr     | snr conn |  device | only reboot  | core app programmed | core net programmed |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050162998 |   True   | headset | Not selected |     Selected TBD    |     Selected TBD    |
|    1000    |  False   | gateway | Not selected |     Selected TBD    |     Selected TBD    |
|    1000    |  False   | headset | Not selected |     Selected TBD    |     Selected TBD    |
+------------+----------+---------+--------------+---------------------+---------------------+
Invoking build step
Net core uses precompiled hex
Run: west build C:\ncs\v2.4.0\nrf\applications\nrf5340_audio -b nrf5340_audio_dk_nrf5340_cpuapp -p -d C:\ncs\v2.4.0\nrf\applications\nrf5340_audio\build\dev_headset\build_debug -DCONFIG_AUDIO_DEV=1
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio
-- CMake version: 3.20.5
-- Using NCS Toolchain 2.4.0 for building. (C:/ncs/toolchains/31f4403e35/cmake)
-- Found Python3: C:/ncs/toolchains/31f4403e35/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.4.0/zephyr/.cache
-- Zephyr version: 3.3.99 (C:/ncs/v2.4.0/zephyr)
-- Found west (found suitable version "1.0.0", minimum required is "0.7.1")
-- Board: nrf5340_audio_dk_nrf5340_cpuapp
-- Found host-tools: zephyr 0.16.0 (C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.0 (C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/31f4403e35/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")

-- Found BOARD.dts: C:/ncs/v2.4.0/zephyr/boards/arm/nrf5340_audio_dk_nrf5340/nrf5340_audio_dk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_headset/build_debug/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_headset/build_debug/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_headset/build_debug/zephyr/dts.cmake

warning: Experimental symbol NRF5340_AUDIO is enabled.


warning: Experimental symbol BT_LL_ACS_NRF53 is enabled.


warning: Experimental symbol BT_ISO_PERIPHERAL is enabled.


warning: Experimental symbol BT_AUDIO is enabled.


warning: Experimental symbol BT_BAP_UNICAST_SERVER is enabled.


warning: Experimental symbol BT_VCP_VOL_REND is enabled.


warning: Experimental symbol BT_CSIP_SET_MEMBER is enabled.


warning: Experimental symbol BT_MCC is enabled.


warning: Experimental symbol BT_CAP_ACCEPTOR is enabled.

Parsing C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/Kconfig
Loaded configuration 'C:/ncs/v2.4.0/zephyr/boards/arm/nrf5340_audio_dk_nrf5340/nrf5340_audio_dk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/prj.conf'
Merged configuration 'C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_headset/build_debug/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to 'C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_headset/build_debug/zephyr/.config'
Kconfig header saved to 'C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_headset/build_debug/zephyr/include/generated/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- libmetal version: 1.3.0 (C:/ncs/v2.4.0/nrf/applications/nrf5340_audio)
-- Build type:
-- Host:    Windows/AMD64
-- Target:  Generic/arm
-- Machine: arm
-- Looking for include file stdatomic.h
-- Looking for include file stdatomic.h - found
-- open-amp version: 1.3.0 (C:/ncs/v2.4.0/modules/lib/open-amp/open-amp)
-- Host:    Windows/AMD64
-- Target:  Generic/arm
-- Machine: arm
-- C_FLAGS :  -Wall -Wextra
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
CMake Warning at C:/ncs/v2.4.0/zephyr/CMakeLists.txt:838 (message):
  No SOURCES given to Zephyr library: lib__libc__common

  Excluding target from build.


CMake Warning at C:/ncs/v2.4.0/zephyr/CMakeLists.txt:1864 (message):
  __ASSERT() statements are globally ENABLED


-- Configuring done
-- Generating done
-- Build files have been written to: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_headset/build_debug
-- west build: building application
[1/434] Generating include/generated/version.h
-- Zephyr version: 3.3.99 (C:/ncs/v2.4.0/zephyr), build: v3.3.99-ncs1
[424/434] Linking C executable zephyr\zephyr_pre0.elf

[428/434] Linking C executable zephyr\zephyr_pre1.elf

[434/434] Linking C executable zephyr\zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      578904 B         1 MB     55.21%
             RAM:      108536 B       448 KB     23.66%
        IDT_LIST:          0 GB         2 KB      0.00%
Run: west build C:\ncs\v2.4.0\nrf\applications\nrf5340_audio -b nrf5340_audio_dk_nrf5340_cpuapp -p -d C:\ncs\v2.4.0\nrf\applications\nrf5340_audio\build\dev_gateway\build_debug -DCONFIG_AUDIO_DEV=2
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio
-- CMake version: 3.20.5
-- Using NCS Toolchain 2.4.0 for building. (C:/ncs/toolchains/31f4403e35/cmake)
-- Found Python3: C:/ncs/toolchains/31f4403e35/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.4.0/zephyr/.cache
-- Zephyr version: 3.3.99 (C:/ncs/v2.4.0/zephyr)
-- Found west (found suitable version "1.0.0", minimum required is "0.7.1")
-- Board: nrf5340_audio_dk_nrf5340_cpuapp
-- Found host-tools: zephyr 0.16.0 (C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.0 (C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/31f4403e35/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")

-- Found BOARD.dts: C:/ncs/v2.4.0/zephyr/boards/arm/nrf5340_audio_dk_nrf5340/nrf5340_audio_dk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/dts.cmake

warning: Experimental symbol NRF5340_AUDIO is enabled.


warning: Experimental symbol BT_LL_ACS_NRF53 is enabled.


warning: Experimental symbol BT_ISO_CENTRAL is enabled.


warning: Experimental symbol BT_AUDIO is enabled.


warning: Experimental symbol BT_BAP_UNICAST_CLIENT is enabled.


warning: Experimental symbol BT_VCP_VOL_CTLR is enabled.


warning: Experimental symbol BT_MCS is enabled.


warning: Experimental symbol BT_MPL is enabled.


warning: Experimental symbol MCTL is enabled.

Parsing C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/Kconfig
Loaded configuration 'C:/ncs/v2.4.0/zephyr/boards/arm/nrf5340_audio_dk_nrf5340/nrf5340_audio_dk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/prj.conf'
Merged configuration 'C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to 'C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/.config'
Kconfig header saved to 'C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/include/generated/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- libmetal version: 1.3.0 (C:/ncs/v2.4.0/nrf/applications/nrf5340_audio)
-- Build type:
-- Host:    Windows/AMD64
-- Target:  Generic/arm
-- Machine: arm
-- Looking for include file stdatomic.h
-- Looking for include file stdatomic.h - found
-- open-amp version: 1.3.0 (C:/ncs/v2.4.0/modules/lib/open-amp/open-amp)
-- Host:    Windows/AMD64
-- Target:  Generic/arm
-- Machine: arm
-- C_FLAGS :  -Wall -Wextra
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
CMake Warning at C:/ncs/v2.4.0/zephyr/CMakeLists.txt:838 (message):
  No SOURCES given to Zephyr library: lib__libc__common

  Excluding target from build.


CMake Warning at C:/ncs/v2.4.0/zephyr/CMakeLists.txt:1864 (message):
  __ASSERT() statements are globally ENABLED


-- Configuring done
-- Generating done
-- Build files have been written to: C:/ncs/v2.4.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug
-- west build: building application
[1/445] Generating include/generated/version.h
-- Zephyr version: 3.3.99 (C:/ncs/v2.4.0/zephyr), build: v3.3.99-ncs1
[435/445] Linking C executable zephyr\zephyr_pre0.elf

[439/445] Linking C executable zephyr\zephyr_pre1.elf

[445/445] Linking C executable zephyr\zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      608000 B         1 MB     57.98%
             RAM:      125068 B       448 KB     27.26%
        IDT_LIST:          0 GB         2 KB      0.00%
Using NET hex: C:\ncs\v2.4.0\nrf\lib\bin\bt_ll_acs_nrf53\bin\ble5-ctr-rpmsg_3349.hex for 1050162998 headset right
Programming net core on: 1050162998 headset right
Programming app core on: 1050162998 headset right
Programming UICR
Parsing parameters.
Writing.
Parsing parameters.
Writing.
Resetting 1050162998 headset right
Applying system reset.
Run.
build_prog.py finished. Report:
+------------+----------+---------+--------------+---------------------+---------------------+
|    snr     | snr conn |  device | only reboot  | core app programmed | core net programmed |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050162998 |   True   | headset | Not selected |         Done        |         Done        |
|    1000    |  False   | gateway | Not selected |     Not selected    |     Not selected    |
|    1000    |  False   | headset | Not selected |     Not selected    |     Not selected    |
+------------+----------+---------+--------------+---------------------+---------------------+

nRF5340 Audio nRF5340 Audio DK cpuapp                      
         NCS base version: 2.4.0                            
         Cmake run : Tue May 07 18:12:14 2024
HR [00:00:00.258,544] <inf> fw_info: ------- DEBUG BUILD -------
HR [00:00:00.258,544] <inf> fw_info: HEADSET right device
HR [00:00:00.269,165] <inf> board_version: Compatible board/HW version found: 1.1.0
HR [00:00:00.307,128] <wrn> bt_hci_core: Controller to host flow control not supported
HR [00:00:00.310,333] <inf> bt_hci_core: No ID address. App must call settings_load()
HR [00:00:00.310,394] <inf> ble: MAC: 00:00:00:00:00:00 (public)
HR [00:00:00.310,943] <inf> ble: Controller version: 3349
HR [00:00:00.312,316] <inf> bt_hci_core: Identity: E3:87:52:BE:DF:F4 (random)
HR [00:00:00.312,347] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0d15, manufacturer 0x07e8
HR [00:00:00.312,377] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0x0d15
HR [00:00:00.433,258] <inf> cis_headset: Advertising successfully started

RE: nRF audio DK reference application not visible to smartphone scan

dejans — Tue, 07 May 2024 14:33:20 GMT

Hi,

Which NCS version do you use?

Have you modified nrf5340_audio application in any way?

Best regards,
Dejan