• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 91 subscribers
  • Views 663 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 287892
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

Segger Embedded Studio with multiple Zephyr repos

droid

I have been using Segger Embedded Studio with an external zephyr repo by setting the following in SES:

Tools->Options->nRF Connect->Zephyr Base

It works fine. However, if I attempt to change the value to another Zephyr repo, I am unable to create a newSES  project with:

File->Open nRF Connect SDK Project

The problem is that SES caches information from the old Zephyr Base which causes a conflict and error message (problem with cmake etc etc).

Is it possible to flush SES cache e.g. delete certain files, etc. so multiple Zephyr repos can be used?

This would be very helpful for development.

Parents
  • +1

    Hello, 

    First of all I would encourage you to move over to our VS Code extension instead of Segger Embedded Studio. Starting with nRF Connect SDK v2.0.0 we will not bundle Segger Embedded Studio with our SDK.

    Out-of-the-box support for Segger Embedded Studio Nordic Edition (SES-NE) will not be present in nRF Connect SDK 2.0 and later versions. This means that from 2.0, nRF Connect SDK will no longer be supported for use with SES-NE. This does not mean that Segger Embedded Studio standard edition (SES)  will be made unavailable for nRF5 SDK customers or nRF Connect SDK 1.x customer using SES-NE. The free license for Nordics customers will be continued, and support for existing customers will continue. But from nRF Connect SDK 2.0 onwards the development platform promoted by Nordic will be based on an extension to Visual Studio Code. Customers working in SES-NE can migrate their work to VS Code using the “Add an existing application” feature in VSCode.
    Nordic now has a dedicated development team working on VSCode and this means Nordic can define the priorities for the platform and enable a tight integration with the SDK and the devices.

    I have been using Segger Embedded Studio with an external zephyr repo by setting the following in SES:

    What version of nRF Connect SDK are you trying to switch to? Have you installed these versions manually or via the Toolchain Manager?

    The problem is that SES caches information from the old Zephyr Base which causes a conflict and error message (problem with cmake etc etc).

    What errors are you seeing? Please provide full log output from Segger Embedded Studio. Make sure that you are configuring the SES environment correctly

    Kind regards,
    Øyvind

Reply
  • +1

    Hello, 

    First of all I would encourage you to move over to our VS Code extension instead of Segger Embedded Studio. Starting with nRF Connect SDK v2.0.0 we will not bundle Segger Embedded Studio with our SDK.

    Out-of-the-box support for Segger Embedded Studio Nordic Edition (SES-NE) will not be present in nRF Connect SDK 2.0 and later versions. This means that from 2.0, nRF Connect SDK will no longer be supported for use with SES-NE. This does not mean that Segger Embedded Studio standard edition (SES)  will be made unavailable for nRF5 SDK customers or nRF Connect SDK 1.x customer using SES-NE. The free license for Nordics customers will be continued, and support for existing customers will continue. But from nRF Connect SDK 2.0 onwards the development platform promoted by Nordic will be based on an extension to Visual Studio Code. Customers working in SES-NE can migrate their work to VS Code using the “Add an existing application” feature in VSCode.
    Nordic now has a dedicated development team working on VSCode and this means Nordic can define the priorities for the platform and enable a tight integration with the SDK and the devices.

    I have been using Segger Embedded Studio with an external zephyr repo by setting the following in SES:

    What version of nRF Connect SDK are you trying to switch to? Have you installed these versions manually or via the Toolchain Manager?

    The problem is that SES caches information from the old Zephyr Base which causes a conflict and error message (problem with cmake etc etc).

    What errors are you seeing? Please provide full log output from Segger Embedded Studio. Make sure that you are configuring the SES environment correctly

    Kind regards,
    Øyvind

Children
No Data
Related
Terms of service