• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 8 replies
  • Answers 7 answers
  • Subscribers 99 subscribers
  • Views 1432 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[FAQ] AM6442, AM6441, AM6422, AM6421, AM6412, AM6411 and AM2434, AM2432, AM2431 (ALV, ALX) Custom board hardware design – I2C interface

Lavanya M R
Intellectual 1590 points
Part Number: AM6442
Other Parts Discussed in Thread: AM62A7, AM6412, AM6422, , AM2434, SK-AM64B

Hi TI Experts,

I have the below queries regarding the I2C interface:

  1. Need information on the number of I2C interfaces available
  2. Termination of I2C interfaces when used as I2C interface and not used as I2C interface
  3. Any additional recommendations / Guidelines
  4. Any concerns on Interfacing SoC Non-Failsafe I2C to devices that are powered before the SoC- Ex PMIC 
  5. Any exception that are required to be considered when using the I2C interfaces
  6. Can the I2C interface be used to interface with devices supporting SMBus or PMBus 

Let me know your thoughts.

  • +1
    TI__Intellectual 1590 points

    Hi Board designers, 

    Refer below inputs for the I2C interface related queries.

           1. Need information on the number of I2C interfaces available

    The processor supports x6 (six, ALV) and x3 (three, ALX) multicontroller Inter-Integrated Circuit (I2C) controllers. Each I2C controller was designed to be compliant to the Philips I2C-bus specification version 2.1. However, the device IOs are not fully compliant to the I2C electrical specification.

    Open Drain buffer type I2C interface - I2C0 and MCU_I2C0 (ALV)

    These I2C interfaces are Open drain type IOs. These I2C interfaces are fail-safe IO terminals.

    The rise and fall times of the I2C signals connected to these ports must not exceed a slew rate of 0.08 V/ns (or 8E+7 V/s). This limit is more restrictive than the minimum fall time limits defined in the I2C specification. Therefore, it may be necessary to add additional capacitance to the I2C signals to slow the rise and fall times such that they do not exceed a slew rate of 0.08 V/ns.

    Refer below 

    AM62A7 Reference 

    Reference: AM64 SK schematics

    LVCMOS buffer type I2C interface - I2C1, I2C2 (ALV), I2C3 and MCU_I2C1 (ALV)

    These I2C interfaces are LVCMOS IO types. LVCMOS IOs being used on these ports are connected such they emulate open-drain outputs.

             2. Termination of I2C interfaces when used as I2C interface and not used as I2C interface.

    Open Drain buffer type I2C interface - I2C0 and MCU_I2C0 (ALV)

    Refer 6.4 Pin Connectivity Requirements in the device specific datasheet.

    These interfaces are recommended to be terminated when configured as I2C or as GPIO. When the IO is configured as input and being driven by a push-pull input from power-up the termination can be depopulated

    LVCMOS buffer type I2C interface - I2C1, I2C2 (ALV), I2C3 and MCU_I2C1 (ALV)

    When configured as I2C interface, pullups are recommended. Since these IOs are LVCMOS type, the pullups are recommended to be connected with the shortest stub. When configured as GPIO, based on the use case an external pull can be provided or the internal pulls can be used.

           3. Any additional recommendations / Guidelines

    Refer below section of the device specific datasheet.

    7.7.1 I2C Open-Drain, and Fail-Safe (I2C OD FS) Electrical Characteristics

           4. Any concerns on Interfacing SoC Non-Failsafe I2C to devices that are powered before the SoC- Ex PMIC 

    Are the attached PMIC IOs true open-drain I2C IOs?  If so, are the pull-up resistors associated with this I2C port powered by the same power supply that is used to power SoC I2C Example I2C0 IOs?  We should not have a fail-safe problem if the answer to both questions is yes.

     Is there anything else connected to these I2C signals that could source a potential to the I2C0 pins before the IOs are powered? 

    We are only concerned with fail-safe if there is a possibility for the attached devices to apply a potential to the SoC IOs before they receive power.  We do not have any fail-safe concern if that is not possible.

           5. Any exception that are required to be considered when using the I2C interfaces. 

    Refer section 7.10.5.9 I2C of the data sheet.

    Read through the Exceptions section for I2C1, I2C2 (ALV), I2C3 and MCU_I2C1 (ALV)+ Exceptions section for I2C0 and MCU_I2C0 (ALV)

    Note: 
    Refer below documents during the I2C interface design.

    Hardware Design Guide for AM6442, AM6422, AM6412 and AM2434 Processors

    https://www.ti.com/lit/an/sprad67a/sprad67a.pdf

    AM64x and AM243x Schematic Design and Review Checklist

    https://www.ti.com/lit/an/spracu5c/spracu5c.pdf

    6.Can the I2C interface be used to interface with devices supporting SMBus or PMBus 

    The I2C module implemented in these processor families does not support SM Bus or PM Bus

    Regards,

    Lavanya M R.

  • 0 in reply to Lavanya M R
    TI__Guru**** 192089 points

    Hi Board designers, 

    Refer below inputs for  I2C pullup calculation
    www.ti.com/.../slva689.pdf

    The board designer is responsible for selecting a pull-up value that meets the rise time requirements for their specific system implementation.
    The I2C signal trace capacitance will vary based on their PCB design which means the pull-up value may need to be adjusted to achieve the appropriate rise time. A large pull-up value will produce a slow rise time, that will be easy to pull below VIL max. A small pull-up value will produce a fast rise time, that may be difficult to pull below VIL max. The I2C standard defines a range for the expected rise and fall times. However, some of the devices being connected to the I2C signal may have their own requirements and characteristics.
    For example, our I2C ports implemented with the “I2C OD FS” IO cells have a very restrictive maximum input slew rate when operating at 3.3V and this limit
    needs to be considered when selecting a pull-up resistor value. Another example, our I2C ports implemented with the “LVCMOS” IO cells will violate the minimum fall time defined in the I2C standard when driving the signal low. Note: This last example is not a function of pull-up value and was only mentioned for completeness. The board designer must also consider the output drive strength of each device driving the I2C signal to ensure it is able to pull the signal low enough for it to be considered a valid logic low for each device connected to the signal. Some devices may not be able to pull the signal below the lowest VIL max of the attached devices if the pull-up value is too small.

    Regards,

    Sreenivasa

  • 0 in reply to Kallikuppa Sreenivasa
    TI__Guru**** 192089 points

    Hi Board designers, 

    The current circuit diagram is as shown in ②, and if there are no issues with this, I would like to proceed as is.

     We have updated or will be updating the pin connectivity requirements to allow the unused open drain I2C interface to be connected to VSS through a resistor. Customer connected  the unused open drain interface directly to ground on their board.

    Any thoughts?

    This is okay since the IO cell is implemented with a true open-drain output buffer. Therefore, it is not possible for these pins to be driven high.  So there is no chance of contention.

    This should not be done with the I2C ports that use LVCMOS or SDIO IO cells since these IOs are implemented with push-pull output buffers that may accidently be driven high.

    (+) [FAQ] AM6412: unused MMC0_CLK - Processors forum - Processors - TI E2E support forums

    Your concern with respect to the I2C0_SCL pin is already addressed in the Connectivity Requirements table. Note: The description for the I2C_SCL connectivity will be updated in the next revision of the datasheet to include the option of pulling the pin high or low, by saying, "Each of these balls must be connected to the corresponding power supply or VSS through separate external pull resistors to ensure the inputs associated with these balls are held to a valid logic high or low level as appropriate for the selected signal function."

     Regards,

    Sreenivasa

  • 0 in reply to Kallikuppa Sreenivasa
    TI__Guru**** 192089 points

    Hi Board designers, 

    Refer below inputs on I2C current:

    "I2C OD FS" and "LVCMOS" using I2C exist minimum output current specification, but not exist maximum specification.
    What value is the maximum output current specification?
    I have a additional question. When I use Pin C18 / B19 as I2C1, Is the output current specifications of Pin C18 / B19 same to "LVCMOS"?

    We indirectly define a maximum output current, by defining our minimum current which the output buffer can sink or source while maintaining a valid Vol or Voh. I will try to explain below.
    We define a maximum low output voltage and a minimum high output voltage. These values are typically set to industry standard values. The output buffer will have internal voltage drop that increases as output current increases. At some point the voltage drop in the output buffer will cause the voltage to rise above the maximum Vol or drop below the minimum Voh limits defined in the datasheet. The actual output current where this occurs varies from one device to another due to Process, Voltage, and Temperature (PVT) differences. Therefore, we define the minimum value of this output current range in the datasheet that will always provide a valid Vol and Voh. These parameter are named Low Level Output Current and High Level Output Current in the datasheet.
    These minimum output current values defined in the datasheet actually defines the maximum output current your product should expect for maintaining a valid Vol or Voh across all PVT variations.


    I didn't see your other question until I sent my first reply. Yes, pins C18 and B19 are implemented with LVCMOS IOs.
    The Buffer Type column in the Pin Attributes table can be used to determine which IO type was implemented for a specific pin.
    Note: I2C ports implemented with LVCMOS IOs will not be fully compliant to the I2C specification. Only I2C0 and MCU_I2C0 ports are implemented with the I2C OD FS IOs, which are compliant to the I2C specification.

    I understood the minimum output current specification. Regarding 2nd question,
    Is it correct that the low level output current specifications of Pin C18 / B19 as I2C1 is 5mA ?

    Yes. It is 5mA when operating at 3.3V , and 3mA when operating at 1.8V.
    FYI, I added a note to each Electrical Characteristic table that explains the IOL and IOH parameters. See the note below.
    The IOL and IOH parameters define the minimum Low Level Output Current and High Level Output Current for which the device is able to maintain the specified VOL and VOH values. Values defined by these parameters should be considered the maximum current available to a system implementation which needs to maintain the specified VOL and VOH values for attached components.
    Hopefully, the note above will clarify what is being defined by these parameters.

    Regards,

    Sreenivasa

  • 0 in reply to Kallikuppa Sreenivasa
    TI__Guru**** 192089 points

    Hi Board designers, 

    Refer below regarding I2C interface clock frequency 

    Refer to the Pin Connectivity Requirements section of the processor-specific data sheet. A pullup (4.7kΩ, adjust after testing) is recommended. When do i adjust the pullup.

    The I2C interface pullup and the capacitive loading affect the I2C clock slew.

    In use cases where the measured clock frequency does not match the configured clock frequency, the recommendation is to adjust the pull (stronger pullup - reduce value) and measure the clock frequency.

    Regards,

    Sreenivasa

  • 0 in reply to Kallikuppa Sreenivasa
    TI__Guru**** 192089 points

    Hi Board designers, 

    Refer below regarding I2C slew rate control RC

    AM6442: SK-AM64B purpose of RC filter

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1362478/am6442-sk-am64b-purpose-of-rc-filter

    RC filter cutoff frequency is 338KHZ with 4.7K pullup, 62E series resistor and 100pF. and I2C operating frequency is 400KHZ. Thus I2C signal not reach to 3.3V lavel.

    We used 4.7K pullup, 62E series resistor and 10pF. and not observer any concern on VIL & VIH. 

    Does TI have any concern with 4.7K pullup, 62E series resistor and 10pF? if not then we are ok to go...

    Below is requested data. 

    Regards,

    Sreenivasa

  • 0 in reply to Kallikuppa Sreenivasa
    TI__Guru**** 192089 points

    Hi Board designers, 

    Refer below regarding I2C clock stretching

    https://www.ti.com/lit/an/sbaa565/sbaa565.pd

    6.2 Clock Stretching In some I2C target devices, there are situations that the target device controls the SCL serial clock. In those cases, the target device can slow down the communication. This process is known as clock stretching. In general, the SCL line and therefore the I2C clock rate, is controlled by the controller. However, there are instances where the target device is unable to comply with the clock rate. For example, the target device requires extra time to process a command or send data. In such cases, the target device can slow down the communication through clock stretching.

    The clock stretching depends on the Bus capacitance.

    In case the measured speed does not match the set I2C speed, verify the I2C clock slew and adjust the slew by varying the pullup on the I2C bus.

    Regards,

    Sreenivasa