Updating from 2.3 to v2.5 errors

[IvanR]

In prj.conf I have defined

CONFIG_NEWLIB_LIBC=y

but i get error 

CONFIG_NEWLIB_LIBC was assigned the value y, but got the value n. Missing dependencies: NEWLIB_LIBC_SUPPORTED

also im getting this error but I do have pm_static.yml in my boards folder:

-- C_FLAGS : -Wall -Wextra
CMake Warning at C:/ncs/v2.5.0/nrf/cmake/partition_manager.cmake:79 (message):

---------------------------------------------------------------------
--- WARNING: Using a bootloader without pm_static.yml. ---
--- There are cases where a deployed product can consist of ---
--- multiple images, and only a subset of these images can be ---
--- upgraded through a firmware update mechanism. In such cases, ---
--- the upgradable images must have partitions that are static ---
--- and are matching the partition map used by the bootloader ---
--- programmed onto the device. ---
---------------------------------------------------------------------

Call Stack (most recent call first):
C:/ncs/v2.5.0/zephyr/cmake/modules/kernel.cmake:247 (include)
C:/ncs/v2.5.0/zephyr/cmake/modules/zephyr_default.cmake:138 (include)
C:/ncs/v2.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/ncs/v2.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
CMakeLists.txt:2 (find_package)

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)
| ^~~~~~~~~~~~~~

What changed from 2.3 to 2.5 ? I cant find the references. 

[Hung Bui]

Hi Ivan, 
Could you please double check in your autoconfig.h if you have CONFIG_NEWLIB_LIBC_SUPPORTED=y.

By default this value should be y:
 https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/kconfig/index.html#!CONFIG_NEWLIB_LIBC_SUPPORTED

Have you tested with the smp_svr sample in nRF Connect v2.5.0 ? 

[IvanR]

CONFIG_NEWLIB_LIBC_SUPPORTED was assigned the value y, but got the value n. Missing dependencies:
"" = y

 im using nrf5340

[Hung Bui]

What I meant is to provide the build log of your project not smp_svr. 
From what I can see you can build smp_svr with no problem , correct ? 
When you post a long log, please use Insert ->Code

[IvanR]

both are provided and as I can see it does not use NEWLIB_LIBC. Also the issue with pm_static.yml exists there also

[Hung Bui]

In the build for your project, I don't see any complain about NEWLIB so I assume you only see "CONFIG_NEWLIB_LIBC_SUPPORTED was assigned the value y, but got the value n. " in VSCode , correct ? 
If it's the case, it's just a glitch in VS Code, you can ignore that. As long as the compiler/linker doesn't complain, then it's OK. 

[IvanR]

sorry for the confusion: if I add

"CONFIG_NEWLIB_LIBC_SUPPORTED=y

I get 

error: NEWLIB_LIBC_SUPPORTED (defined at lib/libc/Kconfig:26) is assigned in a configuration file,
but is not directly user-configurable (has no prompt). It gets its value indirectly from other
symbols. See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NEWLIB_LIBC_SUPPORTED and/or
look up NEWLIB_LIBC_SUPPORTED in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

CMake Error at C:/ncs/v2.5.0/zephyr/cmake/modules/kconfig.cmake:348 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/ncs/v2.5.0/nrf/cmake/modules/kconfig.cmake:29 (include)
  C:/ncs/v2.5.0/zephyr/cmake/modules/zephyr_default.cmake:129 (include)
  C:/ncs/v2.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
  CMakeLists.txt:2 (find_package)

there is no error when:

CONFIG_NEWLIB_LIBC=y

[Hung Bui]

Hi, 

You are not supposed to configure directly 

CONFIG_NEWLIB_LIBC_SUPPORTED=y

You can see that in the documentation: 
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/kconfig/index.html#!CONFIG_NEWLIB_LIBC_SUPPORTED

No prompt - not directly user assignable.

I assume by setting CONFIG_NEWLIB_LIBC=y you have no error now and can use the newlib with no problem ?  

[IvanR]

code compiles but VS code is returning that 

math.h 

The math library must be enabled by CONFIG_NEWLIB_LIBC to be included in the build

Is that something about the VS Code extension or?

also what about the warning about pm_static.yml.?

[Hung Bui]

Hi Ivan, 

I don't get it. Do you have CONFIG_NEWLIB_LIBC=y in your prj.conf or not ? 
Please ignore the warning showed by VSCode (the red underline) 

You can check if NEWLIB_LIBC is enabled or not in your project by looking at the autoconf.h inside \build\zephyr\include\generated folder. 
You should see this: 

Regarding the issue with pm_static.yml, could you try putting the file in the project root folder ? Something like this: 

If you need different pm_static for different boards, you may want to take a look at this thread:  how to define 2 boards for the same application 

[IvanR]

Yes I have CONFIG_NEWLIB_LIBC=y but VS code extension is giving an error.

Usually, it was correct. so there's an issue with the extension?

moving the pm_static.yml solved the issue. Thx!

[Hung Bui]

Yeah, it's an issue with VSCode extension that it doesn't always discover all the config setting especially if they are set in multiple child images or libraries. 

If there is really an issue that cause a configuration get a value different from the value you set, you will see it as a warning red text in the build log. For example something like this: