build and run secure_bootloader example from SDK 15.3.0

[Wujas Dongiel]

Hello, 

I'm trying to build and run 'secure_bootloader/pca10040_ble_debug/armgcc/' example and it seams that it stops with some hard fault:

    Remote debugging using localhost:2331

    0xfffffffe in ?? ()

    (gdb) continue

    Continuing.

    Program received signal SIGTRAP, Trace/breakpoint trap.

    0xfffffffe in ?? ()

When I flash the 'secure_bootloader/pca10040_ble_debug/hex/ binary everything works fine. I can perform DFU and all.

nrf52832_xxaa_s132.mapnrf52832_xxaa_s132.hex

[Vidar Berg]

Hi,

Did you remember to flash the Softdevice as well? You can use the flash_softdevice target for that: make flash_softdevice && make flash. The pre-compiled hex files have been merged with the Softdevice.

[Wujas Dongiel]

Yes, I have done that as well

And before any building I've followed instruction regarding keys generation from here: devzone.nordicsemi.com/.../getting-started-with-nordics-secure-dfu-bootloader

[Vidar Berg]

Your hex file runs fine on my DK. Maybe the BL start address is not set. Try to read out the bootloader start address which is stored inside the MBR:

> nrfjprog --memrd 0xff8 // should return 0x72000

Edit: both flash targets are using the --sectorease option. This will cause the start address to be erased when you run both. Try make flash_softdevice && make flash the configuration below.

# Flash the program
flash: default
	@echo Flashing: $(OUTPUT_DIRECTORY)/nrf52832_xxaa_s132.hex
	nrfjprog -f nrf52 --program $(OUTPUT_DIRECTORY)/nrf52832_xxaa_s132.hex 
	nrfjprog -f nrf52 --reset

# Flash softdevice
flash_softdevice:
	@echo Flashing: s132_nrf52_6.1.1_softdevice.hex
	nrfjprog -f nrf52 --program $(SDK_ROOT)/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex --chiperase
	nrfjprog -f nrf52 --reset

[Wujas Dongiel]

My output is:

$ nrfjprog --memrd 0xff8
0x00000FF8: 00072000 |. ..|

So it seams ok.

[Wujas Dongiel]

Yes, after that I can see DfuTarg running.

Thank You