Hey Everyone,
I got a Jetson Nano a few weeks ago and have an 802.11ad WiGig M.2 Module based on the QCA6335 chipset, which is Qualcomm’s 60GHz MAC/BB solution supporting the WiGig Specification and IEEE 802.11ad-2012 with a PCIe 2.0 interface. I am trying to use the Jetson Nano and module to stream high quality video from several cameras within my apartment and the 60 GHz WiGig module would be ideal for that.
The Jetson Nano seems to recognize the module as a WiFi adapter and properly boots when it is intalled. I’ve run the commands below and pasted their output to see if the adapter is connected and recognized.
lspci -nnk | grep -A2 0280
01:00.0 Network controller [0280]: Wilocity Ltd. Wil6200 802.11ad Wireless Network Adapter [1ae9:0310](rev 02)
Subsystem: Wilocity Ltd. Wil6200 802.11ad Wireless Network Adapter [1ae9:0000]
Kernel driver in use: wil6210
modinfo wil6210
filename: /lib/modules/4.9.140-tegra/kernel/drivers/net/wireless/ath/wil6210/wil6210.ko
description: Driver for 60g WiFi WIL6210 card
author: Qualcomm Atheros <wil6210@qca.qualcomm.com>
license: Dual BSD/GPL
firmware: wil6210.brd
firmware: wil6210.fw
alias: pci:v00001AE9d00000302sv*sd*bc*sc*i*
alias: pci:v00001AE9d00000310sv*sd*bc*sc*i*
depends: cfg80211
intree: Y
vermagic: 4.9.140-tegra SMP preempt mod_unload modversions aarch64
parm: rtap_include_phy_info: Include PHY info in the radiotap header, default - no (bool)
parm: rx_align_2: align Rx buffers on 4*n+2, default - no (bool)
parm: max_assoc_sta: Max number of stations associated to the AP (uint)
parm: agg_wsize: Window size for Tx Block Ack after connect; 0 - use default; < 0 - don't auto-establish (int)
parm: led_id: 60G device led enablement. Set the led ID (0-2) to enable (byte)
parm: use_msi: Use MSI interrupt, default - true (bool)
parm: debug_fw: do not perform card reset. For FW debug (bool)
parm: oob_mode: enable out of the box (OOB) mode in FW, for diagnostics and certification (bool)
parm: no_fw_recovery: disable automatic FW error recovery (bool)
parm: rx_ring_overflow_thrsh: RX ring overflow threshold in descriptors. (ushort)
parm: mtu_max: Max MTU value.
parm: rx_ring_order: Rx ring order; size = 1 << order
parm: tx_ring_order: Tx ring order; size = 1 << order
parm: bcast_ring_order: Bcast ring order; size = 1 << order
iw list
Wiphy phy0
max # scan SSIDs: 1
max scan IEs length: 1024 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Supported Ciphers:
* GCMP-128 (00-0f-ac:8)
Available Antennas: TX 0 RX 0
Supported interface modes:
* managed
* AP
* monitor
* P2P-client
* P2P-GO
* P2P-device
Band 3:
Capabilities: 0x00
HT20
Static SM Power Save
No RX STBC
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 1-12
Bitrates (non-HT):
Frequencies:
* 58320 MHz [1] (0.0 dBm)
* 60480 MHz [2] (0.0 dBm)
* 62640 MHz [3] (0.0 dBm)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* set_bss
* remain_on_channel
* frame
* set_channel
* probe_client
* start_p2p_device
* connect
* disconnect
Supported TX frame types:
* managed: 0x50 0xd0
* AP: 0x50 0xd0
* P2P-client: 0x50 0xd0
* P2P-GO: 0x50 0xd0
* P2P-device: 0x50 0xd0
Supported RX frame types:
* managed: 0x40 0xd0
* AP: 0x40 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x40 0xd0
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
interface combinations are not supported
Device supports TX status socket option.
Device supports scan flush.
From my somewhat limited knowledge of Ubuntu, it appears that the Jetson Nano properly identifies the WiGig adapter card, has the properly installed drivers, and has associated the two together. However, after several days of trying I have not been able to get the Jetson Nano to recognize or connect to the 60 GHz router I have. Additionally, I have not been able to get the Jetson Nano to act as its own Access Point either. I am trying to identify what is causing this issue.
Does anyone have any experience with 802.11ad WiGig adapters on the Jetson Nano or know if they are compatible?
Thank you!