nRF5340 Audio DK - gateway central LED colour?

[bluetooth_mdw]

Hi, I just started working with three Audio DK boards. All I'm doing at this stage is trying to familiarise myself with the SDK by building and programming the nrf5340_audio application, as headset for two of the boards and gateway for the third. Building and programming seems to be working OK but I was expecting the central LED to be a different colour on each of the three boards, reflecting their roles as headset (L), gateway and headset (r).

Instead, my gateway device has a blue LED, the same as the device flashed with code for headset (left).

In the image above, the device in the foreground is the right headset. In the background on the left we have the left headset and in the background on the right, the gateway.

Here's how I build and program the gateway:

C:\ncs\v2.2.0\nrf\applications\nrf5340_audio\tools\buildprog>python buildprog.py -c app -b debug -d gateway
+------------+----------+---------+--------------+---------------------+---------------------+
|    snr     | snr conn |  device | only reboot  | core app programmed | core net programmed |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050146584 |  ←[33mFalse←[0m   | headset | Not selected |     Not selected    |     Not selected    |
| 1050193182 |   ←[32mTrue←[0m   | gateway | Not selected |     Selected TBD    |     Not selected    |
| 1050112489 |  ←[33mFalse←[0m   | headset | Not selected |     Not selected    |     Not selected    |
+------------+----------+---------+--------------+---------------------+---------------------+
Invoking build step
Run: west build C:\ncs\v2.2.0\nrf\applications\nrf5340_audio -b nrf5340_audio_dk_nrf5340_cpuapp -d C:\ncs\v2.2.0\nrf\applications\nrf5340_audio\build\dev_gateway\build_debug
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.2.0/nrf/applications/nrf5340_audio
-- Using NCS Toolchain 2.2.0 for building. (C:/ncs/toolchains/v2.2.0/cmake)
-- Found Python3: C:/ncs/toolchains/v2.2.0/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Cache files will be written to: C:\Users\mwoolley\AppData\Local/.cache/zephyr
-- Zephyr version: 3.2.99 (C:/ncs/v2.2.0/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf5340_audio_dk_nrf5340_cpuapp
-- Found host-tools: zephyr 0.15.1 (C:/ncs/toolchains/v2.2.0/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.15.1 (C:/ncs/toolchains/v2.2.0/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/v2.2.0/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: C:/ncs/v2.2.0/nrf/boards/arm/nrf5340_audio_dk_nrf5340/nrf5340_audio_dk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: C:/ncs/v2.2.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/ncs/v2.2.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/ncs/v2.2.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/dts.cmake

warning: Experimental symbol NRF5340_AUDIO is enabled.


warning: Experimental symbol BT_ISO_PERIPHERAL is enabled.


warning: Experimental symbol BT_AUDIO is enabled.


warning: Experimental symbol BT_AUDIO_UNICAST_SERVER is enabled.


warning: Experimental symbol BT_VCS is enabled.


warning: Experimental symbol BT_CSIS is enabled.


warning: Experimental symbol BT_MCC is enabled.


warning: Experimental symbol BT_CAP_ACCEPTOR is enabled.

Parsing C:/ncs/v2.2.0/nrf/applications/nrf5340_audio/Kconfig
Loaded configuration 'C:/ncs/v2.2.0/nrf/boards/arm/nrf5340_audio_dk_nrf5340/nrf5340_audio_dk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/ncs/v2.2.0/nrf/applications/nrf5340_audio/prj.conf'
Configuration saved to 'C:/ncs/v2.2.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/.config'
Kconfig header saved to 'C:/ncs/v2.2.0/nrf/applications/nrf5340_audio/build/dev_gateway/build_debug/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 12.1.0
-- The CXX compiler identification is GNU 12.1.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- libmetal version: 1.2.0 (C:/ncs/v2.2.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.2.0 (C:/ncs/v2.2.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.2.0/zephyr/CMakeLists.txt:1833 (message):
  __ASSERT() statements are globally ENABLED


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

[415/421] Linking C executable zephyr\zephyr_pre1.elf

[421/421] Linking C executable zephyr\zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      559696 B         1 MB     53.38%
             RAM:      101044 B       448 KB     22.03%
        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 |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050146584 |  False   | headset | Not selected |     Not selected    |     Not selected    |
| 1050193182 |   True   | gateway | Not selected |     Selected TBD    |     Not selected    |
| 1050112489 |  False   | headset | Not selected |     Not selected    |     Not selected    |
+------------+----------+---------+--------------+---------------------+---------------------+

C:\ncs\v2.2.0\nrf\applications\nrf5340_audio\tools\buildprog>python buildprog.py -c app -b debug -d gateway -p
+------------+----------+---------+--------------+---------------------+---------------------+
|    snr     | snr conn |  device | only reboot  | core app programmed | core net programmed |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050146584 |  ←[33mFalse←[0m   | headset | Not selected |     Not selected    |     Not selected    |
| 1050193182 |   ←[32mTrue←[0m   | gateway | Not selected |     Selected TBD    |     Not selected    |
| 1050112489 |  ←[33mFalse←[0m   | headset | Not selected |     Not selected    |     Not selected    |
+------------+----------+---------+--------------+---------------------+---------------------+
Invoking build step
Run: west build C:\ncs\v2.2.0\nrf\applications\nrf5340_audio -b nrf5340_audio_dk_nrf5340_cpuapp -d C:\ncs\v2.2.0\nrf\applications\nrf5340_audio\build\dev_gateway\build_debug
ninja: no work to do.
Programming app core on: 1050193182 gateway
Parsing parameters.
Writing.
Resetting 1050193182 gateway
Applying system reset.
Run.
build_prog.py finished. Report:
+------------+----------+---------+--------------+---------------------+---------------------+
|    snr     | snr conn |  device | only reboot  | core app programmed | core net programmed |
+------------+----------+---------+--------------+---------------------+---------------------+
| 1050146584 |  False   | headset | Not selected |     Not selected    |     Not selected    |
| 1050193182 |   True   | gateway | Not selected |         Done        |     Not selected    |
| 1050112489 |  False   | headset | Not selected |     Not selected    |     Not selected    |
+------------+----------+---------+--------------+---------------------+---------------------+

And here's my JSON config file:

[{
        "nrf5340_audio_dk_snr": 1050146584,
        "nrf5340_audio_dk_dev": "headset",
        "channel": "left"
    },
    {
        "nrf5340_audio_dk_snr": 1050193182,
        "nrf5340_audio_dk_dev": "gateway",
        "channel": "NA"
    },
    {
        "nrf5340_audio_dk_snr": 1050112489,
        "nrf5340_audio_dk_dev": "headset",
        "channel": "right"
    }
]

Can you please explain why my gateway device does not light its central LED green? Does this indicate it really is not running the gateway code?

Thanks

[Elfving]

Hello,

I will have to get back to you on this next week.

Regards,

Elfving

[bluetooth_mdw]

Any news on this? Whilst my initial question highlighted the discrepancy between expected and actual LED colours, the bottom line is my gateway node is not working after a clean build. Could you help me get up and running, please?

[Elfving]

Hello Martin!

Sorry about the delay, I've been sick for a few days.

When it comes to your problem, I agree that it doesn't seem to behave the way it should. So after you have recovered, and flashed both cores with a pristine build, LED3 flashes yellow?

python buildprog.py -c both -b debug -d gateway -p --pristine 

Are you seeing this issue on the other DKs as well?

Have you shorted anything on the board?

And btw, are you sure you are flashing the correct board? The magenta one in the image of yours seems to have the ID ending with 9.

Regards,

Elfving

[bluetooth_mdw]

Hi Elfving, hope you're feeling better now! I confess, I hadn't noticed the --pristine arg and have been running buildprog per the examples that appear in the Building and Running section of the documentation. But guess what? It looks like that's all I needed as I now have three boards, all displaying the expected colours in their central LED *and* flashing a blue LED. Duh! That should have been an easy one, sorry about that :-)

First test successfully completed and results in the form of a short video, here!

https://youtu.be/dIDk5Ck1cQc 

Thanks for nudging my brain into gear!

[Elfving]

Btw, it seems that LED3 is only green, though it might look more yellow than RGB2's green.

So what you are seeing there is LED3 blinking green, which indicates ongoing CPU activity.

Regards,

Elfving

[Elfving]

Ah great! I'm glad you've gotten it working.

bluetooth_mdw said:

That should have been an easy one, sorry about that :-)

No that is no problem at all! Using the 'pristine' argument isn't mentioned explicitly in the documentation, so it sounds like a very easy mistake to make.

Thanks for sharing the video!

Regards,

Elfving

[bluetooth_mdw]

Great arg name btw. When a clean build just isn't enough, go --pristine! :-)