[nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

RE: [nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

Kenneth — Wed, 01 Nov 2023 08:57:34 GMT

Looks like a collegue found the cause, see here:
https://devzone.nordicsemi.com/f/nordic-q-a/105249/warning-pm-defined-at-soc-arm-microchip_mec-mec172x-kconfig-defconfig-series-36-is-occured-after-upgrading-sdk-2-5-0-from-sdk-2-3-0

https://github.com/nrfconnect/sdk-zephyr/commit/96b38273138f05dd06cf7a58fa361f401e773e5e

tldr; It's not supported anymore, since it's not required to achieve low power.

I was not aware of this change, so sorry for the confusion.

Kenneth

RE: [nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

MarkK — Wed, 01 Nov 2023 06:55:03 GMT

Same issue here for nrf5340. I just installed SDK v2.5.0 through NRF Connect for desktop.

RE: [nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

KIM DAE HYUN — Wed, 01 Nov 2023 01:29:30 GMT

I have same issue after changing SDK V2.5.0

RE: [nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

Patrick — Tue, 31 Oct 2023 21:42:51 GMT

Just wanted to chime in to say that I have the same issue. NCS v2.5.0 was installed through VSCode.

RE: [nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

Audifaz — Tue, 31 Oct 2023 18:44:51 GMT

Even after applying the west commands, I still get the same Kconfig warning 😞

RE: [nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

Kenneth — Tue, 31 Oct 2023 18:17:49 GMT

Assuming the toolchain is installed correctly, then it must be something that have gone wrong here at some point with the repositories is my best guess. Maybe you can run in v2.5.0 root:

west forall -c "git reset --hard"

west forall -c "git clean -fxd"

In an nRF Connect terminal window you should get something like:

Kenneth

RE: [nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

Audifaz — Tue, 31 Oct 2023 15:53:54 GMT

The commit file that seems modified is just a vscode configuration that do not interfere with the code.

More than an error is a precompile warning of the Kconfig, nevertheless, it sets CONFIG_PM to n.

RE: [nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

Audifaz — Tue, 31 Oct 2023 15:35:04 GMT

RE: [nrfConnect 2.5.0] CONFIG_PM cannot be set to y in Kconfig with nrf52833

Kenneth — Tue, 31 Oct 2023 15:04:45 GMT

I can't see such error when compiling: