iOS DFU Writing to characteristic failed

RE: iOS DFU Writing to characteristic failed

Chris — Tue, 20 Jun 2017 11:08:55 GMT

// Optional: // initiator.forceDfu = YES/NO; // default NO // initiator.packetReceiptNotificationParameter = N; // default is 12

please annotation two line and its ok

RE: iOS DFU Writing to characteristic failed

Hung Bui — Tue, 27 Dec 2016 09:09:09 GMT

I think it's fine, we will keep it this way.

RE: iOS DFU Writing to characteristic failed

Dennis Lan — Mon, 26 Dec 2016 06:43:15 GMT

Hi Hung, Thanks for your help, then this issue may no longer exist. So do I need to modify my answer or I just delete right away?

RE: iOS DFU Writing to characteristic failed

Hung Bui — Fri, 23 Dec 2016 13:26:30 GMT

Hi Dennis,

It's great that you figured out the issue. Please be noted that the library you pointed to is obsoleted and should be replaced by this one.

In the new repo the issue is fixed, and you are free to set it to 0 (to disable notification) or to something >12 as mentioned here.

RE: iOS DFU Writing to characteristic failed

Dennis Lan — Fri, 23 Dec 2016 08:22:44 GMT

After Several testing, I found out that the problem may be the same as the following link: github.com/.../24

According to the log in Xcode, the Value for my case return 0

ex. 10: Packet Receipt Notif Req (Op Code = 8, Value = 0) request sent

As the upon link said, maybe the .packetReceiptNotificationParameter was modified by user to return 0. As the result, I modified with following example and it just suceed.

DFUServiceInitiator *initiator = [[DFUServiceInitiator alloc] initWithCentralManager:bluetoothManager target:peripheral];
NSString *selectedPath = [[NSBundle mainBundle] pathForResource:@"selectedfile" ofType:@"zip"];
         NSURL *url = [NSURL fileURLWithPath:selectedPath];
         selectedFirmware = [[DFUFirmware alloc] initWithUrlToZipFile:url];
         [initiator withFirmwareFile:selectedFirmware];
         initiator.forceDfu = [[[NSUserDefaults standardUserDefaults] valueForKey:@"dfu_force_dfu"] boolValue]; 
// initiator.packetReceiptNotificationParameter = [[[NSUserDefaults standardUserDefaults] valueForKey:@"dfu_number_of_packets"] intValue];

         initiator.logger = self;
         initiator.delegate = self;
         initiator.progressDelegate = self;
         controller = [initiator start];

RE: iOS DFU Writing to characteristic failed

Dennis Lan — Thu, 10 Nov 2016 02:15:23 GMT

I see. I'll try to modify the code in my application to be the same as Toolbox. By the way, I'm still purchasing the sniffer from the supplier, it may take some days.

RE: iOS DFU Writing to characteristic failed

Hung Bui — Tue, 08 Nov 2016 08:11:42 GMT

If you change the code in your application to request notification packet after every 12 data packet, the same as the Toolbox does, would the error still occur ?

RE: iOS DFU Writing to characteristic failed

Dennis Lan — Mon, 07 Nov 2016 15:36:26 GMT

Hi Hung, I'll provide the sniffer trace later. The only difference is the following line:

from Toolbox Packet Receipt Notif Req (Op Code= 8, Value = 12) request sent.

from DFUfulllog: Packet Receipt Notif Req (Op Code= 8, Value = 0) request sent. Thanks~

RE: iOS DFU Writing to characteristic failed

Hung Bui — Mon, 07 Nov 2016 13:27:18 GMT

Hi Dennis, I got the log. It seems it's not the issue with service discovery or switching between application and bootloader. I suspect the bootloader crashed in the middle of the process. I would need to see the sniffer trace to understand what went wrong.

You can also try to catch the log when you do DFU with nRFToolbox and compare to see what makes the difference.

RE: iOS DFU Writing to characteristic failed

Dennis Lan — Mon, 07 Nov 2016 08:27:08 GMT

Hi Hung, I couldn't provide the full log cause of Internal server error, I'll just provide the url here. drive.google.com/.../view

I'll try to change the characteristic, thanks!

RE: iOS DFU Writing to characteristic failed

Hung Bui — Mon, 07 Nov 2016 08:09:24 GMT

Hi Dennis, If you are testing with the Buttonless DFU, please make sure you have enabled service changed characteristic IS_SRVC_CHANGED_CHARACT_PRESENT = 1 on both the bootloader and the application.

I assume you have written to the DFU control point to tell the application to switch to the bootloader and the reconnect to the bootloader.

The full log is not attached only a local link, please re-attach it.

RE: iOS DFU Writing to characteristic failed

Dennis Lan — Sat, 05 Nov 2016 13:22:33 GMT

Hi Hung, You're right, I'm testing with the bootloader + application (buttonless DFU). According to the iOSDFULibrary log, I'm sure that DFU service is discovered from the phone within the line 3, please checkout the full log as the attachment above.

By the way, I'll try to use sniffer trace, too. Thanks for your reply!

RE: iOS DFU Writing to characteristic failed

Hung Bui — Fri, 04 Nov 2016 13:40:41 GMT

Hi Dennis,

Are you testing with the bootloader or with your application+ bootloader ( buttonless DFU ) ? Seems like the write command to 00001531-1212-EFDE-1523-785FEABCD123 failed. Have you made sure the DFU service is discovered from the phone ? A sniffer trace would be useful.