I have used sofdevice v7.1.0 and nrf51 sdk 6.1.0 the ble_app_hrs project which has support of dfu is not discovering the dfu services. i have enabled the BLE_DFU_APP_SUPPORT flag , then also facing same issue.
I have used sofdevice v7.1.0 and nrf51 sdk 6.1.0 the ble_app_hrs project which has support of dfu is not discovering the dfu services. i have enabled the BLE_DFU_APP_SUPPORT flag , then also facing same issue.
@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 ?
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?
@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 ?
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.
@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.