• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 88 subscribers
  • Views 809 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281584
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to import basic sample project "blinky" into Segger IDE

oldViking

Hi,  Here is what I have done so far:

Windows 10,  installed Segger for ARM 5.68,  using the Tool Chain Manager installed nRF Connect SDK v1.8.0 ( installed in folder C:\Nordic_Semi ) 

Problem 1:     Cannot locate the basic samples folder in my SDK.  Specifically looking for project "blinky"

Problem 2:   Not sure of the correct method for  importing project blinky into Segger IDE.

Thank you for your help

oldViking

Parents
  • +1

    Hi,

    Did you install the regular version of Segger Embedded Studio (SES)? For nRF Connect SDK you must use SES Nordic Edition. 

    Installing the toolchain with toolchain manager will install SES as well, so do not have to install it seperately. Please see Building with SES for information about how to open and build nRF Connect SDK projects using SES.

    Best regards,

    Marte

  • 0 in reply to Marte Myrvold

    Hi Marte,

    I uninstalled SES, and removed the SDK.  Then ran Toolchain and let it setup SES and the SDK.

    Using directions in getting started I was able to build sample blinky and program it into the DK board.

    Now it works !

    One more question:   Can I get a start button for SES on my desktop, so that it is not necessary to use Toolchain to launch  SES ?

    Thankyou

    oldViking

  • 0 in reply to oldViking

    Hi oldViking,

    I am glad to hear that it works!

    When you open SES using the "Open Segger Embedded Studio" button in the toolchain manager you do not open SES directly. Instead it runs a cmd file that sets up the environment variables and opens SES. You can also open this file directly instead of going through the toolchain manager, so you can create a shortcut of this file to your desktop. You can find the file by clicking on the down button next to "Open Segger Embedded Studio" in the toolchain manager and select "Open toolchain directory". The file in question is the one called SEGGER Embedded Studio.cmd.

    Best regards,

    Marte

Reply
  • 0 in reply to oldViking

    Hi oldViking,

    I am glad to hear that it works!

    When you open SES using the "Open Segger Embedded Studio" button in the toolchain manager you do not open SES directly. Instead it runs a cmd file that sets up the environment variables and opens SES. You can also open this file directly instead of going through the toolchain manager, so you can create a shortcut of this file to your desktop. You can find the file by clicking on the down button next to "Open Segger Embedded Studio" in the toolchain manager and select "Open toolchain directory". The file in question is the one called SEGGER Embedded Studio.cmd.

    Best regards,

    Marte

Children
No Data
Related