• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 206 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.

PROCESSOR-SDK-AM64X: Customer PCB ETH0/ETH1 with DP83867 issue

Rio Chan
Genius 14705 points
Part Number: PROCESSOR-SDK-AM64X

Hi Schuyler:

This new E2E is cloned from this Old E2E: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1158875/sk-am64-sdk8-4-of-am64-is-buggy-on-the-eth-phy/4397447#4397447

Let me make it shorter and much clear:

#1. Customer is testing with SDK8.4 + Their PCB.

#2. They are using 2 DP83867 ETH phy, this is the same design with the TI EVM.

#3. The current issue is:

          Step0: Ifconfgi ETH0 / ETH1 down.

          Step1: Ifconfig ETH0 up, do the ping. (No any problem here.)

          Step2: ifconfig ETH1 up, do the ping. (No any problem here.)

          Step3: ifconfig ETH0 down, ETH1 is still working. (No problem here.)

          Step4: ifconfig ETH1 down. (No problem here.)

          Step5: ifconfig ETH1 / ETH0 up. (No problem here.)

          Step6: do the ping from ETH1/ ETH0, (no problem here.)

          Step7: ifconfig ETH1 down. (We will have the problem here.)

                     In the normal case, when doing the ifconfig ETH1 down, the ETH1 will be down, but the ETH0 should be working here.

                     in the fail case,,the ETH0 will be down after ETH is down. (The ETH0 should not be effected by ETH1.)

           So, the fail case reproduced rate is about 30%.

           IE: 70% Customer PCB has no this issue, only 30% of their PCB has this issue.

Any comments?

We will do the schematic review.

But, we want to know if this is the HW issue to cause since I never met this kind of issue from the other customer.

BR Rio

  • 0
    TI__Mastermind 40080 points

    Hi Rio,

    From the previous e2e thread I notice that the same IP address is being assigned statically to both ports. I see that the other port is down before bringing up the other port. The suggestion for the moment is to try different IP addresses on each port when it is up. For example eth0 192.168.1.11 and eth1 192.168.1.12 and re-run the test. Or use a WLAN router that has DHCP support if one is available.

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    TI__Genius 14705 points

    Hi Schuyler:

    This issue is resolved since the root cause is found.

    THanks for your helping.

    BR Rio