Implementing DFU OTA for beacon

RE: Implementing DFU OTA for beacon

arjun — Tue, 12 Sep 2017 13:33:34 GMT

Thanks Petter, its working.

RE: Implementing DFU OTA for beacon

Petter Myhre — Tue, 12 Sep 2017 10:17:24 GMT

I'm not too familiar with IAR, but it seems you can add the define in the .ewp file

    <option>
      <name>CCDefines</name>
      <state>BLE_DFU_APP_SUPPORT</state>
      <state>BLE_STACK_SUPPORT_REQD</state>
      <state>S132</state>
      <state>BOARD_PCA10040</state>
      ...
      <state>CONFIG_GPIO_AS_PINRESET</state>
      <state>NRF_LOG_USES_UART=1</state>
      <state>SWI_DISABLE0</state>
      <state>SOFTDEVICE_PRESENT</state>
      <state>NRF52</state>
    </option>

RE: Implementing DFU OTA for beacon

arjun — Tue, 12 Sep 2017 09:29:30 GMT

I am using IAR compiler.

I am copying the dfu code snippet in hrs example as it is. The code itself is conditional implementation. It is not working. It works fine when I comment the Ifdef and endif lines, ie. directly including it to the project.

RE: Implementing DFU OTA for beacon

Petter Myhre — Tue, 12 Sep 2017 07:37:23 GMT

This is obviously a mistake, but typically you would bond and share this bond information between application and bootloader, and then you would need the device manager. It is probably why the documentation mentions this, anyways, it is not correct.

Which compiler are you using? Could you explain a bit more about how you are implementing this conditional compilation?

RE: Implementing DFU OTA for beacon

arjun — Tue, 12 Sep 2017 06:48:12 GMT

Hi Petter, I tried as you suggested. Its working fine without the device manager. However I don't understand, why in the tutorial, it is mentioned that device manager must be used.

I have one more doubt.. I am able to get DFU icon in nRF Connect. But I am not able to implement conditional compilation as in hrs example. When I am directly including dfu headers and code snippets, its working and I am able to see the DFU icon in nRF Connect, but when I put it inside ifdef/endif as in hrs example, its not working.

RE: Implementing DFU OTA for beacon

arjun — Mon, 11 Sep 2017 14:28:57 GMT

Thank you. I will try and let you know.

RE: Implementing DFU OTA for beacon

Petter Myhre — Mon, 11 Sep 2017 14:26:26 GMT

I did a quick test, seems to be working without Device Manager. I just skipped calling dfu_app_dm_appl_instance_set() after removing Device Manager.

Here is my main.c, can be used with the ble_app_hrs dfu example.

The first step is to see add the DFU service and get it to appear in nRF Connect.

You need a trigger. You need a way to tell the application that it should go into bootloader mode. This is typically done by a button, or you can go buttonless by using DFU service. The DFU service can only be accessed in a connection.

You can implement buttonless DFU in a beacon application, but then it must be connectable. A beacon is typically not connectable, only advertises.

RE: Implementing DFU OTA for beacon

arjun — Mon, 11 Sep 2017 12:49:09 GMT

In the link you shared, there it is written that device manager must be used (1st point).

No I can't see the DFU service in nrf connect.

So I can't implement buttonless dfu in beacon ??

Also, is it possible to make beacon connectable ??

RE: Implementing DFU OTA for beacon

Petter Myhre — Mon, 11 Sep 2017 12:11:34 GMT

Ok. I don't see how Device Manager is relevant.

Are you seeing the DFU service in nRF Connect?

If by beacon you mean that you will not connect, buttonless DFU is not possible, but DFU is, but you need some way to go to bootloader mode.

RE: Implementing DFU OTA for beacon

arjun — Mon, 11 Sep 2017 11:44:26 GMT

Yes, I am following the following tutorial.

In the template code, device manager code is already there. I am only adding the dfu code snippet.

I am merely copying the dfu code snippet and pasting it in template code as mentioned in the tutorial and as implemented in the hrs example.Practically the code snippet for device manager/dfu are same in both hrs example and template code.

However I will try debugging and narrow down the problem. It would be be helpful if u could give some suggestions.

Meanwhile could you confirm, if DFU/OTA implementation is possible in beacon.

Thank you.

RE: Implementing DFU OTA for beacon

Petter Myhre — Mon, 11 Sep 2017 11:28:31 GMT

I'm sorry, but you need to provide some more information. Have you followed this? Are you seeing the DFU service in nRF Connect?

RE: Implementing DFU OTA for beacon

arjun — Mon, 11 Sep 2017 11:08:20 GMT

For understanding, I tried adding dfu feature to the ble_template project which already has device manager code in it. I added the dfu code snippet as in hrs_example, but it is not displaying dfu icon in nrfConnect.

RE: Implementing DFU OTA for beacon

Petter Myhre — Mon, 11 Sep 2017 11:00:19 GMT

Then you need to add the DFU service, and you need to connect for the peer to be able to access this service, and tell the device when to go to bootloader mode. (Device Manager is not needed as long as you will not bond)

RE: Implementing DFU OTA for beacon

arjun — Mon, 11 Sep 2017 10:48:23 GMT

I am trying to implement buttonless dfu.

RE: Implementing DFU OTA for beacon

Petter Myhre — Mon, 11 Sep 2017 10:42:55 GMT

It depends a bit, how do you intend to switch from beacon application to bootloader? By pressing a button or similar? Or some other way?

RE: Implementing DFU OTA for beacon

arjun — Mon, 11 Sep 2017 10:24:52 GMT

The things I need to clear are following :

1.In the hrs example code, the peripheral is in non-beacon mode. So it it needs to be disconnected/shutdown and connect/start in bootloader mode. Since in the beacon mode, there is no need for connect/disconnect, is device manager relevant code snippets necessary.

2.Is the tutorial given for extending dfu to the application is generic or is it exclusive for peripherals in non-beacon mode.

Thank you..

RE: Implementing DFU OTA for beacon

Petter Myhre — Mon, 11 Sep 2017 10:16:47 GMT

What is it that is not clear? Exactly what snippet are you talking about?