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.

AM5718: AM5718 use RGMII1 in u-boot

Part Number: AM5718

CPU : AM5718

SDK  : am57xx-evm-linux-sdk-src-06.03.00.106

I have a custom board with AM5718 processor and PHY is connected to RGMII1.

When I checked the RGMII1 interface using MII utility.

U-BOOT> mii info

PHY 0x01: OUI = 0x0885, Model = 0x22, Rev = 0x02, 1000baseT, FDX

I think my issue is same the link below, so I followed the solution.

https://e2e.ti.com/support/processors/f/791/t/559648?tisearch=e2e-sitesearch&keymatch=rgmii1

But My board can't pass the PING test.

My board is connected to PC using RGMII1 interface.

My PC sends the PING test packet, but it can't detect eth1.

My Question : How can I change from RGMII0 to RGMII1 In the u-boot?

                        I want that u-boot uses RGMII1 (eth1) instead of RGMII0 (eth0) for ethernet.

  • Hi Remony,

    The older thread you referred talks of active_slave in platform_data.

    Currently that setting needs to be done in DT:

    diff --git a/arch/arm/dts/dra7.dtsi b/arch/arm/dts/dra7.dtsi
    index e2e958b366..fbb9e8a750 100644
    --- a/arch/arm/dts/dra7.dtsi
    +++ b/arch/arm/dts/dra7.dtsi
    @@ -1794,7 +1794,7 @@
                            bd_ram_size = <0x2000>;
                            mac_control = <0x20>;
                            slaves = <2>;
    -                       active_slave = <0>;
    +                       active_slave = <1>;
                            cpts_clock_mult = <0x784CFE14>;
                            cpts_clock_shift = <29>;
                            reg = <0x48484000 0x1000

    With the above change i could easily get dhcp working on the ethernet1.

    Please let me know if that helps you.

    BR,
    Keerthy

  • Hi Keerthy,

    Thank you for your reply.

    I modified dra7.dtsi file according to your recommend and then tested PING.

    But it still fails.

  • Hi Remony,

    Could you try the same on TI-IDK? Can you see if that change gets ping working on ethernet1?

    Also can you share the failure logs on your custom evm?

    - Keerthy

  • Hi Keerthy,

    First of all, I'm as good as a beginner.

    I am not very familiar with Ethernet.
    I added log capture of the custom board. 

    I have to update EVM SDK. 

    I will test it as soon as the update is over and share the results.