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.

AM6412: Schmitt Trigger inputs - characteristics

Part Number: AM6412

Hi,

do you have electrical characteristics of the Schmitt-Trigger Inputs on AM64xx? Couldn´t find any in data sheet or TRM.

Thank you!

  • Every pin with hysteresis has a min voltage value published in the respective Electrical Characteristics table.

    Regards,
    Paul

  • Hi Paul,

    i expected to find this in the electrical characteristics. I assume it is on me... here is what I was doing:

     TRM (https://www.ti.com/lit/ug/spruim2b/spruim2b.pdf) page 130:

    Now I open the data sheet (https://www.ti.com/lit/ds/symlink/am6412.pdf), Ctrl-F: search for schmitt -> no results; scrolled through Electrical characterisitcs (page 130 ff) -> nothing about Schmitt-Trigger thresholds.

    Without this piece of information, this feature is useless.

    This sounds maybe a bit stupid, but please point me to the right place in the data sheet.

    Thank you!

    Christian 

  • The input switching thresholds can be anywhere between VIL and VIH, with the minimum hysteresis defined in the datasheet.

    Note: Any signal you apply to an AM64x input is expected to swing rail to rail as fast as possible and never speed much time transitioning between VILSS and VIHSS.  An input voltage between VILSS and VIHSS causes shoot-though current to flow from VDD to VSS through the input buffer, which can create long-term reliability issues if a signal spends too much time between these limits.

    Regards,
    Paul

  • Hi,

    I do not think Pauls reply answers the question. And there are other pin properties like DRV_STR (driver strength) and DEBOUNCE_SEL that I did not found explained neither in the TRM nor in SPRSP56A. None of these properties can be set with the driver delivered in the mcu_plus_sdk_am64x_08_00_00_21.

    Thanks & regards,

    Frank

  • With respect to you question about drive strength, all peripheral timing was closed assuming default drive strength. Therefore, all timing parameters defined in the datasheet are only valid with the default value of drive strength. The drive strength of the default configuration is also the only configuration defined in the respective Electrical Characteristic table with the VOL, VOH, IOL, and IOH parameters.

    I will need to ask about de-bounce, as this is not a parameter typically defined in the datasheet. This information would typically be discussed in the TRM.

    Regards,
    Paul 

  • I found where the de-bounce related registers are discussed in the TRM. There is a note that says de-bounce logic is not associated with all signals. It also says signals with de-bounce are defined in the datasheet. However, that is not the case.

    I sent an email to the design team asking for this information. 

    It may take a while for me to get this information.

    I will reply again after finding something to share.

    Regards,
    Paul

  • I found which AM64x signal functions include the de-bounce function, where I have listed the signals below.

    MCU_GPIO0_[21:20]
    MCU_GPIO0_[17:16]
    MCU_GPIO0_[13:12]
    MCU_GPIO0_[6:5]
    MCU_GPIO0_[1:0]

    EQEP2_A
    EQEP2_B
    EQEP2_S
    EQEP2_I

    EQEP1_A
    EQEP1_B
    EQEP1_S
    EQEP1_I

    EQEP0_A
    EQEP0_B
    EQEP0_S
    EQEP0_I

    GPIO0_[87:80]
    GPIO0_[78:70]
    GPIO0_68
    GPIO0_[44:43]

    ADC_EXT_TRIGGER0
    ADC_EXT_TRIGGER1

    I'm still trying to find delay values associated with register settings.

    Regards,
    Paul

  • Okay, I finally received information associated with de-bounce delays.

    The attached file defines a delay for each value of db_cfg_[5:0].  Note: GPIO signals have different delays than all other signals. The table contains two delay columns where one represents delays possible for GPIO signals and the other represents delays possible for all other signals. 

    AM64x Debounce Delays.xlsx

    Regards,
    Paul