DFU Update OTA of an application with ble secure bootloader works only once

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Wed, 13 Dec 2017 07:37:01 GMT

For us it works fine with the modification for this time. If I have the time, I try to debug the bootloader. So, we can close this item. Thank you for your help

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Tue, 12 Dec 2017 16:26:13 GMT

This time the board doesn't even advertise.

I don't think we are going any where trying back and forth like this. Most of our customers having no problem compile and do DFU with the stock bootloader.

Please try to debug the bootloader on your side. After you do a successful DFU, find why this check if(enter_bootloader_mode != 0 || !nrf_dfu_app_is_valid()) doesn't return false (so that application will be enterred).

We haven't got report that NRF_FSTORAGE_DEF caused the problem.

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Tue, 12 Dec 2017 14:10:01 GMT

Hi Hung, here is a new compiled and merged file without the modification. s132_V5.0.0_dfu_boot.hex

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Tue, 12 Dec 2017 12:24:13 GMT

Hi Boisi,

Could you clarify, the bootloader in the .zip file was with or without your modification ? It worked fine for me when testing here.

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Fri, 08 Dec 2017 07:42:23 GMT

Hi Hung, it should be the file without the patch ?!?! For me it seems like that the values are not set after a restart. Can you show me the source where the values normal initialize ?? I think that would be at startup (startup.S file) ???? Thank you for your help.

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Fri, 08 Dec 2017 07:29:59 GMT

Hi boisi,

With the bootloader in the .zip file it worked fine for me here. I can upload the image several times without any problem. Is it with or without the patch you made ?

Anyway, I don't think it would be a big problem with the modification you made. In the DFU use case there is only one fstorage user.

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Tue, 05 Dec 2017 10:37:11 GMT

Nordic_zip.zip

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Tue, 05 Dec 2017 10:34:53 GMT

Hi, here the zip with my files. Now I have a solution. I init the m_fs values (evt_handler, start_addr and end_addr) in the nrf_dfu_init_user function. Here the code in main.c :

/* @BS*/
#include "nrf_fstorage.h"
#include "nrf_dfu_types.h"
extern nrf_fstorage_t m_fs;
extern void dfu_fstorage_evt_handler(nrf_fstorage_evt_t * p_evt);

uint32_t nrf_dfu_init_user(void)/* call in bootloader.c */
{
    NRF_LOG_DEBUG("nrf_dfu_init_user");
    /* fs_data init */
    m_fs.evt_handler   = dfu_fstorage_evt_handler;
    m_fs.start_addr     = MBR_SIZE;
    m_fs.end_addr       = BOOTLOADER_SETTINGS_ADDRESS + CODE_PAGE_SIZE;

    return NRF_SUCCESS;
}

/**@brief Function for application main entry. */
int main(void)
{
   :
   :
}

With this init it works fine. But I don't understand if it's only a workaround or a necessary init ??? Where are the 3 values init after a new start of the eval board. After the programing the values are set. but after a restart they are not set.

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Tue, 05 Dec 2017 01:09:14 GMT

In my case it just rejects the DFU image, I can't even update once. Please try to zip all the file in one zip file and upload. You can create a new private (and public) key for testing if you don't want to expose your private key.

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Mon, 04 Dec 2017 07:48:50 GMT

template_CortexM_flash.ld

...sorry, but I can't upload the private.key file

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Mon, 04 Dec 2017 07:45:55 GMT

Hi Hung, I don't think that the private key is wrong. The first dfu is ok (with the image zip). I think in the ld script is the problem. here my key file and the ld script of the bootloader.

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Fri, 01 Dec 2017 23:11:31 GMT

Hi Boisi,

The s132_V5.0.0_dfu_boot.hex runs on PCA10040 DK but the image zip file is not accepted. Suspect that it was wrong private key. Could you also provide the private key file ?

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Wed, 29 Nov 2017 14:00:59 GMT

s132_V5.0.0_dfu_boot.hex

Here is the SD_V5.0.0 and the bootloader.hex files merged together. I only include my own key. I use Atollic True Studio to generate my files else I don't touch the example code. I program the hex file with:

nrfjprog -e
nrfjprog -r -f NRF52 --program s132_V5.0.0_dfu_boot.hex

After the first dfu I hold the button and start the Evalboard to enter the dfu mode again.

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Wed, 29 Nov 2017 13:49:56 GMT

I tried to flash your bootloader on a NRF52DK and it doesn't run. LED3 is lid but no advertising. What was your modification ? Is there any dependency that your bootloader only runs on the BMD300 ?

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Wed, 29 Nov 2017 12:44:40 GMT

Hi boisi,

This is pretty strange, and NRF_FSTORAGE_DEF() should not be removed as it define the boundary for the fstorage.

I tried here with \examples\dfu\bootloader_secure_ble\pca10040\armgcc\ and the ble_app_blinky in SDK v14.1 exactly as you described but I can do re-dfu update with no problem. How did you enter the DFU mode after you do the first DFU ?

Can you upload your bootloader.hex, your application.zip dfu file so that I can test here ?

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Wed, 29 Nov 2017 12:42:50 GMT

Here my workaround: In file nrf_dfu_flash.c

// original code //NRF_FSTORAGE_DEF(nrf_fstorage_t m_fs) = ......

// original code (decoded)
//nrf_fstorage_t m_fs attribute ((section( "." "fs_data"))) attribute((used)) = .....

// workaround code
nrf_fstorage_t m_fs =
{
.evt_handler = dfu_fstorage_evt_handler,
.start_addr = MBR_SIZE,
.end_addr = BOOTLOADER_SETTINGS_ADDRESS + CODE_PAGE_SIZE
};

I don't know why, but it works with this workaround.

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Wed, 29 Nov 2017 09:11:19 GMT

Here the update log file from my Phone (App nRF Connect)

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Wed, 29 Nov 2017 09:06:37 GMT

BMD300_Blinky-e.zip(/attachment/496c739eb238e719b34e1fce556dc6ec)

BMD300_DFU_BOOTLOADER.hex

Update_Log_Fail.txt

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Wed, 29 Nov 2017 07:28:31 GMT

I have found the reason of the error. The .evt_andler, .start_addr and .end_addr are not initialized (in file nrf_dfu_flash.c) at the second try. NRF_FSTORAGE_DEF(nrf_fstorage_t m_fs) = { .evt_handler = dfu_fstorage_evt_handler, .start_addr = MBR_SIZE, .end_addr = BOOTLOADER_SETTINGS_ADDRESS + CODE_PAGE_SIZE };

If I delete NRF_FSTORAGE_DEF it work fine (nrf_fstorage_t m_fs = .....).

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Tue, 28 Nov 2017 16:44:40 GMT

I would suggest you to test with other example to know how the log system works. Maybe with ble_app_hrs.

Please post the full log on the phone.

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Tue, 28 Nov 2017 13:36:24 GMT

I included the files and paths. Now I can compile but where can I see the debug info's ? Must I include the uart files ?

I think the error occurs in the fuction nrf_fstorage_erase at the aligned and boundary check. But I don't know why. At the first time I can debug and all is fine. At the secound time I can't debug it but I see the return values (send it to Smartphone App ;) ).

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Tue, 28 Nov 2017 13:17:46 GMT

When you turn on logging you needs logging files. Make sure nrf_log_frontend.c is included and components\libraries\experimental_log\src\ include path is included.

Bootloader setting is a normal flash page and can be erased.

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Mon, 27 Nov 2017 12:51:37 GMT

If I turn on the NRF_LOG_ENABLE following errors occurs [undefined reference to `nrf_log_frontend_std_0'....]

I think the problem is that the bootsetting page can not be erased ?!?!?

RE: DFU Update OTA of an application with ble secure bootloader works only once

Hung Bui — Mon, 27 Nov 2017 12:38:06 GMT

@boisi: have you tried to change the application version when you create the zip file ? try to increase application version by one. There is a chance the the bootloader reject uploading because the application version is the same.

Also please follow shibshab suggestion, you can turn on LOGGING on the bootloader and see what cause the problem (turn the log level to DEBUG mode)

RE: DFU Update OTA of an application with ble secure bootloader works only once

boisi73 — Mon, 27 Nov 2017 07:41:33 GMT

In the DFU zip there is only the application (ble_app_blinky) included. I've debugged the code and the error is probably when deleting the flash area. Maybe there is a problem with the alignment ??