Problems in adding FOTA support

Hello,

I'm working on a project in which we are adding FOTA functionality based on application_update example. As soon as I add 

CONFIG_BOOTLOADER_MCUBOOT=y
I see 

Changed board to secure xxxyyyyzzz_nrf9160 (NOT NS)

in the build log, and soon after that these warnings:

warning: NRF_MODEM_LIB_NET_IF (defined at
/opt/nordic/ncs/v2.6.1/nrf/lib/nrf_modem_lib/lte_net_if/Kconfig:6) was assigned the value 'y' but
got the value 'n'. Check these unsatisfied dependencies: NET_SOCKETS_OFFLOAD (=n),
NRF_MODEM_LIB_ON_FAULT_APPLICATION_SPECIFIC (=n), NRF_MODEM_LIB (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NRF_MODEM_LIB_NET_IF and/or look up
NRF_MODEM_LIB_NET_IF 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.


warning: AT_HOST_LIBRARY (defined at /opt/nordic/ncs/v2.6.1/nrf/lib/at_host/Kconfig:7) was assigned
the value 'y' but got the value 'n'. Check these unsatisfied dependencies: NRF_MODEM_LIB (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_AT_HOST_LIBRARY and/or look up
AT_HOST_LIBRARY 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.


warning: MODEM_KEY_MGMT (defined at /opt/nordic/ncs/v2.6.1/nrf/lib/modem_key_mgmt/Kconfig:7) was
assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies: NRF_MODEM_LIB
(=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MODEM_KEY_MGMT and/or look up
MODEM_KEY_MGMT 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.


warning: NET_SOCKETS_OFFLOAD (defined at subsys/net/lib/sockets/Kconfig:219) was assigned the value
'y' but got the value 'n'. Check these unsatisfied dependencies: NET_SOCKETS (=n), NETWORKING (=n).
See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NET_SOCKETS_OFFLOAD and/or look up
NET_SOCKETS_OFFLOAD 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.


warning: The choice symbol NRF_MODEM_LIB_ON_FAULT_APPLICATION_SPECIFIC (defined at
/opt/nordic/ncs/v2.6.1/nrf/lib/nrf_modem_lib/Kconfig.modemlib:213) was selected (set =y), but no
symbol ended up as the choice selection. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NRF_MODEM_LIB_ON_FAULT_APPLICATION_SPECIFIC
and/or look up NRF_MODEM_LIB_ON_FAULT_APPLICATION_SPECIFIC 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.

These warnings do not appear without CONFIG_BOOTLOADER_MCUBOOT=y configuration.

Th build does not fail, but the application seems not to boot.

I have searched for similar problems, like
https://devzone.nordicsemi.com/f/nordic-q-a/107303/config_bootloader_mcuboot-on-custom-nrf9160-board
but haven't succeeded to solve the issue.

Any ideas what might be wrong?

Parents
  • Hello,

    I wanted to let you know that I have been assigned to this case and have started looking into it. Does this issue occur only with your application, or have you tried any sample applications included in the SDK with MCUboot enabled?

    It might be possible that certain dependencies are not satisfied for specific configurations. Please check the dependencies for the configurations mentioned in the warning and ensure they are enabled in your prj.conf file. Additionally, try deleting the build folder and rebuilding the project to start from a clean slate.

    Kind regards,

    Abhijith

Reply
  • Hello,

    I wanted to let you know that I have been assigned to this case and have started looking into it. Does this issue occur only with your application, or have you tried any sample applications included in the SDK with MCUboot enabled?

    It might be possible that certain dependencies are not satisfied for specific configurations. Please check the dependencies for the configurations mentioned in the warning and ensure they are enabled in your prj.conf file. Additionally, try deleting the build folder and rebuilding the project to start from a clean slate.

    Kind regards,

    Abhijith

Children
Related