Having some success using the RE200v3 image on RE220v1.
High level steps
Connect to Serial
Interrupt U-Boot
tftpboot RE200v3 initramfs version
sysupgrade the RE200v3 sysupgrade version
Leds all work properly. Tested with script in above post.
There are a couple of oddities with LEDs, nothing major and probably the same behavior on the RE200v3.
On boot, during u-boot phase a lights come on. Then they all go off during the time their should be the flashing to indicate the timing to go to failsafe.
During normal operation using just wifi, the wifi2g and wifi5g are blinking as expected, but the power light is off.
If I manually toggle off the power light per above script, all lights go off. If I toggle power light back on, all lights return to their previous state (some on, some off)
Ran tyrekick.sh with medium. All passed
This was run on RE220v1 with RE200v3 image, so script reports it as RE200v3. Version 22.03.
model,OUI,testID,result-v1
TP-Link-RE200-v3,74da88,inet-dns-000001,pass
TP-Link-RE200-v3,74da88,ntp-000001,pass
TP-Link-RE200-v3,74da88,uhttpd-000001,pass
TP-Link-RE200-v3,74da88,firewall-fw4-test-000001,pass
TP-Link-RE200-v3,74da88,opkg-unzip-000001,pass
TP-Link-RE200-v3,74da88,iperf3-000001,pass
TP-Link-RE200-v3,74da88,all-radio-on-000001,pass
TP-Link-RE200-v3,74da88,wireless-extra-options-radio0-2g-11-10-psk2,pass
TP-Link-RE200-v3,74da88,wireless-extra-options-radio1-5g-36-10-psk2+ccmp,pass
TP-Link-RE200-v3,74da88,radio0-2g-1-10-psk2,pass
TP-Link-RE200-v3,74da88,radio0-2g-1-10-sae,pass
TP-Link-RE200-v3,74da88,radio0-2g-1-10-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio0-2g-1-1-psk2,pass
TP-Link-RE200-v3,74da88,radio0-2g-1-1-sae,pass
TP-Link-RE200-v3,74da88,radio0-2g-1-1-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio0-2g-6-10-psk2,pass
TP-Link-RE200-v3,74da88,radio0-2g-6-10-sae,pass
TP-Link-RE200-v3,74da88,radio0-2g-6-10-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio0-2g-6-1-psk2,pass
TP-Link-RE200-v3,74da88,radio0-2g-6-1-sae,pass
TP-Link-RE200-v3,74da88,radio0-2g-6-1-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio0-2g-11-10-psk2,pass
TP-Link-RE200-v3,74da88,radio0-2g-11-10-sae,pass
TP-Link-RE200-v3,74da88,radio0-2g-11-10-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio0-2g-11-1-psk2,pass
TP-Link-RE200-v3,74da88,radio0-2g-11-1-sae,pass
TP-Link-RE200-v3,74da88,radio0-2g-11-1-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio1-5g-36-4-psk2,pass
TP-Link-RE200-v3,74da88,radio1-5g-36-4-sae,pass
TP-Link-RE200-v3,74da88,radio1-5g-36-4-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio1-5g-36-1-psk2,pass
TP-Link-RE200-v3,74da88,radio1-5g-36-1-sae,pass
TP-Link-RE200-v3,74da88,radio1-5g-36-1-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio1-5g-100-4-psk2,pass
TP-Link-RE200-v3,74da88,radio1-5g-100-4-sae,pass
TP-Link-RE200-v3,74da88,radio1-5g-100-4-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio1-5g-100-1-psk2,pass
TP-Link-RE200-v3,74da88,radio1-5g-100-1-sae,pass
TP-Link-RE200-v3,74da88,radio1-5g-100-1-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio1-5g-149-4-psk2,pass
TP-Link-RE200-v3,74da88,radio1-5g-149-4-sae,pass
TP-Link-RE200-v3,74da88,radio1-5g-149-4-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio1-5g-149-1-psk2,pass
TP-Link-RE200-v3,74da88,radio1-5g-149-1-sae,pass
TP-Link-RE200-v3,74da88,radio1-5g-149-1-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio1-5g-165-4-psk2,pass
TP-Link-RE200-v3,74da88,radio1-5g-165-4-sae,pass
TP-Link-RE200-v3,74da88,radio1-5g-165-4-sae-mixed,pass
TP-Link-RE200-v3,74da88,radio1-5g-165-1-psk2,pass
TP-Link-RE200-v3,74da88,radio1-5g-165-1-sae,pass
TP-Link-RE200-v3,74da88,radio1-5g-165-1-sae-mixed,pass
Buttons worked great.
Followed the button test web page. The reset button short press would reboot. The reset button 10s would do a factor reset. The WPS button generated a WPS event.
root@OpenWrt:/# find /sys/firmware/devicetree/base/keys -mindepth 1 -type d | wh
ile read -r f; do printf '%s: %s\n' $(basename $f) $(hexdump -s2 -e '2/1 "%02x""
\n"' $f/linux,code); done
wps: 0211
reset: 0198
0198 KEY_RESTART reset
0211 KEY_WPS_BUTTON wps
root@OpenWrt:/# opkg install kmod-button-hotplug
Installing kmod-button-hotplug (5.10.138-3) to root...
Downloading https://downloads.openwrt.org/releases/22.03.0/targets/ramips/mt76x8/packages/kmod-button-hotplug_5.10.138-3_mipsel_24kc.ipk
Installing kmod-input-core (5.10.138-1) to root...
Downloading https://downloads.openwrt.org/releases/22.03.0/targets/ramips/mt76x8/packages/kmod-input-core_5.10.138-1_mipsel_24kc.ipk
Configuring kmod-input-core.
Configuring kmod-button-hotplug.
[ 2200.060910] kmodloader: loading kernel modules from /etc/modules.d/*
[ 2200.091097] Button Hotplug driver version 0.4.1
[ 2200.112167] kmodloader: done loading kernel modules from /etc/modules.d/*
root@OpenWrt:/# mkidr -p /etc/hotplug.d/button
/bin/ash: mkidr: not found
root@OpenWrt:/# mkdir -p /etc/hotplug.d/button
root@OpenWrt:/# cat << "EOF" > /etc/hotplug.d/button/buttons
> logger "the button was ${BUTTON} and the action was ${ACTION}"
> EOF
root@OpenWrt:/# logread -f
Tue Sep 27 20:04:44 2022 user.notice root: the button was wps and the action was pressed
Tue Sep 27 20:04:45 2022 user.notice root: the button was wps and the action was released
Tue Sep 27 20:04:48 2022 user.notice root: the button was wps and the action was pressed
Tue Sep 27 20:04:50 2022 user.notice root: the button was wps and the action was released
Tue Sep 27 20:05:19 2022 user.notice root: the button was reset and the action was pressed
REBOOT
Tue Sep 27 20:05:19 2022 daemon.info procd: - shutdown -
Tue Sep 27 20:05:19 2022 user.notice root: the button was reset and the action was released
Wired interface on lan worked as expected.
Tested using radios. Used 5Ghz for uplink and 2.4Ghz for clients. Mostly worked ok. It would just repeatedly try to connect to 5Ghz three times and then fail. Eventually it would connect and stay connected. Performance was poor. Maybe an optimized config or environment would work better. Not seeing anything to indicate problem w/ running this image.
Will share anything else interesting.
Conclusion: The RE200v3 images works on the RE220v1 device. Support can be added for the RE220v1 by cloning the specifics of the RE200v3.