Guys, FYI, PR to check for EEPROM with the MT7613BE has been opened on the MT76 GitHub by svanheule:
See the EAP235-Wall posts for comparative tests between OpenWrt master and OEM firmware v1.0.2.
Can someone do an OEM/OpenWrt comparison for the A6 v3? Would be curious to see how it plays out.
Line of sight
./iperf3 -c 192.168.1.1
Connecting to host 192.168.1.1, port 5201
[ 4] local 192.168.1.130 port 50680 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 51.4 MBytes 431 Mbits/sec
[ 4] 1.00-2.00 sec 56.9 MBytes 476 Mbits/sec
[ 4] 2.00-3.00 sec 54.5 MBytes 458 Mbits/sec
[ 4] 3.00-4.00 sec 35.8 MBytes 300 Mbits/sec
[ 4] 4.00-5.00 sec 11.1 MBytes 93.3 Mbits/sec
[ 4] 5.00-6.00 sec 14.2 MBytes 119 Mbits/sec
[ 4] 6.00-7.00 sec 29.9 MBytes 251 Mbits/sec
[ 4] 7.00-8.00 sec 44.8 MBytes 375 Mbits/sec
[ 4] 8.00-9.00 sec 20.4 MBytes 171 Mbits/sec
[ 4] 9.00-10.00 sec 39.5 MBytes 331 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 358 MBytes 301 Mbits/sec sender
[ 4] 0.00-10.00 sec 358 MBytes 300 Mbits/sec receiver
Across wall in next room with a door it drops significantly
$ ./iperf3 -c 192.168.1.1
Connecting to host 192.168.1.1, port 5201
[ 4] local 192.168.1.130 port 50717 connected to 192.168.1.1 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 5.75 MBytes 48.2 Mbits/sec
[ 4] 1.00-2.00 sec 2.00 MBytes 16.8 Mbits/sec
[ 4] 2.00-3.00 sec 4.88 MBytes 40.9 Mbits/sec
[ 4] 3.00-4.00 sec 2.25 MBytes 18.9 Mbits/sec
[ 4] 4.00-5.00 sec 3.62 MBytes 30.4 Mbits/sec
[ 4] 5.00-6.00 sec 3.50 MBytes 29.3 Mbits/sec
[ 4] 6.00-7.00 sec 5.12 MBytes 43.0 Mbits/sec
[ 4] 7.00-8.00 sec 3.12 MBytes 26.2 Mbits/sec
[ 4] 8.00-9.00 sec 1.25 MBytes 10.5 Mbits/sec
[ 4] 9.00-10.00 sec 2.62 MBytes 22.0 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 34.1 MBytes 28.6 Mbits/sec sender
[ 4] 0.00-10.00 sec 34.0 MBytes 28.5 Mbits/sec receiver
iperf Done.
Hello everyone , based on information from this topic , I was able to run the firmware on my archer c6u (RU version) with a working switch , I needed to edit reset.c , dts file and also edit tplink_safeloader.c to add the special_id from my device , but I don't understand how to add my edits to the pull request , and so I left a comment in conversation about this pull request , but even this I didn't succeed , so I have a request to correctly issue these patches so that soon you can already build firmwarte without any problems
Link on my comment: https://github.com/openwrt/openwrt/pull/3757#issuecomment-771599191
Good to hear
It is not common for a pull request to have commits from multiple authors.
when the pull request is accepted, you are welcome to create a new pull request that adds a profile to the makefile and the special_id to tplink_safeloader.c for your RU version.
but my device is the same, just with a different special_id, and I suppose that most likely ethernet in the dts file would also be worth registering for both versions (RU and EN), although of course it would be worth checking for the EN version first before confirming, but unfortunately I do not have it, otherwise the configuration, as far as I can tell, is identical , otherwise, I would of course try to create a new pull request
You have to wait for the EN version pull request to be accepted
After, when you make a new pull request, the only change it will have is the special_id
here is an example
I understood correctly that the pull request that i commented on was rejected , which means that i can add my own pull request? And has anyone posted a patch that reigns reset.c ?
no it is not rejected. it is "open"
everyone is waiting for the mdio reset issue to be fixed
I've sent the reset patch to linux-mips, let's see how it goes 
https://lore.kernel.org/linux-mips/20210203092140.12458-1-sander@svanheule.net/
Sysupgrade of Openwrt is broken in development or main branch,
- watchdog -
killall: telnetd: no process killed
Wed Feb 3 17:46:05 UTC 2021 upgrade: Sending TERM to remaining processes ... logd rpcd sh ubus hostapd wpa_supplicant netifd odhcpd uhttpd ntpd[262483.902962] device wlan0 left promiscuous mode
dnsmasq[262483.907783] br-lan: port 6(wlan0) entered disabled state
ubusd urngdsh: S: out of range
sh: S: out of range
[262483.970913] device wlan1 left promiscuous mode
[262483.975639] br-lan: port 5(wlan1) entered disabled state
Wed Feb 3 17:46:08 UTC 2021 upgrade: Sending KILL to remaining processes ...sh: S: out of range
sh: S: out of range
[262488.081822] sh (13246): drop_caches: 3
Wed Feb 3 17:46:09 UTC 2021 upgrade: Switching to ramdisk...
Wed Feb 3 17:46:12 UTC 2021 upgrade: Performing system upgrade...
[262490.959932] sh (13246): drop_caches: 3
Could not open mtd device: firmware
Can't open device for writing!
cat: write error: Broken pipe
[262490.979479] reboot: Restarting system
sysupgrade aborted with return code: 256
Could not open mtd device: firmware
Because the OpenWrt image of Archer A6 v3 doesn't have "firmware" partition, it's not defined in your dts.
yes it was not defined, as we are maintaining OS and Rootfs different partitions. Merging them had some other issue, OEM/Bootloader changing partition table, and bricking the device.
Did you try "firmware" in tplink-safeloader.c like Archer C6U v1?
yes same partition layout was applied, and it changed the partition layout. And bricked as below
I think it is worth trying again, there may have been a mistake or typo that caused the brick
I don't know exactly what this means, but it looks like the length of a partition was wrong...
make sure that whatever you do in tplink_safeloader.c, that the DTS also matches
are we sure that the partition table is the same as Archer C6U? I would not copy from that, rather do the math ourselves to verify
also when making a joined partition "firmware" you need the compatible line
compatible = "denx,uimage";
@mpratt14 will give a try. TP-link-safeloader.c partition table is from the dump of OEM firmware using tp-link tool available in scripts folder. But Operwrt partition layout was similar to C6U, as lengths were same.
backport of the mdio reset fix coming soon
https://patchwork.ozlabs.org/project/openwrt/patch/20210204144914.293546-1-sander@svanheule.net/
It worked. It was typo I guess earlier.
Glad to see it works on the easy way! 