|
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
|
|
. /lib/functions/system.sh
|
|
|
|
|
. /lib/functions/uci-defaults.sh
|
|
|
|
|
. /lib/functions/k2t.sh
|
|
|
|
|
|
|
|
|
|
ath79_setup_interfaces()
|
|
|
|
|
{
|
|
|
|
|
local board="$1"
|
|
|
|
|
|
|
|
|
|
case "$board" in
|
ath79: add support for Bluesocket BSAP1880 board
This board was used in dual-band 802.11n enterprise access points, models
BSAP-1800v2 and BSAP-1840, introduced in 2010 by Bluesocket, which was
acquired by Adtran in 2011, who has now EOL'ed them. They differed only in
that the BSAP-1840's antennae were detachable, while the BSAP-1800v2's were
inside the case. They have an external RJ-45 console port, which works with
standard Cisco 72-3383-01 console cables.
Specification:
- System-On-Chip: AR7161
- CPU/Speed: 600 MHz
- Flash-Chip: Macronix MX25L12845E
- Flash size: 16 MiB
- RAM: 64 MiB
- Wireless No1: Lite-On WN2601A card: AR9160/AR9103 2.4GHz 802.11bgn
- Wireless No2: Lite-On WN2502A card: AR9160/AR9106 5GHz 802.11an
- PHY: Vitesse VSC8601, Rev. B
Installation:
1. Connect to the serial console using a terminal that supports YMODEM at
115200 bps, 8 data bits, no parity, 1 stop bit
2. Interrupt the bootloader using its password, which is: r00t
3. Issue the "fis init" command, confirming if prompted
4. Look at the length of the openwrt-ath79-generic-*-squashfs-kernel.bin
file, and substitute it below, instead of where I have "LeNgTh"
5. Issue the following command, and upload this file using YMODEM protocol
load -r -v -b 0x80060000 -m ymodem
6. Issue the following commands, substituting as mentioned above:
fis create -b 0x80060000 -l LeNgTh vmlinux_2
load -r -v -b 0x80100000 -m ymodem
7. Using YMODEM, upload openwrt-ath79-generic-*-squashfs-rootfs.bin
8. Issue the "fis free" command, and for the first range in its response,
use a hexadecimal calculator to subtract the start from the end in order
to substitute it below, with the leading "0x" to specify it in
hexadecimal, instead of where I have "LeNgTh"
9. Issue the following commands, substituting as mentioned above:
fis create -b 0x80100000 -l LeNgTh -e 0 -r 0 rootfs
reset
10.Wait for the status LED to go solid green
Tested-by: Brian Gonyer <bgonyer@gmail.com>
Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
[fixed obsolete $ARGV in platform_do_upgrade]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
6 years ago
|
|
|
adtran,bsap1800-v2|\
|
|
|
|
|
adtran,bsap1840|\
|
|
|
|
|
alfa-network,ap121f|\
|
|
|
|
|
aruba,ap-105|\
|
|
|
|
|
avm,fritz300e|\
|
|
|
|
|
devolo,dvl1200i|\
|
|
|
|
|
devolo,dvl1750c|\
|
|
|
|
|
devolo,dvl1750i|\
|
|
|
|
|
devolo,dvl1750x|\
|
|
|
|
|
engenius,ecb1750|\
|
|
|
|
|
glinet,gl-ar300m-lite|\
|
ath79: add support for Netgear EX6400 and EX7300
This is sold as a dual-band 802.11ac range extender. It has a sliding
switch for Extender mode or Access Point mode, a WPS button, a recessed
Reset button, a hard-power button, and a multitude of LED's, some
multiplexed via an NXP 74AHC164D chip. The internal serial header pinout is
Vcc, Tx, Rx, GND, with GND closest to the corner of the board. You may
connect at 115200 bps, 8 data bits, no parity, 1 stop bit.
Specification:
- System-On-Chip: QCA9558
- CPU/Speed: 720 MHz
- Flash-Chip: Winbond 25Q128FVSG
- Flash size: 16 MiB
- RAM: 128 MiB
- Wireless No1: QCA9558 on-chip 2.4GHz 802.11bgn, 3x3
- Wireless No2: QCA99x0 chip 5GHz 802.11an+ac, 4x4
- PHY: Atheros AR8035-A
Installation:
If you can get to the stock firmware's firmware upgrade option, just feed
it the factory.img and boot as usual. As an alternative, TFTP the
factory.img to the bootloader.
Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
[whitespace fix in DTS and reorder of make variables]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
6 years ago
|
|
|
netgear,ex6400|\
|
|
|
|
|
netgear,ex7300|\
|
|
|
|
|
ocedo,koala|\
|
|
|
|
|
ocedo,raccoon|\
|
|
|
|
|
pcs,cap324|\
|
|
|
|
|
pisen,ts-d084|\
|
|
|
|
|
pisen,wmb001n|\
|
|
|
|
|
pisen,wmm003n|\
|
|
|
|
|
tplink,cpe210-v2|\
|
|
|
|
|
tplink,cpe210-v3|\
|
|
|
|
|
tplink,cpe510-v2|\
|
|
|
|
|
tplink,cpe510-v3|\
|
|
|
|
|
tplink,cpe610-v1|\
|
|
|
|
|
tplink,re350k-v1|\
|
|
|
|
|
tplink,re355-v1|\
|
|
|
|
|
tplink,re450-v1|\
|
|
|
|
|
tplink,re450-v2|\
|
ath79: add support for TP-Link TL-WR902AC v1
TP-Link TL-WR902AC v1 is a pocket-size, dual-band (AC750), successor of
TL-MR3020 (both devices use very similar enclosure, in same size). New
device is based on Qualcomm QCA9531 v2 + QCA9887. FCC ID: TE7WR902AC.
Specification:
- 650/391/216 MHz (CPU/DDR/AHB)
- 1x 10/100 Mbps Ethernet
- 1x USB 2.0 (GPIO-controlled power)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz (QCA9531)
- 1T1R 5 GHz (QCA9887)
- 5x LED (GPIO-controlled), 2x button, 1x 3-pos switch
- UART pads on PCB (TP1 -> TX, TP2 -> RX, TP3 -> GND, TP4 -> 3V3, jumper
resitors are missing on TX/RX lines)
- 1x micro USB (for power only)
Flash instructions:
Use "factory" image under vendor GUI.
Recovery instructions:
This device contains tftp recovery mode inside U-Boot. You can use it to
flash OpenWrt (use "factory" image) or vendor firmware.
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "openwrt-ath79-generic-tplink_tl-wr902ac-v1-squashfs-factory.bin"
to "wr902acv1_un_tp_recovery.bin" and place it in tftp server dir.
3. Connect PC with LAN port, press the reset button, power up the router
and keep button pressed until WPS LED lights up.
4. Router will download file from server, write it to flash and reboot.
MAC Address summary:
- wlan1 (2.4GHz Wi-Fi): Label MAC
- wlan0 (5GHz Wi-Fi): Offset -1 from label
- eth0 (Wired): Offset +1 from label
Root access over serial line in vendor firmware: root/sohoadmin.
Based on support in ar71xx target by: Piotr Dymacz <pepe2k@gmail.com>
Signed-off-by: Lech Perczak <lech.perczak@gmail.com>
[remove size-cells from gpio-export]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
tplink,tl-wr902ac-v1|\
|
|
|
|
|
ubnt,bullet-m|\
|
|
|
|
|
ubnt,bullet-m-xw|\
|
|
|
|
|
ubnt,lap-120|\
|
|
|
|
|
ubnt,litebeam-ac-gen2|\
|
|
|
|
|
ubnt,nanobeam-ac|\
|
|
|
|
|
ubnt,nanostation-ac-loco|\
|
|
|
|
|
ubnt,rocket-m|\
|
|
|
|
|
ubnt,unifiac-lite|\
|
|
|
|
|
ubnt,unifiac-lr|\
|
|
|
|
|
ubnt,unifiac-mesh|\
|
|
|
|
|
ubnt,unifi|\
|
|
|
|
|
wd,mynet-wifi-rangeextender|\
|
|
|
|
|
winchannel,wb2000)
|
|
|
|
|
ucidef_set_interface_lan "eth0"
|
|
|
|
|
;;
|
ath79: add support for Archer C58/C59 v1
This commit adds support for the Archer C58 v1 and C59 v1, previously
supported in the ar71xx target.
CPU: Qualcomm QCA9561
RAM: 64M (C58) / 128M (C59)
FLASH: 8M (C58) / 16M (C59)
WiFi: QCA9561 bgn 3x3:3
QCA9888 nac 2x2:2
LED: Power, WiFi 2.4, WiFi 5, WAN green, WAN amber, LAN, WPS
Only C59: USB
BTN: WPS, WiFi, Reset
Installation
------------
Via Web-UI:
Update factory image via Web-UI.
Via TFTP:
Rename factory image to "tp_recovery.bin" and place it in the root-dir
of your tftp server. Configure to listen on 192.168.0.66. Power up the
router while holding down the reset-button. The router will flash itself
and reboot.
Note: For TFTP, you might need a switch between router and computer, as
link establishment might take to long.
Signed-off-by: David Bauer <mail@david-bauer.net>
6 years ago
|
|
|
avm,fritz4020|\
|
|
|
|
|
pcs,cr3000|\
|
ath79: add support for Archer C58/C59 v1
This commit adds support for the Archer C58 v1 and C59 v1, previously
supported in the ar71xx target.
CPU: Qualcomm QCA9561
RAM: 64M (C58) / 128M (C59)
FLASH: 8M (C58) / 16M (C59)
WiFi: QCA9561 bgn 3x3:3
QCA9888 nac 2x2:2
LED: Power, WiFi 2.4, WiFi 5, WAN green, WAN amber, LAN, WPS
Only C59: USB
BTN: WPS, WiFi, Reset
Installation
------------
Via Web-UI:
Update factory image via Web-UI.
Via TFTP:
Rename factory image to "tp_recovery.bin" and place it in the root-dir
of your tftp server. Configure to listen on 192.168.0.66. Power up the
router while holding down the reset-button. The router will flash itself
and reboot.
Note: For TFTP, you might need a switch between router and computer, as
link establishment might take to long.
Signed-off-by: David Bauer <mail@david-bauer.net>
6 years ago
|
|
|
tplink,archer-c58-v1|\
|
|
|
|
|
tplink,archer-c59-v1|\
|
|
|
|
|
tplink,archer-c59-v2)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan:1" "2:lan:4" "3:lan:3" "4:lan:2"
|
|
|
|
|
;;
|
|
|
|
|
buffalo,bhr-4grv|\
|
|
|
|
|
buffalo,wzr-hp-g450h)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "2:lan" "3:lan" "4:lan" "5:lan" "1:wan"
|
|
|
|
|
;;
|
|
|
|
|
buffalo,bhr-4grv2|\
|
|
|
|
|
trendnet,tew-823dru)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth1" "1:lan" "2:lan" "3:lan" "4:lan" "5:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
buffalo,wzr-hp-ag300h|\
|
|
|
|
|
tplink,archer-c25-v1|\
|
|
|
|
|
tplink,tl-wdr3500-v1|\
|
|
|
|
|
tplink,tl-wr842n-v1|\
|
|
|
|
|
tplink,tl-wr842n-v3|\
|
|
|
|
|
ubnt,airrouter)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1"
|
|
|
|
|
;;
|
|
|
|
|
buffalo,wzr-hp-g302h-a1a0)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan:1" "3:lan:4" "4:lan:3" "5:lan:2" "2:wan"
|
|
|
|
|
;;
|
|
|
|
|
comfast,cf-e110n-v2|\
|
|
|
|
|
comfast,cf-e120a-v3|\
|
|
|
|
|
comfast,cf-e314n-v2|\
|
|
|
|
|
tplink,cpe210-v1|\
|
|
|
|
|
tplink,cpe220-v2|\
|
|
|
|
|
tplink,cpe220-v3|\
|
|
|
|
|
tplink,cpe510-v1|\
|
|
|
|
|
tplink,wbs210-v2|\
|
|
|
|
|
tplink,wbs510-v1|\
|
|
|
|
|
tplink,wbs510-v2|\
|
|
|
|
|
ubnt,nanostation-m|\
|
|
|
|
|
ubnt,routerstation)
|
|
|
|
|
ucidef_set_interfaces_lan_wan "eth1" "eth0"
|
|
|
|
|
;;
|
|
|
|
|
comfast,cf-wr650ac-v1|\
|
|
|
|
|
comfast,cf-wr650ac-v2)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan" "2:lan" "3:lan" "4:lan" "5:wan" "6@eth1"
|
|
|
|
|
;;
|
|
|
|
|
devolo,dvl1200e|\
|
|
|
|
|
devolo,dvl1750e|\
|
|
|
|
|
ocedo,ursus)
|
|
|
|
|
ucidef_set_interface_lan "eth0 eth1"
|
|
|
|
|
;;
|
|
|
|
|
dlink,dir-825-b1)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "5@eth0"
|
|
|
|
|
;;
|
|
|
|
|
dlink,dir-825-c1|\
|
|
|
|
|
dlink,dir-835-a1|\
|
|
|
|
|
dlink,dir-842-c1|\
|
|
|
|
|
dlink,dir-842-c2|\
|
|
|
|
|
dlink,dir-842-c3|\
|
|
|
|
|
dlink,dir-859-a1|\
|
ath79: add suport for EnGenius EPG5000
EnGenius EPG5000 (v1.0.0, marketed as IoT Gateway) is a dual band
wireless router.
Specification
SoC: Qualcomm Atheros QCA9558
RAM: 256 MB DDR2
Flash: 16 MB SPI NOR
WIFI: 2.4 GHz 3T3R integrated
5 GHz 3T3R QCA9880 Mini PCIe card
Ethernet: 5x 10/100/1000 Mbps QCA8337N
USB: 1x 2.0
LEDS: 4x GPIO controlled
Buttons: 2x GPIO controlled
UART: 4 pin header, starting count from white triangle on PCB
1. VCC 3.3V, 2. GND, 3. TX, 4. RX
baud: 115200, parity: none, flow control: none
Installation
1. Connect to one of LAN (yellow) ethernet ports,
2. Open router configuration interface,
3. Go to Tools > Firmware,
4. Select OpenWrt factory image with dlf extension and hit Apply,
5. Wait few minutes, after the Power LED will stop blinking, the router
is ready for configuration.
Alternative installation
1. Prepare TFTP server with OpenWrt sysupgrade image,
2. Connect to one of LAN (yellow) ethernet ports,
3. Connect to UART port (leaving out VCC pin!),
4. Power on router,
5. When asked to enter a number 1 or 3 hit 2, this will select flashing
image from TFTP server option,
6. You'll be prompted to enter TFTP server ip (default is 192.168.99.8),
then router ip (default is 192.168.99.9) and for last, image name
downloaded from TFTP server (default is uImageESR1200_1750),
7. After providing all information U-Boot will start flashing the image,
You can observe progress on console, it'll take few minutes and when
the Power LED will stop blinking, router is ready for configuration.
Additional information
If connected to UART, when prompted for number on boot, one can enter
number 4 to open bootloader (U-Boot) command line.
OEM firmware shell password is: aigo3d0a0tdagr
useful for creating backup of original firmware.
When doing upgrade from OpenWrt ar71xx image, it is recomended to not keep
the old configuration.
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
5 years ago
|
|
|
engenius,epg5000|\
|
|
|
|
|
tplink,archer-c2-v3|\
|
|
|
|
|
tplink,tl-wr1043nd-v4|\
|
|
|
|
|
tplink,tl-wr1043n-v5)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "5:wan"
|
|
|
|
|
;;
|
|
|
|
|
elecom,wrc-1750ghbk2-i|\
|
|
|
|
|
elecom,wrc-300ghbk2-i)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "2:lan:4" "3:lan:3" "4:lan:2" "5:lan:1" "1:wan"
|
|
|
|
|
;;
|
|
|
|
|
embeddedwireless,dorin)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:wan" "2:lan:3" "3:lan:2"
|
|
|
|
|
;;
|
|
|
|
|
engenius,ews511ap)
|
|
|
|
|
ucidef_set_interface_lan "eth0 eth1" "dhcp"
|
|
|
|
|
;;
|
|
|
|
|
etactica,eg200)
|
|
|
|
|
ucidef_set_interface_lan "eth0" "dhcp"
|
|
|
|
|
;;
|
|
|
|
|
glinet,gl-ar750)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan" "2:lan"
|
|
|
|
|
;;
|
|
|
|
|
iodata,etg3-r|\
|
|
|
|
|
iodata,wn-ac1167dgr|\
|
|
|
|
|
iodata,wn-ac1600dgr|\
|
|
|
|
|
iodata,wn-ac1600dgr2|\
|
|
|
|
|
iodata,wn-ag300dgr|\
|
|
|
|
|
pcs,cr5000|\
|
ath79: add support for Sitecom WLR-7100
Sitecom WLR-7100 v1 002 (marketed as X7 AC1200) is a dual band wireless
router.
Specification
SoC: Atheros AR1022
RAM: 64 MB DDR2
Flash: 8 MB SPI NOR
WIFI: 2.4 GHz 2T2R integrated
5 GHz 2T2R QCA9882 integrated (connected to PCIe lane)
Ethernet: 5x 10/100/1000 Mbps QCA8337N
USB: 1x 2.0
LEDS: 4x GPIO controlled, 5x switch
Buttons: 2x GPIO controlled
UART: row of 4 unpopulated holes near USB port, starting count from
white triangle on PCB
1. VCC 3.3V, 2. GND, 3. TX, 4. RX
baud: 115200, parity: none, flow control: none
Installation
1. Connect to one of LAN (yellow) ethernet ports,
2. Open router configuration interface,
3. Go to Toolbox > Firmware,
4. Browse for OpenWrt factory image with dlf extension and hit Apply,
5. Wait few minutes, after the Power LED will stop blinking, the router
is ready for configuration.
Known issues
5GHz LED doesn't work
Additional information
When TX line on UART is connected, and board is switched on from power
off state, the DDR memory training may fail.
If connected to UART, when prompted for number on boot, one can enter
number 4 to open bootloader (U-Boot) command line.
OEM firmware shell password is: SitecomSenao
useful for creating backup of original firmware.
There is also another revision of this device (v1 001), which may or may
not work with introduced images.
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
5 years ago
|
|
|
sitecom,wlr-7100|\
|
|
|
|
|
wd,mynet-n750)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan" "2:lan" "3:lan" "4:lan" "5:wan"
|
|
|
|
|
;;
|
|
|
|
|
librerouter,librerouter-v1)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "5:wan" "6@eth1" "4:lan"
|
|
|
|
|
;;
|
|
|
|
|
nec,wg1200cr|\
|
|
|
|
|
ubnt,nanostation-ac|\
|
|
|
|
|
ubnt,unifiac-mesh-pro|\
|
ath79: add support for YunCore XD4200 and A782
YunCore XD4200 ('XD4200_W6.0' marking on PCB) is Qualcomm/Atheros based
(QCA9563, QCA9886, QCA8334) dual-band, Wave-2 AC1200 ceiling AP with PoE
(802.3at) support. A782 model ('T750_V5.1' marking on PCB) is a smaller
version of the XD4200, with similar specification but lower TX power.
Specification:
- QCA9563 (775 MHz)
- 128 MB of RAM (DDR2)
- 16 MB of FLASH (SPI NOR)
- 2x 10/100/1000 Mbps Ethernet (QCA8334), with 802.3at PoE support (WAN)
- Wi-Fi 2.4 GHz:
- XD4200: 2T2R (QCA9563), with ext. PA (SKY65174-21) and LNA
- A782: 2T2R (QCA9563), with ext. FEM (SKY85329-11)
- Wi-Fi 5 GHz:
- XD4200: 2T2R (QCA9886), with ext. FEM (SKY85728-11)
- A782: 2T2R (QCA9886), with ext. FEM (SKY85735-11)
- LEDs:
- XD4200: 5x (2x driven by SOC, 1x driven by AC radio, 2x Ethernet)
- A782: 3x (1x RGB, driven by SOC and radio, 2x Ethernet)
- 1x button (reset)
- 1x UART (4-pin, 2.54 mm pitch) header on PCB
- 1x DC jack (12 V)
Flash instructions:
If your device comes with generic QSDK based firmware, you can login
over telnet (login: root, empty password, default IP: 192.168.188.253),
issue first (important!) 'fw_setenv' command and then perform regular
upgrade, using 'sysupgrade -n -F ...' (you can use 'wget' to download
image to the device, SSH server is not available):
fw_setenv bootcmd "bootm 0x9f050000 || bootm 0x9fe80000"
sysupgrade -n -F openwrt-...-yuncore_...-squashfs-sysupgrade.bin
In case your device runs firmware with YunCore custom GUI, you can use
U-Boot recovery mode:
1. Set a static IP 192.168.0.141/24 on PC and start TFTP server with
'tftp' image renamed to 'upgrade.bin'
2. Power the device with reset button pressed and release it after 5-7
seconds, recovery mode should start downloading image from server
(unfortunately, there is no visible indication that recovery got
enabled - in case of problems check TFTP server logs)
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
5 years ago
|
|
|
ubnt,unifiac-pro|\
|
|
|
|
|
yuncore,a782|\
|
|
|
|
|
yuncore,xd4200)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "2:lan" "3:wan"
|
|
|
|
|
;;
|
|
|
|
|
nec,wg800hp)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "2:lan" "3:lan" "4:lan" "1:wan"
|
|
|
|
|
;;
|
|
|
|
|
netgear,wndr3700|\
|
|
|
|
|
netgear,wndr3700v2|\
|
|
|
|
|
netgear,wndr3800|\
|
|
|
|
|
netgear,wndr3800ch)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "5u@eth0"
|
|
|
|
|
ucidef_add_switch_attr "switch0" "blinkrate" 2
|
|
|
|
|
ucidef_add_switch_port_attr "switch0" 1 led 6
|
|
|
|
|
ucidef_add_switch_port_attr "switch0" 2 led 9
|
|
|
|
|
ucidef_add_switch_port_attr "switch0" 5 led 2
|
|
|
|
|
;;
|
|
|
|
|
netgear,wnr2200-8m|\
|
|
|
|
|
netgear,wnr2200-16m)
|
|
|
|
|
ucidef_set_interface_wan "eth0"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth1" "1:lan" "2:lan" "3:lan" "4:lan"
|
|
|
|
|
;;
|
|
|
|
|
phicomm,k2t)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "3:lan:1" "5:lan:2" "4:wan"
|
|
|
|
|
;;
|
|
|
|
|
qihoo,c301)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "2:lan" "3:lan"
|
|
|
|
|
;;
|
ath79: add support for ROSINSON WR818 board
This commit adds support for the ROSINSON WR818 WiFi-Router
SoC: Qualcomm Atheros QCA9563,
FLASH: Winbond W25Q128FV 16MBytes,
WiFi: QCA9563 b/g/n 3x3 450Mbit/s,
USB: 1x USB 2.0 Type A, 1x USB2.0 Type C,
IN: WPS/Reset button GPIO1,
OUT: Power LED red, Internet LED red, WLAN LED red,
LAN1 LED red, LAN2 LED red, System LED red,
UART: RX-GPIO18, TX-GPIO22,
Tested and working:
- Ethernet (LAN + WAN)
- WiFi
- OpenWRT sysupgrade
- Button
- LEDs
Installation of OpenWRT from vendor firmware:
- Connect to the Web-interface at http://192.168.1.1
- Go to "Administration" -> "Firmware Upgrade"
- Upload the OpenWrt sysupgrade image
Signed-off-by: Rosy Song <rosysong@rosinson.com>
6 years ago
|
|
|
rosinson,wr818)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan" "2:lan" "3:wan"
|
|
|
|
|
;;
|
|
|
|
|
tplink,archer-a7-v5|\
|
|
|
|
|
tplink,archer-c6-v2|\
|
ath79: add support for TP-Link Archer C6 v2 (US) and A6 (US/TW)
This patch is based on #1689 and adds support for TP-Link Archer
C6 v2 (US) and A6 (US/TW).
The hardware is the same as EU and RU variant, except for GPIOs
(LEDS/Buttons), flash(chip/partitions) and UART being available
on the board.
- SOC: Qualcomm QCA9563 @ 775MHz
- Flash: GigaDevice GD25Q127CS1G (16MiB)
- RAM: Zentel A3R1GE40JBF (128 MiB DDR2)
- Ethernet: Qualcomm QCA8337N: 4x 1Gbps LAN + 1x 1Gbps WAN
- Wireless:
- 2.4GHz (bgn) QCA9563 integrated (3x3)
- 5GHz (ac) Qualcomm QCA9886 (2x2)
- Button: 1x power, 1x reset, 1x wps
- LED: 6x LEDs: power, wlan2g, wlan5g, lan, wan, wps
- UART: 115200, 8n1 (header available on board)
Known issues:
- Wireless: 5GHz is known to have lower RSSI signal, it affects speed and range.
Flash instructions:
Upload openwrt-ath79-generic-tplink_archer-c6-v2-us-squashfs-factory.bin
via the router Web interface.
Flash instruction using tftp recovery:
1. Connect the computer to one of the LAN ports of the router
2. Set the computer IP to 192.168.0.66
3. Start a tftp server with the OpenWrt factory image in the
tftp root directory renamed to ArcherA6v2_tp_recovery.bin.
4. Connect power cable to router, press and hold the
reset button and turn the router on
5. Keep the reset button pressed until the WPS LED lights up
6. Wait ~150 seconds to complete flashing
Flash partitioning: I've followed #1689 for defining the partition layout
for this patch. The partition named as "tplink" @ 0xfd0000 is marked
as read only as it is where some config for stock firmware are stored.
On stock firmware those stock partitions starts at 0xfd9400 however
I had not been able to make it functional starting on the same address as
on stock fw, so it has been partitioned following #1689 and not the stock
partition layout for this specific partition. Due to that firmware/rootfs
partition lenght is 0xf80000 and not 0xf89400 as stock.
According to the GPL code, the EU/RU/JP variant does have different GPIO pins
assignment to LEDs and buttons, also the flash memory layout is different.
GPL Source Code: https://static.tp-link.com/resources/gpl/gpl-A6v2_us.tar.gz
Signed-off-by: Anderson Vulczak <andi@andi.com.br>
[wrap commit message, remove soft_ver change for C6 v2 EU, move LED aliases
to DTS files, remove dts-v1 in DTSI, node/property reorder in DTSI]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
tplink,archer-c6-v2-us|\
|
|
|
|
|
tplink,archer-c7-v4|\
|
|
|
|
|
tplink,archer-c7-v5|\
|
|
|
|
|
tplink,tl-wdr3600-v1|\
|
|
|
|
|
tplink,tl-wdr4300-v1|\
|
|
|
|
|
tplink,tl-wdr4300-v1-il)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "2:lan:1" "3:lan:2" "4:lan:3" "5:lan:4" "1:wan"
|
|
|
|
|
;;
|
|
|
|
|
tplink,archer-c5-v1|\
|
|
|
|
|
tplink,archer-c7-v1|\
|
|
|
|
|
tplink,archer-c7-v2|\
|
|
|
|
|
tplink,tl-wdr4900-v2)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth1" "2:lan" "3:lan" "4:lan" "5:lan" "6@eth0" "1:wan"
|
|
|
|
|
;;
|
|
|
|
|
tplink,archer-c60-v1|\
|
|
|
|
|
tplink,archer-c60-v2)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan" "2:lan" "3:lan" "4:lan"
|
|
|
|
|
;;
|
|
|
|
|
tplink,archer-d50-v1)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "2:lan:3" "3:lan:2" "4:lan:1" "1:wan"
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-wr842n-v2)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan:4" "2:lan:1" "3:lan:2" "4:lan:3"
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-wr1043nd-v1)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "5@eth0"
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-wr1043nd-v2|\
|
|
|
|
|
tplink,tl-wr1043nd-v3|\
|
|
|
|
|
tplink,tl-wr1045nd-v2)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth1" "1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "5:wan" "6@eth0"
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-wr2543-v1)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "9@eth0"
|
|
|
|
|
;;
|
|
|
|
|
ubnt,acb-isp)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "2:lan:1" "3:lan:3" "4:lan:2"
|
|
|
|
|
;;
|
|
|
|
|
ubnt,edgeswitch-5xp)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "1:lan" "2:lan" "3:lan" "4:lan" "5:lan"
|
|
|
|
|
;;
|
|
|
|
|
ubnt,edgeswitch-8xp)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan:1" "1:lan:2" "2:lan:3" "3:lan:4" "4:lan:5" "5:lan:6" "6:lan:7" "7:lan:8" "8@eth0"
|
|
|
|
|
;;
|
ath79: initial support for Ubiquiti RouterStation and RouterStation Pro
This adds a shared ar7161_ubnt_routerstation.dtsi as well as two other
.dts files that utilize it, ar7161_ubnt_routerstation.dts and
ar7161_ubnt_routerstation-pro.dts.
The modifications to generic-ubnt.mk, config-default, and base-files
necessary for image generation, parsing RedBoot FIS partitions, network
configuration, and sysupgrade are also included.
This reintroduces vital bits from platform_do_upgrade_combined() and its
supporting functions to /lib/upgrade/platform.sh, which were previously
removed from ath79 in 3e9d9f62258f80298710441e0db557e59e152dcf "ath79:
sysupgrade: drop unused platform checks". The new function is called
"routerstation_do_upgrade" and will *only* work for the RouterStation
series of boards. It does however retain the ability to downgrade (e.g.
from master -> 17.01.x using sysupgrade -F).
All hardware is functional including the AR8216 switch (for the Pro),
wireless via ath5k/ath9k using the miniPCI slots, flash, USB, button,
and LED.
Switch and LAN/WAN configuration is the same as it is with the
equivalent ar71xx targets. MAC addresses are assigned based upon the
content stored in the RedBoot config partition.
Flashing via both sysupgrade and TFTP has been confirmed to work. Also,
the initramfs images are now raw .bin files instead of being wrapped in
a uImage (as they currently are in ar71xx), which makes them bootable
with RedBoot.
One notable difference to ar71xx is the inclusion of the RedBoot
"fconfig" utility (analogous to U-Boot’s fw_printenv/fw_setenv) in
DEVICE_PACKAGES. The FIS partitions are probed using the RedBoot MTD
parser’s DT binding, whose proper usage is mutually exclusive to
defining a separate fixed-partitions node for "RedBoot config". This
config partition contains the board's base MAC address. The lack of a
hard-coded flash location means that the mtd-mac-address property cannot
be used in the .dts, so instead fconfig is used to read the MAC
addresses from flash in userspace during first boot.
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
Signed-off-by: Matt Merhar <mattmerhar@protonmail.com>
6 years ago
|
|
|
ubnt,routerstation-pro)
|
|
|
|
|
ucidef_set_interface_wan "eth0"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth1" "2:lan:3" "3:lan:2" "4:lan:1"
|
|
|
|
|
;;
|
|
|
|
|
ubnt,nanostation-m-xw)
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "5:lan" "1:wan"
|
|
|
|
|
;;
|
ath79: Add support for ZBT-WD323
ZBT-WD323 is a dual-LTE router based on AR9344. The detailed
specifications are:
* AR9344 560MHz/450MHz/225MHz (CPU/DDR/AHN).
* 128 MB RAM
* 16MB of flash(SPI-NOR, 22MHz)
* 1x 2.4GHz wifi (Atheros AR9340)
* 3x 10/100Mbos Ethernet (AR8229)
* 1x USB2.0 port
* 2x miniPCIe-slots (USB2.0 only)
* 2x SIM slots (standard size)
* 4x LEDs (1 gpio controlled)
* 1x reset button
* 1x 10 pin terminal block (RS232, RS485, 4x GPIO)
* 2x CP210x UART bridge controllers (used for RS232 and RS485)
* 1x 2 pin 5mm industrial interface (input voltage 12V~36V)
* 1x DC jack
* 1x RTC (PCF8563)
Tested:
- Ethernet switch
- Wifi
- USB port
- MiniPCIe-slots (+ SIM slots)
- Sysupgrade
- Reset button
- RS232
Intallation and recovery:
The board ships with OpenWRT, but sysupgrade does not work as a
different firmware format than what is expected is generated. The
easiest way to install (and recover) the router, is to use the
web-interface provided by the bootloader (Breed).
While the interface is in Chinese, it is easy to use. First, in order to
access the interface, you need to hold down the reset button for around
five seconds. Then, go to 192.168.1.1 in your browser. Click on the
second item in the list on the left to access the recovery page. The
second item on the next page is where you select the firmware. Select
the menu item containing "Atheros SDK" and "16MB" in the dropdown close
to the buttom, and click on the button at the bottom to start
installation/recovery.
Notes:
* RS232 is available on /dev/ttyUSB0 and RS485 on /dev/ttyUSB1
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
[removed unused poll-interval from gpio-keys, i2c-gpio 4.19 compat]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
5 years ago
|
|
|
zbtlink,zbt-wd323|\
|
|
|
|
|
xiaomi,mi-router-4q)
|
|
|
|
|
ucidef_set_interface_wan "eth1"
|
|
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0@eth0" "3:lan:1" "4:lan:2"
|
|
|
|
|
;;
|
|
|
|
|
*)
|
|
|
|
|
ucidef_set_interfaces_lan_wan "eth0" "eth1"
|
|
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
ath79_setup_macs()
|
|
|
|
|
{
|
|
|
|
|
local board="$1"
|
|
|
|
|
|
|
|
|
|
case "$board" in
|
ath79: add support for Bluesocket BSAP1880 board
This board was used in dual-band 802.11n enterprise access points, models
BSAP-1800v2 and BSAP-1840, introduced in 2010 by Bluesocket, which was
acquired by Adtran in 2011, who has now EOL'ed them. They differed only in
that the BSAP-1840's antennae were detachable, while the BSAP-1800v2's were
inside the case. They have an external RJ-45 console port, which works with
standard Cisco 72-3383-01 console cables.
Specification:
- System-On-Chip: AR7161
- CPU/Speed: 600 MHz
- Flash-Chip: Macronix MX25L12845E
- Flash size: 16 MiB
- RAM: 64 MiB
- Wireless No1: Lite-On WN2601A card: AR9160/AR9103 2.4GHz 802.11bgn
- Wireless No2: Lite-On WN2502A card: AR9160/AR9106 5GHz 802.11an
- PHY: Vitesse VSC8601, Rev. B
Installation:
1. Connect to the serial console using a terminal that supports YMODEM at
115200 bps, 8 data bits, no parity, 1 stop bit
2. Interrupt the bootloader using its password, which is: r00t
3. Issue the "fis init" command, confirming if prompted
4. Look at the length of the openwrt-ath79-generic-*-squashfs-kernel.bin
file, and substitute it below, instead of where I have "LeNgTh"
5. Issue the following command, and upload this file using YMODEM protocol
load -r -v -b 0x80060000 -m ymodem
6. Issue the following commands, substituting as mentioned above:
fis create -b 0x80060000 -l LeNgTh vmlinux_2
load -r -v -b 0x80100000 -m ymodem
7. Using YMODEM, upload openwrt-ath79-generic-*-squashfs-rootfs.bin
8. Issue the "fis free" command, and for the first range in its response,
use a hexadecimal calculator to subtract the start from the end in order
to substitute it below, with the leading "0x" to specify it in
hexadecimal, instead of where I have "LeNgTh"
9. Issue the following commands, substituting as mentioned above:
fis create -b 0x80100000 -l LeNgTh -e 0 -r 0 rootfs
reset
10.Wait for the status LED to go solid green
Tested-by: Brian Gonyer <bgonyer@gmail.com>
Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
[fixed obsolete $ARGV in platform_do_upgrade]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
6 years ago
|
|
|
adtran,bsap1800-v2|\
|
|
|
|
|
adtran,bsap1840)
|
|
|
|
|
lan_mac=$(mtd_get_mac_binary "Board data" 2)
|
ath79: provide label MAC address
This patch adds the label MAC address for several devices in
ath79.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- alfa-network,ap121f
- avm,fritz300e
- ubnt-xm devices
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- adtran,bsap1800-v2
- adtran,bsap1840
- dlink,dir-842-c1/-c2/-c3
- engenius,ecb1750
- iodata,etg3-r
- iodata,wn-ac1167dgr
- iodata,wn-ac1600dgr
- iodata,wn-ac1600dgr2
- iodata,wn-ag300dgr
- nec,wg800hp
- nec,wg1200cr
- trendnet,tew-823dru
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
label_mac=$lan_mac
|
|
|
|
|
;;
|
ath79: fix source of label MAC address for Ubiquiti XM devices
In d421a8b94489 ("ath79: read label MAC address from flash instead
of using phy0/phy1") the source of the label MAC address was changed
for devices just reading it from phy0. To get rid of the dependency
from phy startup, addresses were read directly from the flash
locations that are used to initialize the phy MAC addresses.
Unfortunately, it turned out that Ubiquiti XM devices seem to have
different flash locations than expected, and also seem to have
specific locations for different devices (all in art/EEPROM):
0xe012 AR9280 Nanostation M2 - 0x120c
0xe035 AR9280 Nanostation M3 - 0x120c
0xe1b2 AR9280 Rocket M2 - 0x120c
0xe1c3 AR9280 Rocket M3 - 0x120c
0xe1b5 AR9280 Rocket M5 - 0x120c
0xe2d5 AR9280 Bullet M2 Titanium - 0x120c
0xe2b5 AR9280 Nanobridge M5 - 0x120c
0xe202 AR9280 Bullet M2 - 0x120c
0xe232 AR9287 Nanobridge M2 - 0x110c
0xe4a2 AR9285 AirRouter - 0xa0bf
Picostation M2 - 0x120c and 0xa0bf
Nanostation Loco M2 - not in 0x120c, other locations not checked
An additional problem of the Ubiquiti device support in OpenWrt is
that we provide images that match several subvariants of the devices,
which might have different MAC address locations.
Given that reading the address from phy0 in 02_network _is_ working
for the ath79 target in general, it does not seem reasonable to
rebuild a complex MAC address retrieval mechanism which is already
present in the ath9k driver.
So, this patch reverts the label MAC address source for Ubiquiti XM
devices (and the Unifi AP) to /sys/class/ieee80211/phy0/macaddress.
This doesn't affect XW and Unifi AC devices, where the label MAC
address source is defined via device tree.
For alfa-network,ap121f the location 0x1002 is kept, as this has
been verified during device support preparation in PR #2199.
Fixes: d421a8b94489 ("ath79: read label MAC address from flash
instead of using phy0/phy1")
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
alfa-network,ap121f)
|
|
|
|
|
label_mac=$(mtd_get_mac_binary art 0x1002)
|
ath79: add support for Bluesocket BSAP1880 board
This board was used in dual-band 802.11n enterprise access points, models
BSAP-1800v2 and BSAP-1840, introduced in 2010 by Bluesocket, which was
acquired by Adtran in 2011, who has now EOL'ed them. They differed only in
that the BSAP-1840's antennae were detachable, while the BSAP-1800v2's were
inside the case. They have an external RJ-45 console port, which works with
standard Cisco 72-3383-01 console cables.
Specification:
- System-On-Chip: AR7161
- CPU/Speed: 600 MHz
- Flash-Chip: Macronix MX25L12845E
- Flash size: 16 MiB
- RAM: 64 MiB
- Wireless No1: Lite-On WN2601A card: AR9160/AR9103 2.4GHz 802.11bgn
- Wireless No2: Lite-On WN2502A card: AR9160/AR9106 5GHz 802.11an
- PHY: Vitesse VSC8601, Rev. B
Installation:
1. Connect to the serial console using a terminal that supports YMODEM at
115200 bps, 8 data bits, no parity, 1 stop bit
2. Interrupt the bootloader using its password, which is: r00t
3. Issue the "fis init" command, confirming if prompted
4. Look at the length of the openwrt-ath79-generic-*-squashfs-kernel.bin
file, and substitute it below, instead of where I have "LeNgTh"
5. Issue the following command, and upload this file using YMODEM protocol
load -r -v -b 0x80060000 -m ymodem
6. Issue the following commands, substituting as mentioned above:
fis create -b 0x80060000 -l LeNgTh vmlinux_2
load -r -v -b 0x80100000 -m ymodem
7. Using YMODEM, upload openwrt-ath79-generic-*-squashfs-rootfs.bin
8. Issue the "fis free" command, and for the first range in its response,
use a hexadecimal calculator to subtract the start from the end in order
to substitute it below, with the leading "0x" to specify it in
hexadecimal, instead of where I have "LeNgTh"
9. Issue the following commands, substituting as mentioned above:
fis create -b 0x80100000 -l LeNgTh -e 0 -r 0 rootfs
reset
10.Wait for the status LED to go solid green
Tested-by: Brian Gonyer <bgonyer@gmail.com>
Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
[fixed obsolete $ARGV in platform_do_upgrade]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
6 years ago
|
|
|
;;
|
|
|
|
|
avm,fritz300e)
|
|
|
|
|
lan_mac=$(fritz_tffs -n maca -i $(find_mtd_part "tffs (1)"))
|
|
|
|
|
label_mac=$(fritz_tffs -n macwlan -i $(find_mtd_part "tffs (1)"))
|
|
|
|
|
;;
|
ath79: add support for Fritz!Box 4020
This commit adds support for the AVM Fritz!Box 4020 WiFi-router.
SoC: Qualcomm Atheros QCA9561 (Dragonfly) 750MHz
RAM: Winbond W971GG6KB-25
FLASH: Macronix MX25L12835F
WiFi: QCA9561 b/g/n 3x3 450Mbit/s
USB: 1x USB 2.0
IN: WPS button, WiFi button
OUT: Power LED green, Internet LED green, WLAN LED green,
LAN LED green, INFO LED green, INFO LED red
UART: Header Next to Black metal shield
Pinout is 3.3V - RX - TX - GND (Square Pad is 3.3V)
The Serial setting is 115200-8-N-1.
Tested and working:
- Ethernet (LAN + WAN)
- WiFi (correct MAC)
- Installation via EVA bootloader
- OpenWRT sysupgrade
- Buttons
- LEDs
The USB port doesn't work. Both Root Hubs are detected as having 0 Ports:
[ 3.670807] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 3.723267] usbcore: registered new interface driver usbfs
[ 3.729058] usbcore: registered new interface driver hub
[ 3.734616] usbcore: registered new device driver usb
[ 3.744181] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.758357] SCSI subsystem initialized
[ 3.766026] ehci-platform: EHCI generic platform driver
[ 3.771548] ehci-platform ehci-platform.0: EHCI Host Controller
[ 3.777708] ehci-platform ehci-platform.0: new USB bus registered, assigned bus number 1
[ 3.788169] ehci-platform ehci-platform.0: irq 48, io mem 0x1b000000
[ 3.816647] ehci-platform ehci-platform.0: USB 2.0 started, EHCI 0.00
[ 3.824001] hub 1-0:1.0: USB hub found
[ 3.828219] hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
[ 3.835825] ehci-platform ehci-platform.1: EHCI Host Controller
[ 3.842009] ehci-platform ehci-platform.1: new USB bus registered, assigned bus number 2
[ 3.852481] ehci-platform ehci-platform.1: irq 49, io mem 0x1b400000
[ 3.886631] ehci-platform ehci-platform.1: USB 2.0 started, EHCI 0.00
[ 3.894011] hub 2-0:1.0: USB hub found
[ 3.898190] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)
[ 3.908928] usbcore: registered new interface driver usb-storage
[ 3.915634] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
A few words about the shift-register:
AVM used a trick to control the shift-register for the LEDs with only 2
pins, SERCLK and MOSI. Q7S, normally used for daisy-chaining multiple
shift-registers, pulls the latch, moving the shift register-state to
the storage register. It also pulls down MR (normally pulled up) to
clear the storage register, so the latch gets released and will not be
pulled by the remaining bits in the shift-register. Shift register is
all-zero after this.
For that we need to make sure output 7 is set to high on driver probe.
We accomplish this by using gpio-hogging.
Installation via EVA:
In the first seconds after Power is connected, the bootloader will
listen for FTP connections on 169.254.157.1 (Might also be 192.168.178.1).
Firmware can be uploaded like following:
ftp> quote USER adam2
ftp> quote PASS adam2
ftp> binary
ftp> debug
ftp> passive
ftp> quote MEDIA FLSH
ftp> put openwrt-sysupgrade.bin mtd1
Note that this procedure might take up to two minutes. After transfer is
complete you need to powercycle the device to boot OpenWRT.
Signed-off-by: David Bauer <mail@david-bauer.net>
6 years ago
|
|
|
avm,fritz4020)
|
|
|
|
|
lan_mac=$(fritz_tffs -n maca -i $(find_mtd_part "tffs (1)"))
|
|
|
|
|
wan_mac=$(fritz_tffs -n macb -i $(find_mtd_part "tffs (1)"))
|
|
|
|
|
;;
|
|
|
|
|
dlink,dir-825-b1)
|
|
|
|
|
lan_mac=$(mtd_get_mac_text "caldata" 0xffa0)
|
|
|
|
|
wan_mac=$(mtd_get_mac_text "caldata" 0xffb4)
|
|
|
|
|
;;
|
|
|
|
|
dlink,dir-825-c1|\
|
|
|
|
|
dlink,dir-835-a1)
|
|
|
|
|
lan_mac=$(mtd_get_mac_text "mac" 0x4)
|
|
|
|
|
wan_mac=$(mtd_get_mac_text "mac" 0x18)
|
|
|
|
|
;;
|
|
|
|
|
dlink,dir-842-c1|\
|
|
|
|
|
dlink,dir-842-c2|\
|
|
|
|
|
dlink,dir-842-c3|\
|
ath79: provide label MAC address
This patch adds the label MAC address for several devices in
ath79.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- alfa-network,ap121f
- avm,fritz300e
- ubnt-xm devices
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- adtran,bsap1800-v2
- adtran,bsap1840
- dlink,dir-842-c1/-c2/-c3
- engenius,ecb1750
- iodata,etg3-r
- iodata,wn-ac1167dgr
- iodata,wn-ac1600dgr
- iodata,wn-ac1600dgr2
- iodata,wn-ag300dgr
- nec,wg800hp
- nec,wg1200cr
- trendnet,tew-823dru
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
nec,wg1200cr)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii devdata "lanmac")
|
|
|
|
|
wan_mac=$(mtd_get_mac_ascii devdata "wanmac")
|
|
|
|
|
label_mac=$lan_mac
|
|
|
|
|
;;
|
|
|
|
|
dlink,dir-859-a1|\
|
ath79: provide label MAC address
This patch adds the label MAC address for several devices in
ath79.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- alfa-network,ap121f
- avm,fritz300e
- ubnt-xm devices
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- adtran,bsap1800-v2
- adtran,bsap1840
- dlink,dir-842-c1/-c2/-c3
- engenius,ecb1750
- iodata,etg3-r
- iodata,wn-ac1167dgr
- iodata,wn-ac1600dgr
- iodata,wn-ac1600dgr2
- iodata,wn-ag300dgr
- nec,wg800hp
- nec,wg1200cr
- trendnet,tew-823dru
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
qihoo,c301|\
|
|
|
|
|
wd,mynet-n750)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii devdata "lanmac")
|
|
|
|
|
wan_mac=$(mtd_get_mac_ascii devdata "wanmac")
|
|
|
|
|
;;
|
|
|
|
|
elecom,wrc-1750ghbk2-i|\
|
|
|
|
|
elecom,wrc-300ghbk2-i)
|
|
|
|
|
wan_mac=$(macaddr_add "$(mtd_get_mac_binary art 0x1002)" -2)
|
|
|
|
|
;;
|
|
|
|
|
engenius,ecb1750)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii u-boot-env ethaddr)
|
ath79: provide label MAC address
This patch adds the label MAC address for several devices in
ath79.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- alfa-network,ap121f
- avm,fritz300e
- ubnt-xm devices
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- adtran,bsap1800-v2
- adtran,bsap1840
- dlink,dir-842-c1/-c2/-c3
- engenius,ecb1750
- iodata,etg3-r
- iodata,wn-ac1167dgr
- iodata,wn-ac1600dgr
- iodata,wn-ac1600dgr2
- iodata,wn-ag300dgr
- nec,wg800hp
- nec,wg1200cr
- trendnet,tew-823dru
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
label_mac=$(mtd_get_mac_ascii u-boot-env athaddr)
|
|
|
|
|
;;
|
ath79: provide label MAC address
This patch adds the label MAC address for several devices in
ath79.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- alfa-network,ap121f
- avm,fritz300e
- ubnt-xm devices
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- adtran,bsap1800-v2
- adtran,bsap1840
- dlink,dir-842-c1/-c2/-c3
- engenius,ecb1750
- iodata,etg3-r
- iodata,wn-ac1167dgr
- iodata,wn-ac1600dgr
- iodata,wn-ac1600dgr2
- iodata,wn-ag300dgr
- nec,wg800hp
- nec,wg1200cr
- trendnet,tew-823dru
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
engenius,epg5000)
|
ath79: add suport for EnGenius EPG5000
EnGenius EPG5000 (v1.0.0, marketed as IoT Gateway) is a dual band
wireless router.
Specification
SoC: Qualcomm Atheros QCA9558
RAM: 256 MB DDR2
Flash: 16 MB SPI NOR
WIFI: 2.4 GHz 3T3R integrated
5 GHz 3T3R QCA9880 Mini PCIe card
Ethernet: 5x 10/100/1000 Mbps QCA8337N
USB: 1x 2.0
LEDS: 4x GPIO controlled
Buttons: 2x GPIO controlled
UART: 4 pin header, starting count from white triangle on PCB
1. VCC 3.3V, 2. GND, 3. TX, 4. RX
baud: 115200, parity: none, flow control: none
Installation
1. Connect to one of LAN (yellow) ethernet ports,
2. Open router configuration interface,
3. Go to Tools > Firmware,
4. Select OpenWrt factory image with dlf extension and hit Apply,
5. Wait few minutes, after the Power LED will stop blinking, the router
is ready for configuration.
Alternative installation
1. Prepare TFTP server with OpenWrt sysupgrade image,
2. Connect to one of LAN (yellow) ethernet ports,
3. Connect to UART port (leaving out VCC pin!),
4. Power on router,
5. When asked to enter a number 1 or 3 hit 2, this will select flashing
image from TFTP server option,
6. You'll be prompted to enter TFTP server ip (default is 192.168.99.8),
then router ip (default is 192.168.99.9) and for last, image name
downloaded from TFTP server (default is uImageESR1200_1750),
7. After providing all information U-Boot will start flashing the image,
You can observe progress on console, it'll take few minutes and when
the Power LED will stop blinking, router is ready for configuration.
Additional information
If connected to UART, when prompted for number on boot, one can enter
number 4 to open bootloader (U-Boot) command line.
OEM firmware shell password is: aigo3d0a0tdagr
useful for creating backup of original firmware.
When doing upgrade from OpenWrt ar71xx image, it is recomended to not keep
the old configuration.
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
5 years ago
|
|
|
lan_mac=$(mtd_get_mac_ascii u-boot-env ethaddr)
|
|
|
|
|
wan_mac=$(mtd_get_mac_ascii u-boot-env wanaddr)
|
|
|
|
|
;;
|
|
|
|
|
engenius,ews511ap)
|
|
|
|
|
lan_mac=$(mtd_get_mac_text "u-boot-env" 0xe9)
|
|
|
|
|
eth1_mac=$(macaddr_add "$lan_mac" 1)
|
|
|
|
|
ucidef_set_interface "eth0" ifname "eth0" protocol "none" macaddr "$lan_mac"
|
|
|
|
|
ucidef_set_interface "eth1" ifname "eth1" protocol "none" macaddr "$eth1_mac"
|
|
|
|
|
;;
|
|
|
|
|
iodata,etg3-r)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii u-boot-env ethaddr)
|
|
|
|
|
wan_mac=$(macaddr_add "$lan_mac" -1)
|
ath79: provide label MAC address
This patch adds the label MAC address for several devices in
ath79.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- alfa-network,ap121f
- avm,fritz300e
- ubnt-xm devices
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- adtran,bsap1800-v2
- adtran,bsap1840
- dlink,dir-842-c1/-c2/-c3
- engenius,ecb1750
- iodata,etg3-r
- iodata,wn-ac1167dgr
- iodata,wn-ac1600dgr
- iodata,wn-ac1600dgr2
- iodata,wn-ag300dgr
- nec,wg800hp
- nec,wg1200cr
- trendnet,tew-823dru
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
label_mac=$wan_mac
|
|
|
|
|
;;
|
|
|
|
|
iodata,wn-ac1167dgr|\
|
|
|
|
|
iodata,wn-ac1600dgr|\
|
|
|
|
|
iodata,wn-ac1600dgr2|\
|
|
|
|
|
iodata,wn-ag300dgr)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii u-boot-env ethaddr)
|
|
|
|
|
wan_mac=$(mtd_get_mac_ascii u-boot-env wanaddr)
|
|
|
|
|
label_mac=$wan_mac
|
|
|
|
|
;;
|
ath79: add support for jjPlus JA76PF2
jjPlus JA76PF2 (marketed as IntellusPro2) is a network embedded board.
Specification
SoC: Atheros AR7161
RAM: 64 MB DDR
Flash: 16 MB SPI NOR
Ethernet: 2x 10/100/1000 Mbps AR8316
LAN (CN11), WAN/PoE (CN6 - close to power barrel
connector, 48 V)
MiniPCI: 2x
LEDS: 4x, which 3 are GPIO controlled
Buttons: 2x GPIO controlled
Reset (SW1, closer to ethernet ports), WPS (SW2)
Serial: 1x (only RX and TX are wired)
baud: 115200, parity: none, flow control: none
Currently there is one caveat compared to ar71xx target images as the
MAC addresses are random on every reboot. To remedy this one needs to
store the WAN MAC address in RedBoot configuration. OpenWrt on first
boot, after flashing, will read out the address and assign proper ones
to both WAN and LAN ports. It is iportant to NOT keep the old
configuration when doing sysupgrade from ar71xx.
Upgrading from OpenWrt ar71xx image
1. Connect to serial port,
2. Download OpenWrt sysupgrade image to /tmp directory and flash it
with:
sysupgrade -n <openwrt_sysupgrade_image_name>
3. After writing new image OpenWrt will reboot, now interrupt boot
process and enter RedBoot (bootloader) command line by pressing
Ctrl+C,
4. Enter following commands (replace variable accordingly),
set_mac (to view MAC addresses)
alias ethaddr <wan_port_mac_adress>
(confirm storing the value by inputting y and pressing Enter)
reset
5. Now board should restart and boot OpenWrt with proper MAC addresses.
Installation
1. Prepare TFTP server with OpenWrt initramfs image,
2. Connect to WAN ethernet port,
3. Connect to serial port,
4. Power on the board and enter RedBoot (bootloader) command line by
pressing Ctrl+C,
5. Enter following commands (replace variables accordingly):
set_mac (to view MAC addresses)
alias ethaddr <wan_port_mac_address>
(confirm storing the value by inputting y and pressing Enter)
ip_adress -l <board_ip_adress>/24 -h <tftp_server_ip_adress>
load -r -b 0x80060000 <openwrt_initramfs_image_name>
exec -c ""
6. Now board should boot OpenWrt initramfs image,
7. Download OpenWrt sysupgrade image to /tmp directory and flash it
with:
sysupgrade <openwrt_sysupgrade_image_name>
8. Wait few minutes, after the D2 LED will stop blinking, the board
is ready for configuration.
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
5 years ago
|
|
|
jjplus,ja76pf2)
|
|
|
|
|
wan_mac=$(fconfig -s -r -d $(find_mtd_part "RedBoot config") -n alias/ethaddr)
|
|
|
|
|
lan_mac=$(macaddr_add "$wan_mac" 1)
|
|
|
|
|
;;
|
|
|
|
|
nec,wg800hp)
|
|
|
|
|
lan_mac=$(mtd_get_mac_text board_data 0x280)
|
|
|
|
|
wan_mac=$(mtd_get_mac_text board_data 0x480)
|
ath79: provide label MAC address
This patch adds the label MAC address for several devices in
ath79.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- alfa-network,ap121f
- avm,fritz300e
- ubnt-xm devices
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- adtran,bsap1800-v2
- adtran,bsap1840
- dlink,dir-842-c1/-c2/-c3
- engenius,ecb1750
- iodata,etg3-r
- iodata,wn-ac1167dgr
- iodata,wn-ac1600dgr
- iodata,wn-ac1600dgr2
- iodata,wn-ag300dgr
- nec,wg800hp
- nec,wg1200cr
- trendnet,tew-823dru
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
label_mac=$wan_mac
|
|
|
|
|
;;
|
|
|
|
|
netgear,wndr3700|\
|
|
|
|
|
netgear,wndr3700v2|\
|
|
|
|
|
netgear,wndr3800)
|
|
|
|
|
lan_mac=$(macaddr_setbit_la "$(mtd_get_mac_binary art 0x0)")
|
|
|
|
|
;;
|
|
|
|
|
phicomm,k2t)
|
|
|
|
|
lan_mac=$(k2t_get_mac "lan_mac")
|
|
|
|
|
wan_mac=$(k2t_get_mac "wan_mac")
|
|
|
|
|
;;
|
ath79: add support for ROSINSON WR818 board
This commit adds support for the ROSINSON WR818 WiFi-Router
SoC: Qualcomm Atheros QCA9563,
FLASH: Winbond W25Q128FV 16MBytes,
WiFi: QCA9563 b/g/n 3x3 450Mbit/s,
USB: 1x USB 2.0 Type A, 1x USB2.0 Type C,
IN: WPS/Reset button GPIO1,
OUT: Power LED red, Internet LED red, WLAN LED red,
LAN1 LED red, LAN2 LED red, System LED red,
UART: RX-GPIO18, TX-GPIO22,
Tested and working:
- Ethernet (LAN + WAN)
- WiFi
- OpenWRT sysupgrade
- Button
- LEDs
Installation of OpenWRT from vendor firmware:
- Connect to the Web-interface at http://192.168.1.1
- Go to "Administration" -> "Firmware Upgrade"
- Upload the OpenWrt sysupgrade image
Signed-off-by: Rosy Song <rosysong@rosinson.com>
6 years ago
|
|
|
rosinson,wr818)
|
|
|
|
|
wan_mac=$(mtd_get_mac_binary factory 0x0)
|
ath79: add support for ROSINSON WR818 board
This commit adds support for the ROSINSON WR818 WiFi-Router
SoC: Qualcomm Atheros QCA9563,
FLASH: Winbond W25Q128FV 16MBytes,
WiFi: QCA9563 b/g/n 3x3 450Mbit/s,
USB: 1x USB 2.0 Type A, 1x USB2.0 Type C,
IN: WPS/Reset button GPIO1,
OUT: Power LED red, Internet LED red, WLAN LED red,
LAN1 LED red, LAN2 LED red, System LED red,
UART: RX-GPIO18, TX-GPIO22,
Tested and working:
- Ethernet (LAN + WAN)
- WiFi
- OpenWRT sysupgrade
- Button
- LEDs
Installation of OpenWRT from vendor firmware:
- Connect to the Web-interface at http://192.168.1.1
- Go to "Administration" -> "Firmware Upgrade"
- Upload the OpenWrt sysupgrade image
Signed-off-by: Rosy Song <rosysong@rosinson.com>
6 years ago
|
|
|
lan_mac=$(macaddr_setbit_la "$wan_mac")
|
|
|
|
|
;;
|
ath79: add support for Sitecom WLR-7100
Sitecom WLR-7100 v1 002 (marketed as X7 AC1200) is a dual band wireless
router.
Specification
SoC: Atheros AR1022
RAM: 64 MB DDR2
Flash: 8 MB SPI NOR
WIFI: 2.4 GHz 2T2R integrated
5 GHz 2T2R QCA9882 integrated (connected to PCIe lane)
Ethernet: 5x 10/100/1000 Mbps QCA8337N
USB: 1x 2.0
LEDS: 4x GPIO controlled, 5x switch
Buttons: 2x GPIO controlled
UART: row of 4 unpopulated holes near USB port, starting count from
white triangle on PCB
1. VCC 3.3V, 2. GND, 3. TX, 4. RX
baud: 115200, parity: none, flow control: none
Installation
1. Connect to one of LAN (yellow) ethernet ports,
2. Open router configuration interface,
3. Go to Toolbox > Firmware,
4. Browse for OpenWrt factory image with dlf extension and hit Apply,
5. Wait few minutes, after the Power LED will stop blinking, the router
is ready for configuration.
Known issues
5GHz LED doesn't work
Additional information
When TX line on UART is connected, and board is switched on from power
off state, the DDR memory training may fail.
If connected to UART, when prompted for number on boot, one can enter
number 4 to open bootloader (U-Boot) command line.
OEM firmware shell password is: SitecomSenao
useful for creating backup of original firmware.
There is also another revision of this device (v1 001), which may or may
not work with introduced images.
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
5 years ago
|
|
|
sitecom,wlr-7100)
|
|
|
|
|
lan_mac=$(mtd_get_mac_ascii u-boot-env ethaddr)
|
|
|
|
|
wan_mac=$(mtd_get_mac_ascii u-boot-env wanaddr)
|
|
|
|
|
label_mac=$lan_mac
|
|
|
|
|
;;
|
|
|
|
|
tplink,archer-a7-v5|\
|
|
|
|
|
tplink,archer-c7-v4|\
|
|
|
|
|
tplink,archer-c7-v5|\
|
|
|
|
|
tplink,tl-wr1043nd-v4|\
|
|
|
|
|
tplink,tl-wr1043n-v5)
|
|
|
|
|
base_mac=$(mtd_get_mac_binary info 0x8)
|
|
|
|
|
wan_mac=$(macaddr_add "$base_mac" 1)
|
|
|
|
|
;;
|
|
|
|
|
tplink,tl-wdr3600-v1|\
|
|
|
|
|
tplink,tl-wdr4300-v1|\
|
|
|
|
|
tplink,tl-wdr4300-v1-il)
|
|
|
|
|
base_mac=$(mtd_get_mac_binary u-boot 0x1fc00)
|
|
|
|
|
wan_mac=$(macaddr_add "$base_mac" 1)
|
|
|
|
|
;;
|
|
|
|
|
trendnet,tew-823dru)
|
|
|
|
|
lan_mac=$(mtd_get_mac_text mac 0x4)
|
|
|
|
|
wan_mac=$(mtd_get_mac_text mac 0x18)
|
ath79: provide label MAC address
This patch adds the label MAC address for several devices in
ath79.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- alfa-network,ap121f
- avm,fritz300e
- ubnt-xm devices
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- adtran,bsap1800-v2
- adtran,bsap1840
- dlink,dir-842-c1/-c2/-c3
- engenius,ecb1750
- iodata,etg3-r
- iodata,wn-ac1167dgr
- iodata,wn-ac1600dgr
- iodata,wn-ac1600dgr2
- iodata,wn-ag300dgr
- nec,wg800hp
- nec,wg1200cr
- trendnet,tew-823dru
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
label_mac=$wan_mac
|
|
|
|
|
;;
|
ath79: fix source of label MAC address for Ubiquiti XM devices
In d421a8b94489 ("ath79: read label MAC address from flash instead
of using phy0/phy1") the source of the label MAC address was changed
for devices just reading it from phy0. To get rid of the dependency
from phy startup, addresses were read directly from the flash
locations that are used to initialize the phy MAC addresses.
Unfortunately, it turned out that Ubiquiti XM devices seem to have
different flash locations than expected, and also seem to have
specific locations for different devices (all in art/EEPROM):
0xe012 AR9280 Nanostation M2 - 0x120c
0xe035 AR9280 Nanostation M3 - 0x120c
0xe1b2 AR9280 Rocket M2 - 0x120c
0xe1c3 AR9280 Rocket M3 - 0x120c
0xe1b5 AR9280 Rocket M5 - 0x120c
0xe2d5 AR9280 Bullet M2 Titanium - 0x120c
0xe2b5 AR9280 Nanobridge M5 - 0x120c
0xe202 AR9280 Bullet M2 - 0x120c
0xe232 AR9287 Nanobridge M2 - 0x110c
0xe4a2 AR9285 AirRouter - 0xa0bf
Picostation M2 - 0x120c and 0xa0bf
Nanostation Loco M2 - not in 0x120c, other locations not checked
An additional problem of the Ubiquiti device support in OpenWrt is
that we provide images that match several subvariants of the devices,
which might have different MAC address locations.
Given that reading the address from phy0 in 02_network _is_ working
for the ath79 target in general, it does not seem reasonable to
rebuild a complex MAC address retrieval mechanism which is already
present in the ath9k driver.
So, this patch reverts the label MAC address source for Ubiquiti XM
devices (and the Unifi AP) to /sys/class/ieee80211/phy0/macaddress.
This doesn't affect XW and Unifi AC devices, where the label MAC
address source is defined via device tree.
For alfa-network,ap121f the location 0x1002 is kept, as this has
been verified during device support preparation in PR #2199.
Fixes: d421a8b94489 ("ath79: read label MAC address from flash
instead of using phy0/phy1")
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
ubnt,airrouter|\
|
|
|
|
|
ubnt,bullet-m|\
|
|
|
|
|
ubnt,nanostation-m|\
|
|
|
|
|
ubnt,rocket-m|\
|
|
|
|
|
ubnt,unifi)
|
|
|
|
|
label_mac=$(cat /sys/class/ieee80211/phy0/macaddress)
|
|
|
|
|
;;
|
|
|
|
|
ubnt,litebeam-ac-gen2)
|
|
|
|
|
label_mac=$(mtd_get_mac_binary art 0x5006)
|
|
|
|
|
;;
|
ath79: initial support for Ubiquiti RouterStation and RouterStation Pro
This adds a shared ar7161_ubnt_routerstation.dtsi as well as two other
.dts files that utilize it, ar7161_ubnt_routerstation.dts and
ar7161_ubnt_routerstation-pro.dts.
The modifications to generic-ubnt.mk, config-default, and base-files
necessary for image generation, parsing RedBoot FIS partitions, network
configuration, and sysupgrade are also included.
This reintroduces vital bits from platform_do_upgrade_combined() and its
supporting functions to /lib/upgrade/platform.sh, which were previously
removed from ath79 in 3e9d9f62258f80298710441e0db557e59e152dcf "ath79:
sysupgrade: drop unused platform checks". The new function is called
"routerstation_do_upgrade" and will *only* work for the RouterStation
series of boards. It does however retain the ability to downgrade (e.g.
from master -> 17.01.x using sysupgrade -F).
All hardware is functional including the AR8216 switch (for the Pro),
wireless via ath5k/ath9k using the miniPCI slots, flash, USB, button,
and LED.
Switch and LAN/WAN configuration is the same as it is with the
equivalent ar71xx targets. MAC addresses are assigned based upon the
content stored in the RedBoot config partition.
Flashing via both sysupgrade and TFTP has been confirmed to work. Also,
the initramfs images are now raw .bin files instead of being wrapped in
a uImage (as they currently are in ar71xx), which makes them bootable
with RedBoot.
One notable difference to ar71xx is the inclusion of the RedBoot
"fconfig" utility (analogous to U-Boot’s fw_printenv/fw_setenv) in
DEVICE_PACKAGES. The FIS partitions are probed using the RedBoot MTD
parser’s DT binding, whose proper usage is mutually exclusive to
defining a separate fixed-partitions node for "RedBoot config". This
config partition contains the board's base MAC address. The lack of a
hard-coded flash location means that the mtd-mac-address property cannot
be used in the .dts, so instead fconfig is used to read the MAC
addresses from flash in userspace during first boot.
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
Signed-off-by: Matt Merhar <mattmerhar@protonmail.com>
6 years ago
|
|
|
ubnt,routerstation|\
|
|
|
|
|
ubnt,routerstation-pro)
|
|
|
|
|
wan_mac=$(fconfig -s -r -d $(find_mtd_part "RedBoot config") -n ar7100_esa)
|
|
|
|
|
lan_mac=$(macaddr_add "$wan_mac" 1)
|
|
|
|
|
;;
|
|
|
|
|
wd,mynet-wifi-rangeextender)
|
|
|
|
|
lan_mac=$(nvram get et0macaddr)
|
|
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
|
|
|
|
|
[ -n "$lan_mac" ] && ucidef_set_interface_macaddr "lan" $lan_mac
|
|
|
|
|
[ -n "$wan_mac" ] && ucidef_set_interface_macaddr "wan" $wan_mac
|
ath79: provide label MAC address
This patch adds the label MAC address for several devices in
ath79.
Some devices require setting the MAC address in 02_network:
For the following devices, the netif device can be linked in
device tree, but the MAC address cannot be read:
- alfa-network,ap121f
- avm,fritz300e
- ubnt-xm devices
For the following devices, label MAC address is tied to lan or
wan, so no node to link to exists in device tree:
- adtran,bsap1800-v2
- adtran,bsap1840
- dlink,dir-842-c1/-c2/-c3
- engenius,ecb1750
- iodata,etg3-r
- iodata,wn-ac1167dgr
- iodata,wn-ac1600dgr
- iodata,wn-ac1600dgr2
- iodata,wn-ag300dgr
- nec,wg800hp
- nec,wg1200cr
- trendnet,tew-823dru
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
5 years ago
|
|
|
[ -n "$label_mac" ] && ucidef_set_label_macaddr $label_mac
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
board_config_update
|
|
|
|
|
board=$(board_name)
|
|
|
|
|
ath79_setup_interfaces $board
|
|
|
|
|
ath79_setup_macs $board
|
|
|
|
|
board_config_flush
|
|
|
|
|
|
|
|
|
|
exit 0
|
