Migration v2.7.0 to v2.8.0 crashes before main() is reached

[MarcelR]

Hi,

I'm having Bluetooth LE peripheral nus code which works fine with v2.7.0 with nrf52840DK (I can connect with an Android App and stream data etc):

  Memory region         Used Size  Region Size  %age Used
            FLASH:      345312 B         1 MB     32.93%
              RAM:      118976 B       256 KB     45.39%

Changing the build configuration to v2.8.0, without any changes produces a much bigger flash:

Memory region         Used Size  Region Size  %age Used
           FLASH:      340640 B     474624 B     71.77%
             RAM:      115112 B       256 KB     43.91%

but the startup never reaches main, the debugger shows

JLinkGDBServerCLExe:
=thread-group-added,id="i1"
=cmd-param-changed,param="pagination",value="off"
0xfffffffe in ?? ()
Program received signal SIGTRAP, Trace/breakpoint trap.
0xfffffffe in ?? ()

These are some compile warnings (which I don't yet know how to address):

warning: NCS_SAMPLE_MCUMGR_BT_OTA_DFU (defined at
/home/bledev/ncs/v2.8.0/nrf/samples/common/mcumgr_bt_ota_dfu/Kconfig:9) was assigned the value 'y'
but got the value 'n'. Check these unsatisfied dependencies: BOOTLOADER_MCUBOOT (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU and/or look up
NCS_SAMPLE_MCUMGR_BT_OTA_DFU 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: IMG_ERASE_PROGRESSIVELY (defined at
/home/bledev/ncs/v2.8.0/nrf/samples/common/mcumgr_bt_ota_dfu/Kconfig:45, subsys/dfu/Kconfig:69) was
assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies:
(NCS_SAMPLE_MCUMGR_BT_OTA_DFU || (MCUBOOT_IMG_MANAGER && IMG_MANAGER)) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_IMG_ERASE_PROGRESSIVELY and/or look up
IMG_ERASE_PROGRESSIVELY 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.

-- Found partition manager static configuration : /home/bledev/bleproj_z/pm_static.yml
Partition 'settings_storage' is not included in the dynamic resolving since it is statically defined.
CMake Warning at /home/bledev/ncs/v2.8.0/nrf/cmake/sysbuild/partition_manager.cmake:188 (message):
  MCUboot padding partition size is 0x200 but signing uses , please adjust
  `PM_MCUBOOT_PAD` value in sysbuild Kconfig to 0x200.
Call Stack (most recent call first):
  /home/bledev/ncs/v2.8.0/nrf/cmake/sysbuild/partition_manager.cmake:630 (partition_manager)
  /home/bledev/ncs/v2.8.0/nrf/sysbuild/CMakeLists.txt:661 (include)
  cmake/modules/sysbuild_extensions.cmake:583 (nrf_POST_CMAKE)
  cmake/modules/sysbuild_extensions.cmake:583 (cmake_language)
  cmake/modules/sysbuild_images.cmake:23 (sysbuild_module_call)
  cmake/modules/sysbuild_default.cmake:20 (include)
  /home/bledev/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  /home/bledev/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  /home/bledev/ncs/v2.8.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)

Do you have any idea on how to proceed?

Thank you
Marcel

[Menon]

Hello,

The warnings you shared are mostly related to configuration issues. Please check if there are any unmet dependencies for the configurations you have enabled. You can use the Kconfig reference for this. Additionally, some warnings pertain to OTA_DFU and the bootloader. You might consider disabling the DFU feature in the application to see if that allows the rest of the application to function correctly.

I'd suggest taking a look at the migration guide to make sure you've covered all the important steps, especially the ones that could affect your setup (if any).

Kind Regards,

Abhijith