Issues in loading application via nRFConnect using Secure Serial Bootloader & SoftDevice

Question

Hello, 
 
 I am using nRF52840, SDK_16.0.0, S140 SoftDevice and Segger 4.16 for flashing the image. I am using ‘ble_app_blinky’. 
 
 1) Initially I loaded Secure serial bootloader with Public/Private key and SoftDevice S140 from below path using nRF Connect Desktop tool. 
 \examples\dfu\secure_bootloader\pca10056_uart\ses\Output\Release\Exe 
 \components\softdevice\s140\hex

2) Later I am trying to load ble_app_blinky example using private/public key. But in nRF Connect tool its showing different address. Application is overlapping to SoftDevice.

3) Still after flashing I am not able to see the application running and device is still in boot mode. Even after reset, device is in boot mode.

4) But using nrfutil tool I am able to flash via secure serial bootloader.

My query is why I am not able to load using nRFConnect Desktop tool after loading Secure serial bootloader and SoftDevice but worked using nrfutil. 
 
 Thanks & Regards 
 Vishnu Beema

Hung Bui · Accepted Answer

Hi Vishnu, I'm sorry, my mistake. 
 I was a bit confused when you mentioned " Later I am trying to load ble_app_blinky example using private/public key. " What exactly you meant by "using private/public key" ? I assume you didn't use the Bootloader to load the application ? 
 If you load the application using nRFConnect, you need to create the bootloader setting and flash the bootloader setting. There reason for bootloader setting is to tell the bootloader that you have a valid application and the bootloader should start the application. 
 You can find some information about that here: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/getting-started-with-nordics-secure-dfu-bootloader#h61sjziauupw1j397q9s9ldr01q4j6d5

Hung Bui · Answer

Hi Vishnu, 
 1)The bootloader setting is normally written when the bootloader booting up and find nothing in the bootloader setting area. It's also get updated when a new image is DFU updated. It will mark the application area as valid area. 
 The reason we generate the bootloader setting and flash it manually is to tell the bootloader that there is a valid image and it should boot to the application instead of staying at DFU mode. 
 2) The bootloader setting has nothing to do with the softdevice. The information about the softdevice is extracted from the softdevice itself and is not stored in the bootloader setting.

Issues in loading application via nRFConnect using Secure Serial Bootloader & SoftDevice

Top Replies