DFU is Failed on nrf connect for desktop, when use public device address.

RE: DFU is Failed on nrf connect for desktop, when use public device address.

Einar Thorsrud — Wed, 16 Jun 2021 07:50:43 GMT

Hi,

If the problem here is that nRF Connect assumes the address is incremented by 1 and the bootloader do not do it (as is the case with the original issue in this thread), then you could modify the nRF Connect BLE app to do that (possibly within the pc-nrf-dfu-js module).

The name is not relevant for nRF Connect for desktop as it searches for the BT address (in buttonless DFU context name is needed for iOS only, as the iOS BT API does not provide the BT address, so a special name is set and used to connect to the same device again to work around that).

Update: to not increment the address, remove / comment out this._addOneToAddress() on line 253 in bleTransport.js.

RE: DFU is Failed on nrf connect for desktop, when use public device address.

RVM — Tue, 15 Jun 2021 23:55:44 GMT

Is there any way I can change the desktop application to use the name 'DfuTarg' instead of the +1 MAC address?

We have about 5000 devices with a boot loader that we cannot change, and we are trying to avoid being forced to use the mobile version of the nRF Connect since it is a nightmare trying to match the MAC addresses to the devices on hand.

RE: DFU is Failed on nrf connect for desktop, when use public device address.

loquat — Tue, 22 Dec 2020 03:31:32 GMT

OK.

Thnak you.

RE: DFU is Failed on nrf connect for desktop, when use public device address.

Einar Thorsrud — Mon, 21 Dec 2020 09:22:14 GMT

Hi,

[quote user="loquat"]Please tell me the best place to set BDADDR.[/quote]

The problem here is that you set the address after it has allready been set by the bootloader, which reads the address increments by one and writes it. This is done in gap_address_change() in nrf_dfu_ble.c. I suggest you either change that function directly, or add another function that is called immediately before it, that sets the public address, and then gap_address_change() will be called to increment it again by 1 only if appropriate (which is when not using bonding in the bootloader, which is the most sensible in most cases).

RE: DFU is Failed on nrf connect for desktop, when use public device address.

loquat — Fri, 18 Dec 2020 09:06:45 GMT

I added the following:,

nrf_dfu_ble.c
................
static uint32_t advertising_init(uint8_t adv_flags, ble_gap_adv_params_t const * const p_adv_params)
{
    uint32_t err_code;
    uint16_t actual_device_name_length = BLE_GAP_ADV_SET_DATA_SIZE_MAX - APP_ADV_DATA_HEADER_SIZE;

    /* This needs to be static because of SoftDevice API requirements. */
    static uint8_t m_enc_advdata[BLE_GAP_ADV_SET_DATA_SIZE_MAX];

    ble_gap_adv_data_t m_adv_data =
    {
        .adv_data =
        {
            .p_data = m_enc_advdata,
            .len    = APP_ADV_DATA_HEADER_SIZE,
        }
    };
 /****** Add start ********/
    ble_gap_addr_t bdaddr;
    bdaddr.addr_id_peer = 0;
    bdaddr.addr_type = BLE_GAP_ADDR_TYPE_PUBLIC;
    memcpy(&bdaddr.addr, PUBLIC_DEVICE_ADDRESS, BLE_GAP_ADDR_LEN);
    sd_ble_gap_addr_set(&bdaddr);
 /****** Add end   ********/

Please tell me the best place to set BDADDR.
(top of gap_params_init()?)

RE: DFU is Failed on nrf connect for desktop, when use public device address.

Einar Thorsrud — Fri, 18 Dec 2020 08:25:55 GMT

Hi,

Now I see the problem. You have the exact same address in bootloader mode and in normal mode, but nRF Connect will assume that the address is incremented by one when not using bonding in the bootloader.

Where did you set the public BLE address in the bootloader? Referring to components\libraries\bootloader\ble_dfu\nrf_dfu_ble.c you have a gap_address_change() function there, which takes the address and increments it (when not using bonding in bootloader). You should change your address immediately before that runs, or modify that function to set it to your public address + 1. (I admit though that this approach is a bit odd with public addresses as there is a higher likelihood of having a device in range with this +1 address, but that is how this has been solved).

RE: DFU is Failed on nrf connect for desktop, when use public device address.

loquat — Fri, 18 Dec 2020 07:56:54 GMT

1. Connect to Allication.

2. run the DFU. wait a bit. (nrf connect is down to white screen.)

3. rescan and connect.

Aditional,
If you execute DFU on DfuTarg, it will work normally.

RE: DFU is Failed on nrf connect for desktop, when use public device address.

Einar Thorsrud — Thu, 17 Dec 2020 15:58:06 GMT

Hi,

I have not been able to reproduce this issue. Can you double check that the nRF uses the expected address when in bootloader mode? Depending on NRF_DFU_BLE_REQUIRES_BONDS, that should be either your public address or public address + 1. nRF Connect for mobile can also use device name to separate devices so it might work even if the address is not correct.