DFU service Enable in proximitty code

RE: DFU service Enable in proximitty code

Murugan — Mon, 12 Sep 2016 13:09:59 GMT

DFU successfully implemented in proximitty code.Thanks for the support.

RE: DFU service Enable in proximitty code

Hung Bui — Mon, 12 Sep 2016 07:58:46 GMT

@Murugan: I'm afraid that I don't fully understand you. Could you please clarify if you still have any issue ? If you do, please let me know what exactly it is ?

RE: DFU service Enable in proximitty code

Murugan — Fri, 09 Sep 2016 06:32:39 GMT

Thanks for support . In my proximitty application code we can use

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(500, UNIT_1_25_MS) /< Minimum acceptable connection interval (0.5 seconds). */

#define MAX_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)**

RE: DFU service Enable in proximitty code

Rajneesh — Fri, 09 Sep 2016 06:25:25 GMT

change connection time interval in dfu_transport_ble.c file

RE: DFU service Enable in proximitty code

Rajneesh — Fri, 09 Sep 2016 06:23:30 GMT

Hi Murugan,

Please follow below link this will be your Answer of question : devzone.nordicsemi.com/.../

I think you should change connection interval time. I have also faced same issues but after changing interval time this was solved.

Regards, Rajneesh

RE: DFU service Enable in proximitty code

Murugan — Thu, 08 Sep 2016 16:26:20 GMT

In my question the main.c is not updated code. i am very sorry. Today i have to modify the code from This example. Then only DFU service is activated. My Previous code is not support for DFU service activation. Here is my modified code main.c. Once again i am sorry for not informing earlier.

RE: DFU service Enable in proximitty code

Hung Bui — Thu, 08 Sep 2016 14:30:06 GMT

@Murugan: I can see your activity here. Have you tried to test with the example provided here ?

It's the issue that the we made the DFU service for the device manager not the peer manager. The ble_app_hrs_with_dfu uses the device manager when the ble_app_proximity use peer manager.

So you will have trouble if you use the DFU service in your application without any modification. You would need to follow the example that my coworker made and apply the changes to the proximity example.

RE: DFU service Enable in proximitty code

Murugan — Thu, 08 Sep 2016 14:15:13 GMT

Please check this screenshot

Screenshot_20160908-194117.png

RE: DFU service Enable in proximitty code

Murugan — Thu, 08 Sep 2016 14:06:01 GMT

The softdevice and bootloader are already upload through nrf go studio.

Mobile app cant show the error. Repeatedly showing below process

Connecting........
Starting DFU........
starting bootloader ........

RE: DFU service Enable in proximitty code

Murugan — Thu, 08 Sep 2016 13:53:06 GMT

I am using central device my android mobile (android v6.0). Used SDK11.0 tested with example in nrf51 DK. Example codes are working fine. used Bootloader dual_bank_ble_s130.

As per the document DFU service is successfully enabled and checked my mobile APP.

RE: DFU service Enable in proximitty code

Hung Bui — Thu, 08 Sep 2016 13:43:39 GMT

What kind of error do you have when doing that ? Which central device did you use to test ? Which SDK version did you use, which Softdevice was that ?

Have you flashed the bootloader ? Have you tested just the bootloader to update your application ? You need to know how to use the bootloader before you integrate DFU service into your application.

Have you tried to test with our example in the SDK , the \examples\ble_peripheral\ble_app_hrs\pca10028\s130_with_dfu for example. It's an example on how you implement DFU service into your application.

RE: DFU service Enable in proximitty code

Murugan — Thu, 08 Sep 2016 13:35:30 GMT

Thanks for support.

when i am going to upload image file using DFU in my android app blow process repeated

Connecting........
Starting DFU........
starting bootloader ........ I dont know what i am doing wrong.

RE: DFU service Enable in proximitty code

Hung Bui — Thu, 08 Sep 2016 13:30:45 GMT

@Murugan: Please be specific and describe your issue clearly, what didn't work, how did you test , etc. Otherwise we can't help.