Problems building Direction_finding_central sample

[johan_1234]

Hi, I recently installed the last version of the SDK v2.5.2 and when I try to build the sample direction_finding_central  I am getting the following error

I am running this command to build

west build -b nrf52833dk_nrf52833 -- -DCONF_FILE=prj.conf

the other sample, direction_finding_peripheral builds without problems, and other samples also.

Is there a special configuration for building this sample?

I will need the AoA mode only, however as I understand there is no need to use the overlay for this.

On VsCode I get this warning



I think this may be related since the callback cte_report_cb in the conn.h has a condition that only enables if the CONFIG_BT_DF_CONNECTION_CTE_RX=y

Any help would be greatly appreciated.

[Elfving]

Oh, and I see here that the OP built this using the command line and not using the default building action in the VSC Extension, and also made a mistake in the build command that prevents this auto-discovery of the board specific KConfig files. Did you build it in this way as well?

It is supposed to be: "west build -b nrf52833dk_nrf52833 -- -DCONF_FILE=prj.conf", when you specify "-DCONF_FILE=<file>" you must provide all the KConfig files. The other simple option is to simply build using "west build -b nrf52833dk_nrf52833".

Regards,

Elfving

[Zihao]

Hi,

Yes, there is certainly a boards folder in my project. And I find the CONFIG_BT_LL_SW_SPLIT=y in nrf52833dk_nrf52833.conf. 

When I was studying the Nordic BLE course, my understanding was that board.conf takes precedence over prj.conf. Therefore, I don't understand why this setting doesn't seem to be taking effect.

You are great! I think this is important, but why would such a problem occur? 

Anything helpful will be appreciated.

Yours,

Zihao

[Zihao]

Hi,

No, I built it using the default building action in VSCode. Because it seems that Nordic strongly encourages everyone to use the VSC Extension. Also, I'm really new to this, so I think the learning curve of using the command line might be higher, so I didn't use the command line...

Yours,

Zihao

[Zihao]

Hi,

Today I ran this sample successfully! Here's the thing: the nrf52833dk_nrf52833.conf in the board seems to be correct, but I don't know why it didn't work as expected. So, I copied all the code from nrf52833dk_nrf52833.conf into prj.conf. Subsequently, both the build and flash processes went smoothly, and CTE seemed fine too. Finally, I can start my project development.

At the same time, I'd like to ask, will this solution have any other adverse effects?

Thank you so much for your help, Elfving! you really helped me a lot! You are awesome!!

Yours,

Zihao

[Elfving]

None at all, so this is something you can definitely do. Though I still find it strange how these files weren't dragged in automatically when you tried to build the project.

The one file that remains now is the dts overlay file for the board. You can have a look at the device tree drop down menu to see if it is there. If it isn't, you can try pressing "create overlay file" and creating one with the same contents.

 

Regards,

Elfving