• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 91 subscribers
  • Views 661 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
  • 0

    Thank you for the information. It is probably best that I try the VS Code extension since that is where support is moving.

    So this issue may be closed.

    For reference (in case someone else has this issue), current tool versions are:

    nRF Connect for Desktop v3.11.0

    Toolchain Manager v0.10.3

    nRF Connect SDK v1.9.1

    All tools were installed "automatically" (i.e. using GUI, not command line).

    There is no log visible in SES. The File->Open nRF Connect SDK Project operation fails with:

    Script Error: Syntax Error: Unable to parse JSON.string

    An "alert" was added to import_nordic_project.htm which shows that 2 separate Zephyr Base paths are used (one for previous Zephyr repo and one for current Zephyr repo). This is why an SES caching issue is suspected. Zephyr repo was specified using GUI as described previously.

    Tangentially, the problem may be a bit related to this:

    devzone.nordicsemi.com/.../ses-opens-wrong-project-with-multiple-git-repos-of-the-same-project

Reply
  • 0

    Thank you for the information. It is probably best that I try the VS Code extension since that is where support is moving.

    So this issue may be closed.

    For reference (in case someone else has this issue), current tool versions are:

    nRF Connect for Desktop v3.11.0

    Toolchain Manager v0.10.3

    nRF Connect SDK v1.9.1

    All tools were installed "automatically" (i.e. using GUI, not command line).

    There is no log visible in SES. The File->Open nRF Connect SDK Project operation fails with:

    Script Error: Syntax Error: Unable to parse JSON.string

    An "alert" was added to import_nordic_project.htm which shows that 2 separate Zephyr Base paths are used (one for previous Zephyr repo and one for current Zephyr repo). This is why an SES caching issue is suspected. Zephyr repo was specified using GUI as described previously.

    Tangentially, the problem may be a bit related to this:

    devzone.nordicsemi.com/.../ses-opens-wrong-project-with-multiple-git-repos-of-the-same-project

Children
No Data
Related
Terms of service