SEGGER Embedded Studio can't find softdevice binary

[raemond]

When I try to build and run any example from the nRF5 SDK, it can compile successfully. But when loading to the eval kit, it can't find the 's140_nrf52840_5.0.0-2_alpha_softdevice.hex'.

Error reported: Additional Load File[0] "../../../../../../components/softdevice/s140/hex/s140_nrf52840_5.0.0-2_alpha_softdevice.hex does not exist."

I can't figure out how to modify the path to ensure it is actually looking in the correct directory.

Versions: SEGGER Embedded Studio 3.30, nRF5 SDK 14.2.0

[bjorn-spockeli]

Select Project in the Project Explorer, right-click it and select "Edit Options". In the options there should be a dropdown menu beside the search bar, set this to "Common".

Now, select "Loader" under "Debug" and click the "Additional Load File[0]" field. Change this to to point to the components\softdevice\s140\hex folder and the s140_nrf52840_5.0.0-2.alpha_softdevice.hex file

[raemond]

I find that there isn't a way for the loader to notice the configuration change. After doing some random combination of closing SES, and rebuilding/cleaning, the config actually worked. Now I am trying to switch it to SoftDevice 6 and it isn't switching the load file to the new hex.

[butch]

I have a similar issue with "../../../../../../components/softdevice/s132/hex/s132_nrf52_5.0.0_softdevice.hex" does not exist. In your case, it seems to be a typo where a "_" should be a ".". I don't see a similar typo for my case, and can't find the problem. Should I open a new thread? Versions: Ubuntu 16.04, SES 3.30 Linux x64, SDK 14.2. I followed the video tutorial rather closely. Sorry Raemond to interfere. Your issue with configuration change not effective a bug in SES?

[raemond]

I think the SES bug, causes issues with finding the softdevice binary. Because any change you make isn't immediately effective, not sure where it caches the preferences or how to refresh them. But at some point it takes effect and it starts working.

[butch]

So, acting on your experience, I restarted SES after any change to configuration. At some point I chose "Hex" instead of "Detect" for "Additional Load File Type[0]" Then I got "Invalid ASCII encoded byte line 1". And I tried "Build and Debug" instead of "Build and Run." I reverted the "Hex" change. At some point, it magically seemed to work, the hrs example downloaded and responded to the button. Something is not ready for prime time.

[butch]

May I ask if you are new to SES, and why? I was using Eclipse, and not using the Nordic makefiles, but that was tedious and error prone so decided to try SES. And working with SDK 13.2 and thinking I needed to stay current with a new version. Not a good first impression.