Does the G700 EVK support WOL functionality on Android T and Ethernet?
G700 supports Mac WOL functionality
How to enable WOL on G700?
we use tool to send magic packet but PHY not anly action(INTB pin not change to low)
The following command is required to enable WOL functionality.
ethtool -s eth0 wol g
The ethtool command could not be found. (Android T V9.174)
I looked at the BSP code (external/ethtool), compiled it (mmm external/ethtool), and pushed the compiled program into the system for execution. The result is as follows.
console:/data # ifconfig
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:1000
RX bytes:0 TX bytes:0
dummy0 Link encap:Ethernet HWaddr 82:f2:00:51:77:1f
inet6 addr: fe80::80f2:ff:fe51:771f/64 Scope: Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 TX bytes:490
eth0 Link encap:Ethernet HWaddr 00:55:7b:b5:7d:f7 Driver dwmac-mediatek
inet addr:192.168.50.183 Bcast:192.168.50.255 Mask:255.255.255.0
inet6 addr: fe80::cde8:9daf:87b7:f9d3/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3605 TX bytes:4385
Interrupt:82
console:/data # ./ethtool -s eth0 wol g
Cannot set new wake-on-lan settings: Operation not supported on transport endpoi
nt
not setting wol
HI,You also need to add the following parameters to the eth node of the DTS.
mediatek,mac-wol
Adding “mediatek,mac-wol”,
“ethtool” runs without error messages, and the PHY link LED no longer disconnects during sleep.
Due to project progress, the Realtek PHY on the EVK has been replaced with your company’s currently promoted Airoha AN8801, and the AN8801 driver from the G720 BSP has been copied to the G700 for compilation, and it now works correctly.
The current issue is that the AN8801 INTB is not functioning correctly. In AC on → system ready → ethtool setting → suspend, the voltage level unchanged, always on “Lo”
What kernel version are you currently running on your G700? Could you please send us the DTS and Ethernet drivers you are using?
Are you currently using a Yocto environment or an Android environment?
Uploading using “MTK file exchange service” ?
Using Android environment
If you are using Android TV 9.174 as mentioned in the previous discussion, after adding Mediatek and Mac-WOL, Mac WOL is supported, but Phy WOL is not supported, so INTB will not be pulled up.
We using IOT Genio platform Android T (V9.174)
This version does not support Phys.wol, only Mac.wol. Is it currently possible to wake the system using the Magic package after suspending?
I’m using wol wakeup in the ASUS router’s web UI, but the system isn’t waking up.
When the device is in suspend mode, EVK will disappear from the router’s device list, but the LINK status LED will remain active, indicating that the link is still active.
At this time, the Router WOL function cannot wake the system.
You can use the following command to check if WOL functionality is enabled:
ethtool eth0
With WOL enabled, check if the interrupt count on eth0 increases after the magic packet is sent: cat /proc/interrupts | grep eth0
Does the Ethernet function work properly after changing the PHY?
Send magic package from Router : (4 times)
console:/data # cat /proc/interrupts | grep eth0
82: 105 0 0 0 0 0 0 0 GICv3 748 Level eth0
console:/data # cat /proc/interrupts | grep eth0
82: 106 0 0 0 0 0 0 0 GICv3 748 Level eth0
console:/data # cat /proc/interrupts | grep eth0
82: 107 0 0 0 0 0 0 0 GICv3 748 Level eth0
console:/data # cat /proc/interrupts | grep eth0
82: 108 0 0 0 0 0 0 0 GICv3 748 Level eth0
console:/data # cat /proc/interrupts | grep eth0
82: 108 0 0 0 0 0 0 0 GICv3 748 Level eth0
console:/data # ping 192.168.50.1
PING 192.168.50.1 (192.168.50.1) 56(84) bytes of data.
64 bytes from 192.168.50.1: icmp_seq=1 ttl=64 time=2.23 ms
64 bytes from 192.168.50.1: icmp_seq=2 ttl=64 time=0.744 ms
64 bytes from 192.168.50.1: icmp_seq=3 ttl=64 time=0.853 ms
^C
— 192.168.50.1 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2005ms
rtt min/avg/max/mdev = 0.744/1.276/2.233/0.678 ms
console:/data # ping 192.168.50.105
PING 192.168.50.105 (192.168.50.105) 56(84) bytes of data.
64 bytes from 192.168.50.105: icmp_seq=1 ttl=64 time=1.38 ms
64 bytes from 192.168.50.105: icmp_seq=2 ttl=64 time=0.937 ms
64 bytes from 192.168.50.105: icmp_seq=3 ttl=64 time=1.03 ms
^C
— 192.168.50.105 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2005ms
rtt min/avg/max/mdev = 0.937/1.116/1.381/0.194 ms
console:/data #