NCS sample peripheral_power_profiling gives build warning

RE: NCS sample peripheral_power_profiling gives build warning

dejans — Thu, 08 Dec 2022 14:34:41 GMT

Hi Michael,

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

Best regards,
Dejan

RE: NCS sample peripheral_power_profiling gives build warning

dejans — Wed, 30 Nov 2022 09:12:51 GMT

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

RE: NCS sample peripheral_power_profiling gives build warning

mchartier — Mon, 28 Nov 2022 16:03:52 GMT

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.

RE: NCS sample peripheral_power_profiling gives build warning

mchartier — Fri, 11 Nov 2022 15:42:52 GMT

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.

RE: NCS sample peripheral_power_profiling gives build warning

dejans — Fri, 11 Nov 2022 12:40:28 GMT

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

RE: NCS sample peripheral_power_profiling gives build warning

mchartier — Thu, 10 Nov 2022 16:37:31 GMT

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)

RE: NCS sample peripheral_power_profiling gives build warning

mchartier — Thu, 10 Nov 2022 15:56:30 GMT

I just added CONFIG_BT_L2CAP_TX_MTU=65 to prj.conf and ran pristine build. Same result.

RE: NCS sample peripheral_power_profiling gives build warning

dejans — Thu, 10 Nov 2022 15:43:30 GMT

Hi Michael,

Can you try adding CONFIG_BT_L2CAP_TX_MTU=65 to your prj.conf before building?

Best regards,
Dejan

RE: NCS sample peripheral_power_profiling gives build warning

mchartier — Wed, 09 Nov 2022 17:51:00 GMT

Reinstalling VS Code did not solve the problem. Further testing shows the same issue with each workspace I create. Basically the items in the 'Problems' tab never go away. As you can image this makes it very difficult to write code and compile with VS Code.

To dupe the problem you would need to first change the code so it will generate build errors/warnings. Then fix the code and build again. The Problems tab should clear when you run the 2nd build but in my case it does not.

Microsoft reported this on their GitHub forum page for VS Code:

Problems view gets updated automatically when an error is added/removed/updated. In your case, it means the corresponding extension is not updating. So please file issue against the extension.

You can find similar issues by searching for "vs code problems refresh". Here is the page where I found the comment from Microsoft:

https://github.com/microsoft/vscode/issues/111443

Note I am building on M1 Mac with the latest version of VS code and nRF Connect plugin: v2022.10.30

Thanks for looking into this.

RE: NCS sample peripheral_power_profiling gives build warning

dejans — Tue, 08 Nov 2022 08:45:47 GMT

Hi Michael,

I used VS Code (v1.72.0) to build the sample and there was no warning related to BT_POWER_PROFILING_DATA_LENGTH. If you do not see this warning when you build the sample using command line, you could consider reinstalling VS Code.

Best regards,
Dejan

RE: NCS sample peripheral_power_profiling gives build warning

mchartier — Mon, 07 Nov 2022 14:50:58 GMT

I am using the same target board:

This is looking more like a bug with VS code. When I look at the build output I only see the one warning about ASSERT. The other warning about BT_POWER_PROFILING_DATA_LENGTH does not appear in the build output. I even created a fresh new project and I get the same build warning in the "Problems" tab in VS code.

is there some way to clear this out? Or do I need to reinstall VS code?

Note that I created new build configurations and tried different boards but always get the same 'phantom' build warning.

RE: NCS sample peripheral_power_profiling gives build warning

dejans — Mon, 07 Nov 2022 13:54:20 GMT

Hi Michael,

As you can see from .config file located in the your_application_folder\build\zephyr, the value of BT_L2CAP_TX_MTU is set to 65, i.e. CONFIG_BT_L2CAP_TX_MTU=65. You get this value because CONFIG_BT_SMP is enabled in prj.conf. You can find all possible values for CONFIG_BT_L2CAP_TX_MTU in the KConfig documentation.

I have tested the peripheral power profiling sample using nRF52840dk_nrf52840 as the build target, but I could not reproduce your issue. In other words, I did not get the warning related to BT_POWER_PROFILING_DATA_LENGTH.

Peripheral power profiling sample supports several build targets. Could you specify which build target did you use? Is there any difference when you use other build targets?

Best regards,
Dejan