Library heap not functional when migrating from SES 5.70a to SES 7.32

RE: Library heap not functional when migrating from SES 5.70a to SES 7.32

Vidar Berg — Mon, 20 Nov 2023 10:18:00 GMT

Hello,

This is the first time I'm hearing of issues with license activation on older SES versions, but it's good to hear that you have a way to get around this issue. Yes, there can be other potential unreported issues with using version 7.32

Best regards,

Vidar

RE: Library heap not functional when migrating from SES 5.70a to SES 7.32

jmoraal — Mon, 20 Nov 2023 08:54:12 GMT

Hi Vidar

Our only concern with 5.70a is the license. We've found that the Nordic SES licence doesn't activate it anymore. We have workaround it by installing 7.32 and activating it. Then 5.70a is also activated

I actually thought I was missing something trivial when migrating to 7.32, but your comment makes me think that it is not the case. And I also think this is only the first runtime issue, and there are many more hiding behind it. For now we can close this case

RE: Library heap not functional when migrating from SES 5.70a to SES 7.32

Vidar Berg — Fri, 17 Nov 2023 13:42:44 GMT

Hello,

Unfortunately, my recommendation is to stay on version 5.70a unless there is a strong need to upgrade. Segger removed the Embedded Studio v4 runtime library from SES in the v6.20 release, which is the library our SDK has been developed and verified with. From v6.20 and later, you are forced to use their emRun l library instead. This is the main reason most of the SDK examples will fail to build out of the box with the new versions (v6.20 and above). If I recall correctly, there have also been instances where the newer GCC versions have led to runtime errors.

Let me know if you still want to migrate to SES 7.32. In that case, I can try to investigate why you can't allocate memory from heap.

Best regards,

Vidar