1891676_en-US

Installing new SDK causes automation project migration

I have S32 DS 3.5 and S32K344 micro.

It was originally set with SDK/RTD V2.0.0

It became necessary to add SDK 4.0.0, so that one project would migrate to 4.0.0 and another project stays at 2.0.0

SDK 4.0.0 gets installed properly and both SDKs appear under project settings.

I was expecting that by attaching/detaching SDK I can control which SDK current project would use.

However those "attached/detached" check-boxes seems to have no effect.

Regardless of that all projects would use 4.0.0 and it is was not possible to keep one project with 2.0.0

Is there a way to avoid that?

Re: Installing new SDK causes automation project migration

That works, thank you

Re: Installing new SDK causes automation project migration

S32DS 3.5 can keep one RTD version only (plus additional extensions packages/stacks).

The solution is to install more S32DS instances. Just use different folder name of S32DS like:

c:\NXP\S32DS.3.5_RTD_200\

c:\NXP\S32DS.3.5_RTD_400\

And install corresponding RTD package to those instances.

Regards,

Lukas