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|\
|
2018-06-15 15:27:51 +00:00
|
|
|
elecom,wrc-1167ghbk2-s|\
|
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-12-30 09:19:18 +00:00
|
|
|
firewrt|\
|
2017-09-09 13:16:11 +00:00
|
|
|
hg255d|\
|
ramips: add support for I-O DATA WN-GX300GR
I-O DATA WN-GX300GR is a 2.4 GHz band 11n router, based on MediaTek
MT7621S.
Specification:
- MT7621S (1-Core, 2-Threads)
- 64 MB of RAM
- 8 MB of Flash (SPI)
- 2T2R 2.4 GHz
- 5x 10/100/1000 Mbps Ethernet
- 2x LEDs, 4x keys (2x buttons, 1x slide switch)
- UART header on PCB
- Vcc, GND, TX, RX from ethernet port side
- baudrate: 115200 bps (U-Boot, OpenWrt)
Flash instruction using initramfs image:
1. Connect serial cable to UART header
2. Rename OpenWrt initramfs image for WN-GX300GR to "uImageWN-GX300GR"
and place it in the TFTP directory
3. Set the IP address of the computer to 192.168.99.8, connect to the
LAN port of WN-GX300GR, and start the TFTP server on the computer
4. Connect power cable to WN-GX300GR and turn on the router
5. Press "1" key on the serial console to interrupt boot process on
U-Boot, press Enter key 3 times and start firmware download via TFTP
6. WN-GX300GR downloads initramfs image and boot with it
7. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-GX300GR
8. Wait ~150 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-05-16 12:42:48 +00:00
|
|
|
iodata,wn-gx300gr|\
|
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|\
|
2018-01-09 11:25:53 +00:00
|
|
|
tplink,c20-v4|\
|
2018-01-28 18:49:38 +00:00
|
|
|
tplink,c50-v3|\
|
2017-12-15 14:57:49 +00:00
|
|
|
tplink,tl-mr3420-v5|\
|
2018-05-30 15:41:53 +00:00
|
|
|
tplink,tl-wr842n-v5|\
|
2018-03-17 17:47:51 +00:00
|
|
|
tplink,tl-wr902ac-v3|\
|
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
|
|
|
;;
|
2017-10-14 08:44:39 +00:00
|
|
|
alfa-network,ac1200rm|\
|
|
|
|
|
awapn2403|\
|
|
|
|
|
dir-645|\
|
|
|
|
|
sk-wb8|\
|
2018-05-17 09:57:00 +00:00
|
|
|
tplink,c2-v1|\
|
2017-10-14 08:44:39 +00:00
|
|
|
wrh-300cr)
|
|
|
|
|
status_led="$boardname:green:wps"
|
|
|
|
|
;;
|
2018-01-26 15:21:34 +00:00
|
|
|
alfa-network,awusfree1)
|
|
|
|
|
status_led="$boardname:orange:system"
|
|
|
|
|
;;
|
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|\
|
2018-01-20 08:27:03 +00:00
|
|
|
dlink,dwr-116-a1|\
|
2018-05-27 00:26:14 +00:00
|
|
|
gnubee,gb-pc1|\
|
2018-02-17 08:54:57 +00:00
|
|
|
gnubee,gb-pc2|\
|
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
|
|
|
;;
|
2018-03-10 09:34:38 +00:00
|
|
|
dlink,dwr-921-c1)
|
|
|
|
|
status_led="$boardname:green:sigstrength"
|
|
|
|
|
;;
|
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
|
|
|
;;
|
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|\
|
2018-03-29 10:33:02 +00:00
|
|
|
w502u|\
|
|
|
|
|
youhua,wr1200js)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:wps"
|
2015-08-17 06:24:47 +00:00
|
|
|
;;
|
2017-02-04 20:28:52 +00:00
|
|
|
d240|\
|
2015-08-17 06:24:47 +00:00
|
|
|
dap-1350|\
|
|
|
|
|
na930|\
|
ramips: add support for newifi d2
Previously Newifi D2 could only use PandoraBox M1's firmware.
It works fine, but LED GPIO is different.
As a result, a separated DTS file for this device should be implemented.
Hardware spec:
* CPU: MTK MT7621A
* RAM: 512MB
* ROM: 32MB SPI Flash
* WiFi: MTK MT7603+MT7612
* Button: 2 buttons (reset, wps)
* LED: 3 single-color LEDs (USB, WiFi 2.4GHz, WiFi 5GHz) &
2 dual-color LEDs (Power, Internet)
* Ethernet: 5 ports, 4 LAN + 1 WAN
Installation method:
Same as Newifi D1, users may need to request unlock code from the device
manufacturer. Otherwise, a SPI flash programmer may be necessary to get
the firmware flashed. After the device is unlocked, press and hold reset
button before power cable plugs in. Then go to http://192.168.1.1 to
upload and flash the firmware package.
Signed-off-by: Jackson Ming Hu <huming2207@gmail.com>
2017-12-15 03:51:33 +00:00
|
|
|
d-team,newifi-d2|\
|
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|\
|
2018-01-13 07:16:20 +00:00
|
|
|
tplink,c20-v1|\
|
2015-08-17 06:24:47 +00:00
|
|
|
wl-330n|\
|
|
|
|
|
wl-330n3g|\
|
|
|
|
|
wli-tx4-ag300n|\
|
|
|
|
|
y1|\
|
2017-10-21 09:07:43 +00:00
|
|
|
y1s|\
|
2018-04-03 23:19:22 +00:00
|
|
|
youku-yk1|\
|
|
|
|
|
zorlik,zl5900v2)
|
2017-11-16 21:17:42 +00:00
|
|
|
status_led="$boardname:blue:power"
|
2014-11-05 14:37:13 +00:00
|
|
|
;;
|
2018-02-17 08:18:09 +00:00
|
|
|
dlink,dap-1522-a1|\
|
2018-06-20 16:56:38 +00:00
|
|
|
phicomm,k2g|\
|
2017-10-28 12:24:21 +00:00
|
|
|
k2p|\
|
|
|
|
|
m3|\
|
|
|
|
|
mir3g|\
|
|
|
|
|
miwifi-nano)
|
|
|
|
|
status_led="$boardname:blue:status"
|
|
|
|
|
;;
|
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-11-16 21:58:23 +00:00
|
|
|
linkits7688)
|
2017-12-21 18:55:25 +00:00
|
|
|
status_led="linkit-smart-7688:orange:wifi"
|
2015-11-03 13:32:02 +00:00
|
|
|
;;
|
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)
|
2018-02-20 17:39:16 +00:00
|
|
|
status_led="$boardname:green:power"
|
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"
|
|
|
|
|
;;
|
ramips: Add support for Mikrotik RouterBOARD RBM33g
This commit adds support for the Mikrotik RouterBOARD RBM33g.
=Hardware=
The RBM33g is a mt7621 based device featuring three gigabit ports, 2
miniPCIe slots with sim card sockets, 1 M.2 slot, 1 USB 3.0 port and a male
onboard RS-232 serial port. Additionally there are a lot of accessible
GPIO ports and additional buses like i2c, mdio, spi and uart.
==Switch==
The three Ethernet ports are all connected to the internal switch of the
mt7621 SoC:
port 0: Ethernet Port next to barrel jack with PoE printed on it
port 1: Innermost Ethernet Port on opposite side of RS-232 port
port 2: Outermost Ethernet Port on opposite side of RS-232 port
port 6: CPU
==Flash==
The device has two spi flash chips. The first flash chips is rather small
(512 kB), connected to CS0 by default and contains only the RouterBOOT
bootloader and some factory information (e.g. mac address).
The second chip has a size of 16 MB, is by default connected to CS1 and
contains the firmware image.
==PCIe==
The board features three PCIe-enabled slots. Two of them are miniPCIe
slots (PCIe0, PCIe1) and one is a M.2 (Key M) slot (PCIe2).
Each of the miniPCIe slots is connected to a dedicated mini SIM socket
on the back of the board.
Power to all three PCIe-enabled slots is controlled via GPIOs on the
mt7621 SoC:
PCIe0: GPIO9
PCIe1: GPIO10
PCIe2: GPIO11
==USB==
The board has one external USB 3.0 port at the rear. Additionally PCIe
port 0 has a permanently enabled USB interface. PCIe slot 1 shares its
USB interface with the rear USB port. Thus only either the rear USB port
or the USB interface of PCIe slot 1 can be active at the same time. The
jumper next to the rear USB port controls which one is active:
open: USB on PCIe 1 is active
closed: USB on rear USB port is active
==Power==
The board can accept both, passive PoE and external power via a 2.1 mm
barrel jack. The input voltage range is 11-32 V.
=Installation=
==Prerequisites==
A USB -> RS-232 Adapter and a null modem cable are required for
installation.
To install an OpenWRT image to the device two components must be built:
1. A openwrt initramfs image
2. A openwrt sysupgrade image
===initramfs & sysupgrade image===
Select target devices "Mikrotik RBM33G" in
openwrt menuconfig and build the images. This will create the images
"openwrt-ramips-mt7621-mikrotik_rbm33g-initramfs-kernel.bin" and
"openwrt-ramips-mt7621-mikrotik_rbm33g-squashfs-sysupgrade.bin" in the output
directory.
==Installing==
**Make sure to back up your RouterOS license in case you do ever want to
go back to RouterOS using "/system license output" and back up the created
license file.**
Serial settings: 115200 8N1
The installation is a two-step process. First the
"openwrt-ramips-mt7621-mikrotik_rbm33g-initramfs-kernel.bin" must be booted
via tftp:
1. Set up a dhcp server that points the bootfile to tftp server serving
the "openwrt-ramips-mt7621-mikrotik_rbm33g-initramfs-kernel.bin"
initramfs image
2. Connect to WAN port (left side, next to sys-LED and power indicator)
3. Connect to serial port of board
4. Power on board and enter RouterBOOT setup menu
5. Set boot device to "boot over ethernet"
6. Set boot protocol to "dhcp protocol" (can be omitted if DHCP server
allows dynamic bootp)
6. Save config
7. Wait for board to boot via Ethernet
On the serial port you should now be presented with the OpenWRT boot log.
The next steps will install OpenWRT persistently.
1. Copy "openwrt-ramips-mt7621-mikrotik_rbm33g-squashfs-sysupgrade.bin" to the device
using scp.
2. Write openwrt to flash using "sysupgrade
openwrt-ramips-mt7621-mikrotik_rbm33g-squashfs-sysupgrade.bin"
Once the flashing completes reboot the router and let it boot from flash.
It should boot straight to OpenWRT.
Signed-off-by: Tobias Schramm <tobleminer@gmail.com>
2018-05-04 01:47:23 +00:00
|
|
|
mikrotik,rbm33g)
|
|
|
|
|
status_led="rbm33g:green:usr"
|
|
|
|
|
;;
|
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|\
|
2017-12-27 21:09:52 +00:00
|
|
|
whr-600d)
|
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|\
|
2018-05-03 15:59:27 +00:00
|
|
|
mqmaker,witi-256m|\
|
|
|
|
|
mqmaker,witi-512m|\
|
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
|
|
|
;;
|
2018-01-08 05:27:28 +00:00
|
|
|
widora,neo-16m|\
|
|
|
|
|
widora,neo-32m)
|
2017-12-27 21:09:52 +00:00
|
|
|
status_led="widora:orange:wifi"
|
|
|
|
|
;;
|
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
|
|
|
;;
|
2018-01-24 00:27:51 +00:00
|
|
|
zbtlink,zbt-we1226)
|
|
|
|
|
status_led="$boardname:green:wlan"
|
2018-01-23 01:46:36 +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
|
|
|
|
|
}
|