• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 254 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.

AM2434: AM243x-LP

Jinlong Shen
Intellectual 540 points

Part Number: AM2434
Other Parts Discussed in Thread: DP83869

Tool/software:

Hi there, 

we can image connecting two EtherCAT slave nodes, i.e. two AM2434 chips, without ETH PHYs in-between. Will TI AM243x firmware support this use case?

Best regards,
Jinlong 

  • +1
    TI__Genius 11335 points

    Hi,

    May I know the use case for this? How are you planning to link the EtherCAT SubDevice nodes without PHY ?

    Regards,
    Aaron

  • +1
    TI__Genius 11335 points

    We do not support PHY less connection between EtherCAT devices. You will be needing an external logic to manage link state as firmware needs this link state input to configure the ports correctly. Also without PHY, there will be reduction of 300ns in latency, and we can't predict the firmware impact due to this reduced latency.

    Regards,
    Aaron 

  • 0 in reply to Aaron Thomas
    Intellectual 540 points

    I have to reactivate this question. 

    We need to use two AM2434 chips on the same board. Normally we need 4 PHYs for this setup. We wish to remove two PHYs in between. See below. We have consulted Beckhoff. Physically it should work. However, we have some problem with Option 2. 
    Can we somehow keep one PHY and skip the other? In detail, where is the source code of these two APIs : () and PRU_MDIO_initPhy()?


    Option 1/Now:
    RJ45 PHY_IN_AM243 (chip1) PHY_OUT --> PHY_IN_AM243 (chip2)  PHY_OUT -RJ45
    Option 2/Wish:
    RJ45 PHY_IN_AM243 (chip1)  - AM243 (chip2)  PHY_OUT -RJ45

    We have a single board with option 2.
    This is the serial output:

    Configure Phy bits: PhyAddr:3, LinPol:HIGH, PhyAddr:15, LinPol:HIGH, (0x0)
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    PRU_PHY_detect:156 PHY0 not ok
    DP83869 detected
    PRU_PHY_detect:185 Phy 15 alive
    No PHYs found !!!
    PRU_MDIO_initPhy: 0x120003 EC is fatal=1, SRC:PRU_MDIO_initPhy:339





  • 0 in reply to Jinlong Shen
    Intellectual 540 points

    Request for new feature:
    When configuring PHY in syscfg. Is it possible to configure PHY as BYPASS in addition?