Buttonless OTA DFU stops after switching to bootloader

RE: Buttonless OTA DFU stops after switching to bootloader

Archana Fugare — Wed, 27 Nov 2019 09:18:58 GMT

Not resolved.

RE: Buttonless OTA DFU stops after switching to bootloader

Geek — Thu, 05 Sep 2019 14:56:36 GMT

Hello Archana,

Im facing the same issue. My Application won't give control to my Bootloader DFU after firmware download.

Im using The exemple inside the SDK11 and Red Bear Nano V2 Board.

Did you resolve this issue ?

RE: Buttonless OTA DFU stops after switching to bootloader

Archana Fugare — Thu, 06 Jun 2019 06:49:42 GMT

Hi,

Please help me in this

How to switch from application mode to bootloader mode again in OTA.

I am using nRF52832 DK as well as my custom board based on nRF52832.

I have implemented the OTA-DFU and uploaded the application zip.

Now I want to upload new application hex'z zip but unable to switch from application mode to bootloader mode again.

regards,

Archana

RE: Buttonless OTA DFU stops after switching to bootloader

Edvin — Mon, 20 Aug 2018 13:12:57 GMT

Hello Roland,

Try to modify the gap_params_init() function in nrf_dfu_ble.c in the bootloader project:

static uint32_t gap_params_init(void)
{
    uint32_t                err_code;
    ble_gap_conn_sec_mode_t sec_mode;
    uint8_t const *         device_name;
    uint32_t                name_len;

    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&sec_mode);

#if (!NRF_DFU_BLE_REQUIRES_BONDS)

    err_code = gap_address_change();
    VERIFY_SUCCESS(err_code);

    if ((m_flags & DFU_BLE_FLAG_USE_ADV_NAME) != 0)
    {
        NRF_LOG_DEBUG("Setting adv name: %s, length: %d", m_adv_name.name, m_adv_name.len);
        device_name = m_adv_name.name;
        name_len    = m_adv_name.len;
    }
    else
    
#endif
    {
        // Change address here:
        ble_gap_addr_t my_addr;
        err_code = sd_ble_gap_addr_get(&my_addr);
        APP_ERROR_CHECK(err_code);
        
        my_addr.addr_type = BLE_GAP_ADDR_TYPE_PUBLIC;
        my_addr.addr[0] = 0x00;
        my_addr.addr[1] = 0x00;
        my_addr.addr[2] = 0x00;
        my_addr.addr[3] = 0x00;
        my_addr.addr[4] = 0x00;
        my_addr.addr[5] = 0x00;
        
        err_code = sd_ble_gap_addr_set(&my_addr);
        VERIFY_SUCCESS(err_code);
        
        NRF_LOG_DEBUG("Using default advertising name");
        device_name = (uint8_t const *)(NRF_DFU_BLE_ADV_NAME);
        name_len    = strlen(NRF_DFU_BLE_ADV_NAME);
    }

    err_code = sd_ble_gap_device_name_set(&sec_mode, device_name, name_len);
    VERIFY_SUCCESS(err_code);

    err_code = sd_ble_gap_ppcp_set(&m_gap_conn_params);
    return err_code;
}

Best regards,

Edvin

RE: Buttonless OTA DFU stops after switching to bootloader

roland.schenk — Mon, 20 Aug 2018 09:10:38 GMT

Hello Edvin,

Yes, the address i used, was didfferent form the standard address, and the bootloader was advertising as "DfuTarg" on the standard device address from FICR->DEVICEADDR[0] and FICR->DEVICEADDR[1].

An other problem was, that I had set m_bt_addr.addr_type = BLE_GAP_ADDR_TYPE_PUBLIC;.

Now it's working fine, but i had to change the address to the standard address and the address type to BLE_GAP_ADDR_TYPE_RANDOM_STATIC (like in the nordic buttonless example).

Which changes are needed in the bootloder to use a custom address with address type BLE_GAP_ADDR_TYPE_PUBLIC?

Thanks a lot for your help!

Best regards,

Roland

RE: Buttonless OTA DFU stops after switching to bootloader

Edvin — Mon, 20 Aug 2018 07:43:01 GMT

Hello Roland,

So I assume that you call BLC_vSetBtAddress with a custom value for u32SerialNumber, not equal to the device address already defined in the FICR, is that correct?

Do you do the same operation in the bootloader project?

I suspect that when the device starts up in bootloader mode, the device uses the standard address found in FICR->DEVICEADDR[0] and FICR->DEVICEADDR[1], and hence, the PC is looking for a bootloader with a different address.

Can you check this by opening nRF Connect (for desktop), and start scanning after you try to perform the DFU. See if there is a device advertising with "DfuTarg" (or any other name if you changed it in the bootloader project), and see if the address corresponds with the address that you set, EC:2A:F0:F0:F0:DB, or another address?

Best regards,

Edvin

RE: Buttonless OTA DFU stops after switching to bootloader

roland.schenk — Mon, 20 Aug 2018 06:47:49 GMT

Hello,

In the bootloader NRF_DFU_BLE_REQUIRES_BONDS and NRF_SDH_BLE_SERVICE_CHANGED are set to 1.

The device address is set once at he startup of the application:

void BLC_vSetBtAddress(uint32_t u32SerialNumber)
{
   ble_gap_addr_t m_bt_addr = BT_BASE_ADDRESS;
   m_bt_addr.addr_type     = BLE_GAP_ADDR_TYPE_PUBLIC;
   m_bt_addr.addr[0] = u32SerialNumber & 0xFF;
   m_bt_addr.addr[1] = (u32SerialNumber >> 8) & 0xFF;
   ret_code_t err_code = sd_ble_gap_addr_set(&m_bt_addr);
   APP_ERROR_CHECK(err_code);

   NRF_LOG_INFO("BT Address: %02x:%02x:%02x:%02x:%02x:%02x", m_bt_addr.addr[5],m_bt_addr.addr[4], m_bt_addr.addr[3], m_bt_addr.addr[2],m_bt_addr.addr[1], m_bt_addr.addr[0]);
}

<info> app: BT Address: EC:2A:F0:F0:F0:DB

Best regards,

Roland

RE: Buttonless OTA DFU stops after switching to bootloader

Edvin — Fri, 17 Aug 2018 07:25:06 GMT

Hello,

Do you do anything special with the device address? Have you changed it in the buttonless application?

Have you changed the define in sdk_config.h in the bootloader project, called: NRF_DFU_BLE_REQUIRES_BONDS to 1?

Best regards,

Edvin

RE: Buttonless OTA DFU stops after switching to bootloader

roland.schenk — Thu, 16 Aug 2018 13:55:10 GMT

Hello,

I have integrated the peer manager in my application and now I am using the buttonless DFU service with bonding.

I use PC nRF Connect to upload the firmware. The pairing / bonding is working fine. But after switching to the bootloader the connection stops and the bootloader rises a timeout error after some seconds. Then the bootloader is advertising as DfuTarg.

I have added a logfile from nRF Connect and a logfile from the J-Link RTT connected to the targed running the application.

What could be the reason of braeking the connection, after changeing from the application to the bootloader?

devzone.nordicsemi.com/.../nrfconnect_5F00_log_5F00_my_5F00_app.txt devzone.nordicsemi.com/.../rtt_5F00_log_5F00_my_5F00_app.txt

RE: Buttonless OTA DFU stops after switching to bootloader

Edvin — Tue, 03 Jul 2018 08:44:14 GMT

Hello,

You may be aware of this, but the application should reset after entering bootloader mode, and start advertising as DfuTarg, so there will be a disconnect and a reconnect, but that is also the case for the buttonless example, so there is no reason it shouldn't work in your application.

Do you use nRF Connect to upload your firmware? Do you get any information from the log there? What happens after the disconnect? Does it return to application, or does it stay in bootloader mode?

Best regards,

Edvin