Hello,
As of nRF Connect SDK v1.3.0, I now get an additional output target called "merged_domain_hex". I don't recall this being part of the output prior to nRF Connect SDK v1.3.0.
Can someone at Nordic shed some light into what this output target is for?
See below for snippet of the end of the build logs...
[ 97%] Linking C executable zephyr.elf
Generating files from zephyr.elf for board: nrf9160_custom_boardns
[ 97%] Built target zephyr_final
Scanning dependencies of target mcuboot_primary_app_hex
Scanning dependencies of target mcuboot_primary_hex
[ 98%] Generating zephyr/mcuboot_primary.hex
[ 98%] Generating zephyr/mcuboot_primary_app.hex
[ 98%] Built target mcuboot_primary_hex
[ 98%] Built target mcuboot_primary_app_hex
Scanning dependencies of target mcuboot_sign_target
[ 98%] Generating ../../zephyr/app_update.bin, ../../zephyr/app_signed.hex, ../../zephyr/app_test_update.hex, ../../zephyr/app_moved_test_update.hex
[ 98%] Built target mcuboot_sign_target
Scanning dependencies of target merged_hex
[ 98%] Generating zephyr/merged.hex
[ 98%] Built target merged_hex
Scanning dependencies of target merged_domains_hex
[100%] Generating zephyr/merged_domains.hex
[100%] Built target merged_domains_hex
Thanks,
Cody