2009-10-23 18:51:51 +02:00
|
|
|
#!/bin/sh
|
2011-12-01 23:48:35 +01:00
|
|
|
|
2012-12-19 17:07:50 +01:00
|
|
|
. /lib/functions.sh
|
2015-12-11 16:26:06 +01:00
|
|
|
. /lib/functions/uci-defaults.sh
|
2014-07-23 09:49:50 +02:00
|
|
|
. /lib/functions/system.sh
|
2011-12-01 23:48:35 +01:00
|
|
|
|
2012-08-29 12:37:38 +02:00
|
|
|
ramips_setup_rt3x5x_vlans()
|
|
|
|
|
{
|
|
|
|
|
if [ ! -x /sbin/swconfig ]; then
|
|
|
|
|
# legacy default
|
|
|
|
|
ucidef_set_interfaces_lan_wan "eth0.1" "eth0.2"
|
|
|
|
|
return
|
|
|
|
|
fi
|
|
|
|
|
local wanports=""
|
|
|
|
|
local lanports=""
|
|
|
|
|
for port in 5 4 3 2 1 0; do
|
|
|
|
|
if [ `swconfig dev rt305x port $port get disable` = "1" ]; then
|
|
|
|
|
continue
|
|
|
|
|
fi
|
|
|
|
|
if [ `swconfig dev rt305x port $port get lan` = "0" ]; then
|
2015-12-03 16:46:29 +01:00
|
|
|
wanports="$port:wan $wanports"
|
2012-08-29 12:37:38 +02:00
|
|
|
else
|
2015-12-03 16:46:29 +01:00
|
|
|
lanports="$port:lan $lanports"
|
2012-08-29 12:37:38 +02:00
|
|
|
fi
|
|
|
|
|
done
|
2016-10-12 19:04:08 +02:00
|
|
|
ucidef_add_switch "rt305x" $lanports $wanports "6t@eth0"
|
2012-08-29 12:37:38 +02:00
|
|
|
}
|
|
|
|
|
|
2011-12-01 23:48:43 +01:00
|
|
|
ramips_setup_interfaces()
|
|
|
|
|
{
|
|
|
|
|
local board="$1"
|
2011-12-01 23:48:35 +01:00
|
|
|
|
2011-12-01 23:48:43 +01:00
|
|
|
case $board in
|
2016-12-23 08:21:31 +01:00
|
|
|
11acnas|\
|
2017-03-18 17:11:14 +01:00
|
|
|
w2914nsv2|\
|
|
|
|
|
zbt-we2026)
|
2016-12-23 08:21:31 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "4:wan:5" "6@eth0"
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
3g150b|\
|
|
|
|
|
3g300m|\
|
2016-05-04 21:22:19 +02:00
|
|
|
a5-v11|\
|
2017-04-08 00:34:48 +02:00
|
|
|
all0256n-4M|\
|
|
|
|
|
all0256n-8M|\
|
2015-08-17 08:02:59 +02:00
|
|
|
all5002|\
|
|
|
|
|
all5003|\
|
2018-02-22 17:58:23 +01:00
|
|
|
bocco|\
|
2015-08-17 08:02:59 +02:00
|
|
|
broadway|\
|
|
|
|
|
dcs-930|\
|
|
|
|
|
dcs-930l-b1|\
|
|
|
|
|
ht-tm02|\
|
2018-07-04 03:29:36 +02:00
|
|
|
kimax,u35wf|\
|
2015-10-19 12:07:38 +02:00
|
|
|
linkits7688 | \
|
2016-05-04 21:21:41 +02:00
|
|
|
m2m|\
|
2015-08-17 08:02:59 +02:00
|
|
|
microwrt|\
|
2018-06-25 22:51:43 +02:00
|
|
|
mikrotik,rbm11g|\
|
2016-05-19 07:37:58 +02:00
|
|
|
mpr-a2|\
|
2015-08-17 08:02:59 +02:00
|
|
|
ncs601w|\
|
2017-01-09 20:59:56 +01:00
|
|
|
omega2 | \
|
|
|
|
|
omega2p | \
|
2016-08-10 02:18:32 +02:00
|
|
|
timecloud|\
|
2018-06-27 01:24:39 +02:00
|
|
|
tplink,tl-wa801nd-v5|\
|
2015-08-17 08:02:59 +02:00
|
|
|
w150m|\
|
2018-01-17 08:14:41 +01:00
|
|
|
widora,neo-16m|\
|
2018-01-08 06:27:28 +01:00
|
|
|
widora,neo-32m|\
|
2015-08-17 08:02:59 +02:00
|
|
|
wnce2001|\
|
2016-09-25 21:09:31 +02:00
|
|
|
zbt-cpe102|\
|
2018-04-04 01:19:22 +02:00
|
|
|
zorlik,zl5900v2|\
|
2015-08-17 08:02:59 +02:00
|
|
|
zte-q7)
|
2015-12-03 18:30:08 +01:00
|
|
|
ucidef_add_switch "switch0"
|
2016-05-04 21:21:41 +02:00
|
|
|
ucidef_add_switch_attr "switch0" "enable" "false"
|
2012-08-29 12:37:47 +02:00
|
|
|
ucidef_set_interface_lan "eth0"
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
mlw221|\
|
2015-05-23 17:27:05 +02:00
|
|
|
mr-102n)
|
2015-01-08 21:25:55 +01:00
|
|
|
ucidef_set_interface_lan "eth0.2"
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
3g-6200n|\
|
|
|
|
|
ai-br100|\
|
2017-10-14 10:44:39 +02:00
|
|
|
alfa-network,ac1200rm|\
|
2018-02-22 17:08:14 +01:00
|
|
|
mediatek,ap-mt7621a-v60|\
|
2017-02-04 21:28:52 +01:00
|
|
|
d240|\
|
2015-09-14 22:08:55 +02:00
|
|
|
db-wrt01|\
|
2015-08-17 08:02:59 +02:00
|
|
|
dir-300-b7|\
|
|
|
|
|
dir-320-b1|\
|
|
|
|
|
dir-610-a1|\
|
|
|
|
|
dir-615-h1|\
|
2018-08-23 15:04:31 +02:00
|
|
|
dir-810l|\
|
2018-01-20 09:27:03 +01:00
|
|
|
dlink,dwr-116-a1|\
|
2018-03-10 10:34:38 +01:00
|
|
|
dlink,dwr-921-c1|\
|
2017-02-27 21:59:50 +01:00
|
|
|
ew1200|\
|
2015-08-17 08:02:59 +02:00
|
|
|
firewrt|\
|
2017-02-25 00:19:15 +01:00
|
|
|
hc5661a|\
|
2017-02-22 13:47:22 +01:00
|
|
|
hc5962|\
|
2015-08-17 08:02:59 +02:00
|
|
|
hlk-rm04|\
|
2017-07-18 07:02:51 +02:00
|
|
|
k2p|\
|
2017-04-27 20:02:05 +02:00
|
|
|
kn|\
|
2017-04-22 22:46:23 +02:00
|
|
|
kn_rc|\
|
2016-09-09 00:57:31 +02:00
|
|
|
mac1200rv2|\
|
2015-08-17 08:02:59 +02:00
|
|
|
miwifi-mini|\
|
2016-03-16 10:26:48 +01:00
|
|
|
miwifi-nano|\
|
2015-08-17 08:02:59 +02:00
|
|
|
mt7621|\
|
|
|
|
|
mt7628|\
|
|
|
|
|
mzk-750dhp|\
|
|
|
|
|
mzk-w300nh2|\
|
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 04:51:33 +01:00
|
|
|
d-team,newifi-d2|\
|
2018-06-12 21:17:23 +02:00
|
|
|
netgear,r6120|\
|
2017-04-08 00:34:48 +02:00
|
|
|
nixcore-x1-8M|\
|
|
|
|
|
nixcore-x1-16M|\
|
2015-08-17 08:02:59 +02:00
|
|
|
oy-0001|\
|
|
|
|
|
pbr-m1|\
|
2016-02-15 19:45:22 +01:00
|
|
|
psg1208|\
|
2017-04-21 02:47:44 +02:00
|
|
|
psg1218a|\
|
2017-03-11 08:44:33 +01:00
|
|
|
r6220|\
|
2017-12-08 20:36:06 +01:00
|
|
|
rt-n12p|\
|
2015-08-17 08:02:59 +02:00
|
|
|
sap-g3200u3|\
|
2016-05-10 18:17:54 +02:00
|
|
|
sk-wb8|\
|
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 16:04:49 +01:00
|
|
|
u7621-06-256M-16M|\
|
2016-10-10 03:24:42 +02:00
|
|
|
vr500|\
|
2015-11-24 19:29:26 +01:00
|
|
|
wf-2881|\
|
2018-03-23 06:59:39 +01:00
|
|
|
whr-g300n|\
|
2018-05-03 17:59:27 +02:00
|
|
|
mqmaker,witi-256m|\
|
|
|
|
|
mqmaker,witi-512m|\
|
2016-11-06 13:00:38 +01:00
|
|
|
wl-wn575a3|\
|
2016-04-26 13:43:53 +02:00
|
|
|
wndr3700v5|\
|
2016-09-09 20:57:58 +02:00
|
|
|
youku-yk1|\
|
|
|
|
|
zbt-ape522ii|\
|
2017-04-20 05:07:26 +02:00
|
|
|
zbt-we1326|\
|
2017-12-01 08:10:24 +01:00
|
|
|
zbtlink,zbt-we3526|\
|
2017-04-12 07:53:56 +02:00
|
|
|
zbt-we826-16M|\
|
|
|
|
|
zbt-we826-32M|\
|
2015-11-24 19:29:02 +01:00
|
|
|
zbt-wg2626|\
|
2017-04-07 23:52:27 +02:00
|
|
|
zbt-wg3526-16M|\
|
2017-04-01 10:46:44 +02:00
|
|
|
zbt-wg3526-32M|\
|
2016-09-09 20:57:58 +02:00
|
|
|
zbt-wr8305rt)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "6@eth0"
|
2015-08-17 08:02:59 +02:00
|
|
|
;;
|
2018-01-26 16:21:34 +01:00
|
|
|
alfa-network,awusfree1|\
|
|
|
|
|
cs-qr10|\
|
|
|
|
|
d105|\
|
|
|
|
|
dlink,dap-1522-a1|\
|
|
|
|
|
dch-m225|\
|
|
|
|
|
ex2700|\
|
|
|
|
|
ex3700|\
|
|
|
|
|
hpm|\
|
|
|
|
|
mzk-ex300np|\
|
|
|
|
|
mzk-ex750np|\
|
|
|
|
|
na930|\
|
|
|
|
|
pbr-d1|\
|
2018-05-23 23:19:47 +02:00
|
|
|
ravpower,wd03|\
|
2018-01-26 16:21:34 +01:00
|
|
|
tama,w06|\
|
2018-08-26 21:11:59 +02:00
|
|
|
tplink,tl-mr3020-v3|\
|
2018-01-26 16:21:34 +01:00
|
|
|
u25awf-h1|\
|
|
|
|
|
wli-tx4-ag300n|\
|
|
|
|
|
wmdr-143n|\
|
|
|
|
|
wmr-300|\
|
|
|
|
|
wn3000rpv3|\
|
|
|
|
|
wrh-300cr)
|
|
|
|
|
ucidef_set_interface_lan "eth0"
|
|
|
|
|
;;
|
2018-04-19 19:34:22 +02:00
|
|
|
dlink,dwr-118-a2)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan:2" "2:lan:1" "3:lan:3" "4:lan" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
2017-08-12 16:56:11 +02:00
|
|
|
mir3g)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
ramips: improve Xiaomi Mi Router 3G support
This commit improves support for the Xiaomi Mi Router 3G originally
added in commit 6e283cdc0da25928f8148805ebef7f8f2b769ee8
Improvements:
- Remove software watchdog as hardware watchdog now working as per
commit 3fbf3ab44f5cebb22e30a4c8681b13341feed6a6 for all mt7621
devices.
- Reset button polarity corrected - length of press determines reboot
(short press) vs. reset to defaults (long press) behaviour.
- Enable GPIO amber switch port LEDs on board rear - lit indicates 1Gbit
link and blink on activity. Green LEDs driven directly by switch
indicating any link speed and tx activity.
- USB port power on/off GPIO exposed as 'usbpower'
- Add access to uboot environment settings for checking/setting uboot
boot order preference from user space.
Changes:
- Front LED indicator is physically made of independent Yellow/Amber,
Red & Blue LEDs combined via a plastic 'lightpipe' to a front panel
indicator, hence the colour behaviour is similar to an RGB LED. RGB
LEDs are not supported at this time because they produce colour results
that do not then match colour labels, e.g. enabling 'mir3g:red' and
'mir3g:blue' would result in a purple indicator and we have no such
label for purple.
The yellow, red & blue LEDs have been split out as individual yellow,
red & blue status LEDs, with yellow being the default status LED as
before and with red's WAN and blue's USB default associations removed.
- Swapped order of vlan interfaces (eth0.1 & eth0.2) to match stock vlan
layout. eth0.1 is LAN, eth0.2 is WAN
- Add 'lwlll' vlan layout to mt7530 switch driver to prevent packet
leakage between kernel switch init and uci swconfig
uboot behaviour & system 'recovery'
uboot expects to find bootable kernels at nand addresses 0x200000 &
0x600000 known by uboot as "system 1" and "system 2" respectively.
uboot chooses which system to hand control to based on 3 environment
variables: flag_last_success, flag_try_sys1_failed & flag_try_sys2_failed
last_success represents a preference for a particular system and is set
to 0 for system 1, set to 1 for system 2. last_success is considered *if*
and only if both try_sys'n'_failed flags are 0 (ie. unset) If *either*
failed flags are set then uboot will attempt to hand control to the
non failed system. If both failed flags are set then uboot will check
the uImage CRC of system 1 and hand control to it if ok. If the uImage
CRC of system is not ok, uboot will hand control to system 2
irrespective of system 2's uImage CRC.
NOTE: uboot only ever sets failed flags, it *never* clears them. uboot
sets a system's failed flag if that system's was selected for boot but
the uImage CRC is incorrect.
Fortunately with serial console access, uboot provides the ability to
boot an initramfs image transferred via tftp, similarly an image may
be flashed to nand however it will flash to *both* kernels so a backup
of stock kernel image is suggested. Note that the suggested install
procedure below set's system 1's failed flag (stock) thus uboot ignores
the last_success preference and boots LEDE located in system 2.
Considerable thought has gone into whether LEDE should replace both
kernels, only one (and which one) etc. LEDE kernels do not include a
minimal rootfs and thus unlike the stock kernel cannot include a
method of controlling uboot environment variables in the event of
rootfs mount failure. Similarly uboot fails to provide an external
mechanism for indicating boot system failure.
Installation - from stock.
Installation through telnet/ssh:
- copy lede-ramips-mt7621-mir3g-squashfs-kernel1.bin and
lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin to usb disk or wget it
from LEDE download site to /tmp
- switch to /extdisks/sda1/ (if copied to USB drive) or to /tmp if
wgetted from LEDE download site
- run: mtd write lede-ramips-mt7621-mir3g-squashfs-kernel1.bin kernel1
- run: mtd write lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin rootfs0
- run: nvram set flag_try_sys1_failed=1
- run: nvram commit
- run: reboot
Recovery - to stock.
Assuming you used the above installation instructions you will have a
stock kernel image in system 1. If it can be booted then it may be used
to perform a stock firmware recovery, thus erasing LEDE completely. From
a 'working' LEDE state (even failsafe)
Failsafe only:
- run: mount_root
- run: sh /etc/uci-defaults/30_uboot-envtools
Then do the steps for 'All'
All:
- run: fw_setenv flag_try_sys2_failed 1
- run: reboot
The board will reboot into system 1 (stock basic kernel) and wait with
system red light slowly blinking for a FAT formatted usb stick with a
recovery image to be inserted. Press and hold the reset button for
around 1 second. Status LED will turn yellow during recovery and blue
when recovery complete.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
2017-09-25 21:41:13 +02:00
|
|
|
"2:lan:2" "3:lan:1" "1:wan" "6t@eth0"
|
2017-08-12 16:56:11 +02:00
|
|
|
;;
|
2017-04-21 02:47:44 +02:00
|
|
|
psg1218b)
|
2017-04-21 00:53:03 +02:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:3" "1:lan:2" "2:lan:1" "3:wan" "6@eth0"
|
|
|
|
|
;;
|
2016-11-14 20:04:36 +01:00
|
|
|
whr-300hp2|\
|
|
|
|
|
whr-600d|\
|
|
|
|
|
wsr-1166|\
|
|
|
|
|
wsr-600)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:1" "1:lan:2" "2:lan:3" "3:lan:4" "4:wan:5" "6@eth0"
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
ar670w|\
|
|
|
|
|
ar725w|\
|
2017-05-05 17:54:26 +02:00
|
|
|
rt-ac51u)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:wan" "1:lan" "2:lan" "3:lan" "4:lan" "6t@eth0"
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
rt-n15|\
|
|
|
|
|
wl-351)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "5@eth0"
|
2015-01-17 15:06:13 +01:00
|
|
|
;;
|
2017-04-08 00:34:48 +02:00
|
|
|
asl26555-8M|\
|
|
|
|
|
asl26555-16M|\
|
2015-11-02 11:17:26 +01:00
|
|
|
rp-n53)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "6t@eth0"
|
2012-01-24 12:48:47 +01:00
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
atp-52b|\
|
2017-04-08 00:34:48 +02:00
|
|
|
awm002-evb-4M|\
|
|
|
|
|
awm002-evb-8M|\
|
2016-07-26 06:44:19 +02:00
|
|
|
c20i|\
|
2015-08-17 08:02:59 +02:00
|
|
|
dir-645|\
|
2016-03-10 20:11:57 +01:00
|
|
|
gl-mt300a|\
|
2016-03-10 20:12:04 +01:00
|
|
|
gl-mt300n|\
|
2016-03-10 20:12:10 +01:00
|
|
|
gl-mt750|\
|
2015-08-17 08:02:59 +02:00
|
|
|
hg255d|\
|
2018-08-09 19:22:46 +02:00
|
|
|
hiwifi,hc5861b|\
|
2016-03-04 09:33:09 +01:00
|
|
|
jhr-n805r|\
|
|
|
|
|
jhr-n825r|\
|
|
|
|
|
jhr-n926r|\
|
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 03:47:23 +02:00
|
|
|
mikrotik,rbm33g|\
|
2016-09-09 20:57:58 +02:00
|
|
|
mzk-wdpr|\
|
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 22:05:32 +02:00
|
|
|
rb750gr3|\
|
2015-08-17 08:02:59 +02:00
|
|
|
rt-n14u|\
|
2018-01-09 12:25:53 +01:00
|
|
|
tplink,c20-v4|\
|
2018-01-28 19:49:38 +01:00
|
|
|
tplink,c50-v3|\
|
2017-12-15 15:57:49 +01:00
|
|
|
tplink,tl-mr3420-v5|\
|
2018-05-30 17:41:53 +02:00
|
|
|
tplink,tl-wr842n-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 14:16:15 +02:00
|
|
|
tl-wr840n-v4|\
|
2017-11-08 14:00:06 +01: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 14:16:15 +02:00
|
|
|
tl-wr841n-v13|\
|
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 21:12:49 +01:00
|
|
|
u7628-01-128M-16M|\
|
ramips: add support for Ubiquiti EdgeRouter X (UBNT-ERX)
This router is based on MT7621 SoC, no wifi, no usb, nand.
Works:
* Boots.
* Ethernet.
* Switch.
* Button (reset).
* Flashing OpenWrt from stock firmware.
* Upgrading OpenWrt.
Doesn't work:
* No GPIO leds. All leds are controlled by switch,
but stock firmware was able to control them.
* SoC has crypto engine but no open driver.
* SoC has nat acceleration, but no open driver.
* This router has 2MB spi flash soldered in but MT
nand/spi drivers do not support pin sharing,
so it is not accessable and disabled. Stock
firmware could read it and it was empty.
* PoE out.
Router has serial pins populated. If looking at the top
of the router, then counting from Eth sockets pins go as:
'GND, RX, TX, GND'. 3.3v, 57600.
U-boot bootloader supports tftpboot, controlled from serial.
This router has two kernel partitions: 'live' and 'backup'.
They are swapped during flashing (on both stock and OpenWrt).
Active partition is controlled by a flag in a factory partition.
U-boot has custom command to switch active kernel partition.
Kernel partitions are 'bare flash' 3MB. Stock bootloader has
no UBI support. Stock rootfs is UBIFS.
Flashing procedure.
Stock firmware uses custom kernel patch to mount squashfs
from a file that is located on UBIFS volume. This makes wiping
out this volume from within stock firmware difficult.
Instead this patch builds image that is flashable by stock firmware
and contains initrams image (with minimal set of packages
to fit into kernel partition). Once this is flashed one can reboot
into initramfs OpenWrt and use sysupgrade to flash OpenWrt including
rootfs into nand.
Note: factory image is only built if initramfs image is enabled.
Signed-off-by: Nikolay Martynov <mar.kolya@gmail.com>
SVN-Revision: 47881
2015-12-12 08:38:06 +01:00
|
|
|
ubnt-erx|\
|
2017-05-29 11:24:49 +02:00
|
|
|
ubnt-erx-sfp|\
|
2015-08-17 08:02:59 +02:00
|
|
|
ur-326n4g|\
|
ramips: Add support for ZTE ZXECS EBG3130 aka BDCOM WAP2100-SK
On the bottom sticker it's branded as ZTE ZXECS EBG3130 device, but in factory
OpenWrt image it's referenced as BDCOM WAP2100-SK device.
Specifications:
- SoC: MediaTek MT7620A
- RAM: 128 MB
- Flash: 16 MB
- Ethernet: 5 FE ports
- Wireless radio: 2T2R 2.4 GHz and 1T1R 5 GHz (MT7610EN, unsupported)
- UART: 1 x UART on PCB marked as J2 (R=RX, T=TX, G=GND) with 115200 8N1 config
- LEDs: Power, FE ports 1-5, WPS, USB, RF 2.4G, RF 5G
- Other: USB port, SD card slot and 2x external antennas (non-detachable)
Flashing instructions:
A) The U-Boot has HTTP based firmware upgrade
A1) Flashing notes
We've identified so far two different batches of units, unfortunately
each batch has different U-Boot bootloader flashed with different
default environment variables, thus each batch has different IP address
for accessing web based firmware updater.
* First batch has web based bootloader IP address 1.1.1.1
* Second batch has web based bootloader IP address 192.168.1.250
In case you can't connect to either of those IPs, you can try to get
the default IP address via two methods:
A1.1) Serial console, then the IP address is visible during the boot
...
HTTP server is starting at IP: 1.1.1.1
raspi_read: from:40004 len:6
HTTP server is ready!
...
A1.2) Over telnet/SSH using this command:
root@bdcom:/# grep ipaddr= /dev/mtd0
ipaddr=1.1.1.1
A2) Flashing with browser
* Change IP address of PC to 1.1.1.2 with 255.255.255.0 netmask
* Reboot the device and try to reach web based bootloader in the
browser with the following URL http://1.1.1.1
* Quickly select the firmware sysupgrade file and click on the
`Update firmware` button, this all has to be done within 10 seconds,
bootloader doesn't wait any longer
If done correctly, the web page should show UPDATE IN PROGRESS page
with progress indicator. Once the flashing completes (it takes roughly
around 1 minute), the device will reboot to the OpenWrt firmware
A3) Flashing with curl
sudo ip addr add 1.1.1.2/24 dev eth0
curl \
--verbose \
--retry 3 \
--retry-delay 1 \
--retry-max-time 30 \
--connect-timeout 30 \
--form "firmware=@openwrt-ramips-mt7620-BDCOM-WAP2100-SK-squashfs-sysupgrade.bin" \
http://1.1.1.1
Now power on the router.
B) The U-boot is based on Ralink SDK so we can flash the firmware using UART.
1. Configure PC with a static IP address and setup an TFTP server.
2. Put the firmware into the tftp directory.
3. Connect the UART line as described on the PCB (G=GND, R=RX, T=TX)
4. Power up the device and press 2, follow the instruction to set device and
tftp server IP address and input the firmware file name. U-boot will then load
the firmware and write it into the flash.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
2018-11-13 13:10:40 +01:00
|
|
|
wap2100-sk|\
|
2015-08-17 08:02:59 +02:00
|
|
|
wrtnode|\
|
2016-01-01 22:19:50 +01:00
|
|
|
wrtnode2p | \
|
|
|
|
|
wrtnode2r | \
|
2018-03-29 12:33:02 +02:00
|
|
|
youhua,wr1200js|\
|
2018-04-08 16:04:11 +02:00
|
|
|
zbt-wa05|\
|
|
|
|
|
zyxel,keenetic-extra-ii)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "6@eth0"
|
2011-12-01 23:48:35 +01:00
|
|
|
;;
|
2018-01-13 08:16:20 +01:00
|
|
|
c50|\
|
|
|
|
|
tplink,c20-v1)
|
2017-07-28 22:36:52 +02:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan:3" "2:lan:4" "3:lan:1" "4:lan:2" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
2018-06-15 17:27:51 +02:00
|
|
|
dir-860l-b1|\
|
2018-06-27 07:51:25 +02:00
|
|
|
elecom,wrc-1167ghbk2-s|\
|
2018-07-26 16:24:22 +02:00
|
|
|
elecom,wrc-2533gst|\
|
2018-08-19 01:05:15 +02:00
|
|
|
elecom,wrc-1900gst|\
|
ramips: add support for I-O DATA WN-AX1167GR
I-O DATA WN-AX1167GR is a 2.4/5 GHz band 11ac router, based on
MediaTek MT7621A.
Specification:
- MT7621A (2-Cores, 4-Threads)
- 64 MB of RAM (DDR2)
- 16 MB of Flash (SPI)
- 2T2R 2.4/5 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)
Stock firmware:
In the stock firmware, WN-AX1167GR has two os images each composed of
Linux kernel and rootfs.
These images are stored in "Kernel" and "app" partition of the
following partitions, respectively.
(excerpt from dmesg):
MX25L12805D(c2 2018c220) (16384 Kbytes)
mtd .name = raspi, .size = 0x01000000 (16M) .erasesize = 0x00010000 (64K) .numeraseregions = 0
Creating 10 MTD partitions on "raspi":
0x000000000000-0x000001000000 : "ALL"
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config "
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000060000 : "iNIC_rf"
0x000000060000-0x0000007e0000 : "Kernel"
0x000000800000-0x000000f80000 : "app"
0x000000f90000-0x000000fa0000 : "Key"
0x000000fa0000-0x000000fb0000 : "backup"
0x000000fb0000-0x000001000000 : "storage"
The flag for boot partition is stored in "Key" partition, and U-Boot
reads this and determines the partition to boot.
If the image that U-Boot first reads according to the flag is
"Bad Magic Number", U-Boot then tries to boot from the other image.
If the second image is correct, change the flag to the number
corresponding to that image and boot from that image.
(example):
## Booting image at bc800000 ...
Bad Magic Number,FFFFFFFF
Boot from KERNEL 1 !!
## Booting image at bc060000 ...
Image Name: MIPS OpenWrt Linux-4.14.50
Image Type: MIPS Linux kernel Image (lzma compressed)
Data Size: 1865917 Bytes = 1.8 MB
Load Address: 80001000
Entry Point: 80001000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
raspi_erase_write: offs:f90000, count:34
.
.
Done!
Starting kernel ...
Flash instruction using factory image:
1. Connect the computer to the LAN port of WN-AX1167GR
2. Connect power cable to WN-AX1167GR and turn on it
3. Access to "192.168.0.1" on the web browser and open firmware
update page ("ファームウェア")
4. Select the OpenWrt factory image and perform firmware update
5. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-AX1167GR
6. Wait ~180 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-06-27 15:47:13 +02:00
|
|
|
iodata,wn-ax1167gr|\
|
2018-06-27 07:51:25 +02:00
|
|
|
iodata,wn-gx300gr)
|
2017-07-25 12:29:14 +02:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
2018-05-27 02:26:14 +02:00
|
|
|
gnubee,gb-pc1|\
|
2018-02-17 09:54:57 +01:00
|
|
|
gnubee,gb-pc2)
|
2017-07-22 03:15:56 +02:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "4:lan" "6@eth0"
|
|
|
|
|
;;
|
2017-05-17 12:18:45 +02:00
|
|
|
gl-mt300n-v2)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
2014-06-13 11:16:15 +02:00
|
|
|
awapn2403)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"0:lan" "1:wan" "6@eth0"
|
2014-06-13 11:16:15 +02:00
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
b2c|\
|
|
|
|
|
nw718|\
|
|
|
|
|
psr-680w|\
|
|
|
|
|
sl-r7205|\
|
|
|
|
|
ur-336un|\
|
|
|
|
|
w502u|\
|
|
|
|
|
wr6202)
|
|
|
|
|
ucidef_set_interfaces_lan_wan "eth0.1" "eth0.2"
|
|
|
|
|
;;
|
2014-01-15 19:29:44 +01:00
|
|
|
br-6475nd)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "9@eth0"
|
2014-01-15 19:29:44 +01:00
|
|
|
;;
|
2017-09-06 11:14:16 +02:00
|
|
|
c108|\
|
2017-01-13 16:37:36 +01:00
|
|
|
cf-wr800n)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"4:lan" "6t@eth0"
|
2015-05-23 17:26:39 +02:00
|
|
|
;;
|
2014-06-02 14:42:52 +02:00
|
|
|
cy-swr1100)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "9@eth0"
|
2014-06-02 14:42:52 +02:00
|
|
|
;;
|
2016-05-28 16:22:10 +02:00
|
|
|
duzun-dm06)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
e1700|\
|
|
|
|
|
mt7620a_mt7530)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch1" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "6@eth0"
|
2013-03-11 22:02:43 +01:00
|
|
|
;;
|
2018-08-06 19:52:28 +02:00
|
|
|
edimax,br-6478ac-v2|\
|
|
|
|
|
tplink,c2-v1)
|
|
|
|
|
ucidef_add_switch "switch1" \
|
|
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
2015-10-05 12:25:47 +02:00
|
|
|
hc5*61|\
|
|
|
|
|
y1s)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "5:lan" "0:wan" "6@eth0"
|
2015-10-05 12:25:47 +02:00
|
|
|
;;
|
2016-11-28 19:41:51 +01:00
|
|
|
kn_rf)
|
2017-01-01 22:46:33 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2016-11-28 19:41:51 +01:00
|
|
|
"0:wan" "1:lan" "2:lan" "3:lan" "4:lan" "6@eth0"
|
|
|
|
|
;;
|
2016-10-29 14:26:58 +02:00
|
|
|
kng_rc)
|
|
|
|
|
ucidef_add_switch "switch1" \
|
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "7t@eth0"
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
mlwg2|\
|
|
|
|
|
wizard8800|\
|
2016-07-05 09:07:33 +02:00
|
|
|
wl-330n)
|
2015-08-17 08:02:59 +02:00
|
|
|
ucidef_set_interface_lan "eth0.1"
|
2011-12-23 15:27:16 +01:00
|
|
|
;;
|
2016-09-24 21:41:43 +02:00
|
|
|
mr200)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "6t@eth0"
|
|
|
|
|
ucidef_set_interface_wan "usb0"
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
mzk-dp150n|\
|
2017-04-08 00:34:48 +02:00
|
|
|
vocore-8M|\
|
|
|
|
|
vocore-16M)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"0:lan" "4:lan" "6t@eth0"
|
2012-02-22 20:46:15 +01:00
|
|
|
;;
|
2016-09-27 08:25:04 +02:00
|
|
|
newifi-d1)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
2017-02-11 14:32:07 +01:00
|
|
|
"1:lan:2" "2:lan:1" "4:wan" "6@eth0"
|
2016-09-27 08:25:04 +02:00
|
|
|
;;
|
2018-06-20 18:56:38 +02:00
|
|
|
phicomm,k2g)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "5:wan" "6@eth0"
|
|
|
|
|
;;
|
2017-07-23 21:06:44 +02:00
|
|
|
re350-v1)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "6@eth0"
|
|
|
|
|
;;
|
2017-03-07 17:38:30 +01:00
|
|
|
re6500)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:1" "1:lan:2" "2:lan:3" "3:lan:4" "6@eth0"
|
|
|
|
|
;;
|
2012-02-13 16:18:04 +01:00
|
|
|
rt-n56u)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "8@eth0"
|
2012-02-13 16:18:04 +01:00
|
|
|
;;
|
ramips: add support for Skylab SKW92A in EVB
Specifically, SKW92A_E16, described here:
http://www.skylabmodule.com/wp-content/uploads/SkyLab_SKW92A_V1.04_datasheet.pdf
Specification:
- MediaTek MT7628N/N (580 Mhz)
- 64 MB of RAM
- 16 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x u.FL
- Power by micro-USB connector at USB1 on EVB
- UART via micro-USB connector at USB3 on EVB (57600 8n1)
- 5x Ethernet LEDs
- 1x WLAN LEDs
- 1x WPS LED connected by jumper wire from I2S_CK on J20 to WPS_LED pin hole next
to daughter board on EVB
- WPS/Reset button (S2 on EVB)
- RESET button (S1 on EVB) is *not* connected to RST hole next to daughter board
Flash instruction:
>From Skylab firmware:
1. Associate with SKYLAP_AP
2. In a browser, load: http://10.10.10.254/
3. Username/password: admin/admin
4. In web admin interface: Administration / Upload Firmware, browse to
sysupgrade image, apply, flash will fail with a message:
Not a valid firmware. *** Warning: "/var/tmpFW" has corrupted data!
5. Telnet to 10.10.10.254, drops you into a root shell with no credentials
6. # cd /var
7. # mtd_write -r write tmpFW mtd4
Unlocking mtd4 ...
Writing from tmpFW to mtd4 ... [e]
8. When flash has completed, you will have booted into your firmware.
>From U-boot via TFTP and initramfs:
1. Place openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin on a TFTP server
2. Connect to serial console at USB3 on EVB
3. Connect ethernet between port 1 (not WAN) and your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "1"
7. At u-boot prompts:
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin
8. Move ethernet to port 0 (WAN) on EVB
9. At new OpenWrt console shell, fetch squashfs-sysupgrade image and flash
with sysupgrade.
>From U-boot via TFTP direct flash:
1. Place openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin on a TFTP server
2. Connect to serial console at USB3 on EVB (57600 8N1)
3. Connect ethernet between port 1 (not WAN) an your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "2"
7. At u-boot prompts:
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) Y
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin
8. When transfer is complete or as OpenWrt begins booting, move ethernet to
port 0 (WAN).
Signed-off-by: Russell Senior <russell@personaltelco.net>
2018-11-25 12:39:19 +01:00
|
|
|
skw92a)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
2017-06-09 13:02:56 +02:00
|
|
|
tew-638apb-v2)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"4:lan" "6@eth0"
|
|
|
|
|
;;
|
2018-11-17 09:47:40 +01:00
|
|
|
lava,lr-25g001|\
|
2012-10-18 09:23:12 +02:00
|
|
|
tew-691gr|\
|
2016-08-14 23:30:44 +02:00
|
|
|
tew-692gr|\
|
|
|
|
|
wlr-6000)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "5:wan" "0@eth0"
|
2012-10-18 09:23:07 +02:00
|
|
|
;;
|
2018-03-17 18:47:51 +01:00
|
|
|
tplink,tl-wr902ac-v3)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"4:lan" "6@eth0"
|
|
|
|
|
;;
|
2018-03-08 07:49:00 +01:00
|
|
|
vonets,var11n-300|\
|
|
|
|
|
wt1520-4M|\
|
|
|
|
|
wt1520-8M)
|
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-24 00:52:13 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
2017-08-03 22:09:06 +02:00
|
|
|
vocore2|\
|
|
|
|
|
vocore2lite)
|
2017-01-08 07:30:10 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "2:lan" "6t@eth0"
|
|
|
|
|
;;
|
2016-12-01 15:08:22 +01:00
|
|
|
f5d8235-v1|\
|
2018-11-18 14:46:58 +01:00
|
|
|
f5d8235-v2|\
|
2016-08-03 19:58:01 +02:00
|
|
|
tew-714tru|\
|
2015-08-17 08:02:59 +02:00
|
|
|
v11st-fe|\
|
|
|
|
|
wzr-agl300nh)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "5@eth0"
|
2014-08-01 22:51:24 +02:00
|
|
|
;;
|
2017-01-28 17:05:56 +01:00
|
|
|
wcr-1166ds)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"3:lan" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
ramips: Add support for ZBT WE1026-5G
The ZBT WE1026-5G
(http://www.zbtlink.com/products/router/WE1026-5G.html) is the follow-up
to the ZBT WE1026 and is based on MT7620. For the previous WE1026, the
ZBT WE826 image could be used. However, as the name implies, the -5G
comes equipped with a 5GHz wifi radio. As the WE826 only has a 2.4GHz
radio, the addition of 5GHz means that a separate image is needed for
the WE1026-5G. I suspect that this image will also work on the previous
WE1026, but I don't have a device to test with.
The WE1026-5G has following specifications:
* CPU: MT7620A
* 1x 10/100Mbps Ethernet.
* 16 MB Flash.
* 64 MB RAM.
* 1x USB 2.0 port.
* 1x mini-PCIe slots.
* 1x SIM slots.
* 1x 2.4Ghz WIFI.
* 1x 5GHz wifi (MT7612)
* 1x button.
* 3x controllable LEDs.
Works:
* Wifi.
* Switch.
* mini-PCIe slot. Only tested with a USB device (a modem).
* SIM slot.
* Sysupgrade.
* Button (reset).
Not working:
* The 5GHz WIFI LED is completely dead. I suspect the issue is the same
as on other devices with Mediatek 5Ghz wifi-cards/chips. The LED is
controlled by the driver, and mt76 (currently) does not support this.
Not tested:
* SD card reader.
Notes:
* The modem (labeled 3G/4G) and power LEDs are controlled by the
hardware.
* There is a 32MB version of this device available, but I do not have
access to it. I have therefor only added support for the 16MB version,
but added all the required infrastructure to make adding support for the
32MB version easy.
Installation:
The router comes pre-installed with OpenWRT, including a variant of
Luci. The initial firmware install can be done through this UI,
following normal procedure. I.e., access the UI and update the firmware
using the sysupgrade-image. Remember to select that you do not want to
keep existing settings.
Recovery:
If you brick the device, the WE1026-5G supports recovery using HTTP. Keep the
reset button pressed for ~5sec when booting to start the web server. Set the
address of the network interface on your machine to 192.168.1.2/24, and
point your browser to 192.168.1.1 to access the recovery UI. From the
recovery UI you can upload a firmware image.
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-09-10 14:44:47 +02:00
|
|
|
wcr-150gn|\
|
|
|
|
|
we1026-5g-16m)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"0:lan" "6t@eth0"
|
2011-12-27 17:56:30 +01:00
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
whr-1166d)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2015-12-03 16:46:29 +01:00
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "5:wan" "6@eth0"
|
2014-07-12 08:54:03 +02:00
|
|
|
;;
|
2015-09-14 22:09:31 +02:00
|
|
|
wizfi630a)
|
2015-12-03 18:30:24 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
2018-06-27 00:50:11 +02:00
|
|
|
"0:lan" "1:lan" "2:wan" "6@eth0"
|
2015-09-14 22:09:31 +02:00
|
|
|
;;
|
2018-03-08 07:49:00 +01:00
|
|
|
wt3020-4M|\
|
|
|
|
|
wt3020-8M)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"4:lan" "0:wan" "6@eth0"
|
|
|
|
|
;;
|
2018-01-24 01:27:51 +01:00
|
|
|
zbtlink,zbt-we1226|\
|
2017-12-29 05:35:32 +01:00
|
|
|
y1)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:2" "1:lan:1" "4:wan" "6@eth0"
|
|
|
|
|
;;
|
2011-12-01 23:48:35 +01:00
|
|
|
*)
|
2012-09-25 16:47:18 +02:00
|
|
|
RT3X5X=`cat /proc/cpuinfo | egrep "(RT3.5|RT5350)"`
|
2011-12-01 23:48:51 +01:00
|
|
|
if [ -n "${RT3X5X}" ]; then
|
2012-08-29 12:37:38 +02:00
|
|
|
ramips_setup_rt3x5x_vlans
|
2011-12-01 23:48:51 +01:00
|
|
|
else
|
2013-11-18 10:35:14 +01:00
|
|
|
ucidef_set_interfaces_lan_wan "eth0.1" "eth0.2"
|
2011-12-01 23:48:51 +01:00
|
|
|
fi
|
2011-12-01 23:48:35 +01:00
|
|
|
;;
|
2011-12-01 23:48:43 +01:00
|
|
|
esac
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
ramips_setup_macs()
|
|
|
|
|
{
|
|
|
|
|
local board="$1"
|
2011-12-01 23:48:45 +01:00
|
|
|
local lan_mac=""
|
|
|
|
|
local wan_mac=""
|
2011-12-01 23:48:43 +01:00
|
|
|
|
|
|
|
|
case $board in
|
2016-05-04 22:04:24 +02:00
|
|
|
a5-v11|\
|
ramips: add support for Loewe WMDR-143N
The WMDR-143N is a small module originally used as a Wifi client
in some Loewe smart TV sets. It is sold cheaply at german surplus
shops. The module contains a RT3662 SOC.
Specifications:
- 500 MHz CPU Clock
- 1x 10/100Mbps Ethernet (pin header)
- 32 MB of RAM
- 8 MB of FLASH
- 2T3R 2.4/5 GHz (SOC internal)
- 3 Antennas on PCB
- UART pads on PCB (J3: 1 = +3.3V, 2 = RX, 3 = TX, 4 = GND), TX
and RX are 3,3V only! The square hole is pin 1
- Power supply pads on PCB (J6: 1 and 2 = +5V, 3 and 4 = GND)
The square hole is pin 1
The original firmware has two identical kernel/rootfs images and
two "Factory" calibration data blocks in flash. The LEDE image
leaves only the first "Factory" block in place and uses both
"Kernel" blocks and the redundant "Factory" block together to gain
enough space for the jffs2 partition.
Flash instructions:
You need UART and Ethernet connections to flash the board. Use
the LEDE "sysupgrade.bin" image with tftp.
Apply power to the board and in the first 5 seconds, hit 2 to
select TFTP upload. The bootloader asks for board- and server IP
addresses and filename.
Alternate method: With the vendor firmware running, assign an IP
address to the ethernet port, tftp the firmware image to
/tmp and write to mtd4 ("KernelA").
Signed-off-by: Oliver Fleischmann <ogf@bnv-bamberg.de>
[remove pinctrl node from dts, no pin is used as GPIO]
Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-07-20 21:02:33 +02:00
|
|
|
ht-tm02|\
|
|
|
|
|
wmdr-143n)
|
2016-05-04 22:04:24 +02:00
|
|
|
lan_mac=$(cat /sys/class/net/eth0/address)
|
|
|
|
|
;;
|
|
|
|
|
all0239-3g|\
|
|
|
|
|
carambola|\
|
|
|
|
|
freestation5|\
|
|
|
|
|
w502u|\
|
|
|
|
|
wnce2001)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 46)
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
bc2|\
|
|
|
|
|
broadway|\
|
|
|
|
|
d105|\
|
|
|
|
|
dir-300-b7|\
|
|
|
|
|
dir-320-b1|\
|
|
|
|
|
dir-620-a1|\
|
|
|
|
|
esr-9753|\
|
|
|
|
|
freestation5|\
|
|
|
|
|
hlk-rm04|\
|
|
|
|
|
mpr-a1|\
|
|
|
|
|
psr-680w|\
|
|
|
|
|
sl-r7205|\
|
|
|
|
|
y1|\
|
|
|
|
|
y1s)
|
2014-07-26 22:36:09 +02:00
|
|
|
lan_mac=$(cat /sys/class/net/eth0/address)
|
2015-08-17 08:02:59 +02:00
|
|
|
lan_mac=$(macaddr_setbit_la "$lan_mac")
|
|
|
|
|
wan_mac=$(macaddr_add "$lan_mac" 1)
|
2014-01-15 19:29:44 +01:00
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
br-6475nd)
|
2014-07-26 22:36:09 +02:00
|
|
|
lan_mac=$(cat /sys/class/net/eth0/address)
|
2015-08-17 08:02:59 +02:00
|
|
|
wan_mac=$(mtd_get_mac_binary devdata 7)
|
2012-04-21 14:30:40 +02:00
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
cy-swr1100|\
|
2016-05-02 05:57:40 +02:00
|
|
|
dch-m225)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii factory lanmac)
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
dir-645)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii nvram lanmac)
|
|
|
|
|
wan_mac=$(mtd_get_mac_ascii nvram wanmac)
|
2012-06-23 15:58:29 +02:00
|
|
|
;;
|
2016-06-30 16:16:30 +02:00
|
|
|
dir-860l-b1)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii factory lanmac)
|
|
|
|
|
wan_mac=$(mtd_get_mac_ascii factory wanmac)
|
|
|
|
|
;;
|
2018-03-10 10:34:38 +01:00
|
|
|
dlink,dwr-116-a1|\
|
2018-04-19 19:34:22 +02:00
|
|
|
dlink,dwr-118-a2|\
|
2018-11-17 09:47:40 +01:00
|
|
|
dlink,dwr-921-c1|\
|
|
|
|
|
lava,lr-25g001)
|
2018-01-20 09:27:03 +01:00
|
|
|
wan_mac=$(jboot_config_read -m -i $(find_mtd_part "config") -o 0xE000)
|
|
|
|
|
lan_mac=$(macaddr_add "$wan_mac" 1)
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
e1700)
|
|
|
|
|
wan_mac=$(mtd_get_mac_ascii config WAN_MAC_ADDR)
|
|
|
|
|
;;
|
2018-08-06 19:52:28 +02:00
|
|
|
edimax,br-6478ac-v2)
|
|
|
|
|
lan_mac=$(cat /sys/class/net/eth0/address)
|
|
|
|
|
wan_mac=$(macaddr_add "$lan_mac" 2)
|
|
|
|
|
;;
|
2018-06-15 17:27:51 +02:00
|
|
|
elecom,wrc-1167ghbk2-s|\
|
2018-07-26 16:24:22 +02:00
|
|
|
elecom,wrc-2533gst|\
|
2018-08-19 01:05:15 +02:00
|
|
|
elecom,wrc-1900gst|\
|
2018-06-15 17:27:51 +02:00
|
|
|
sk-wb8)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 57350)
|
|
|
|
|
;;
|
2018-03-23 06:59:39 +01:00
|
|
|
gl-mt300n-v2|\
|
|
|
|
|
whr-g300n)
|
2017-07-13 14:03:07 +02:00
|
|
|
wan_mac=$(mtd_get_mac_binary factory 4)
|
|
|
|
|
;;
|
2017-02-25 00:19:15 +01:00
|
|
|
hc5*61|\
|
2017-02-22 13:47:22 +01:00
|
|
|
hc5661a|\
|
2018-08-09 19:22:46 +02:00
|
|
|
hc5962|\
|
|
|
|
|
hiwifi,hc5861b)
|
2015-10-05 12:25:47 +02:00
|
|
|
lan_mac=`mtd_get_mac_ascii bdinfo "Vfac_mac "`
|
|
|
|
|
[ -n "$lan_mac" ] || lan_mac=$(cat /sys/class/net/eth0/address)
|
|
|
|
|
wan_mac=$(macaddr_add "$lan_mac" 1)
|
|
|
|
|
;;
|
ramips: add support for I-O DATA WN-AX1167GR
I-O DATA WN-AX1167GR is a 2.4/5 GHz band 11ac router, based on
MediaTek MT7621A.
Specification:
- MT7621A (2-Cores, 4-Threads)
- 64 MB of RAM (DDR2)
- 16 MB of Flash (SPI)
- 2T2R 2.4/5 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)
Stock firmware:
In the stock firmware, WN-AX1167GR has two os images each composed of
Linux kernel and rootfs.
These images are stored in "Kernel" and "app" partition of the
following partitions, respectively.
(excerpt from dmesg):
MX25L12805D(c2 2018c220) (16384 Kbytes)
mtd .name = raspi, .size = 0x01000000 (16M) .erasesize = 0x00010000 (64K) .numeraseregions = 0
Creating 10 MTD partitions on "raspi":
0x000000000000-0x000001000000 : "ALL"
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config "
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000060000 : "iNIC_rf"
0x000000060000-0x0000007e0000 : "Kernel"
0x000000800000-0x000000f80000 : "app"
0x000000f90000-0x000000fa0000 : "Key"
0x000000fa0000-0x000000fb0000 : "backup"
0x000000fb0000-0x000001000000 : "storage"
The flag for boot partition is stored in "Key" partition, and U-Boot
reads this and determines the partition to boot.
If the image that U-Boot first reads according to the flag is
"Bad Magic Number", U-Boot then tries to boot from the other image.
If the second image is correct, change the flag to the number
corresponding to that image and boot from that image.
(example):
## Booting image at bc800000 ...
Bad Magic Number,FFFFFFFF
Boot from KERNEL 1 !!
## Booting image at bc060000 ...
Image Name: MIPS OpenWrt Linux-4.14.50
Image Type: MIPS Linux kernel Image (lzma compressed)
Data Size: 1865917 Bytes = 1.8 MB
Load Address: 80001000
Entry Point: 80001000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
raspi_erase_write: offs:f90000, count:34
.
.
Done!
Starting kernel ...
Flash instruction using factory image:
1. Connect the computer to the LAN port of WN-AX1167GR
2. Connect power cable to WN-AX1167GR and turn on it
3. Access to "192.168.0.1" on the web browser and open firmware
update page ("ファームウェア")
4. Select the OpenWrt factory image and perform firmware update
5. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-AX1167GR
6. Wait ~180 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-06-27 15:47:13 +02:00
|
|
|
iodata,wn-ax1167gr|\
|
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 14:42:48 +02:00
|
|
|
iodata,wn-gx300gr)
|
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary Factory 4)" 1)
|
|
|
|
|
;;
|
2017-01-05 12:25:59 +01:00
|
|
|
kn_rc|\
|
|
|
|
|
kn_rf|\
|
2016-10-29 14:26:58 +02:00
|
|
|
kng_rc)
|
2017-01-05 12:25:59 +01:00
|
|
|
wan_mac=$(mtd_get_mac_binary factory 40)
|
2016-10-29 14:26:58 +02:00
|
|
|
;;
|
2017-11-16 22:58:23 +01:00
|
|
|
linkits7688)
|
2015-10-19 12:07:38 +02:00
|
|
|
wan_mac=$(mtd_get_mac_binary factory 4)
|
|
|
|
|
lan_mac=$(mtd_get_mac_binary factory 46)
|
|
|
|
|
;;
|
2016-09-09 00:57:31 +02:00
|
|
|
mac1200rv2)
|
|
|
|
|
lan_mac=$(mtd_get_mac_binary factory_info 13)
|
|
|
|
|
wan_mac=$(macaddr_add "$lan_mac" 1)
|
|
|
|
|
;;
|
2017-08-12 16:56:11 +02:00
|
|
|
mir3g)
|
ramips: improve Xiaomi Mi Router 3G support
This commit improves support for the Xiaomi Mi Router 3G originally
added in commit 6e283cdc0da25928f8148805ebef7f8f2b769ee8
Improvements:
- Remove software watchdog as hardware watchdog now working as per
commit 3fbf3ab44f5cebb22e30a4c8681b13341feed6a6 for all mt7621
devices.
- Reset button polarity corrected - length of press determines reboot
(short press) vs. reset to defaults (long press) behaviour.
- Enable GPIO amber switch port LEDs on board rear - lit indicates 1Gbit
link and blink on activity. Green LEDs driven directly by switch
indicating any link speed and tx activity.
- USB port power on/off GPIO exposed as 'usbpower'
- Add access to uboot environment settings for checking/setting uboot
boot order preference from user space.
Changes:
- Front LED indicator is physically made of independent Yellow/Amber,
Red & Blue LEDs combined via a plastic 'lightpipe' to a front panel
indicator, hence the colour behaviour is similar to an RGB LED. RGB
LEDs are not supported at this time because they produce colour results
that do not then match colour labels, e.g. enabling 'mir3g:red' and
'mir3g:blue' would result in a purple indicator and we have no such
label for purple.
The yellow, red & blue LEDs have been split out as individual yellow,
red & blue status LEDs, with yellow being the default status LED as
before and with red's WAN and blue's USB default associations removed.
- Swapped order of vlan interfaces (eth0.1 & eth0.2) to match stock vlan
layout. eth0.1 is LAN, eth0.2 is WAN
- Add 'lwlll' vlan layout to mt7530 switch driver to prevent packet
leakage between kernel switch init and uci swconfig
uboot behaviour & system 'recovery'
uboot expects to find bootable kernels at nand addresses 0x200000 &
0x600000 known by uboot as "system 1" and "system 2" respectively.
uboot chooses which system to hand control to based on 3 environment
variables: flag_last_success, flag_try_sys1_failed & flag_try_sys2_failed
last_success represents a preference for a particular system and is set
to 0 for system 1, set to 1 for system 2. last_success is considered *if*
and only if both try_sys'n'_failed flags are 0 (ie. unset) If *either*
failed flags are set then uboot will attempt to hand control to the
non failed system. If both failed flags are set then uboot will check
the uImage CRC of system 1 and hand control to it if ok. If the uImage
CRC of system is not ok, uboot will hand control to system 2
irrespective of system 2's uImage CRC.
NOTE: uboot only ever sets failed flags, it *never* clears them. uboot
sets a system's failed flag if that system's was selected for boot but
the uImage CRC is incorrect.
Fortunately with serial console access, uboot provides the ability to
boot an initramfs image transferred via tftp, similarly an image may
be flashed to nand however it will flash to *both* kernels so a backup
of stock kernel image is suggested. Note that the suggested install
procedure below set's system 1's failed flag (stock) thus uboot ignores
the last_success preference and boots LEDE located in system 2.
Considerable thought has gone into whether LEDE should replace both
kernels, only one (and which one) etc. LEDE kernels do not include a
minimal rootfs and thus unlike the stock kernel cannot include a
method of controlling uboot environment variables in the event of
rootfs mount failure. Similarly uboot fails to provide an external
mechanism for indicating boot system failure.
Installation - from stock.
Installation through telnet/ssh:
- copy lede-ramips-mt7621-mir3g-squashfs-kernel1.bin and
lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin to usb disk or wget it
from LEDE download site to /tmp
- switch to /extdisks/sda1/ (if copied to USB drive) or to /tmp if
wgetted from LEDE download site
- run: mtd write lede-ramips-mt7621-mir3g-squashfs-kernel1.bin kernel1
- run: mtd write lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin rootfs0
- run: nvram set flag_try_sys1_failed=1
- run: nvram commit
- run: reboot
Recovery - to stock.
Assuming you used the above installation instructions you will have a
stock kernel image in system 1. If it can be booted then it may be used
to perform a stock firmware recovery, thus erasing LEDE completely. From
a 'working' LEDE state (even failsafe)
Failsafe only:
- run: mount_root
- run: sh /etc/uci-defaults/30_uboot-envtools
Then do the steps for 'All'
All:
- run: fw_setenv flag_try_sys2_failed 1
- run: reboot
The board will reboot into system 1 (stock basic kernel) and wait with
system red light slowly blinking for a FAT formatted usb stick with a
recovery image to be inserted. Press and hold the reset button for
around 1 second. Status LED will turn yellow during recovery and blue
when recovery complete.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
2017-09-25 21:41:13 +02:00
|
|
|
lan_mac=$(mtd_get_mac_binary Factory 0xe006)
|
2017-08-12 16:56:11 +02:00
|
|
|
;;
|
2017-01-18 10:45:48 +01:00
|
|
|
miwifi-mini)
|
|
|
|
|
wan_mac=$(cat /sys/class/net/eth0/address)
|
|
|
|
|
lan_mac=$(macaddr_setbit_la "$wan_mac")
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
m3|\
|
2017-04-08 00:34:48 +02:00
|
|
|
m4-4M|\
|
|
|
|
|
m4-8M|\
|
2015-08-17 08:02:59 +02:00
|
|
|
x5|\
|
2013-11-25 09:33:42 +01:00
|
|
|
x8)
|
2014-07-26 22:36:09 +02:00
|
|
|
lan_mac=$(cat /sys/class/net/eth0/address)
|
|
|
|
|
lan_mac=$(macaddr_add "$lan_mac" -2)
|
2011-12-06 21:06:08 +01:00
|
|
|
;;
|
2016-09-27 08:25:04 +02:00
|
|
|
newifi-d1)
|
|
|
|
|
lan_mac=$(cat /sys/class/net/eth0/address)
|
|
|
|
|
lan_mac=$(macaddr_add "$lan_mac" 2)
|
|
|
|
|
;;
|
2017-01-09 20:59:56 +01:00
|
|
|
omega2|\
|
|
|
|
|
omega2p)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 4)
|
|
|
|
|
lan_mac=$(mtd_get_mac_binary factory 46)
|
|
|
|
|
;;
|
2018-06-20 18:56:38 +02:00
|
|
|
oy-0001|\
|
|
|
|
|
phicomm,k2g)
|
2015-08-17 08:02:59 +02:00
|
|
|
lan_mac=$(mtd_get_mac_binary factory 40)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 46)
|
|
|
|
|
;;
|
2017-03-11 08:44:33 +01:00
|
|
|
r6220)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 4)
|
|
|
|
|
lan_mac=$(macaddr_add "$wan_mac" 1)
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
rt-n56u)
|
2014-07-26 22:36:09 +02:00
|
|
|
lan_mac=$(cat /sys/class/net/eth0/address)
|
2013-02-16 12:50:25 +01:00
|
|
|
lan_mac=$(macaddr_setbit_la "$lan_mac")
|
2015-08-17 08:02:59 +02:00
|
|
|
wan_mac=$(mtd_get_mac_binary factory 32772)
|
2012-08-12 14:48:24 +02:00
|
|
|
;;
|
ramips: add support for Skylab SKW92A in EVB
Specifically, SKW92A_E16, described here:
http://www.skylabmodule.com/wp-content/uploads/SkyLab_SKW92A_V1.04_datasheet.pdf
Specification:
- MediaTek MT7628N/N (580 Mhz)
- 64 MB of RAM
- 16 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x u.FL
- Power by micro-USB connector at USB1 on EVB
- UART via micro-USB connector at USB3 on EVB (57600 8n1)
- 5x Ethernet LEDs
- 1x WLAN LEDs
- 1x WPS LED connected by jumper wire from I2S_CK on J20 to WPS_LED pin hole next
to daughter board on EVB
- WPS/Reset button (S2 on EVB)
- RESET button (S1 on EVB) is *not* connected to RST hole next to daughter board
Flash instruction:
>From Skylab firmware:
1. Associate with SKYLAP_AP
2. In a browser, load: http://10.10.10.254/
3. Username/password: admin/admin
4. In web admin interface: Administration / Upload Firmware, browse to
sysupgrade image, apply, flash will fail with a message:
Not a valid firmware. *** Warning: "/var/tmpFW" has corrupted data!
5. Telnet to 10.10.10.254, drops you into a root shell with no credentials
6. # cd /var
7. # mtd_write -r write tmpFW mtd4
Unlocking mtd4 ...
Writing from tmpFW to mtd4 ... [e]
8. When flash has completed, you will have booted into your firmware.
>From U-boot via TFTP and initramfs:
1. Place openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin on a TFTP server
2. Connect to serial console at USB3 on EVB
3. Connect ethernet between port 1 (not WAN) and your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "1"
7. At u-boot prompts:
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin
8. Move ethernet to port 0 (WAN) on EVB
9. At new OpenWrt console shell, fetch squashfs-sysupgrade image and flash
with sysupgrade.
>From U-boot via TFTP direct flash:
1. Place openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin on a TFTP server
2. Connect to serial console at USB3 on EVB (57600 8N1)
3. Connect ethernet between port 1 (not WAN) an your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "2"
7. At u-boot prompts:
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) Y
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin
8. When transfer is complete or as OpenWrt begins booting, move ethernet to
port 0 (WAN).
Signed-off-by: Russell Senior <russell@personaltelco.net>
2018-11-25 12:39:19 +01:00
|
|
|
skw92a)
|
|
|
|
|
lan_mac=$(mtd_get_mac_binary factory 40)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 46)
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
tew-691gr)
|
2016-08-19 20:46:50 +02:00
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 4)" 3)
|
2015-01-08 21:26:20 +01:00
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
tew-692gr)
|
2016-08-14 00:47:14 +02:00
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 4)" 1)
|
2012-10-18 09:23:03 +02:00
|
|
|
;;
|
2015-11-02 11:17:51 +01:00
|
|
|
tiny-ac)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii u-boot-env LAN_MAC_ADDR)
|
|
|
|
|
wan_mac=$(mtd_get_mac_ascii u-boot-env WAN_MAC_ADDR)
|
|
|
|
|
;;
|
2016-10-10 03:24:42 +02:00
|
|
|
vr500)
|
|
|
|
|
lan_mac=$(mtd_get_mac_binary factory 57344)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 57350)
|
|
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
w306r-v20)
|
|
|
|
|
lan_mac=$(cat /sys/class/net/eth0/address)
|
|
|
|
|
wan_mac=$(macaddr_add "$lan_mac" 5)
|
2014-11-05 15:37:13 +01:00
|
|
|
;;
|
2017-01-28 17:05:56 +01:00
|
|
|
wcr-1166ds|\
|
|
|
|
|
wsr-1166)
|
|
|
|
|
local index="$(find_mtd_index "board_data")"
|
|
|
|
|
wan_mac="$(grep -m1 mac= "/dev/mtd${index}" | cut -d= -f2)"
|
|
|
|
|
lan_mac=$wan_mac
|
|
|
|
|
;;
|
2012-02-11 16:11:34 +01:00
|
|
|
wcr-150gn)
|
2015-01-08 21:25:55 +01:00
|
|
|
wan_mac=$(mtd_get_mac_binary factory 40)
|
2011-12-05 18:27:07 +01:00
|
|
|
;;
|
2015-08-17 08:02:59 +02:00
|
|
|
whr-1166d|\
|
|
|
|
|
whr-300hp2|\
|
|
|
|
|
whr-600d|\
|
|
|
|
|
wsr-600)
|
2015-03-20 10:37:07 +01:00
|
|
|
wan_mac=$(mtd_get_mac_binary factory 4)
|
|
|
|
|
lan_mac=$wan_mac
|
|
|
|
|
;;
|
2015-09-14 22:09:31 +02:00
|
|
|
wizfi630a)
|
|
|
|
|
lan_mac=$(mtd_get_mac_binary factory 4)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 40)
|
|
|
|
|
;;
|
2016-08-14 23:30:44 +02:00
|
|
|
wlr-6000)
|
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 32772)" 2)
|
|
|
|
|
;;
|
2014-06-02 14:43:04 +02:00
|
|
|
*)
|
2014-07-14 09:38:23 +02:00
|
|
|
lan_mac=$(cat /sys/class/net/eth0/address)
|
2014-06-02 14:43:04 +02:00
|
|
|
wan_mac=$(macaddr_add "$lan_mac" 1)
|
|
|
|
|
;;
|
2011-12-01 23:48:43 +01:00
|
|
|
esac
|
2011-12-01 23:48:45 +01:00
|
|
|
|
2016-09-10 09:46:14 +02:00
|
|
|
[ -n "$lan_mac" ] && ucidef_set_interface_macaddr "lan" $lan_mac
|
|
|
|
|
[ -n "$wan_mac" ] && ucidef_set_interface_macaddr "wan" $wan_mac
|
2011-12-01 23:48:43 +01:00
|
|
|
}
|
|
|
|
|
|
2014-08-18 15:09:20 +02:00
|
|
|
board_config_update
|
2017-05-12 22:36:07 +02:00
|
|
|
board=$(board_name)
|
2011-12-01 23:48:43 +01:00
|
|
|
ramips_setup_interfaces $board
|
|
|
|
|
ramips_setup_macs $board
|
2014-08-18 15:09:20 +02:00
|
|
|
board_config_flush
|
2011-12-01 23:48:48 +01:00
|
|
|
|
|
|
|
|
exit 0
|