LPI2C and FlexIO_I2S Clock Initialization API

MohitManvar — Tue, 22 Aug 2023 13:27:48 GMT

Hello,

Board: S32K142 Eval board

In sample codes of LPI2C and FexIO_I2S, the APIs used for initializing clock are different.

What is the significance for both APIs and when can each of them be used?

The issue we are facing is, when we are trying to combine both peripheral configurations (i2c and i2s), it is now working. No clocks generated for i2c (scl) or i2s (sclk)

Could this be because of the use of different APIs for Clock init?

Or is there any other configuration impacting the functionality

Sample code snippets below:

Re: LPI2C and FlexIO_I2S Clock Initialization API

Robin_Shen — Wed, 23 Aug 2023 12:06:46 GMT

Sorry for the inconvenience we bring you!

The CLOCK_SYS_* API was deprecated
CLOCK_SYS_Init();
CLOCK_SYS_UpdateConfiguration();
can be replaced with:
CLOCK_DRV_Init(&clockMan1_InitConfig0);

Similar topics are discussed in SDK problem in S32 Design Studio for ARM 2.2

Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" 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.
-------------------------------------------------------------------------------

topic LPI2C and FlexIO_I2S Clock Initialization API in S32 SDK

LPI2C and FlexIO_I2S Clock Initialization API

Re: LPI2C and FlexIO_I2S Clock Initialization API