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

DFU not jumping to Application

Hi,

I have a DFU issue. Using Visual GDB IDE and gcc tool chain.

I Can get my signed application generated into zip then DFU it into the device which all works. Once I get that far I expect it to jump to the application. It passes CRC etc then goes to jump but the application will not start. The address it uses is MAIN_APPLICATION_START_ADDR is = 0x1F000 nrf_bootloader_app_start(MAIN_APPLICATION_START_ADDR);

Without the DFU I know that my application starts so it is compatible with the softdevice. Is there something I need to add to my make file? In my application It has placed the ISR_Vector at 0x1f000 which I think should be correct for the DFU.

Thank you

Parents
  • Stuff.zip Hi, I put the blinky project in here also the package and the hex for the bootloader. The bootloader does a whole lot of LED flashing which is to help me debug it but otherwise is pretty straight and standard. It runs on the PCA10040 board. The Blinky project works but it does the same as my project when I bootload it in. I used this command line to generate the package. nrfutil pkg generate --hw-version 52 --sd-req 0x8C --application-version 4 --application Blinky.hex --key-file Key2.pem BlinkyDFU.zip The bootloader is compiled with the same key. As you can easily see the binary in the package is encrypted or corrupted. Really appreciate any help on this.

Reply
  • Stuff.zip Hi, I put the blinky project in here also the package and the hex for the bootloader. The bootloader does a whole lot of LED flashing which is to help me debug it but otherwise is pretty straight and standard. It runs on the PCA10040 board. The Blinky project works but it does the same as my project when I bootload it in. I used this command line to generate the package. nrfutil pkg generate --hw-version 52 --sd-req 0x8C --application-version 4 --application Blinky.hex --key-file Key2.pem BlinkyDFU.zip The bootloader is compiled with the same key. As you can easily see the binary in the package is encrypted or corrupted. Really appreciate any help on this.

Children
No Data
Related