• State Not Answered
  • Replies 14 replies
  • Subscribers 63 subscribers
  • Views 6136 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 201142
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf52810 dfu can't work

Brian Qin

Hi,


I have met problem when apply dfu of nrf52810.


I used dfu sample of 52810 from devzone link: https://devzone.nordicsemi.com/f/nordic-q-a/28471/about-ota-for-nrf52810-on-sdk-v14-1/112571#112571, but I changed sdk to 14.2

the app is modified from project of ble_app_buttonless_dfu,


the memory address set as below:


IROM1 start 0x18000, size 0x1000, IRAM1 start 0x200024F8,size 0x3B08.


the app package generate by command: nrfutil pkg generate --hw-version 52 --application-version 4 --application nrf52810_xxaa.hex --sd-req  0xA6  --key-file private.key dfu52810.zip


the dfu process never started, what is the issue? or can you share a project of dfu app which is well validated?


thanks!

Brian Qin.

Parents
  • 0

    Hi,

    Sorry for the late response.

    From your description I can't really see any obvious issues, so you will have to debug this and see if you can figure out what some details regarding what is causing this. As I understand it you are able to connect and start the DFU process, but it fails early in the process. What error message are you getting when this happens? Does the device just crash, or do you get an error in nRF Connect? Below I have attached a screen recording where I upload an invalid DFU package so that you can see the error message I am getting. Let me know what you get when you try to do the same.

    Based on your description it sounds like there is a problem with your bootloader or the way you compile, flash, or use the bootloader. The application never gets far enough to run, so the application is not part of the problem. I recommend testing that you get the regular bootloader from the SDK to work on an nRF52832. Then check that you can successfully run the nRF52810 BLE Secure DFU bootloader based on SDK14.1.0 from bjorn-spockeli in the thread you linked to. Jumping straight into porting the solution to SDK14.2.0 on nRF52810 can go wrong in many ways, so it is good to start by verifying that you get the update process to work with the firmware you started with.

    Best regards,
    Rune Holmgren

Reply
  • 0

    Hi,

    Sorry for the late response.

    From your description I can't really see any obvious issues, so you will have to debug this and see if you can figure out what some details regarding what is causing this. As I understand it you are able to connect and start the DFU process, but it fails early in the process. What error message are you getting when this happens? Does the device just crash, or do you get an error in nRF Connect? Below I have attached a screen recording where I upload an invalid DFU package so that you can see the error message I am getting. Let me know what you get when you try to do the same.

    Based on your description it sounds like there is a problem with your bootloader or the way you compile, flash, or use the bootloader. The application never gets far enough to run, so the application is not part of the problem. I recommend testing that you get the regular bootloader from the SDK to work on an nRF52832. Then check that you can successfully run the nRF52810 BLE Secure DFU bootloader based on SDK14.1.0 from bjorn-spockeli in the thread you linked to. Jumping straight into porting the solution to SDK14.2.0 on nRF52810 can go wrong in many ways, so it is good to start by verifying that you get the update process to work with the firmware you started with.

    Best regards,
    Rune Holmgren

Children
No Data
Related