Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

etienne — Fri, 07 Apr 2017 14:36:15 GMT

@kamisen sorry for the delay... We find out that the compiler options in release -Ofast -flto -ffat-lto-objects break the DFU OTA process. What we did, is to build the nano_ecc with the same compiler options as in the sdk example and then we replaced the release options only with -0s. BTW we use the SDK 12.2.0

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

kamisen — Fri, 07 Apr 2017 14:20:15 GMT

@etienne "by checking and fixing the compiler optimisation flag for the nano_ecc library", any detail?

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Mon, 03 Apr 2017 10:34:40 GMT

@etienne: Could you post the changes you had to do in the comment section?

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

etienne — Mon, 03 Apr 2017 09:13:12 GMT

Hi sananth, like i said it before we had the same issue. What i forgot in my last comment, was to mention that we also fixed it by checking and fixing the compiler optimisation flag for the nano_ecc library...

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Mon, 03 Apr 2017 08:04:49 GMT

@kamisen: I will follow your question and work on the issue with Hung. I would appreciate if we could move the conversation to that thread.

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

kamisen — Fri, 31 Mar 2017 14:47:36 GMT

devzone.nordicsemi.com/.../ here is my post

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Fri, 31 Mar 2017 14:17:09 GMT

@kamisen: Which WDT interval are you using?

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

kamisen — Sat, 25 Mar 2017 08:54:22 GMT

I met the same question. But even I reloading the WDT in the bootloader main before nrf_bootloader_init was called, the twice DFU situation happen again. Have you solved this issue?

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

etienne — Tue, 07 Mar 2017 16:30:51 GMT

hi sananth, we had exactly the same issue... when we reloaded the WDT in wait_for_event & nrf_dfu_wait in nrf_dfu.c after configuring and enabling it on the App side. Changing the timeout did not change anything. But only reloading the WDT in the bootloader main before nrf_bootloader_init was called, fixes the issue.

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Wed, 23 Nov 2016 09:15:40 GMT

If there is only the SoftDevice and the bootloader present, then you should not reach nrf_bootloader_app_start in nrf_dfu.c. If you read the bank 0 code at 0x0007F020 it should be 0x00000000. After the DFU of the applications it should be set to 0x00000001 and the nrf_dfu_app_is_valid check should return true.

 if (nrf_dfu_app_is_valid())
    {
        NRF_LOG_INFO("Jumping to: 0x%08x\r\n", MAIN_APPLICATION_START_ADDR);
        nrf_bootloader_app_start(MAIN_APPLICATION_START_ADDR);
    }

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

sananth — Tue, 22 Nov 2016 15:47:46 GMT

From a clean start (e.g. just soft device and bootloader running in debug mode), it does reach that line and execute it. I left the bootloader on debug and try to reload again and the phone acts as if the app was successfully loaded yet that same line in code is never reached. I try again, and it reaches that line. So essentially every other time it reaches that nrf_bootloader_app_start line.

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Tue, 22 Nov 2016 15:36:43 GMT

I checked the "Not working hex file" and the dfu settings bank_0 code is set to NRF_DFU_BANK_VALID_APP, i.e.

 0x0007F020: 00000001

This means that the bootloader should reach nrf_bootloader_app_start in nrf_dfu.c (should be at line 143 in nrf_dfu.c). Could check this by debugging the bootloader?

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

sananth — Tue, 22 Nov 2016 15:26:04 GMT

Hi Bjorn

I ran the above line twice. Once when things load properly (here is the output):

Working Hex file

And when things don't (here is the file):

Not working hex file

I used a hex file comparator and the working one has values in place where the not working one has 0xFF

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Tue, 22 Nov 2016 14:40:05 GMT

If you debug the bootloader after the DFU, does it reach nrf_bootloader_app_start in nrf_dfu.c (should be at line 143 in nrf_dfu.c)? If so, could you try to debug the application? Lastly, could you read back the flash after a failed DFU to a file and attach it to the question? You can read back the flash and store it to a file using the following command.

nrfjprog -f nrf52 --memrd 0x00000000 --n 524288 >> hex_dump.txt

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

sananth — Tue, 22 Nov 2016 14:27:39 GMT

Hi Bjorn,

We start/setup the watchdog right before we enter the

for (;;)
{
    app_sched_execute();
    UTIL_kickWatchdog();
    APP_ERROR_CHECK(sd_app_evt_wait());
}

It is hard to pinpoint when the failure occurs. We currently have an led that is one during the bootloader phase. It most likely is happening at the end of the bootloading (or at least that is my guess). As when it works the led blinks really quickly and shuts off. Versus when it doesn't work the led goes off and within a second is back on. All signs on the nordic phone app make it seem like it correctly boot loaded.

Do you have an suggestions on what to try to debug this better? So I can provide more info

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Tue, 22 Nov 2016 13:16:02 GMT

I've done some testing with the bootloader where I initialize and start the WDT right after entering main(). I am not seeing any issues with a WDT timeout interval of 2 seconds, so I do not think you should be breaking any timing requirements in the bootloader. When does the failures occur? I would expect that you sometimes could run into some issues as the device is jumping from application mode to bootloader mode, i.e. if you jump at the end of the WDT interval in the application then the WDT might expire before you reach the wait_for_event() loop.

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

sananth — Mon, 21 Nov 2016 19:53:13 GMT

Hi Bjorn

I added what you recommend to the code, but it still fails sporadically. when the WDT has a timeout of 2000.

Any suggestions?

Thanks again for your help!

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Mon, 21 Nov 2016 12:48:55 GMT

Could you try to feed the WDT in the location suggested by this post?

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

sananth — Thu, 17 Nov 2016 16:32:14 GMT

I've zipped both the DFU and nrf5_Sdk folders but they might be too large too attach so have used a link to a google drive folder...attached zipped files

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Thu, 17 Nov 2016 15:34:23 GMT

Ok, if you have set ble_enable_params.gatts_enable_params.service_changed = 1; then you should be O.K. Have you done the same in the application? Hmm, I dont see why the WDT should only fire every other time. Can you attach the bootloader project to your quetion so I can test it?

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

sananth — Thu, 17 Nov 2016 14:11:59 GMT

Hi Bjorn,

Thanks for the response, it is set to 0.

#define SOFTDEVICE_GATTS_SRV_CHANGED   0

but we have

ble_enable_params.gatts_enable_params.service_changed = 1;

Also we have experimented with increasing the timeout on the WDT and things work fine with these settings:

#ifndef WDT_CONFIG_BEHAVIOUR
#define WDT_CONFIG_BEHAVIOUR 0
#endif

// <o> WDT_CONFIG_RELOAD_VALUE - Reload value  <15-4294967295> 


#ifndef WDT_CONFIG_RELOAD_VALUE
#define WDT_CONFIG_RELOAD_VALUE 5000
#endif

What we are worried about is if the WDT_VALUE is set to 2000 it works only every other time. We don't want to set the config value to something large as we need the WDT timeout to be shorter for the main application. We aren't sure why the WDT is firing every other time. I added the NRF_WDT->RR[0] = WDT_RR_RR_Reload; in the DFU in the wait_for_event() loop as recommended by this forum...

       NRF_WDT->RR[0] = WDT_RR_RR_Reload; //ADDED
       app_sched_execute();
       NRF_WDT->RR[0] = WDT_RR_RR_Reload; //ADDED

RE: Using the DFU SDK 12.1 with a BLE command to jump to 'bootloader' works every other time with nordic connect app

bjorn-spockeli — Thu, 17 Nov 2016 09:30:41 GMT

Is the SOFTDEVICE_GATTS_SRV_CHANGEDdefine in softdevice_handler.c set to 1, i.e. #define SOFTDEVICE_GATTS_SRV_CHANGED 1 ?