NCS sample peripheral_power_profiling gives build warning

[mchartier]

Using NCS SDK v2.1.0 

Example Project: nrf/samples/bluetooth/peripheral_power_profiling

Building the example project gives build warnings:

Could you help me understand the second warning and how to fix it.

I am new to the nRF Connect SDK so I am trying to understand how the kconfig files work and all the dependencies. It appears this build has defined the acceptable range for this value as 1...0 which is non-sensical. The acceptable range is defined in Kconfig to be 1...BT_L2CAP_TX_MTU but I don't know where this value (BT_L2CAP_TX_MTU) comes from.

[mchartier]

Just another observation about the problems tab. I'm adding here as it may help the developer sort out the problem. 

I am adding new source files to my /src/ folder but I have not yet added these files to my CmakeLists.txt file yet. The build completes without errors, however the problems tab is showing errors from the new source files which are not yet part of the build. Feature? or Bug?

By the way I just upgraded to the November release of nRF Connect for VS Code.

[dejans]

Hi Michael,

I have provided your observation to the team internally. I'll get back to you when I get new information related to this issue.

Best regards,
Dejan

[dejans]

Hi Michael,

Can you check if nRF Kconfig extension 2022.11.50 solves your issue?

Best regards,
Dejan