Changes between Version 66 and Version 67 of expansion/gw16146


Ignore:
Timestamp:
12/27/2024 06:50:51 PM (3 weeks ago)
Author:
Ryan Erbstoesser
Comment:

add note about wireless interfaces

Legend:

Unmodified
Added
Removed
Modified
  • expansion/gw16146

    v66 v67  
    11061106lrwxrwxrwx 1 root root 0 Aug 31 20:13 spi3 -> ../../devices/platform/soc@0/soc@0:bus@32c00000/32e50000.usb/ci_hdrc.1/usb1/1-1/1-1.3/1-1.3:1.0/spi-ft232h.0/spi_master/spi3
    11071107}}}
    1108 1. Ensure the there is a wireless interface in /sys/class/net:
     11081. Ensure the there is a wireless interface in /sys/class/net. NOTE that on devices with multiple wireless devices, such as wlan0 and wlan1, these can get swapped sporadically across boots, and thus extreme detail needs to be taken to be sure the interface being used is truly the GW16146 card. For persistent naming, read more on the FAQ [wiki:faq#HowdoIhandlemultiplewirelessradiosononeSBC here]
    11091109{{{#!bash
    11101110# ls /sys/class/net
     
    11221122iw reg set US
    11231123}}}
    1124 6. Verify the cli_app can talk to the GW16146 module:
     11241. Verify the cli_app can talk to the GW16146 module:
    11251125{{{#!bash
    11261126# cli_app show version
     
    11301130
    11311131}}}
    1132 7. Device sleeping
     11321. Device sleeping
    11331133{{{#!bash
    11341134[Error] the target device cannot respond while deep sleep.
     
    11391139}}}
    11401140
     1141This can also be caused by accessing the wrong wlan interface in Linux. See above.
    11411142
    11421143== Hardware