Error uploading .hex generated from keil or seggar through nRF connect to nRF52840 dongle, but upload .hex files that are already in hex folder

[iamsheikhubaid]

Hello there, I am trying to write hex file generated form Keil or Segger studio but a popup window comes out to select the soft device in nRF connect programmer, I have selected every option but it will fail to write the hex, but if I will upload the hex that are given in hex folder it will upload that one. Does any body know that what exactly is the error? or is there any way to remove that soft device firmware so that it will be able to upload the hex.

Here is the ScreenShot

also if i select the s140 the following error comes out

Data block: 0x00026000-0x0002B8BC (0x000058BC bytes long)

Hash is generated by SHA256

Performing DFU. This may take a few seconds

DFU procedure starts. This may take a few seconds.

DFU failed: Error message for known extended error code from DFU target: The array of supported SoftDevices for the update does not contain the FWID of the current SoftDevice.

Device not found due to failure during DFU

and it shows that the specified sdReq does not match the current soft device, please select a different value

and it stop writing the hex, does any one help me out in this.

[Vidar Berg]

Hi,

Are you using the 1.0.0-experimental.5 version of the Programmer app, and did you upload the correct softdevice version (s140 v.6.1.0 if you are building examples from SDK 15.2.0)?

I tried this with the hrs example and was unable to reproduce the error. This is what I did:

1. Built the hrs example with Keil

2. Opened the programmer app and selected the .hex file I built together with the s140 softdevice from  nRF5_SDK_15.2.0_9412b96\components\softdevice\s140

3. Verified that the dongle was advertising.

[iamsheikhubaid]

I have used nrfjprog but it will not actually program .hex in the dongle, error occurs that there is no debugger connected to the PC. I actually done that part to press that button and get the dongle in the programming mode. Red led starts blinking but it is unable to write .hex file that was generated by Keil, it will just add the .hex that was present in the directory of hex like

D:\nRF5_SDK_15.2.0_9412b96\nRF5_SDK_15.2.0_9412b96\examples\ble_peripheral\ble_app_blinky\hex\

but unable to upload the hex of keil like

D:\nRF5_SDK_15.2.0_9412b96\nRF5_SDK_15.2.0_9412b96\examples\ble_peripheral\ble_app_blinky\pca10059\s140\arm5_no_packs\_build

Help me in this, Thanks

[Vidar Berg]

You need to include the softdevice .hex in addition to the application .hex in D:\nRF5_SDK_15.2.0_9412b96\nRF5_SDK_15.2.0_9412b96\examples\ble_peripheral\ble_app_blinky\pca10059\s140\arm5_no_packs\_build, see screedump from my previous reply.

The pre-compiled hex in D:\nRF5_SDK_15.2.0_9412b96\nRF5_SDK_15.2.0_9412b96\examples\ble_peripheral\ble_app_blinky\hex\ contains softdevice+application which is why you don't have to include the softdevice.