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

dfu fails only if bonded

Hello,

Thanks for reading this! I have an odd behavior on my nrf52832 where I am capable of uploading a new firmware via BLE DFU to the peripheral device if it is not bonded to the central device. However, when I bond, the DFU always fails. I suspect it is for this reason, ie the NOINIT section in the ram is not retaining my bond information when passing to the bootloader. I am using Elcipse GCC, so in order to rectify this, I have to modify this linker script: dfu_gcc_nrf52.ld. I dont know how to do so, can anyone point me in the right direction? Is there any way to check that there is indeed bond information retention?

Thank you very much for your time.

edit for phone screenshot: image description

Parents
  • I have added a screenshot in the original question. Notice that, at the very bottom, myapp.zip is grayed out. Am I not using nrfutil.exe properly? Here is an example of the types of commands I write:

    nrfutil dfu genpkg --application nrf52832_xxaa_s132.hex --application-version 0xffffffff --dev-revision 0xffff --dev-type 0xffff --sd-req 0xfffe myapp.zip
    

    Is it possible that this is a problem with Google drive, which does not recognize that this is indeed a .zip file format? When I use my phone to check information on this file, it says "unknown type".

Reply
  • I have added a screenshot in the original question. Notice that, at the very bottom, myapp.zip is grayed out. Am I not using nrfutil.exe properly? Here is an example of the types of commands I write:

    nrfutil dfu genpkg --application nrf52832_xxaa_s132.hex --application-version 0xffffffff --dev-revision 0xffff --dev-type 0xffff --sd-req 0xfffe myapp.zip
    

    Is it possible that this is a problem with Google drive, which does not recognize that this is indeed a .zip file format? When I use my phone to check information on this file, it says "unknown type".

Children
No Data
Related