Upload application via BLE

RE: Upload application via BLE

Hung Bui — Wed, 02 Oct 2019 11:04:07 GMT

Please create a new case !

RE: Upload application via BLE

lynxemi — Wed, 02 Oct 2019 09:35:25 GMT

Ok, so that link has helped a fair bit ... I have been able to make some headway. However, the response code I am getting to the 'Create command: size [01 01 XXXXXXXX] in the Init Block is not [60 01 01] but [60 01 04] and I cannot for a reference to the response codes ...

Are you able to direct me accordingly?

RE: Upload application via BLE

Hung Bui — Tue, 01 Oct 2019 11:23:07 GMT

The DFU protocol has changed quite a lot, especially when we move from legacy DFU to the secure DFU in SDK v12.

The documentation in https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_dfu_transport_ble.html?cp=5_1_3_5_2_2 should provide enough information to build a DFU master.

It would be much easier if you can get the sniffer working and capture a successful DFU session to match the protocol documentation with the implementation.

Please create a new case(s) on each of issue you are having now including the sniffer.

RE: Upload application via BLE

lynxemi — Tue, 01 Oct 2019 03:42:36 GMT

Hi,

Yes I'm aware that the code you asked me to consult uses a NRF5 chip to make connection. We have a fully working system and have been able to perform DFU using the PCA10056 and Android.

Obviously doing a DFU does not exclusively require a NRF5 chipset as the upgrades can be achieved using an Android device with a variety of other BT chipsets.

The reason I've posted to this thread is that the OPs code is based on using bluez/gatttool from a solution that used the native Bluetooth chip and was able to make it work 3 years ago on a older SDK which in turn was based on older code for the NRF51 here github.com/.../ota-dfu-python

I am trying to modify this to work with the new SDKs but I'm in able to find documentation that would describe the DFU process (which would have been required to write the DFU functionality).

My attempts to sniff the traffic with the nrfsniffer tool also ended up being highly frustrating and I seem to be having to use a chainsaw to cut bread.

If you'd prefer this moved to a different thread then please suggest a query that would direct me to information that would help.

Cheers,

David

RE: Upload application via BLE

Hung Bui — Mon, 30 Sep 2019 14:16:17 GMT

The python application is to be used with a Nordic nRF5x connect to a PC (or a Raspberry PI), not the native R PI bluetooth.

The documentation I point to has the characteristics and the protocol you need to do DFU. I'm not sure what else you are looking for.

Before you start your DFU application on the R.PI, I would suggest to write a normal application that can communicate with the NRF5 chip to make a connection, transmit data for example first.

I don't think we should continue here, it's better that you can create a new case. You can leave the link to your new case here.

RE: Upload application via BLE

lynxemi — Mon, 30 Sep 2019 12:24:55 GMT

I am feeling very stupid here ... no matter what I look at, I don't seem to find the information I need to use. I am trying to update the devices already in DFU mode using a Raspberry Pi BT interface ... using a functional gatttool utility. The python application above does not quite work as it fails getting notification.

What I am after is some list of what the protocol actually requires ... commands to which characteristic and what notification are expected ... I don't want to have to plow through a tonne of source code to try and find what should be well documented.

For the last couple of hours, I have been trying to get the nrfsniffer working with a PCA10056 ... and the instructions for Wireshark don't work and the example API seems to cause the PCA10056 to crash.

I am going in circles with this, and I am about to throw the towel in and find another way to do this.

Is there any relevant command/ data flow/ notification information on the DFU process anywhere?

RE: Upload application via BLE

Hung Bui — Mon, 30 Sep 2019 09:17:53 GMT

Hi David,

The best source of documentation is to look at the bootloader protocol as defined here: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_dfu_transport_ble.html?cp=5_1_3_5_2_2

It's actually not too difficult. I have an example of doing serial DFU from a NRF52 to another nRF52 here. The code is less than 200 lines of code as far as I remember.

RE: Upload application via BLE

lynxemi — Mon, 30 Sep 2019 06:05:05 GMT

Surely there must be more direct documentation than having to fish through that rather complex set of sources?

RE: Upload application via BLE

Hung Bui — Wed, 25 Sep 2019 13:58:56 GMT

Hi David,

For new SDK, please look into source code of nRFConnect - Bluetooth Low Energy app

RE: Upload application via BLE

lynxemi — Wed, 25 Sep 2019 09:41:54 GMT

Hi. I know this has been a while, but I'd like a method that works with the newer SDKs. I have 2 requirements, one for 14.2 and 15.2. I don't seem to be able to find relevant info on the DFU processes (and uuids) for the newer SDKs. Any direction appreciated.

RE: Upload application via BLE

Hung Bui — Thu, 28 Jul 2016 12:28:06 GMT

@astronomer: it looks right !

You may probably already know, but just in case, you can have a look at C:\Program Files (x86)\Nordic Semiconductor\Master Control Panel\3.10.0.14\lib\dfu, we have the python library for DFU that used by the Master Control Panel application that you can follow.

The rest of the DFU process is described in the documentation here.

RE: Upload application via BLE

astronomer — Thu, 28 Jul 2016 10:01:24 GMT

OK, looking the log from the Android nrfToolBox I modified my script in this way:

I read the DFU version with the command char-read-uuid 00001534-1212-efde-1523-785feabcd123. If the response is 01 00 the nrf52 has an application with DFU Service, if the response is 08 00 the nrf52 is already in DFU mode and you need to follow the DFU mode procedure.
Read the handles of UUID 0x2902, it replies in my case with handle 0x0b and 0x14.
Read the handles of UUID 00001531-1212-efde-1523-785feabcd123, it replies 0x13
Write the command char-write-req 0x14 01 to enable notifications
Write the command char-write-req 0x13 0104 to go in DFU mode (04 says that I want to upload an application)
Reconnect the board and follow the same procedure for DFU mode, I'll upload the new version to my github: github.com/.../ota-dfu-python

RE: Upload application via BLE

astronomer — Tue, 26 Jul 2016 13:47:28 GMT

I can do the same thing with nFTToolbox for Android I think. Anyway, now I forsaken the Iron Python code and I'm trying to create a simple C# application to establish a connection to my board, discover services and write commands and datas.

RE: Upload application via BLE

Hung Bui — Tue, 26 Jul 2016 12:15:22 GMT

As you can see, both of them are for NRF51, you have nRF52 board. But you can use nRFConnect instead.

The nRF Connect doesn't support DFU yet, but you can use it to do service discovery, read, write, enable notification, basically can tell the application switch to bootloader.

RE: Upload application via BLE

astronomer — Tue, 26 Jul 2016 11:28:00 GMT

I have this one: infocenter.nordicsemi.com/index.jsp

I tried with both of: www.dropbox.com/.../Screenshot 2016-07-26 13.26.30.png but the result is the same.

RE: Upload application via BLE

Hung Bui — Tue, 26 Jul 2016 10:15:29 GMT

Which hardware board did you use for the Master Control Panel ? It should be a NRF51 Dongle or DK. Have you flashed the board with the MEFW firmware comes with the Master Control Panel ?

RE: Upload application via BLE

astronomer — Tue, 26 Jul 2016 09:34:36 GMT

Yes but I can't work with the Master Control Panel, is very frustrating! Here some screenshots: www.dropbox.com/.../Screenshot 2016-07-26 11.30.35.png www.dropbox.com/.../Screenshot 2016-07-26 11.30.29.png www.dropbox.com/.../Screenshot 2016-07-26 11.30.10.png

RE: Upload application via BLE

Hung Bui — Tue, 26 Jul 2016 08:27:07 GMT

@astronomer: For testing, I suggest you first try with the Master Control Panel binary application and make sure you can switch between application and bootloader (also to know which CCCD handle you should write to). Then you can continue to your Iron Python application.

RE: Upload application via BLE

astronomer — Mon, 25 Jul 2016 15:06:29 GMT

I'm trying Master Control Panel with Iron Python because I should create the same application for Windows: infocenter.nordicsemi.com/index.jsp

But the I had to change something on the code because I think that the script is not allowed to start from /dfu/main.py

RE: Upload application via BLE

Hung Bui — Mon, 25 Jul 2016 14:09:51 GMT

@astronomer: If you use Master Control Panel to do a service discovery you should be able to know your CCCD handle ID.

In addition, when you add a characteristic in to your attribute table on the slave with sd_ble_gatts_characteristic_add(), you will receive the ble_gatts_char_handles_t as an output and you can find CCCD handle with that.

RE: Upload application via BLE

astronomer — Mon, 25 Jul 2016 09:30:16 GMT

I'm watching this link: infocenter.nordicsemi.com/index.jsp "First, you must write the value 0100 to the CCCD for the DFU Control Point characteristic to enable DFU notifications. " But I don't understand how to retrieve the CCCD handle when I have an application with DFU service, is not 0x10 like just the DFU mode. I'm trying to use the function getHandle in this repo but it doesn't work on my NRF52: github.com/.../dfu.py

RE: Upload application via BLE

Hung Bui — Mon, 25 Jul 2016 07:45:45 GMT

@astronomer: I'm glad that it worked now. To let the device enter bootloader mode, you can follow this instruction

RE: Upload application via BLE

astronomer — Thu, 21 Jul 2016 13:33:14 GMT

IT WORKS!!!! github.com/.../ota-dfu-python

Is necessary to send the file dat too and you need to send data in a proper format.

Now I need to find what is the way to go automatically in DFU mode.

RE: Upload application via BLE

astronomer — Thu, 21 Jul 2016 09:01:34 GMT

Maybe I missed this part: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk52.v0.9.2%2Fbledfu_example_init.html

RE: Upload application via BLE

Hung Bui — Thu, 21 Jul 2016 07:54:45 GMT

@astronomer: We need to see the sniffer trace to know what happens with the gattools. Have you managed to use gattools to test with normal application such as with ble_app_hrs (the normal one not the dfu one) to receive battery and HRM notification ?