Using Xavier NX Dev Kit's Azurewave AW-CB375NF M.2 Module on Jetson Nano

Autonomous Machines Jetson & Embedded Systems Jetson Nano
,
#1

Hi all,

I was just wondering if its possible to use M.2 Wi-Fi module of Jetson Xavier NX Dev Kit on Jetson Nano. When I plug it in, Jetson Nano recognizes it as RealTek Semiconductor Inc. but under the Wi-Fi Networks, it doesn’t show any available networks to connect and says “device not ready”.

Is there any chance or workaround to use this M.2 module on Jetson Nano Dev Kit or Jetson AGX Xavier Dev Kit?

#2

I don’t know anything about the specific hardware, but if you see USB announce the device, then it implies the m.2 slot (or USB for USB devices) has done its job. What happens next is that a driver must take ownership of the device. If the driver is not present, or if some sort of customization by the manufacturer causes the device to not be recognized by drivers otherwise capable of using this device, then nothing more happens and the device will be there without function.

Due to RF compliance it isn’t unusual for firmware to also be required for WiFi devices. Any driver would require the device to be set up by its firmware before it can load without error. Your WiFi may not require extra firmware, but this could also cause failure.

Someone else may be able to answer for your specific case, but you’ll need to include the log of “dmesg” first.

1 Like
#4

3rdparty vendor driver is probably needed for M.2 wifi card. For example, Intel driver is required for ac8265 wifi card.

Your card may need that driver and firmware too. Some cards are lucky enough that don’t need to install extra drivers because our kernel has installed them already.

#5

Thanks for the explanation. I think that two below lines are relevant with the new Wi-Fi module:

[    5.631556] rtk_btusb: fw name is  rtl8822cu_fw
[    5.638667] rtk_btusb: This is not 8723a, use new patch style!

And also here is the full dmesg output.

dmesg_out.log (62.8 KB)

#6

Yeah I agree that Jetson Nano also needs to have the same drivers with Jetson Xavier NX Dev Kit in order to be able utilize the same Wi-Fi module. I just thought that JetPack 4.4 for Jetson Nano would have the driver so I just upgraded my JetPack from 4.3 to 4.4 on the Jetson Nano but no luck.

#7

Hi,
According to your log, looks like not a driver issue but some smmu problem.

Could you remove below lines in tegra210-porg-pcie.dts?

           /delete-property/ iommus;
           /delete-property/ iommu-map;
           /delete-property/ iommu-map-mask;
Does PCIe in the M.2 need some kind of activation?
#8

Sorry for the inconvenience but I can’t find the exact tegra210-porg-pcie.dts file neither within my filesystem nor sdkm directory on the host PC. But when I check the log file, there is a line as follows: DTS File Name: /dvs/git/dirty/git-master_linux/kernel/kernel-4.9/arch/arm64/boot/dts/../../../../../../hardware/nvidia/platform/t210/porg/kernel-dts/tegra210-p3448-0000-p3449-0000-b00.dts

Should I make the change within this file? Thanks.

#9

Hi,

Because it is in the kernel source tarball. Please download it from download center and follow the guidance in l4t development guide to rebuild a new dtb and reflash it to your device.

#11

Could we use the AW-CB375NF(SDIO3.0 interface) on Xavier NX? Thanks.

#12

Hi chen.arby,

Please help to open a new topic for your issue. Thanks

#13

Hi, I can confirm that the previously mentioned DTB patch fixes the issue and the Wifi card works without a glitch (I ran iperf over half an hour on it without a single lost packet).

Is there a reason why is the IOMMU configured like this on Nano? Could the three lines be deleted in the default distribution’s DTB so that everyone can swap cards between NX and Nano without this kind of hassle?

Does PCIe in the M.2 need some kind of activation?