• State Not Answered
  • Replies 9 replies
  • Subscribers 75 subscribers
  • Views 1532 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 301875
Options

Unable to parse JSON String

John

Nordic has for whatever reason made the decision to demand that users invest time and effort learning a new environment Visual Studio.

It is extremely dissapointing that it seems that both Segger and Visual Studio are unable to be installed on the same machine.

Once Visual Studio is installed it's impossible to use Segger, because whenever you try and open a project with Segger the error "

Unable to parse JSON String

Is presented.

I tried to install VS to a different directory, but the same issue exists.

The only work around that seems to allow me to use Segger is to remove V2.2.0 SDK

I'm trying to create code and at the same time learn how to become familiar with VS so that I don't get left behind.

What is obvioulsy incredibly frustrating is the inability have bith SDK's installed simultaneously, mainly because there are considerable code changes required to convert to the new VS SDK.

This issue has been around for many months now, I'd be grateful if someone would be kind enough to take the issue seriously please.

Parents Reply Children
  • 0 in reply to Priyanka

    I tried to open SES from Toolchain Manager and see the same error. This is with NCS v1.6.1. I also have v2.0.0, v2.2.2, and v2.2.99-dev3 installed.

    Opening SES from Toolchain Manager only works if all later SDK versions that reference VS Code are removed.

  • 0 in reply to brec

    Hi Bob,

    As mentioned earlier,

    Priyanka said:
    Could you try to open SEGGER directly and load your nRF projects instead of going via the "Open Segger Embedded Studio" in Toolchain manager?

    -Priyanka

  • 0 in reply to Priyanka

    If I uninstall all toolchain versions that reference VS Code, then the script runs. 

    SES does not appear in the Windows start menu since it was installed through Toolchain Manager, so the only way to start it (easily) is from Toolchain Manager. 

    Existing projects can be opened; however, I still see the JSON error when trying to create a new project through the "File | Open nRF Connect SDK project" if any NCS versions for VS Code are present.

    I am at a point where I can proceed with what I need on the older version, so I'm no longer stopped.

  • 0 in reply to brec

    In case of any further queries, I would suggest you to open a new ticket, in order to keep Devzone clean and help other seekers in the future. Slight smile

    The problem you face happens because we no longer support SEGGER and are moving with VSCode. But it should work with older versions if you open it separately. Understand that opening via Toolchain is easier, but there's a problem with the zephyr files if you do that, which causes the JSON error. Hope this helps.

    -Priyanka

  • 0 in reply to Priyanka

    I thought about creating a new ticket but wanted to leave the history here. I'm now trying to start using the latest version of the SDK V2.5.1 which obviously uses VS Code.

    However the problem still exists that when I load the new SDK, I can no longer use Segger, which makes things very problematic.

    The error is unable to parse json string.

    Things have changed, I noticed the post where a shortcut was created to load Segger directly from the bin directory.

    This did allow Segger to open the project, however it wouldn't compile, giving the following error:

    I had to once again remove the latest SDK V2.5.1 then it compiled as expected.

    This makes it very difficult to try and upgrade our software using the new SDK, when we are unable to abandon Segger at the moment.

    Help would be very much appreciated please.

Related
Terms of service