DFU has stopped working since upgrade to nRF5_SDK_for_Thread_and_Zigbee_3.X

[Liam]

Our BLE DFU has stopped working in SDK 3 so I have tried to simplify it by going back to SDKs.

If I compile D:\NordicSemi\nRF5_SDK_for_Thread_and_Zigbee_2.0.0_29775ac\Examples\dfu\secure_bootloader\pca10056_ble using latest segger and then add that and the softdevice in nRF Connect it works fine. I can see the DfuTarg appears on blue tooth list. Also nRF Connect indicates that there is a bootloader present (shows red and black).

If I do the same with D:\NordicSemi\nRF5_SDK_3.1.0\examples\dfu\secure_bootloader\pca10056_ble it does not work. It does not even program (log attached)2019-09-05T14_54_56.241Z-log.txt

Nothing appears in the BT list. Also nRF shows the bootloader as just application code. The only change is the SDK.

Any ideas please?

kind regards

Liam

[Hung Bui]

Hi Liam, 

Have you tried using nrfjprog to program ? 

The issue could be related to the fact that in new SDK the bootloader address is stored in the MBR area. You can have a look at my answer here.

Our suggestion is to modify the bootloader after you have written the bootloader address into the MBR area, so that it won't try to write to there again. 

[Liam]

Switching to nrfjprog seems to have fixed the problem. Thanks.

I've noticed that there is a BUTTON_PULL in nrf_bootloader.c. BUTTON_PULL is no longer defined in my project because  I removed define PCA100056 because I'm not running on a dev board. I think BUTTON_PULL should be NRF_GPIO_PIN_PULLUP as referenced in this previous ticket https://devzone.nordicsemi.com/f/nordic-q-a/1432/button_pull-in-app_uart-c


Thanks again