Wireless
Issues related to Intel® Wireless Adapters and technologies
6174 Discussions

Problem with AX200 wi-fi module

stevan_marinkovic
645 Views

Dear Community,

 

We are using your Wi-Fi 6 AX200 wi-fi module in order to proof our development concept and planning to build it into final solution.
But we have the following problem:


- We are using ARM processor in Xilinx Zynq UltraScale+ FPGA and running Linux Kernel 5.4 on it.
- Firmware file that we are using is iwlwifi-cc-a0-46.ucode (also tried FWs 48 and 50 without success)
- These are the additional configs that we enabled in our Kernel:
   CONFIG_FW_LOADER=y
   CONFIG_PCI_MSI=y
   CONFIG_EXTRA_FIRMWARE="iwlwifi-cc-a0-46.ucode"
   CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
   CONFIG_IWLWIFI=y
   CONFIG_IWLWIFI_LEDS=y
   CONFIG_IWLDVM=y
   CONFIG_IWLMVM=y


- After executing iw dev command from Kernel command line, we have the following:
phy#0
Interface wlan0
ifindex 4
wdev 0x1
addr 6c:94:66:a2:04:ae
type managed
txpower 0.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0


- Then after "ip link show wlan0":
4: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 6c:94:66:a2:04:ae brd ff:ff:ff:ff:ff:ff

- But when we try to set the link up (ip link set wlan0 up), we have the following errors (complete dmesg is below):

root@bvgen2:~# ip link set wlan0 up
[ 4326.760874] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[ 4326.911185] iwlwifi 0000:01:00.0: FW already configured (0) - re-configuring
[ 4327.118590] iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 4327.126516] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[ 4327.132087] iwlwifi 0000:01:00.0: Status: 0x00000050, count: 6
[ 4327.137918] iwlwifi 0000:01:00.0: Loaded firmware version: 46.177b3e46.0
[ 4327.144615] iwlwifi 0000:01:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[ 4327.151572] iwlwifi 0000:01:00.0: 0x00A03EF5 | trm_hw_status0
[ 4327.157314] iwlwifi 0000:01:00.0: 0x00000000 | trm_hw_status1
[ 4327.163057] iwlwifi 0000:01:00.0: 0x004FC308 | branchlink2
[ 4327.168536] iwlwifi 0000:01:00.0: 0x004E8926 | interruptlink1
[ 4327.174279] iwlwifi 0000:01:00.0: 0x004E8926 | interruptlink2
[ 4327.180021] iwlwifi 0000:01:00.0: 0x00016F7E | data1
[ 4327.184981] iwlwifi 0000:01:00.0: 0x00001000 | data2
[ 4327.189941] iwlwifi 0000:01:00.0: 0xF0000008 | data3
[ 4327.194902] iwlwifi 0000:01:00.0: 0x00000000 | beacon time
[ 4327.200384] iwlwifi 0000:01:00.0: 0x0004FAB9 | tsf low
[ 4327.205518] iwlwifi 0000:01:00.0: 0x00000000 | tsf hi
[ 4327.210563] iwlwifi 0000:01:00.0: 0x00000000 | time gp1
[ 4327.215788] iwlwifi 0000:01:00.0: 0x0004FAB9 | time gp2
[ 4327.221007] iwlwifi 0000:01:00.0: 0x00000001 | uCode revision type
[ 4327.227183] iwlwifi 0000:01:00.0: 0x0000002E | uCode version major
[ 4327.233360] iwlwifi 0000:01:00.0: 0x177B3E46 | uCode version minor
[ 4327.239536] iwlwifi 0000:01:00.0: 0x00000340 | hw version
[ 4327.244929] iwlwifi 0000:01:00.0: 0x18489000 | board version
[ 4327.250584] iwlwifi 0000:01:00.0: 0x800EF500 | hcmd
[ 4327.255460] iwlwifi 0000:01:00.0: 0x80120000 | isr0
[ 4327.260332] iwlwifi 0000:01:00.0: 0x00000000 | isr1
[ 4327.265204] iwlwifi 0000:01:00.0: 0x08F00002 | isr2
[ 4327.270080] iwlwifi 0000:01:00.0: 0x00C0001C | isr3
[ 4327.274954] iwlwifi 0000:01:00.0: 0x00000000 | isr4
[ 4327.279829] iwlwifi 0000:01:00.0: 0x00000000 | last cmd Id
[ 4327.285309] iwlwifi 0000:01:00.0: 0x00016F7E | wait_event
[ 4327.290707] iwlwifi 0000:01:00.0: 0x00000000 | l2p_control
[ 4327.296186] iwlwifi 0000:01:00.0: 0x00002820 | l2p_duration
[ 4327.301754] iwlwifi 0000:01:00.0: 0x00000000 | l2p_mhvalid
[ 4327.307235] iwlwifi 0000:01:00.0: 0x00000000 | l2p_addr_match
[ 4327.312978] iwlwifi 0000:01:00.0: 0x00000009 | lmpm_pmg_sel
[ 4327.318545] iwlwifi 0000:01:00.0: 0x19071335 | timestamp
[ 4327.323853] iwlwifi 0000:01:00.0: 0x0000082C | flow_handler
[ 4327.329455] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[ 4327.335018] iwlwifi 0000:01:00.0: Status: 0x00000050, count: 7
[ 4327.340845] iwlwifi 0000:01:00.0: 0x20000034 | NMI_INTERRUPT_WDG
[ 4327.346847] iwlwifi 0000:01:00.0: 0x00000000 | umac branchlink1
[ 4327.352759] iwlwifi 0000:01:00.0: 0xC008B1C0 | umac branchlink2
[ 4327.358671] iwlwifi 0000:01:00.0: 0x8048BC5C | umac interruptlink1
[ 4327.364845] iwlwifi 0000:01:00.0: 0xC0084264 | umac interruptlink2
[ 4327.371021] iwlwifi 0000:01:00.0: 0x00000004 | umac data1
[ 4327.376416] iwlwifi 0000:01:00.0: 0xC0084264 | umac data2
[ 4327.381810] iwlwifi 0000:01:00.0: 0xDEADBEEF | umac data3
[ 4327.387204] iwlwifi 0000:01:00.0: 0x0000002E | umac major
[ 4327.392600] iwlwifi 0000:01:00.0: 0x177B3E46 | umac minor
[ 4327.397994] iwlwifi 0000:01:00.0: 0x0004FAA2 | frame pointer
[ 4327.403650] iwlwifi 0000:01:00.0: 0xC08869B4 | stack pointer
[ 4327.409305] iwlwifi 0000:01:00.0: 0x0009050D | last host cmd
[ 4327.414961] iwlwifi 0000:01:00.0: 0x00000000 | isr status reg
[ 4327.420704] iwlwifi 0000:01:00.0: Fseq Registers:
[ 4327.425400] iwlwifi 0000:01:00.0: 0xE0000101 | FSEQ_ERROR_CODE
[ 4327.431224] iwlwifi 0000:01:00.0: 0x80290008 | FSEQ_TOP_INIT_VERSION
[ 4327.437569] iwlwifi 0000:01:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[ 4327.444088] iwlwifi 0000:01:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 4327.449999] iwlwifi 0000:01:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 4327.456604] iwlwifi 0000:01:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 4327.462515] iwlwifi 0000:01:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 4327.468079] iwlwifi 0000:01:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 4327.473643] iwlwifi 0000:01:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 4327.479730] iwlwifi 0000:01:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 4327.485815] iwlwifi 0000:01:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 4327.493636] iwlwifi 0000:01:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 4327.501810] iwlwifi 0000:01:00.0: Firmware error during reconfiguration - reprobe!
[ 4327.509385] iwlwifi 0000:01:00.0: FW error in SYNC CMD RFH_QUEUE_CONFIG_CMD
[ 4327.509411] iwlwifi 0000:01:00.0: LED command failed: -5
[ 4327.516346] CPU: 3 PID: 787 Comm: ip Tainted: G O 5.4.0-xilinx-v2020.1 #1
[ 4327.521691] iwlwifi 0000:01:00.0: LED command failed: -5
[ 4327.529712] Hardware name: xlnx,zynqmp (DT)
[ 4327.529714] Call trace:
[ 4327.529722] dump_backtrace+0x0/0x140
[ 4327.529730] show_stack+0x14/0x20
[ 4327.548560] dump_stack+0xac/0xd0
[ 4327.551867] iwl_trans_pcie_gen2_send_hcmd+0x3b4/0x3c0
[ 4327.556995] iwl_trans_send_cmd+0x54/0x108
[ 4327.561075] iwl_mvm_send_cmd+0x18/0x40
[ 4327.564895] iwl_configure_rxq+0xfc/0x168
[ 4327.568887] iwl_mvm_up+0x4fc/0x5d8
[ 4327.572358] __iwl_mvm_mac_start+0x2c/0x1d8
[ 4327.576524] iwl_mvm_mac_start+0x28/0x48
[ 4327.580432] drv_start+0x30/0x50
[ 4327.583644] ieee80211_do_open+0x1f0/0x830
[ 4327.587723] ieee80211_open+0x44/0x60
[ 4327.591370] __dev_open+0xe4/0x160
[ 4327.594762] __dev_change_flags+0x160/0x1b8
[ 4327.598929] dev_change_flags+0x20/0x60
[ 4327.602747] do_setlink+0x5f0/0xc08
[ 4327.606220] __rtnl_newlink+0x3e8/0x6e8
[ 4327.610038] rtnl_newlink+0x48/0x70
[ 4327.613510] rtnetlink_rcv_msg+0x2a0/0x348
[ 4327.617592] netlink_rcv_skb+0x54/0x110
[ 4327.621411] rtnetlink_rcv+0x14/0x20
[ 4327.624969] netlink_unicast+0x174/0x200
[ 4327.628875] netlink_sendmsg+0x15c/0x328
[ 4327.632781] ___sys_sendmsg+0x280/0x2c0
[ 4327.636600] __sys_sendmsg+0x64/0xb8
[ 4327.640159] __arm64_sys_sendmsg+0x20/0x28
[ 4327.644241] el0_svc_common.constprop.0+0x68/0x160
[ 4327.649022] el0_svc_handler+0x6c/0x88
[ 4327.652753] el0_svc+0x8/0xc
[ 4327.655636] iwlwifi 0000:01:00.0: Failed to configure RX queues: -5
RTNETLINK answers: Input/output error

I saw a lot of similar issues on different forums (but with different Linux Kernels), tried all of suggested workarounds, but without success.
Could you please suggest me proper solution for upper explained problem?

 

Thanks a lot,

Stevan

0 Kudos
1 Solution
AndrewG_Intel
Moderator
621 Views

Hello @stevan_marinkovic

Thank you for posting on the Intel® communities.


We understand you have opened an internal Web Ticket with us regarding the same hardware/software environment and the same issue. In this case, we will continue to help you through the internal Web Ticket. We will therefore close this community case. Thank you.


Best regards,

Andrew G.

Intel Customer Support Technician


View solution in original post

1 Reply
AndrewG_Intel
Moderator
622 Views

Hello @stevan_marinkovic

Thank you for posting on the Intel® communities.


We understand you have opened an internal Web Ticket with us regarding the same hardware/software environment and the same issue. In this case, we will continue to help you through the internal Web Ticket. We will therefore close this community case. Thank you.


Best regards,

Andrew G.

Intel Customer Support Technician


Reply