S32 Design StudioのトピックS32DS SDK Migration

S32DS SDK Migration

durga_choudhury — Tue, 03 Jun 2025 21:02:16 GMT

I have a project for S32K148 that was created with S32SD for ARM v 2.2. The project compiles and runs as expected. It uses SDK 'S32SDK_S32K1xx_RTM_3.0.0'

In my attempt to upgrade to S32DS v 3.4 (the eventual goal is to upgrade to the latest v 3.6.2, but I used 3.4 as a interim stepping stone so that I can use the automatic migration feature of the SDK), I did the following:

1. Installed SDK 'S32_SDK_S32K1xx_RTM_4.0.2'

2. Installed S32DS v 3.4

3. Opened the project with S32DS v 3.4

4. Right clicked on the project and clicked 'Migrate'

The migration tool correctly identified SDK_S32K1xx_RTM_4.0.2 as the available migration and I chose all the default options. This created (among other things) a new directory called 'board' and created some new .c files (such as 'peripherals_SPI0.c') that has no actual source code except an include file with the same name (e.g. peripherals_SPI0.h). The problem is that these header files don't seem to exist, either in the project or in the SDK.

What am I missing?

Re: S32DS SDK Migration

Robin_Shen — Thu, 05 Jun 2025 06:58:22 GMT

Video: Migrating S32K1 projects from S32DS for ARM and SDK 3.0.x to S32DS 3.4 and SDK 4.0.2

Did you click Open S32 Configuration and then click Update Code?

Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

Re: S32DS SDK Migration

durga_choudhury — Thu, 05 Jun 2025 15:47:58 GMT

Thanks for the hint and this fixed the issue. FWIW, the triangular exclamation in my case was green and the 'update code' button seemed to be greyed out, but clicking on it anyway solved the issue.

Also, as a feedback, the security settings on this site is way too tight, making me personally want to skip replying although that is not the intent. It asks me to re-verify that I am not a robot literally every 10 seconds, faster than what it takes me to type a line. Until this is fixed, I am probably going to stop responding when my issue has been fixed.