topic Re: SDK problem in S32 Design Studio for ARM 2.2 in S32 SDK

SDK problem in S32 Design Studio for ARM 2.2

1040180003 — Wed, 05 Feb 2020 04:54:03 GMT

Hello,

As to the problem I met: Errors in official example

I reinstall the S32DS. This time I use the latest version "S32DS_ARM_Win32_v2.2.exe".

After installation, I have not installed any patches, like "update11".

But when I try to create a new project, I cannot choose any SDKs. Please see the picture below:

I think there is already a SDK installed in my S32DS:

Can anyone help me, why can't I choose "RTM SDK 3.0.0" in my project?

Thanks!

Re: SDK problem in S32 Design Studio for ARM 2.2

jiri_kral — Wed, 05 Feb 2020 11:07:53 GMT

Hi,

you probably chose Standard S32DS toolchain for ARM when you created new project.. Please select ARM Bare-Metal 32-bit Target Binary toolchain.

Jiri

Re: SDK problem in S32 Design Studio for ARM 2.2

1040180003 — Wed, 05 Feb 2020 12:11:18 GMT

Thanks Jiri.

Yes, you're right.

When I choose the "ARM Bare-Metal 32-bit Target Binary toolchain", I can see the SDK 3.0.0.

But In this way, I will encounter the previous problem again：What are the differences between different toolchains?

When the "ARM Bare-Metal 32-bit Target Binary Toolchain" is used，then I cannot find the "CLOCK_SYS_Init" function in the "clock_manager".

Do you know why?

Thank you again!

Re: SDK problem in S32 Design Studio for ARM 2.2

jiri_kral — Wed, 05 Feb 2020 12:47:37 GMT

Hi,

this is very interesting question - I didn't realize yet that the function set is different. More strange thing is, that in Examples is used CLOCK_SYS_Init(...) but clock manager component offers only CLOCK_DRV_Init(...). To be honest - have no idea why is this component acting this way. So, I'll move your thread into S32 SDK community space. Someone from SDK team will answer your question.

Jiri

Re: SDK problem in S32 Design Studio for ARM 2.2

1040180003 — Thu, 06 Feb 2020 03:15:28 GMT

Ok thank you！

I wait for your message.

Re: SDK problem in S32 Design Studio for ARM 2.2

raresvasile — Thu, 06 Feb 2020 12:05:53 GMT

Hi,

The CLOCK_SYS_* API was deprecated, this is why it was removed from the list.

It can still be used, but we recommend using CLOCK_DRV_* functions.

Thank you,

Rares

Re: SDK problem in S32 Design Studio for ARM 2.2

1040180003 — Thu, 06 Feb 2020 15:17:41 GMT

Hi, Rares

Thanks for your answer.

But I found that most of the official examples use these two functions to initialize:

CLOCK_SYS_Init(g_clockManConfigsArr, CLOCK_MANAGER_CONFIG_CNT, g_clockManCallbacksArr, CLOCK_MANAGER_CALLBACK_CNT);
CLOCK_SYS_UpdateConfiguration(0U, CLOCK_MANAGER_POLICY_FORCIBLE);

Can you provide some new examples, which use "CLOCK_DRV_* functions" ?

Give me some guidance.

Thank you!

Re: SDK problem in S32 Design Studio for ARM 2.2

raresvasile — Thu, 06 Feb 2020 15:55:49 GMT

Hi Lu,

The sequence:

CLOCK_SYS_Init(g_clockManConfigsArr, CLOCK_MANAGER_CONFIG_CNT, g_clockManCallbacksArr, CLOCK_MANAGER_CALLBACK_CNT);
CLOCK_SYS_UpdateConfiguration(0U, CLOCK_MANAGER_POLICY_FORCIBLE);

can be replaced with:

CLOCK_DRV_Init(&clockMan1_InitConfig0);

Best regards,

Rares

Re: SDK problem in S32 Design Studio for ARM 2.2

m_mishrikey — Tue, 19 May 2020 02:56:01 GMT

I would recommend following:

1) Update SDK examples to match 3.0.2 command set. Presently the examples utilize the deprecated functions, but the SDK does not include those.

2) S32DS should really make it clear that 3.0.2 is the version being used. If you install S32DS for ARM 2.2, it comes with 3.0.2, but as in the screenshots above the user only sees 3.0.0 listed. This is super confusing.