We used nRF5_SDK_15.0.0_a53641a and nrf5_SDK_for_Mesh_v2.0.0_src.
We are following DFU quick start guide http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v0.10.0%2Findex.html
For nRF52:
We used nRF5_SDK_15.0.0_a53641a and nrf5_SDK_for_Mesh_v2.0.0_src.
We are following DFU quick start guide http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v0.10.0%2Findex.html
For nRF52:
Hi Arij could you please open a new case regarding this.
iotlight Like I mentioned in the comment above, I would use nrfjprog --reset -s without the Segger ID. That way, if you have multiple dev kits attached to your pc, you will get a popup where you can select the correct ID.
Another tip: make a script to automate all of the steps. I should have done this from the beginning too, but did not.
In general, it is a good idea to connect all of the dev kits to your computer via usb. That way, you can program & power the DKs via USB. You will need to attach both DKs to the computer via USB. That is the reason you are getting the error.
You will need to program both kits via USB with the softdevice, bootloader & application before you can do a DFU over the mesh network.
There is documentation which shows how to install the nrfutil mesh branch. What happens when you enter the command "nrfutil version" in a command prompt?
I opened a new case about this issue