Regarding hex file setting

RE: Regarding hex file setting

Einar Thorsrud — Mon, 06 Jan 2020 07:44:33 GMT

Hi,

I have some more questions and comments:

Have you created your own project from scratch, or based it on an example project?
1. If so, which?
If you have not based your SES project on an example project, it does not flash the SoftDevice unless you have added support for it, so It does not seem like the case.
1. If however, you do use the SoftDevice, then this needs to be flashed. Do you use the SoftDevice?
2. If you use the SoftDevice, then you need to flash it in addition to the application. You can find it for nRF52840 here: <SDK>\components\softdevice\s140\hex

This suggestion about missing SoftDevice was a gut feeling based on what you wrote in the initial post. But if this looks like a dead-end, then please specify more about your application (SDK version, example project, flash location, using SoftDevice or not, what debugging you have done, etc.)

RE: Regarding hex file setting

RakeshHegden — Sat, 04 Jan 2020 06:22:46 GMT

Hi Einar, Thanks for the response,

yes I am using the SES- Segger Embedded Studio,

I have generated the .hex file and erased the chip first using J link and flashed the hex file

I have created my own project, not from example project Can you please explain to me how do I need to program the SoftDEvice.hex

RE: Regarding hex file setting

Einar Thorsrud — Fri, 03 Jan 2020 12:20:11 GMT

Hi,

You do not write which IDE you use to build and debug, nor how you program the .hex file or what application you are using. If you are making a BLE application (or another application that relies on the SoftDevice), then this must also be programmed. If you program and/or debug from Segger Embedded Studio using an SDK example project, this will be programmed for you automatically. Is that the case? On the other hand, if you program the .hex file manually after doing a chip erase, you must also program the SoftDEvice .hex file.