AR8033 Ethernet PHY on i.MX6 Solo

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AR8033 Ethernet PHY on i.MX6 Solo

2,382 Views
vipulkumar
Contributor III

Hi,

I am using a customised board based on i.MX6 Solo. I am using AR8033 ehternet phy from Atheros. Link is successully established on board on u-boot ae well as on kernel and we are able to read the chip id also. But data transmission is not working neither on u-boot nor on kernel.. We are neither able to send packets nor able to receive the packets.

BSP - Yocto -1.6

Kernel - linux-imx-3.10

u-boot - u-boot-fslc-2014

Labels (3)
0 Kudos
4 Replies

1,315 Views
vipulkumar
Contributor III

Hi Lee,

Now ethernet is working on both u-boot and kernel and we are able to ping successfully. In my case on u-boot, we are not getting the clock due to the some hardware issue. Once they fixed clock issue, we were able to ping on u-boot.

After fixing clock issue on u-boot, we were able to get clock on kernel also but the amplitude of the clock is below 3.3v. So, we were not able to ping on kernel.

Actually we were using LDO VGEN 3 to provide supply to the PHY. But after registering the all LDO's, VGEN 3 LDO was going to disbled. So, in imx6dl-sabresd.dts file, we had added the regulator-always-on; in pmic regulators setting. After adding this line, VGEN 3 always remain on and we are getting the required voltage level.

                        vgen3_reg: vgen3 {
                                regulator-min-microvolt = <1800000>;
                                regulator-max-microvolt = <3300000>;
                                regulator-always-on;
                        };

0 Kudos

1,315 Views
vipulkumar
Contributor III

Hi,

Thanks for reply. Now the Ethernet PHY is working fine on u-boot. But still we are not able to ping on kernel. All clocks are coming fine.

$ ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 4
        Transceiver: external
        Auto-negotiation: on
        Link detected: yes

$  ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:22:33:44:55  
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::211:22ff:fe33:4455/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3190 (3.1 KiB)  TX bytes:3407 (3.3 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

$ ping 192.168.1.11
PING 192.168.1.11 (192.168.1.11): 56 data bytes
^C
--- 192.168.1.11 ping statistics ---
8 packets transmitted, 0 packets received, 100% packet loss

$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:22:33:44:55  
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::211:22ff:fe33:4455/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:49 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5382 (5.2 KiB)  TX bytes:4697 (4.5 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1400 (1.3 KiB)  TX bytes:1400 (1.3 KiB)

RX bytes and TX bytes are increased after the ping command.

0 Kudos

1,315 Views
hanseunglee
Contributor III

Hi kumar.

I also same problem. ping is not work on i.mx6solo sabresd board.

If do you have solution? share for me plz.

when i solve the problem, i also share for you. 

Thank you.

0 Kudos

1,315 Views
igorpadykov
NXP Employee
NXP Employee

Hi Vipul

please check with oscilloscope rgmii signal timings using

Table 59. RGMII Signal Switching Specifications i.MX6SDL Datasheet

and try to adjust them if necessary

http://cache.freescale.com/files/32bit/doc/data_sheet/IMX6SDLCEC.pdf

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos