Restore nRF52840 DK Bootloader and mesh-DFU pc-nrfutil

[erik]

When using nRF Connect I by mistake hit erase-all, which erased the bootloader (and cleared UICR?)

I flashed the MeshSDK v3.0 bin/bootloader/gccarmemb/mesh_bootloader_gccarmemb_nrf52840_xxAA.hex  using nRF_Connect. When therafter using SES to
push down a pre-compiled binary example and run Debug, it gets stuck at address 0x000FABBC (bkpt #0), which is in Bootloader memory area. After some more
more reading, understand the mesh-DFU bootloader requires a special flash procedure and separate git branch of pc-nrfutil, so likely cause of current problem.

Where can I find the .hex file for the nRF52840 DK bootloader to restore to factory config? I am using SDKv15.2. I see a separate post pointed to
pre-compiled Bootloader .hex for nRF52840 Dongle which has DFU serial-USB transport. Can I use same file, or need one supporting DFU-serial-UART transport?
Once have the correct bootloader .hex, will it be sufficient to flash it using nRFConnect, or need to use pc-nrfutil (if so can you point to instructions?)

Is it possible to recreate the DK factory bootloader from one of the SDKv15.2 DFU projects?

Are there any plans to merge the mesh-DFU branch of pc-nrfutil into GIT master? It seems the mesh-DFU branch hasn't been updated for over 2 years, so
have concern it will rot and leave us stranded if follow that path.

Thanks

[Hung Bui]

Hi Erik, 

There isn't a factory bootloader or anything that need to be restored. 

If you do an erase all, please just flash the softdevice and application. 

The softdevice and application is flashed together when you flash using SES. 

Please try to do an erase all and then open SES and flash the light switch example. Please follow the SDK instruction. 

The nrfutil mesh branch is still working fine as we haven't changed anything related to that. 

[erik]

Thanks - it works now.