Installing new SDK causes automation project migration

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

Installing new SDK causes automation project migration

跳至解决方案
269 次查看
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 项奖励
回复
1 解答
210 次查看
sstelmak
Contributor III

That works, thank you

在原帖中查看解决方案

0 项奖励
回复
2 回复数
211 次查看
sstelmak
Contributor III

That works, thank you

0 项奖励
回复
246 次查看
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 项奖励
回复