About DeviceTree and Overlay files

[Junichi]

I want to edit the sample source (nRF5340 Audio) and program it on my own board.

I'm using CIS.

I'm using NCS version 2.5.0.

The nRF5340 Audio DK board is exactly the same hardware,

so one overlay file works fine.

The circuit of the transmitter and receiver of my own board is different.

Therefore, I think two overlay files are necessary.

VSCODE is not recommended for nRF5340 Audio.

Therefore, I run the program made in Python from the command prompt.

Specifically, I run buildprog.py in the Tools/buildprog folder with the following command.

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

How can I achieve this?

For example, is it possible to create two types of overlay files in one source and use different overlay files when running the script?

I would like to know the specific method.

When I enter the corresponding
J-Link serial number only into the Headset in the nrf5340_audio_dk_devices.json file and execute the build and write, then I enter the corresponding J-Link serial number only into the Gateway and execute the build and write, and I am unable to connect to BLE.

Do you know what the cause is?

[Junichi]

Thank you for your answer.

I'm using the default version of the source.

Since the application differs depending on the NCS version, after installing 2.6.1, I'm using the source generated by Create a new application -> Copy a sample.

I'm using buildprog.py generated by the version created above,
so I don't think there's a version mistake.

[Hieu]

Hi Junichi,

My apology for the late follow-up and thank you for the patience.

Maria is out of office, and since a few days ago, I have taken over this case. However, I haven't figured out what could be wrong besides what Maria has already thought of.

I will continue to investigate this issue and update you within this week.

Hieu

[Hieu]

P.s: I just realized a potential source of the problem. How are you calling buildprog.py? In particular, do you know what python.exe is being used to run buildprog.py? It's best to try with the Python copy in the toolchain. If you are using the nRF Connect VS Code extension, you could do so by opening a nRF Connect terminal.

[Hieu]

P.p.s: I notice that you are on NCS 2.6.1. The error message you got from buildprog.py is still the wrong one but is there any reason you want to use buildprog.py? buildprog.py is to be used with the LE Audio Controller, which is now deprecated. 

With NCS 2.6.1, you could build with west like a non-Audio application and use the SoftDevice Controller.

See: Migration guide for nRF Connect SDK v2.6.0 (nordicsemi.com)