2019-10-22 12:37:13 +02:00
|
|
|
|
|
|
|
. /lib/functions.sh
|
|
|
|
. /lib/functions/uci-defaults.sh
|
|
|
|
. /lib/functions/system.sh
|
|
|
|
|
|
|
|
ramips_setup_interfaces()
|
|
|
|
{
|
|
|
|
local board="$1"
|
|
|
|
|
|
|
|
case $board in
|
|
|
|
aigale,ai-br100|\
|
|
|
|
alfa-network,ac1200rm|\
|
|
|
|
asus,rt-n12p|\
|
|
|
|
dlink,dwr-116-a1|\
|
|
|
|
dlink,dwr-921-c1|\
|
|
|
|
dlink,dwr-922-e2|\
|
2020-04-29 01:23:34 +02:00
|
|
|
dovado,tiny-ac|\
|
2019-10-22 12:37:13 +02:00
|
|
|
ohyeah,oy-0001|\
|
|
|
|
phicomm,psg1208|\
|
|
|
|
planex,db-wrt01|\
|
|
|
|
planex,mzk-750dhp|\
|
2020-04-29 01:23:34 +02:00
|
|
|
ralink,mt7620a-evb|\
|
|
|
|
ralink,mt7620a-mt7610e-evb|\
|
|
|
|
ralink,mt7620a-v22sg-evb|\
|
2019-10-22 12:37:13 +02:00
|
|
|
sanlinking,d240|\
|
|
|
|
zbtlink,zbt-ape522ii|\
|
|
|
|
zbtlink,zbt-we826-16m|\
|
|
|
|
zbtlink,zbt-we826-32m|\
|
|
|
|
zbtlink,zbt-we826-e|\
|
|
|
|
zbtlink,zbt-wr8305rt|\
|
|
|
|
zyxel,keenetic-omni)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "6@eth0"
|
|
|
|
;;
|
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|\
|
|
|
|
zbtlink,zbt-we1026-h-32m)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"3:lan" "4:wan" "6@eth0"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
alfa-network,tube-e4g|\
|
|
|
|
buffalo,wmr-300|\
|
|
|
|
dlink,dch-m225|\
|
2020-04-10 06:32:42 +02:00
|
|
|
edimax,ew-7476rpc|\
|
|
|
|
edimax,ew-7478ac|\
|
2019-10-22 12:37:13 +02:00
|
|
|
elecom,wrh-300cr|\
|
ramips: add support for HooToo HT-TM05
The HooToo HT-TM05 is a battery powered router, with an Ethernet and USB port.
Vendor U-Boot limited to 1.5 MB kernel size, so use lzma loader (loader-okli).
Specifications:
SOC: MediaTek MT7620N
BATTERY: 10400mAh
WLAN: 802.11bgn
LAN: 1x 10/100 Mbps Ethernet
USB: 1x USB 2.0 (Type-A)
RAM: 64 MB
FLASH: GigaDevice GD25Q64, Serial 8 MB Flash, clocked at 50 MHz
Flash itself specified to 80 MHz, but speed limited by mt7620 SPI
fast-read enabled (m25p)
LED: Status LED (blue after boot, green with WiFi traffic
4 leds to indicate power level of the battery (unable to control)
INPUT: Power, reset button
MAC assignment based on vendor firmware:
2.4 GHz *:b4 (factory 0x04)
LAN/label *:b4 (factory 0x28)
WAN *:b5 (factory 0x2e)
Tested and working:
- Ethernet
- 2.4 GHz WiFi (Correct MAC-address)
- Installation from TFTP (recovery)
- OpenWRT sysupgrade (Preserving and non-preserving), through the usual
ways: command line and LuCI
- LEDs (except as noted above)
- Button (reset)
- I2C, which is needed for reading battery charge status and level
- U-Boot environment / variables (from U-Boot, and OpenWrt)
Installation:
- Download the needed OpenWrt install files, place them in the root
of a clean TFTP server running on your computer. Rename the files as,
- ramips-mt7620-hootoo_tm05-squashfs-kernel.bin => kernel
- ramips-mt7620-hootoo_tm05-squashfs-rootfs.bin => rootfs
- Plug the router into your computer via Ethernet
- Set your computer to use 10.10.10.254 as its IP address
- With your router shut down, hold down the power button until the first
white LED lights up.
- Push and hold the reset button and release the power button. Continue
holding the reset button for 30 seconds or until it begins searching
for files on your TFTP server, whichever comes first.
- The router (10.10.10.128) will look for your computer at 10.10.10.254
and install the two files. Once it has finished installation, it will
automatically reboot and start up OpenWrt.
- Set your computer to use DHCP for its IP address
Notes:
- U-Boot environment can be modified, u-boot-env is preserved on initial
install or sysupgrade
- mtd-concat functionality is included, to leave a "hole" for u-boot-env,
combining the OEM kernel and rootfs partitions
I would like to thank @mpratt14 and @xabolcs for their help getting the
lzma loader to work!
Signed-off-by: Russell Morris <rmorris@rkmorris.us>
[drop changes in image/Makefile, fix indent and PKG_RELEASE in
uboot-envtools, fix LOADER_FLASH_OFFS, minor commit message facelift,
add COMPILE to Device/Default]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-25 01:38:36 +01:00
|
|
|
hootoo,ht-tm05|\
|
2019-10-22 12:37:13 +02:00
|
|
|
kimax,u25awf-h1|\
|
2020-04-10 06:32:42 +02:00
|
|
|
kimax,u35wf|\
|
|
|
|
kingston,mlw221|\
|
|
|
|
kingston,mlwg2|\
|
|
|
|
microduino,microwrt|\
|
2019-10-22 12:37:13 +02:00
|
|
|
netgear,ex2700|\
|
|
|
|
netgear,ex3700|\
|
2020-06-09 12:31:57 +02:00
|
|
|
netgear,ex6120|\
|
2019-07-29 20:23:28 +02:00
|
|
|
netgear,ex6130|\
|
2019-10-22 12:37:13 +02:00
|
|
|
netgear,wn3000rp-v3|\
|
|
|
|
planex,cs-qr10|\
|
|
|
|
planex,mzk-ex300np|\
|
|
|
|
planex,mzk-ex750np|\
|
2020-09-11 17:09:44 +02:00
|
|
|
ravpower,rp-wd03|\
|
2020-03-02 22:24:19 +01:00
|
|
|
sercomm,na930|\
|
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-04-10 06:32:42 +02:00
|
|
|
tplink,re210-v1|\
|
|
|
|
yukai,bocco|\
|
|
|
|
zbtlink,zbt-cpe102|\
|
|
|
|
zte,q7)
|
|
|
|
ucidef_add_switch "switch0"
|
|
|
|
ucidef_add_switch_attr "switch0" "enable" "false"
|
2019-10-22 12:37:13 +02:00
|
|
|
ucidef_set_interface_lan "eth0"
|
|
|
|
;;
|
|
|
|
asus,rp-n53)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "6t@eth0"
|
|
|
|
;;
|
ramips: add support for ASUS RT-AC54U
Specification:
- CPU: MTK MT7620A
- RAM: 64MB
- ROM: 16MB SPI Flash Macronix MX25L12835E
- WiFi1: MediaTek MT7620A
- WiFi2: MediaTek MT7612E
- Button: reset, wps
- LED: 9 LEDs:Power, WiFi 2.4G,WiFi 5G, USB, LAN1, LAN2, LAN3, LAN4, WAN
- Ethernet: 5 ports, 4 LAN + 1 WAN
- Other: 1x UART 1x USB2.0
Installation:
Update using ASUS Firmware Restoration Tool:
1. Download the ASUS Firmware Restoration Tool but don't open it yet
2. Unplug your computer from the router
3. Put the router into Rescue Mode by: turning the power off, using a pin
to press and hold the reset button, then turning the router back on while
keeping the reset button pressed for ~5 secs until the power LED starts
flashing slowly (which indicates the router has entered Rescue Mode)
4. Important (if you don't do this next step the Asus Firmware
Restoration Tool will wrongly assume that the router is not in Rescue Mode
and will refuse to flash it): go to the Windows Control Panel and
temporarily disable ALL other network adapters except the one you will use
to connect your computer to the router
5. For the single adapter you left enabled, temporarily give it the
static IP 192.168.1.10 and the subnet mask 255.255.255.0
6. Connect a LAN cable between your computer (make sure to use the
Ethernet port of the adapter you've just set up) and port 1 of the router
(not the router's WAN port)
7. Rename sysupgrade.bin to factory.trx
8. Open the Asus Firmware Restoration Tool, locate factory.trx and click
upload (if Windows shows a compatibility prompt, confirm that the tool worked fine)
9. Flashing and reboot is finished when the power LED stops blinking and
stays on
MAC assignment based on vendor firmware:
2g 0x4 label
5g 0x8004 label +4
lan 0x22 label +4
wan 0x28 label
Signed-off-by: Zhijun You <hujy652@gmail.com>
[rebased due to DTSI patch, minor commit message adjustments, fix
label MAC address (lan->wan), do spi frequency increase separately]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-05-14 13:37:40 +02:00
|
|
|
asus,rt-ac51u|\
|
2020-04-29 01:23:34 +02:00
|
|
|
asus,rt-ac54u|\
|
2019-10-22 12:37:13 +02:00
|
|
|
asus,rt-n14u|\
|
|
|
|
bdcom,wap2100-sk|\
|
2021-07-27 06:32:00 +02:00
|
|
|
domywifi,dm202|\
|
|
|
|
domywifi,dm203|\
|
|
|
|
domywifi,dw22d|\
|
2020-04-29 01:23:34 +02:00
|
|
|
edimax,ew-7478apc|\
|
2019-10-22 12:37:13 +02:00
|
|
|
glinet,gl-mt300a|\
|
|
|
|
glinet,gl-mt300n|\
|
|
|
|
glinet,gl-mt750|\
|
|
|
|
hiwifi,hc5661|\
|
|
|
|
wrtnode,wrtnode|\
|
2020-04-29 01:23:34 +02:00
|
|
|
zbtlink,zbt-wa05|\
|
|
|
|
zyxel,keenetic-omni-ii)
|
2019-10-22 12:37:13 +02:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
buffalo,whr-300hp2|\
|
|
|
|
buffalo,whr-600d)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan:1" "1:lan:2" "2:lan:3" "3:lan:4" "4:wan:5" "6@eth0"
|
|
|
|
;;
|
|
|
|
buffalo,whr-1166d)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "5:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
comfast,cf-wr800n|\
|
|
|
|
hnet,c108)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"4:lan" "6@eth0"
|
|
|
|
;;
|
|
|
|
dlink,dir-510l)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan" "6@eth0"
|
|
|
|
;;
|
2020-06-09 12:01:43 +02:00
|
|
|
dlink,dir-810l|\
|
ramips: add support for Netgear JWNR2010 v5
Specification:
- CPU: MediaTek MT7620N (580 MHz)
- Flash size: 4 MB NOR SPI
- RAM size: 32 MB DDR1
- Bootloader: U-Boot
- Wireless: MT7620N 2x2 MIMO 802.11b/g/n (2.4 GHz)
- Switch: MT7620 built-in 10/100 switch with vlan support
- Ports: 4x LAN, 1x WAN
- Others: 7x LED, Reset button, UART header on PCB (57600 8N1)
Flash instructions:
1. Use ethernet cable to connect router with PC/Laptop, any router
LAN port will work.
2. To flash openwrt we are using nmrpflash[1].
3. Flash commands:
First we need to identify the correct Ethernet id.
nmrpflash -L
nmrpflash -i net* -f openwrt-ramips-mt7620-netgear_jwnr2010-v5-squashfs-factory.img
This will show something like "Advertising NMRP server on net*..." (net*, *=1,2,3... etc.)
4. Now remove the power cable from router back side and immediately connect it again.
You will see flash notification in CMD window, once it says reboot the device just
plug off the router and plug in again.
Revert to stock:
1. Download the stock firmware from official netgear support[2].
2. Follow the same nmrpflash procedure like above, this time just use the stock firmware.
nmrpflash -i net* -f N300-V1.1.0.54_1.0.1.img
MAC addresses on stock firmware:
LAN = *:28 (label)
WAN = *:29
WLAN = *:28
On flash, the only valid MAC address is found in factory 0x4.
Special Note:
This openwrt firmware will also support other netgear N300 routers like below as they
share same stock firmware[3].
JNR1010v2 / WNR614 / WNR618 / JWNR2000v5 / WNR2020 / WNR1000v4 / WNR2020v2 / WNR2050
[1] https://github.com/jclehner/nmrpflash
[2] https://www.netgear.com/support/product/JWNR2010v5.aspx
[3] http://kb.netgear.com/000059663
Signed-off-by: Shibajee Roy <ador250@protonmail.com>
[create DTSI, use netgear_sercomm_nor, disable by default, add MAC
addresses to commit message, add label MAC address]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-08-02 17:19:52 +02:00
|
|
|
netgear,jwnr2010-v5|\
|
ramips: add new flash layout support to Phicomm K2
Descriptions:
Phicomm K2 (PSG1218) got a new "permanent_config" partition after
update firmware to v22.5. This partition located in front of the
firmware partition, same as The Phicomm K2P and K2G. Due to this
change the new bootloader can't load previous firmware any more.
This commit is aimed at add support for Phicomm K2 which official
firmware version is 22.5.x or newer. For which runs old firmware
version, just update OpenWrt that has a prefix of "k2-v22.4".
For uniform naming, this commit also changed the model name
PSG1218 to a more recognizable name K2, refer to Phicomm K2G,
K2P K2T.
OpenWrt selection table:
official firmware version OpenWrt
v22.4.x.x or older phicomm_k2-v22.4
v22.5.x.x or newer phicomm_k2-v22.5
Installation:
Same as Phicomm K2G, K2P, PSG1208.
a. TFTP + U-Boot
b. Open telnet by some web page vulnerability (Search Baidu by key
words "K2 telnet"), and then we can upload firmware image to
/tmp and write it to firmware partition with mtd instruction.
Signed-off-by: Shiji Yang <yangshiji66@qq.com>
[rebase, add/harmonize version in model variables, fix version typo
in commit message, wrap commit message properly]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2021-07-27 06:45:05 +02:00
|
|
|
phicomm,k2-v22.4|\
|
|
|
|
phicomm,k2-v22.5|\
|
2020-06-12 18:04:15 +02:00
|
|
|
trendnet,tew-810dr|\
|
2020-06-09 12:01:43 +02:00
|
|
|
zbtlink,zbt-we2026)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "4:wan" "6@eth0"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
dlink,dwr-118-a1)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan:2" "2:lan:3" "3:lan:1" "4:lan:0" "5:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
dlink,dwr-118-a2)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan:2" "2:lan:1" "3:lan:3" "4:lan" "0:wan" "6@eth0"
|
|
|
|
;;
|
2018-04-19 09:20:58 +02:00
|
|
|
dlink,dwr-960)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan" "2:lan" "3:lan" "5:lan" "0:wan" "6@eth0"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
edimax,br-6478ac-v2|\
|
2020-04-17 22:31:11 +02:00
|
|
|
lb-link,bl-w1200|\
|
2019-10-22 12:37:13 +02:00
|
|
|
tplink,archer-c2-v1)
|
|
|
|
ucidef_add_switch "switch0"
|
|
|
|
ucidef_add_switch_attr "switch0" "enable" "false"
|
2020-04-10 06:32:42 +02:00
|
|
|
ucidef_add_switch "switch1" \
|
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "6@eth0"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
ramips: add support for Sitecom WLR-4100 v1 002
Sitecom WLR-4100 v1 002 (marked as X4 N300) is a wireless router
Specification:
SoC: MT7620A
RAM: 64 MB DDR2
Flash: MX25L6405D SPI NOR 8 MB
WIFI: 2.4 GHz integrated
Ethernet: 5x 10/100/1000 Mbps QCA8337
USB: 1x 2.0
LEDS: 2x GPIO controlled, 5x switch
Buttons: 1x GPIO controlled
UART: row of 4 unpopulated holes near USB port, starting count from
white triangle on PCB:
VCC 3.3V
GND
TX
RX
baud: 115200, parity: none, flow control: none
Installation
Connect to one of LAN (yellow) ethernet ports,
Open router configuration interface,
Go to Toolbox > Firmware,
Browse for OpenWrt factory image with dlf extension and hit Apply,
Wait few minutes, after the Power LED will stop blinking, the router is
ready for configuration.
Known issues
Some USB 2.0 devices work at full speed mode 1.1 only
MAC addresses
factory partition only contains one (binary) MAC address in 0x4.
u-boot-env contains four (ascii) MAC addresses, of which two appear
to be valid.
factory 0x4 **:**:**:**:b9:84 binary
u-boot-env ethaddr **:**:**:**:b9:84 ascii
u-boot-env wanaddr **:**:**:**:b9:85 ascii
u-boot-env wlanaddr 00:AA:BB:CC:DD:12 ascii
u-boot-env iNICaddr 00:AA:BB:CC:DD:22 ascii
The factory firmware only assigns ethaddr. Thus, we take the
binary value which we can use directly in DTS.
Additional information
OEM firmware shell password is: SitecomSenao
useful for creating backup of original firmware.
There is also another revision of this device (v1 001), based on RT3352 SoC
Signed-off-by: Andrea Poletti <polex73@yahoo.it>
[remove config DT label, convert to nvmem, remove MAC address
setup from u-boot-env, add MAC address info to commit message]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2021-07-23 18:15:00 +02:00
|
|
|
engenius,esr600|\
|
2021-11-29 13:56:49 +01:00
|
|
|
lava,lr-25g001|\
|
ramips: add support for Sitecom WLR-4100 v1 002
Sitecom WLR-4100 v1 002 (marked as X4 N300) is a wireless router
Specification:
SoC: MT7620A
RAM: 64 MB DDR2
Flash: MX25L6405D SPI NOR 8 MB
WIFI: 2.4 GHz integrated
Ethernet: 5x 10/100/1000 Mbps QCA8337
USB: 1x 2.0
LEDS: 2x GPIO controlled, 5x switch
Buttons: 1x GPIO controlled
UART: row of 4 unpopulated holes near USB port, starting count from
white triangle on PCB:
VCC 3.3V
GND
TX
RX
baud: 115200, parity: none, flow control: none
Installation
Connect to one of LAN (yellow) ethernet ports,
Open router configuration interface,
Go to Toolbox > Firmware,
Browse for OpenWrt factory image with dlf extension and hit Apply,
Wait few minutes, after the Power LED will stop blinking, the router is
ready for configuration.
Known issues
Some USB 2.0 devices work at full speed mode 1.1 only
MAC addresses
factory partition only contains one (binary) MAC address in 0x4.
u-boot-env contains four (ascii) MAC addresses, of which two appear
to be valid.
factory 0x4 **:**:**:**:b9:84 binary
u-boot-env ethaddr **:**:**:**:b9:84 ascii
u-boot-env wanaddr **:**:**:**:b9:85 ascii
u-boot-env wlanaddr 00:AA:BB:CC:DD:12 ascii
u-boot-env iNICaddr 00:AA:BB:CC:DD:22 ascii
The factory firmware only assigns ethaddr. Thus, we take the
binary value which we can use directly in DTS.
Additional information
OEM firmware shell password is: SitecomSenao
useful for creating backup of original firmware.
There is also another revision of this device (v1 001), based on RT3352 SoC
Signed-off-by: Andrea Poletti <polex73@yahoo.it>
[remove config DT label, convert to nvmem, remove MAC address
setup from u-boot-env, add MAC address info to commit message]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2021-07-23 18:15:00 +02:00
|
|
|
sitecom,wlr-4100-v1-002)
|
2019-10-22 12:37:13 +02:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "5:wan" "0@eth0"
|
2021-04-20 18:35:47 +02:00
|
|
|
ucidef_add_switch "switch1" \
|
|
|
|
"5:lan" "6@eth0"
|
|
|
|
ucidef_add_switch_attr "switch1" "enable" "false"
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
fon,fon2601)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan" "4:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
head-weblink,hdrm200)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "5:lan" "0:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
hiwifi,hc5761)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan" "4:lan" "0:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
hiwifi,hc5861)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan" "1:lan" "5:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
iodata,wn-ac1167gr|\
|
2019-09-26 17:21:25 +02:00
|
|
|
iodata,wn-ac733gr3|\
|
|
|
|
iptime,a1004ns)
|
2020-04-10 06:32:42 +02:00
|
|
|
ucidef_add_switch "switch0"
|
|
|
|
ucidef_add_switch_attr "switch0" "enable" "false"
|
2019-10-22 12:37:13 +02:00
|
|
|
ucidef_add_switch "switch1" \
|
|
|
|
"1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "0:wan" "6@eth0"
|
|
|
|
;;
|
2019-09-26 17:16:33 +02:00
|
|
|
iptime,a104ns)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "0:wan" "6@eth0"
|
|
|
|
;;
|
2019-10-16 08:34:14 +02:00
|
|
|
lenovo,newifi-y1|\
|
|
|
|
xiaomi,miwifi-mini)
|
2019-10-22 12:37:13 +02:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan:2" "1:lan:1" "4:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
lenovo,newifi-y1s)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan:4" "2:lan:3" "4:lan:2" "5:lan:1" "0:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
linksys,e1700|\
|
2019-11-11 17:23:07 +01:00
|
|
|
netis,wf2770|\
|
2019-10-22 12:37:13 +02:00
|
|
|
ralink,mt7620a-mt7530-evb)
|
2020-04-10 06:32:42 +02:00
|
|
|
ucidef_add_switch "switch0"
|
|
|
|
ucidef_add_switch_attr "switch0" "enable" "false"
|
2019-10-22 12:37:13 +02:00
|
|
|
ucidef_add_switch "switch1" \
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
nexx,wt3020-4m|\
|
|
|
|
nexx,wt3020-8m)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"4:lan" "0:wan" "6@eth0"
|
|
|
|
;;
|
2020-08-14 00:26:13 +02:00
|
|
|
phicomm,k2g|\
|
|
|
|
wavlink,wl-wn530hg4)
|
2019-10-22 12:37:13 +02:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "5:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
phicomm,psg1218b)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan:3" "1:lan:2" "2:lan:1" "3:wan" "6@eth0"
|
|
|
|
;;
|
2019-12-04 21:07:58 +01:00
|
|
|
tplink,archer-c20i|\
|
2019-10-22 12:37:13 +02:00
|
|
|
tplink,archer-c20-v1|\
|
|
|
|
tplink,archer-c50-v1)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"1:lan:3" "2:lan:4" "3:lan:1" "4:lan:2" "0:wan" "6@eth0"
|
|
|
|
;;
|
|
|
|
tplink,archer-mr200)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "6t@eth0"
|
|
|
|
ucidef_set_interface_wan "usb0"
|
|
|
|
;;
|
|
|
|
vonets,var11n-300)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan" "4:wan" "6@eth0"
|
|
|
|
;;
|
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_add_switch "switch0" \
|
|
|
|
"5:lan" "4:wan" "6@eth0"
|
|
|
|
;;
|
2021-05-16 15:21:09 +02:00
|
|
|
youku,yk-l1|\
|
|
|
|
youku,yk-l1c)
|
2021-03-21 10:01:49 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan" "1:lan" "4:wan" "6@eth0"
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
zbtlink,zbt-we1026-5g-16m)
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
"0:lan" "6t@eth0"
|
|
|
|
;;
|
|
|
|
zyxel,keenetic-viva)
|
|
|
|
ucidef_add_switch "switch1" \
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "7t@eth0"
|
|
|
|
;;
|
|
|
|
esac
|
|
|
|
}
|
|
|
|
|
|
|
|
ramips_setup_macs()
|
|
|
|
{
|
|
|
|
local board="$1"
|
|
|
|
local lan_mac=""
|
|
|
|
local wan_mac=""
|
|
|
|
local label_mac=""
|
|
|
|
|
|
|
|
case $board in
|
ramips: remove default case for MAC address assignment
So far, MAC address assignment in ramips has contained a default
case, which defined wan_mac = eth0 + 1 for _every_ device not
having an explicit case there.
This is not desirable, as many device supporters will just not
care or know about this definition, so another MAC address will be
introduced by accident. In some cases the wan_mac is assigned
although it is not needed, in other cases even addresses not
dedicated to the device will be used (e.g. wan_mac actually is
eth0 - 1, but during support nobody cared, so eth0 + 1 is used now,
which might actually belong to another device ...).
Thus, in this PR the former default case is converted to an
explicit case. This one comprises all devices not being accounted
for by other cases, reduced by those not having wan at all.
The big number of entries for this node might be another indication
that many of them wouldn't actually be there if there hadn't been
default wan_mac setup.
In exchange, the current "do nothing" case can be removed, as it
will be the new default case.
The devices being put in the newly created explicit case were
determined as follows:
1. Create a list of all devices based on the DTS files.
2. Remove all devices already having an explicit entry setting
their address.
3. Remove all devices that only have lan set up in the first part
of 02_network:
mt7620:
- alfa-network,tube-e4g
- asus,rp-n53
- buffalo,wmr-300
- comfast,cf-wr800n
- edimax,ew-7476rpc
- edimax,ew-7478ac
- elecom,wrh-300cr
- hnet,c108
- kimax,u25awf-h1
- kimax,u35wf
- kingston,mlw221
- kingston,mlwg2
- microduino,microwrt
- netgear,ex2700
- netgear,ex3700
- netgear,wn3000rp-v3
- planex,cs-qr10
- planex,mzk-ex300np
- planex,mzk-ex750np
- ravpower,wd03
- sercomm,na930
- yukai,bocco
- zbtlink,zbt-cpe102
- zte,q7
mt7621:
- gnubee,gb-pc1
- gnubee,gb-pc2
- linksys,re6500
- mikrotik,rbm11g
- netgear,ex6150
- thunder,timecloud
- tplink,re350-v1
- tplink,re650-v1
mt76x8:
- alfa-network,awusfree1
- d-team,pbr-d1
- glinet,vixmini
- vocore,vocore2-lite
- tama,w06
- tplink,tl-mr3020-v3
- tplink,tl-wa801nd-v5
- tplink,tl-wr802n-v4
- tplink,tl-wr902ac-v3
- vocore,vocore2
- widora,neo-16m
- widora,neo-32m
rt288x:
- buffalo,wli-tx4-ag300n
- dlink,dap-1522-a1
rt305x:
- allnet,all0256n-4m
- allnet,all0256n-8m
- allnet,all5002
- allnet,all5003
- alphanetworks,asl26555-16m
- alphanetworks,asl26555-8m
- asus,wl-330n
- aximcom,mr-102n
- dlink,dcs-930
- easyacc,wizard-8800
- hame,mpr-a2
- hootoo,ht-tm02
- huawei,d105
- intenso,memory2move
- planex,mzk-dp150n
- rt305x dlink,dcs-930l-b1
- sparklan,wcr-150gn
- tenda,3g150b
- tenda,3g300m
- tenda,w150m
- trendnet,tew-638apb-v2
- unbranded,a5-v11
- vocore,vocore-16m
- vocore,vocore-8m
- wansview,ncs601w
- zorlik,zl5900v2
rt3883:
- loewe,wmdr-143n
- omnima,hpm
4. Put the remaining devices in the new case.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-10-22 19:04:27 +02:00
|
|
|
aigale,ai-br100|\
|
|
|
|
asus,rt-n12p|\
|
|
|
|
asus,rt-n14u|\
|
|
|
|
bdcom,wap2100-sk|\
|
|
|
|
edimax,ew-7478apc|\
|
|
|
|
fon,fon2601|\
|
|
|
|
head-weblink,hdrm200|\
|
ramips: add support for Netgear JWNR2010 v5
Specification:
- CPU: MediaTek MT7620N (580 MHz)
- Flash size: 4 MB NOR SPI
- RAM size: 32 MB DDR1
- Bootloader: U-Boot
- Wireless: MT7620N 2x2 MIMO 802.11b/g/n (2.4 GHz)
- Switch: MT7620 built-in 10/100 switch with vlan support
- Ports: 4x LAN, 1x WAN
- Others: 7x LED, Reset button, UART header on PCB (57600 8N1)
Flash instructions:
1. Use ethernet cable to connect router with PC/Laptop, any router
LAN port will work.
2. To flash openwrt we are using nmrpflash[1].
3. Flash commands:
First we need to identify the correct Ethernet id.
nmrpflash -L
nmrpflash -i net* -f openwrt-ramips-mt7620-netgear_jwnr2010-v5-squashfs-factory.img
This will show something like "Advertising NMRP server on net*..." (net*, *=1,2,3... etc.)
4. Now remove the power cable from router back side and immediately connect it again.
You will see flash notification in CMD window, once it says reboot the device just
plug off the router and plug in again.
Revert to stock:
1. Download the stock firmware from official netgear support[2].
2. Follow the same nmrpflash procedure like above, this time just use the stock firmware.
nmrpflash -i net* -f N300-V1.1.0.54_1.0.1.img
MAC addresses on stock firmware:
LAN = *:28 (label)
WAN = *:29
WLAN = *:28
On flash, the only valid MAC address is found in factory 0x4.
Special Note:
This openwrt firmware will also support other netgear N300 routers like below as they
share same stock firmware[3].
JNR1010v2 / WNR614 / WNR618 / JWNR2000v5 / WNR2020 / WNR1000v4 / WNR2020v2 / WNR2050
[1] https://github.com/jclehner/nmrpflash
[2] https://www.netgear.com/support/product/JWNR2010v5.aspx
[3] http://kb.netgear.com/000059663
Signed-off-by: Shibajee Roy <ador250@protonmail.com>
[create DTSI, use netgear_sercomm_nor, disable by default, add MAC
addresses to commit message, add label MAC address]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-08-02 17:19:52 +02:00
|
|
|
netgear,jwnr2010-v5|\
|
ramips: remove default case for MAC address assignment
So far, MAC address assignment in ramips has contained a default
case, which defined wan_mac = eth0 + 1 for _every_ device not
having an explicit case there.
This is not desirable, as many device supporters will just not
care or know about this definition, so another MAC address will be
introduced by accident. In some cases the wan_mac is assigned
although it is not needed, in other cases even addresses not
dedicated to the device will be used (e.g. wan_mac actually is
eth0 - 1, but during support nobody cared, so eth0 + 1 is used now,
which might actually belong to another device ...).
Thus, in this PR the former default case is converted to an
explicit case. This one comprises all devices not being accounted
for by other cases, reduced by those not having wan at all.
The big number of entries for this node might be another indication
that many of them wouldn't actually be there if there hadn't been
default wan_mac setup.
In exchange, the current "do nothing" case can be removed, as it
will be the new default case.
The devices being put in the newly created explicit case were
determined as follows:
1. Create a list of all devices based on the DTS files.
2. Remove all devices already having an explicit entry setting
their address.
3. Remove all devices that only have lan set up in the first part
of 02_network:
mt7620:
- alfa-network,tube-e4g
- asus,rp-n53
- buffalo,wmr-300
- comfast,cf-wr800n
- edimax,ew-7476rpc
- edimax,ew-7478ac
- elecom,wrh-300cr
- hnet,c108
- kimax,u25awf-h1
- kimax,u35wf
- kingston,mlw221
- kingston,mlwg2
- microduino,microwrt
- netgear,ex2700
- netgear,ex3700
- netgear,wn3000rp-v3
- planex,cs-qr10
- planex,mzk-ex300np
- planex,mzk-ex750np
- ravpower,wd03
- sercomm,na930
- yukai,bocco
- zbtlink,zbt-cpe102
- zte,q7
mt7621:
- gnubee,gb-pc1
- gnubee,gb-pc2
- linksys,re6500
- mikrotik,rbm11g
- netgear,ex6150
- thunder,timecloud
- tplink,re350-v1
- tplink,re650-v1
mt76x8:
- alfa-network,awusfree1
- d-team,pbr-d1
- glinet,vixmini
- vocore,vocore2-lite
- tama,w06
- tplink,tl-mr3020-v3
- tplink,tl-wa801nd-v5
- tplink,tl-wr802n-v4
- tplink,tl-wr902ac-v3
- vocore,vocore2
- widora,neo-16m
- widora,neo-32m
rt288x:
- buffalo,wli-tx4-ag300n
- dlink,dap-1522-a1
rt305x:
- allnet,all0256n-4m
- allnet,all0256n-8m
- allnet,all5002
- allnet,all5003
- alphanetworks,asl26555-16m
- alphanetworks,asl26555-8m
- asus,wl-330n
- aximcom,mr-102n
- dlink,dcs-930
- easyacc,wizard-8800
- hame,mpr-a2
- hootoo,ht-tm02
- huawei,d105
- intenso,memory2move
- planex,mzk-dp150n
- rt305x dlink,dcs-930l-b1
- sparklan,wcr-150gn
- tenda,3g150b
- tenda,3g300m
- tenda,w150m
- trendnet,tew-638apb-v2
- unbranded,a5-v11
- vocore,vocore-16m
- vocore,vocore-8m
- wansview,ncs601w
- zorlik,zl5900v2
rt3883:
- loewe,wmdr-143n
- omnima,hpm
4. Put the remaining devices in the new case.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-10-22 19:04:27 +02:00
|
|
|
nexx,wt3020-4m|\
|
|
|
|
nexx,wt3020-8m|\
|
|
|
|
phicomm,psg1208|\
|
|
|
|
planex,db-wrt01|\
|
|
|
|
planex,mzk-750dhp|\
|
|
|
|
sanlinking,d240|\
|
|
|
|
vonets,var11n-300|\
|
|
|
|
wrtnode,wrtnode|\
|
|
|
|
zbtlink,zbt-ape522ii|\
|
|
|
|
zbtlink,zbt-wa05|\
|
|
|
|
zbtlink,zbt-we2026|\
|
|
|
|
zbtlink,zbt-we826-16m|\
|
|
|
|
zbtlink,zbt-we826-32m|\
|
|
|
|
zbtlink,zbt-we826-e|\
|
|
|
|
zbtlink,zbt-wr8305rt)
|
2019-12-08 13:20:50 +01:00
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 0x4)" 1)
|
|
|
|
;;
|
|
|
|
alfa-network,ac1200rm|\
|
|
|
|
dlink,dir-810l|\
|
2020-05-26 03:24:40 +02:00
|
|
|
trendnet,tew-810dr)
|
2019-12-08 13:20:50 +01:00
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 0x28)" 1)
|
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|\
|
2021-07-27 06:32:00 +02:00
|
|
|
domywifi,dm202|\
|
|
|
|
domywifi,dm203|\
|
|
|
|
domywifi,dw22d|\
|
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
|
|
|
zbtlink,zbt-we1026-h-32m)
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x2e)
|
|
|
|
label_mac=$(mtd_get_mac_binary factory 0x4)
|
|
|
|
;;
|
2020-05-18 21:26:20 +02:00
|
|
|
asus,rt-ac51u|\
|
ramips: add support for ASUS RT-AC54U
Specification:
- CPU: MTK MT7620A
- RAM: 64MB
- ROM: 16MB SPI Flash Macronix MX25L12835E
- WiFi1: MediaTek MT7620A
- WiFi2: MediaTek MT7612E
- Button: reset, wps
- LED: 9 LEDs:Power, WiFi 2.4G,WiFi 5G, USB, LAN1, LAN2, LAN3, LAN4, WAN
- Ethernet: 5 ports, 4 LAN + 1 WAN
- Other: 1x UART 1x USB2.0
Installation:
Update using ASUS Firmware Restoration Tool:
1. Download the ASUS Firmware Restoration Tool but don't open it yet
2. Unplug your computer from the router
3. Put the router into Rescue Mode by: turning the power off, using a pin
to press and hold the reset button, then turning the router back on while
keeping the reset button pressed for ~5 secs until the power LED starts
flashing slowly (which indicates the router has entered Rescue Mode)
4. Important (if you don't do this next step the Asus Firmware
Restoration Tool will wrongly assume that the router is not in Rescue Mode
and will refuse to flash it): go to the Windows Control Panel and
temporarily disable ALL other network adapters except the one you will use
to connect your computer to the router
5. For the single adapter you left enabled, temporarily give it the
static IP 192.168.1.10 and the subnet mask 255.255.255.0
6. Connect a LAN cable between your computer (make sure to use the
Ethernet port of the adapter you've just set up) and port 1 of the router
(not the router's WAN port)
7. Rename sysupgrade.bin to factory.trx
8. Open the Asus Firmware Restoration Tool, locate factory.trx and click
upload (if Windows shows a compatibility prompt, confirm that the tool worked fine)
9. Flashing and reboot is finished when the power LED stops blinking and
stays on
MAC assignment based on vendor firmware:
2g 0x4 label
5g 0x8004 label +4
lan 0x22 label +4
wan 0x28 label
Signed-off-by: Zhijun You <hujy652@gmail.com>
[rebased due to DTSI patch, minor commit message adjustments, fix
label MAC address (lan->wan), do spi frequency increase separately]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-05-14 13:37:40 +02:00
|
|
|
asus,rt-ac54u)
|
2020-05-18 21:38:00 +02:00
|
|
|
lan_mac=$(mtd_get_mac_binary factory 0x22)
|
ramips: add support for ASUS RT-AC54U
Specification:
- CPU: MTK MT7620A
- RAM: 64MB
- ROM: 16MB SPI Flash Macronix MX25L12835E
- WiFi1: MediaTek MT7620A
- WiFi2: MediaTek MT7612E
- Button: reset, wps
- LED: 9 LEDs:Power, WiFi 2.4G,WiFi 5G, USB, LAN1, LAN2, LAN3, LAN4, WAN
- Ethernet: 5 ports, 4 LAN + 1 WAN
- Other: 1x UART 1x USB2.0
Installation:
Update using ASUS Firmware Restoration Tool:
1. Download the ASUS Firmware Restoration Tool but don't open it yet
2. Unplug your computer from the router
3. Put the router into Rescue Mode by: turning the power off, using a pin
to press and hold the reset button, then turning the router back on while
keeping the reset button pressed for ~5 secs until the power LED starts
flashing slowly (which indicates the router has entered Rescue Mode)
4. Important (if you don't do this next step the Asus Firmware
Restoration Tool will wrongly assume that the router is not in Rescue Mode
and will refuse to flash it): go to the Windows Control Panel and
temporarily disable ALL other network adapters except the one you will use
to connect your computer to the router
5. For the single adapter you left enabled, temporarily give it the
static IP 192.168.1.10 and the subnet mask 255.255.255.0
6. Connect a LAN cable between your computer (make sure to use the
Ethernet port of the adapter you've just set up) and port 1 of the router
(not the router's WAN port)
7. Rename sysupgrade.bin to factory.trx
8. Open the Asus Firmware Restoration Tool, locate factory.trx and click
upload (if Windows shows a compatibility prompt, confirm that the tool worked fine)
9. Flashing and reboot is finished when the power LED stops blinking and
stays on
MAC assignment based on vendor firmware:
2g 0x4 label
5g 0x8004 label +4
lan 0x22 label +4
wan 0x28 label
Signed-off-by: Zhijun You <hujy652@gmail.com>
[rebased due to DTSI patch, minor commit message adjustments, fix
label MAC address (lan->wan), do spi frequency increase separately]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-05-14 13:37:40 +02:00
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
dlink,dch-m225)
|
|
|
|
lan_mac=$(mtd_get_mac_ascii factory lanmac)
|
|
|
|
;;
|
|
|
|
dlink,dir-510l|\
|
|
|
|
dlink,dwr-116-a1|\
|
|
|
|
dlink,dwr-118-a1|\
|
|
|
|
dlink,dwr-118-a2|\
|
|
|
|
dlink,dwr-921-c1|\
|
|
|
|
dlink,dwr-922-e2|\
|
2018-04-19 09:20:58 +02:00
|
|
|
dlink,dwr-960|\
|
2019-10-22 12:37:13 +02:00
|
|
|
lava,lr-25g001)
|
|
|
|
wan_mac=$(jboot_config_read -m -i $(find_mtd_part "config") -o 0xE000)
|
|
|
|
lan_mac=$(macaddr_add "$wan_mac" 1)
|
|
|
|
label_mac=$wan_mac
|
|
|
|
;;
|
|
|
|
dovado,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)
|
|
|
|
;;
|
|
|
|
edimax,br-6478ac-v2)
|
2019-12-08 13:20:50 +01:00
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 0x4)" 2)
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
engenius,esr600)
|
|
|
|
lan_mac=$(mtd_get_mac_ascii u-boot-env ethaddr)
|
|
|
|
wan_mac=$(mtd_get_mac_ascii u-boot-env wanaddr)
|
|
|
|
;;
|
|
|
|
glinet,gl-mt300a|\
|
|
|
|
glinet,gl-mt300n|\
|
|
|
|
glinet,gl-mt750)
|
2019-12-08 13:20:50 +01:00
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary factory 0x4000)" 1)
|
2019-11-11 00:18:45 +01:00
|
|
|
label_mac=$(mtd_get_mac_binary factory 0x4)
|
2019-10-22 12:37:13 +02:00
|
|
|
;;
|
|
|
|
hiwifi,hc5661|\
|
|
|
|
hiwifi,hc5761|\
|
|
|
|
hiwifi,hc5861)
|
|
|
|
lan_mac=$(mtd_get_mac_ascii bdinfo "Vfac_mac ")
|
|
|
|
label_mac=$lan_mac
|
|
|
|
[ -n "$lan_mac" ] || lan_mac=$(cat /sys/class/net/eth0/address)
|
|
|
|
wan_mac=$(macaddr_add "$lan_mac" 1)
|
|
|
|
;;
|
|
|
|
iodata,wn-ac1167gr|\
|
|
|
|
iodata,wn-ac733gr3)
|
|
|
|
wan_mac=$(mtd_get_mac_ascii u-boot-env wanaddr)
|
|
|
|
;;
|
2019-09-26 17:21:25 +02:00
|
|
|
iptime,a1004ns)
|
|
|
|
wan_mac=$(mtd_get_mac_binary u-boot 0x1fc40)
|
|
|
|
;;
|
2019-09-26 17:16:33 +02:00
|
|
|
iptime,a104ns)
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary u-boot 0x1fc20)" 2)
|
|
|
|
;;
|
2021-02-22 16:44:18 +01:00
|
|
|
lb-link,bl-w1200|\
|
ramips: add new flash layout support to Phicomm K2
Descriptions:
Phicomm K2 (PSG1218) got a new "permanent_config" partition after
update firmware to v22.5. This partition located in front of the
firmware partition, same as The Phicomm K2P and K2G. Due to this
change the new bootloader can't load previous firmware any more.
This commit is aimed at add support for Phicomm K2 which official
firmware version is 22.5.x or newer. For which runs old firmware
version, just update OpenWrt that has a prefix of "k2-v22.4".
For uniform naming, this commit also changed the model name
PSG1218 to a more recognizable name K2, refer to Phicomm K2G,
K2P K2T.
OpenWrt selection table:
official firmware version OpenWrt
v22.4.x.x or older phicomm_k2-v22.4
v22.5.x.x or newer phicomm_k2-v22.5
Installation:
Same as Phicomm K2G, K2P, PSG1208.
a. TFTP + U-Boot
b. Open telnet by some web page vulnerability (Search Baidu by key
words "K2 telnet"), and then we can upload firmware image to
/tmp and write it to firmware partition with mtd instruction.
Signed-off-by: Shiji Yang <yangshiji66@qq.com>
[rebase, add/harmonize version in model variables, fix version typo
in commit message, wrap commit message properly]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2021-07-27 06:45:05 +02:00
|
|
|
phicomm,k2-v22.4|\
|
|
|
|
phicomm,k2-v22.5|\
|
2021-02-22 16:44:18 +01:00
|
|
|
phicomm,k2g|\
|
|
|
|
phicomm,psg1218b)
|
2020-04-17 22:31:11 +02:00
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x2e)
|
|
|
|
label_mac=$wan_mac
|
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
lenovo,newifi-y1|\
|
|
|
|
lenovo,newifi-y1s|\
|
|
|
|
ohyeah,oy-0001|\
|
2021-05-05 13:48:01 +02:00
|
|
|
wavlink,wl-wn530hg4|\
|
2021-05-16 15:21:09 +02:00
|
|
|
youku,yk-l1|\
|
|
|
|
youku,yk-l1c)
|
2019-10-22 12:37:13 +02:00
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x2e)
|
|
|
|
;;
|
|
|
|
linksys,e1700)
|
|
|
|
wan_mac=$(mtd_get_mac_ascii config WAN_MAC_ADDR)
|
|
|
|
;;
|
2019-11-11 17:23:07 +01:00
|
|
|
netis,wf2770)
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x2e)
|
|
|
|
label_mac=$wan_mac
|
|
|
|
;;
|
2019-12-08 13:20:50 +01:00
|
|
|
tplink,archer-c2-v1|\
|
|
|
|
tplink,archer-c20-v1|\
|
|
|
|
tplink,archer-c20i|\
|
|
|
|
tplink,archer-c50-v1|\
|
|
|
|
tplink,archer-mr200)
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary rom 0xf100)" 1)
|
|
|
|
;;
|
2019-11-02 15:18:54 +01:00
|
|
|
zbtlink,zbt-we1026-5g-16m)
|
2019-11-11 00:18:45 +01:00
|
|
|
label_mac=$(mtd_get_mac_binary factory 0x4)
|
2019-11-02 15:18:54 +01:00
|
|
|
;;
|
2019-10-22 12:37:13 +02:00
|
|
|
zyxel,keenetic-omni|\
|
|
|
|
zyxel,keenetic-omni-ii|\
|
|
|
|
zyxel,keenetic-viva)
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x28)
|
|
|
|
;;
|
|
|
|
esac
|
|
|
|
|
|
|
|
[ -n "$lan_mac" ] && ucidef_set_interface_macaddr "lan" $lan_mac
|
|
|
|
[ -n "$wan_mac" ] && ucidef_set_interface_macaddr "wan" $wan_mac
|
|
|
|
[ -n "$label_mac" ] && ucidef_set_label_macaddr $label_mac
|
|
|
|
}
|
|
|
|
|
|
|
|
board_config_update
|
|
|
|
board=$(board_name)
|
|
|
|
ramips_setup_interfaces $board
|
|
|
|
ramips_setup_macs $board
|
|
|
|
board_config_flush
|
|
|
|
|
|
|
|
exit 0
|