IPQ5018: Support for Linksys MX2000 Atlas 6 & MX5500 Atlas 6 Pro

georgem83 · 2024-04-04T18:19:25.755Z

Thank you @hzyitc, will test that small patch tomorrow.

I’ve got the same DTS except for port6 being configured as the cpu port on the switch and the reset-gpios property is defined at the mdio level, else the phys can’t be scanned.
Will circle back tomorrow

georgem83 · 2024-04-05T06:13:11.875Z

so, just tested the suggested patch and the results are confusing.
The patch enables Serdev auto-negotiation when BIT(7) of the PWS reg is set to 0 (disabled when set to 1)

When the patch is applied and auto-neg is enabled:

boot from uboot (initramfs image): there's no traffic
boot from nand (factory image): there's traffic and the switch works correctly

When the patch is not applied and auto-neg is disabled, the results are opposite:

boot from uboot (initramfs image): there's traffic and the switch works correctly
boot from nand (factory image): there's no traffic

any thoughts?

hzyitc · 2024-04-05T06:45:25.310Z

The reset GPIO of switch maybe incorrect. So when booting from uboot, some settings may be inherited from uboot.

tomw · 2024-04-09T11:59:39.791Z

These are very interesting updates. As someone with an abundance of MX5500 nodes, I'm eagerly awaiting a build. Happy to help with testing and validation. I'm a network and security guy by trade, so I should be able to meaningfully test anything you want me to.

georgem83 · 2024-04-10T17:24:53.240Z

I'm having issues with wifi, the MX5500 has a QCN9074 (9024 actually) radio.
Ath11k loads correctly, finds the regdb.bin (extracted from the qca repo on codelinaro). I've used the same bdwlan file that the stock FW uses (bdwlan.ba0), but get the following error:

[   21.900849] ath11k_pci 0001:01:00.0: No reg rules available
[   21.904037] ath11k_pci 0001:01:00.0: failed to extract regulatory info from received event

I then tried the same file from different regions such as FCC and EU and also the .bin instead of .ba0 files. With some BDFs, luci suggests it's using a 6Ghz channel while the radio doesn't support that, and with others it shows the correct 5Ghz channel, but only when specific countries are selected (for ex. US when using the FCC BDF file). In that case, one may think it works, but none of my devices can actually detect the SSID or can connect to it.

@lytr: I know you have looked into this as well, perhaps you can give me some pointers?
Anyone else?

lytr · 2024-04-10T18:22:37.033Z

You probably have this problem: OpenWrt support for Linksys MX8500 - #47 by lytr

georgem83 · 2024-04-11T01:49:12.147Z

you're right, the stock FW version is 2.4 (WLAN.HK.2.4-02142-QCAHKSWPL_SILICONZ-1.395212.1.407947.2 v1)
I've downloaded the board-2.bin v2.4 from the qca repo here but it contains no regdb info. Is there any way to convert the regdb found in v2.9 and make it work for v.2.4?

dingo · 2024-04-11T16:35:21.687Z

qca swiss army-knife maybe ? https://github.com/qca/qca-swiss-army-knife

georgem83 · 2024-04-12T09:13:24.453Z

We use that tool to package the BDF and/or extract the regdb from the QCA board-2.bin. But AFAIK the tool can’t be used to convert the regdb from a v2.9 BDF to a v2.4.

robimarko · 2024-04-12T10:28:06.195Z

Regdb does not depend on FW version, its format has been the same from the start unless its 6G regulatory

georgem83 · 2024-04-12T11:12:29.687Z

I was led to believe the regdb does differ based on version, see this post by @lytr:

OpenWrt support for Linksys MX8500 For Developers

There is regdb (starting at address 0x12df0 with size 0x1c00). This is default for the firmware WLAN.HK.2.4.0.1. BDFs for newer firmware use regdb with size 0x2800 (starting at the same address).

I’ve extracted the regdb from here

Ath11k loads, radio is up, but it’s not broadcasting.


root@ae-ap06:~# cat /etc/config/wireless 

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'soc@0/a0000000.pcie/pci0001:00/0001:00:00.0/0001:01:00.0'
        option channel '48'
        option band '5g'
        option htmode 'HE80'
        option cell_density '0'
        option country 'US'

config wifi-iface 'wifinet0'
        option device 'radio0'
        option mode 'ap'
        option ssid 'M-TEST'
        option encryption 'psk2+ccmp'
        option key 'test1234'
        option network 'lan'

Regulatory:


root@ae-ap06:~# 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)

phy#0 (self-managed)
country US: DFS-FCC
        (2402 - 2472 @ 40), (6, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
        (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
        (5925 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW

What am I missing?

robimarko · 2024-04-12T11:15:10.180Z

Well, it does differ in the sense that its growing and being updated but it is not tied for FW versions.

Sadly, I have no idea what is wrong in your case though

lytr · 2024-04-12T11:15:34.844Z

For IPQ5018, QCN6122 and QCN9074 the format is changed. Starting from FW 2.5 their using 10k regdb format. Previous FW use 7k regdb format (like IPQ6018, IPQ8074).

robimarko · 2024-04-12T11:16:30.225Z

Probably space for 6GHz rules as well as that was not included previously

georgem83 · 2024-04-12T11:24:13.641Z

I saw this patch, do you think reg domain needs to be removed?

BDFs and precal blobs are just black boxes to me and I wouldn’t know where to start

lytr · 2024-04-12T11:24:19.695Z

I've prepared a regdb update tool: https://github.com/testuser7/ath_bdf_tool
to make life easier...

But the case with regdb extension is not supported.

lytr · 2024-04-12T11:26:15.177Z

If regdomain is set, then probably yes.

georgem83 · 2024-04-12T11:42:43.157Z

will test the script to remove the regdomain and report back..

dingo · 2024-04-12T11:53:37.006Z

hoping theres commits soon then maybe i can move forward with mine

georgem83 · 2024-04-12T12:14:32.231Z

removed regdomain, but still can't connect to the AP. At least now it's not barfing on a country code change. When CC is set to US:

root@ae-ap06:~# 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)

phy#0 (self-managed)
country US: DFS-FCC
        (2402 - 2472 @ 40), (6, 30), (N/A)
        (5170 - 5250 @ 80), (N/A, 30), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
        (5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS, AUTO-BW
        (5735 - 5895 @ 160), (N/A, 30), (N/A), AUTO-BW
        (5925 - 7125 @ 160), (N/A, 30), (N/A), NO-OUTDOOR, AUTO-BW

changing it to GB:

root@ae-ap06:~# iw reg get
global
country GB: DFS-ETSI
        (2400 - 2483 @ 40), (N/A, 20), (N/A)
        (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
        (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
        (5470 - 5730 @ 160), (N/A, 26), (0 ms), DFS
        (5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
        (5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
        (57000 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0 (self-managed)
country GB: DFS-ETSI
        (2402 - 2482 @ 40), (N/A, 20), (N/A)
        (5170 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
        (5250 - 5330 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
        (5490 - 5590 @ 80), (N/A, 30), (0 ms), DFS, AUTO-BW
        (5590 - 5650 @ 40), (N/A, 30), (600000 ms), DFS, AUTO-BW
        (5650 - 5710 @ 40), (N/A, 30), (0 ms), DFS, AUTO-BW
        (5945 - 6425 @ 160), (N/A, 24), (N/A), NO-OUTDOOR, AUTO-BW

just to validate I get these steps right:

check OEM bootlog for BDF file used (in my case bdwlan.ba0)
grab that specific file from FCC or EU folder (see list of available folders below)
remove regdomain: ath11k_bdf_tool.py -r bdwlan.ba0 -o board-2.qcn9074.bin
package with qca-swiss-armyknife: ath11k-bdencoder -c board-2.json -o board-2.bin
upload board-2.bin to router replacing the current one
reboot

anything else?

image477×502 4.41 KB