nRF51 OTA DFU: cannot write to DFU control point attribute

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

diode — Wed, 29 Apr 2015 21:55:29 GMT

Hi Hung, I just sent you a private message.

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

Hung Bui — Mon, 27 Apr 2015 15:32:46 GMT

@Diode: PCA10000 dongle contains XLR2 chip when the PCA100031 has XLR3 chip. The SDK and S110 v.8.0 was made for the XLR3 chip. Now I'm kind of lost of what is working and what is not on your side.

Could you please summarize on what is working and what is not , and if not what was showed ? a sniffer trace is recommended.

Test with PCA100028 (what my bootloader compiled for) with MCP on PC and MCP on Android
Test with PCA100031 with MCP on PC and MCP on Android
Test with PCA10001 on MCP PC and MCP on Android.

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

diode — Sun, 26 Apr 2015 02:23:53 GMT

Hi Hung, the diff output showed your bootloader and mine (that was compiled from the nRF51 SDK example without modification) were different. This time I gave it another try with PCA10000 dongle, and OTA DFU worked for both your image and my image. However, I still couldn't got it working with the Master Control Panel app (version 2.1.1) on my Android in either case. Previously, it didn't work with PCA10031 dongle either. However, I could see "DfuTarg" service and could connect to it in all cases. Why is it different on Nordic supported hardware/software?

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

Hung Bui — Fri, 24 Apr 2015 08:00:16 GMT

@diode: I'm seeing from the log that after the bootloader received the image size it didn't response. After 10 seconds, the MCP timed out and disconnect (packet 851 at 19:48:00). I suspect there could be smth wrong with the bootloader firmware you compiled. I attached my bootloader hex file. Could you try to:

Erase the chip
Program softdevice
Program the provided bootloader hex file using "Program Bootloader"
Make sure you updated the firmware on the dongle/DK to use with MCP to v0.11

nrf51422_xxac_bootloader.hex

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

diode — Thu, 23 Apr 2015 16:18:31 GMT

Hi Hung, the 3rd-party BLE central device was based on BL620 from Laird. I used it as nothing too complex other than reading from and writing to BLE peripheral. It worked for other BLE devices. Everything was in command line, so I am no sure if a screenshot made a difference. For your second comment, I was using an unmodified bootloader from nRF51 SDK 8.0.0 on nRF51-DK, and followed the instructions on developer.nordicsemi.com/.../a00091.html exactly. As for the log on my Android Master Control Panel app, I saw "Connected to XXXXXX" and "Services Discovered" after I connected to the DfuTarg service. However, once I hit the "DFU" log to upload a zip file ("dfu_test_app_hrm.zip"), the log showed "Disconnected". And in the next time when I retried, it showed the same behavior. And I also notice the VDD on board was ~2.9V instead of 3.3V.

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

Hung Bui — Thu, 23 Apr 2015 12:55:03 GMT

@Diode: For the first issue, please provide more information on your 3rd party BLE central device. A screenshot would be great. For the second issue, I'm seeing a timeout. Have you tested with an unmodified bootloader ? Which bootloader project did you use ?

Please provide sniffer trace for both cases.

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

diode — Thu, 23 Apr 2015 03:00:24 GMT

Hi Hung, so there are actually two related problems here. For the first problem, I can still not write to the 0x10 to start DFU with my 3rd-party BLE central device. For the second problem, OTA DFU with Master Control Panel Android app doesn't work either, since I cannot see "Dfu_HRM" after that. The log.txt of the Windows version Master Control Panel is pasted here http://pastebin.com/PEsbxGVs . Please let me know what sniffing traces you need.

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

Hung Bui — Wed, 22 Apr 2015 08:01:25 GMT

@diode: Could you confirm the issue you mentioned earlier was fixed ?

I can see that the DFU Control Point has Write property which meant it can be written.

Regarding the issue you are experiencing, have you tried to do DFU with the nRFToolbox app on iOS or Android ? Could you send the log file on Master Control panel when the error occurs ( you can find the log in File menu)

For better debugging, I would need a sniffer trace to see what happened over the air. You would need an extra PCA10028 or PCA10031 or PCA10001 to act as the sniffer.

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

diode — Wed, 22 Apr 2015 03:36:33 GMT

I have followed the instructions on developer.nordicsemi.com/.../a00091.html exactly, with an unmodified bootloader. I am using nRF51-DK (PCA10028), and the version of Master Control Panel x64 program I am using is 3.8.0.7. I can see the DFU service (named "DfuTarg"). However, I still cannot do OTA DFU and get errors like "timeout while waiting for response from device". You can see a screenshot of this problem in this link http://i.imgur.com/VQH0MS6.png . What am I missing?

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

Hung Bui — Mon, 20 Apr 2015 12:55:19 GMT

Have you made sure you haven't modified the bootloader example? Could you take a screen shot when the error occurs ?

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

diode — Sat, 18 Apr 2015 02:45:11 GMT

I tried writing 01-04 to DFU control point, and still got the same error. I am using a 3rd-party gatttool-like application on the BLE central. But at the same time, after downloading the bootloader, I tried to OTA flash the "dfu_test_app_hrm.zip" in nRF51 SDK doc (developer.nordicsemi.com/.../a00091.html) via Nordic's Master Control Panel Android app, but could not see the new "Dfu_HRM" service after it finished. I assume that test application was on SoftDevice 8.0.0. What was I missing?

RE: nRF51 OTA DFU: cannot write to DFU control point attribute

Bobby B — Sat, 18 Apr 2015 02:05:22 GMT

Are you using the latest Master Control Panel (3.8.0.7) to do this? Upgrade if not. Also, try to write 01-04 to the DFU Control Point after writing 01-00 to the CCCD. The 04 signals application (you could also signal bootloader, softdevice, or all). Also, try the iOS app if you haven't yet, it can make this a bit easier.