• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 778 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.

Original question:

Linux/AM4377: RGMII2 RX issue

Linux/AM4377: Ethernet ping fails in U-boot

guangzhao lv
Intellectual 275 points
Part Number: AM4377

Tool/software: Linux

Dear Sir:

         We make AM437X StarterKit EVM as reference board.

         we use SDK ti-processor-sdk-linux-am437x-evm-04.03.00.05-Linux-x86-Install.bin

         with our custom board, we have make ethernet work well under linux kernel.

         but it does't work under u-boot.

         it ping PC IP fail. it call cpsw_send to send arp packet, but we use wireshark to capture arp request in PC site.

         but there is no any packet in PC Site with wireshark.

        so i think it can send out any packet from target board.

        we don't know the root cause.

         can you give us some advice or some  help ?

  • 0
    Intellectual 275 points
    Dear Sir:
    we use port2 as rgmii2 interface connected to RTL8211F PHY IC.
    Under u-boot, we can dump phy info as below:

    => mii dump 4 0
    0. (1040) -- PHY control register --
    (8000:0000) 0.15 = 0 reset
    (4000:0000) 0.14 = 0 loopback
    (2040:0040) 0. 6,13 = b10 speed selection = 1000 Mbps
    (1000:1000) 0.12 = 1 A/N enable
    (0800:0000) 0.11 = 0 power-down
    (0400:0000) 0.10 = 0 isolate
    (0200:0000) 0. 9 = 0 restart A/N
    (0100:0000) 0. 8 = 0 duplex = half
    (0080:0000) 0. 7 = 0 collision test enable
    (003f:0000) 0. 5- 0 = 0 (reserved)


    => mii dump 4 1
    1. (79ad) -- PHY status register --
    (8000:0000) 1.15 = 0 100BASE-T4 able
    (4000:4000) 1.14 = 1 100BASE-X full duplex able
    (2000:2000) 1.13 = 1 100BASE-X half duplex able
    (1000:1000) 1.12 = 1 10 Mbps full duplex able
    (0800:0800) 1.11 = 1 10 Mbps half duplex able
    (0400:0000) 1.10 = 0 100BASE-T2 full duplex able
    (0200:0000) 1. 9 = 0 100BASE-T2 half duplex able
    (0100:0100) 1. 8 = 1 extended status
    (0080:0080) 1. 7 = 1 (reserved)
    (0040:0000) 1. 6 = 0 MF preamble suppression
    (0020:0020) 1. 5 = 1 A/N complete
    (0010:0000) 1. 4 = 0 remote fault
    (0008:0008) 1. 3 = 1 A/N able
    (0004:0004) 1. 2 = 1 link status
    (0002:0000) 1. 1 = 0 jabber detect
    (0001:0001) 1. 0 = 1 extended capabilities


    => mii dump 4 2
    2. (001c) -- PHY ID 1 register --
    (ffff:001c) 2.15- 0 = 28 OUI portion


    => mii dump 4 3
    3. (c916) -- PHY ID 2 register --
    (fc00:c800) 3.15-10 = 50 OUI portion
    (03f0:0110) 3. 9- 4 = 17 manufacturer part number
    (000f:0006) 3. 3- 0 = 6 manufacturer rev. number


    => mii dump 4 4
    4. (01e1) -- Autonegotiation advertisement register --
    (8000:0000) 4.15 = 0 next page able
    (4000:0000) 4.14 = 0 (reserved)
    (2000:0000) 4.13 = 0 remote fault
    (1000:0000) 4.12 = 0 (reserved)
    (0800:0000) 4.11 = 0 asymmetric pause
    (0400:0000) 4.10 = 0 pause enable
    (0200:0000) 4. 9 = 0 100BASE-T4 able
    (0100:0100) 4. 8 = 1 100BASE-TX full duplex able
    (0080:0080) 4. 7 = 1 100BASE-TX able
    (0040:0040) 4. 6 = 1 10BASE-T full duplex able
    (0020:0020) 4. 5 = 1 10BASE-T able
    (001f:0001) 4. 4- 0 = 1 selector = IEEE 802.3


    => mii dump 4 5
    5. (45e1) -- Autonegotiation partner abilities register --
    (8000:0000) 5.15 = 0 next page able
    (4000:4000) 5.14 = 1 acknowledge
    (2000:0000) 5.13 = 0 remote fault
    (1000:0000) 5.12 = 0 (reserved)
    (0800:0000) 5.11 = 0 asymmetric pause able
    (0400:0400) 5.10 = 1 pause able
    (0200:0000) 5. 9 = 0 100BASE-T4 able
    (0100:0100) 5. 8 = 1 100BASE-X full duplex able
    (0080:0080) 5. 7 = 1 100BASE-TX able
    (0040:0040) 5. 6 = 1 10BASE-T full duplex able
    (0020:0020) 5. 5 = 1 10BASE-T able
    (001f:0001) 5. 4- 0 = 1 selector = IEEE 802.3
  • 0
    TI__Guru**** 393215 points
    You already have a thread opened on this issue here: e2e.ti.com/.../687727

    Please do not open multiple threads on the same subject on this forum. This thread will be closed now. Continue on the original thread.