S32K中的主题 SDK Migration

SDK Migration

vmhb — Fri, 25 Oct 2024 09:46:37 GMT

Initially some bare metal projects were constructed for S32K344 evaluation boards and our own S32K324 based boards using S32DS 3.5 and essentially and SDK version of 3.0.0. We would like to update the development environment to used SDK version 4.0.0. The tools have been updated and we are able to build and run projects for the S32K344 boards. However if we attempt any form of automated migration to 4.0.0, even though the project settings say platform SDK 3.0.0 does not exist, the project gets messed up big time. Source files deleted, project settings changed. Net result event though we can eventually build the project it does not run on the target properly.

For our in house S32K324 based boards we cannot even build the generated sources from the mex files. The general issue seem to be that Siul2_Port says that Mscr is not configured in the pins tool. Had the same issue with the S32k344 projects but this was resolved when the functional group name was updated in the pins configuration. For some reason this was not the same for the S32K324 projects.

Are there any documents out there on general migration of S32DS 3.5 projects from SDK 3.0.0 to 4.0.0?

Re: SDK Migration

VaneB — Fri, 25 Oct 2024 21:25:06 GMT

Hi @vmhb

I am afraid that the most viable option is to generate a new project with the corresponding software version and then copy the application source files from your pre-existing project as well as any customizations you made to the project properties.

Sorry for the inconvenience.

BR, VaneB

Re: SDK Migration

vmhb — Tue, 29 Oct 2024 16:13:51 GMT

Thank you for the feedback.

Managed to create a new 4.0.0 project for S32k344 processor. However when following the same process for S32K324 using just one core I still get an error with Siul2_port. Can anyone advise as how to overcome this?

Re: SDK Migration

vmhb — Tue, 29 Oct 2024 16:43:09 GMT

Seems to be tied to the pin configuration, rather than processor type. In the S32K344 projects PTA0 is connected, in the S32K324 projects PTA0 is not connected. As PTA1 is connected the PortPin Mscr value of 1 is valid. This was not the case with earlier versions of the software.

I would like to understand what the correct setting is here as I can define PTA0 in the PINS tool, even though it is not connected and set PortPin Mscr to 0 or leave PTA0 undefined and set PortPin Mscr to 1 as PTA1 is defined?

Can anyone explain this change in behaviour of the tools and why, it seems, this value is now some kind of index to the first pin defined?

Re: SDK Migration

VaneB — Wed, 30 Oct 2024 19:49:29 GMT

Hi @vmhb

For RTD version 4.0.0 onwards it is necessary to configure the pins in the Pins tool and also add the pin in Siul2_Port in the Pheripheral tool and assign the corresponding Mscr.

Re: SDK Migration

LBowen — Thu, 31 Oct 2024 02:10:27 GMT

你是不是把自动生成的一个引脚gpio0给删除了，不要删除，不用去管那个引脚，这个错误就会消失

Re: SDK Migration

vmhb — Thu, 31 Oct 2024 08:02:24 GMT

So the best way seems to be to keep the automatically generated PTA0, even though in my case this pin is not connected.