SEGGER Embedded studio version to use with nRF5 SDK v17.*?

[samsam]

Ambiguous information about SES version to be used in Nordic documentation: mentioned install the most recent release … or Embedded Studio for ARM (version 3.30 or later).

Currently most recent version ES for ARM that Segger offers is V7.32a, but is marked as (legacy)

While there is a newer version ES V8.10b (that supports and ARM). I already asked Segger support, but the forward me back to Nordic support, so my question will be which version to use for developing with nRF5 SDK v17.*?   If it is ES V8.10b – is the free commercial license for developments with nRF still valid with it?

 

BTW: Is there a way to use VS Code with nRF5 SDK (I think I saw long time ago  some tutorials from Sparkfun)?

Thanks

[Vidar Berg]

Hi,

I apologize for the ambiguity in our documentation. We recommend using the SES version specified in the SDK release notes:

 

v6.20 introduced some breaking changes, as I mentioned in this post:  RE: Library heap not functional when migrating from SES 5.70a to SES 7.32 

BTW: Is there a way to use VS Code with nRF5 SDK (I think I saw long time ago  some tutorials from Sparkfun)?

We only offer official support for VS Code development with our nRF Connect SDK. While it is possible to use VS Code with the nRF5 SDK, doing so would require setting up your environment from scratch and use third-party plug-ins for debugger integration, etc.

Best regards,

Vidar

[samsam]

Hello, thank you very much – I understand nRF5 is in maintenance mode, but isn’t possible to fix with information that you just gave me (SES v5.42a for nRF5 SDK v17.1.0 -> look at  nRF5_SDK_***\documentation\release_notes.txt) at least in the web page for Installing SEGGER tools that comes from either of those links:

https://infocenter.nordicsemi.com/topic/ug_gsg_ses/UG/gsg/install_segger_tools.html

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_gsg_ses%2FUG%2Fgsg%2Finstall_segger_tools.html

Thanks

[Vidar Berg]

Hello, 

Thank you for providing the documentation links. Yes, we should update the documentation to reflect this. I will report this feedback internally.