Able to build, but not run unaltered example SDK projects using Segger (ses)

[TedNim]

Newbie here simply trying to run some example projects from the SDK.

Setup:

• Segger Embedded Studio 5.10b
• Tried example projects in both SDK v17 and v16
• nRF52 DK as attached hardware

I'm unable to run some (not all) unaltered SDK example projects from SES.  Some projects I have no trouble with, e.g. blinky, and the UART example.  I'm trying to add a UART interface to the Gazell example project, and as a first step I'm simply trying to build and run the unaltered Gazell example project:  gzll_ack_payload

I can open and build the example project (both host and device) without issue...see attached screen-cap showing that the build completes without issue.

The problem arises when I click the "play" button to upload and execute the program.  The output window shows:

However, SES then is looking for and is unable to find the files shown below.  Some of these files and/or directories don't even exist within the SDK, and I can't find where they do reside.  I also don't understand why it's looking for these files after it completes the build process?  After it reports being unable to find each of these files, it ends up with the the Segger Crash Report window.  

I've used nRFgo Studio to do an erase all before trying these steps, it didn't seem to help.  I understand this may be an SES issue, but it seems to work fine on some projects, so I thought it might also be an SDK/project issue.

Thanks!

[TedNim]

Hello Edvin,

Sorry, the first screenshot was supposed to be different.  It was nothing really interesting though, just showing the output window that the project built with success.

The last screenshot is one that I created by copying the files that it was looking for and pasting them into a single image...just to show each of the files that it was looking for.  The crash report window was also nothing interesting...just a red window saying it crashed, and asking me whether I want to send a report or not.

I tried to run the project directly from where it is in the SDK...I did not move it.  I have the SDK installed very close to the top level:  C:\temp\

I will attempt again today on different computer.

Thanks,

Ted