I2C IBDF register setting

[yanis-waabi]

Hello,
this is a two part post regarding some issues & quirks i've noticed while working with the I2C for the S32G RTD + DesignStudio1:
I've been having trouble with the baud rate IBDF register. I'm using an input clock of 133Mhz to the I2C module from the clock tree, for most clocks IBDF settings, i see no response from attached I2C devices. However, with a decimal IBDF register setting of '73' (0x49),
I do see responses from attached devices. I set this value via the RTD SetBaudRate_Privileged function. But '73' in Design Studio shows an invalid baud rate (2MHz):
I'm trying to understand why this IBDF register value is working, and what the real baud rate of the unit is, and how to understand which IBDF register values are actually functional on my system, right now i've been performing baud scans of attached devices to see what works, which is not ideal.

Could you recommend an IBDF register value that would work with my clock settings. That would give a baudrate between 80 and 400 kHz ?

Secondly, I noticed in the RTD generated code, the glitch filter arrays are misused when trying to calculate the baudrate: This is in I2c_Ip.c. See how the glitch filter array is used when the glitchfilter is disabled in the i2c instance.

[alejandro_e]

Hello @yanis-waabi,

 
Thanks for contacting NXP support. To understand your problem better, can you provide more details about your setup? Please provide the following:

• The version of the S32 Design Studio you are using
• Are you using the default compiler and optimization options from S32 Design studio?
• Are you using S32G2 or S32G3?
• The version of the RTD's you are using.
• Are you using a Custom board or an RDB/EVB board?
• Are you running a multicore setup? This is, with applications running in both the A53 and M7 cores?
• Are you using S32 Debug Probe or Lauterbach to debug your issue?
• Can you describe the steps you followed to generate the problematic code in I2c_Ip.c
  • If possible share your project and point out the problematic part.
  • Please also tell me the exact name of the variable and functions you are seeing
• About the IBDF register, can you share the project in which you see this problem? this way I can analyze it better.

If you are not comfortable sharing information in this public post, you can open a private support ticket from the NXP main page:

 

 

One finial topic, I saw that there is a very similar private ticket already open, from one of your colleagues, would like to keep the conversation on this community post or follow the discussion with your colleague internally and cancel this post?

Thanks in advance for the information and please let me know hoy you want to proceed.