About OTA for nRF52810 on SDK v14.1

RE: About OTA for nRF52810 on SDK v14.1

joe — Fri, 23 Feb 2018 08:40:26 GMT

thanks,it can run.

RE: About OTA for nRF52810 on SDK v14.1

Sigurd — Thu, 22 Feb 2018 16:47:17 GMT

Hi joe, see this post.

RE: About OTA for nRF52810 on SDK v14.1

joe — Thu, 22 Feb 2018 16:41:01 GMT

I build code using keil.

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Thu, 22 Feb 2018 07:38:29 GMT

Are you building the code using GCC or Keil?

RE: About OTA for nRF52810 on SDK v14.1

joe — Thu, 22 Feb 2018 03:41:10 GMT

Hi ,I buid this zip ,it has below error ,could you have any suggestion?

.\_build\nrf52832_xxaa_s132.axf: Error: L6366E: uECC.c.o attributes are not compatible with the provided attributes .
Object uECC.c.o contains Build Attributes that are incompatible with the provided attributes.

RE: About OTA for nRF52810 on SDK v14.1

Alice — Mon, 25 Dec 2017 05:31:01 GMT

Hi Bjørn Spockeli，If you have new information, pls let me know, thanks.

RE: About OTA for nRF52810 on SDK v14.1

Alice — Sat, 16 Dec 2017 08:45:05 GMT

Yes, I have set the Optimization Level to 0 and increased the vs_uuid_count to 5 as well as allocated enough RAM returned by sd_ble_enable.

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Fri, 15 Dec 2017 12:32:18 GMT

MAke sure that you have set the Optimization Level to 0, to ensure that you're seeing the returned value for the correct function. Also make sure that you've increased the vs_uuid_count as well as allocated enough RAM for the softdevice by checking the app_ram_base variable returned by sd_ble_enable.

RE: About OTA for nRF52810 on SDK v14.1

Alice — Fri, 15 Dec 2017 11:39:01 GMT

Yes, I have flashed the bootloader to the board. Now it's the sd_ble_gatts_service_add function returns 0x04 error, not the nrf_dfu_svci_vector_table_set. So strange.

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Thu, 14 Dec 2017 15:06:36 GMT

Did you flash the secure bootlaoder to your nRF52832 board in addition to the application? ble_dfu_buttonless_async_svci_init() will call nrf_dfu_svci_vector_table_set() which checks if there is a bootloader present or not, i.e.

uint32_t nrf_dfu_svci_vector_table_set(void)
{
    uint32_t err_code;

    if (NRF_UICR->NRFFW[0] != 0xFFFFFFFF)
    {
        NRF_LOG_INFO("Setting vector table to bootloader: 0x%08x", NRF_UICR->NRFFW[0]);
        err_code = sd_softdevice_vector_table_base_set(NRF_UICR->NRFFW[0]);
        if (err_code != NRF_SUCCESS)
        {
            NRF_LOG_ERROR("Failed running sd_softdevice_vector_table_base_set");
            return err_code;
        }

        return NRF_SUCCESS;
    }

    NRF_LOG_ERROR("No bootloader was found");
    return NRF_ERROR_NO_MEM;
}

RE: About OTA for nRF52810 on SDK v14.1

Alice — Thu, 14 Dec 2017 02:59:47 GMT

Yes, using --family NRF52810 wouldn't meet any issues when flash it to nRF52810. But I meet another problem. I have debug the application, I would get 0x04 error when it calls nrf_dfu_svci_vector_table_set in the ble_dfu_buttonless_async_svci_init function. I have set the IRAM1 according to the indication of nrf_sdh_ble_enable function.

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Wed, 13 Dec 2017 12:57:55 GMT

Hi Alice, you need to generate the settings for --family NRF52810 and not --family NRF52. If I use the NRF52810 option for family I am not seeing any issues with the application starting up if i use mergehex to create a combined SD+BL+APP hex file.

RE: About OTA for nRF52810 on SDK v14.1

Alice — Wed, 13 Dec 2017 09:05:32 GMT

OK, I have known it before. So I just use application.hex to generate the DFU image and use SD+BL+APP+setting page to Merge into one file then flash it to nRF52810. Would you meet the problem as me?

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Wed, 13 Dec 2017 09:00:51 GMT

I am asking because the settings page, i.e. the settings.hex file you're generating with nrfutil should not be included in the DFU image. You should only merge it with the bootloader if you want to flash a combined SD+BL+APP image to the nRF52810 with a programmer.

RE: About OTA for nRF52810 on SDK v14.1

Alice — Wed, 13 Dec 2017 08:57:22 GMT

How to include the settings page in the DFU image?

I generate the DFU image as follow: nrfutil pkg generate --hw-version 52 --sd-req 0xFFFE --application-version 1 --application Clife.hex --key-file key_pro.pem Clife.zip

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Wed, 13 Dec 2017 08:50:08 GMT

Are you including the settings page in the DFU image?

RE: About OTA for nRF52810 on SDK v14.1

Alice — Wed, 13 Dec 2017 03:15:11 GMT

So sorry that I have a business trip for some days.Now I have update nrfutil to the latest version v3.4.0. I just flash the bootloader and the softdevice. After the update, I found that crc != s_dfu_settings.bank_0.image_crc in the nrf_dfu_app_is_valid function. Could you run application after the update? The command as follow:

nrfutil settings generate --family NRF52 --application Clife.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 Clife_setting.hex

Merge them into one file:

mergehex -m s112_nrf52810_5.1.0-2.alpha_softdevice.hex bootloader.hex Clife_setting.hex -o 123.hex 
mergehex -m 123.hex Clife.hex -o Clife_APP_SD_BL.hex

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Wed, 06 Dec 2017 14:47:53 GMT

Are you able to debug the application after the update?I am not able to get the Clife.hex to run on a nRF52 DK where the nRF52832 has been replaced with a nRF52810. Which version on nrfutil did you use to generate the settings page? Can you post the command you used to generate the settings page?

RE: About OTA for nRF52810 on SDK v14.1

Alice — Wed, 06 Dec 2017 09:57:05 GMT

The nrf_dfu_app_is_valid function returns true.But it still couldn't run my application. Except for the problem, I have merge SD bootloader and application into one file, but when I flash the one file to 52810, it tell me "The file specified is not a valid hex file,has data outside valid areas or does not have data in valid areas". So I couldn't flash it. I have attached the files and please see the 52810_OTA files. Could you help me have a look?

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Wed, 06 Dec 2017 06:14:17 GMT

The bootloader will automatically switch to a single bank update if the application is larger than 35kB. Are you able to debug the application after the DFU? If not please start a debug session in the bootloader and verify that it passes the nrf_dfu_app_is_valid check in nrf_dfu_init() in nrf_dfu.c

RE: About OTA for nRF52810 on SDK v14.1

Alice — Wed, 06 Dec 2017 06:06:47 GMT

Yes, it could run if I just flash the application and the softdevice. Our application would larger than 35kb generally, so do you have the single bank bootloader?

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Tue, 05 Dec 2017 12:23:23 GMT

Is the Clife.hex compiled against the headers of the SoftDevice present on the device? Does it run if you only flash the application to the nRF52810? Yes, there is a size limitation, 192kB - 96kB for the SoftDevice - 26 kB for the bootloader = 70 kB. This means that you can do a dual bank update of a 35kB application or a single bank update of an 35-70kB application.

RE: About OTA for nRF52810 on SDK v14.1

Alice — Tue, 05 Dec 2017 11:42:01 GMT

It's OK now. I should use 0xFFFE as its ID. I just program softdevice and bootloader then I could do OTA. However,after finish it, it haven't run application and it also have not advertised as DfuTarg. Is there limitation for the application size? My application code size is 44.42kB (Code + RO Data + RW Data)

RE: About OTA for nRF52810 on SDK v14.1

bjorn-spockeli — Tue, 05 Dec 2017 11:19:40 GMT

Which SoftDevice version have you flashed to the nRF52810? The example is compiled with the S112 v5.1.0-2.alpha SoftDevice which has 0xFFFE as its ID. I also assume that you have replaced the public key in the bootloader?

RE: About OTA for nRF52810 on SDK v14.1

Alice — Tue, 05 Dec 2017 10:13:49 GMT

Thanks. It could run now. But when I use nRF Connect to do OTA, it said SD version check failed.

nrfutil pkg generate --hw-version 52 --sd-req 0xA6 --application-version 1 --application Clife.hex --key-file key_pro.pem Clife.zip