I noticed when I use nrfutil DFU BLE command on the nRF52 DK the nrfutil program a "connectivity firmware" before the perform the DFU BLE to a Target device.
The issue I am facing is I am using a custom hardware with a different pinout that nRF52 DK and with no J-Link OB like the nRF5X DK boards. Making incompatible it with the "connectivity firmware"
Are there any documentation to use nrfutil DFU BLE using a custom hardware with no J-Link OB chip? or where can I find an using that firmware (I dont know the correct name) to edit the board.h and make it compatible with my hardware and be able to make BLE DFU from a window PC
in order to create connectivity firmware that is compatible with custom nRF52 hardware you have to apply the sdk121_connectivity.patch, found here in the pc-ble-driver GitHub repo, to the connectivity example in SDK v12.1.0. You can find the connectivity example in examples\ble_central_and_peripheral\ble_connectivity\pca10040\ser_s132_hci. You can then change the pinout in pca10040.h or create a custom_board.h to match your custom hardware.
Does it works using SDK v13?
The patch is based on SDK v12.1.0. It will not work on other SDK releases. If you need to base it on another version of the SDK then you must port this patched version to the target SDK on your own.
The patch is SDK v12.1.0 specific, however it might work with SDK v13, but I have not tried that.
@tesc I want to port it to another SDK version
@bjorn-spockeli Thank for the info now it is more clear for me