OTA DFU SD 8.0 SDK 8.0 Uploaded application does not run

[Lucas]

I am using SD 8.0 SDK 8.0 and MCP 3.8 I am able to find the DFUtarg service and successfully complete the transfer of my applcation (100% complete). However, upon finishing the application does not boot. This is the command I am using to generate my .zip packet. Perhaps this is a CRC problem?

nrf.exe dfu genpkg j1.zip --application nrf51822_xxac.bin --application-version 0xff --dev-revision 0xffff --dev-type 0xffff --sd-req 0x64

[Stian Røed Hafskjold]

The command is right. I tried generating a zip file with the same command containing an example application from the SDK 8.0, and it worked. I see the bin file you are using is for target nrf51822. All the examples in SDK 8.0 are compiling for target nrf51422. So, is you application based on the SDK8.0? Are you sure the application runs with SD 8.0 without using the bootloader?

[Lucas]

My custom application is for custom hardware currently using nRF51822QFAC (HW XLR3). The application works fine without the bootloader. One this to note is that this setup worked with SDK 7.1 SD 7.1. In porting to SD 8.0 SDK 8.0 I had to make some modifications to my application to get it to run. I'm using the new DFU library that came with SD 8.0, but I took my main.c, dfu_ble_svc.c, hci_mem_pool_internal.h, and pstorage_platform.h from my SD 7.1 SDK 7.1 project. Those files seemed to be external to the library so I figured I could use them with SD 8.0 SDK 8.0.

My guess is that it is this line causing the problem

if (bootloader_app_is_valid(DFU_BANK_0_REGION_START) && !bootloader_dfu_sd_in_progress())

bootloader_app_is_valid checks the memory contents as well as CRC? Is CRC enabled by default?

[sruthiraj koodathil]

when am executing this command "nrf.exe dfu genpkg --application nrf51422_xxac.hex --application-version 0xffffffff --softdevice s110_nrf51822_7.1.0_softdevice.hex --dev-type 0xffff --dev-revision 0xffff --sd-req 0x5A myfile.zip" i got an error IOError: [Errno 13] Permission denied: 'myfile.zip'

what is the reason for this?

[Inspectron]

There is no answer on this question? So what could be wrong when DFU is completed with sucess but the device is still as DfuTarget visible?