2019-10-22 12:37:13 +02:00
|
|
|
|
|
|
|
. /lib/functions/leds.sh
|
|
|
|
. /lib/functions/uci-defaults.sh
|
|
|
|
|
|
|
|
board=$(board_name)
|
|
|
|
|
|
|
|
board_config_update
|
|
|
|
|
|
|
|
case $board in
|
|
|
|
aigale,ai-br100)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "wan" "wan" "blue:wan" "eth0.2"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "blue:wlan" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
alfa-network,ac1200rm)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wlan2g" "wlan1"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
ramips: add support for ALFA Network R36M-E4G
ALFA Network R36M-E4G is a dual-SIM, N300 Wi-Fi, compact size platform
based on MediaTek MT7620A WiSoC. This product is designed for operation
with 4G modem (can be bought in bundle with Quectel EC25, EG25 or EP06)
but supports also Wi-Fi modules (miniPCIe slot has USB and PCIe buses).
Specification:
- MT7620A (580 MHz)
- 64/128/256 MB of RAM (DDR2)
- 16/32+ MB of FLASH (SPI NOR)
- 2x 10/100 Mbps Ethernet, with passive PoE support (24 V)
- 2T2R 2.4 GHz (MT7620A), with ext. LNA (RFFM4227)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses and optional 5 V)
- 2x SIM slot (mini, micro) with detect and switch driven by GPIO
- 2x u.fl antenna connectors (for Wi-Fi)
- 8x LED (7 driven by GPIO)
- 2x button (reset, wifi)
- 2x UART (4-pin/2.54 mm pitch, 10-pin/1.27 mm pitch) headers on PCB
- 1x I2C (4-pin, 1.27 mm pitch) header on PCB
- 1x LED (8-pin, 1.27 mm pitch) header on PCB
- 1x DC jack with lock (12 V)
Other:
- there is a dedicated, 4-pin connector for optional RTC module (Holtek
HT138x) with 'enable' input, not available at the time of preparing
support for this board
- miniPCIe slot supports additional 5 V supply on pins 47 and 49 but a
jumper resistor (R174) is not installed by default
- U-Boot selects default SIM slot, based on value of 'default_sim' env
variable: '1' or unset -> SIM1 (mini), '2' -> SIM2 (micro). This will
work only if both slots are occupied, otherwise U-Boot will always
select slot with SIM card inside (user can override it later, in
user-space)
- U-Boot resets the modem, using PERSTn signal, before starting kernel
- this board supports 'dual image' feature (controlled by 'dual_image'
U-Boot environment variable)
Flash instruction:
You can use the 'sysupgrade' image directly in vendor firmware which is
based on OpenWrt (make sure to not preserve settings - use 'sysupgrade
-n -F ...' command). Alternatively, use web recovery mode in U-Boot:
1. Power the device with reset button pressed, the modem LED will start
blinking slowly and after ~3 seconds, when it starts blinking faster,
you can release the button.
2. Setup static IP 192.168.1.2/24 on your PC.
3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-10-30 00:10:40 +01:00
|
|
|
alfa-network,r36m-e4g)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "4g" "4g" "orange:4g" "wwan0"
|
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch0" "0x8"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x10"
|
ramips: add support for ALFA Network R36M-E4G
ALFA Network R36M-E4G is a dual-SIM, N300 Wi-Fi, compact size platform
based on MediaTek MT7620A WiSoC. This product is designed for operation
with 4G modem (can be bought in bundle with Quectel EC25, EG25 or EP06)
but supports also Wi-Fi modules (miniPCIe slot has USB and PCIe buses).
Specification:
- MT7620A (580 MHz)
- 64/128/256 MB of RAM (DDR2)
- 16/32+ MB of FLASH (SPI NOR)
- 2x 10/100 Mbps Ethernet, with passive PoE support (24 V)
- 2T2R 2.4 GHz (MT7620A), with ext. LNA (RFFM4227)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses and optional 5 V)
- 2x SIM slot (mini, micro) with detect and switch driven by GPIO
- 2x u.fl antenna connectors (for Wi-Fi)
- 8x LED (7 driven by GPIO)
- 2x button (reset, wifi)
- 2x UART (4-pin/2.54 mm pitch, 10-pin/1.27 mm pitch) headers on PCB
- 1x I2C (4-pin, 1.27 mm pitch) header on PCB
- 1x LED (8-pin, 1.27 mm pitch) header on PCB
- 1x DC jack with lock (12 V)
Other:
- there is a dedicated, 4-pin connector for optional RTC module (Holtek
HT138x) with 'enable' input, not available at the time of preparing
support for this board
- miniPCIe slot supports additional 5 V supply on pins 47 and 49 but a
jumper resistor (R174) is not installed by default
- U-Boot selects default SIM slot, based on value of 'default_sim' env
variable: '1' or unset -> SIM1 (mini), '2' -> SIM2 (micro). This will
work only if both slots are occupied, otherwise U-Boot will always
select slot with SIM card inside (user can override it later, in
user-space)
- U-Boot resets the modem, using PERSTn signal, before starting kernel
- this board supports 'dual image' feature (controlled by 'dual_image'
U-Boot environment variable)
Flash instruction:
You can use the 'sysupgrade' image directly in vendor firmware which is
based on OpenWrt (make sure to not preserve settings - use 'sysupgrade
-n -F ...' command). Alternatively, use web recovery mode in U-Boot:
1. Power the device with reset button pressed, the modem LED will start
blinking slowly and after ~3 seconds, when it starts blinking faster,
you can release the button.
2. Setup static IP 192.168.1.2/24 on your PC.
3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-10-30 00:10:40 +01:00
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
alfa-network,tube-e4g)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "4g" "4g" "green:4g" "wwan0"
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "blue:lan" "eth0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
asus,rp-n53)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "eth" "Network" "white:back" "eth0"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "blue:wifi" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
asus,rt-n12p)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "lan" "lan" "green:lan" eth0.1
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "green:wan" eth0.2
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:air" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
asus,rt-n14u)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "lan" "lan" "blue:lan" eth0.1
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "blue:wan" eth0.2
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "blue:air" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
bdcom,wap2100-sk)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wlan2g" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
ramips: add support for BOLT BL100
BL100 is a router made by Bolt by a provider in Indonesia
The original firmware created using Mediatek SDK and kernel 2.6.36
- Chipset: MediaTek MT7620A ver 2, eco 6
- RAM: 64 MB
- Bootloader: U Boot
- Flash: Winbond W25Q128BV (16 MB)
- Ports: 2x 10/100 Ethernet, 1x RJ-11 VoIP
- Modem: Qualcomm LTE B40 (2300 Mhz) VID:05c6 PID:9026
- Wireless: Internal MT7620A (2.4 Ghz) & Mediatek MT76x2E (5.8 Ghz)
- Switch: MediaTek MT7620A built-in 5-port 10/100M switch
- Voltage: DC 12V 1A
- Antenna Port: 2x External Antenna, 2 LTE U.FL, 2 WiFi U.FL
- Serial Port: Yes, 3.3 V TTL, Baud 57600 8N1
- Buttons: Reset and WPS
- LED: 15 Total
- 4 blue lte, 2 red lte, 1 reset, 1 power.
- 1 wps, 1 voip, 1 wlan2, 1 wlan5, 1 lan, 1 wan, 1 wlan.
Installation via stock firmware
1. Unlock Telnet access by downloading the backup .tar.gz file
2. Change the Telnet configuration to LAN_Telnet=1
3. Import backup configuration
4. Restart the router
5. Login to telnet with username and password = admin : db40
6. Download sysupgrade binary and mtd_write to the kernel partition
`mtd_write write openwrt-bolt_bl100-squashfs-sysupgrade.bin Kernel`
Signed-off-by: Radito Wahyu <arditogits@gmail.com>
2024-03-30 03:28:57 +01:00
|
|
|
bolt,bl100)
|
|
|
|
ucidef_set_led_default "power" "power" "blue:power" "1"
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "green:lan" "eth0.1"
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "green:wan" "eth0.2"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
comfast,cf-wr800n)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "lan" "lan" "white:ethernet" eth0.1
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "white:wifi" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2023-05-31 16:50:23 +02:00
|
|
|
dlink,dir-806a-b1)
|
|
|
|
ucidef_set_led_netdev "wifi_led" "2.4g" "green:wlan" "phy1-ap0"
|
|
|
|
;;
|
2020-06-09 11:52:26 +02:00
|
|
|
dlink,dir-810l|\
|
|
|
|
trendnet,tew-810dr)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x10"
|
2020-06-09 11:52:26 +02:00
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
dlink,dwr-116-a1|\
|
|
|
|
head-weblink,hdrm200|\
|
|
|
|
ohyeah,oy-0001|\
|
|
|
|
planex,mzk-ex300np|\
|
2020-09-27 19:40:51 +02:00
|
|
|
zbtlink,zbt-we826-16m|\
|
|
|
|
zbtlink,zbt-we826-32m|\
|
2019-10-22 12:37:13 +02:00
|
|
|
zbtlink,zbt-wr8305rt|\
|
ramips: add support for Keenetic Lite III rev. A
General specification:
SoC Type: MediaTek MT7620N (580MHz)
ROM: 8 MB SPI-NOR (W25Q64FV)
RAM: 64 MB DDR (EM6AB160TSD-5G)
Switch: MediaTek MT7530
Ethernet: 5 ports - 5×100MbE (WAN, LAN1-4)
Wireless: 2.4 GHz (MediaTek RT5390): b/g/n
Buttons: 3 button (POWER, RESET, WPS)
Slide switch: 4 position (BASE, ADAPTER, BOOSTER, ACCESS POINT)
Bootloader: U-Boot 1.1.3
Power: 9 VDC, 0.6 A
MAC in stock:
|- + |
| LAN | RF-EEPROM + 0x04 |
| WLAN | RF-EEPROM + 0x04 |
| WAN | RF-EEPROM + 0x28 |
OEM easy installation
1. Use a PC to browse to http://my.keenetic.net.
2. Go to the System section and open the Files tab.
3. Under the Files tab, there will be a list of system
files. Click on the Firmware file.
4. When a modal window appears, click on the Choose File
button and upload the firmware image.
5. Wait for the router to flash and reboot.
OEM installation using the TFTP method
1. Download the latest firmware image and rename it to
klite3_recovery.bin.
2. Set up a Tftp server on a PC (e.g. Tftpd32) and place the
firmware image to the root directory of the server.
3. Power off the router and use a twisted pair cable to connect
the PC to any of the router's LAN ports.
4. Configure the network adapter of the PC to use IP address
192.168.1.2 and subnet mask 255.255.255.0.
5. Power up the router while holding the reset button pressed.
6. Wait approximately for 5 seconds and then release the
reset button.
7. The router should download the firmware via TFTP and
complete flashing in a few minutes.
After flashing is complete, use the PC to browse to
http://192.168.1.1 or ssh to proceed with the configuration.
Signed-off-by: Alexey Bartenev <41exey@proton.me>
2023-03-10 16:35:30 +01:00
|
|
|
zyxel,keenetic-lite-iii-a|\
|
2019-10-22 12:37:13 +02:00
|
|
|
zyxel,keenetic-omni|\
|
|
|
|
zyxel,keenetic-omni-ii|\
|
|
|
|
zyxel,keenetic-viva)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wifi" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
dlink,dwr-118-a1)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch0" "0x1f"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x20"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wlan2g" "wlan1"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
dlink,dwr-118-a2)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch0" "0x1e"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x01"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wlan2g" "wlan1"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
dlink,dwr-921-c1|\
|
|
|
|
dlink,dwr-922-e2)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch0" "0x0f"
|
|
|
|
ucidef_set_led_netdev "signalstrength" "signalstrength" "green:sigstrength" "wwan0" "link"
|
|
|
|
ucidef_set_led_netdev "4g" "4g" "green:4g" "wwan0" "tx rx"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wifi" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2018-04-19 09:20:58 +02:00
|
|
|
dlink,dwr-960)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch0" "0x2e"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x01"
|
2020-04-10 08:56:37 +02:00
|
|
|
;;
|
2022-02-18 00:23:45 +01:00
|
|
|
dlink,dwr-961-a1)
|
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch0" "0x3c"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x02"
|
|
|
|
;;
|
2021-07-27 06:32:00 +02:00
|
|
|
domywifi,dm202|\
|
|
|
|
domywifi,dm203|\
|
|
|
|
domywifi,dw22d)
|
|
|
|
ucidef_set_led_switch "lan1" "lan1" "amber:lan1" "switch0" "0x02"
|
|
|
|
ucidef_set_led_switch "lan2" "lan2" "amber:lan2" "switch0" "0x04"
|
|
|
|
ucidef_set_led_switch "lan3" "lan3" "amber:lan3" "switch0" "0x08"
|
|
|
|
ucidef_set_led_switch "lan4" "lan4" "amber:lan4" "switch0" "0x10"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "amber:wan" "switch0" "0x01"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
dovado,tiny-ac)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "orange:wifi" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2023-03-02 21:45:50 +01:00
|
|
|
edimax,br-6208ac-v2)
|
|
|
|
ucidef_set_led_netdev "wan" "Internet" "green:internet" "eth0.2" "tx rx"
|
|
|
|
ucidef_set_led_netdev "wifi_led" "WLAN 2.4 GHz" "green:wlan2g" "wlan1"
|
|
|
|
ucidef_set_led_netdev "wifi_led" "WLAN 5 GHz" "green:wlan5g" "wlan1"
|
|
|
|
ucidef_set_led_netdev "wifi_led" "Firmware" "green:firmware" "wlan1"
|
|
|
|
ucidef_set_led_netdev "lan" "VPN" "green:vpn" "switch0" "0x20"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
edimax,br-6478ac-v2|\
|
|
|
|
edimax,ew-7478apc)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "blue:wlan" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2022-10-25 03:13:30 +02:00
|
|
|
ampedwireless,b1200ex|\
|
2019-10-22 12:37:13 +02:00
|
|
|
edimax,ew-7476rpc|\
|
|
|
|
edimax,ew-7478ac)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch0" "0x20"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
elecom,wrh-300cr)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "lan" "lan" "green:ethernet" "eth0"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wlan" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
engenius,esr600)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "wlan5g" "5.0GHz" "blue:wlan5g" "wlan0"
|
|
|
|
ucidef_set_led_netdev "wlan2g" "2.4GHz" "blue:wlan2g" "wlan1"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
glinet,gl-mt300a|\
|
|
|
|
glinet,gl-mt300n|\
|
|
|
|
glinet,gl-mt750)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "wlan" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2019-12-31 15:35:41 +01:00
|
|
|
hiwifi,hc5661|\
|
2019-10-22 12:37:13 +02:00
|
|
|
hiwifi,hc5761)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "internet" "internet" "blue:internet" "switch0" "0x01"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
hiwifi,hc5861)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "internet" "internet" "blue:internet" "switch0" "0x20"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
hnet,c108)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "lan" "lan" "green:lan" "eth0"
|
|
|
|
ucidef_set_led_netdev "modem" "modem" "green:modem" "wwan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2021-12-24 20:48:22 +01:00
|
|
|
humax,e2)
|
|
|
|
ucidef_set_led_netdev "lan" "lan" "green:lan" "eth0"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
iodata,wn-ac1167gr|\
|
|
|
|
iodata,wn-ac733gr3)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_wlan "wlan5g" "WLAN5G" "green:wlan5g" "phy0radio"
|
|
|
|
ucidef_set_led_wlan "wlan2g" "WLAN2G" "green:wlan2g" "phy1radio"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
kimax,u25awf-h1)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "eth" "eth" "green:lan" "eth0"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "red:wifi" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
kimax,u35wf)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "eth" "ETH" "green:eth" "eth0"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "blue:wifi" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2020-05-14 15:16:57 +02:00
|
|
|
kingston,mlw221|\
|
|
|
|
kingston,mlwg2|\
|
|
|
|
sanlinking,d240)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "blue:wifi" "wlan0"
|
2020-05-14 15:16:57 +02:00
|
|
|
;;
|
2022-10-24 17:50:33 +02:00
|
|
|
snr,cpe-w4n-mt)
|
|
|
|
ucidef_set_led_heartbeat "wps" "WPS" "green:wps"
|
|
|
|
ucidef_set_led_timer "sys" "System" "green:sys" "500" "500"
|
|
|
|
ucidef_set_led_wlan "wlan" "Wi-Fi" "green:wlan" "phy0tpt"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
lenovo,newifi-y1)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "wifi" "WIFI" "blue:wifi" "wlan1"
|
|
|
|
ucidef_set_led_netdev "wifi5g" "WIFI5G" "blue:wifi5g" "wlan0"
|
|
|
|
ucidef_set_led_switch "lan" "LAN" "blue:lan" "switch0" "0x03"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
lenovo,newifi-y1s)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "wifi" "WIFI" "yellow:wifi" "wlan1"
|
|
|
|
ucidef_set_led_netdev "wifi5g" "WIFI5G" "blue:wifi" "wlan0"
|
|
|
|
ucidef_set_led_netdev "wan" "WAN" "blue:internet" "eth0.2" "tx rx"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
ramips: add support for Netcore NW5212
This patch adds support for Netcore NW5212, provided by some carrier in
China.
Specifications:
--------------
* SoC: Mediatek MT7620A
* RAM: 128MB DDR2
* Flash: 16MB SPI NOR flash (Winbond W25Q128BV)
* WiFi 2.4GHz: builtin
* Ethernet: builtin
* LED: Power, WAN, LAN 1-4, WiFi
* Buttons: Reset (GPIO 13)
* UART: Serial console (57600 8n1)
* USB: 1 x USB2
Installation:
------------
The router comes with OpenWrt 14.07 built with MTK SDK. However, as the
modem is provided by carriers, so the web interface is highly minimized and
only contains a static page with no interaction options.
There are two possible ways to gain the access.
1) Open the shell and use a UART2USB convert to gain TTY access. Please
notice you have to remove resistance R54 at the back of the board
otherwise you won't be able to input anything.
2) Use built-in backdoor. Access http://192.168.1.1/cgi-bin/_/testxst to
start dropbear service at port 9122. Be warned the software is super
old and only diffie-hellman-group1-sha1, diffie-hellman-group14-sha1,
kexguess2@matt.ucc.asn.au is support, you may not be able to connect it
with an up-to-date ssh client.
After you can control the device, flash the firmware as usual. Here are
some hints for that.
Option 1 (via original firmware):
1) Setup HTTP server on your computer, for example:
python3 -m http.server
2) Connect to the route and flash:
cd /tmp
wget http://<your-computer-host>/<your-firmware-name>
mtd -r write <your-firmware-name> firmware
Option 2 (replacing u-boot via breed):
1) Download breed-mt7620-reset13.bin from https://breed.hackpascal.net/
2) Setup HTTP server on your computer, for example:
python3 -m http.server
You can skip this step if your breed is already accessible from HTTP,
since the original wget does not support HTTPS.
3) Connect to the route and flash breed:
cd /tmp
wget http://<your-computer-host>/breed-mt7620-reset13.bin
mtd write breed-mt7620-reset13.bin Bootloader
4) Reboot. Hold reset key or press any key in TTY to enter breed.
5) Access breed web interface (http://192.168.1.1/). Choose the flash
layout to be 0x50000 and flash new firmware.
MAC addresses:
-------------
There are three MACs stored in factory, as in MT7620A reference design:
source address usage
0x4 label WLAN
0x28 label MAC 1
0x2e label + 1 MAC 2
However, the OEM firmware only uses one single MAC (label) for all
interfaces, probably a misconfiguration.
Signed-off-by: David Yang <mmyangfl@gmail.com>
2021-06-06 16:42:49 +02:00
|
|
|
netcore,nw5212|\
|
|
|
|
netgear,jwnr2010-v5)
|
|
|
|
ucidef_set_led_switch "lan1" "lan1" "green:lan1" "switch0" "0x08"
|
|
|
|
ucidef_set_led_switch "lan2" "lan2" "green:lan2" "switch0" "0x04"
|
|
|
|
ucidef_set_led_switch "lan3" "lan3" "green:lan3" "switch0" "0x02"
|
|
|
|
ucidef_set_led_switch "lan4" "lan4" "green:lan4" "switch0" "0x01"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x10"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
netgear,ex2700|\
|
ramips: add support for Netgear WN3100RPv2
This patch adds support for the Netgear WN3100RPv2
http://www.netgear.com/support/product/wn3100rpv2.aspx
Specifications:
- SoC: MediaTek MT7620A (580MHz, ramips)
- RAM: 32MB DDR
- Storage: 8MB NOR SPI flash
- Wireless: builtin MT7620A, 2x2:2 with u.FL connectors
- Ethernet: 1x100M
- Stock firmware based on OpenWRT Kamikaze
Like the EX2700, the bootloader expects a secondary image signature,
see https://forum.openwrt.org/viewtopic.php?pid=312577#p312577
This device seems to be same hardware as a WN3000RPv3
Flash instructions:
- Use the Netgear WebUI to upgrade to OpenWRT using the factory image
(see note below),
- Use the sysupgrade image for upgrading versions from OpenWRT,
- TFTP recovery procedure can be used to flash the factory image
(preferred method).
Note:
- The WebUI may not reboot automatically, wait at least 5 minutes before
powercycling the device
Flashing using TFTP:
- Set you IP address to 192.168.1.10/24 (no gateway)
- Connect your machine to the Ethernet port
- Power off the device and wait for 10 seconds,
- Hold the reset button and power on the device (do not release reset),
- Hold the reset button until the green light is flashing (Approx. 15s)
- launch tftp, set mode to binary and connect to 192.168.1.1
- put the factory firmware image
- All leds will switch off (like a power off), this is normal
- Wait for the device to reboot in the new OpenWRT image (max 5 mins)
- The first boot will take longer than usual.
- After boot, the Device IP on the ethernet port is 192.168.1.1
Signed-off-by: Rodolphe de Saint Léger <rdesaintleger@gmail.com>
[drop unneeded includes in dts, wrap commit message]
Signed-off-by: Sungbo Eo <mans0n@gorani.run>
2022-03-16 10:19:30 +01:00
|
|
|
netgear,wn3000rp-v3|\
|
|
|
|
netgear,wn3100rp-v2)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:router" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2019-07-29 20:23:28 +02:00
|
|
|
netgear,ex3700|\
|
|
|
|
netgear,ex6130)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "wlan5g" "ROUTER (green)" "green:router" "wlan0"
|
|
|
|
ucidef_set_led_netdev "wlan2g" "DEVICE (green)" "green:device" "wlan1"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
ramips: add support for Netgear PR2000
This patch adds support for Netgear PR2000, sold as "Travel Router and
Range Extender".
Specifications:
--------------
* SoC: Mediatek MT7620N
* RAM: 64MB DDR2
* Flash: 16MB SPI NOR flash (Macronix MX25L12805D)
* WiFi 2.4GHz: builtin
* Ethernet: builtin
* LED: Power, Internet, WiFi, USB
* Buttons: Reset (GPIO 1/2)
* UART: Serial console (57600 8n1)
* USB: 1 x USB2
SPECIAL NOTES:
-------------
Problem: WiFi is super weak, but SSID beacons seems to be right.
Solve: Change 36h in factory partition (namely 0xf60036) to be 0x0.
Explain: Clearly Netgear have different ideas on how EEPROM is used. Bit 2
of 36h indicates the presence of External LNA for 11g (2.4 GHz) band,
which seems to be incorrectly set by Netgear (originally 0x04). Lifting it
solves the problem of weak RX signal.
Installation:
------------
There are two possible ways to install the firmware. Flashing via web
interface of original firmware is not tested due to a broken firmware.
1) Open the shell and use a UART2USB convert to gain TTY access (TP7: RXD,
TP9: TXD, TP10: GND). Please notice you have to remove resistance R54
next to TP7 otherwise you won't be able to input anything.
2) Use well-known Netgear debug switch. Access
http://192.168.168.1/setup.cgi?todo=debug to start telnet service
(username: root, password: <none>).
Please back up firmware if you want to go back to the original.
After you can control the device, flash the firmware as usual. Here are
some hints for that.
Option 1 (via nmrpflash):
1) Download nmrpflash from https://github.com/jclehner/nmrpflash
2) Use *-factory.img and flash:
nmrpflash -L
nmrpflash -i net* -f <your-firmware-name>
3) Turn off then turn on the device, wait it finishing flash.
Option 2 (replacing u-boot via breed):
1) Download breed-mt7620-reset1.bin from https://breed.hackpascal.net/
2) Setup HTTP server on your computer, for example:
python3 -m http.server
You can skip this step if your breed is already accessible from HTTP,
since the original wget does not support HTTPS.
3) Connect to the route and flash breed:
cd /tmp
wget http://<your-computer-host>/breed-mt7620-reset1.bin
dd if=breed-mt7620-reset1.bin of=/dev/mtdblock0 bs=64k
4) Reboot. Hold reset key or press any key in TTY to enter breed.
5) Access breed web interface (http://192.168.1.1/). Choose memory layout
to be 0x40000 and flash new firmware.
Remark:
------
As a "Range Extender", it has a switch to switch between Wired mode (GPIO
21 low) and Wireless mode (GPIO 20 low), which is not implemented in this
patch. However, the router will be turned off when it switches to the
middle, which makes this switch much less useful.
MAC addresses:
-------------
The OEM firmware uses one single MAC for all interfaces, located at
0xf700b0.
Signed-off-by: David Yang <mmyangfl@gmail.com>
2021-06-08 18:53:27 +02:00
|
|
|
netgear,pr2000)
|
|
|
|
ucidef_set_led_switch "internet" "internet" "green:internet" "switch0" "0x01"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
phicomm,psg1208)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "white:wlan2g" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
planex,mzk-ex750np|\
|
|
|
|
zbtlink,zbt-we826-e)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "red:wifi" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2020-09-11 18:01:19 +02:00
|
|
|
ravpower,rp-wd03)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "internet" "internet" "green:wifi" "eth0"
|
2020-09-11 18:01:19 +02:00
|
|
|
;;
|
2023-11-12 08:58:26 +01:00
|
|
|
rostelecom,rt-fl-1|\
|
|
|
|
rostelecom,s1010)
|
|
|
|
ucidef_set_led_switch "lan-1" "lan-1" "green:lan-1" "switch0" "0x02"
|
|
|
|
ucidef_set_led_switch "lan-2" "lan-2" "green:lan-2" "switch0" "0x04"
|
|
|
|
ucidef_set_led_switch "lan-3" "lan-3" "green:lan-3" "switch0" "0x08"
|
|
|
|
ucidef_set_led_switch "lan-4" "lan-4" "green:lan-4" "switch0" "0x10"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x01"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
tplink,archer-c2-v1)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch1" "0x1e"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch1" "0x01"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2020-09-27 19:40:51 +02:00
|
|
|
tplink,archer-c20-v1|\
|
2019-10-22 12:37:13 +02:00
|
|
|
tplink,archer-c20i)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "lan" "lan" "blue:lan" "switch0" "0x1e"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "blue:wan" "switch0" "0x01"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2024-02-23 20:53:37 +01:00
|
|
|
tplink,archer-c5-v4)
|
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch1" "0x0f"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch1" "0x10"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
tplink,archer-c50-v1)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch0" "0x1e"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x01"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
tplink,archer-mr200)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "lan" "lan" "white:lan" "eth0.1"
|
|
|
|
ucidef_set_led_netdev "wan" "wan" "white:wan" "usb0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2024-04-12 16:44:23 +02:00
|
|
|
tplink,ec220-g5-v2)
|
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch1" "0x17"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "orange:wan" "switch1" "0x08"
|
|
|
|
;;
|
ramips: add support for TP-Link RE200 v1
TP-Link RE200 v1 is a wireless range extender with Ethernet and 2.4G and 5G
WiFi with internal antennas. It's based on MediaTek MT7620A+MT7610EN.
Specifications
--------------
- MediaTek MT7620A (580 Mhz)
- 64 MB of RAM
- 8 MB of FLASH
- 2T2R 2.4 GHz and 1T1R 5 GHz
- 1x 10/100 Mbps Ethernet
- UART header on PCB (57600 8n1)
- 8x LED (GPIO-controlled; only 6 supported), 2x button
There are 2.4G and 5G LEDs in red and green which are controlled
separately. The 5G LED is currently not supported, since the GPIOs couldn't
be determined.
Installation
------------
Web Interface
-------------
It is possible to upgrade to OpenWrt via the web interface. However, the
OEM firmware upgrade file is required and a tool to fix the MD5 sum of
the header. This procedure overwrites U-Boot and there is not failsafe /
recovery mode present! To prepare an image, you need to take the header
and U-Boot (i.e. 0x200 + 0x20000 bytes) from an OEM firmware file and
attach the factory image to it. Then fix the header MD5Sum1.
Serial console
--------------
Opening the case is quite hard, since it is welded together. Rename the
OpenWrt factory image to "test.bin", then plug in the device and quickly
press "2" to enter flash mode (no line feed). Follow the prompts until
OpenWrt is installed.
Unfortunately, this devices does not offer a recovery mode or a tftp
installation method. If the web interface upgrade fails, you have to open
your device and attach serial console. Since the web upgrade overwrites
the boot loader, you might also brick your device.
Additional notes
----------------
MAC address assignment is based on stock-firmware. For me, the device
assigns the MAC on the label to Ethernet and the 2.4G WiFi, while the 5G
WiFi has a separate MAC with +2.
*:88 Ethernet/2.4G label, uboot 0x1fc00, userconfig 0x0158
*:89 unused userconfig 0x0160
*:8A 5G not present in flash
This seems to be the first ramips device with a TP-Link v1 header. The
original firmware has the string "EU" embedded, there might be some region-
checking going on during the firmware upgrade process. The original
firmware also contains U-Boot and thus overwrites the boot loader during
upgrade.
In order to flash back to stock, the first header and U-Boot need to be
stripped from the original firmware.
Signed-off-by: Andreas Böhler <dev@aboehler.at>
2019-12-19 10:29:14 +01:00
|
|
|
tplink,re200-v1)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "lan" "lan" "green:lan" "eth0"
|
ramips: add support for TP-Link RE200 v1
TP-Link RE200 v1 is a wireless range extender with Ethernet and 2.4G and 5G
WiFi with internal antennas. It's based on MediaTek MT7620A+MT7610EN.
Specifications
--------------
- MediaTek MT7620A (580 Mhz)
- 64 MB of RAM
- 8 MB of FLASH
- 2T2R 2.4 GHz and 1T1R 5 GHz
- 1x 10/100 Mbps Ethernet
- UART header on PCB (57600 8n1)
- 8x LED (GPIO-controlled; only 6 supported), 2x button
There are 2.4G and 5G LEDs in red and green which are controlled
separately. The 5G LED is currently not supported, since the GPIOs couldn't
be determined.
Installation
------------
Web Interface
-------------
It is possible to upgrade to OpenWrt via the web interface. However, the
OEM firmware upgrade file is required and a tool to fix the MD5 sum of
the header. This procedure overwrites U-Boot and there is not failsafe /
recovery mode present! To prepare an image, you need to take the header
and U-Boot (i.e. 0x200 + 0x20000 bytes) from an OEM firmware file and
attach the factory image to it. Then fix the header MD5Sum1.
Serial console
--------------
Opening the case is quite hard, since it is welded together. Rename the
OpenWrt factory image to "test.bin", then plug in the device and quickly
press "2" to enter flash mode (no line feed). Follow the prompts until
OpenWrt is installed.
Unfortunately, this devices does not offer a recovery mode or a tftp
installation method. If the web interface upgrade fails, you have to open
your device and attach serial console. Since the web upgrade overwrites
the boot loader, you might also brick your device.
Additional notes
----------------
MAC address assignment is based on stock-firmware. For me, the device
assigns the MAC on the label to Ethernet and the 2.4G WiFi, while the 5G
WiFi has a separate MAC with +2.
*:88 Ethernet/2.4G label, uboot 0x1fc00, userconfig 0x0158
*:89 unused userconfig 0x0160
*:8A 5G not present in flash
This seems to be the first ramips device with a TP-Link v1 header. The
original firmware has the string "EU" embedded, there might be some region-
checking going on during the firmware upgrade process. The original
firmware also contains U-Boot and thus overwrites the boot loader during
upgrade.
In order to flash back to stock, the first header and U-Boot need to be
stripped from the original firmware.
Signed-off-by: Andreas Böhler <dev@aboehler.at>
2019-12-19 10:29:14 +01:00
|
|
|
;;
|
ramips: add support for Wavlink WL-WN535K1
The Wavlink WL-WN535K1 is a "mesh" router with 2 gigabit ethernet ports
and one fast ethernet port. Mine is branded as Talius TAL-WMESH1.
It can be found in kits of 2 or 3 (WL-WN535K2 or WL-WN535K3).
The motherboard is labelled as WS-WN535G3-B-V1.2 so this image could
potentially work for WL-WN535G3R and WS-WN535G3R with little to none
effort, but it's untested.
Hardware
--------
SoC: Mediatek MT7620A
RAM: 64MB
FLASH: 8MB NOR (GigaDevice GD25Q64CS)
ETH:
- 2x 10/100/1000 Mbps Ethernet (RTL8211F)
- 1x 10/100 Mbps Ethernet (integrated in SOC)
WIFI:
- 2.4GHz: 1x (integrated in SOC) (2x2:2)
- 5GHz: 1x MT7612E (2x2:2)
- 4 internal antennas
BTN:
- 1x Reset button
- 1x Touchlink button (set to WPS)
- 1x ON/OFF switch
LEDS:
- 1x Red led (system status)
- 1x Blue led (system status)
- 3x Green leds (ethernet port status/act)
UART:
- 57600-8-N-1
Everything works correctly.
Currently there is no firmware update available. Because of this, in
order to restore the OEM firmware, you must firstly dump the OEM
firmware from your router before you flash the OpenWrt image.
Backup the OEM Firmware
-----------------------
The following steps are to be intended for users having little to none
experience in linux. Obviously there are many ways to backup the OEM
firmware, but probably this is the easiest way for this router.
Procedure tested on WN535K1_V1510_200916 firmware version.
1) Go to http://192.168.10.1/webcmd.shtml
2) Type the following line in the "Command" input box and then press enter:
mkdir /etc_ro/lighttpd/www/dev; dd if=/dev/mtd0ro of=/etc_ro/lighttpd/www/dev/mtd0ro
3) After few seconds in the textarea should appear this output:
16384+0 records in
16384+0 records out
If your output doesn't match mine, stop reading and ask for
help in the forum.
4) Open in another tab http://192.168.10.1/dev/mtd0ro to download the
content of the whole NOR. If the file size is 0 byte, stop reading
and ask for help in the forum.
5) Come back to the http://192.168.10.1/webcmd.shtml webpage and type:
rm /etc_ro/lighttpd/www/dev/mtd0ro;for i in 1 2 3 4 5; do dd if=/dev/mtd${i}ro of=/etc_ro/lighttpd/www/dev/mtd${i}ro; done
6) After few seconds, in the textarea should appear this output:
384+0 records in
384+0 records out
128+0 records in
128+0 records out
128+0 records in
128+0 records out
14720+0 records in
14720+0 records out
1024+0 records in
1024+0 records out
If your output doesn't match mine, stop reading and ask for
help in the forum.
7) Open the following links to download the partitions of the OEM FW:
http://192.168.10.1/dev/mtd1ro
http://192.168.10.1/dev/mtd2ro
http://192.168.10.1/dev/mtd3ro
http://192.168.10.1/dev/mtd4ro
http://192.168.10.1/dev/mtd5ro
If one (or more) of these files are 0 byte, stop reading and ask
for help in the forum.
8) Store these downloaded files in a safe place.
9) Reboot your router to remove any temporary file in ram.
Installation
------------
Flash the initramfs image in the OEM firmware interface
(http://192.168.10.1/update_mesh.shtml).
When Openwrt boots, flash the sysupgrade image otherwise you won't be
able to keep configuration between reboots.
Restore OEM Firmware
--------------------
Flash the "mtd4ro" file you previously backed-up directly from LUCI.
Warning: Remember to not keep settings!
Warning2: Remember to force the flash.
Notes
-----
1) Router mac addresses:
LAN XX:XX:XX:XX:XX:E2 (factory @ 0x28)
WAN XX:XX:XX:XX:XX:E3 (factory @ 0x2e)
WIFI 2G XX:XX:XX:XX:XX:E4 (factory @ 0x04)
WIFI 5G XX:XX:XX:XX:XX:E5 (factory @ 0x8004)
LABEL XX:XX:XX:XX:XX:E5
2) The OEM firmware upgrade page accepts only files containing the
string "WN535K1" in the filename.
3) Additional notes 1,2,3 in the WS-WN583A6 commit are still valid
(https://github.com/openwrt/openwrt/commit/92780d80ab6f5f03fac2407c06eb267dd83914a1)
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
[remove trailing whitespace]
Signed-off-by: Sungbo Eo <mans0n@gorani.run>
2021-12-04 04:15:30 +01:00
|
|
|
wavlink,wl-wn535k1)
|
2023-06-21 21:53:07 +02:00
|
|
|
ucidef_set_led_switch "lan1" "lan1" "green:lan1" "switch0" "0x20"
|
|
|
|
ucidef_set_led_switch "lan2" "lan2" "green:lan2" "switch0" "0x04"
|
ramips: add support for Wavlink WL-WN535K1
The Wavlink WL-WN535K1 is a "mesh" router with 2 gigabit ethernet ports
and one fast ethernet port. Mine is branded as Talius TAL-WMESH1.
It can be found in kits of 2 or 3 (WL-WN535K2 or WL-WN535K3).
The motherboard is labelled as WS-WN535G3-B-V1.2 so this image could
potentially work for WL-WN535G3R and WS-WN535G3R with little to none
effort, but it's untested.
Hardware
--------
SoC: Mediatek MT7620A
RAM: 64MB
FLASH: 8MB NOR (GigaDevice GD25Q64CS)
ETH:
- 2x 10/100/1000 Mbps Ethernet (RTL8211F)
- 1x 10/100 Mbps Ethernet (integrated in SOC)
WIFI:
- 2.4GHz: 1x (integrated in SOC) (2x2:2)
- 5GHz: 1x MT7612E (2x2:2)
- 4 internal antennas
BTN:
- 1x Reset button
- 1x Touchlink button (set to WPS)
- 1x ON/OFF switch
LEDS:
- 1x Red led (system status)
- 1x Blue led (system status)
- 3x Green leds (ethernet port status/act)
UART:
- 57600-8-N-1
Everything works correctly.
Currently there is no firmware update available. Because of this, in
order to restore the OEM firmware, you must firstly dump the OEM
firmware from your router before you flash the OpenWrt image.
Backup the OEM Firmware
-----------------------
The following steps are to be intended for users having little to none
experience in linux. Obviously there are many ways to backup the OEM
firmware, but probably this is the easiest way for this router.
Procedure tested on WN535K1_V1510_200916 firmware version.
1) Go to http://192.168.10.1/webcmd.shtml
2) Type the following line in the "Command" input box and then press enter:
mkdir /etc_ro/lighttpd/www/dev; dd if=/dev/mtd0ro of=/etc_ro/lighttpd/www/dev/mtd0ro
3) After few seconds in the textarea should appear this output:
16384+0 records in
16384+0 records out
If your output doesn't match mine, stop reading and ask for
help in the forum.
4) Open in another tab http://192.168.10.1/dev/mtd0ro to download the
content of the whole NOR. If the file size is 0 byte, stop reading
and ask for help in the forum.
5) Come back to the http://192.168.10.1/webcmd.shtml webpage and type:
rm /etc_ro/lighttpd/www/dev/mtd0ro;for i in 1 2 3 4 5; do dd if=/dev/mtd${i}ro of=/etc_ro/lighttpd/www/dev/mtd${i}ro; done
6) After few seconds, in the textarea should appear this output:
384+0 records in
384+0 records out
128+0 records in
128+0 records out
128+0 records in
128+0 records out
14720+0 records in
14720+0 records out
1024+0 records in
1024+0 records out
If your output doesn't match mine, stop reading and ask for
help in the forum.
7) Open the following links to download the partitions of the OEM FW:
http://192.168.10.1/dev/mtd1ro
http://192.168.10.1/dev/mtd2ro
http://192.168.10.1/dev/mtd3ro
http://192.168.10.1/dev/mtd4ro
http://192.168.10.1/dev/mtd5ro
If one (or more) of these files are 0 byte, stop reading and ask
for help in the forum.
8) Store these downloaded files in a safe place.
9) Reboot your router to remove any temporary file in ram.
Installation
------------
Flash the initramfs image in the OEM firmware interface
(http://192.168.10.1/update_mesh.shtml).
When Openwrt boots, flash the sysupgrade image otherwise you won't be
able to keep configuration between reboots.
Restore OEM Firmware
--------------------
Flash the "mtd4ro" file you previously backed-up directly from LUCI.
Warning: Remember to not keep settings!
Warning2: Remember to force the flash.
Notes
-----
1) Router mac addresses:
LAN XX:XX:XX:XX:XX:E2 (factory @ 0x28)
WAN XX:XX:XX:XX:XX:E3 (factory @ 0x2e)
WIFI 2G XX:XX:XX:XX:XX:E4 (factory @ 0x04)
WIFI 5G XX:XX:XX:XX:XX:E5 (factory @ 0x8004)
LABEL XX:XX:XX:XX:XX:E5
2) The OEM firmware upgrade page accepts only files containing the
string "WN535K1" in the filename.
3) Additional notes 1,2,3 in the WS-WN583A6 commit are still valid
(https://github.com/openwrt/openwrt/commit/92780d80ab6f5f03fac2407c06eb267dd83914a1)
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
[remove trailing whitespace]
Signed-off-by: Sungbo Eo <mans0n@gorani.run>
2021-12-04 04:15:30 +01:00
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x10"
|
|
|
|
;;
|
ramips: add support for the Wavlink WL-WN579X3
About the device
----------------
SoC: MediaTek MT7620a @ 580MHz
RAM: 64M
FLASH: 8MB
WiFi: SoC-integrated: MediaTek MT7620a bgn
WiFi: MediaTek MT7612EN nac
GbE: 2x (RTL8211F)
BTN: - WPS
- Reset
- Router/Repeater/AP (3-way slide-switch)
LED: - WPS (blue)
- 3-segment Wifi signal representation (blue)
- WiFi (blue)
- WAN (blue)
- LAN (blue)
- Power (blue)
UART: UART is present as Pads with through-holes on the PCB. They are
located next to the reset button and are labelled Vcc/TX/RX/GND as
appropriate. Use 3.3V, 57600-8N1.
Installation
------------
Using the webcmd interface
--------------------------
Warning: Do not update to the latest Wavlink firmware (version
20201201) as this removes the webcmd console and you will need to
use the serial port instead.
You will need to have built uboot/sqauashfs image for this device,
and you will need to provide an HTTP service where the image can
be downloaded from that is accessible by the device.
You cannot use the device manufacturers firmware upgrade interface
as it rejects the OpenWrt image.
1. Log into the device's admin portal. This is necessary to
authenticate you as a user in order to be able to access the
webcmd interface.
2. Navigate to http://<device-ip>/webcmd.shtml - you can access
the console directly through this page, or you may wish to
launch the installed `telnetd` and use telnet instead.
* Using telnet is recommended since it provides a more
convenient shell interface that the web form.
* Launch telnetd from the form with the command `telnetd`.
* Check the port that telnetd is running on using
`netstat -antp|grep telnetd`, it is likely to be 2323.
* Connect to the target using `telnet`. The username should
be `admin2860`, and the password is your admin password.
3. On the target use `curl` to download the image.
e.g. `curl -L -O http://<some-other-lan-ip>/openwrt-ramips-mt7620-\
wavlink_wl-wn579x3-squashfs-sysupgrade.bin`.
Check the hash using `md5sum`.
4. Use the mtd_write command to flash the image.
* The flash partition should be mtd4, but check
/sys/class/mtd/mtd4/name first. The partition should be
called 'Kernel'.
* To flash use the following command:
`mtd_write -r -e /dev/mtd<n> write <image-file> /dev/mtd<n>`
Where mtd<n> is the Kernel partition, and <image-file> is
the OpenWrt image previously downloaded.
* The command above will erase, flash and then reboot the
device. Once it reboots it will be running OpenWrt.
Connect via ssh to the device at 192.168.1.1 on the LAN port.
The WAN port will be configured via DHCP.
Using the serial port
---------------------
The device uses uboot like many other MT7260a based boards. To
use this interface, you will need to connect to the serial
interface, and provide a TFTP server. At boot follow the
bootloader menu and select option 2 to erase/flash the image.
Provide the address and filename details for the tftp server.
The bootloader will do the rest.
Once the image is flashed, the board will boot into OpenWrt. The
console is available over the serial port.
Signed-off-by: Ben Gainey <ba.gainey@googlemail.com>
2021-01-31 12:15:38 +01:00
|
|
|
wavlink,wl-wn579x3)
|
|
|
|
ucidef_set_led_switch "lan" "lan" "blue:lan" "switch0" "0x20"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "blue:wan" "switch0" "0x10"
|
|
|
|
;;
|
2021-07-11 17:17:43 +02:00
|
|
|
xiaomi,miwifi-mini)
|
|
|
|
ucidef_set_led_switch "lan1" "lan1" "green:lan1" "switch0" "0x02"
|
|
|
|
ucidef_set_led_switch "lan2" "lan2" "green:lan2" "switch0" "0x01"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x10"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
zbtlink,zbt-ape522ii)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "wlan2g4" "wlan1-link" "green:wlan2g4" "wlan1"
|
|
|
|
ucidef_set_led_netdev "sys1" "wlan1" "green:sys1" "wlan1" "tx rx"
|
|
|
|
ucidef_set_led_netdev "sys2" "wlan0" "green:sys2" "wlan0" "tx rx"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
zbtlink,zbt-wa05)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "blue:air" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
zbtlink,zbt-we1026-5g-16m)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_netdev "lan" "LAN" "green:lan" "eth0"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wifi" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
2019-11-02 15:18:55 +01:00
|
|
|
zbtlink,zbt-we1026-h-32m)
|
2020-09-27 19:40:51 +02:00
|
|
|
ucidef_set_led_switch "lan" "lan" "green:lan" "switch0" "0x8"
|
|
|
|
ucidef_set_led_switch "wan" "wan" "green:wan" "switch0" "0x10"
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wifi" "wlan0"
|
2019-11-02 15:18:55 +01:00
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
zbtlink,zbt-we2026)
|
2020-09-27 23:35:11 +02:00
|
|
|
ucidef_set_led_netdev "wifi_led" "wifi" "green:wlan" "wlan0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
esac
|
|
|
|
|
|
|
|
board_config_flush
|
|
|
|
|
|
|
|
exit 0
|