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]

Here is another example to show how the data in the Problems tab is stale. See the screenshot below. In a previous build there was a genuine warning message about "notify_timeout". That issue is now resolved and a new build was run. However the Problems tab still says there is a warning on line 29. When I examine line 29 you can see the the editor is highlighting the wrong symbol (BT_LE_AD_GENERAL)  

[dejans]

Hi Michael,

I have reported the issue internally. For now, you can ignore the warning from the Problems tab. As long as you are able to successfully build your application, the warning from Problems tab should not impede your application development.

Best regards,
Dejan

[mchartier]

For now I think the best option is to disable (or ignore) the Problems tab in my workspace. Then for each build I need to view the full build output and manually search for build warnings and errors. For each warning I use the mouse to select the full path to the source file and then use File-->Open to open that file. Then search for the line with the warning/error. This is the only alternative I am aware of. Development will be slower.