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

[loquat]

I modified,
 My application's bdaddr is set public device address.
 secure bootloader's bdaddr is set same public device address.

When run DFU on nrf connect for desktop,
nrf connect for desktop is hung up.

When use nrf connect for mobile(Android), It's no problem.

[loquat]

OK.

Thnak you.

[RVM]

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.

[Einar Thorsrud]

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.