Nano won't boot with intel 8260NGW mini-pcie wifi card.

Nothing shows up on display, not even nvidia logo.

wonder what I can do to diagnose it.

Already run sudo apt-get install linux-firmware, checked /lib/firmware has intel 8000 series driver

If anyone get other intel card working please let me know too.

Thx.

Are you able to get the UART log from the board?

@WayneWWW Serial is not open when the board boot up with the wifi card installed.

I connect through microUSB to read Serial, is there something else I should do to get the log?

Please let me know I will get it tested.

Hi,

Could you use the serial connector on nano devkit for the log?

We notice this is a known issue on our side too. Still checking.

Ok I will read and get the log tmr.

Cool if it’s a known issue that would be good news. Meanwhile i will still try to get the log.

Hi,

After some investigation, we found out the root cause.

The Intel 8260 is using the I2C pins as a different interface, which causes it to drive the I2C bus low. This causes I2C transactions from the bootloader to the ID_EEPROM (which is on the same bus as the M.2 I2C) to fail, causing the bootloader to hang.

In the meantime, this issue also happens to Jetson Xavier due to same reason.

We can only suggest you not to use this card. Intel uses I2C pins on this card for different usecase which we don’t know. Maybe they have other purpose on their platform.

I’m considering trying tomorrow to mask the keyed pins before insertion. Does anyone suggest not?
This should disable Bluetooth. My understanding is that WiFi is PCIe, but Bluetooth us over USB. It is also my understanding g that the keyed pins are auxiliary, carrying different types of signals such as i2c and USB.

That sounds like a valid idea. If you make any progress please report back thanks!

I found a intel 8265 in my laptop, so I replaced my laptop wifi with 8260, and jetson is on 8265.

It’s the same that have happened to me with an Intel 8265! Is it due to the same thing related to the I2C pins?

Better sharing the dmesg with us to debug.

Can’t do anything! Nano can’t boot, only black screen while green LED is on!

Can you paste the output over the serial port pins?
The 8265ngw module is supposed to be supported perfectly. Are you sure that you don’t have and 8260? That has an electrical incompatibility due to the i2c bus exposed in m.2 key E.

Sorry, I don’t know how to paste the output over the serial port pins.
It is the 8265NGW.
I have formatted the SD and I have flashed it with Balena Etcher. It boots again normally. I switched off, installed the 8265 and this time it could boot with no problem, but no WiFi card detected neither Bluetooth device. Later, I had the same problem with the black screen, so I have to format the SD card again.
Oh, my god

Regarding intel 8260 i2c issue, is it possible not to use i2c at bootloader in Jetson nano?
If yes, could you tell me the location of bootloader source code in order to implement that?

For those who have intel 8260 and still want it to work with nano, you can just mask out the I2C pins on the wifi card with tape.

The I2C signals use 8th and 9th pins on the back (counting from right to left).

https://1drv.ms/u/s!ApXJrfCKTCq_gQAVFeDSbXuwPwa4

Hi huyijfmqp,

Great post. Believe this can help others.

Hi huyijfmqp,
Does that mean it works but without a bluetooth?

Hi Simon_L,

Bluetooth should work because it’s I2C that we masked out. BT on 8260 is a separate USB device which seems functional on nano. Here’s some info from the stock driver/kernel of R32.2 image:

$ dmesg | egrep -i “iwlwifi | blue”
[ 0.614861] Bluetooth: Core ver 2.22
[ 0.614919] Bluetooth: HCI device and connection manager initialized
[ 0.614933] Bluetooth: HCI socket layer initialized
[ 0.614942] Bluetooth: L2CAP socket layer initialized
[ 0.614967] Bluetooth: SCO socket layer initialized
[ 1.923957] Bluetooth: RFCOMM socket layer initialized
[ 1.923968] Bluetooth: RFCOMM ver 1.11
[ 1.923974] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1.923979] Bluetooth: HIDP socket layer initialized
[ 5.883284] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[ 5.891915] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8000C-26.ucode failed with error -2
[ 5.891922] iwlwifi 0000:01:00.0: Falling back to user helper
[ 5.892885] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8000C-25.ucode failed with error -2
[ 5.892889] iwlwifi 0000:01:00.0: Falling back to user helper
[ 5.896148] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8000C-24.ucode failed with error -2
[ 5.896154] iwlwifi 0000:01:00.0: Falling back to user helper
[ 5.899547] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8000C-23.ucode failed with error -2
[ 5.899553] iwlwifi 0000:01:00.0: Falling back to user helper
[ 5.995194] iwlwifi 0000:01:00.0: loaded firmware version 22.391740.0 op_mode iwlmvm
[ 6.050941] Bluetooth: hci0: Firmware revision 0.0 build 176 week 45 2017
[ 6.803187] iwlwifi 0000:01:00.0: Detected Intel® Dual Band Wireless AC 8260, REV=0x208
[ 6.805617] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 6.806465] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 7.705053] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 7.705065] Bluetooth: BNEP socket layer initialized
[ 7.818634] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 7.819067] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 7.959963] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 7.960319] iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled

$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

$ hciconfig hci0
hci0: Type: Primary Bus: USB
BD Address: A4:34:D9:6F:72:E5 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:1349 acl:0 sco:0 events:85 errors:0
TX bytes:2889 acl:0 sco:0 commands:85 errors:0

$ ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.111 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::a634:d9ff:fe6f:72e1 prefixlen 64 scopeid 0x20
ether a4:34:d9:6f:72:e1 txqueuelen 1000 (Ethernet)
RX packets 1356 bytes 136846 (136.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 556 bytes 114020 (114.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/5p, 480M
|__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

$ lsusb
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ lspci -nn
00:01.0 PCI bridge [0604]: NVIDIA Corporation Device [10de:0fae] (rev a1)
00:02.0 PCI bridge [0604]: NVIDIA Corporation Device [10de:0faf] (rev a1)
01:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)

I’m working on a headless setup without any BT devices at hand, so sorry I cannot verify it for you.

Thanks. I was wondering if I should go for it because I can get one cheap.