|
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
|
|
. /lib/functions.sh
|
|
|
|
|
. /lib/functions/uci-defaults.sh
|
|
|
|
|
. /lib/functions/system.sh
|
|
|
|
|
|
|
|
|
|
ramips_setup_interfaces()
|
|
|
|
|
{
|
|
|
|
|
local board="$1"
|
|
|
|
|
|
|
|
|
|
case $board in
|
|
|
|
|
alfa-network,awusfree1|\
|
|
|
|
|
d-team,pbr-d1|\
|
|
|
|
|
mediatek,linkit-smart-7688|\
|
|
|
|
|
onion,omega2p|\
|
|
|
|
|
onion,omega2|\
|
|
|
|
|
tama,w06|\
|
|
|
|
|
tplink,re200-v2|\
|
|
|
|
|
tplink,re305-v1|\
|
|
|
|
|
tplink,tl-mr3020-v3|\
|
|
|
|
|
tplink,tl-wr802n-v4|\
|
|
|
|
|
tplink,tl-wa801nd-v5|\
|
|
|
|
|
widora,neo-16m|\
|
|
|
|
|
widora,neo-32m)
|
|
|
|
|
ucidef_add_switch "switch0"
|
|
|
|
|
ucidef_add_switch_attr "switch0" "enable" "false"
|
|
|
|
|
ucidef_set_interface_lan "eth0"
|
|
|
|
|
;;
|
|
|
|
|
asus,rt-n10p-v3|\
|
|
|
|
|
asus,rt-n11p-b1|\
|
|
|
|
|
asus,rt-n12-vp-b1|\
|
|
|
|
|
hiwifi,hc5661a|\
|
|
|
|
|
mediatek,mt7628an-eval-board|\
|
|
|
|
|
mercury,mac1200r-v2|\
|
|
|
|
|
totolink,lr1200|\
|
|
|
|
|
wavlink,wl-wn570ha1|\
|
|
|
|
|
wavlink,wl-wn575a3)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
buffalo,wcr-1166ds|\
|
|
|
|
|
wavlink,wl-wn577a2)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"3:lan" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
cudy,wr1000)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"2:lan:2" "3:lan:1" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
duzun,dm06)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
glinet,gl-mt300n-v2)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
glinet,microuter-n300|\
|
|
|
|
|
glinet,vixmini)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
hilink,hlk-7628n|\
|
|
|
|
|
hiwifi,hc5861b|\
|
|
|
|
|
skylab,skw92a|\
|
|
|
|
|
tplink,archer-c20-v4|\
|
ramips: add support for TP-Link Archer C20 v5
TP-Link Archer C20 v5 is a router with 5-port FE switch and
non-detachable antennas. It's based on MediaTek MT7628N+MT7610EN.
Specification:
- MediaTek MT7628N/N (580 Mhz)
- 64 MB of RAM
- 8 MB of FLASH
- 2T2R 2.4 GHz and 1T1R 5 GHz
- 5x 10/100 Mbps Ethernet
- 3x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- 7x LED (GPIO-controlled*), 2x button, power input switch
* WAN LED in this devices is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Create Factory image
--------------------
As all installation methods require a U-Boot to be integrated into the
Image (and we do not ship one with the image) we are not able to create
an image in the OpenWRT build-process.
Download a TP-Link image from their Website and a OpenWRT sysupgrade
image for the device and build yourself a factory image like following:
TP-Link image: tpl.bin
OpenWRT sysupgrade image: owrt.bin
> dd if=tpl.bin of=boot.bin bs=131584 count=1
> cat owrt.bin >> boot.bin
Installing via Web-UI
---------------------
Upload the boot.bin via TP-Links firmware upgrade tool in the
web-interface.
Installing via Recovery
-----------------------
Activate Web-Recovery by beginning the upgrade Process with a
Firmware-Image from TP-Link. After starting the Firmware Upgrade,
wait ~3 seconds (When update status is switching to 0%), then
disconnect the power supply from the device. Upgrade flag (which
activates Web-Recovery) is written before the OS-image is touched and
removed after write is succesfull, so this procedure should be safe.
Plug the power back in. It will come up in Recovery-Mode on 192.168.0.1.
When active, all LEDs but the WPS LED are off.
Remeber to assign yourself a static IP-address as DHCP is not active in
this mode.
The boot.bin can now be uploaded and flashed using the web-recovery.
Installing via TFTP
-------------------
Prepare an image like following (Filenames from factory image steps
apply here)
> dd if=/dev/zero of=tp_recovery.bin bs=196608 count=1
> dd if=tpl.bin of=tmp.bin bs=131584 count=1
> dd if=tmp.bin of=boot.bin bs=512 skip=1
> cat boot.bin >> tp_recovery.bin
> cat owrt.bin >> tp_recovery.bin
Place tp_recovery.bin in root directory of TFTP server and listen on
192.168.0.66/24.
Connect router LAN ports with your computer and power up the router
while pressing the reset button. The router will download the image via
tftp and after ~1 Minute reboot into OpenWRT.
U-Boot CLI
----------
U-Boot CLI can be activated by holding down '4' on bootup.
Dual U-Boot
-----------
This is TP-Link MediaTek device with a split-uboot feature design like
a TP-Link Archer C50 v4. The first (factory-uboot) provides recovery via
TFTP and HTTP, jumping straight into the second (firmware-uboot) if no
recovery needs to be performed. The firmware-uboot unpacks and executed
the kernel.
Web-Recovery
------------
TP-Link integrated a new Web-Recovery like the one on the Archer C7v4 /
TL-WR1043v5 / Archer C50v4. Stock-firmware sets a flag in the "romfile"
partition before beginning to write and removes it afterwards. If the
router boots with this flag set, bootloader will automatically start
Web-recovery and listens on 192.168.0.1. This way, the vendor-firmware
or an OpenWRT factory image can be written.
By doing the same while performing sysupgrade, we can take advantage of
the Web-recovery in OpenWRT.
It is important to note that Web-Recovery is only based on this flag. It
can't detect e.g. a crashing kernel or other means. Once activated it
won't boot the OS before a recovery action (either via TFTP or HTTP) is
performed. This recovery-mode is indicated by an illuminated WPS-LED on
boot.
Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com>
[adjust some node names for LEDs in DTS]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
4 years ago
|
|
|
tplink,archer-c20-v5|\
|
|
|
|
|
tplink,archer-c50-v3|\
|
|
|
|
|
tplink,archer-c50-v4|\
|
|
|
|
|
tplink,tl-mr3420-v5|\
|
|
|
|
|
tplink,tl-wr840n-v4|\
|
|
|
|
|
tplink,tl-wr840n-v5|\
|
|
|
|
|
tplink,tl-wr841n-v13|\
|
|
|
|
|
tplink,tl-wr841n-v14|\
|
|
|
|
|
tplink,tl-wr842n-v5|\
|
|
|
|
|
unielec,u7628-01-16m|\
|
|
|
|
|
wrtnode,wrtnode2p|\
|
|
|
|
|
wrtnode,wrtnode2r|\
|
|
|
|
|
zyxel,keenetic-extra-ii)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
hiwifi,hc5761a)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "1:lan" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
iptime,a3|\
|
|
|
|
|
totolink,a3)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"2:lan:2" "3:lan:1" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
iptime,a604m)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
ramips: add support for Netgear R6080
This adds support for the Netgear R6080, aka Netgear AC1000.
The R6080 has almost the same hardware as the Netgear R6120,
aka Netgear AC1200, but it lacks the USB port, has only 8 MiB flash and
uses a different SERCOMM_HWID.
Specification:
SoC: MediaTek MT7628 (580 MHz)
Flash: 8 MiB
RAM: 64 MiB
Wireless: 2.4Ghz (builtin) and 5Ghz (MT7612E)
LAN speed: 10/100
LAN ports: 4
WAN speed: 10/100
WAN ports: 1
UART (57600 8N1) on PCB
Installation:
Flashing OpenWRT from stock firmware requires nmrpflash. Use an ethernet
cable to connect to LAN port 1 of the R6080, and power the R6080 off.
From the connected workstation, run
`nmrpflash -i eth0 -f openwrt-ramips-mt76x8-netgear_r6080-squashfs-factory.img`,
replacing eth0 with the appropriate interface (can be identified by
running `nmrpflash -L`). Then power on the R6080. After flashing has finished,
power cycle the R6080, and it will boot into OpenWRT. Once OpenWRT has been
installed, subsequent flashes can use the web interface and sysupgrade files.
Signed-off-by: Alex Lewontin <alex.c.lewontin@gmail.com>
[rebase and adjust for 5.4]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
4 years ago
|
|
|
netgear,r6080|\
|
|
|
|
|
netgear,r6120)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
rakwireless,rak633)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:wan" "1:lan" "2:lan" "3:lan" "4:lan" "6t@eth0"
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-wr902ac-v3)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"4:lan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
vocore,vocore2|\
|
|
|
|
|
vocore,vocore2-lite)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "2:lan" "6t@eth0"
|
|
|
|
|
;;
|
|
|
|
|
wiznet,wizfi630s)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:wan" "3:lan" "4:lan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
xiaomi,mir4a-100m)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"4:lan:1" "2:lan:2" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
xiaomi,miwifi-nano)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:2" "2:lan:1" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
zbtlink,zbt-we1226)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:2" "1:lan:1" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
ramips_setup_macs()
|
|
|
|
|
{
|
|
|
|
|
local board="$1"
|
|
|
|
|
local lan_mac=""
|
|
|
|
|
local wan_mac=""
|
|
|
|
|
local label_mac=""
|
|
|
|
|
|
|
|
|
|
case $board in
|
|
|
|
|
buffalo,wcr-1166ds)
|
|
|
|
|
local index="$(find_mtd_index "board_data")"
|
|
|
|
|
wan_mac="$(grep -m1 mac= "/dev/mtd${index}" | cut -d= -f2)"
|
|
|
|
|
lan_mac=$wan_mac
|
|
|
|
|
;;
|
|
|
|
|
cudy,wr1000)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x2e)
|
ramips: remove bogus ralink,mtd-eeprom with offset 0x4
Several devices in mt76x8 subtarget use the following line to set
up wmac in their DTS(I) files:
ralink,mtd-eeprom = <&factory 0x4>
This is strange for several reasons:
- They should use mediatek,mtd-eeprom on this SOC
- The caldata is supposed to start at 0x0
- The parent DTSI mt7628an.dtsi specifies mediatek,mtd-eeprom anyway,
starting from 0x0
- The offset coincides with the default location of the MAC address
in caldata
Based on the comment in b28e94d4bfa1 ("ramips: MiWiFi Nano fixes"),
it looks like the author for this device wanted to actually use
mtd-mac-address instead of ralink,mtd-eeprom. A check on the same
device revealed that actually the MAC address start at offset 4 there,
so the correct caldata offset is 0x0.
Based on these findings, and the fact that the expected location on
this SOC is 0x0, we remove the "ralink,mtd-eeprom = <&factory 0x4>"
statement from all devices in ramips (being only mt7628an anyway).
Thanks to Sungbo Eo for finding and researching this.
Reported-by: Sungbo Eo <mans0n@gorani.run>
Fixes: b28e94d4bfa1 ("ramips: MiWiFi Nano fixes")
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
4 years ago
|
|
|
label_mac=$(mtd_get_mac_binary factory 0x4)
|
|
|
|
|
;;
|
ramips: remove default case for MAC address assignment
So far, MAC address assignment in ramips has contained a default
case, which defined wan_mac = eth0 + 1 for _every_ device not
having an explicit case there.
This is not desirable, as many device supporters will just not
care or know about this definition, so another MAC address will be
introduced by accident. In some cases the wan_mac is assigned
although it is not needed, in other cases even addresses not
dedicated to the device will be used (e.g. wan_mac actually is
eth0 - 1, but during support nobody cared, so eth0 + 1 is used now,
which might actually belong to another device ...).
Thus, in this PR the former default case is converted to an
explicit case. This one comprises all devices not being accounted
for by other cases, reduced by those not having wan at all.
The big number of entries for this node might be another indication
that many of them wouldn't actually be there if there hadn't been
default wan_mac setup.
In exchange, the current "do nothing" case can be removed, as it
will be the new default case.
The devices being put in the newly created explicit case were
determined as follows:
1. Create a list of all devices based on the DTS files.
2. Remove all devices already having an explicit entry setting
their address.
3. Remove all devices that only have lan set up in the first part
of 02_network:
mt7620:
- alfa-network,tube-e4g
- asus,rp-n53
- buffalo,wmr-300
- comfast,cf-wr800n
- edimax,ew-7476rpc
- edimax,ew-7478ac
- elecom,wrh-300cr
- hnet,c108
- kimax,u25awf-h1
- kimax,u35wf
- kingston,mlw221
- kingston,mlwg2
- microduino,microwrt
- netgear,ex2700
- netgear,ex3700
- netgear,wn3000rp-v3
- planex,cs-qr10
- planex,mzk-ex300np
- planex,mzk-ex750np
- ravpower,wd03
- sercomm,na930
- yukai,bocco
- zbtlink,zbt-cpe102
- zte,q7
mt7621:
- gnubee,gb-pc1
- gnubee,gb-pc2
- linksys,re6500
- mikrotik,rbm11g
- netgear,ex6150
- thunder,timecloud
- tplink,re350-v1
- tplink,re650-v1
mt76x8:
- alfa-network,awusfree1
- d-team,pbr-d1
- glinet,vixmini
- vocore,vocore2-lite
- tama,w06
- tplink,tl-mr3020-v3
- tplink,tl-wa801nd-v5
- tplink,tl-wr802n-v4
- tplink,tl-wr902ac-v3
- vocore,vocore2
- widora,neo-16m
- widora,neo-32m
rt288x:
- buffalo,wli-tx4-ag300n
- dlink,dap-1522-a1
rt305x:
- allnet,all0256n-4m
- allnet,all0256n-8m
- allnet,all5002
- allnet,all5003
- alphanetworks,asl26555-16m
- alphanetworks,asl26555-8m
- asus,wl-330n
- aximcom,mr-102n
- dlink,dcs-930
- easyacc,wizard-8800
- hame,mpr-a2
- hootoo,ht-tm02
- huawei,d105
- intenso,memory2move
- planex,mzk-dp150n
- rt305x dlink,dcs-930l-b1
- sparklan,wcr-150gn
- tenda,3g150b
- tenda,3g300m
- tenda,w150m
- trendnet,tew-638apb-v2
- unbranded,a5-v11
- vocore,vocore-16m
- vocore,vocore-8m
- wansview,ncs601w
- zorlik,zl5900v2
rt3883:
- loewe,wmdr-143n
- omnima,hpm
4. Put the remaining devices in the new case.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
duzun,dm06|\
|
ramips: add support for Netgear R6080
This adds support for the Netgear R6080, aka Netgear AC1000.
The R6080 has almost the same hardware as the Netgear R6120,
aka Netgear AC1200, but it lacks the USB port, has only 8 MiB flash and
uses a different SERCOMM_HWID.
Specification:
SoC: MediaTek MT7628 (580 MHz)
Flash: 8 MiB
RAM: 64 MiB
Wireless: 2.4Ghz (builtin) and 5Ghz (MT7612E)
LAN speed: 10/100
LAN ports: 4
WAN speed: 10/100
WAN ports: 1
UART (57600 8N1) on PCB
Installation:
Flashing OpenWRT from stock firmware requires nmrpflash. Use an ethernet
cable to connect to LAN port 1 of the R6080, and power the R6080 off.
From the connected workstation, run
`nmrpflash -i eth0 -f openwrt-ramips-mt76x8-netgear_r6080-squashfs-factory.img`,
replacing eth0 with the appropriate interface (can be identified by
running `nmrpflash -L`). Then power on the R6080. After flashing has finished,
power cycle the R6080, and it will boot into OpenWRT. Once OpenWRT has been
installed, subsequent flashes can use the web interface and sysupgrade files.
Signed-off-by: Alex Lewontin <alex.c.lewontin@gmail.com>
[rebase and adjust for 5.4]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
4 years ago
|
|
|
netgear,r6080|\
|
ramips: remove default case for MAC address assignment
So far, MAC address assignment in ramips has contained a default
case, which defined wan_mac = eth0 + 1 for _every_ device not
having an explicit case there.
This is not desirable, as many device supporters will just not
care or know about this definition, so another MAC address will be
introduced by accident. In some cases the wan_mac is assigned
although it is not needed, in other cases even addresses not
dedicated to the device will be used (e.g. wan_mac actually is
eth0 - 1, but during support nobody cared, so eth0 + 1 is used now,
which might actually belong to another device ...).
Thus, in this PR the former default case is converted to an
explicit case. This one comprises all devices not being accounted
for by other cases, reduced by those not having wan at all.
The big number of entries for this node might be another indication
that many of them wouldn't actually be there if there hadn't been
default wan_mac setup.
In exchange, the current "do nothing" case can be removed, as it
will be the new default case.
The devices being put in the newly created explicit case were
determined as follows:
1. Create a list of all devices based on the DTS files.
2. Remove all devices already having an explicit entry setting
their address.
3. Remove all devices that only have lan set up in the first part
of 02_network:
mt7620:
- alfa-network,tube-e4g
- asus,rp-n53
- buffalo,wmr-300
- comfast,cf-wr800n
- edimax,ew-7476rpc
- edimax,ew-7478ac
- elecom,wrh-300cr
- hnet,c108
- kimax,u25awf-h1
- kimax,u35wf
- kingston,mlw221
- kingston,mlwg2
- microduino,microwrt
- netgear,ex2700
- netgear,ex3700
- netgear,wn3000rp-v3
- planex,cs-qr10
- planex,mzk-ex300np
- planex,mzk-ex750np
- ravpower,wd03
- sercomm,na930
- yukai,bocco
- zbtlink,zbt-cpe102
- zte,q7
mt7621:
- gnubee,gb-pc1
- gnubee,gb-pc2
- linksys,re6500
- mikrotik,rbm11g
- netgear,ex6150
- thunder,timecloud
- tplink,re350-v1
- tplink,re650-v1
mt76x8:
- alfa-network,awusfree1
- d-team,pbr-d1
- glinet,vixmini
- vocore,vocore2-lite
- tama,w06
- tplink,tl-mr3020-v3
- tplink,tl-wa801nd-v5
- tplink,tl-wr802n-v4
- tplink,tl-wr902ac-v3
- vocore,vocore2
- widora,neo-16m
- widora,neo-32m
rt288x:
- buffalo,wli-tx4-ag300n
- dlink,dap-1522-a1
rt305x:
- allnet,all0256n-4m
- allnet,all0256n-8m
- allnet,all5002
- allnet,all5003
- alphanetworks,asl26555-16m
- alphanetworks,asl26555-8m
- asus,wl-330n
- aximcom,mr-102n
- dlink,dcs-930
- easyacc,wizard-8800
- hame,mpr-a2
- hootoo,ht-tm02
- huawei,d105
- intenso,memory2move
- planex,mzk-dp150n
- rt305x dlink,dcs-930l-b1
- sparklan,wcr-150gn
- tenda,3g150b
- tenda,3g300m
- tenda,w150m
- trendnet,tew-638apb-v2
- unbranded,a5-v11
- vocore,vocore-16m
- vocore,vocore-8m
- wansview,ncs601w
- zorlik,zl5900v2
rt3883:
- loewe,wmdr-143n
- omnima,hpm
4. Put the remaining devices in the new case.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
netgear,r6120|\
|
|
|
|
|
wrtnode,wrtnode2p|\
|
|
|
|
|
wrtnode,wrtnode2r|\
|
|
|
|
|
zyxel,keenetic-extra-ii)
|
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 0x4)" 1)
|
|
|
|
|
;;
|
|
|
|
|
hilink,hlk-7628n)
|
|
|
|
|
lan_mac=$(macaddr_setbit_la "$(cat /sys/class/net/eth0/address)")
|
|
|
|
|
wan_mac=$(macaddr_add "$lan_mac" 1)
|
|
|
|
|
;;
|
|
|
|
|
hiwifi,hc5661a|\
|
|
|
|
|
hiwifi,hc5761a|\
|
|
|
|
|
hiwifi,hc5861b)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii bdinfo "Vfac_mac ")
|
|
|
|
|
label_mac=$lan_mac
|
|
|
|
|
[ -n "$lan_mac" ] || lan_mac=$(cat /sys/class/net/eth0/address)
|
|
|
|
|
wan_mac=$(macaddr_add "$lan_mac" 1)
|
|
|
|
|
;;
|
|
|
|
|
iptime,a3|\
|
|
|
|
|
iptime,a604m|\
|
|
|
|
|
totolink,a3)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary u-boot 0x1fc40)
|
|
|
|
|
;;
|
|
|
|
|
mediatek,linkit-smart-7688|\
|
|
|
|
|
onion,omega2|\
|
|
|
|
|
onion,omega2p)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x4)
|
|
|
|
|
lan_mac=$(mtd_get_mac_binary factory 0x2e)
|
|
|
|
|
;;
|
|
|
|
|
mercury,mac1200r-v2)
|
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory_info 0xd)" 1)
|
|
|
|
|
;;
|
|
|
|
|
rakwireless,rak633|\
|
|
|
|
|
unielec,u7628-01-16m|\
|
|
|
|
|
wavlink,wl-wn575a3|\
|
|
|
|
|
wiznet,wizfi630s)
|
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 0x28)" 1)
|
|
|
|
|
;;
|
|
|
|
|
wavlink,wl-wn577a2)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x2e)
|
|
|
|
|
label_mac=$(mtd_get_mac_binary factory 0x4)
|
|
|
|
|
;;
|
|
|
|
|
skylab,skw92a|\
|
|
|
|
|
totolink,lr1200)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x2e)
|
|
|
|
|
;;
|
|
|
|
|
tplink,archer-c20-v4|\
|
|
|
|
|
tplink,archer-c50-v3|\
|
|
|
|
|
tplink,tl-mr3420-v5|\
|
|
|
|
|
tplink,tl-wr840n-v4|\
|
|
|
|
|
tplink,tl-wr840n-v5|\
|
|
|
|
|
tplink,tl-wr841n-v13|\
|
|
|
|
|
tplink,tl-wr841n-v14|\
|
|
|
|
|
tplink,tl-wr842n-v5)
|
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 0xf100)" 1)
|
|
|
|
|
;;
|
ramips: add support for TP-Link Archer C20 v5
TP-Link Archer C20 v5 is a router with 5-port FE switch and
non-detachable antennas. It's based on MediaTek MT7628N+MT7610EN.
Specification:
- MediaTek MT7628N/N (580 Mhz)
- 64 MB of RAM
- 8 MB of FLASH
- 2T2R 2.4 GHz and 1T1R 5 GHz
- 5x 10/100 Mbps Ethernet
- 3x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- 7x LED (GPIO-controlled*), 2x button, power input switch
* WAN LED in this devices is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Create Factory image
--------------------
As all installation methods require a U-Boot to be integrated into the
Image (and we do not ship one with the image) we are not able to create
an image in the OpenWRT build-process.
Download a TP-Link image from their Website and a OpenWRT sysupgrade
image for the device and build yourself a factory image like following:
TP-Link image: tpl.bin
OpenWRT sysupgrade image: owrt.bin
> dd if=tpl.bin of=boot.bin bs=131584 count=1
> cat owrt.bin >> boot.bin
Installing via Web-UI
---------------------
Upload the boot.bin via TP-Links firmware upgrade tool in the
web-interface.
Installing via Recovery
-----------------------
Activate Web-Recovery by beginning the upgrade Process with a
Firmware-Image from TP-Link. After starting the Firmware Upgrade,
wait ~3 seconds (When update status is switching to 0%), then
disconnect the power supply from the device. Upgrade flag (which
activates Web-Recovery) is written before the OS-image is touched and
removed after write is succesfull, so this procedure should be safe.
Plug the power back in. It will come up in Recovery-Mode on 192.168.0.1.
When active, all LEDs but the WPS LED are off.
Remeber to assign yourself a static IP-address as DHCP is not active in
this mode.
The boot.bin can now be uploaded and flashed using the web-recovery.
Installing via TFTP
-------------------
Prepare an image like following (Filenames from factory image steps
apply here)
> dd if=/dev/zero of=tp_recovery.bin bs=196608 count=1
> dd if=tpl.bin of=tmp.bin bs=131584 count=1
> dd if=tmp.bin of=boot.bin bs=512 skip=1
> cat boot.bin >> tp_recovery.bin
> cat owrt.bin >> tp_recovery.bin
Place tp_recovery.bin in root directory of TFTP server and listen on
192.168.0.66/24.
Connect router LAN ports with your computer and power up the router
while pressing the reset button. The router will download the image via
tftp and after ~1 Minute reboot into OpenWRT.
U-Boot CLI
----------
U-Boot CLI can be activated by holding down '4' on bootup.
Dual U-Boot
-----------
This is TP-Link MediaTek device with a split-uboot feature design like
a TP-Link Archer C50 v4. The first (factory-uboot) provides recovery via
TFTP and HTTP, jumping straight into the second (firmware-uboot) if no
recovery needs to be performed. The firmware-uboot unpacks and executed
the kernel.
Web-Recovery
------------
TP-Link integrated a new Web-Recovery like the one on the Archer C7v4 /
TL-WR1043v5 / Archer C50v4. Stock-firmware sets a flag in the "romfile"
partition before beginning to write and removes it afterwards. If the
router boots with this flag set, bootloader will automatically start
Web-recovery and listens on 192.168.0.1. This way, the vendor-firmware
or an OpenWRT factory image can be written.
By doing the same while performing sysupgrade, we can take advantage of
the Web-recovery in OpenWRT.
It is important to note that Web-Recovery is only based on this flag. It
can't detect e.g. a crashing kernel or other means. Once activated it
won't boot the OS before a recovery action (either via TFTP or HTTP) is
performed. This recovery-mode is indicated by an illuminated WPS-LED on
boot.
Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com>
[adjust some node names for LEDs in DTS]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
4 years ago
|
|
|
tplink,archer-c20-v5|\
|
|
|
|
|
tplink,archer-c50-v4)
|
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary rom 0xf100)" 1)
|
|
|
|
|
;;
|
|
|
|
|
vocore,vocore2|\
|
|
|
|
|
vocore,vocore2-lite)
|
ramips: remove bogus ralink,mtd-eeprom with offset 0x4
Several devices in mt76x8 subtarget use the following line to set
up wmac in their DTS(I) files:
ralink,mtd-eeprom = <&factory 0x4>
This is strange for several reasons:
- They should use mediatek,mtd-eeprom on this SOC
- The caldata is supposed to start at 0x0
- The parent DTSI mt7628an.dtsi specifies mediatek,mtd-eeprom anyway,
starting from 0x0
- The offset coincides with the default location of the MAC address
in caldata
Based on the comment in b28e94d4bfa1 ("ramips: MiWiFi Nano fixes"),
it looks like the author for this device wanted to actually use
mtd-mac-address instead of ralink,mtd-eeprom. A check on the same
device revealed that actually the MAC address start at offset 4 there,
so the correct caldata offset is 0x0.
Based on these findings, and the fact that the expected location on
this SOC is 0x0, we remove the "ralink,mtd-eeprom = <&factory 0x4>"
statement from all devices in ramips (being only mt7628an anyway).
Thanks to Sungbo Eo for finding and researching this.
Reported-by: Sungbo Eo <mans0n@gorani.run>
Fixes: b28e94d4bfa1 ("ramips: MiWiFi Nano fixes")
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
4 years ago
|
|
|
label_mac=$(mtd_get_mac_binary factory 0x4)
|
|
|
|
|
;;
|
|
|
|
|
wavlink,wl-wn570ha1|\
|
|
|
|
|
zbtlink,zbt-we1226)
|
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 0x2e)" 1)
|
|
|
|
|
;;
|
|
|
|
|
xiaomi,mir4a-100m)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x4)
|
|
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
|
|
|
|
|
[ -n "$lan_mac" ] && ucidef_set_interface_macaddr "lan" $lan_mac
|
|
|
|
|
[ -n "$wan_mac" ] && ucidef_set_interface_macaddr "wan" $wan_mac
|
|
|
|
|
[ -n "$label_mac" ] && ucidef_set_label_macaddr $label_mac
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
board_config_update
|
|
|
|
|
board=$(board_name)
|
|
|
|
|
ramips_setup_interfaces $board
|
|
|
|
|
ramips_setup_macs $board
|
|
|
|
|
board_config_flush
|
|
|
|
|
|
|
|
|
|
exit 0
|
