OTA fail after set the public address

RE: OTA fail after set the public address

ovrebekk — Mon, 13 May 2024 08:13:19 GMT

Very good to hear. The best of luck with your project 🙂

RE: OTA fail after set the public address

Gin — Wed, 08 May 2024 04:56:17 GMT

My problem has been resolved because the version of the nrf connect software I am using is too low. I switched to the latest version 4.28 and everything has been resolved

RE: OTA fail after set the public address

Gin — Tue, 07 May 2024 10:12:36 GMT

The initial mobile system I used was Android 10 but couldn't be upgraded. Later, I used Android 14, but it couldn't be upgraded the first time. If I try to use a program that can be upgraded to insert nrf52832 and perform DFU upgrade on it, then erase all the programs and burn my program, then I can upgrade using my phone, but when I change the public MAC address, I cannot upgrade again

Here are the functions for me to change the public MAC and write to the UICR register

void load_dvc_mac(void)
{

    uint32_t err_code = 0;
    ble_gap_addr_t addr;
    err_code = sd_ble_gap_addr_get(&addr);
    APP_ERROR_CHECK(err_code);

    //  LOG("mac:%X:%X:%X:%X:%X:%X",dvc_ble_info.ble_mac[0],dvc_ble_info.ble_mac[1],dvc_ble_info.ble_mac[2], dvc_ble_info.ble_mac[3],dvc_ble_info.ble_mac[4],dvc_ble_info.ble_mac[5]);

    addr.addr[0] = dvc_ble_info.ble_mac[5];
    addr.addr[1] = dvc_ble_info.ble_mac[4];
    addr.addr[2] = dvc_ble_info.ble_mac[3];
    addr.addr[3] = dvc_ble_info.ble_mac[2];
    addr.addr[4] = dvc_ble_info.ble_mac[1];
    addr.addr[5] = dvc_ble_info.ble_mac[0];

    addr.addr_type = BLE_GAP_ADDR_TYPE_PUBLIC; // 公共类型的广播地址;  如果是静态随机，最高2位需要为11:  addr[5]|0xC0

    if (addr.addr_type == BLE_GAP_ADDR_TYPE_RANDOM_STATIC)
    {
        addr.addr[5] = (addr.addr[5] | 0xC0);
    }
    // LOG("<%d-%d-%x>\n", addr.addr_id_peer, addr.addr_type, addr.addr[5]);

    err_code = sd_ble_gap_addr_set(&addr);

    APP_ERROR_CHECK(err_code);

}

void Save_mac_to_UICR(void)
{

    NRF_UICR_Type t_uicr = {0};
    memcpy((uint8_t *)&t_uicr, (uint8_t *)NRF_UICR, sizeof(NRF_UICR_Type));
    memcpy((uint8_t *)&t_uicr.UNUSED0, &dvc_ble_info.ble_mac[0], 6);

    nrf_nvmc_page_erase((uint32_t)&NRF_UICR->UNUSED0); // 一次擦除连续写入
    nrf_nvmc_write_bytes((uint32_t)&NRF_UICR->UNUSED0, (uint8_t *)&t_uicr, sizeof(NRF_UICR_Type));

}

RE: OTA fail after set the public address

ovrebekk — Mon, 06 May 2024 09:36:41 GMT

If you are using SDK v12 or newer what you describe should work fine, as long as you make sure to write your data to one of the CUSTOMER registers in the UICR.

If you're still having issues with this please open a new ticket, and share the details of what you have tried and which problems you are experiencing. Then we can have a look.

Best regards
Torbjørn

RE: OTA fail after set the public address

Gin — Mon, 29 Apr 2024 08:14:06 GMT

I also encountered the same problem. The chip I used is NRF52832. I set a public address in the application and saved it in the NRF_UICR register to read the address when bootloader dfu starts. But there is a serious and unsolvable problem here. My phone keeps reminding me of connection timeout when performing DUF. Through simulation, I found that the application did not start the DFU process. If I do not set a public address, the DFU process is successful. Through low-power analysis of the current, I determined that the application did not enter the bootloader at all because the DFU process restarts and the current tends to decrease. However, the problem I encountered did not involve a restart. The routine I used was ble_uart, and I have no way to solve this problem. I am saddened

RE: OTA fail after set the public address

Hung Bui — Fri, 23 Dec 2016 13:00:58 GMT

Hi Alice,

The problem is that when we reset to the OTA bootloader, the softdevice is reinitialized, therefore the address used here is the original one. Not the one you set in your application. Therefore the app on the phone won't be able to find the DFU bootloader to do DFU update since the address is changed.

So what you need to do is to also set the address to the address you saved in UICR in the bootloader.

Note that inside dfu_transport_update_start() we do an address change if there is no re-bond required, we increase the address by 1 to make the DFU look like a new device, just to make sure it's not cached by the peer device, or the peer device try to re-bond with the DFU bootloader. The app do search for both the device address and the device address + 1 to do a re-connect.