Installing new SDK causes automation project migration

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Installing new SDK causes automation project migration

ソリューションへジャンプ
270件の閲覧回数
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 解決策
211件の閲覧回数
sstelmak
Contributor III

That works, thank you

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
212件の閲覧回数
sstelmak
Contributor III

That works, thank you

0 件の賞賛
返信
247件の閲覧回数
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 件の賞賛
返信