How do I calculate the Softdevice requriment parameter (--sd-req) parameter when genenrating DFU-Mesh

[msalmankhan334]

I am working on DFU over Mesh, I am following the quick start guide provided by you.
when generating the pakage I am unable to understand the option list for nrfutil, like for example --sd-req how do I use the corret one for s140_nrf52_7.2.0_softdevice.hex.
Also the documentation is very confusing, can you please suggest me a consice guide that can help to acheive this task?

Thanks

This is for the softdevice s132 and I am using s140_nrf52_7.2.0_softdevice.

[Vidar Berg]

Hello, 

You can run "nrfutil pkg generate --help" to view the FWIDs for our Softdevice releases.

Best regards,

Vidar

[msalmankhan334]

Thanks for the reply but when I use the above command it says

C:\Users\NRF_DFU\Desktop\DFU_Sensor>nrfutil pkg generate --help
Usage: nrfutil [OPTIONS] COMMAND [ARGS]...
Try 'nrfutil --help' for help.

Error: No such command 'pkg'.

[Vidar Berg]

Sorry, I forgot you were using the Mesh DFU protocol which relies on an older version of nrfutil. Note that you can find the FWID from the Softdevice release notes too.

[msalmankhan334]

Yes I figured it already for softdevice the one I am using have FWID is: 0x0100.
but when performing DFU over Mesh I encounter this :

[Vidar Berg]

--sd-req must specify the FWID of the Softdevice currently present on the device. Please correct me if I'm wrong, but I assume 0x0100 is the FWID of the Softdevice you are upgrading to?

[msalmankhan334]

Yes, softdevice Id currently present on the the device, I am using DFU example to perform DFU over Mesh, In which blinky application DFU file (in my case blinky) will be sent over the air.
I am actually following this guide https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v5.0.0%2Fmd_examples_dfu_README.html&anchor=dfu_example
But unable perform...

[Vidar Berg]

Please run 'nrfjprog --version' to check what version of the Jlink drivers you have installed. From previous tickets I see some have experienced the same problem as you where it turned out to be caused by a bug in the Segger VCOM interface.

e.g.

 Mesh DFU Failed to establish connection 

I would also suggest that you disable the Mass storage functionality as explained here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.2.0/zephyr/develop/flash_debug/nordic_segger.html#disabling-the-mass-storage-device-functionality. This is worth a try even if you use Windows.  

[msalmankhan334]

Yes, exactly the problem was due to Jlink ( I was using a clone version).
Changing the Segger Jlink resolved the issue.
Thanks for the support.