Using 840DK and latest Segger (4.42)
Building Mesh DFU example: dfu_nrf52840_xxAA_s140_7_0_1
Latest Mesh SDK v4
Latest SDK 16
Build with no errors, when starting debug, loads app, soft device without any problems, an runs with following output: No CMD handler!
In one post found suggestion to change RAM_PH_SIZE to RAM_SIZE in flash_placement.xml
<MemorySegment name="RAM" start="$(RAM_PH_START)" size="$(RAM_PH_SIZE)">
but this results in the linking errors.
Building ‘dfu_nrf52840_xxAA_s140_7.0.1’ from solution ‘dfu_nrf52840_xxAA_s140_7.0.1’ in configuration ‘Debug’
Generating linker script ‘dfu_nrf52840_xxAA_s140_7.0.1.ld’
Linking dfu_nrf52840_xxAA_s140_7.0.1.elf
.reserved_ram is too large to fit in RAM memory segment
.data_run is too large to fit in RAM memory segment
.bss is too large to fit in RAM memory segment
.heap is too large to fit in RAM memory segment
section .heap overlaps absolute placed section .stack
Build failed
<t: 0>, main.c, 194, ----- Bluetooth Mesh DFU Example -----
<t: 13451>, serial_handler_prov.c, 267, Generating encryption keypair...
<t: 18243>, main.c, 200, Initialization complete!
<t: 22923>, main.c, 221, Enabling serial interface...
<t: 22926>, mesh_app_utils.c, 65, Device UUID (raw): A5C185160B129148864B03CC8F8DA428
<t: 22929>, mesh_app_utils.c, 66, Device UUID : 1685C1A5-120B-4891-864B-03CC8F8DA428
<t: 22939>, nrf_mesh_dfu.c, 919, ERROR: No CMD handler!
<t: 22946>, main.c, 229, DFU example started!