View Post - post118049 | |
09/19/2017 7:34 AM
post118049
|
回复: Re: 回复: [atheros] status is always no carrier
ok, i will examine the configuration on the phy , maybe there is a difference between ar8035 and ar8031, but i do not aware of it now. thank you for helping me , thanks! ------------------ 原始邮件 ------------------ 发件人: "Hugh Brown";<community-noreply@qnx.com>; 发送时间: 2017年9月18日(星期一) 晚上8:18 收件人: "drivers-networking@community.qnx.com"<drivers-networking@community.qnx.com>; 主题: Re: 回复: [atheros] status is always no carrier Starting the mx6x driver will turn the PHY off, but when you run “ifconfig fec0 up” the PHY should initialize and the link should come up. It sounds as though you have a configuration problem with the PHY. The nicinfo state of “unknown” is because the link isn’t up. Then link state is normally read from the PHY status register. On 2017-09-15, 10:53 PM, "blinking" <community-noreply@qnx.com> wrote: maybe the problem i described is not clear, i have already pluggled the cable into my board. the detail operations list as below: 1.plugged the cable into my embeded board, and another port connect to my computer(win10). 2.power on the board without starting the network service in the bulid configeration file. etc, #display_msg Starting Networking #io-pkt-v6-hc -dmx6x #if_up -p fec0 #ifconfig fec0 up #dhclient -nw fec0 3. the led of the net port in board and computer is on and blinking, at this time the phy is not init because i do not start the service. 4. when i input io-pkt-v6-hc -d mx6x in the command line, the led is off, and the link becomes down, the nicinfo and ifconfig info in the last email the key point of this problem is why the status of ifconfig info is always no carrier, not active. Have you ever encountered such problems before? another question is the Current Operation Rate of nicinfo is always unknown, what does this means ? which register is this read? thank you very much! ------------------ 原始邮件 ------------------ 发件人: "Hugh Brown";<community-noreply@qnx.com>; 发送时间: 2017年9月15日(星期五) 晚上8:26 收件人: "drivers-networking@community.qnx.com"<drivers-networking@community.qnx.com>; 主题: Re: [atheros] status is always no carrier Are you using a crossover cable to connect to your win10 machine? Have you tried plugging the cable into a switch? On 2017-09-15, 4:10 AM, "blinking" <community-noreply@qnx.com> wrote: hello,drivers-networking engineer: My Development Environment Host: Ubuntu 14. Qnx: SDP 7.0 Target: iMx6q Sabre Auto/AI I face a strange problem when i am debugging phy(atheros ar8095) driver on imx6q board, when i have started the io-pkt service and configed ip, the nicinfo changes below: --> nicinfo fec0: i.MX6 Ethernet Controller Link is DOWN Physical Node ID ........................... 000012 345678 Current Physical Node ID ................... 000012 345678 Current Operation Rate ..................... Unknown Active Interface Type ...................... MII Active PHY address ....................... 0 Maximum Transmittable data Unit ............ 1500 Maximum Receivable data Unit ............... 1500 Hardware Interrupt ......................... 0x96 Hardware Interrupt ......................... 0x97 Memory Aperture ............................ 0x2188000 - 0x2188fff Memory Aperture ............................ 0x2098000 - 0x2098fff Promiscuous Mode ........................... Off Multicast Support .......................... Enabled and the network port status is : -->ifconfig fec0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:00:12:34:56:78 media: Ethernet 10baseT full-duplex (none) status: no carrier inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::200:12ff:fe34:5678%fec0 prefixlen 64 scopeid 0x11 whatever the configuration of the phy has made,the fec0's status is always no carrier. by the way, cable is connected to my win10 computer. do you have any suggestions to my problem? thank u! _______________________________________________ Networking Drivers http://community.qnx.com/sf/go/post118034 To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com _______________________________________________ Networking Drivers http://community.qnx.com/sf/go/post118038 To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com _______________________________________________ Networking Drivers http://community.qnx.com/sf/go/post118039 To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com _______________________________________________ Networking Drivers http://community.qnx.com/sf/go/post118041 To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com |
|
|