No "Execute Command" after "Calculate CRC Response

RE: No "Execute Command" after "Calculate CRC Response

Aleksander Nowakowski — Tue, 10 Dec 2019 10:06:49 GMT

As you're not using our SDK, but writing your own bootloader, you should decide to use either legacy or secure DFU and prepare binaries that are compatible with it. You may use nrf util https://github.com/NordicSemiconductor/pc-nrfutil to generate valid zip files for secure DFU. For legacy DFU use branch 0.5.x instead.

RE: No "Execute Command" after "Calculate CRC Response

Aleksander Nowakowski — Tue, 10 Dec 2019 10:04:44 GMT

Hello,

If you're using the Secure DFU from SDK 16 you should also prepare a valid binaries to be uploaded. The files you have chosen (blinky_s110_v7_1_0_ext_init.dat (16 B just as a dummy file to test with)) is not compatible with Secure DFU. It's an old, legacy DFU dat file, with very different content.

If you want to test DFU, you may find example HEX and ZIP files (ZIP contains BIN+DAT+manifest.json) in SDK in nRF5_SDK_16.0.0_98a08e2\examples\dfu\secure_dfu_test_images\ble\[BOARD].

Flash the biggest HEX files onto your DK and then try sending one of the ZIP files from the same folder. For start I would recommend without bonds versions.

Regarding the issue, why the DFU just hangs. I've noticed, that the notification (with CRC) is sent before Write Request was acknowledged. Have a look at packet 359: sending write request 0x03, followed by a notification with crc in 360, and then in 361 comes Rcvd Write Response. That should not matter for the DFU library, but in my opinion 360 and 361 should be sent in the opposite order.

Also, I don't know why the 357 and 358 are duplicated, but perhaps one of them was not received and the phone repeated. The reported size of init packet is 16, so only 1 packet was actually processed on the peripheral side.

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Tue, 10 Dec 2019 08:23:34 GMT

Correct, after testing with several different delays I removed them since I didn't notice any difference.
And the empty PDU are filtered out, if they can help I saved the complete log as well.

RE: No "Execute Command" after "Calculate CRC Response

bjorn-spockeli — Tue, 10 Dec 2019 07:56:20 GMT

Hi Mike,
so in the log from November 22nd you added a 5 second delay it seems

A   16:24:59.576   [DFU] Command object sent (CRC = 61066AB5)
V   16:24:59.576   [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
D   16:24:59.576   [DFU] gatt.writeCharacteristic(8ec90001-f315-4f60-9fb8-838830daea50)
I   16:25:04.732   [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-03-01-20-00-00-00-CC-4E-91-35

and in the Wireshark trace its about 1 second between the Master sending the Calculate CRC request and the Slave replying with the CRC value in the notification. So neither the 1 second and 5 second delay resolved the issue. Correct?

And you have also filtered out empty PDUs right?

Aleksander Nowakowski: Any ideas?

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Thu, 05 Dec 2019 09:06:06 GMT

I've captured the frames using the sniffer now, the dfu sequence of the init packet can be seen at the very end of the file.

devzone.nordicsemi.com/.../dfu_5F00_log_5F00_2019_2D00_12_2D00_05_5F00_filtered.pcapng

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Fri, 22 Nov 2019 15:36:06 GMT

I don't have a dedicated analyzer but I've ordered the NRF52 DK to be able to sniff the air traffic.

RE: No "Execute Command" after "Calculate CRC Response

Aleksander Nowakowski — Fri, 22 Nov 2019 15:29:20 GMT

Thanks. I'll have a look at it in Monday.

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Fri, 22 Nov 2019 15:27:08 GMT

That log was from before I added the huge delay.

See new log below:

A   16:24:59.576   [DFU] Command object sent (CRC = 61066AB5)
V   16:24:59.576   [DFU] Writing to characteristic 8ec90001-f315-4f60-9fb8-838830daea50
D   16:24:59.576   [DFU] gatt.writeCharacteristic(8ec90001-f315-4f60-9fb8-838830daea50)
I   16:25:04.732   [DFU] Data written to 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-03-01-20-00-00-00-CC-4E-91-35

RE: No "Execute Command" after "Calculate CRC Response

Aleksander Nowakowski — Fri, 22 Nov 2019 15:20:23 GMT

From the kids you posted above there is just 140ms from when you send 0x03 and the received notification is printed. See last 2 lines of the log.

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Fri, 22 Nov 2019 15:16:45 GMT

Packet characteristic property is set to Write Without Response + Notify.

Connection Interval is set to:
min_int = 20 ms
max_int = 40 ms
timeout = 400 ms.

The delay before sending the notification is set to 5 seconds (huge i guess).

RE: No "Execute Command" after "Calculate CRC Response

bjorn-spockeli — Fri, 22 Nov 2019 14:19:46 GMT

Also a on-air trace that shows the communication between the DFU controller and the DFU target would be usefull. THat way we can compare the timing of our implementation versus yours.

You can use our nRF Sniffer Plugin in Wireshark and a NRF52 DK to capture the trace if you do not have a dedicated Bluetooth Protocol Analyzer, e.g. Ellisys

Best regards

Bjørn

RE: No "Execute Command" after "Calculate CRC Response

Aleksander Nowakowski — Fri, 22 Nov 2019 14:16:04 GMT

How long delay did you add? Did you try something huge, just to test it?

Also, are you using Write Without Response in your DFU implementation?

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Wed, 20 Nov 2019 12:04:38 GMT

The delay didn't change anything.

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Wed, 20 Nov 2019 12:04:02 GMT

Yes, I've tried that but still same result.

RE: No "Execute Command" after "Calculate CRC Response

bjorn-spockeli — Wed, 20 Nov 2019 11:21:08 GMT

Ok, have you had the chance to add a delay before sending the notification (i.e. the CRC response) from the nRF side as suggested by Aleksander Nowakowski?

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Wed, 20 Nov 2019 11:06:08 GMT

We saw the log entry "Checksum received (Offset = %d, CRC = %08X)" once on a Galaxy S7, but we can't reproduce this as it seems independent of log level.

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Tue, 19 Nov 2019 20:12:57 GMT

I was also expecting the "Notification received" log entry but this behavior is constant, it is not something that happens randomly.

I'm using a Samsung Galaxy S8. (Runnning nRF Connect for Mobile 15.11.2019 - version 4.23.0)
On the server side I'm not using the SDK from Nordic since I'm implementing for another microcontroller (esp32), but I'm reading the specs from 1.6.

I've left the office but will try first thing tomorrow to add a short delay before sending the response message with the calculated CRC.

RE: No "Execute Command" after "Calculate CRC Response

miktr112 — Tue, 19 Nov 2019 20:03:22 GMT

At this point I haven't tried with any other images since I never got passed transferring the init package.

RE: No "Execute Command" after "Calculate CRC Response

Aleksander Nowakowski — Tue, 19 Nov 2019 16:06:04 GMT

The last line should say: Data written to 8ec90001-f315-4f60-9fb8-838830daea50,v (0x): 03

And should be followed by: Notification received from 8ec90001-f315-4f60-9fb8-838830daea50, value (0x): 60-03-01-10-00-00-00-B5-6A-06-61

Seems like the notification was received so quickly, that during logging the written data was already replaced by received, and the library has missed the notification. This indeed is a library issue, but as a workaround you may delay this notification a bit, or longer connection interval. Did you modify the bootloader? What SDK is it from and what phone are you using? How often this error happens?

RE: No "Execute Command" after "Calculate CRC Response

bjorn-spockeli — Tue, 19 Nov 2019 15:27:43 GMT

Do you get the same behaviour when using one of the DFU test images from SDK v16.0.0?

Looking at the Android DFU Library code, I find it odd that the log does not contain a log message stating that the Checksum has been received, i.e. Checksum received (Offset = %d, CRC = %08X) when the Command object sent (CRC = %08X) is printed to the log, see https://github.com/NordicSemiconductor/Android-DFU-Library/blob/ebd769c55ce5ef072aaba5b1b14d60c8d5a38d58/dfu/src/main/java/no/nordicsemi/android/dfu/SecureDfuImpl.java#L432

Will run it by the Android developer responsible for the DFU library.

Best regards

Bjørn