DFU OTA issue on NRF51822AA

RE: DFU OTA issue on NRF51822AA

JamesPan — Fri, 04 Mar 2016 09:33:36 GMT

It's big help for me. Many thanks. How do you know or where are the instructions for the two initial parameters:SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION, true); and SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_2000MS_CALIBRATION, false);

RE: DFU OTA issue on NRF51822AA

Hung Bui — Mon, 08 Jun 2015 11:01:26 GMT

@sidekick: I'm sorry that I forgot to check if you may not have the 32kHz crystal. Do you have that in your custom board ? If you don't you would need to do the same modification on the application firmware as well.

RE: DFU OTA issue on NRF51822AA

sidekick — Fri, 05 Jun 2015 09:03:52 GMT

Update: Finally managed to successfully perform DFU-OTA :) Modified ble_stack_init routine in bootloader to use LFCLK RC oscillator, 250ms calibration interval. i.e.

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION, true);

and ble_stack_init() routine in application:

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_2000MS_CALIBRATION, false);

Rest of the steps were the same as mentioned in my last comment (except that I used .hex file instead of .bin). reference: this thread.

RE: DFU OTA issue on NRF51822AA

sidekick — Thu, 04 Jun 2015 12:58:55 GMT

Another DFU-OTA attempt:

Restarted both cellphone and our custom board
Use nRF Toolbox mobile app from Nordic (v 1.3.1 for samsung S3, android v4.3) to flash application.
Select our custom board as the device which is now advertising as "DFU Targ" (I must say that it is very unstable, i've to do multiple scans from nRF Toolbox to even find our custom board)
Select .bin file (generated using fromelf.exe, application.bin file size ~29kB) from internal storage (Instead of uploading file from Google drive)
No init (.dat file)
Upgrade

Result: GATT ERROR or DFU SERVICE NOT FOUND ERROR

RE: DFU OTA issue on NRF51822AA

sidekick — Thu, 04 Jun 2015 12:00:19 GMT

Reached text size limit in my previous post, hence continuing here. Steps this time:

Erased all (using nrfjprog.exe --eraseall)
Program SD ( s110 v7.1.0) using nRFgo Studio
Flash bootloader. Using KEIL uVision, J-link and nrfjprog.exe
Use nRF Toolbox mobile app from Nordic (v 1.3.1 for samsung S3, android v4.3) to flash application.
Select our custom board as the device which is now advertising as "DFU Targ"
Select .hex file (size ~82kB) from Google drive
No init (.dat file)
Upgrade

Result: DFU FILE ERROR (2)

RE: DFU OTA issue on NRF51822AA

sidekick — Thu, 04 Jun 2015 11:40:00 GMT

Thank you Hung Bui for following up on this. As I'm reading more about DFU-OTA, my issue is turning multifaceted.

I'm not using nRFgo Starter Kit (No button #7 as mentioned here) to go into bootloader mode, it's a custom board and has nrf51822QFAA SOC.
Cannot use Experimental, sample PC applications*(~/\ble_dfu_send_hex/*) to perform device firmware update as I do not have Master Control Panel dongle. Initially I wanted, SD + Bootloader + App on our custom board and perform application upgrade later, but as I've understood so far, I've to implement a logic using GPREGRET register, both in Bootloader and in our application. So currently, just to test DFU, I should not write 0x01 to 0x00003fc00 and try only with SD and Bootloader.

RE: DFU OTA issue on NRF51822AA

Hung Bui — Thu, 04 Jun 2015 09:34:42 GMT

@sidekick: It's my mistake in the presentation. As shown here the init packet is optional. I will update the slide. Sorry about that.

Could you explain why you want to write 0x01 to 0x00003fc00 ?

With nRFLogger, after you have done a DFU session in nRFToolbox, you should see the log in the logger app. You can also try to use nRF Master Control Panel to do DFU. You can swipe right when doing it to see the log.

To be able to open a file on your phone, you can try to install a File manager app. There are several of them on Goolge Play.

Which phone did you use to test ?

RE: DFU OTA issue on NRF51822AA

sidekick — Wed, 03 Jun 2015 15:24:49 GMT

Is this documentation on BLE DFU-OTA for SD v7.X.X up to date ? If yes, where can I find the experimental sample PC applications as mentioned in this tutorial ? I've nRF 51822QFAA (256 kB flash) chip on our custom board.

RE: DFU OTA issue on NRF51822AA

sidekick — Wed, 03 Jun 2015 14:27:01 GMT

Update: This time I Used ".bin" file (Used fromelf.exe which is part of ARM toolchain) to generate .bin file and also renamed the .bin and .dat file as application.bin and application.dat (nRF Toolbox app suggests naming them as application.(bin|hex|dat). My .dat file contents are (As seen in sublime 3 editor) is: "ffff ffff ffff ffff 0100 feff f109 ") and invoking crc.exe on application.bin generated following: (shown here CRC value for 0xffff seed only)

CRC-CCITT (0xffff) = 0x09F1 / 2545

Steps:

Erased all (using nrfjprog.exe)
Program SD using nRF Studio
Flash bootloader. Using KEIL uVision, J-link and nrfjprog.exe
Write 0x1 at the address 0x00003fc00 using nrfjprog.exe

Device is advertising as "Dfu Targ". Trying to flash application.bin using nRF Toobox app now gives DFU SERVICE ERROR (6) and a re-attempt gives DFU GATT INTERNAL ERROR(129) :(

RE: DFU OTA issue on NRF51822AA

sidekick — Wed, 03 Jun 2015 08:07:21 GMT

@Hung Bui: Init packet wtih SDK V6.1 is compulsory (as mentioned in the video here @4:03). In my phone(Android version 4.3), when I try to add the file, I am given only two options; either to use my google drive or Dropbox to locate the file. Probably it's because, I do not have Android version 4.4 on my phone as mentioned in this external link. Meanwhile, I've also installed nRFLogger on my phone, but I'm not sure, how to use it. I also tried to supply a init file to nRFToolbox during application upload (.dat file by following the link I posted before), but I still get the same "DFU File Error (2)" error message. What does this error stands for? This same error I'm getting in nRFToolbox (with or without .dat file).

RE: DFU OTA issue on NRF51822AA

Hung Bui — Tue, 02 Jun 2015 19:51:21 GMT

@Pektusin: What stated in nRFToolbox was correct. You don't need init packet for bootloader in SDK v6.1.

I am testing here with no problem. Which hex file did you use ?

Could you try with the hex file comes with the nRFToolbox located in NordicSemiconductor\board folder on your phone ?

Could you install nRFLogger and find the log file of the update process (DEBUG log) and post here ?

RE: DFU OTA issue on NRF51822AA

sidekick — Tue, 02 Jun 2015 13:21:12 GMT

I tried option 2:

Flash SD using nRFGo Studio (v1.18.0.9)
Flash Bootloader using nrfjprog.exe
Flash the application using KEIL uVision (no external flash utility)
Program BANK_VALID_APP(nrfjprog.exe --memwr 0x0003fc00 --val 0x1) to 0x01
Restarted our custom board

Now the application is running fine. So far so good. Now when I tried to use nRF Toolbox Application for Android cellphones for DFU-OTA (there is a DFU profile in nRF toolbox application), It asked for .hex and .dat file. I selected "No" for .dat file and the Firmware upgrade failed with Error code (2). According to this thread, .dat file is compulsory for SDK version v7.0 or v7.1, but I'm using SDK v6.1.0 (nrf51_sdk_v6_1_0_b2ec2e6) and Soft device version s110, v7.1.0. Do I still need to use the .dat file.

RE: DFU OTA issue on NRF51822AA

sidekick — Tue, 02 Jun 2015 07:28:52 GMT

Thank you Pektusin, While I go through the link that you have mentioned, I'd like to inform you that, meanwhile I also tried to use "nrfjprog.exe" to program the bootloader (In Keil uVision, selected by "Project -> option for Target XYZ -> Utilities -> Use External tool for flash programming"), SD using nRFGo Studio and the application again using KEIL uVision but, without using any external tool for flashing, but the result was same :(

RE: DFU OTA issue on NRF51822AA

Pektusin — Mon, 01 Jun 2015 17:32:10 GMT

If you're flashing all three parts using Jlink, it won't work as is. When starts, bootloader checks BANK_VALID_APP variable that is not set in your case. You have few options:

Flash SD and bootloader, and write your app over DFU - bootloader will handle BANK_VALID_APP for you.
After flashing SD, bootloader and the app, manually program BANK_VALID_APP to 0x01
Flash SD and your app only. Your app will start, but DFU obviously won't work without the bootloader.

More details: devzone.nordicsemi.com/.../