DFU of SDK15.3

RE: DFU of SDK15.3

Hung Bui — Tue, 29 Oct 2019 08:36:58 GMT

Hi Hansome,

Please just follow the documentation of the bootloader.

The only note is that when you flash using Keil from the second time, you may erase the MBR, so you need to comment out the code to write to MBR inside nrf_bootloader_info.c. But remember to enable it again if you flashing the bootloader the first time (after a chip erase for example)

RE: DFU of SDK15.3

Hansome — Tue, 29 Oct 2019 01:28:45 GMT

Where are the new operation steps or guide by SDK15.3?

RE: DFU of SDK15.3

Hung Bui — Mon, 28 Oct 2019 13:07:14 GMT

Hi Hansome,

I'm not sure why the bootloader doesn't work. However, regarding the problem that nRFGo Studio doesn't display that the bootloader is flashed, I think it's related to this: https://devzone.nordicsemi.com/f/nordic-q-a/44768/sdk-15-3-cannot-program-default-bootloader

The address of the bootloader now stored inside the MBR, not in the UICR.

The nRFGo Studio is deprecated application and replaced by nRF Connect application.

I would suggest you to test with the bootloader and the softdevice only first. You can flash using nrfjprog.exe application. Make sure you can see the device advertising as DFUTarg, before testing combining with application.