Undefined reference to pm_state_force on Windows, works fine on Linux

[Nicolas Goualard]

Hi devzone,

I am having a weird problem. I was guiding a new employee to set up their Windows computer to develop our application. Once everything was set up, we built a stable version of our application, but the build failed due to an undefined reference to pm_state_force. I have no issues building the same app on a Linux VM with, to the best of my knowledge, the same parameters (toolchain, etc ). I am reproducing the same issue when I try to build on my windows computer i.e. not in the VM.

Do you have any ideas where this might come from, and how to solve the issue ?

Thanks in advance for your help.

Best regards,

Nicolas Goualard

[IvanR]

Im getting the same issue with fresh install of v2.5.

I check and toolchain and SDK are set to v2.5

 warning: implicit declaration of function 'pm_state_force' [-Wimplicit-function-declaration]

and as a bonus Im getting

warning: return type of 'main' is not 'int' [-Wmain]

also 

C:\ncs\v2.5.0\zephyr\include\zephyr\init.h:193:44: warning: initialization of 'int (*)(void)' from incompatible pointer type 'int (*)(const struct device *)' [-Wincompatible-pointer-types]
193 | .init_fn = {.sys = (init_fn_)}, \
| ^
C:\ncs\v2.5.0\zephyr\include\zephyr\init.h:174:9: note: in expansion of macro 'SYS_INIT_NAMED'
174 | SYS_INIT_NAMED(init_fn, init_fn, level, prio)
| ^~~~~~~~~~~~~~

C:\ncs\v2.5.0\zephyr\include\zephyr\init.h:193:44: note: (near initialization for '__init_battery_setup.init_fn.sys')
193 | .init_fn = {.sys = (init_fn_)}, \
| ^
C:\ncs\v2.5.0\zephyr\include\zephyr\init.h:174:9: note: in expansion of macro 'SYS_INIT_NAMED'
174 | SYS_INIT_NAMED(init_fn, init_fn, level, prio)
| ^~~~~~~~~~~~~~

[Einar Thorsrud]

I see. Have you made any changes in the SDK itself, or is it unmodified SDK 2.5.0? And are you able to build and run sample applications? If not, can you try to download the SDK and toolchain separately from VS Code (as explained here) and see if it works also with your app then?

If your application does not work, but samples do, then perhaps there is an issue with the application or project itself and not the SDK or toolchain install. Perhaps you are missing #include <zephyr/pm/pm.h>? Or perhaps missing CONFIG_PM=y in your prj.conf?

[IvanR]

no, just installed it.

I had 2.3 up to now and chose to do a fresh install. uninstalled 2.3, installed 2.5

Everything worked in 2.3, nothing changed. 

[Nicolas Goualard]

In my case I changed from pm_state_force to sys_poweroff with SDK version 2.5.0 as I used it to make the device go in low power mode.

[IvanR]

thx, will try