SDK problem in S32 Design Studio for ARM 2.2

cancel
Showing results for 
Search instead for 
Did you mean: 

SDK problem in S32 Design Studio for ARM 2.2

Jump to solution
1,299 Views
1040180003
Contributor III

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:

pastedImage_2.png

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

pastedImage_3.png

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

Thanks!

Lu

1 Solution
765 Views
raresvasile
NXP Employee
NXP Employee

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

View solution in original post

8 Replies
765 Views
jiri_kral
NXP Employee
NXP Employee

Hi, 

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

pastedImage_1.png

Jiri

0 Kudos
765 Views
1040180003
Contributor III

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".

pastedImage_2.png

Do you know why?

Thank you again!

Lu

0 Kudos
765 Views
jiri_kral
NXP Employee
NXP Employee

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

765 Views
1040180003
Contributor III

Ok thank you!

I wait for your message.

Lu

0 Kudos
765 Views
raresvasile
NXP Employee
NXP Employee

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

765 Views
1040180003
Contributor III

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!

Lu

0 Kudos
766 Views
raresvasile
NXP Employee
NXP Employee

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

View solution in original post

765 Views
m_mishrikey
Contributor II

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.

0 Kudos