SES Version Compatibility

RE: SES Version Compatibility

CheMax — Tue, 06 Oct 2020 15:32:21 GMT

It's my pleasure. I actually spent a few days dealing with project compatibility issues after the upgrade.

Look, the main difference between 4 and 5 studio versions is only in the size of the generated firmware hex file. And only when using the proprietary linker and compiler from Segger. Otherwise, the list of changes is not significant.

RE: SES Version Compatibility

mchartier — Tue, 06 Oct 2020 14:44:57 GMT

Thanks for posting, you probably saved me many hours of frustration. I was going to try the latest SES v5.10 but now I will definitely stick to a version referenced in the nRF SDK release notes.

RE: SES Version Compatibility

CheMax — Tue, 06 Oct 2020 07:45:51 GMT

Hi,

Not certainly in that way. sometimes upgrading to a new version leads to interesting bugs. For example,problem with new projects for nrf52 ,my discussion of the problem on the Segger forum.

By the way, it also states that Nordic must provide an updated package (Nordic Semiconductor nRF CPU Support Package).

RE: SES Version Compatibility

Einar Thorsrud — Tue, 06 Oct 2020 07:07:21 GMT

The Nordic SES variant has support for configuring and building nRF Connect SDK projects, using Cmake and Kconfig etc. Other then that it is equivalent to the "normal" SES edition. The free SES license for Nordic targets applies to both SES variants.

RE: SES Version Compatibility

mchartier — Mon, 05 Oct 2020 20:50:27 GMT

Thanks, that does make sense. Do you know what is the difference between the standard Segger release of SES and the Nordic variant? I read the Nordic version has an extra menu option "Open nRF Connect SDK Project" which could be a nice benefit. Any others? Will the Segger licensing work the same with either version?

RE: SES Version Compatibility

Einar Thorsrud — Mon, 05 Oct 2020 19:32:14 GMT

Hello,

The release notes of every nRF5 SDK version specifies which version of SES (and other toolchains) has been used for release testing, and it could make sense to pick the same version. For instance you can see here that SDK 17.0.2 was release tested using SES 4.50. In most cases using a newer version should not cause any problems, though.