2010-04-11 17:47:23 +00:00
|
|
|
#!/bin/sh
|
2013-02-18 09:56:29 +00:00
|
|
|
# Copyright (C) 2010-2013 OpenWrt.org
|
2010-04-11 17:47:23 +00:00
|
|
|
|
2017-05-12 20:36:07 +00:00
|
|
|
. /lib/functions.sh
|
2013-02-18 09:56:29 +00:00
|
|
|
. /lib/functions/leds.sh
|
2010-04-11 17:47:23 +00:00
|
|
|
|
|
|
|
|
get_status_led() {
|
2017-05-12 20:36:07 +00:00
|
|
|
board=$(board_name)
|
2017-11-16 21:17:42 +00:00
|
|
|
boardname="${board##*,}"
|
2015-08-17 06:24:47 +00:00
|
|
|
|
|
|
|
|
case $board in
|
|
|
|
|
3g150b|\
|
|
|
|
|
3g300m|\
|
|
|
|
|
w150m)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:ap"
|
2015-08-17 06:24:47 +00:00
|
|
|
;;
|
|
|
|
|
3g-6200n|\
|
|
|
|
|
ar670w|\
|
|
|
|
|
ar725w|\
|
|
|
|
|
br-6475nd|\
|
2016-10-13 19:00:06 +00:00
|
|
|
c50|\
|
2016-05-02 03:57:40 +00:00
|
|
|
dch-m225|\
|
2016-06-30 13:18:03 +00:00
|
|
|
dir-860l-b1|\
|
2015-08-17 06:24:47 +00:00
|
|
|
e1700|\
|
2017-07-30 13:42:38 +00:00
|
|
|
ex2700|\
|
2017-03-03 14:36:51 +00:00
|
|
|
ex3700|\
|
2015-08-17 06:24:47 +00:00
|
|
|
fonera20n|\
|
2017-09-09 13:16:11 +00:00
|
|
|
hg255d|\
|
2017-04-27 18:02:05 +00:00
|
|
|
kn|\
|
2016-11-28 18:41:51 +00:00
|
|
|
kn_rc|\
|
|
|
|
|
kn_rf|\
|
2016-10-29 12:26:58 +00:00
|
|
|
kng_rc|\
|
2016-04-20 17:19:05 +00:00
|
|
|
mzk-750dhp|\
|
2015-08-17 06:24:47 +00:00
|
|
|
mzk-dp150n|\
|
|
|
|
|
mzk-w300nh2|\
|
|
|
|
|
nbg-419n|\
|
2016-07-24 15:37:52 +00:00
|
|
|
nbg-419n2|\
|
2015-08-17 06:24:47 +00:00
|
|
|
pwh2004|\
|
2017-03-11 07:44:33 +00:00
|
|
|
r6220|\
|
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13
TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with
5-port FE switch and non-detachable antennas. Both are very similar
and are based on MediaTek MT7628NN (aka MT7628N) WiSoC.
The difference between these two models is in number of available
LEDs, buttons and power input switch.
This work is partially based on GitHub PR#974.
Specification:
- MT7628N/N (580 MHz)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- TL-WR840N v4: 5x LED (GPIO-controlled), 1x button
- TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input
switch
* WAN LED in TL-WR841N v13 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.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device ("0x4"/"0x13" for these devices) but it seems
that anything other than "0" is correct.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash.
Tests showed that the GUI upgrade routine copies value of "Additional
Hardware Version" from existing firmware into offset "0x2023c" in
provided file, _before_ storing it in flash. In case of vendor firmware
upgrade files (which all include U-Boot image and two headers), this
offset points to the matching field in kernel+rootfs firmware part
header. Unfortunately, in case of LEDE factory image file which contains
only one header, it points to the offset "0x2023c" in kernel image. This
leads to a corrupted kernel and ends up with a "soft-bricked" device.
The good news is that U-Boot in these devices contains well known tftp
recovery mode, which can be triggered with "reset" button. What's more,
in comparison to some of older MediaTek based TP-Link devices, this
recovery mode doesn't write whole file at offset "0x0" in flash, without
verifying provided file in advance. In case of recovery mode in these
devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes
from rest of the file are stored in flash at offset "0x20000".
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot:
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin"
to "tp_recovery.bin" and place it in tftp server directory.
3. Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
4. Router will download file from server, write it to flash and reboot.
To access U-Boot CLI, keep pressed "4" key during boot.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-06-21 12:16:15 +00:00
|
|
|
tl-wr840n-v4|\
|
2017-11-08 13:00:06 +00:00
|
|
|
tl-wr840n-v5|\
|
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13
TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with
5-port FE switch and non-detachable antennas. Both are very similar
and are based on MediaTek MT7628NN (aka MT7628N) WiSoC.
The difference between these two models is in number of available
LEDs, buttons and power input switch.
This work is partially based on GitHub PR#974.
Specification:
- MT7628N/N (580 MHz)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- TL-WR840N v4: 5x LED (GPIO-controlled), 1x button
- TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input
switch
* WAN LED in TL-WR841N v13 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.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device ("0x4"/"0x13" for these devices) but it seems
that anything other than "0" is correct.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash.
Tests showed that the GUI upgrade routine copies value of "Additional
Hardware Version" from existing firmware into offset "0x2023c" in
provided file, _before_ storing it in flash. In case of vendor firmware
upgrade files (which all include U-Boot image and two headers), this
offset points to the matching field in kernel+rootfs firmware part
header. Unfortunately, in case of LEDE factory image file which contains
only one header, it points to the offset "0x2023c" in kernel image. This
leads to a corrupted kernel and ends up with a "soft-bricked" device.
The good news is that U-Boot in these devices contains well known tftp
recovery mode, which can be triggered with "reset" button. What's more,
in comparison to some of older MediaTek based TP-Link devices, this
recovery mode doesn't write whole file at offset "0x0" in flash, without
verifying provided file in advance. In case of recovery mode in these
devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes
from rest of the file are stored in flash at offset "0x20000".
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot:
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin"
to "tp_recovery.bin" and place it in tftp server directory.
3. Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
4. Router will download file from server, write it to flash and reboot.
To access U-Boot CLI, keep pressed "4" key during boot.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-06-21 12:16:15 +00:00
|
|
|
tl-wr841n-v13|\
|
2016-10-10 01:24:42 +00:00
|
|
|
vr500|\
|
2015-08-17 06:24:47 +00:00
|
|
|
wnce2001|\
|
2016-04-26 11:43:53 +00:00
|
|
|
wndr3700v5|\
|
2015-08-17 06:24:47 +00:00
|
|
|
x5|\
|
|
|
|
|
x8|\
|
2017-07-30 13:42:38 +00:00
|
|
|
xdxrn502j|\
|
|
|
|
|
wn3000rpv3)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:power"
|
2014-06-13 09:16:15 +00:00
|
|
|
;;
|
2016-09-27 05:16:16 +00:00
|
|
|
3g-6200nl)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:internet"
|
2016-09-27 05:16:16 +00:00
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
a5-v11|\
|
2016-04-26 11:43:01 +00:00
|
|
|
cs-qr10|\
|
2015-08-17 06:24:47 +00:00
|
|
|
d105|\
|
|
|
|
|
dcs-930l-b1|\
|
|
|
|
|
hlk-rm04|\
|
2016-03-04 08:33:09 +00:00
|
|
|
jhr-n825r|\
|
2015-08-17 06:24:47 +00:00
|
|
|
mpr-a1|\
|
2016-04-29 11:34:56 +00:00
|
|
|
mpr-a2|\
|
2017-07-30 13:42:38 +00:00
|
|
|
mzk-ex750np)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:red:power"
|
2012-01-23 10:23:32 +00:00
|
|
|
;;
|
2017-04-01 08:46:44 +00:00
|
|
|
ai-br100|\
|
|
|
|
|
ht-tm02)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:wlan"
|
2017-04-01 08:46:44 +00:00
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
all0239-3g|\
|
|
|
|
|
dcs-930|\
|
|
|
|
|
dir-300-b1|\
|
|
|
|
|
dir-300-b7|\
|
|
|
|
|
dir-320-b1|\
|
|
|
|
|
dir-600-b1|\
|
|
|
|
|
dir-610-a1|\
|
|
|
|
|
dir-615-d|\
|
|
|
|
|
dir-615-h1|\
|
|
|
|
|
dir-620-a1|\
|
|
|
|
|
dir-620-d1|\
|
2016-11-13 22:36:00 +00:00
|
|
|
dwr-512-b|\
|
2017-07-22 01:15:56 +00:00
|
|
|
gb-pc1|\
|
2015-08-17 06:24:47 +00:00
|
|
|
hpm|\
|
|
|
|
|
hw550-3g|\
|
2016-09-08 22:57:31 +00:00
|
|
|
mac1200rv2|\
|
2015-08-17 06:24:47 +00:00
|
|
|
miniembwifi|\
|
|
|
|
|
mofi3500-3gn|\
|
|
|
|
|
rut5xx|\
|
|
|
|
|
v11st-fe|\
|
2015-11-02 10:18:19 +00:00
|
|
|
wmr-300|\
|
2017-04-07 21:52:27 +00:00
|
|
|
zbt-wg2626)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:status"
|
2015-08-17 06:24:34 +00:00
|
|
|
;;
|
2017-04-07 22:34:48 +00:00
|
|
|
asl26555-8M|\
|
|
|
|
|
asl26555-16M)
|
|
|
|
|
status_led="asl26555:green:power"
|
|
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
atp-52b|\
|
2017-02-27 20:59:50 +00:00
|
|
|
ew1200|\
|
2015-08-17 06:24:47 +00:00
|
|
|
ip2202)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:run"
|
2013-04-25 19:02:53 +00:00
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
awapn2403|\
|
2016-04-21 19:46:59 +00:00
|
|
|
dir-645|\
|
2016-05-10 16:17:54 +00:00
|
|
|
sk-wb8|\
|
2016-04-21 19:46:59 +00:00
|
|
|
wrh-300cr)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:wps"
|
2013-02-02 17:01:50 +00:00
|
|
|
;;
|
2017-09-06 09:14:16 +00:00
|
|
|
c108)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:lan"
|
2017-09-06 09:14:16 +00:00
|
|
|
;;
|
2016-02-15 18:45:22 +00:00
|
|
|
cf-wr800n|\
|
|
|
|
|
psg1208)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:white:wps"
|
2015-08-17 06:24:34 +00:00
|
|
|
;;
|
2017-04-21 00:47:44 +00:00
|
|
|
psg1218a|\
|
|
|
|
|
psg1218b)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:yellow:status"
|
2016-09-30 11:41:12 +00:00
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
cy-swr1100|\
|
|
|
|
|
w502u)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:wps"
|
2015-08-17 06:24:47 +00:00
|
|
|
;;
|
ramips: add support for TP-Link Archer C20 v1
TP-Link Archer C20 v1 is a router with 5-port FE switch and
non-detachable antennas. It's very similiar to TP-Link Archer C50.
Also it's based on MediaTek MT7620A+MT7610EN.
Specification:
- MediaTek MT7620A (580 Mhz)
- 64 MB of RAM
- 8 MB of FLASH
- 2T2R 2.4 GHz and 1T1R 5 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- 8x LED (GPIO-controlled*), 2x button, power input switch
- 1 x USB 2.0 port
* 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 blue part of the LED.
* MT7610EN ac chip isn't not supported by LEDE. Therefore 5Ghz won't
work.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash. So, to flash this device we must
to prepare image using original firmware from tp-link site with uboot.
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot.
There are two ways to flash the device to LEDE:
1) Using tftp mode with UART connection and original LEDE image
- Place lede-ramips-mt7620-ArcherC20-squashfs-factory.bin in tftp
server directory
- Configure PC with static IP 192.168.0.66/24 and tftp server.
- Connect PC with one of LAN ports, power up the router and press
key "4" to access U-Boot CLI.
- Use the following commands to update the device to LEDE:
setenv serverip 192.168.0.66
tftp 0x80060000 lede-ramips-mt7620-ArcherC20-squashfs-factory.bin
erase tplink 0x20000 0x7a0000
cp.b 0x80060000 0x20000 0x7a0000
reset
- After that the device will reboot and boot to LEDE
2) Using tftp mode without UART connection but require some
manipulations with target image
- Download and unpack TP-Link Archer C20 v1 firmware from original web
site
- Split uboot.bin from original firmware by this command (example):
dd if=Archer_C20v1_0.9.1_4.0_up_boot(160427)_2016-04-27_13.53.59.bin of=uboot.bin bs=512 count=256 skip=1
- Create ArcherC20V1_tp_recovery.bin using this command:
cat uboot.bin lede-ramips-mt7620-ArcherC20-squashfs-factory.bin > ArcherC20V1_tp_recovery.bin
- Place ArcherC20V1_tp_recovery.bin in tftp server directory.
- Configure PC with static IP 192.168.0.66/24 and tftp server.
- Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
- Router will download file from server, write it to flash and reboot.
Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com>
2017-09-08 09:39:17 +00:00
|
|
|
c20|\
|
2017-02-04 20:28:52 +00:00
|
|
|
d240|\
|
2015-08-17 06:24:47 +00:00
|
|
|
dap-1350|\
|
|
|
|
|
na930|\
|
2015-12-11 15:03:50 +00:00
|
|
|
pbr-m1|\
|
2017-07-23 19:06:44 +00:00
|
|
|
re350-v1|\
|
2017-05-05 15:54:26 +00:00
|
|
|
rt-ac51u|\
|
2015-08-17 06:24:47 +00:00
|
|
|
rt-n13u|\
|
|
|
|
|
rt-n14u|\
|
|
|
|
|
rt-n15|\
|
|
|
|
|
rt-n56u|\
|
|
|
|
|
wl-330n|\
|
|
|
|
|
wl-330n3g|\
|
|
|
|
|
wli-tx4-ag300n|\
|
|
|
|
|
y1|\
|
2017-10-21 09:07:43 +00:00
|
|
|
y1s|\
|
|
|
|
|
youku-yk1)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:power"
|
2014-11-05 14:37:13 +00:00
|
|
|
;;
|
2015-09-14 20:08:55 +00:00
|
|
|
db-wrt01|\
|
2016-09-27 06:23:27 +00:00
|
|
|
esr-9753|\
|
|
|
|
|
pbr-d1)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:orange:power"
|
2011-12-23 14:27:10 +00:00
|
|
|
;;
|
2016-12-01 14:08:22 +00:00
|
|
|
f5d8235-v1)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:wired"
|
2016-12-01 14:08:22 +00:00
|
|
|
;;
|
2012-01-23 10:23:32 +00:00
|
|
|
f5d8235-v2)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:router"
|
2015-08-17 06:24:34 +00:00
|
|
|
;;
|
2016-08-10 00:18:32 +00:00
|
|
|
f7c027|\
|
|
|
|
|
timecloud)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:orange:status"
|
2015-08-17 06:24:34 +00:00
|
|
|
;;
|
2015-10-05 10:25:47 +00:00
|
|
|
hc5*61|\
|
2017-02-24 23:19:15 +00:00
|
|
|
hc5661a|\
|
2016-03-04 08:33:09 +00:00
|
|
|
jhr-n805r|\
|
|
|
|
|
jhr-n926r|\
|
2015-10-05 10:25:47 +00:00
|
|
|
mlw221|\
|
ramips: add support for Vonets VAR11N-300
The VAR11N-300 is a tiny wireless-N device with a hardwired Ethernet
cable, one extra Ethernet port, and an internal antenna, based on the
MediaTek MT7620n chipset.
Specs:
- MT7620n WiSoC @ 600MHz
- 32 MB SDRAM
- 4 MB SPI flash
- 2T2R 2.4GHz WiFi-N
- 1 attached 10/100 Ethernet cable (LAN)
- 1 10/100 Ethernet port (WAN)
- 1 attached USB / barrel 5vdc power cable
- 5 LEDs (see notes below)
- 1 reset button
- 1 UART (3 pads on board)
Installation:
The stock firmware does not support uploading new firmware directly,
only checking the manufacturer's site for updates. This process may be
possible to spoof, but the update check uses some kind of homebrew
encryption that I didn't investigate. Instead, you can install via a
backdoor:
1. Set up a TFTP server to serve the firmware binary
(lede-ramips-mt7620-var11n-300-squashfs-sysupgrade.bin)
2. Factory reset the device by holding the reset button for a few
seconds.
3. Open the web interface (default IP: 192.168.253.254)
4. Log in with the "super admin" credentials: username `vonets`,
password `vonets26642519`.
5. On the "Operative Status" page, click the text "System Uptime", then
quickly click the uptime value.
6. If successful, an alert dialog will appear reading "Ated start", and
the device will now accept telnet connections. If the alert does not
appear, repeat step 5 until it works (the timing is a bit tricky).
7. Telnet to the device using credentials "admin / admin"
8. Retrieve the firmware binary from the tftp server: `tftp -l lede.bin
-r lede-ramips-mt7620-var11n-300-squashfs-sysupgrade.bin -g
<tftp-server-ip>`
9. Write the firmware to flash: `mtd_write write lede.bin /dev/mtd4`
10. Reboot
Tested:
- LAN / WAN ethernet
- WiFi
- LAN / WAN / status LED GPIOs (see notes below)
- Reset button
- Sysupgrade
Notes:
LEDs:
The board has 5 LEDs - two green LEDs for LAN / WAN activity, one blue
LED for WiFi, and a pair of "status" LEDs connected to the same GPIO
(the blue LED lights when the GPIO is low, and the green when it's
high). I was unable to determine how to operate the WiFi LED, as it
does not appear to be controlled by a GPIO directly.
Recovery:
The default U-boot installation will only boot from flash due to a
missing environment block. I generated a valid 4KB env block using
U-boot's `fw_setenv` tool and wrote it to flash at 0x30000 using an
external programmer. After this, it was possible to enter the U-boot
commandline interface and download a new image via TFTP (`tftpboot
81b00000 <image-filename>`), but while I could boot this image
sucessfully (`bootm`), writing it to flash (`cp.linux`) just corrupted
the flash chip. The sysupgrade file can be written to flash at 0x50000
using an external programmer.
Signed-off-by: Andrew Crawley <acrawley@gmail.com>
2017-11-23 23:52:13 +00:00
|
|
|
mlwg2|\
|
|
|
|
|
vonets,var11n-300)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:system"
|
2015-10-05 10:25:47 +00:00
|
|
|
;;
|
2017-02-22 12:47:22 +00:00
|
|
|
hc5962)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:white:status"
|
2017-02-22 12:47:22 +00:00
|
|
|
;;
|
2017-07-18 05:02:51 +00:00
|
|
|
k2p|\
|
|
|
|
|
m3|\
|
|
|
|
|
miwifi-nano)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:status"
|
2017-07-18 05:02:51 +00:00
|
|
|
;;
|
2017-11-16 21:58:23 +00:00
|
|
|
linkits7688)
|
2015-11-03 13:32:02 +00:00
|
|
|
[ "$1" = "upgrade" ] && status_led="mediatek:orange:wifi"
|
|
|
|
|
;;
|
2015-01-17 14:06:13 +00:00
|
|
|
m2m)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:wifi"
|
2013-08-01 14:30:53 +00:00
|
|
|
;;
|
2017-05-17 10:18:45 +00:00
|
|
|
gl-mt300n-v2)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:red:wlan"
|
2017-05-17 10:18:45 +00:00
|
|
|
;;
|
2017-04-07 22:34:48 +00:00
|
|
|
m4-4M|\
|
|
|
|
|
m4-8M)
|
|
|
|
|
status_led="m4:blue:status"
|
|
|
|
|
;;
|
2017-08-12 14:56:11 +00:00
|
|
|
mir3g)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:yellow:status"
|
2017-08-12 14:56:11 +00:00
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
miwifi-mini|\
|
|
|
|
|
zte-q7)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:red:status"
|
2015-08-17 06:24:34 +00:00
|
|
|
;;
|
2015-05-23 15:27:05 +00:00
|
|
|
mr-102n)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:amber:status"
|
2011-08-22 20:41:49 +00:00
|
|
|
;;
|
2016-09-24 19:41:43 +00:00
|
|
|
mr200)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:white:power"
|
2016-09-24 19:41:43 +00:00
|
|
|
;;
|
2011-07-28 10:56:32 +00:00
|
|
|
nw718)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:amber:cpu"
|
2011-07-28 10:56:32 +00:00
|
|
|
;;
|
2016-09-27 06:25:04 +00:00
|
|
|
newifi-d1)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:status"
|
2016-09-27 06:25:04 +00:00
|
|
|
;;
|
2017-01-09 19:59:56 +00:00
|
|
|
omega2| \
|
|
|
|
|
omega2p)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:amber:system"
|
2017-01-09 19:59:56 +00:00
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
oy-0001|\
|
2017-04-12 05:53:56 +00:00
|
|
|
sl-r7205)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:wifi"
|
2011-12-14 20:51:26 +00:00
|
|
|
;;
|
2012-06-19 09:52:15 +00:00
|
|
|
psr-680w)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:red:wan"
|
2015-08-17 06:24:34 +00:00
|
|
|
;;
|
2017-04-07 22:34:48 +00:00
|
|
|
px-4885-4M|\
|
|
|
|
|
px-4885-8M)
|
|
|
|
|
status_led="px-4885:orange:wifi"
|
|
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
re6500|\
|
|
|
|
|
whr-1166d|\
|
2016-05-28 10:04:17 +00:00
|
|
|
whr-600d|\
|
|
|
|
|
widora-neo)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:orange:wifi"
|
2012-02-13 15:18:04 +00:00
|
|
|
;;
|
2016-04-26 11:43:06 +00:00
|
|
|
mzk-ex300np|\
|
2015-08-17 06:24:47 +00:00
|
|
|
rt-n10-plus|\
|
2017-06-09 11:02:56 +00:00
|
|
|
tew-638apb-v2|\
|
2015-08-17 06:24:47 +00:00
|
|
|
tew-691gr|\
|
|
|
|
|
tew-692gr|\
|
|
|
|
|
ur-326n4g|\
|
|
|
|
|
ur-336un|\
|
2017-04-07 22:34:48 +00:00
|
|
|
wf-2881)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:wps"
|
2014-06-02 12:42:48 +00:00
|
|
|
;;
|
ramips: add support for MikroTik hEX v3 (RB750Gr3)
The MikroTik hEX v3 (RB750Gr3) is a MT7621AT board which is similar to most MT7621 reference designs, it can be easily supported by this patch; however, the stock RouterBOOT bootloader has to be replaced by a MT7621 SDK U-Boot such as https://github.com/ndoo/RB750Gr3-U-Boot - U-Boot configured for the RB750Gr3 (16MiB SPI flash, 256MiB DDR3 RAM at 1200MHz).
RouterBOOT, the stock bootloader, does not initialize the UART and boots silently, making it preferable to replace it with a MT7621 SDK U-Boot with UART (57600 8N1) that supports HTTP, TFTP or serial upload of sysupgrade firmware and U-Boot.
Furthermore, RouterOS, the stock firmware, is contained in a proprietary modification of SquashFS without GPL sources; UART is also disabled in stock firmware.
The combination of LEDE firmware generated by this PR and MT7621 SDK U-Boot expects the printed MAC address to reside at offset `0xe000` of the factory partition (absolute offset is `0x4e000`); this is similar to the factory MAC address offset for several other MT7621 devices.
A 16MiB flash dump suitable for use with flashrom will be provided if/once this patch is accepted and binaries are built by LEDE buildbot. Alternatively, writing the U-Boot to the SPI flash starting at 0x0 offset and booting the board with serial console attached will allow TFTP, HTTP or serial upload of sysupgrade firmware.
Signed-off-by: Andrew Yong <me@ndoo.sg>
2016-10-18 20:05:32 +00:00
|
|
|
rb750gr3)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:pwr"
|
ramips: add support for MikroTik hEX v3 (RB750Gr3)
The MikroTik hEX v3 (RB750Gr3) is a MT7621AT board which is similar to most MT7621 reference designs, it can be easily supported by this patch; however, the stock RouterBOOT bootloader has to be replaced by a MT7621 SDK U-Boot such as https://github.com/ndoo/RB750Gr3-U-Boot - U-Boot configured for the RB750Gr3 (16MiB SPI flash, 256MiB DDR3 RAM at 1200MHz).
RouterBOOT, the stock bootloader, does not initialize the UART and boots silently, making it preferable to replace it with a MT7621 SDK U-Boot with UART (57600 8N1) that supports HTTP, TFTP or serial upload of sysupgrade firmware and U-Boot.
Furthermore, RouterOS, the stock firmware, is contained in a proprietary modification of SquashFS without GPL sources; UART is also disabled in stock firmware.
The combination of LEDE firmware generated by this PR and MT7621 SDK U-Boot expects the printed MAC address to reside at offset `0xe000` of the factory partition (absolute offset is `0x4e000`); this is similar to the factory MAC address offset for several other MT7621 devices.
A 16MiB flash dump suitable for use with flashrom will be provided if/once this patch is accepted and binaries are built by LEDE buildbot. Alternatively, writing the U-Boot to the SPI flash starting at 0x0 offset and booting the board with serial console attached will allow TFTP, HTTP or serial upload of sysupgrade firmware.
Signed-off-by: Andrew Yong <me@ndoo.sg>
2016-10-18 20:05:32 +00:00
|
|
|
;;
|
2015-07-24 09:09:22 +00:00
|
|
|
sap-g3200u3)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:usb"
|
2012-02-15 21:13:11 +00:00
|
|
|
;;
|
2017-02-19 08:46:44 +00:00
|
|
|
u25awf-h1)
|
|
|
|
|
status_led="u25awf:red:wifi"
|
|
|
|
|
;;
|
ramips: add support for UniElec U7621-06
UniElec U7621-06 is a router platform board based on MediaTek MT7621AT.
The device has the following specifications:
- MT7621AT (880 MHz)
- 256/512 MB of RAM (DDR3)
- 8/16/32/64 MB of FLASH (SPI NOR)
- 5x 1 Gbps Ethernet (MT7621 built-in switch)
- 1x ASMedia ASM1061 (for mSATA and SATA)
- 2x miniPCIe slots (PCIe bus only)
- 1x mSATA slot (with USB 2.0 bus for modem)
- 1x SATA
- 1x miniSIM slot
- 1x microSD slot
- 1x USB 3.0
- 12x LEDs (3 GPIO-controlled)
- 1x reset button
- 1x UART header (4-pins)
- 1x GPIO header (30-pins)
- 1x FPC connector for LEDs (20-pin, 0.5 mm pitch)
- 1x DC jack for main power (12 V)
The following has been tested and is working:
- Ethernet switch
- miniPCIe slots (tested with Wi-Fi cards)
- mSATA slot (tested with modem and mSATA drive)
- miniSIM slot
- sysupgrade
- reset button
- microSD slot
Installation:
This board might come with a different firmware versions (MediaTek SDK,
PandoraBox, Padavan, etc.). If your board comes with PandoraBox, you can
install LEDE using sysupgrade. Just SSH to the router and perform forced
sysupgrade (due to a board name mismatch). The default IP of this board
should be: 192.168.1.1 and username/password: root/admin. In case of a
different firmware, you can use web based recovery described below.
Use the following command to perform the sysupgrade (for the 256MB
RAM/16MB flash version):
sysupgrade -n -F lede-ramips-mt7621-u7621-06-256M-16M-squashfs-sysupgrade.bin
Recovery:
This board contains a Chinese, closed-source bootloader called Breed
(Boot and Recovery Environment for Embedded Devices). Breed supports web
recovery and to enter it, you keep the reset button pressed for around
5 seconds during boot. Your machine will be assigned an IP through DHCP
and the router will use IP address 192.168.1.1. The recovery website is
in Chinese, but is easy to use. Click on the second item in the list to
access the recovery page, then the second item on the next page is where
you select the firmware. In order to start the recovery, you click the
button at the bottom.
LEDs list (top row, left to right):
- LED_WWAN# (connected with pin 42 in LTE/mSATA slot)
- Power (connected directly to 3V3)
- CTS2_N (GPIO10, configured as "status" LED)
- TXD2 (GPIO11, configured as "led4", without default trigger)
- RXD2 (GPIO12, configured as "led5", without default trigger)
- LED_WLAN# (connected with pin 44 in wifi0 slot)
LEDs list (bottom row, left to right):
- ESW_P0_LED_0
- ESW_P1_LED_0
- ESW_P2_LED_0
- ESW_P3_LED_0
- ESW_P4_LED_0
- LED_WLAN# (connected with pin 44 in wifi1 slot)
Other notes:
1. The board is available with different amounts of RAM and flash. We
have only added support for the 256/16 MB configuration, as that seems
to be the default. However, all the required infrastructure is in place
for making support for the other configurations easy.
2. The manufacturer offers five different wireless cards with MediaTek
chipsets, based on MT76x2, MT7603 and MT7615. Images of the board all
show that the miniPCIe slots are dedicated to specific Wi-Fi cards.
However, the slots are generic.
3. All boards we got access to had the same EEPROM content. The default
firmware reads the Ethernet MAC from offset 0xe000 in factory partition.
This offset only contains 0xffs, so a random MAC will be generated on
every boot of the router. There is a valid MAC stored at offset 0xe006
and this MAC is shown as the WAN MAC in the bootloader. However, it is
the same on all boards we have checked. Based on information provided
by the vendor, all boards sold in small quantities are considered more
as samples for development purposes.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-11-02 15:04:49 +00:00
|
|
|
u7621-06-256M-16M)
|
|
|
|
|
status_led="u7621-06:green:status"
|
|
|
|
|
;;
|
ramips: add support for UniElec U7628-01
UniElec U7628-01 is a router platform board based on MediaTek MT7628AN.
The device has the following specifications:
- MT7628AN (580MHz)
- 64/128/256 MB of RAM (DDR2)
- 8/16 MB of flash (SPI NOR)
- 5x 10/100 Mbps Ethernet (MT7628 built-in switch)
- 1x 2T2R 2.4 GHz Wi-Fi (MT7628)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses)
- 1x miniSIM slot
- 1x microSD slot
- 1x USB 2.0 port
- 7x single-color LEDs (GPIO-controlled)
- 1x bi-color LED (green GPIO-controlled, red -> LED_WLAN# in miniPCIe)
- 1x reset button
- 1x UART header (4-pins)
- 1x SDXC/GPIO header (10-pins, connected with microSD slot)
- 1x DC jack for main power (12 V)
The following has been tested and is working:
- Ethernet switch
- miniPCIe slot (tested with modem and Wi-Fi card)
- miniSIM slot
- sysupgrade
- reset button
- USB 2.0 port*
Due to a missing driver (MMC over GPIO) this is not supported:
- microSD card reader
* Warning:
USB buses in miniPCIe and regular A-type socket are connected together,
without any proper analog switch or USB HUB.
Installation:
This board might come with a different firmware versions (MediaTek SDK,
PandoraBox, Padavan, etc.). If your board comes with PandoraBox, you can
install LEDE using sysupgrade. Just SSH to the router and perform forced
sysupgrade (due to a board name mismatch). The default IP of this board
should be: 192.168.1.1 and username/password: root/admin. In case of a
different firmware, you can use web based recovery described below.
Use the following command to perform the sysupgrade (for the 128MB
RAM/16MB flash version):
sysupgrade -n -F lede-ramips-mt76x8-u7628-01-128M-16M-squashfs-sysupgrade.bin
Recovery:
This board contains a Chinese, closed-source bootloader called Breed
(Boot and Recovery Environment for Embedded Devices). Breed supports web
recovery and to enter it, you keep the reset button pressed for around
5 seconds during boot. Your machine will be assigned an IP through DHCP
and the router will use IP address 192.168.1.1. The recovery website is
in Chinese, but is easy to use. Click on the second item in the list to
access the recovery page, then the second item on the next page is where
you select the firmware. In order to start the recovery, you click the
button at the bottom.
SDXC/GPIO header (J3):
1. SDXC_D3 / I2C_SCLK
2. SDXC_D2 / I2C_SD
3. SDXC_D1 / I2S_DI
4. SDXC_D0 / I2S_WS
5. SDXC_CMD / I2S_CLK
6. SDXC_CLK / GPIO0
7. SDXC_CD / UART_RXD1
8. UART_TXD1
9. 3V3
10. GND
Other notes:
1. The board is available with different amounts of RAM and flash. We
have only added support for the 128/16 MB configuration, as that seems
to be the default. However, all the required infrastructure is in place
for making support for the other configurations easy.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-11-03 20:12:49 +00:00
|
|
|
u7628-01-128M-16M)
|
|
|
|
|
status_led="u7628-01:green:power"
|
|
|
|
|
;;
|
2011-07-06 08:05:00 +00:00
|
|
|
v22rw-2x2)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:security"
|
2015-02-16 21:19:18 +00:00
|
|
|
;;
|
2017-04-07 22:34:48 +00:00
|
|
|
vocore-8M|\
|
|
|
|
|
vocore-16M)
|
|
|
|
|
status_led="vocore:green:status"
|
|
|
|
|
;;
|
2017-01-08 06:30:10 +00:00
|
|
|
vocore2)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:fuchsia:status"
|
2017-01-08 06:30:10 +00:00
|
|
|
;;
|
2017-08-03 20:09:06 +00:00
|
|
|
vocore2lite)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:status"
|
2017-08-03 20:09:06 +00:00
|
|
|
;;
|
2015-12-11 15:03:50 +00:00
|
|
|
w306r-v20|\
|
2015-12-11 15:04:13 +00:00
|
|
|
witi|\
|
2015-12-11 15:03:50 +00:00
|
|
|
zbt-wr8305rt)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:sys"
|
2015-12-11 15:03:50 +00:00
|
|
|
;;
|
2017-01-28 16:05:56 +00:00
|
|
|
wcr-1166ds|\
|
|
|
|
|
whr-300hp2|\
|
|
|
|
|
wsr-1166|\
|
|
|
|
|
wsr-600)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:power"
|
2017-01-28 16:05:56 +00:00
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
wcr-150gn|\
|
2011-12-23 14:27:16 +00:00
|
|
|
wl-351)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:amber:power"
|
2015-08-17 06:24:34 +00:00
|
|
|
;;
|
2015-08-17 06:24:47 +00:00
|
|
|
whr-g300n|\
|
2017-03-15 08:37:05 +00:00
|
|
|
wlr-6000|\
|
|
|
|
|
zbt-we2026)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:red:power"
|
2016-08-14 21:30:44 +00:00
|
|
|
;;
|
2015-08-17 06:24:34 +00:00
|
|
|
wzr-agl300nh)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:router"
|
2014-02-18 13:33:25 +00:00
|
|
|
;;
|
2015-09-14 20:09:31 +00:00
|
|
|
wizfi630a)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname::run"
|
2015-09-14 20:09:31 +00:00
|
|
|
;;
|
2017-04-07 22:34:48 +00:00
|
|
|
wr512-3gn-4M|\
|
|
|
|
|
wr512-3gn-8M)
|
|
|
|
|
status_led="wr512-3gn:green:wps"
|
|
|
|
|
;;
|
2016-01-01 21:19:50 +00:00
|
|
|
wrtnode2r | \
|
|
|
|
|
wrtnode2p | \
|
|
|
|
|
wrtnode)
|
|
|
|
|
status_led="wrtnode:blue:indicator"
|
|
|
|
|
;;
|
2017-04-07 22:34:48 +00:00
|
|
|
wt3020-4M|\
|
|
|
|
|
wt3020-8M)
|
|
|
|
|
status_led="wt3020:blue:power"
|
|
|
|
|
;;
|
2016-09-25 19:09:31 +00:00
|
|
|
zbt-cpe102)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:green:4g-0"
|
2016-09-25 19:09:31 +00:00
|
|
|
;;
|
2017-04-12 05:53:56 +00:00
|
|
|
zbt-we826-16M|\
|
|
|
|
|
zbt-we826-32M)
|
2017-04-12 05:56:40 +00:00
|
|
|
status_led="zbt-we826:green:power"
|
2017-04-12 05:53:56 +00:00
|
|
|
;;
|
2017-04-01 08:46:44 +00:00
|
|
|
zbt-wg3526-16M|\
|
|
|
|
|
zbt-wg3526-32M)
|
2017-04-07 21:52:27 +00:00
|
|
|
status_led="zbt-wg3526:green:status"
|
|
|
|
|
;;
|
2011-03-27 19:19:40 +00:00
|
|
|
esac
|
2010-04-11 17:47:23 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
set_state() {
|
2015-11-03 13:32:02 +00:00
|
|
|
get_status_led $1
|
2010-04-11 17:47:23 +00:00
|
|
|
|
|
|
|
|
case "$1" in
|
|
|
|
|
preinit)
|
2013-02-18 09:56:29 +00:00
|
|
|
status_led_blink_preinit
|
2010-04-11 17:47:23 +00:00
|
|
|
;;
|
|
|
|
|
failsafe)
|
2013-02-18 09:56:29 +00:00
|
|
|
status_led_blink_failsafe
|
2010-04-11 17:47:23 +00:00
|
|
|
;;
|
2015-11-03 13:32:02 +00:00
|
|
|
upgrade | \
|
2014-12-15 10:37:00 +00:00
|
|
|
preinit_regular)
|
|
|
|
|
status_led_blink_preinit_regular
|
|
|
|
|
;;
|
2010-04-11 17:47:23 +00:00
|
|
|
done)
|
|
|
|
|
status_led_on
|
|
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
}
|
