testing nf5340_audio_dk

[assegid]

I am trying to use the nrf5340 audio DK for the first time using one of the sample blink codes. I keep getting an error when first creating an application by copying the sample provided. The system seems to be missing a board information and I could not figure out where and how to provide that information. My system configuration and versions of my tools are given below. I am beginning to wonder if my installation is ok as some of the folders are different from the nrfConnect instruction videos from Nordic which  were for a Windows PC.

My Toolchain is 2.6.1 at /opt/Nordic/ncs/toolchains

My SDK is 2.6.1 at /opt/Nordic/ncs/v2.6.1

My applications are in user/name/ncs/

MacBook Pro 2.9ghz quad core i7

16GB RAM Mac OS13.6.7

VS Code

Version: 1.90.1

Commit: 611f9bfce64f25108829dd295f54a6894e87339d

Date: 2024-06-11T21:02:41.372Z

Electron: 29.4.0

ElectronBuildId: 9593362

Chromium: 122.0.6261.156

Node.js: 20.9.0

V8: 12.2.281.27-electron.0

OS: Darwin x64 22.6.0

The error I am getting is below. Apologies for the long text captured and pasted. Can someone help?

CMake Error at /opt/nordic/ncs/v2.6.1/zephyr/cmake/modules/extensions.cmake:2891 (message):BOARD is not being defined on the CMake command-line, in the environment or

by the app.

[{

"resource": "/opt/nordic/ncs/v2.6.1/zephyr/cmake/modules/extensions.cmake",

"owner": "cmake-configure-diags",

"severity": 8,

"message": "CMake Error at /opt/nordic/ncs/v2.6.1/zephyr/cmake/modules/extensions.cmake:2891 (message):BOARD is not being defined on the CMake command-line, in the environment or\nby the app.",

"source": "CMake (message)",

"startLineNumber": 2891,

"startColumn": 1,

"endLineNumber": 2891,

"endColumn": 10000,

"relatedInformation": [

{

"startLineNumber": 56,

"startColumn": 1,

"endLineNumber": 56,

"endColumn": 1000,

"message": "In call to 'zephyr_check_cache' here",

"resource": "/opt/nordic/ncs/v2.6.1/zephyr/cmake/modules/boards.cmake"

},

{

"startLineNumber": 129,

"startColumn": 1,

"endLineNumber": 129,

"endColumn": 1000,

"message": "In call to 'include' here",

"resource": "/opt/nordic/ncs/v2.6.1/zephyr/cmake/modules/zephyr_default.cmake"

},

{

"startLineNumber": 66,

"startColumn": 1,

"endLineNumber": 66,

"endColumn": 1000,

"message": "In call to 'include' here",

"resource": "/opt/nordic/ncs/v2.6.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake"

},

{

"startLineNumber": 159,

"startColumn": 1,

"endLineNumber": 159,

"endColumn": 1000,

"message": "In call to 'include_boilerplate' here",

"resource": "/opt/nordic/ncs/v2.6.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake"

},

{

"startLineNumber": 4,

"startColumn": 1,

"endLineNumber": 4,

"endColumn": 1000,

"message": "In call to 'find_package' here",

"resource": "/Users/assegid/ncs/blinky/CMakeLists.txt"

}

]

}]

[AHaug]

Hi,

Glad to see that you've been having some progress. Here's some update/follow up regarding your various comments from the weekend

assegid said:

I followed the installation instructions on your website and another available on youtube. I was unsuccessful on both Mac and Windows machines

I would typically recommend that you go through the guide in this course for installation: https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-1-nrf-connect-sdk-introduction/ (exercise 1), which links to the official documentation here https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/installation.html 

Unfortunately the youtube videos might be slightly updated w.r.t to installing and setting up the SDK.

assegid said:

When I create an application by copying the Blinky example provided, I get the errors shown below in the pictures.

This might not be relevant since you in your latest comment suggests that you've resolved this, but anyways: Is this output generated when you use the Build in the VS Code extension? I.e how did you build the sample?

assegid said:

I am still getting errors when copying sample codes to create an application.

The same errors as previously seen or new ones?

Kind regards,
Andreas

[assegid]

Hi Andreas,

I wanted to try building and programming using the instructions provided here. However, when I run python buildprog.py -h, I get the response below.

assegid@HIDA-4167107 buildprog % python buildprog.py -h

Traceback (most recent call last):

  File "/opt/nordic/ncs/v2.6.1/nrf/applications/nrf5340_audio/tools/buildprog/buildprog.py", line 20, in <module>

    from colorama import Fore, Style

ModuleNotFoundError: No module named 'colorama'

I have already tried to install colorama using the pip instructions.

Any idea what is going on now?

[AHaug]

Hi,

From what I see it looks like you're using an Engineering version of the DK. Is this correct? Referring to the image you pasted showing your connected devices: 

This PDK is an experimental DK so there might be anomalies with this board that causes this issue. I would recommend that you get hold of a newer DK and test with this. Please reach out to your local RSM for more information regarding this.

The error: 

CMake Error at /opt/nordic/ncs/v2.6.1/zephyr/cmake/modules/extensions.cmake:2891 (message):BOARD is not being defined on the CMake command-line, in the environment or by the app.

indicates that the board could be the issue.

We've tried to reproduce it on several MacOS machines, but with non-clean installations and clean installations and we don't see the same issue that you're seeing, so you will have to exclude that this is caused by the board before we move on as well as trying with a 100% clean machine from scratch following the installation guides for your OS on your machine.

Kind regards,
Andreas

[assegid]

After getting over the 'colorama module missing' issue, I have been able to program the boards without issues. I have created another thread regarding 'colorama' to help other users save time if they run into the same issue. I have tested the provided sample code for CIS and BIS modes; Broadcast Source, Broadcast Sink, Unicast Client, Unicast Server, enabling and disabling the configuration bits, and the results are below. 

Summary

In all cases audio input using USB works only briefly or not at all.

In BIS mode volume is lower.

Volume control and test tones work only in CIS mode CONFIG_STREAM_BIDIRECTIONAL=y makes no difference.

In BIS and Bidirectional mode: no mic activity

In CIS and Bidirectional mode: no mic activity

In CIS and walkie talkie: low quality sound from mic from gateway to headset, no line in or test tone working

In CIS walkie talkie and bidirectional: very low mic sound quality, no line in or test tone

In BIS and walkie talkie: cmake error 256

In BIS Bidirectional and walkie talkie: cmake error 256

Please confirm my boards are older engineering versions, I have attached a picture showing version, production date and serial numbers.

[AHaug]

Hi,

assegid said:

After getting over the 'colorama module missing' issue, I have been able to program the boards without issues. I have created another thread regarding 'colorama' to help other users save time if they run into the same issue. I have tested the provided sample code for CIS and BIS modes; Broadcast Source, Broadcast Sink, Unicast Client, Unicast Server, enabling and disabling the configuration bits, and the results are below. 

Glad to hear that you isolated the issue down to this!

Out of curiosity, did you use a terminal that were not opened from either the toolchain manager or the VS Code extension such as the nRF Connect terminal or did you run the buildprog script from a "generic" terminal, i.e something similar to the equivalent of opening command prompt on Windows from the start menu?

I've had a similar experience with a different Python script recently, where a missing module caused errors when I ran the script from the default Windows cmd prompt. This was not caused when running the same script from a command prompt/nRF connect terminal set up through either of the mentioned terminals due to the environment being properly setup, so I'm curious if it's the same case for the buildprog script for nRF Audio on your device as well

If it is, we'll update the documentation to specify that you must either install the missing modules yourself (and that we add a requirements.txt that you can run to install all the missing modules) or to make sure that you use a terminal that has been set up to be a "proper" environment"

Kind regards,
Andreas