Finally understanding the nature of SES version 5.42a

RE: Finally understanding the nature of SES version 5.42a

Bret Foreman — Fri, 16 Dec 2022 22:23:10 GMT

So, if I bought the "regular edition" I would receive version 7.10 from Segger. But none of the SDK examples will run on that version. It's pretty hard to do development without access to working examples for each subsystem of the chip. Who would be on the hook to port the examples to 7.10?

RE: Finally understanding the nature of SES version 5.42a

Vidar Berg — Fri, 16 Dec 2022 22:19:38 GMT

They will not support you with the Nordic edition, but they should provide support for the regular edition. Maybe this was based on some misunderstanding?

RE: Finally understanding the nature of SES version 5.42a

Bret Foreman — Fri, 16 Dec 2022 22:14:31 GMT

I have the free license, of course. But who is supporting the IDE? He was pretty clear that they DO NOT support version 5.42a.

RE: Finally understanding the nature of SES version 5.42a

Vidar Berg — Fri, 16 Dec 2022 22:12:33 GMT

It seems like he thought you were using the Nordic edition of SES. That would explain his response. But you are not. You should still get the free license as before.

RE: Finally understanding the nature of SES version 5.42a

Bret Foreman — Fri, 16 Dec 2022 22:06:42 GMT

Well, I asked them if I could buy their latest SES and have the Nordic SDK supported by them and they said no. I asked if they could support 5.42a if I bought a Segger license and they said no to that too. So it looks like there is no development path starting with the free version of SES and graduating to the paid/support version.

This is quite different from the old Keil model where you could buy a license and get support from them. I'm not really complaining about using VS Code, just pointing out that SES is not as one would expect from the previous path with Keil.

RE: Finally understanding the nature of SES version 5.42a

Vidar Berg — Fri, 16 Dec 2022 22:01:43 GMT

Hello,

It is correct that there was a Nordic edition of SES which was distributed by us, but it was only for use with the nRF connect SDK (has since been replaced with our VS code extension). For our nRF5 SDK we have always directed users to download it from Segger: https://www.nordicsemi.com/Products/Development-tools/segger-embedded-studio

Version 5.42a is recommended for use with nRF5 SDK 17.1.0 because it was the version we used during the release testing, but any version between 5.42a and 6.20 is likely to work. In v6.20 they removed the legacy Embedded Studio Runtime Library used in our examples and is the main reason our examples will not build out-of-the-box with SES v6.20 and later.

Best regards,

Vidar