nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

RE: nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

SteveKay — Wed, 28 Jun 2023 21:00:42 GMT

I have marked this as the solution:

With the help of dejans,I was able to come to the following Build and Program arguments to the pyton script to get it to a point where the 2 audio kits were programmed properly with the Audio Example.

Here are the steps I took:

I rebooted my PC and started with a fresh directory
changed the devices in the file nrf5340_audio_dk_devices.json
Build and Program using no -m internal -M on the build
1. BUILD: python buildprog.py -c both -b debug -d both
2. PROGRAM: python buildprog.py -c both -b debug -d both -p --recover_on_fail

Here is the command screen showing the results of the 2 commands.

sucessfull build



skrug@DESKTOP-KJBLMH9 MINGW64 /c/A/s6/tools/buildprog
$ python buildprog.py -c both -b debug -d both
+------------+----------+---------+--------------+---------------------+---------------------+
|    snr     | snr conn |  device | only reboot  | core app programmed | core net programmed |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050171701 |   ←[32mTrue←[0m   | headset | Not selected |     Selected TBD    |     Selected TBD    |
| 1050131916 |   ←[32mTrue←[0m   | gateway | Not selected |     Selected TBD    |     Selected TBD    |
|     10     |  ←[33mFalse←[0m   | headset | Not selected |     Selected TBD    |     Selected TBD    |
+------------+----------+---------+--------------+---------------------+---------------------+
Invoking build step
Net core uses precompiled hex
Run: west build C:\A\s6 -b nrf5340_audio_dk_nrf5340_cpuapp -d C:\A\s6\build\dev_headset\build_debug -DCONFIG_AUDIO_DEV=1
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/A/s6
-- 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:/A/s6/build/dev_headset/build_debug/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/A/s6/build/dev_headset/build_debug/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/A/s6/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:/A/s6/Kconfig
Loaded configuration 'C:/ncs/v2.4.0/zephyr/boards/arm/nrf5340_audio_dk_nrf5340/nrf5340_audio_dk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/A/s6/prj.conf'
Merged configuration 'C:/A/s6/build/dev_headset/build_debug/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to 'C:/A/s6/build/dev_headset/build_debug/zephyr/.config'
Kconfig header saved to 'C:/A/s6/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:/A/s6)
-- 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:/A/s6/build/dev_headset/build_debug
←[92m-- 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:      578928 B         1 MB     55.21%
             RAM:      108536 B       448 KB     23.66%
        IDT_LIST:          0 GB         2 KB      0.00%
Run: west build C:\A\s6 -b nrf5340_audio_dk_nrf5340_cpuapp -d C:\A\s6\build\dev_gateway\build_debug -DCONFIG_AUDIO_DEV=2
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/A/s6
-- 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:/A/s6/build/dev_gateway/build_debug/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/A/s6/build/dev_gateway/build_debug/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/A/s6/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:/A/s6/Kconfig
Loaded configuration 'C:/ncs/v2.4.0/zephyr/boards/arm/nrf5340_audio_dk_nrf5340/nrf5340_audio_dk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/A/s6/prj.conf'
Merged configuration 'C:/A/s6/build/dev_gateway/build_debug/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to 'C:/A/s6/build/dev_gateway/build_debug/zephyr/.config'
Kconfig header saved to 'C:/A/s6/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:/A/s6)
-- 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:/A/s6/build/dev_gateway/build_debug
←[92m-- 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%
build_prog.py finished. Report:
+------------+----------+---------+--------------+---------------------+---------------------+
|    snr     | snr conn |  device | only reboot  | core app programmed | core net programmed |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050171701 |   True   | headset | Not selected |     Selected TBD    |     Selected TBD    |
| 1050131916 |   True   | gateway | Not selected |     Selected TBD    |     Selected TBD    |
|     10     |  False   | headset | Not selected |     Selected TBD    |     Selected TBD    |
+------------+----------+---------+--------------+---------------------+---------------------+

skrug@DESKTOP-KJBLMH9 MINGW64 /c/A/s6/tools/buildprog
$ python buildprog.py -c both -b debug -d both -p --recover_on_fail
+------------+----------+---------+--------------+---------------------+---------------------+
|    snr     | snr conn |  device | only reboot  | core app programmed | core net programmed |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050171701 |   ←[32mTrue←[0m   | headset | Not selected |     Selected TBD    |     Selected TBD    |
| 1050131916 |   ←[32mTrue←[0m   | gateway | Not selected |     Selected TBD    |     Selected TBD    |
|     10     |  ←[33mFalse←[0m   | headset | Not selected |     Selected TBD    |     Selected TBD    |
+------------+----------+---------+--------------+---------------------+---------------------+
Invoking build step
Net core uses precompiled hex
Run: west build C:\A\s6 -b nrf5340_audio_dk_nrf5340_cpuapp -d C:\A\s6\build\dev_headset\build_debug
ninja: no work to do.
Run: west build C:\A\s6 -b nrf5340_audio_dk_nrf5340_cpuapp -d C:\A\s6\build\dev_gateway\build_debug
ninja: no work to do.
Using NET hex: C:\lib\bin\bt_ll_acs_nrf53\bin\ble5-ctr-rpmsg_3349.hex for 1050171701 headset left
Using NET hex: C:\lib\bin\bt_ll_acs_nrf53\bin\ble5-ctr-rpmsg_3349.hex for 1050131916 gateway
Programming net core on: 1050171701 headset left
Programming net core on: 1050131916 gateway
ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
Recovering device: 1050131916 gateway
ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
Recovering device: 1050171701 headset left
[error] [ Client] - Encountered error -90: Command enable_coprocessor executed for 14 milliseconds with result -90
[error] [ Worker] - Application core access protection is enabled, can't enable coprocessor.
Recovering device. This operation might take 30s.
[error] [ Worker] - Application core access protection is enabled, can't enable coprocessor.
[error] [ Client] - Encountered error -90: Command enable_coprocessor executed for 14 milliseconds with result -90
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.
Writing image to disable ap protect.
Recovering device. This operation might take 30s.
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.
Writing image to disable ap protect.
Programming net core on: 1050171701 headset left
Programming net core on: 1050131916 gateway
Programming app core on: 1050171701 headset left
Programming app core on: 1050131916 gateway
Programming UICR
Parsing parameters.
Parsing parameters.
Writing.
Writing.
Resetting 1050131916 gateway
Applying system reset.
Parsing parameters.
Run.
Writing.
Resetting 1050171701 headset left
Applying system reset.
Run.
build_prog.py finished. Report:
+------------+----------+---------+--------------+---------------------+---------------------+
|    snr     | snr conn |  device | only reboot  | core app programmed | core net programmed |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050171701 |   True   | headset | Not selected |         Done        |         Done        |
| 1050131916 |   True   | gateway | Not selected |         Done        |         Done        |
|     10     |  False   | headset | Not selected |     Not selected    |     Not selected    |
+------------+----------+---------+--------------+---------------------+---------------------+

skrug@DESKTOP-KJBLMH9 MINGW64 /c/A/s6/tools/buildprog

I am evaluating two nRF5340 audio DK's. I am using one as a Gateway and the other as a Left Headset. I was only supplied with 2 kits to evaluate. The Example Audio Application can support a Right Headset If you have an extra 3rd Kit.

Now on to testing the audio example.

[quote userid="118202" url="~/f/nordic-q-a/101195/nrf5340-audio-dk-with-the-audio-application-nrf5340_audio---testing-problem/433054"]If anyone is interested you can follow my review blog on Element14 here Roadtest: Nordic Bluetooth LE Audio Development Kit nRF5340 DK. In this review myself and two other members have reviewed the Kit. I'm using this doc to try to get the 2 boards working with the Audio example. [/quote]

youtube.com/.../QpHmotHVtUs

Thank You ..

Steve K

RE: nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

SteveKay — Wed, 28 Jun 2023 18:47:07 GMT

[quote userid="111786" url="~/f/nordic-q-a/101195/nrf5340-audio-dk-with-the-audio-application-nrf5340_audio---testing-problem/433414"]I have reproduced your reported problem with flash overflow. The issue happens due to debug version being too large. The solution for this is to use the release version.[/quote]

Thanks for taking the time to reproduce the problem. Just as I had thought debug was too large.

At one point in trying to Build and Program, I did try the -release arg for both commands, but I had errors so I abandoned it. I never was able to get it working.

[quote userid="111786" url="~/f/nordic-q-a/101195/nrf5340-audio-dk-with-the-audio-application-nrf5340_audio---testing-problem/433414"]I agree with you that subjectively colors are not quite green, but more on the yellow side. However, the actual color defined by the manufacturer is green.
Regarding RGB2 not blinking, we are aware of this issue, and it does not affect anything[/quote]

The trouble is that YELLOW in the USA indicates CAUTION. GREEN means GO and RED means STOP. '''LOL...

So the blinking YELLOW light to me, means that something is wrong. GREEN would make more sense as an indicator. But no need to split hairs here, It's working now and I can move on to testing the application according to the audio app doc page.

ONE more question?? for you...

Although now, that I have a successful build & program

I still get an error in the recover section of the PROGRAM run. I included the segment from the command screen below.

As you can see it is trying to recover and tells me that I need to use the recover arg, which I did use.? So that's a bit confusing? And then it tells me that there is an error recovering the left headset? Just interested if you know what this is? ERROR means that something has gone wrong.. I think it should be [INFO]

Programming net core on: 1050131916 gateway
ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
Recovering device: 1050131916 gateway
ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
Recovering device: 1050171701 headset left
[error] [ Client] - Encountered error -90: Command enable_coprocessor executed for 14 milliseconds with result -90
[error] [ Worker] - Application core access protection is enabled, can't enable coprocessor.
Recovering device. This operation might take 30s.
[error] [ Worker] - Application core access protection is enabled, can't enable coprocessor.
[error] [ Client] - Encountered error -90: Command enable_coprocessor executed for 14 milliseconds with result -90
Recovering device. This operation might take 30s.

thanks for all your help

Steve K

RE: nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

dejans — Wed, 28 Jun 2023 09:56:41 GMT

Hi,

I have reproduced your reported problem with flash overflow. The issue happens due to debug version being too large. The solution for this is to use the release version.

python buildprog.py -c both -b release -d both -m internal

I agree with you that subjectively colors are not quite green, but more on the yellow side. However, the actual color defined by the manufacturer is green.
Regarding RGB2 not blinking, we are aware of this issue, and it does not affect anything.

Best regards,
Dejan

RE: nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

SteveKay — Wed, 28 Jun 2023 05:17:50 GMT

I ended up getting things to working but the LEDs illumination does not coincide with the doc page?

The LEDS are working an the boards and change colors to indicate the Gateway GREEN and Headset BLUE as shown.

the doc page states:

After programming, RGB2 starts blinking green on every device to indicate the ongoing CPU activity on the network core. LED3 starts blinking green on every device to indicate the ongoing CPU activity on the application core.
Wait for the LED1 on the gateway to start blinking blue. This happens shortly after programming the development kit and indicates that the gateway device is connected to at least one headset and ready to send data.

There are different for me

the RGB2 never blinks and is not Illuminated on both devices.?
LED3 is blinking YELLOW not green?
the LED1 is blinking BLUE on the gateway OK
But LED1 is ALSO blinking BLUE? IS THIS OK?

QUESTIONS

WHY is the RGB2 not illuminated?

why is the LED3 blinking YELLOW not green? what is this indicating?

----------------------------------------------------------------------------------------------------------------------------------

the following steps are what I did to get to this point:

The bottom line is that since I only have 2 kits, the -m internal and the -M args should not be used.

To get it working I did the following:

I rebooted my PC and started with a fresh directory

changed the devices in the file nrf5340_audio_dk_devices.json

Build and Program using no -m internal -M on the build

BUILD: python buildprog.py -c both -b debug -d both
PROGRAM: python buildprog.py -c both -b debug -d both -p --recover_on_fail

here is the full output

devzone.nordicsemi.com/.../s6_5F00_Build_5F00_Program.txt

RE: nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

SteveKay — Tue, 27 Jun 2023 19:46:52 GMT

hi again,

I tried it again with a fresh directory and this time the build failed with the overflow error I mentioned.

This is the output results from the long build. It shows where the overflow happens. it looks like the problems with the flash using -internal -M

skrug@DESKTOP-KJBLMH9 MINGW64 /c/A/s5/tools/buildprog
$ python buildprog.py -c both -b debug -d both -m internal -M

Memory region Used Size Region Size %age Used
FLASH: 19284 B 246 KB 7.66%
RAM: 4080 B 64 KB 6.23%
SRAM1: 0 GB 64 KB 0.00%
IDT_LIST: 0 GB 2 KB 0.00%
[175/178] Creating signature of application
[176/178] Creating validation for zephyr.hex, storing to
[178/178] Generating zephyr/merged_CPUNET.hex
[483/510] Linking C executable zephyr\zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map
cmd.exe /C "cd . && C:\ncs\toolchains\31f4403e35\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -gdwarf-4 @CMakeFiles\zephyr_pre0.rsp -o zephyr\zephyr_pre0.elf && cmd.exe /C "cd /D C:\A\s5\build\dev_gateway\build_debug\zephyr && C:\ncs\toolchains\31f4403e35\opt\bin\cmake.exe -E echo ""
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: zephyr\zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
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: region `FLASH' overflowed by 18384 bytes
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\31f4403e35\opt\bin\cmake.EXE' --build 'C:\A\s5\build\dev_gateway\build_debug'
Traceback (most recent call last):
File "buildprog.py", line 404, in <module>
__main()
File "buildprog.py", line 387, in __main
__build_module(build_cfg, options)
File "buildprog.py", line 150, in __build_module
raise Exception("cmake error: " + str(ret_val))
Exception: cmake error: 1

RE: nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

SteveKay — Tue, 27 Jun 2023 18:37:27 GMT

Hi,

I used the -M in the command "python buildprog.py -c both -b debug -d both -m internal -M"

I tried the build and program again and received no Error but the same results "NO LEDs are illuminated. I'll post the out at the end of this comment after I reply to your question.

[quote userid="111786" url="~/f/nordic-q-a/101195/nrf5340-audio-dk-with-the-audio-application-nrf5340_audio---testing-problem/433315"]Could you please show an error which you get when using "python buildprog.py -c both -b debug -d both -m internal" command for building the application?
[/quote]

I don't have a complete output but here are the notes I took. I hope you can see the error message on the screenshot.

-----------------------------------------------------------------

Now you're ready to run the script.

Copy the sample example from the SDK version directory to C:\A\s1. I used v2.4.0, so here is the directory where the code is: C:\ncs\v2.4.0\nrf\applications\nrf5340_audio
After this is copied, EDIT the Jason config file nrf5340_audio_dk_devices.json as described
To build the script go to the directory cd C:/A/s1/tools/buildprog
1. python buildprog.py -c both -b debug -d both -m internal –M
1. TURN on BOTH BOARDS
2. Enter in the following command:
it starts to build with the following output.

But I ran into a fatal error with building zephyr FLASH OVERFLOW

-------------------------------------------------------------------------------------------

I tried the build and program again and received no Error but the same results "NO LEDs are illuminated. here is the results

devzone.nordicsemi.com/.../NOErrors_2D00_Build_5F00_Program.txt

RE: nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

dejans — Tue, 27 Jun 2023 16:17:51 GMT

Hi,

Could you please show an error which you get when using "python buildprog.py -c both -b debug -d both -m internal" command for building the application?

Best regards,
Dejan

RE: nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

SteveKay — Mon, 26 Jun 2023 19:10:16 GMT

Hello dejans

Thank you so much for responding so quickly. I will answer you questions about my problem.

[quote userid="111786" url="~/f/nordic-q-a/101195/nrf5340-audio-dk-with-the-audio-application-nrf5340_audio---testing-problem/432966"]Could you please specify how RGB2 and LED3 blink in your case compared to what is described in the documentation?[/quote]

the 2 devices are plugged into the same USB connections on my PC running Windows 10. When I turn on the devices the LED's on both the gateway and the headset do not illuminate at all. There is no way for me to continue the test since it appears that "blinking green on every device to indicate the ongoing CPU activity"

[quote userid="111786" url="~/f/nordic-q-a/101195/nrf5340-audio-dk-with-the-audio-application-nrf5340_audio---testing-problem/432966"]Even if you see different colors than expected, there might still be no problem with how the sample is built or programmed. Looking at your provided outputs, I would assume that you programmed the devices correctly and they should work as expected. In addition, there does not seem to be the case that there is something wrong with the SDK. You can always try previous version in case you want to verify programming procedure, compare the outputs or check the colors of RGB2 and LED3.[/quote]

The only reason to question the SDK is that I copied the audio example from the applications directory under the 2.4.0 release "C:\ncs\v2.4.0\nrf\applications\nrf5340_audio" to a new shorter named directory. I then ran the python script from there.I'd rather focus on this version of the SDK, to find out why the LEDS specified are not illuminated.

I would normally debug the application, but I use VSCode to debug C code and VSCode is not supported. So I seek advice from DevZone.

[quote userid="111786" url="~/f/nordic-q-a/101195/nrf5340-audio-dk-with-the-audio-application-nrf5340_audio---testing-problem/432966"]

Still get the use recover arg error in the output, even though I ran the command with “--recover_on_fail” ?
Received some other errors refer to “s4_program_sucess_with_recover.txt”

Could you show the errors in the output that you refer to?

[/quote]

Here it is:

devzone.nordicsemi.com/.../4774.s4_5F00_program_5F00_sucess_5F00_with_5F00_recover.txt

[quote userid="118202" url="~/f/nordic-q-a/101195/nrf5340-audio-dk-with-the-audio-application-nrf5340_audio---testing-problem"]NOTE: The App doc page is incorrect the program command has an incorrect argument “--recover-on-fail”! It should be defined with underscores not dashes.
THIS NEEDS TO BE FIXED ON THE DOC PAGE TO STOP CONFUSION WHEN USING THE AUDIO EXAMPLE TO BUILD & PROGRAM the KIT[/quote][quote userid="111786" url="~/f/nordic-q-a/101195/nrf5340-audio-dk-with-the-audio-application-nrf5340_audio---testing-problem/432966"]Yes, you are right. As you mentioned, a correct parameter would be --recover_on_fail. I have reported this internally and hope for a quick fix.[/quote]

Thanks for reporting this. Is there a way for uses to be aware of Nordic documentation updates? Other vendors, like Renesas support send email notifications to document updates that the user is interested in.. I realize and the doc page notes specifies right up front, that this is experimental and that "There is an ongoing process of restructuring the nRF5340 Audio application project.",.

It would be nice to know for makers like myself who are experimenting with the example and trying to get the application running before making experimental changes.

If anyone is interested you can follow my review blog on Element14 here Roadtest: Nordic Bluetooth LE Audio Development Kit nRF5340 DK. In this review myself and two other members have reviewed the Kit. I'm using this doc to try to get the 2 boards working with the Audio example.

Other Observations

SOME KNOWN issues with different SDK versions and the Audio Application.

i noticed in the TESTING section of the doc, there is a NOTE to check known issues related to serial connections. at nRF5340 Audio application known issues

As noted there are Detection issues with USB-C to USB-C connections, but my PC does not have USB-C connectors. So, I was wondering if it also affect my USB PC USB connection also? Also the versions affected include SDK version 2.4.0. How can I dig deeper into the release notes if possible? All issues listed in the known issues page under the nRF5340 Audio Section report a issue with 2.4.0?

Also, here are the 6 com ports assigned when the devices are connected to the PC

Shown here in my windows device manager.

Let me know your thoughts on this

Regards

Steve K

RE: nRF5340 Audio DK with the audio application nrf5340_audio - Testing Problem

dejans — Mon, 26 Jun 2023 12:24:36 GMT

Hi,

Thank you very much for sharing your observations with us.

[quote user=""]

Now I'm trying to test the boards using the example in the Testing Section HERE.
The RGB2 and LED3 are not blinking as described.
Can anyone help me to determine why?
Is the version of the SDK supported using the python script?
Did I build or program correctly?
I'm stuck. HAs anyone verified this SDK version with the Audio example ?
Do I need to use an earlier version of the SDK?

[/quote]

Could you please specify how RGB2 and LED3 blink in your case compared to what is described in the documentation?

Even if you see different colors than expected, there might still be no problem with how the sample is built or programmed. Looking at your provided outputs, I would assume that you programmed the devices correctly and they should work as expected. In addition, there does not seem to be the case that there is something wrong with the SDK. You can always try previous version in case you want to verify programming procedure, compare the outputs or check the colors of RGB2 and LED3.

[quote user=""]Still get the use recover arg error in the output, even though I ran the command with “--recover_on_fail” ?
Received some other errors refer to “s4_program_sucess_with_recover.txt”[/quote]

Could you show the errors in the output that you refer to?

[quote user=""]NOTE: The App doc page is incorrect the program command has an incorrect argument “--recover-on-fail”! It should be defined with underscores not dashes.
THIS NEEDS TO BE FIXED ON THE DOC PAGE TO STOP CONFUSION WHEN USING THE AUDIO EXAMPLE TO BUILD & PROGRAM the KIT[/quote]

Yes, you are right. As you mentioned, a correct parameter would be --recover_on_fail. I have reported this internally and hope for a quick fix.

Best regards,
Dejan