DFU Bootloader through serial USB not working for Mesh

[Peggy TAN]

Hi All,

I am doing a BLE Mesh development project with nRF52840.
SDK version: nRF5 SDK v15.3.0 & nRF5 SDK for Mesh v3.2.0

Case 1:

- IDE: Keil

- Example tested: nRF5 SDK v15.3.0\examples\dfu\secure_bootloader\pca10056_usb_debug

- Application: nRF5 SDK v15.3.0\examples\ble_peripheral\ble_app_blinky\pca10056\s140

- Through: nrfutil & python 2

- Referring to: Secure Bootloader

### Successfully updated the application through bootloader

Case 2:

- IDE: Segger Embedded Studio

- Example tested: nRF5 SDK v15.3.0\examples\dfu\secure_bootloader\pca10056_usb_debug

- Application: nRF5 SDK v15.3.0\examples\ble_peripheral\ble_app_blinky\pca10056\s140

- Referring to: Secure Bootloader

### Failed updated the application through bootloader

Case 3:

- IDE: Segger Embedded Studio

- Example tested: nRF5 SDK v15.3.0\examples\dfu\secure_bootloader\pca10056_usb_debug

- Application: nRF5 SDK v15.3.0\examples\light_switch\client\build\light_switch_client_nrf52840_xxAA_s140_6.1.1_Debug

- Referring to: Secure Bootloader

### Failed updated the application through bootloader

Hence, I would like to ask what is the problem for these to fail?

Or did i missed out anythings?

[Joakim Jakobsen]

Hi.

Talked to a colleague about this. He told me that he noticed two things about your approach.

First;
The pca10056_usb_debug doesn't have softdevice, it's made for MBR . So you need to flash the softdevice manually

Second;
Mesh application is designed to work with the mesh bootloader. So I can't guarantee that it will work with the BLE Bootloader. However, you still need to flash the softdevice.

Best regards,
Joakim

[Peggy TAN]

Hi,

Thanks for your reply.

Yes, I flash softdevice (s140_nrf52_6.1.1_softdevice) before I program bootloader.

I can successfully update the application if I used Keil to flash bootloader and get the application hex.file.

So wondering, is it any setting or command I missed out when using SES?

[Joakim Jakobsen]

Hi. 

Thanks. 

Your problem might be related to a known issue in SDK v15.3.0, i.e. that the bootloader and SoftDevice( specifically the MBR) have overlapping sections.

Please take a look at this thread and the answers from my colleague Bjørn: 
https://devzone.nordicsemi.com/f/nordic-q-a/47651/uicr_mbr_params_page-and-uicr_bootloader_start_address-overwrite-the-beginning-of-the-softdevice 

Best regards, 
Joakim