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

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

Vidar Berg — Fri, 19 Oct 2018 14:58:35 GMT

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.

RE: 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 — Fri, 19 Oct 2018 13:53:36 GMT

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

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

Vidar Berg — Thu, 18 Oct 2018 11:25:27 GMT

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.