Post Go back to editing

Case (SR-233984-H4J9V5): RXC clock issue at u-boot for ADIN1300 PHY ethernet

We are using ADIN1300 PHY ethernet for our customized board (reference ethernet is KSZ9031RNX PHY). At u-boot level we are not getting any RXC clock but for reference PHY we are getting RXC clock.
Is there any dependency of ADIN PHY in the u-boot? Could you please help us to look into the issue on priority?
monika m
  • Any update on the above  query? could you please provide ADIN driver at u-boot level?

  • Hi Monika,

    The ADIN1300 part has IEEE 802.3 compliant MII, RMII and RGMII MAC interfaces, the registers also comply.

    It should work with the generic PHY driver implementation in u-boot.

    Are you replacing the KSZ9031RNX with the ADIN1300 in a new design? Would you be able to share the schematic for the customized board that is mentioned?

    Best Regards,


  • Hello Mark,

    Yes we are replacing KSZ9031RNX with the ADIN1300 in a new design. With the changes to "mii control" register in the u-boot, we can get RXC clock in u-boot of 25MHZ. (generic driver)

    When complete BSP is booted on the device, able to detect eth node as shown below.


    root@s32g274ardb2:~# [ 5451.150694] 003: s32cc-dwmac 4033c000.ethernet: Set RX/TX clock to 25M
    [ 5451.150739] 003: s32cc-dwmac 4033c000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off

    root@s32g274ardb2:~# ifconfig
    eth0 Link encap:Ethernet HWaddr 00:01:02:03:04:05
    inet addr: Bcast: Mask:
    inet6 addr: fe80::a4ac:f63b:d09e:31a2/64 Scope:Link
    RX packets:269288 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2482 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:23262186 (22.1 MiB) TX bytes:284584 (277.9 KiB)
    Interrupt:63 Base address:0x6000


    ping test is getting failed using udhcpc command, always default setting to static. If tested in static mode also not able to ping


    root@s32g274ardb2:~# udhcpc
    udhcpc: started, v1.32.0
    udhcpc: sending discover
    udhcpc: sending discover
    udhcpc: sending discover


    Clock for RXC and TXC are their when complete BSP is up. Could you please help us to fix the issue on priority?