Installing new SDK causes automation project migration

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Installing new SDK causes automation project migration

Jump to solution
249 Views
sstelmak
Contributor III

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?

0 Kudos
Reply
1 Solution
190 Views
sstelmak
Contributor III

That works, thank you

View solution in original post

0 Kudos
Reply
2 Replies
191 Views
sstelmak
Contributor III

That works, thank you

0 Kudos
Reply
226 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @sstelmak 

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

0 Kudos
Reply