Changes between Version 66 and Version 67 of expansion/gw16146
- Timestamp:
- 12/27/2024 06:50:51 PM (3 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
expansion/gw16146
v66 v67 1106 1106 lrwxrwxrwx 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 1107 1107 }}} 1108 1. Ensure the there is a wireless interface in /sys/class/net :1108 1. 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] 1109 1109 {{{#!bash 1110 1110 # ls /sys/class/net … … 1122 1122 iw reg set US 1123 1123 }}} 1124 6. Verify the cli_app can talk to the GW16146 module:1124 1. Verify the cli_app can talk to the GW16146 module: 1125 1125 {{{#!bash 1126 1126 # cli_app show version … … 1130 1130 1131 1131 }}} 1132 7. Device sleeping1132 1. Device sleeping 1133 1133 {{{#!bash 1134 1134 [Error] the target device cannot respond while deep sleep. … … 1139 1139 }}} 1140 1140 1141 This can also be caused by accessing the wrong wlan interface in Linux. See above. 1141 1142 1142 1143 == Hardware