NRF51 DK don't reset after BLE DFU

[teodf]

Hi,

My bootloader and application work good, I take example from SDK 12. The DFU work correctly but at the end my DK stay in bootloader mode and don't reset to start the application, so i don't see my new application advertising in nRF Connect to see it advertise I need to push button reset or use nrfjprog -p -f nrf51.

When I try with the hex file already compile in folder /bootloader_secure/pca10028_debug/hex I have no problem.

My nrfutil pkg just contain my application there are no bootloader and no softdevice. This can be a problem or not ?

You known the problem ?

Thank You,

Téo Dhien-Fane

[Amanda Hsieh]

Hi Teo, 

 

My bootloader and application work good, I take example from SDK 12.

 Good.  

The DFU work correctly but at the end my DK stay in bootloader mode and don't reset to start the application, so i don't see my new application advertising in nRF Connect to see it advertise I need to push button reset or use nrfjprog -p -f nrf51.

What did you modify? Is it still the same bootloader and only the application is different?

Are you able to provide the debug log?

When I try with the hex file already compile in folder /bootloader_secure/pca10028_debug/hex I have no problem.

Do you mean you can use/bootloader_secure/pca10028_debug/hex to update with your new application without the issue? 

 

My nrfutil pkg just contain my application there are no bootloader and no softdevice. This can be a problem or not ?

 If your application still uses the same version of the sofdevice, it should not have the problem. 

What is the command you use to generate the package? Please post the command you use. 

-Amanda H.

[teodf]

I modify nothing, before to do the DFU I test the application to be sure is functional and after I try to do the DFU with this same application.

I don't know why I can see the debug log. Can you explain me why I can do that please.

Yes I have no problem with the file "secure_dfu_secure_dfu_ble_s130_pca10028_debug.hex". The DFU works good and the new application advertise directly after the DFU. I do not need to push button reset to see the new application in Bluetooth List.

For generate the package I use nrfutil pkg generate --hw-version 51 --application-version 2 --application experimental_ble_app_blinky.hex --sd-req 0x87 --key-file private.pem Blinky_led.zip

I may have misspoken, the DFU work and I have the new application but I am forced to do a reset to access to the application.

I hope this is understandable. 

[Amanda Hsieh]

Hi, 

teodf said:

I modify nothing, before to do the DFU I test the application to be sure is functional and after I try to do the DFU with this same application.

 Which is your based example? You should use the example with _debug to develop and get the help of the RTT logging. 

-Amanda H.

[teodf]

My Bootloader is bootloader_secure/pca10028_debug/armgcc/ and my application experimental_ble_app_blinky/pca10028/s130/armgcc/

I will try to get log with RTT

[Amanda Hsieh]

Hi, 

Do you also program the softdevice?

After porgraming s130_nrf51_2.0.1_softdevice.hex under nRF5_SDK_12.1.0\components\softdevice\s130\hex and nrf51422_xxac_s130.hex under bootloader_secure\pca10028_debug\armgcc\_build, do you see the device adverse as DfuTarg?

Also, need the log to know the detail. 

-Amanda H.