DFU failure

[mregan11]

I'm using SDK 15 and soft device S132 6.0.  Using nrf Toolbox to update custom firmware, I'm running into a situation where the DFU update fails with an error code 4 when trying to rename to DfuTarg before resetting into the bootloader.  

What are some possible reasons why this failure could occur?  What is error code 4?

I'm using similar firmware in other instances and have not had this error occur, so I'm looking for reasons why this error could occur.

Thanks,

Matthew

[mregan11]

Edvin,

I agree that I don't think the issue is the bootloader, and the bootloader does not require bonding. The issue is not with the firmware version. I have built my application from the Buttonless DFU template application with no bonding.  Here's my question:

Under what state, or under what condition, would the Buttonless DFU template application receive and then reject the renaming request from the nrf Toolbox app?

Thanks!

[Edvin]

Hello,

I don't know.

Typically the device performing the DFU operation doesn't rename the device. The device, DfuTarg is defined in the bootloader application:

SDK\examples\dfu\secure_bootloader\pca_10040\config\sdk_config.h.

 

Can you please try with nRF Connect and see what sort of error you get there?