• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 414 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.

AM6412: Resource conflict while assigning RGMII1 pins in Sysconfig tool

Abin Raj
Prodigy 160 points
Part Number: AM6412
Other Parts Discussed in Thread: SYSCONFIG

Hi, I am trying to assign RGMII pins for AM64x. While selecting the pins I am getting a resource conflict error: "Pin is not valid for RGMII1_IOSet_2. Attached the screenshot of the error.

Is it possible to configure and use these pins for RGMII ?

  • 0
    TI__Mastermind 22893 points

    Hello Abin,

    It is possible to configure and use pins V15, V14, W14, AA14, U15, and U14 for an RGMII interface. What version of the SysConfig Tool are you using?

    I do not receive the resource conflict error when using https://dev.ti.com/sysconfig/ (v.1.9.0). Screenshots below:

    Can you share the DEVICE.syscfg file that is causing this issue? Is it possible that the pins are already assigned to signals from another peripheral being used in the configuration?

    Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    Prodigy 160 points

    Hi

    Could you try with the all pins shown in the image (AA13,  U12, Y13, V12, V13, W13, V15, V14, W14, AA14, U15, and U14) ?

    I am guessing its a conflict between RGMII1_IOSet_1 & RGMII1_IOSet_2 as I am mixing and matching Rx & Tx pins from different PHYs from the evaluation module ?

  • +1 in reply to Abin Raj
    TI__Mastermind 22893 points

    You are correct, this is an RGMII IOSet conflict. IOSet restrictions are put in place to prevent invalid signal mix and match options. TI can only validate/guarantee the interface timing requirements for valid IOSet configurations.

  • 0 in reply to Fleenor
    Prodigy 160 points

    Thanks for the update

  • +1 in reply to Abin Raj
    TI__Mastermind 22893 points

    Hey Abin,

    After a secondary review of the source data in the current version of the tool. This is an actual error in the RGMII_IOSet_2 restrictions that causes this false Resource Conflict error for the Transmit signals (TD[0:3], TX_CTL, and TXC). This will be resolved in the AM64x_beta device data release. The same group of TX signals that are available for RGMII1_IOSet_1 are also applicable to RGMII1_IOSet_2.

    The "SIGNALx/Ball# is not valid for RGMII1_IOSet_2" error can be safely ignored in this case.

    Let us know if you have any additional questions.

    Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    Prodigy 160 points

    Thanks for clarifying Slight smile. We have changed the pin out to match the ones used in EVK.  Also it seems like the link is not valid.