s32k3 i2c

[piyush1]

hello dear NXP team .....

i have configured this LPi2c0 as master and Lpi2c1 as slave but it doesn't work...i don't know how to it will communicate with each others....i have uploaded my project code here ...please check and edit necessary things in it and give me workable edited code from your side... 

[piyush1]

brother what i meant is i dont know which API's to call in main source file....so can you please put those API's and configurations which are needed in the project code which i have uploded here...so that i can understand and next time i can configure it by myself.

[VaneB]

Hi @piyush1 

To implement polling mode, use the blocking send and receive functions. For low-level drivers, these are named Lpi2c_Ip_MasterSendDataBlocking() and Lpi2c_Ip_MasterReceiveDataBlocking(). For high-level drivers, use I2c_SyncTransmit().

Additionally, I recommend consulting the S32K3/S32M27x I2C Driver Integration Manual and the User Manual included with the RTDs. These documents provide detailed information on the I2C driver, including its limitations, hardware and software requirements, usage instructions, and configuration guidelines. You can typically find these resources at a path similar to:

C:\NXP\S32DS.3.6.2\S32DS\software\PlatformSDK_S32K3\RTD\I2c_TS_T40D34M60I0R0\doc

[VaneB]

Hi @piyush1 

I have reviewed your code and configuration and would like to share a few observations.

The I2C clock source has been set to CORE_CLK, but the actual source is AIPS_SLOW_CLK. You can confirm this in the Clock Tree within the Clock Tool of ConfigTools or refer to Figure 75 in the S32K3xx Reference Manual, Rev. 11.

Also, when working in polling mode, I recommend separate devices for master and slave, as in this mode, the master continuously checks for the end of transmission or incoming data without interrupts, which can affect.

While there is not a dedicated example for your specific setup, there are two example codes available for S32K1 devices using the S32SDK for S32K1xx. These examples implement similar functionality and can serve as a helpful reference, as the I2C module is similar across these families.

BR, VaneB

[piyush1]

brother i didn't understand...can you please do corrections and update my code ang give me back so that i can understand the things ...

[VaneB]

Hi @piyush1 

Let me show you what I meant earlier. 

In the image below, you will see two sides:

• On the left, there is the clock source that is currently configured in your project.
• On the right, you will see the actual clock source being used by LPI2C0.

Now, about the separate project part. What I meant is that in polling mode, the master keeps checking for data or transmission events all the time. If you set up the slave in the same project, it might interrupt this constant monitoring, which could lead to missing some data. That is why it is better to keep them in separate devices when using polling mode.