DFU failure

RE: DFU failure

Edvin — Fri, 20 Jul 2018 13:12:00 GMT

I haven't tested the mac version. It should probably be the same way. Open the Bluetooth Low Energy application in nRF Connect. Connect to your device (buttonless_dfu). I'l just use the normal bootloader project for now.

After connected, press the DFU button. Please see the attached screenshot:

Then you just select the file which you want to upload, and press "Start DFU".

Since you are able to upload some DFU packets before, I assume you have got the basics up and running, but just in case it may be of any help, I'll attach a link to a blog post describing how to perform the DFU operation step by step.

https://devzone.nordicsemi.com/b/blog/posts/getting-started-with-nordics-secure-dfu-bootloader

Best regards,

Edvin

RE: DFU failure

mregan11 — Fri, 20 Jul 2018 12:58:09 GMT

I downloaded nRF connect for Mac but I'm not sure how to use it to perform firmware updating. Do I need to use the windows version?

RE: DFU failure

Edvin — Fri, 20 Jul 2018 12:46:16 GMT

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?

RE: DFU failure

mregan11 — Fri, 20 Jul 2018 12:32:00 GMT

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!

RE: DFU failure

Edvin — Fri, 20 Jul 2018 12:13:24 GMT

Ok. So it is only for one particular DFU project that you are trying to upload? That would suggest that the issue is not in the bootloader.

Are you sure that you are using the correct application version (at least one higher than the application that is already running?)

Can you please try to perform the DFU operation with nRF Connect for Desktop, and see where it fails there?

Do you get any messages like "INVALID_OBJECT", or "INSUFFICIENT_AUTHENTICATION"?

Does your bootloader require bonding? (By default it does not, so if you have not changed that part, then it probably doesn't).

Best regards,

Edvin

RE: DFU failure

mregan11 — Fri, 20 Jul 2018 11:19:43 GMT

Edvin,

The messages for a failure are below. I think I can isolate the problem to a specific application version that I've written. I don't know of a good way to debug issues related to DFU, so I'm trying to what sort of issue could prevent the device renaming from occurring.

Thanks!

Verbose: Connecting to LSG Troffer A7E0...

Debug: centralManager.connect(peripheral, options: nil)

Debug: [Callback] Central Manager did connect peripheral

Info: Connected to LSG Troffer A7E0

Verbose: Discovering services...

Debug: peripheral.discoverServices(nil)

Info: Services discovered

Verbose: Starting Secure DFU...

Info: Connected to LSG Troffer A7E0

Info: Services discovered

Verbose: Secure DFU Service found

Verbose: Discovering characteristics in DFU Service...

Debug: peripheral.discoverCharacteristics(nil, for: FE59)

Info: DFU characteristics discovered

Verbose: Enabling indications for 8EC90003-F315-4F60-9FB8-838830DAEA50...

Debug: peripheral.setNotifyValue(true, for: 8EC90003-F315-4F60-9FB8-838830DAEA50)

Verbose: Indications enabled for 8EC90003-F315-4F60-9FB8-838830DAEA50

Application: Buttonless DFU indications enabled

Warning: Application with buttonless update found

Verbose: Trying setting bootloader name to Dfu05676

Verbose: Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...

Debug: peripheral.writeValue(0x02084466753035363736, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)

Info: Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50

Info: Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200204

Error: Error 4: Operation failed

Verbose: Disconnecting...

Debug: centralManager.cancelPeripheralConnection(peripheral)

Debug: [Callback] Central Manager did disconnect peripheral

Info: Disconnected

RE: DFU failure

Edvin — Fri, 20 Jul 2018 08:18:35 GMT

Do you have a log from when the update fails as well?

BR,

Edvin

RE: DFU failure

mregan11 — Thu, 19 Jul 2018 15:14:17 GMT

Edvin,

Attached are some of the log messages from the nrfToolbox with a successful update.

There is a section where the app is 'Trying setting bootloader name to Dfu82561'. In this case, the indication received is (0x):200201, which is successful. The app then goes on to reset the 52832 and update the firmware.

I have see instances where the indication received is (0x):200204, which is the error number 4. The app then reports this error and fails in the firmware update. I'm wondering what could prevent the bootloader name from being changed to Dfu82561.

Thanks!

Verbose: Connecting to LSG Troffer 623B...

Debug: centralManager.connect(peripheral, options: nil)

Debug: [Callback] Central Manager did connect peripheral

Info: Connected to LSG Troffer 623B

Verbose: Discovering services...

Debug: peripheral.discoverServices(nil)

Info: Services discovered

Verbose: Starting Secure DFU...

Info: Connected to LSG Troffer 623B

Info: Services discovered

Verbose: Secure DFU Service found

Verbose: Discovering characteristics in DFU Service...

Debug: peripheral.discoverCharacteristics(nil, for: FE59)

Info: DFU characteristics discovered

Verbose: Enabling indications for 8EC90003-F315-4F60-9FB8-838830DAEA50...

Debug: peripheral.setNotifyValue(true, for: 8EC90003-F315-4F60-9FB8-838830DAEA50)

Verbose: Indications enabled for 8EC90003-F315-4F60-9FB8-838830DAEA50

Application: Buttonless DFU indications enabled

Warning: Application with buttonless update found

Verbose: Trying setting bootloader name to Dfu82561

Verbose: Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...

Debug: peripheral.writeValue(0x02084466753832353631, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)

Info: Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50

Info: Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200201

Application: Response (Op Code = 2, Status = 1) received

Application: Bootloader name changed successfully

Verbose: Writing to characteristic 8EC90003-F315-4F60-9FB8-838830DAEA50...

Debug: peripheral.writeValue(0x01, for: 8EC90003-F315-4F60-9FB8-838830DAEA50, type: .withResponse)

Info: Data written to 8EC90003-F315-4F60-9FB8-838830DAEA50

Info: Indication received from 8EC90003-F315-4F60-9FB8-838830DAEA50, value (0x):200101

Application: Response (Op Code = 1, Status = 1) received

Debug: [Callback] Central Manager did disconnect peripheral

Info: Disconnected by the remote device

Verbose: Scanning for the DFU Bootloader...

Info: DFU Bootloader found with name Dfu82561

Verbose: Connecting to Dfu67852...

Debug: centralManager.connect(peripheral, options: nil)

RE: DFU failure

Edvin — Thu, 19 Jul 2018 14:53:41 GMT

Hello Mathew,

I don't think that the phone is trying to rename the device. Are you sure that the phone is not trying to find a device named DfuTarg?

Do you have another DK, so that you can try to do this using nRF Connect for Desktop?

Is there something special that you have done with the bootloader? Static address, Bootloader requires bonding? Have you changed anything in the Bootloader project?

Best regards,

Edvin

RE: DFU failure

mregan11 — Thu, 19 Jul 2018 14:47:13 GMT

Hi Edvin,

I am trying to upload application error. I see the error 4 as a print out from the nrf Toolbox app. The app disconnects from the 52832 after reporting the error 4.

By observing the log messages, my understanding is the nrf toolbox app is trying to rename the device from the name I've given it to DfuTarg before resetting the 52832 into bootloader mode.

RE: DFU failure

Edvin — Thu, 19 Jul 2018 14:43:38 GMT

Hello Matthew,

What custom firmware are you trying to upload? An application or bootloader firmware?

Could you specify where you get the error 4? In nRF Toolbox, or in the application?

Are you trying to rename the DfuTarg before you reset, or is the application failing to update the name, and then it resets?

Sorry there are a lot of questions and no answers, but I am just trying to understand where the issue occurs.

Best regards,

Edvin