Adding support for linksys MR7500

For Developers
21

no idea why this one is complaining:
[ 403.615557] _adpt_hppe_instance0_mode_get[2280]:ERROR:when the port_interface_mode of port 2 is 0, mode0:11 cannot be supported for lan

and this
[13130.107339] uniphy autoneg time out! for wan

22

your not the only one in the community :wink:
Qualcommax NSS Build - Community Builds, Projects & Packages - OpenWrt Forum

23

Current status:
Wi-Fi:
image

  • 6G: working (including 160)
    • set country code & encryption to WPA3
  • 5G: working except for 160, probably not supported by 6018 itself
  • 2.4G: working

ETH:

  • QCA LAN ports: working
  • AQR WAN port: link is not up working!

If you would like to test: link

I have also posted the relevant log and info in the MX8500 post and was taken down by staff for being off-topic except that it is highly likely the same issue MX8500 was having ...

Edit: Add ss of all radio and link to latest test build that has most functions working except for LED and USB

1 Like
24

Aight thanks to whom removed my post, I have figured out myself: IPQ6018 is not in the HHPE target list therefore the AQR hook was never applied.
Now it has been fixed.

Two more things to fix then I think we are gtg for a PR: USB & PWM LED

Huge for the program:

image
image1491×229 22.1 KB

1 Like
25

PR is up: qualcommax: ipq60xx: add Linksys MR7500 support by PIPIPIG233666 · Pull Request #17428 · openwrt/openwrt
Test build can be found at #23

1 Like
26

Not sure if you made some adjustments already but apart of the uboot part i am ready to flash my spare MR7500.
The Uboot part is new to me. Is there no other option to integrate the firmware part into the Openwrt file or like a module adding?

27

Unfortunately, the way Linksys made it work doesn't apply to how OpenWrt does it.
It is easier enough to edit the U-boot parameter as you can just ssh in after the first flash and do it from there without needing serial access.

Edit: more details can be found here on the 8500 post: OpenWrt support for Linksys MX8500 - #77 by lytr

PS: also the OEM fw still works with the edited bootcmd so no need to worry about breaking it.

28

this is very lame but i managed to use the third radio as 5G:

image
image875×121 14.6 KB

Edit: this is on 2.12 fw and 6G simply doesn't work

29

image
image2033×964 154 KB

next step is to get NSS up...
currently a single core throughput is capped at around 800

30

If you used a different BDF with the firmware, these will be the results...

31

Nope, used the same BDF, only loaded 2.12 FW

32

Wait, stock uses *.ba4 -> 164 in dec, should I change the header of bdf from 255 to 164 and try again?

33

No, id 255 is requested.

34

Did some testing with only the openwrt firmware so, without the uboot step.
The 6GHz channel is not very stable.. Channel analysis does not show any 6GHz sidd ( i have at least two from the other MR7500)
But when use "join network mode" is was able to connect with those SSID.

Channel Analysis

Does not show signals on 6GHz

=========================================================

Join Network: Wireless Scan

when using scan network it does sees the 6GHz SSID’s

entering “wpa mixed” result in a disabled 6GHz wifi and no reaction on the “enable” option.

35

Huh,

image
image2686×1394 263 KB

Edit: those are from my neighbors as I do not have other 6GHz around. (by next week I'll get my hands on a CR1000A, but it shouldn't be any issue for the scan)
Also I do have a problem after scanning the 6G radio would go off and restarting the radio makes it work again.
Havn't lost the radio so far, we'll see how long it lasts this time.

36

WPA3 (sae) is required for 6GHz band.

37

Please provide logs.

38

Doesn't look like it happened this time when I have a client connected, will defo grab logs next time it happens

39

After a reboot the channel analyzer does show 6GHz SIDD.
But i still am at a loss how to do the Uboot step. If i was running the original most recent linksys firmware the needed Wlan firmware would already in the wlan chip?
So why the unblob step i do not understand.

40

If i was running the original most recent linksys firmware the needed Wlan firmware would already in the wlan chip?
So why the unblob step i do not understand.

unblob is probably unnecessary because that only makes sure you are loading the latest fw, bootcmd is still needed.

But i still am at a loss how to do the Uboot step

ssh into any install as long as you have ssh access, then
fw_setenv bootcmd 'aq_load_fw; if test $auto_recovery = no; then bootipq; elif test $boot_part = 1; then run bootpart1; else run bootpart2; fi'