ramips: add support for TP-Link RE650 v1
TP-Link RE650 v1 is a dual-band AC2600 range extender,
based on MediaTek MT7621A and MT7615E. According to the
wikidevi entry for RE650 this device is identical with
TP-Link RE500 as hardware. This patch supports only RE650.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin
from the RE650 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com>
[re-added variables for kernel header]
Signed-off-by: David Bauer <mail@david-bauer.net>
2019-04-17 18:17:45 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
|
|
|
|
/dts-v1/;
|
|
|
|
|
|
|
|
#include "mt7621.dtsi"
|
|
|
|
|
|
|
|
#include <dt-bindings/gpio/gpio.h>
|
|
|
|
#include <dt-bindings/input/input.h>
|
|
|
|
|
|
|
|
/ {
|
|
|
|
compatible = "tplink,re650-v1", "mediatek,mt7621-soc";
|
|
|
|
model = "TP-Link RE650 v1";
|
|
|
|
|
|
|
|
aliases {
|
|
|
|
led-boot = &led_power;
|
|
|
|
led-failsafe = &led_power;
|
|
|
|
led-running = &led_power;
|
|
|
|
led-upgrade = &led_power;
|
ramips: provide label MAC address
This patch adds the label MAC address for several devices in
ramips.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- cudy,wr1000
- dlink,dir-615-d
- dlink,dir-615-h1
- dlink,dir-860l-b1
- glinet,gl-mt300a
- glinet,gl-mt300n
- glinet,gl-mt750
- vocore,vocore2
- vocore,vocore2-lite
- zbtlink,zbt-we1326
- zbtlink,zbt-wg3526
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- dlink,dir-510l
- dlink,dwr-116-a1
- dlink,dwr-118-a1
- dlink,dwr-118-a2
- dlink,dwr-921-c1
- dlink,dwr-922-e2
- all hiwifi devices
- lava,lr-25g001
- xiaomi,mir3p
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-06-24 15:57:15 +00:00
|
|
|
label-mac-device = ðernet;
|
ramips: add support for TP-Link RE650 v1
TP-Link RE650 v1 is a dual-band AC2600 range extender,
based on MediaTek MT7621A and MT7615E. According to the
wikidevi entry for RE650 this device is identical with
TP-Link RE500 as hardware. This patch supports only RE650.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin
from the RE650 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com>
[re-added variables for kernel header]
Signed-off-by: David Bauer <mail@david-bauer.net>
2019-04-17 18:17:45 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
chosen {
|
|
|
|
bootargs = "console=ttyS0,57600";
|
|
|
|
};
|
|
|
|
|
|
|
|
leds {
|
|
|
|
compatible = "gpio-leds";
|
|
|
|
|
|
|
|
led_power: power {
|
|
|
|
label = "re650-v1:blue:power";
|
|
|
|
gpios = <&gpio0 22 GPIO_ACTIVE_LOW>;
|
|
|
|
};
|
|
|
|
|
|
|
|
wifi2g {
|
|
|
|
label = "re650-v1:blue:wifi2G";
|
|
|
|
gpios = <&gpio0 23 GPIO_ACTIVE_LOW>;
|
|
|
|
};
|
|
|
|
|
|
|
|
wifi5g {
|
|
|
|
label = "re650-v1:blue:wifi5G";
|
|
|
|
gpios = <&gpio0 24 GPIO_ACTIVE_LOW>;
|
|
|
|
};
|
|
|
|
|
|
|
|
wps_red {
|
|
|
|
label = "re650-v1:red:wps";
|
|
|
|
gpios = <&gpio0 26 GPIO_ACTIVE_HIGH>;
|
|
|
|
};
|
|
|
|
|
|
|
|
wps_blue {
|
|
|
|
label = "re650-v1:blue:wps";
|
|
|
|
gpios = <&gpio0 27 GPIO_ACTIVE_HIGH>;
|
|
|
|
};
|
|
|
|
|
|
|
|
eth_act {
|
|
|
|
label = "re650-v1:green:eth_act";
|
|
|
|
gpios = <&gpio0 28 GPIO_ACTIVE_LOW>;
|
|
|
|
};
|
|
|
|
|
|
|
|
eth_link {
|
|
|
|
label = "re650-v1:green:eth_link";
|
|
|
|
gpios = <&gpio0 29 GPIO_ACTIVE_LOW>;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
keys {
|
|
|
|
compatible = "gpio-keys";
|
|
|
|
|
|
|
|
wps {
|
|
|
|
label = "wps";
|
|
|
|
gpios = <&gpio0 18 GPIO_ACTIVE_LOW>;
|
|
|
|
debounce-interval = <60>;
|
|
|
|
linux,code = <KEY_WPS_BUTTON>;
|
|
|
|
};
|
|
|
|
|
|
|
|
power {
|
|
|
|
label = "power";
|
|
|
|
gpios = <&gpio0 25 GPIO_ACTIVE_LOW>;
|
|
|
|
debounce-interval = <60>;
|
|
|
|
linux,code = <KEY_POWER>;
|
|
|
|
};
|
|
|
|
|
|
|
|
led {
|
|
|
|
label = "led";
|
|
|
|
gpios = <&gpio0 30 GPIO_ACTIVE_LOW>;
|
|
|
|
debounce-interval = <60>;
|
|
|
|
linux,code = <KEY_LIGHTS_TOGGLE>;
|
|
|
|
};
|
|
|
|
|
|
|
|
reset {
|
|
|
|
label = "reset";
|
|
|
|
gpios = <&gpio0 31 GPIO_ACTIVE_LOW>;
|
|
|
|
debounce-interval = <60>;
|
|
|
|
linux,code = <KEY_RESTART>;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
&spi0 {
|
|
|
|
status = "okay";
|
|
|
|
|
|
|
|
w25q64@0 {
|
|
|
|
compatible = "jedec,spi-nor";
|
|
|
|
reg = <0>;
|
|
|
|
spi-max-frequency = <40000000>;
|
|
|
|
|
|
|
|
partitions {
|
|
|
|
compatible = "fixed-partitions";
|
|
|
|
#address-cells = <1>;
|
|
|
|
#size-cells = <1>;
|
|
|
|
|
|
|
|
partition@0 {
|
|
|
|
label = "u-boot";
|
|
|
|
reg = <0x0 0x20000>;
|
|
|
|
read-only;
|
|
|
|
};
|
|
|
|
|
|
|
|
partition@20000 {
|
|
|
|
compatible = "tplink,firmware";
|
|
|
|
label = "firmware";
|
|
|
|
reg = <0x20000 0xde0000>;
|
|
|
|
};
|
|
|
|
|
|
|
|
config: partition@e00000 {
|
|
|
|
label = "config";
|
|
|
|
reg = <0xe00000 0x50000>;
|
|
|
|
read-only;
|
|
|
|
};
|
|
|
|
|
|
|
|
/* range 0xe50000 to 0xff0000 is empty in vendor
|
|
|
|
* firmware, so we do not use it either
|
|
|
|
*/
|
|
|
|
|
|
|
|
radio: partition@ff0000 {
|
|
|
|
label = "radio";
|
|
|
|
reg = <0xff0000 0x10000>;
|
|
|
|
read-only;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
&pcie {
|
|
|
|
status = "okay";
|
|
|
|
};
|
|
|
|
|
|
|
|
&pcie0 {
|
|
|
|
wifi@0,0 {
|
|
|
|
compatible = "mediatek,mt76";
|
|
|
|
reg = <0x0000 0 0 0 0>;
|
|
|
|
mediatek,mtd-eeprom = <&radio 0>;
|
|
|
|
mtd-mac-address = <&config 0x10008>;
|
|
|
|
mtd-mac-address-increment = <1>;
|
|
|
|
ieee80211-freq-limit = <2400000 2500000>;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
&pcie1 {
|
|
|
|
wifi@0,0 {
|
|
|
|
compatible = "mediatek,mt76";
|
|
|
|
reg = <0x0000 0 0 0 0>;
|
|
|
|
mediatek,mtd-eeprom = <&radio 0x8000>;
|
|
|
|
mtd-mac-address = <&config 0x10008>;
|
|
|
|
mtd-mac-address-increment = <2>;
|
|
|
|
ieee80211-freq-limit = <5000000 6000000>;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
ðernet {
|
|
|
|
mtd-mac-address = <&config 0x10008>;
|
|
|
|
};
|
|
|
|
|
|
|
|
&pinctrl {
|
|
|
|
state_default: pinctrl0 {
|
|
|
|
gpio {
|
|
|
|
ralink,group = "rgmii2", "wdt";
|
|
|
|
ralink,function = "gpio";
|
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|