DFU OTA on a custom board using nrf51 DK board

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Mon, 15 May 2017 12:46:31 GMT

To me it sounds like that the nRF Toolbox/ nRF Connect app is not able to connect to the device after the application has branched to the bootloader. Once you try do connect again, the device is in bootloader mode and the DFU will go through.

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Fri, 12 May 2017 14:41:47 GMT

Yes my all updates done successfully in odd numbers like 1th trial, 3rd trial, 5th trial..

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Fri, 12 May 2017 14:16:23 GMT

Are all updates after the third update sucessful?

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Fri, 12 May 2017 05:00:35 GMT

I am trying with the both multiple files or same files. But result is same.

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Tue, 09 May 2017 10:56:07 GMT

Have you tried performing the same application update multiple times after the third successful update? Does all of them succeed or do you see one of the updates failing?

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Fri, 05 May 2017 14:54:24 GMT

Hello Sir,

Now i had done OTA in both nrf51DK board and custom board.

For my custom board, something happened new. When i burn both soft device and boot loader successfully my custom board advertised "DFUtarg" when i update my app.hex then it's changed as per my app.hex file.

Now when i tried to second time to update my app.hex file its shown error message "DFU update failed" and suddenly advertised again "DFutarg".

Or when i tried to update third time my app.hex file then its update successfully. Means First time OTA done successfully second time not and again third time done successfully.

I don't know where i am making mistake.

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Tue, 02 May 2017 14:29:43 GMT

Have you added DFU support to your application, see this Infocenter page. You need to add support for buttonless DFU, see this page, if you do not want to put the device in bootloader mode manually by pressing a button on the board.

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Tue, 02 May 2017 13:36:32 GMT

Hello Sir,

Thank you for your response.

This is my Application file setting Xtal (MHz) -- "16.0" Operating system -- "None" ARM Compiler -- "Use default compiler version" Read/Only Memory Areas -- IROM1 (box is checked) Start-- "0x1B000" Size -- "0x25000" Startup (circle is checked) Read/Write Memory Areas -- IRAM1 (box is checked) Start -- "0x20002080" Size -- "0x5F80"

and this is my bootloader setting Xtal (MHz) -- "16.0" Operating system -- "None" ARM Compiler -- "Use default compiler version" Read/Only Memory Areas -- IROM1 (box is checked) Start-- "0x3C000" Size -- "0x3C00" Startup (circle is checked) Read/Write Memory Areas -- IRAM1 (box is checked) Start -- "0x20002C00" Size -- "0x1380" IRAM2 (box is checked) Start --"0x20003F80" Size -- "0x80".

Using this setting i can done successfully OTA update with SDK11.

But when i trying to second time to update the my program i will stuck on starting bootloader message or if i am update the same file on nrf51DK. it is updated successfully.

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Tue, 02 May 2017 10:36:26 GMT

The IROM1 size must be set to that there is room for the bootloader, i.e. IROM1 size = BOOTLOADER_START_ADDRESS - APPLICATION_START_ADDRESS = 0x3C000 - 0x1B000 = 0x21000.

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Mon, 01 May 2017 12:26:49 GMT

Hi,

Please suggest what are the setting require into the keil to degug bootloader in my nrf51822QFAA like Read/Only Memory Areas -- IROM1 (box is checked) Start, size, IRAM1 and IRAM2.

My keil compiller shows me: Parsing hex file. Reading flash area to program to guarantee it is erased. Checking that the area to write is not protected. Programing device.

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Sat, 29 Apr 2017 09:51:06 GMT

Hi,

Today i tried one another activity as per below. First i erase all and then program dfu_test_softdevice_b_s130.hex available in SDK11 using nrfgo studio then download my app.hex using keil.

Now custom board start advertising as per my app.hex. It means my app.hex is successfully transferred into the custom board. But when i am trying update my app.hex file using mobile app, it continuously showing the message starting boot loader and connecting or after few seconds automatically disconnected.

My keil setting is Target: Xtal (MHz) -- "16.0" Operating system -- "None" ARM Compiler -- "Use default compiler version" Read/Only Memory Areas -- IROM1 (box is checked) Start-- "0x1B000" Size -- "0x25000" Startup (circle is checked) Read/Write Memory Areas -- IRAM1 (box is checked) Start -- "0x20002080" Size -- "0x5F80"

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Thu, 27 Apr 2017 12:46:45 GMT

If your application is based on SDK v11.0.0 then I assume that it uses S130 v2.0. and its not compatible with S110 v7 and the SDK v6.1 bootloader. You need to flash the S130 v2.0 SoftDevice to your board, if you get a read error, then I suggest that you download the S130 v2.0. from here and use that hex file instead.

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Thu, 27 Apr 2017 12:30:48 GMT

No my application is based on SDK11.0.0.

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Thu, 27 Apr 2017 12:29:25 GMT

Is your application(aap.hex) based on SDK v11.0.0 or SDK_v6.1.0?

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Thu, 27 Apr 2017 12:26:25 GMT

First i erase the chip using nrfjprog.exe(nrfjprog --eraseall) then burn softdevice(s110_nrf51822_7.0.0_softdevice) using nrfgo studio. After that open nrf51_sdk_v6_1_0_b2ec2e6\nrf51822\Board\nrf6310\device_firmware_updates\bootloader\arm file in keil build and download the bootloader.

After that my custom board itself advertised "DFUtarg" but my aap.hex is not transferred successfully just process is completed 100%.

Also i am trying to burn test softdevice and bootloader of SDK11 which i have used previously but in that my nrfjprog give me above mentioned error.

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Thu, 27 Apr 2017 12:17:12 GMT

Are you using nRFGoStudio instead of nrfjprog to flash the SoftDevice and bootloader to your module? Have you tried flashing only the SoftDevice and the Application? Are you able to debug your application in Keil after you have flashed it to your module?

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Thu, 27 Apr 2017 12:05:46 GMT

Hello sir,

As per your advise i am trying to burn soft device and boot loader using nrfjprog.exe but when i tried to do that its gives me error of "The file specified could not be open for read" .

Also i am trying with nrf5 SDKv6.1.0 and i had done to burn soft device and boot loader. Now my custom board advertised itself "Dfutarg" but when i tried to OTA with app.hex file using mobile app then transferred process is done 100% but now any success message is shown. Also my application is not transferred successfully.

But same file is transferred successfully in nrf51Dk board. I had done all above values changes of (nrf_clock_lf_cfg_t clock_lf_cfg = NRF_CLOCK_LFCLKSRC)in my code as per your suggestion.

Any other changes will be require in my code or in keil?

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Fri, 21 Apr 2017 14:56:27 GMT

You have to connect a J-Link programmer or nRF5x DK to the SWD interface and then use nrfjprog in order to flash the Softdevice and bootloader.

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Fri, 21 Apr 2017 14:44:49 GMT

Ok, I will do it. And how to burn softdevice and bootloader in this module?

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Fri, 21 Apr 2017 14:34:43 GMT

If you're using SDK v11.0.0, then you have to change the NRF_CLOCK_LFCLKSRC define which used in ble_stack_init in main.c

nrf_clock_lf_cfg_t clock_lf_cfg = NRF_CLOCK_LFCLKSRC;

Go to the definition in pca10028.h and change it to

#define NRF_CLOCK_LFCLKSRC      {.source        =NRF_CLOCK_LF_SRC_RC,            \
                                 .rc_ctiv       = 16,                                \
                                 .rc_temp_ctiv  = 2,                                \
                                 .xtal_accuracy = 0}

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Fri, 21 Apr 2017 14:12:15 GMT

Thank you for the your valueable inputs. i am doing this in keil using SDK11. i already done this in nrf51 DK board. Can you please suggest me how to activate OTA in this module using SDK.

I don't how is it possible same thing in this module

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Fri, 21 Apr 2017 14:02:43 GMT

Yes, you have change the clock source to the internal RC oscillator in your mBed code. I am not familiar with mBed and how this is done in their library, but this appears to be useful.

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Fri, 21 Apr 2017 13:52:21 GMT

Yes i am using same module with the keil code which i used for nrf51 DK board. Now, for OTA update in this module i am tried to same process which i followed in nrf51 Dk board. first i am erase all on chip then burn softdevice and bootloader file using nrfconnect application but after successfully burn the softdevice and bootloader its advtise DFUTESt but if i doing same process in this module its not happened.

Can you suggest me how to activate DFU in this module using keil or mbed?

RE: DFU OTA on a custom board using nrf51 DK board

bjorn-spockeli — Fri, 21 Apr 2017 13:42:52 GMT

If it this module you're using, then I can see that it does not have a 32kHz crystal. You have change the clock source to the internal RC oscillator in your mBed code

RE: DFU OTA on a custom board using nrf51 DK board

Nilesh Bhavsar — Fri, 21 Apr 2017 13:05:29 GMT

Hi,

I apologize for the late response due to some other technical emergency.

i am using RL51822 A1 module and I don't know how to identify that external crystal is available or not in that. But module has nrf51822QFAA type chip and its having external crystal of 32KHz.

Also i am trying to build application file downloaded from mbed compiler using nrf51 Dk then it's done successfully. or i connect this module using nrf51 Dk through in nrfConnect app. then also it shows me that board successfully and done all the thing like erase, program softdevice and bootloader. but the actual effect is not shown by my module like when i burn same bootloader abd softdevice in nrf51 Dk board then it's advtise DFUTEST but my custom module not.