• State Not Answered
  • Replies 4 replies
  • Subscribers 75 subscribers
  • Views 508 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 257223
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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!

Parents
  • 0

    I am a bit confused regarding your first two screenshots. Are they supposed to be the same?

    Did you move the location of the SES project file before you compiled it? If so, try to leave it in the folder that you found it. Does it still behave like this in that case?

    I don't understand where the last screenshot is from. 

     

    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.  

     Can you share what this crash report window looks like?

    It may be that the path to your SDK is too long. Compilers in Windows has a limitation of ~250 characters. Try to unzip the SDK in a folder located in:

    C:\Nordic\SDK17.0.0

    Best regards,

    Edvin

Reply
  • 0

    I am a bit confused regarding your first two screenshots. Are they supposed to be the same?

    Did you move the location of the SES project file before you compiled it? If so, try to leave it in the folder that you found it. Does it still behave like this in that case?

    I don't understand where the last screenshot is from. 

     

    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.  

     Can you share what this crash report window looks like?

    It may be that the path to your SDK is too long. Compilers in Windows has a limitation of ~250 characters. Try to unzip the SDK in a folder located in:

    C:\Nordic\SDK17.0.0

    Best regards,

    Edvin

Children
No Data
Related
Terms of service