This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

New application doesn't run after secure DFU process reaches 100%

Hi to everyone!

I'm following this guide to learn how to use secure DFU on a nRF52832DK board.

All steps have been done successfully, or I think so, until I reach the D4 step where the new program has to start automatically after DFU process, but it never runs.

Instead, the LED 3 lights up and If I press the button 4, the LED 1 also lights up and I can resend another application over DFU. So I think the board is still in the bootloader.

Indeed, I have some cuestions related to this:

  1. BLE Secure DFU example is only a boot loader or it also has an application?

  2. Depending on the above answer, if it is only a boot loader, do I have to program an application before doing the DFU proccess?

  3. The application, that will be written after DFU proccess, must use SoftDevice? (For my test, I upload my own blinky program. It works well when I flash the board directly through USB. But it doesn't use SoftDevice at all).

Thanks in advance!

Parents
  • Hi nemunoz, I just tried doing a secure dfu with the blinky app found in the folder: nRF5_SDK_14.0.0_3bcc1f7\examples\peripheral\blinky\pca10040\s132. Have you tested the blinky program without the bootloader? I had two issues when doing this: firstly, I had to use the blinky example in the peripheral folder that uses the softdevice to be able to create the zip file in step C2 of the secure dfu blog post. Remember to use the 0x9D value after --sd-req, as you are using the SD 132 v 5.0.0 (this can be verified by looking at this folder: nRF5_SDK_14.0.0_3bcc1f7\components\softdevice\s132\hex). What output code did you get once you created the zip file? I got Zip created at app_dfu_package.zip (depends on what you call the zip file). It could be something with the version rule maybe? For me it worked if I set it to 1. Lastly, I used nrfgostudio to flash the softdevice first (located in the nRF5_SDK_14.0.0_3bcc1f7\components\softdevice\s132\hex folder) & then the correct bootloader which I built using Keil. Then, I sent the zip file I generated to myself via email, opened the email on my phone & opened the zip file with nrf toolbox. From there, it should be straight forward. Lastly, after the DFU process was complete, the LEDs started blinking like they should in the blinky example. Hope that helps!

Reply
  • Hi nemunoz, I just tried doing a secure dfu with the blinky app found in the folder: nRF5_SDK_14.0.0_3bcc1f7\examples\peripheral\blinky\pca10040\s132. Have you tested the blinky program without the bootloader? I had two issues when doing this: firstly, I had to use the blinky example in the peripheral folder that uses the softdevice to be able to create the zip file in step C2 of the secure dfu blog post. Remember to use the 0x9D value after --sd-req, as you are using the SD 132 v 5.0.0 (this can be verified by looking at this folder: nRF5_SDK_14.0.0_3bcc1f7\components\softdevice\s132\hex). What output code did you get once you created the zip file? I got Zip created at app_dfu_package.zip (depends on what you call the zip file). It could be something with the version rule maybe? For me it worked if I set it to 1. Lastly, I used nrfgostudio to flash the softdevice first (located in the nRF5_SDK_14.0.0_3bcc1f7\components\softdevice\s132\hex folder) & then the correct bootloader which I built using Keil. Then, I sent the zip file I generated to myself via email, opened the email on my phone & opened the zip file with nrf toolbox. From there, it should be straight forward. Lastly, after the DFU process was complete, the LEDs started blinking like they should in the blinky example. Hope that helps!

Children
No Data
Related