Updating from 2.3 to v2.5 errors

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. 

Parents Reply Children
  • 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: 

Related