S32k314 I2C

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32k314 I2C

Jump to solution
1,958 Views
anoop_r
Contributor II

Hi,

We are using a platform that has an S32K314 controller and we are trying to bring up the I2C, for that, we have used the example "I2c_IP_LPI2C_Transfer_S32K312" as a reference and ported the codes to our platform but the issue that we saw is that there is no clock pulse generating in the SCL pin while probing through the DSO.

So I also tried to build the example code "I2c_IP_LPI2C_Transfer_S32K312" and tried to implement it on the S32k312 eval board.

I verified the I2C in the S32k312 eval board with the RTD example.
I did the test in RTD-2.0.1. and I tried the example in two ways and the following are the observations:
  1. I have given a 4.7k pullup in both SCL & SDA.
    I have tried to send data to the slave in a loop and each time I could see the pulses in both SCL and SDA.
  1. I have given a 4.7k pullup in both SCL & SDA. In the next step, I have removed the connection between the SCL & SDA of the master and slave. In that test, I didn't get the pulses on the master side.
In our hardware also we are seeing the second scenario, there is no pulse generating in the SCL and SDA while sending data.
 

I have followed the description given by giving a 4.7K pull-up in both SCL-VDD and SDA-VDD.

Can anyone please help us bring up the I2C in our S32k platform?

Regards 

Anoop

0 Kudos
Reply
1 Solution
1,951 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello Anoop,

The issue seems strange. When you remove the connections, are the pull-ups still connected to the SDA / SCL of the Master?

In your S32K314 project, I would check the SIUL2 MSCR registers whether the PTD13, PTD14 pins are muxed to LPI2C0, and whether the output / input buffers (OBE, IBE) are set.

You could also add the internal pull-up on those pins (PUE, PUS).

 

Regards,

Daniel

 

 

View solution in original post

0 Kudos
Reply
5 Replies
1,907 Views
anoop_r
Contributor II

Hi Daniel,

Thanks for responding to this and sorry for the delay.

In the device, I have added the pullup in both SCL & SDA on the master side even when the loopback is removed.

I also added the internal pull-up on those pins (PUE, PUS).

Screenshot (75).pngScreenshot (76).png 

Regards

Anoop

0 Kudos
Reply
1,883 Views
anoop_r
Contributor II

Hi Daniel,

Here is the drive link for the I2C project which I created.
0 Kudos
Reply
1,857 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi Anoop,

I just tested it on S32K344 (S32K314 in lockstep) becasue I don't have any decoupled S32K344 (S32K314).

Without any modification and without any external pullups, it works.

This is the signal on PTD13, PTD14.

danielmartynek_0-1683791567339.png

SCL HIgh (MCCR0_CLKHI) is too short, but it works.

I think there might be an issue in your HW.

 

Best regards,

Daniel

 

0 Kudos
Reply
1,887 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello Anoop,

Can you share the project so that I can test it on my side?

 

Thanks,

BR, Daniel

 

0 Kudos
Reply
1,952 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello Anoop,

The issue seems strange. When you remove the connections, are the pull-ups still connected to the SDA / SCL of the Master?

In your S32K314 project, I would check the SIUL2 MSCR registers whether the PTD13, PTD14 pins are muxed to LPI2C0, and whether the output / input buffers (OBE, IBE) are set.

You could also add the internal pull-up on those pins (PUE, PUS).

 

Regards,

Daniel

 

 

0 Kudos
Reply