Segger Support missing in 2.0

[hiteshk014]

Hi Team,

We cloned NCS V2.0.0 and we observed segger_embedded_studio is missing from toolchain folder 

I Nordic recommending to use VS Code ?

Also we observed folder structure is changed toolchain folder is moved outside V.2.0

can you please share details on above points?

Thank you

[Einar Thorsrud]

Hi,

We cloned NCS V2.0.0 and we observed segger_embedded_studio is missing from toolchain folder 

I Nordic recommending to use VS Code ?

Yes, the combination of nRF Connect SDK and Segger Embedded Studio was not optimal, so we decided to develop a set of plugins for VS Code instead, nRF Connect for VS Code. This is the IDE that is supported and recommended with nRF Connect SDK 2.0.0, and will be used in the foreseeable future. If you have old nRF Connect SDK projects based on Segger Embedded Studio I suggest you take a look at Migrating from other IDEs to VS Code.

Also we observed folder structure is changed toolchain folder is moved outside V.2.0

can you please share details on above points?

In nRF Connect SDK 2.0.0, the Zephyr SDK toolchain replaces the GNU ARM Embedded toolchain (see nRF Connect SDK v2.0.0 Release Notes). The folder structure of the toolchain distributed by the toolchain manager is also different, as you noticed.

[hiteshk014]

Hi Einar,

Thank you for quick response,

We have a query, Is there any Cybersecurity updates in updated version ? can we continue with 1.9.1??

Thank you,

[Einar Thorsrud]

Hi,

I am not aware of any critical issues in 1.9.1 that has been fixed in 2.0.2. (There are many updates though, and in wide sense many aspects are security related, so I am sure there will be things that are improved compared to 1.9.1).