Any news? Would be very interested in having the MR9000 supported ... could also help with testing.
Sadly no. Still trying to figure out what the switch and the 3rd radio is. I haven't mess with this in a a few months.
Thanks for trying, don't sweat it. I gave mine away and picked up an ea8300. It's a piece of junk, too, even on 21.02 release candidate.
Considering the EA8300 is a very decent stable router, looks like one more troll comment...
It's not that it is a piece of junk, it's simply that software wasn't written for it's switch and 3rd radio is all.
He wasn't junking the MR9000, but the EA8300, which is a fine machine considering...
And sooooooo the MR8300 firmware works on this, the LAN ports are working and two of the radios are working.
1 Like
So there is a kernel panic at the beginning. It works when you do a bootipq but not a regular boot from either partition. Doing some digging around against other devices to figure why this is an issue.
The issue with the third radio could be wrong or missing firmware. BTW the info provided by Hardware Specs is wrong, the third radio is not a QCA9884 but a QCA9988. Couldn't find much info on this chip but it seems more or less the same as the QCA9984 so the ath10k-firmware-qca9984-ct package should do the trick.
Regarding the kernel panic, do you have a bootlog?
Yes and yes. Just gotta find the correct drivers for it.
Figured it out. The MDIO pin and reset definitions are missing in the .dts file which causes the kernel to panic or, with newer builds, to endlessly retry communication with the switch. Once those are fixed the MR9000 also boots OpenWrt from flash. Why it works at all for the MR8300 without those definitions is rather strange since both devices share the same hardware design apart from the 3rd radio.
Getting the 3rd radio to work was straight forward, replacing ath10k-firmware-qca9888-ct with ath10k-firmware-qca9984-ct and extracting the board calibration files from the OEM firmware was all that was needed.
After applying those fixes to NoTengoBattery's build (in a very dirty way I'm sure) I was able to build and flash a working firmware.
Please give details on your fixes so we can also try it out in a snapshot build. Thanks!
Here is my qcom-ipq4019-mr9000.dts. It makes use of the same xx8300.dtsi that the EA8300 and MR8300 use because the hardware configuration is more or less the same:
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
#include "qcom-ipq4019-xx8300.dtsi"
/ {
model = "Linksys MR9000 (Dallas)";
compatible = "linksys,mr9000", "qcom,ipq4019";
reserved-memory {
#address-cells = <1>;
#size-cells = <1>;
ranges;
ramoops@87500000 {
compatible = "ramoops";
reg = <0x87500000 0x600000>;
console-size = <0x200000>;
pmsg-size = <0x200000>;
record-size = <0x200000>;
ecc-size = <16>;
};
};
aliases {
led-boot = &led_blue;
led-failsafe = &led_red;
led-running = &led_green;
led-upgrade = &led_blue;
serial0 = &blsp1_uart1;
};
// Top panel LEDs, above Linksys logo
leds {
compatible = "gpio-leds";
led_blue: blue {
label = "blue:panel";
gpios = <&tlmm 46 GPIO_ACTIVE_LOW>;
};
led_red: red {
label = "red:panel";
gpios = <&tlmm 47 GPIO_ACTIVE_HIGH>;
panic-indicator;
};
led_green: green {
label = "green:panel";
gpios = <&tlmm 49 GPIO_ACTIVE_HIGH>;
};
// On back panel, above USB socket
led_usb: usb {
label = "green:usb";
gpios = <&tlmm 61 GPIO_ACTIVE_LOW>;
trigger-sources = <&usb3_port1>, <&usb3_port2>,
<&usb2_port1>;
linux,default-trigger = "usbport";
};
};
keys {
compatible = "gpio-keys";
reset {
label = "reset";
linux,code = <KEY_RESTART>;
gpios = <&tlmm 50 GPIO_ACTIVE_LOW>;
};
wps {
label = "wps";
linux,code = <KEY_WPS_BUTTON>;
gpios = <&tlmm 18 GPIO_ACTIVE_LOW>;
};
};
};
&mdio {
status = "okay";
pinctrl-0 = <&mdio_pins>;
pinctrl-names = "default";
reset-gpios = <&tlmm 54 GPIO_ACTIVE_LOW>;
reset-delay-us = <2000>;
reset-post-delay-us = <1000>;
};
&tlmm {
status = "okay";
mdio_pins: mdio_pinmux {
mux_1 {
pins = "gpio6";
function = "mdio";
bias-pull-up;
};
mux_2 {
pins = "gpio7";
function = "mdc";
bias-pull-up;
};
};
};
&wifi0 {
status = "okay";
qcom,ath10k-calibration-variant = "linksys-mr9000-fcc";
};
&wifi1 {
status = "okay";
ieee80211-freq-limit = <5170000 5330000>;
qcom,ath10k-calibration-variant = "linksys-mr9000-fcc";
};
&wifi2 {
status = "okay";
ieee80211-freq-limit = <5490000 5835000>;
qcom,ath10k-calibration-variant = "linksys-mr9000-fcc";
};
The LED config may not be entirely correct yet. There are 5 LEDs defined in the OEM DTB but in reality there is just 1 Multicolour LED. 2 of the GPIOs defined in the OEM DTB seem to drive the same green node of the LED while another of those GPIOs is apparently not connected to a LED at all.
Thanks. That gets the eth ports working in master!
But I get no wifi now. I think the build is missing linksys-mr9000-fcc. Can you please tell me how to include it in a build?
That refers to the board calibration files. Those can be extracted from OEM firmware or, since our device has a backup partition, simply copied over from there (/lib/firmware/). Then with the help of the qca-swiss-army-knife they have to be converted to generate the board-2.bin files for the radios. The big question is which of the considerable number of files to use.
If you just remove the calibration-variant statement from the .dts file, it should work with the standard board-2.bin supplied by the ath10k-firmware packages. This may or may not impair wireless performance.
1 Like
After removing the calibration-variant statement from the .dts file, I still get no wireless. In dmesg is the error "can not find board-2.bin or board.bin for"... (sic).
I thought it would work at least for the first 2 radios. Try replacing the board-2.bin files with those which contain the right calibration variant files. You have to rename the files to board-2.bin and place them in the folders /lib/firmware/ath10k/QCA4019/hw1.0/ and /QCA9984/hw1.0/.