dfu service not getting discovered

RE: dfu service not getting discovered

Hung Bui — Wed, 01 Apr 2015 12:25:31 GMT

@komal: If you have the bootloader setup correctly, the 0x10001014 address should be written automatically when flashing the bootloader hex file. I'm afraid that all the solutions I have for now for you is either:

Use the SDK v6.0 gcc bootloader that provided here.
Use Keil (free version) to compile the bootloader on SDK v6.1 or later. You will have the same file as the bootloader.hex file I provided earlier and you can modify it.

I can get back to make an example for bootloader SDK v6.1 to be compiled on gcc when I have more time. It's pretty limited workforce in our team now due to Easter holiday.

RE: dfu service not getting discovered

komal — Wed, 01 Apr 2015 08:43:36 GMT

i have written the start addr of bootloader to 0x10001014 manually using nrfjprog using this command:- nrfjprog --memwr 0x10001014 --val 0x00035000.

But as i discussed before why my services are not getting discovered completely 2nd tme for dfu i.e. when i jump from my application to bootloader.

RE: dfu service not getting discovered

Hung Bui — Wed, 01 Apr 2015 08:06:11 GMT

@komal: Please double check, if you program the bootloader using nRFGo Studio or nrfjprog, you should see the bootloader region in the memory layout in nRFGo Studio. Or you can use nrfjprog to read out the uicr and check if address 0x10001014 is written.

Testing the bootloader_gcc.hex file I don't see that, and 0x10001014 = 0xFFFFFFFF.

RE: dfu service not getting discovered

komal — Tue, 31 Mar 2015 13:26:11 GMT

yes i have the section reserved for NRF_UICR_BOOT_START_ADDRESS in my gcc_nrf_51_bootloader_xxaa.ld file, as well as i have set it in bootloader_util_gcc.c file.

RE: dfu service not getting discovered

Hung Bui — Tue, 31 Mar 2015 12:56:05 GMT

@Komal: I'm checking the bootloader you provided, I can't find the part where NRF_UICR_BOOT_START_ADDRESS (0x10001014) is written at the end of the hex file. It's where the address of the bootloader is written, in your case it is 0x35000.

Have you made sure you have the code to set the address for bootloader in UICR in bootloader_util_gcc.c , similar to what we have here.

And you have the section are reserved for it in gcc_nrf_51_bootloader_xxaa.ld as we have here ?

RE: dfu service not getting discovered

komal — Tue, 31 Mar 2015 05:52:11 GMT

bootloader_gcc.hex ble_app_hrs_s110_xxaa.hex

i have uploaded my hex files. could u plz try with the hex files which i have provided.

tried with fresh sdk without doing any modifications, still facing the same issues. how do i compile my bootloader code in eclipse?

RE: dfu service not getting discovered

Hung Bui — Mon, 30 Mar 2015 17:04:56 GMT

@komal: it's hard to tell what went wrong here. How do you compiled the code ? Could you try to do a fresh install of the SDK and try to compile the bootloader without any modification ?

RE: dfu service not getting discovered

komal — Mon, 30 Mar 2015 05:38:47 GMT

i tried with ur hex files. they are working properly i.e while 2nd tme firmware update they dont get disconnected. in my code i have handled the BLE_GATTS_EVT_SYS_ATTR_MISSING event properly but still facing the same issue.

Tried to enter bootloader with the help of BUTTON. yes, can update the firmware succefully 2nd tme also with BUTTON, as when i hold the BUTTON while resetting the chip, it ernters into bootloader mode and the further firware update takes place successfully.

But BUTTONLESS i cant update the firmware 2nd tme, as per the functionality provided by your hex files.

Where am i going wrong?

RE: dfu service not getting discovered

Hung Bui — Fri, 27 Mar 2015 15:38:05 GMT

@komal: could you please try the hex files I provided ?

RE: dfu service not getting discovered

komal — Fri, 27 Mar 2015 11:03:29 GMT

i have used ....\Nordic_SDK\nrf51_sdk_v6_1_0_b2ec2e6\nrf51822\Board\nrf6310\s110\ble_app_hrs project which has dfu support in it. the board i used is pca10001(changed the nrf6310 board code to pca10001board ). the ide i am using is eclipse with arm-none-eabi gcc. so i have include bootloader_util_gcc.c file for the start application. rest all is the same.

RE: dfu service not getting discovered

Hung Bui — Fri, 27 Mar 2015 10:23:09 GMT

@kormal: From the log it seems that services discovery of DFUtag if not completed, a read request for handle 0x000E is not responded. This happens if the CCCD value has not been set. Usually when BLE_GATTS_EVT_SYS_ATTR_MISSING has not been handled properly.

I have attached in my answer my bootloader hex file and the ble_app_hrs_dfu. Could you try to test using the hex files ? (Note: make sure you erase the whole chip before you flash the new bootloader)

As you can find in the bootloader source code if BUTTON7 (Pin P0.07) is hold when reseting the chip, it will enter bootloader mode. Could you try that and update the firmware using your bootloader?

RE: dfu service not getting discovered

komal — Thu, 26 Mar 2015 10:39:04 GMT

i have attached the logfile. With BOOT button i haven't not done firmware update yet. logfile.txt

RE: dfu service not getting discovered

Hung Bui — Thu, 26 Mar 2015 10:12:53 GMT

@komal: It's pretty strange issue. Because you can update the ble_app_hrs_dfu the first time without problem, why didn't it work the second time. Could you provide the Master Control panel log. You can get the log by selectin File -> Log File.

Do you have the same issue if you enter bootloader by holding the BOOT button instead of entering if by writing to the DFU control point ?

RE: dfu service not getting discovered

komal — Thu, 26 Mar 2015 08:37:58 GMT

no. this is not the issue i am facing. When I write 1 to the DFU Control Point, link loss takes place. Then i click back, the do start discovery and the dfutarg gets advertised. Then i do service discovery, then services get discovered and i get link loss. that means 2nd tme i cant update my firmware.

RE: dfu service not getting discovered

Hung Bui — Wed, 25 Mar 2015 13:50:22 GMT

On newer SDK (where you have to update the python code in ble_dfu_send_hex\dfu into C:\Program Files (x86)\Nordic Semiconductor\Master Control Panel\3.7.1.8567\lib\dfu) such as SDK v7.1 the Master Control Panel can do update seamlessly from the dfu buttonless application.

RE: dfu service not getting discovered

Hung Bui — Wed, 25 Mar 2015 13:49:44 GMT

@komal: Let me sum up the issue you are having, please correct me if I am wrong:

You can program the bootloader, and can use the bootloader to update application (HRM with DFU)
When you write 1 to the DFU Control Point, you got a link loss. The link got disconnected without any further DFU update.

This is normal behaviour. MCP v3.7 and SDK v6.1 doesn't support seamless DFU update from application to jump to bootloader and do update automatically. What you need to do is to click back, then do Start Discovery to see if the DFU is advertising, if it is advertising you can connect and do DFU. So 2 more step needed, click back and click start discovery to find the DFU bootloader advertising.

RE: dfu service not getting discovered

komal — Wed, 25 Mar 2015 09:43:52 GMT

i have attached the 3 files of mcp screen shot.

bootloader.png is the screenshot of normal bootloader.
application.png is the screenshot of application i.e ble_app_hrs with dfu support.
bootloader2.png is the screenshot of bootloader getting advertised through application after writing 0x0001 to cccd and 0x01 to control point of dfu service to put it into dfu mode. in this services are getting discovered, but after that getting disconneced.

bootloader.png bootloader2.png application.png

RE: dfu service not getting discovered

Hung Bui — Wed, 25 Mar 2015 09:03:54 GMT

@komal: I'm not sure why you need to use nrfjprog to manualy write the address to UICR. If you set it up correctly, with BOOTLOADER_REGION_START = 0x00035000, when you flash the bootloader .hex , the address will be written automatically.

Please let me know your further steps until you get the error.

If you couldn't take a sniffer trace, please send the Master Control panel log and screenshot.

RE: dfu service not getting discovered

komal — Tue, 24 Mar 2015 13:57:58 GMT

i erased full chip using nrfgo studio.
flashed softdevice v7.1.0
flashed bootloader.hex file using nrfjprog utililty also using command nrfjprog --memwr 0x10001014 --val 0x00035000(BOOTLOADER_START_ADDR) gave the starting address of bootloader.

RE: dfu service not getting discovered

Hung Bui — Tue, 24 Mar 2015 13:18:51 GMT

Hi Komal,

I'm seeing without optimization gcc compiler will generate the bootloader code size of 37kB on my setup. If you call make with target all, optimization level 3 will be used and I can see the code occupies about 17kB after compiling.

However, it's not the point here on why it doesn't work. I need to have the sniffer trace to be able to find if there is something wrong.

Also please list step by step of what you did when testing, what do you flash first, how do you flash application etc.

RE: dfu service not getting discovered

komal — Mon, 23 Mar 2015 05:23:31 GMT

I am using arm-none-eabi gcc compiler with eclipse ide.

FLASH (rx) : ORIGIN = 0x0003c000 , LENGTH = 0x3c00 with these memory setting in .ld it throws an error as

_build/bootloader_gcc.out section .text' will not fit in regionFLASH' region `FLASH' overflowed by 27788 bytes

RE: dfu service not getting discovered

Hung Bui — Fri, 20 Mar 2015 14:00:55 GMT

@Komal: It's strange that your have such a big size of the bootloader. Which compiler did you use ?

RE: dfu service not getting discovered

komal — Fri, 20 Mar 2015 13:12:06 GMT

i have modified the bootloader address because if i keep it unmodified and program my device then my device do not advertise the dfu. so i have given BOOTLOADER_REGION_START 0x00035000 and if i keep it 0x0003c000 den memory assigned to the bootloader is 16kb(but actual size of bootloader is 44k).

Where am i going wrong?

RE: dfu service not getting discovered

Hung Bui — Fri, 20 Mar 2015 12:42:37 GMT

@komal: Please edit your question when you want to attach files or picture.

Could you take a screeshot of the Master Control panel when you do service discovery and when you receive the error ? You may want to capture a sniffer trace to know what happens over the air.

I spotted that you modified the bootloader address. What happens if you use the un-modifed bootloader example in the SDK v6.1 ?

RE: dfu service not getting discovered

komal — Fri, 20 Mar 2015 12:16:39 GMT

Yes i have flashed the bootloader code first. And the error i am getting after using mcp v3.71 is, it gets hanged while uploading firmware at 0% only. i have attached the screen shot of the layout of memories.

nRFgoStudio layout.png