• State Verified Answer
  • Replies 8 replies
  • Subscribers 62 subscribers
  • Views 2396 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 129307
Options
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%

nemunoz

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
  • 0

    Hi nemunoz, if you are referring to the BLE Secure DFU Bootloader example in question 1, then yes the example is only a bootloader (see link). So if I understand you correctly, you essentially want to do secure DFU with your own blinky example, which is most likely similar to the Blinky example found in the examples/peripheral/blinky folder, right? The Nordic blinky example found here does not require the softdevice either.

    Essentially, you just want to follow the guide you refer to & in step C1, you just build your own blinky application hex file. If you were using the Nordic blinky example, you could build the program in Keil or Segger Embedded Studio for example. Then, you can find the hex file inside the _build folder if you are using Keil (Output folder for SES). You will have to use the softdevice since you are doing a secure dfu over the air. Essentially, just follow the blog post until step D4. This should hopefully work without any issues. If it doesn't work, let me know & I will test this process using the Nordic Blinky example.

Reply
  • 0

    Hi nemunoz, if you are referring to the BLE Secure DFU Bootloader example in question 1, then yes the example is only a bootloader (see link). So if I understand you correctly, you essentially want to do secure DFU with your own blinky example, which is most likely similar to the Blinky example found in the examples/peripheral/blinky folder, right? The Nordic blinky example found here does not require the softdevice either.

    Essentially, you just want to follow the guide you refer to & in step C1, you just build your own blinky application hex file. If you were using the Nordic blinky example, you could build the program in Keil or Segger Embedded Studio for example. Then, you can find the hex file inside the _build folder if you are using Keil (Output folder for SES). You will have to use the softdevice since you are doing a secure dfu over the air. Essentially, just follow the blog post until step D4. This should hopefully work without any issues. If it doesn't work, let me know & I will test this process using the Nordic Blinky example.

Children
No Data
Related