Forum Discussion

K606's avatar
K606
Icon for Contributor rankContributor
4 months ago

Agilex 5 EMAC GMII loopthrough: signals are not toggling in Fabric

I am trying to route GMII signals through the Agilex5 HPS to the Fabric. In the .dts I am using, I have the following settings for the two EMACs: &gmac0 { status = "okay"; mac-mode = "gmii"; ph...
embedded peripheral
general
Hps Debug
ShunJingG_Altera's avatar
ShunJingG_Altera
Icon for New Contributor rankNew Contributor
4 months ago

Hello K606​ ,

You may have a typo for the rx clock.

Could you please try this?

assign emac1_mac_rx_clk_wire = emac0_mac_tx_clk_o_wire; // 1G

Thank you.

K606's avatar
K606
Icon for Contributor rankContributor
4 months ago

Hi - so I changed this line. However, it seems the issue persists.

Do you know why this might be?

Please also note that the SoC system clocks are confirgured as followed:

root@localhost:~# cat /sys/kernel/debug/clk/clk_summary
                                 enable  prepare  protect                                duty  hardware
   clock                          count    count    count        rate   accuracy phase  cycle    enable
-------------------------------------------------------------------------------------------------------
 qspi-clk                             1        1        0   200000000          0     0  50000         Y
 osc1                                 2        2        0    25000000          0     0  50000         Y
    periph_pll                        1        1        0  2500000000          0     0  50000         Y
       peri_pll_c3                    1        1        0   500000000          0     0  50000         Y
          psi_ref_free_clk            0        0        0   500000000          0     0  50000         Y
             psi_ref_clk              0        0        0   500000000          0     0  50000         Y
          s2f_user1_free_clk          0        0        0   500000000          0     0  50000         Y
             s2f_user1_clk            0        0        0   500000000          0     0  50000         Y
          s2f_user0_free_clk          0        0        0   500000000          0     0  50000         Y
             s2f_user0_clk            0        0        0   500000000          0     0  50000         Y
          emaca_free_clk              3        3        0   250000000          0     0  50000         Y
             emac2_clk                1        1        0   250000000          0     0  50000         Y
             emac1_clk                1        1        0   250000000          0     0  50000         Y
             emac0_clk                1        1        0   250000000          0     0  50000         Y

So it seems the clocks are active, but when sending a 'ping' from EMAC0 to EMAC1 - there is no activity on the GMII lines in Fabric (even though it seems the ping is working in userland in the HPS)

root@localhost:~# sudo ip addr add 192.168.70.5/24 dev eth0
root@localhost:~# sudo ip addr add 192.168.70.1/24 dev eth1
root@localhost:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.70.5  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 3e:17:2e:db:8b:f6  txqueuelen 1000  (Ethernet)
        RX packets 60  bytes 19080 (19.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 168  bytes 27408 (27.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 23  

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.70.1  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 62:6f:4c:21:f2:f4  txqueuelen 1000  (Ethernet)
        RX packets 59  bytes 18762 (18.7 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 170  bytes 27588 (27.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 40  
...

root@localhost:~# ping -I 192.168.70.1 192.168.70.5
PING 192.168.70.5 (192.168.70.5) from 192.168.70.1 : 56(84) bytes of data.
64 bytes from 192.168.70.5: icmp_seq=1 ttl=64 time=0.189 ms
64 bytes from 192.168.70.5: icmp_seq=2 ttl=64 time=0.034 ms
64 bytes from 192.168.70.5: icmp_seq=3 ttl=64 time=0.168 ms
64 bytes from 192.168.70.5: icmp_seq=4 ttl=64 time=0.042 ms
64 bytes from 192.168.70.5: icmp_seq=5 ttl=64 time=0.022 ms
64 bytes from 192.168.70.5: icmp_seq=6 ttl=64 time=0.009 ms
64 bytes from 192.168.70.5: icmp_seq=7 ttl=64 time=0.029 ms
64 bytes from 192.168.70.5: icmp_seq=8 ttl=64 time=0.020 ms
64 bytes from 192.168.70.5: icmp_seq=9 ttl=64 time=0.009 ms
64 bytes from 192.168.70.5: icmp_seq=10 ttl=64 time=0.034 ms
64 bytes from 192.168.70.5: icmp_seq=11 ttl=64 time=0.014 ms
64 bytes from 192.168.70.5: icmp_seq=12 ttl=64 time=0.012 ms
64 bytes from 192.168.70.5: icmp_seq=13 ttl=64 time=0.052 ms
64 bytes from 192.168.70.5: icmp_seq=14 ttl=64 time=0.025 ms
64 bytes from 192.168.70.5: icmp_seq=15 ttl=64 time=0.019 ms
^C
--- 192.168.70.5 ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14335ms