[MT7613BE] -STA does not connect to access points with a bandwidth of 160 MHz.

[rah66]

Hi,

I have a device Xiaomi MiWiFi Range Extender AC1200 (RC04), this is an updated 2023 version of the device Xiaomi MiWiFi Range Extender AC1200 (RA75) - OpenWRT RA75 link. MT7612EN (in RA75) updated to MT7613BE (in RC04).

I have compiled a firmware based on RA75, excluding kmod-mt76x2 module for MT7612EN and adding three modules: kmod-mt7615-firmware (includes: kmod-mt7615-common, kmod-mt7615e), kmod-mt7663-firmware-ap, kmod-mt7663-firmware-sta for MT7613BE.

bootlogRC04_23.05.5.txt

Wifi module MT7613BE in STA client mode connects to the Access Point (Xiaomi AX3000T RD03 OpenWRT) at a width of 80 MHz and works stably.

bootlogRC04_23.05.5_cont.txt

But if switch the access point from 80 to 160 width, the connection immediately drops.

[ 5263.722605] phy1-sta0: deauthenticated from 46:f7:70:fc:4b:bb (Reason: 3=DEAUTH_LEAVING)
[ 5267.448731] phy1-sta0: authenticate with 46:f7:70:fc:4b:bb
[ 5267.459617] phy1-sta0: send auth to 46:f7:70:fc:4b:bb (try 1/3)
[ 5267.469750] phy1-sta0: send auth to 46:f7:70:fc:4b:bb (try 2/3)
[ 5267.479798] phy1-sta0: send auth to 46:f7:70:fc:4b:bb (try 3/3)
[ 5267.489841] phy1-sta0: authentication with 46:f7:70:fc:4b:bb timed out
[ 5269.392603] phy1-sta0: authenticate with 46:f7:70:fc:4b:bb
[ 5269.403590] phy1-sta0: send auth to 46:f7:70:fc:4b:bb (try 1/3)
[ 5269.414075] phy1-sta0: send auth to 46:f7:70:fc:4b:bb (try 2/3)
[ 5269.424282] phy1-sta0: send auth to 46:f7:70:fc:4b:bb (try 3/3)
[ 5269.434709] phy1-sta0: authentication with 46:f7:70:fc:4b:bb timed out
[ 5271.839253] phy1-sta0: authenticate with 46:f7:70:fc:4b:bb
[ 5271.850424] phy1-sta0: send auth to 46:f7:70:fc:4b:bb (try 1/3)
[ 5271.860658] phy1-sta0: send auth to 46:f7:70:fc:4b:bb (try 2/3)
[ 5271.870686] phy1-sta0: send auth to 46:f7:70:fc:4b:bb (try 3/3)
[ 5271.880946] phy1-sta0: authentication with 46:f7:70:fc:4b:bb timed out

This error is not corrected by switching mode AX/AC, channels 36, 40, 44, 48, (64-128), changing WEP encryption and disabling encryption.
I also read that the region and DFS may have an impact. Conducted testing on US, PA and RU regions.

root@MiWiFi_RC04:/# iw reg get
global
country US: DFS-FCC
        (902 - 904 @ 2), (N/A, 30), (N/A)
        (904 - 920 @ 16), (N/A, 30), (N/A)
        (920 - 928 @ 8), (N/A, 30), (N/A)
        (2400 - 2472 @ 40), (N/A, 30), (N/A)
        (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
        (5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
        (5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
        (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
        (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
        (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
        (57240 - 71000 @ 2160), (N/A, 40), (N/A)

root@MiWiFi_RC04:/# iw reg get
global
country PA: DFS-FCC
        (2400 - 2483 @ 40), (N/A, 36), (N/A)
        (5150 - 5250 @ 80), (N/A, 36), (N/A), AUTO-BW
        (5250 - 5350 @ 80), (N/A, 30), (N/A), AUTO-BW
        (5470 - 5725 @ 160), (N/A, 30), (N/A)
        (5725 - 5850 @ 80), (N/A, 36), (N/A)
        (57000 - 64000 @ 2160), (N/A, 43), (N/A)

root@MiWiFi_RC04:/# iw reg get
global
country RU: DFS-UNSET
        (2400 - 2483 @ 40), (N/A, 20), (N/A)
        (5150 - 5350 @ 160), (N/A, 20), (N/A), NO-OUTDOOR
        (5650 - 5850 @ 160), (N/A, 20), (N/A), NO-OUTDOOR
        (5925 - 6425 @ 160), (N/A, 20), (N/A), NO-OUTDOOR
        (57000 - 66000 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR

RU region no DFS and have 160 on 36-64 channels.

The problem of connecting MT7613 in client mode to 160 width is confirmed on Xiaomi AX3000T RD03 OpenWRT (MT7981BA/MT7976CN) and Asus RT-AX88U MerlinWRT (Broadcom BCM49408) access point routers.

UPD Perhaps, the file structure of the original Xiaomi firmware of the latest version *.243, extracted from the dump, will help to study the problem and fix it. There are no problems with the original firmware.
RC04_GD25Q128C_orig_Xiaomi_v.243_11.01.2025.zip

P.S. I am new to OpenWRT, my first device AX3000T with OpenWRT appeared on December 15, 2024, if there are questions about log outputs, etc., please accompany them with commands on how to get them.