How "Use sysbuild" option affects on building hex/elf files

Hi everybody
I'm working on XIAO BLE Sense board based on nRF52840.
I'm using nRF Connect SDK 2.5.0. If I select any existing examples like as Blinky, Mesh Light or etc. then build it with default configurations, after flashing it to the board, it won't work!
But if I select "Use sysbuild" option in build configuration settings, after building and flashing, it will work properly.
While as I remember of "nRF Connect SDK Fundamentals" course in lesson 1 "Use sysbuild" has shown as not selected.
Even I tested flashing the created hex/elf files (zephyr.hex/zephyr.elf) separately by Segger J-Flash programmer for two states, but result was as I mentioned.
Selecting "Use sysbuild" also creates an extra "merged.hex" file that it worked for me, too.

Please, tell about this option.

Best Regards
Mehdi Sadeghian

Parents Reply
  • Comparing the map files of the build with and without sysbuild I can see that the memory partition for the sysbuild is very different. 

    I guess that XIAO's memory partition is done in the way that it assumes sysbuild configuration. 

    If you allow me to guess further, I think it has to do something with the xiao_ble_sense_defconfig setting

    # Build UF2 by default, supported by the Adafruit nRF52 Bootloader
    CONFIG_BUILD_OUTPUT_UF2=y
    CONFIG_USE_DT_CODE_PARTITION=y

    You might need to contact XIAO support to understand to get more detail understanding on this.

Children
Related