ath79: add support for Buffalo WZR-HP-AG300H
Buffalo WZR-HP-AG300H is a dual band router based on
Qualcom Atheros AR7161 rev 2
Specification:
- 680 MHz CPU (Qualcomm Atheros AR7161)
- 128 MiB RAM (2x Samsung K4H511638G-LCCC)
- 32 MiB Flash (2x Winbond 25Q128BVFG)
- WiFi 5 GHz a/n (Atheros AR9220)
- WiFi 2.4 GHz b/g/n (Atheros AR9223)
- 1000Base-T WAN (Atheros AR7161)
- 4x 1000Base-T Switch (Atheros AR8316)
- 1x USB 2.0
- 3 Buttons (AOSS/WPS, Reset, USB Eject)
- 2 Slide switches (Router (on/off/auto), Movie Engine (on/off))
- 9 LEDs (Power green, WLAN 2GHz green, WLAN 2GHz amber,
WLAN 5GHz green, WLAN 5GHz LED amber, Router green,
Diag red, Movie Engine blue, USB green)
It is already supported by the ar71xx target.
For more information on the device visit the wiki:
<https://openwrt.org/toh/buffalo/wzr-hp-ag300h>
Serial console:
- The UART Header is next to Movie Engine Switch.
- Pinout is RX - TX - GND - 3.3V (Square Pad is 3.3V)
- The Serial setting is 115200-8-N-1.
Installation of OpenWRT from vendor firmware:
- Connect to the Web-interface at http://192.168.11.1
- Go to “Administration” → “Firmware Upgrade”
- Upload the OpenWrt factory image
Tested:
- Ethernet (LAN, WAN)
- WiFi
- Installation
- via TFTP rescue
- via factory image
- on firmware v1.77 (28-05-2012)
- on pro firmware v24SP2 r30356 (26-03-2018)
- via sysupgrade from ar71xx
(wlan devices don't work because of new names)
- via sysupgrade from itself
- Buttons
- LEDS
- USB (Power control and device recognition)
Signed-off-by: Bernhard Frauendienst <openwrt@nospam.obeliks.de>
2018-08-18 16:28:02 +00:00
|
|
|
include ./common-buffalo.mk
|
2018-06-13 08:51:51 +00:00
|
|
|
include ./common-netgear.mk
|
2019-06-25 08:32:58 +00:00
|
|
|
include ./common-tp-link.mk
|
2019-08-12 23:26:45 +00:00
|
|
|
include ./common-yuncore.mk
|
2018-03-02 18:28:50 +00:00
|
|
|
|
2018-09-04 21:27:02 +00:00
|
|
|
DEVICE_VARS += ADDPATTERN_ID ADDPATTERN_VERSION
|
2018-12-29 09:22:32 +00:00
|
|
|
DEVICE_VARS += SEAMA_SIGNATURE SEAMA_MTDBLOCK
|
2018-12-31 15:41:07 +00:00
|
|
|
DEVICE_VARS += KERNEL_INITRAMFS_PREFIX
|
ath79: add support for D-Link DAP-2695-A1
Hardware:
* SoC: Qualcomm Atheros QCA9558
* RAM: 256MB
* Flash: 16MB SPI NOR
* Ethernet: 2x 10/100/1000 (1x 802.3at PoE-PD)
* WiFi 2.4GHz: Qualcomm Atheros QCA9558
* WiFi 5GHz: Qualcomm Ahteros QCA9880-2R4E
* LEDS: 1x 5GHz, 1x 2.4GHz, 1x LAN1(POE), 1x LAN2, 1x POWER
* Buttons: 1x RESET
* UART: 1x RJ45 RS-232 Console port
Installation via stock firmware:
* Install the factory image via the stock firmware web interface
Installation via bootloader Emergency Web Server:
* Connect your PC to the LAN1(PoE) port
* Configure your PC with IP address 192.168.0.90
* Open a serial console to the Console port (115200,8n1)
* Press "q" within 2s when "press 'q' to stop autoboot" appears
* Open http://192.168.0.50 in a browser
* Upload either the factory or the sysupgrade image
* Once you see "write image into flash...OK,dest addr=0x9f070000" you
can power-cycle the device. Ignore "checksum bad" messages.
Setting the MAC addresses for the ethernet interfaces via
/etc/board.d/02_network adds the following snippets to
/etc/config/network:
config device 'lan_eth0_1_dev'
option name 'eth0.1'
option macaddr 'xx:xx:xx:xx:xx:xx'
config device 'wan_eth1_2_dev'
option name 'eth1.2'
option macaddr 'xx:xx:xx:xx:xx:xx'
This would result in the proper MAC addresses being set for the VLAN
subinterfaces, but the parent interfaces would still have a random MAC
address. Using untagged VLANs could solve this, but would still leave
those extra snippets in /etc/config/network, and then the device VLAN
setup would differ from the one used in ar71xx. Therefore, the MAC
addresses of the ethernet interfaces are being set via preinit instead.
The bdcfg partition contains 4 MAC address labels:
- lanmac
- wanmac
- wlanmac
- wlanmac_a
The first 3 all contain the same MAC address, which is also the one on
the label.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Reviewed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-06-07 23:11:34 +00:00
|
|
|
DEVICE_VARS += DAP_SIGNATURE
|
2018-09-04 21:27:02 +00:00
|
|
|
|
2018-12-31 15:41:07 +00:00
|
|
|
define Build/add-elecom-factory-initramfs
|
|
|
|
|
$(eval edimax_model=$(word 1,$(1)))
|
|
|
|
|
$(eval product=$(word 2,$(1)))
|
2018-09-10 07:30:28 +00:00
|
|
|
|
2018-12-31 15:41:07 +00:00
|
|
|
$(STAGING_DIR_HOST)/bin/mkedimaximg \
|
|
|
|
|
-b -s CSYS -m $(edimax_model) \
|
|
|
|
|
-f 0x70000 -S 0x01100000 \
|
|
|
|
|
-i $@ -o $@.factory
|
|
|
|
|
|
|
|
|
|
( \
|
|
|
|
|
echo -n -e "ELECOM\x00\x00$(product)" | dd bs=40 count=1 conv=sync; \
|
|
|
|
|
echo -n "0.00" | dd bs=16 count=1 conv=sync; \
|
|
|
|
|
dd if=$@.factory; \
|
|
|
|
|
) > $@.factory.new
|
|
|
|
|
|
|
|
|
|
if [ "$$(stat -c%s $@.factory.new)" -le $$(($(subst k,* 1024,$(subst m, * 1024k,$(IMAGE_SIZE))))) ]; then \
|
|
|
|
|
mv $@.factory.new $(BIN_DIR)/$(KERNEL_INITRAMFS_PREFIX)-factory.bin; \
|
|
|
|
|
else \
|
|
|
|
|
echo "WARNING: initramfs kernel image too big, cannot generate factory image" >&2; \
|
|
|
|
|
fi
|
2018-09-10 07:30:28 +00:00
|
|
|
endef
|
|
|
|
|
|
2019-08-22 12:34:45 +00:00
|
|
|
define Build/addpattern
|
|
|
|
|
-$(STAGING_DIR_HOST)/bin/addpattern -B $(ADDPATTERN_ID) \
|
|
|
|
|
-v v$(ADDPATTERN_VERSION) -i $@ -o $@.new
|
|
|
|
|
-mv "$@.new" "$@"
|
|
|
|
|
endef
|
|
|
|
|
|
2020-02-02 16:09:50 +00:00
|
|
|
define Build/append-md5sum-bin
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/mkhash md5 $@ | sed 's/../\\\\x&/g' |\
|
|
|
|
|
xargs echo -ne >> $@
|
|
|
|
|
endef
|
|
|
|
|
|
2019-08-22 12:34:45 +00:00
|
|
|
define Build/cybertan-trx
|
|
|
|
|
@echo -n '' > $@-empty.bin
|
|
|
|
|
-$(STAGING_DIR_HOST)/bin/trx -o $@.new \
|
|
|
|
|
-f $(IMAGE_KERNEL) -F $@-empty.bin \
|
|
|
|
|
-x 32 -a 0x10000 -x -32 -f $@
|
|
|
|
|
-mv "$@.new" "$@"
|
|
|
|
|
-rm $@-empty.bin
|
|
|
|
|
endef
|
|
|
|
|
|
ath79: add support for D-Link DAP-2695-A1
Hardware:
* SoC: Qualcomm Atheros QCA9558
* RAM: 256MB
* Flash: 16MB SPI NOR
* Ethernet: 2x 10/100/1000 (1x 802.3at PoE-PD)
* WiFi 2.4GHz: Qualcomm Atheros QCA9558
* WiFi 5GHz: Qualcomm Ahteros QCA9880-2R4E
* LEDS: 1x 5GHz, 1x 2.4GHz, 1x LAN1(POE), 1x LAN2, 1x POWER
* Buttons: 1x RESET
* UART: 1x RJ45 RS-232 Console port
Installation via stock firmware:
* Install the factory image via the stock firmware web interface
Installation via bootloader Emergency Web Server:
* Connect your PC to the LAN1(PoE) port
* Configure your PC with IP address 192.168.0.90
* Open a serial console to the Console port (115200,8n1)
* Press "q" within 2s when "press 'q' to stop autoboot" appears
* Open http://192.168.0.50 in a browser
* Upload either the factory or the sysupgrade image
* Once you see "write image into flash...OK,dest addr=0x9f070000" you
can power-cycle the device. Ignore "checksum bad" messages.
Setting the MAC addresses for the ethernet interfaces via
/etc/board.d/02_network adds the following snippets to
/etc/config/network:
config device 'lan_eth0_1_dev'
option name 'eth0.1'
option macaddr 'xx:xx:xx:xx:xx:xx'
config device 'wan_eth1_2_dev'
option name 'eth1.2'
option macaddr 'xx:xx:xx:xx:xx:xx'
This would result in the proper MAC addresses being set for the VLAN
subinterfaces, but the parent interfaces would still have a random MAC
address. Using untagged VLANs could solve this, but would still leave
those extra snippets in /etc/config/network, and then the device VLAN
setup would differ from the one used in ar71xx. Therefore, the MAC
addresses of the ethernet interfaces are being set via preinit instead.
The bdcfg partition contains 4 MAC address labels:
- lanmac
- wanmac
- wlanmac
- wlanmac_a
The first 3 all contain the same MAC address, which is also the one on
the label.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Reviewed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-06-07 23:11:34 +00:00
|
|
|
define Build/mkwrggimg
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/mkwrggimg -b \
|
|
|
|
|
-i $@ -o $@.imghdr -d /dev/mtdblock/1 \
|
|
|
|
|
-m $(DEVICE_MODEL)-$(DEVICE_VARIANT) -s $(DAP_SIGNATURE) \
|
|
|
|
|
-v $(VERSION_DIST) -B $(REVISION)
|
|
|
|
|
mv $@.imghdr $@
|
|
|
|
|
endef
|
|
|
|
|
|
2019-03-16 04:27:32 +00:00
|
|
|
define Build/nec-enc
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/nec-enc \
|
|
|
|
|
-i $@ -o $@.new -k $(1)
|
|
|
|
|
mv $@.new $@
|
|
|
|
|
endef
|
|
|
|
|
|
2018-12-08 06:18:17 +00:00
|
|
|
define Build/nec-fw
|
|
|
|
|
( stat -c%s $@ | tr -d "\n" | dd bs=16 count=1 conv=sync; ) >> $@
|
|
|
|
|
( \
|
|
|
|
|
echo -n -e "$(1)" | dd bs=16 count=1 conv=sync; \
|
|
|
|
|
echo -n "0.0.00" | dd bs=16 count=1 conv=sync; \
|
|
|
|
|
dd if=$@; \
|
|
|
|
|
) > $@.new
|
|
|
|
|
mv $@.new $@
|
|
|
|
|
endef
|
|
|
|
|
|
2019-08-04 14:13:45 +00:00
|
|
|
define Build/pisen_wmb001n-factory
|
|
|
|
|
-[ -f "$@" ] && \
|
|
|
|
|
mkdir -p "$@.tmp" && \
|
|
|
|
|
cp "$(KDIR)/loader-$(word 1,$(1)).uImage" "$@.tmp/uImage" && \
|
|
|
|
|
mv "$@" "$@.tmp/rootfs" && \
|
|
|
|
|
cp "bin/pisen_wmb001n_factory-header.bin" "$@" && \
|
|
|
|
|
$(TAR) -cp --numeric-owner --owner=0 --group=0 --mode=a-s --sort=name \
|
|
|
|
|
$(if $(SOURCE_DATE_EPOCH),--mtime="@$(SOURCE_DATE_EPOCH)") \
|
|
|
|
|
-C "$@.tmp" . | gzip -9n >> "$@" && \
|
|
|
|
|
rm -rf "$@.tmp"
|
|
|
|
|
endef
|
|
|
|
|
|
2020-02-02 16:09:50 +00:00
|
|
|
define Build/teltonika-fw-fake-checksum
|
|
|
|
|
# Teltonika U-Boot web based firmware upgrade/recovery routine compares
|
|
|
|
|
# 16 bytes from md5sum1[16] field in TP-Link v1 header (offset: 76 bytes
|
|
|
|
|
# from begin of the firmware file) with 16 bytes stored just before
|
|
|
|
|
# 0xdeadc0de marker. Values are only compared, MD5 sum is not verified.
|
|
|
|
|
let \
|
|
|
|
|
offs="$$(stat -c%s $@) - 20"; \
|
|
|
|
|
dd if=$@ bs=1 count=16 skip=76 |\
|
|
|
|
|
dd of=$@ bs=1 count=16 seek=$$offs conv=notrunc
|
|
|
|
|
endef
|
|
|
|
|
|
ath79: add support for D-Link DAP-2695-A1
Hardware:
* SoC: Qualcomm Atheros QCA9558
* RAM: 256MB
* Flash: 16MB SPI NOR
* Ethernet: 2x 10/100/1000 (1x 802.3at PoE-PD)
* WiFi 2.4GHz: Qualcomm Atheros QCA9558
* WiFi 5GHz: Qualcomm Ahteros QCA9880-2R4E
* LEDS: 1x 5GHz, 1x 2.4GHz, 1x LAN1(POE), 1x LAN2, 1x POWER
* Buttons: 1x RESET
* UART: 1x RJ45 RS-232 Console port
Installation via stock firmware:
* Install the factory image via the stock firmware web interface
Installation via bootloader Emergency Web Server:
* Connect your PC to the LAN1(PoE) port
* Configure your PC with IP address 192.168.0.90
* Open a serial console to the Console port (115200,8n1)
* Press "q" within 2s when "press 'q' to stop autoboot" appears
* Open http://192.168.0.50 in a browser
* Upload either the factory or the sysupgrade image
* Once you see "write image into flash...OK,dest addr=0x9f070000" you
can power-cycle the device. Ignore "checksum bad" messages.
Setting the MAC addresses for the ethernet interfaces via
/etc/board.d/02_network adds the following snippets to
/etc/config/network:
config device 'lan_eth0_1_dev'
option name 'eth0.1'
option macaddr 'xx:xx:xx:xx:xx:xx'
config device 'wan_eth1_2_dev'
option name 'eth1.2'
option macaddr 'xx:xx:xx:xx:xx:xx'
This would result in the proper MAC addresses being set for the VLAN
subinterfaces, but the parent interfaces would still have a random MAC
address. Using untagged VLANs could solve this, but would still leave
those extra snippets in /etc/config/network, and then the device VLAN
setup would differ from the one used in ar71xx. Therefore, the MAC
addresses of the ethernet interfaces are being set via preinit instead.
The bdcfg partition contains 4 MAC address labels:
- lanmac
- wanmac
- wlanmac
- wlanmac_a
The first 3 all contain the same MAC address, which is also the one on
the label.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Reviewed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-06-07 23:11:34 +00:00
|
|
|
define Build/wrgg-pad-rootfs
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/padjffs2 $(IMAGE_ROOTFS) -c 64 >>$@
|
|
|
|
|
endef
|
|
|
|
|
|
2018-12-29 09:22:32 +00:00
|
|
|
define Device/seama
|
|
|
|
|
KERNEL := kernel-bin | append-dtb | relocate-kernel | lzma
|
|
|
|
|
KERNEL_INITRAMFS := $$(KERNEL) | seama
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
SEAMA_MTDBLOCK := 1
|
|
|
|
|
|
|
|
|
|
# 64 bytes offset:
|
|
|
|
|
# - 28 bytes seama_header
|
|
|
|
|
# - 36 bytes of META data (4-bytes aligned)
|
|
|
|
|
IMAGE/default := append-kernel | pad-offset $$$$(BLOCKSIZE) 64 | append-rootfs
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := $$(IMAGE/default) | seama | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | pad-rootfs -x 64 | seama | \
|
2020-03-10 13:58:27 +00:00
|
|
|
seama-seal | check-size
|
2018-12-29 09:22:32 +00:00
|
|
|
SEAMA_SIGNATURE :=
|
|
|
|
|
endef
|
|
|
|
|
|
2019-08-22 12:34:45 +00:00
|
|
|
|
2019-04-11 16:31:23 +00:00
|
|
|
define Device/8dev_carambola2
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9331
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := 8devices
|
|
|
|
|
DEVICE_MODEL := Carambola2
|
2019-04-11 16:31:23 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-chipidea2
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
SUPPORTED_DEVICES += carambola2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += 8dev_carambola2
|
|
|
|
|
|
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>
2018-09-01 02:28:35 +00:00
|
|
|
define Device/adtran_bsap1880
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7161
|
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>
2018-09-01 02:28:35 +00:00
|
|
|
DEVICE_VENDOR := Adtran/Bluesocket
|
|
|
|
|
DEVICE_PACKAGES += -swconfig -uboot-envtools fconfig
|
2019-09-17 14:21:51 +00:00
|
|
|
KERNEL := kernel-bin | append-dtb | lzma | pad-to $$(BLOCKSIZE)
|
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>
2018-09-01 02:28:35 +00:00
|
|
|
KERNEL_INITRAMFS := kernel-bin | append-dtb
|
|
|
|
|
IMAGE_SIZE := 11200k
|
|
|
|
|
IMAGES += kernel.bin rootfs.bin
|
2019-09-17 14:21:51 +00:00
|
|
|
IMAGE/kernel.bin := append-kernel
|
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>
2018-09-01 02:28:35 +00:00
|
|
|
IMAGE/rootfs.bin := append-rootfs | pad-rootfs
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size | sysupgrade-tar rootfs=$$$$@ | append-metadata
|
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>
2018-09-01 02:28:35 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/adtran_bsap1800-v2
|
|
|
|
|
$(Device/adtran_bsap1880)
|
|
|
|
|
DEVICE_MODEL := BSAP-1800
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += adtran_bsap1800-v2
|
|
|
|
|
|
|
|
|
|
define Device/adtran_bsap1840
|
|
|
|
|
$(Device/adtran_bsap1880)
|
|
|
|
|
DEVICE_MODEL := BSAP-1840
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += adtran_bsap1840
|
|
|
|
|
|
2019-07-04 12:08:10 +00:00
|
|
|
define Device/alfa-network_ap121f
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9331
|
2019-07-04 12:08:10 +00:00
|
|
|
DEVICE_VENDOR := ALFA Network
|
|
|
|
|
DEVICE_MODEL := AP121F
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-chipidea2 kmod-usb-storage -swconfig
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
SUPPORTED_DEVICES += ap121f
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += alfa-network_ap121f
|
|
|
|
|
|
2019-05-05 17:56:03 +00:00
|
|
|
define Device/aruba_ap-105
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7161
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Aruba
|
|
|
|
|
DEVICE_MODEL := AP-105
|
2019-05-05 17:56:03 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
2020-03-05 14:42:18 +00:00
|
|
|
DEVICE_PACKAGES := kmod-i2c-gpio kmod-tpm-i2c-atmel
|
2019-05-05 17:56:03 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += aruba_ap-105
|
|
|
|
|
|
2020-04-12 11:33:01 +00:00
|
|
|
define Device/avm
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := AVM
|
2018-03-02 18:28:50 +00:00
|
|
|
KERNEL := kernel-bin | append-dtb | lzma | eva-image
|
|
|
|
|
KERNEL_INITRAMFS := $$(KERNEL)
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to 64k | \
|
2019-12-19 19:42:19 +00:00
|
|
|
append-squashfs-fakeroot-be | pad-to 256 | append-rootfs | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2020-04-12 11:33:01 +00:00
|
|
|
DEVICE_PACKAGES := fritz-tffs
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/avm_fritz1750e
|
|
|
|
|
$(Device/avm)
|
|
|
|
|
SOC := qca9556
|
|
|
|
|
IMAGE_SIZE := 15232k
|
|
|
|
|
DEVICE_MODEL := FRITZ!WLAN Repeater 1750E
|
2020-04-17 12:15:06 +00:00
|
|
|
DEVICE_PACKAGES += rssileds kmod-ath10k-ct-smallbuffers \
|
2020-04-12 11:33:01 +00:00
|
|
|
ath10k-firmware-qca988x-ct -swconfig
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += avm_fritz1750e
|
|
|
|
|
|
|
|
|
|
define Device/avm_fritz300e
|
|
|
|
|
$(Device/avm)
|
|
|
|
|
SOC := ar7242
|
|
|
|
|
IMAGE_SIZE := 15232k
|
|
|
|
|
DEVICE_MODEL := FRITZ!WLAN Repeater 300E
|
|
|
|
|
DEVICE_PACKAGES += rssileds -swconfig
|
2020-02-13 13:46:52 +00:00
|
|
|
SUPPORTED_DEVICES += fritz300e
|
2018-03-02 18:28:50 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += avm_fritz300e
|
|
|
|
|
|
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>
2018-08-18 16:30:46 +00:00
|
|
|
define Device/avm_fritz4020
|
2020-04-12 11:33:01 +00:00
|
|
|
$(Device/avm)
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9561
|
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>
2018-08-18 16:30:46 +00:00
|
|
|
IMAGE_SIZE := 15232k
|
2020-04-12 11:33:01 +00:00
|
|
|
DEVICE_MODEL := FRITZ!Box 4020
|
2019-02-23 12:12:49 +00:00
|
|
|
SUPPORTED_DEVICES += fritz4020
|
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>
2018-08-18 16:30:46 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += avm_fritz4020
|
|
|
|
|
|
2020-04-14 01:58:37 +00:00
|
|
|
define Device/avm_fritz450e
|
|
|
|
|
$(Device/avm)
|
|
|
|
|
SOC := qca9556
|
|
|
|
|
IMAGE_SIZE := 15232k
|
|
|
|
|
DEVICE_MODEL := FRITZ!WLAN Repeater 450E
|
|
|
|
|
SUPPORTED_DEVICES += fritz450e
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += avm_fritz450e
|
|
|
|
|
|
2018-09-11 11:50:35 +00:00
|
|
|
define Device/buffalo_bhr-4grv
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7242
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Buffalo
|
|
|
|
|
DEVICE_MODEL := BHR-4GRV
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport
|
2018-09-11 11:50:35 +00:00
|
|
|
IMAGE_SIZE := 32256k
|
|
|
|
|
IMAGES += factory.bin tftp.bin
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | append-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
pad-rootfs | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | buffalo-enc BHR-4GRV 1.99 | \
|
|
|
|
|
buffalo-tag BHR-4GRV 3
|
2018-09-11 11:50:35 +00:00
|
|
|
IMAGE/tftp.bin := $$(IMAGE/default) | buffalo-tftp-header
|
|
|
|
|
SUPPORTED_DEVICES += wzr-hp-g450h
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += buffalo_bhr-4grv
|
|
|
|
|
|
ath79: modify mtd partitions for Buffalo BHR-4GRV2
This commit modifies mtd partitions define for Buffalo BHR-4GRV2 and
move it to generic subtarget.
In Buffalo BHR-4GRV2, "kernel" partition is located behined "rootfs"
partition in the stock firmware. This causes the size of the kernel
to be limited by the fixed value.
0x50000 0xe80000 0xff0000
+-------------------------------+--------------+
| rootfs | kernel |
| (14528k) | (1472k) |
+-------------------------------+--------------+
After ar71xx was updated to Kernel 4.14, the kernel size of BHR-4GRV2
exceeded the limit, and it breaks builds on official buildbot.
Since this issue was also confirmed in ath79, I modified the mtd
partitions to get rid of that limitation.
0x50000 0xff0000
+----------------------------------------------+
| firmware |
| (16000k) |
+----------------------------------------------+
However, this commit breaks compatibility with ar71xx firmware, so I
dropped "SUPPORTED_DEVICES += bhr-4grv2".
This commit requires new flash instruction instead of the old one.
Flash instruction using initramfs image:
1. Connect the computer to the LAN port of BHR-4GRV2
2. Set the IP address of the computer to 192.168.12.10
3. Rename the OpenWrt initramfs image to
"bhr4grv2-uImage-initramfs-gzip.bin" and place it into the TFTP
directory
4. Start the tftp server on the computer
5. While holding down the "ECO" button, connect power cable to
BHR-4GRV2 and turn on it
6. Flashing (orange) diag LED and release the finger from the button,
BHR-4GRV2 downloads the intiramfs image from TFTP server and boot
with it
7. On the initramfs image, create "/etc/fw_env.config" file with
following contents
/dev/mtd1 0x0 0x10000 0x10000
8. Execute following commands to add environment variables for
u-boot
fw_setenv ipaddr 192.168.12.1
fw_setenv serverip 192.168.12.10
fw_setenv ethaddr 00:aa:bb:cc:dd:ee
fw_setenv bootcmd "bootm 0x9f050000 || bootm 0x9fe80000"
9. Perform sysupgrade with squashfs-sysupgrade image
10. Wait ~150 seconds to complete flashing
And this commit includes small fix; BHR-4GRV2 has QCA9557 as a SoC,
not QCA9558.
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-11-06 13:37:43 +00:00
|
|
|
define Device/buffalo_bhr-4grv2
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9557
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Buffalo
|
|
|
|
|
DEVICE_MODEL := BHR-4GRV2
|
ath79: modify mtd partitions for Buffalo BHR-4GRV2
This commit modifies mtd partitions define for Buffalo BHR-4GRV2 and
move it to generic subtarget.
In Buffalo BHR-4GRV2, "kernel" partition is located behined "rootfs"
partition in the stock firmware. This causes the size of the kernel
to be limited by the fixed value.
0x50000 0xe80000 0xff0000
+-------------------------------+--------------+
| rootfs | kernel |
| (14528k) | (1472k) |
+-------------------------------+--------------+
After ar71xx was updated to Kernel 4.14, the kernel size of BHR-4GRV2
exceeded the limit, and it breaks builds on official buildbot.
Since this issue was also confirmed in ath79, I modified the mtd
partitions to get rid of that limitation.
0x50000 0xff0000
+----------------------------------------------+
| firmware |
| (16000k) |
+----------------------------------------------+
However, this commit breaks compatibility with ar71xx firmware, so I
dropped "SUPPORTED_DEVICES += bhr-4grv2".
This commit requires new flash instruction instead of the old one.
Flash instruction using initramfs image:
1. Connect the computer to the LAN port of BHR-4GRV2
2. Set the IP address of the computer to 192.168.12.10
3. Rename the OpenWrt initramfs image to
"bhr4grv2-uImage-initramfs-gzip.bin" and place it into the TFTP
directory
4. Start the tftp server on the computer
5. While holding down the "ECO" button, connect power cable to
BHR-4GRV2 and turn on it
6. Flashing (orange) diag LED and release the finger from the button,
BHR-4GRV2 downloads the intiramfs image from TFTP server and boot
with it
7. On the initramfs image, create "/etc/fw_env.config" file with
following contents
/dev/mtd1 0x0 0x10000 0x10000
8. Execute following commands to add environment variables for
u-boot
fw_setenv ipaddr 192.168.12.1
fw_setenv serverip 192.168.12.10
fw_setenv ethaddr 00:aa:bb:cc:dd:ee
fw_setenv bootcmd "bootm 0x9f050000 || bootm 0x9fe80000"
9. Perform sysupgrade with squashfs-sysupgrade image
10. Wait ~150 seconds to complete flashing
And this commit includes small fix; BHR-4GRV2 has QCA9557 as a SoC,
not QCA9558.
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-11-06 13:37:43 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += buffalo_bhr-4grv2
|
|
|
|
|
|
ath79: add support for Buffalo WZR-HP-AG300H
Buffalo WZR-HP-AG300H is a dual band router based on
Qualcom Atheros AR7161 rev 2
Specification:
- 680 MHz CPU (Qualcomm Atheros AR7161)
- 128 MiB RAM (2x Samsung K4H511638G-LCCC)
- 32 MiB Flash (2x Winbond 25Q128BVFG)
- WiFi 5 GHz a/n (Atheros AR9220)
- WiFi 2.4 GHz b/g/n (Atheros AR9223)
- 1000Base-T WAN (Atheros AR7161)
- 4x 1000Base-T Switch (Atheros AR8316)
- 1x USB 2.0
- 3 Buttons (AOSS/WPS, Reset, USB Eject)
- 2 Slide switches (Router (on/off/auto), Movie Engine (on/off))
- 9 LEDs (Power green, WLAN 2GHz green, WLAN 2GHz amber,
WLAN 5GHz green, WLAN 5GHz LED amber, Router green,
Diag red, Movie Engine blue, USB green)
It is already supported by the ar71xx target.
For more information on the device visit the wiki:
<https://openwrt.org/toh/buffalo/wzr-hp-ag300h>
Serial console:
- The UART Header is next to Movie Engine Switch.
- Pinout is RX - TX - GND - 3.3V (Square Pad is 3.3V)
- The Serial setting is 115200-8-N-1.
Installation of OpenWRT from vendor firmware:
- Connect to the Web-interface at http://192.168.11.1
- Go to “Administration” → “Firmware Upgrade”
- Upload the OpenWrt factory image
Tested:
- Ethernet (LAN, WAN)
- WiFi
- Installation
- via TFTP rescue
- via factory image
- on firmware v1.77 (28-05-2012)
- on pro firmware v24SP2 r30356 (26-03-2018)
- via sysupgrade from ar71xx
(wlan devices don't work because of new names)
- via sysupgrade from itself
- Buttons
- LEDS
- USB (Power control and device recognition)
Signed-off-by: Bernhard Frauendienst <openwrt@nospam.obeliks.de>
2018-08-18 16:28:02 +00:00
|
|
|
define Device/buffalo_wzr-hp-ag300h
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7161
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Buffalo
|
|
|
|
|
DEVICE_MODEL := WZR-HP-AG300H
|
2019-10-22 11:08:25 +00:00
|
|
|
IMAGE_SIZE := 32320k
|
ath79: add support for Buffalo WZR-HP-AG300H
Buffalo WZR-HP-AG300H is a dual band router based on
Qualcom Atheros AR7161 rev 2
Specification:
- 680 MHz CPU (Qualcomm Atheros AR7161)
- 128 MiB RAM (2x Samsung K4H511638G-LCCC)
- 32 MiB Flash (2x Winbond 25Q128BVFG)
- WiFi 5 GHz a/n (Atheros AR9220)
- WiFi 2.4 GHz b/g/n (Atheros AR9223)
- 1000Base-T WAN (Atheros AR7161)
- 4x 1000Base-T Switch (Atheros AR8316)
- 1x USB 2.0
- 3 Buttons (AOSS/WPS, Reset, USB Eject)
- 2 Slide switches (Router (on/off/auto), Movie Engine (on/off))
- 9 LEDs (Power green, WLAN 2GHz green, WLAN 2GHz amber,
WLAN 5GHz green, WLAN 5GHz LED amber, Router green,
Diag red, Movie Engine blue, USB green)
It is already supported by the ar71xx target.
For more information on the device visit the wiki:
<https://openwrt.org/toh/buffalo/wzr-hp-ag300h>
Serial console:
- The UART Header is next to Movie Engine Switch.
- Pinout is RX - TX - GND - 3.3V (Square Pad is 3.3V)
- The Serial setting is 115200-8-N-1.
Installation of OpenWRT from vendor firmware:
- Connect to the Web-interface at http://192.168.11.1
- Go to “Administration” → “Firmware Upgrade”
- Upload the OpenWrt factory image
Tested:
- Ethernet (LAN, WAN)
- WiFi
- Installation
- via TFTP rescue
- via factory image
- on firmware v1.77 (28-05-2012)
- on pro firmware v24SP2 r30356 (26-03-2018)
- via sysupgrade from ar71xx
(wlan devices don't work because of new names)
- via sysupgrade from itself
- Buttons
- LEDS
- USB (Power control and device recognition)
Signed-off-by: Bernhard Frauendienst <openwrt@nospam.obeliks.de>
2018-08-18 16:28:02 +00:00
|
|
|
IMAGES += factory.bin tftp.bin
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | append-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
pad-rootfs | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | buffalo-enc WZR-HP-AG300H 1.99 | \
|
|
|
|
|
buffalo-tag WZR-HP-AG300H 3
|
ath79: add support for Buffalo WZR-HP-AG300H
Buffalo WZR-HP-AG300H is a dual band router based on
Qualcom Atheros AR7161 rev 2
Specification:
- 680 MHz CPU (Qualcomm Atheros AR7161)
- 128 MiB RAM (2x Samsung K4H511638G-LCCC)
- 32 MiB Flash (2x Winbond 25Q128BVFG)
- WiFi 5 GHz a/n (Atheros AR9220)
- WiFi 2.4 GHz b/g/n (Atheros AR9223)
- 1000Base-T WAN (Atheros AR7161)
- 4x 1000Base-T Switch (Atheros AR8316)
- 1x USB 2.0
- 3 Buttons (AOSS/WPS, Reset, USB Eject)
- 2 Slide switches (Router (on/off/auto), Movie Engine (on/off))
- 9 LEDs (Power green, WLAN 2GHz green, WLAN 2GHz amber,
WLAN 5GHz green, WLAN 5GHz LED amber, Router green,
Diag red, Movie Engine blue, USB green)
It is already supported by the ar71xx target.
For more information on the device visit the wiki:
<https://openwrt.org/toh/buffalo/wzr-hp-ag300h>
Serial console:
- The UART Header is next to Movie Engine Switch.
- Pinout is RX - TX - GND - 3.3V (Square Pad is 3.3V)
- The Serial setting is 115200-8-N-1.
Installation of OpenWRT from vendor firmware:
- Connect to the Web-interface at http://192.168.11.1
- Go to “Administration” → “Firmware Upgrade”
- Upload the OpenWrt factory image
Tested:
- Ethernet (LAN, WAN)
- WiFi
- Installation
- via TFTP rescue
- via factory image
- on firmware v1.77 (28-05-2012)
- on pro firmware v24SP2 r30356 (26-03-2018)
- via sysupgrade from ar71xx
(wlan devices don't work because of new names)
- via sysupgrade from itself
- Buttons
- LEDS
- USB (Power control and device recognition)
Signed-off-by: Bernhard Frauendienst <openwrt@nospam.obeliks.de>
2018-08-18 16:28:02 +00:00
|
|
|
IMAGE/tftp.bin := $$(IMAGE/default) | buffalo-tftp-header
|
2019-12-19 19:42:19 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-ohci kmod-usb2 kmod-usb-ledtrig-usbport \
|
|
|
|
|
kmod-leds-reset kmod-owl-loader
|
ath79: add support for Buffalo WZR-HP-AG300H
Buffalo WZR-HP-AG300H is a dual band router based on
Qualcom Atheros AR7161 rev 2
Specification:
- 680 MHz CPU (Qualcomm Atheros AR7161)
- 128 MiB RAM (2x Samsung K4H511638G-LCCC)
- 32 MiB Flash (2x Winbond 25Q128BVFG)
- WiFi 5 GHz a/n (Atheros AR9220)
- WiFi 2.4 GHz b/g/n (Atheros AR9223)
- 1000Base-T WAN (Atheros AR7161)
- 4x 1000Base-T Switch (Atheros AR8316)
- 1x USB 2.0
- 3 Buttons (AOSS/WPS, Reset, USB Eject)
- 2 Slide switches (Router (on/off/auto), Movie Engine (on/off))
- 9 LEDs (Power green, WLAN 2GHz green, WLAN 2GHz amber,
WLAN 5GHz green, WLAN 5GHz LED amber, Router green,
Diag red, Movie Engine blue, USB green)
It is already supported by the ar71xx target.
For more information on the device visit the wiki:
<https://openwrt.org/toh/buffalo/wzr-hp-ag300h>
Serial console:
- The UART Header is next to Movie Engine Switch.
- Pinout is RX - TX - GND - 3.3V (Square Pad is 3.3V)
- The Serial setting is 115200-8-N-1.
Installation of OpenWRT from vendor firmware:
- Connect to the Web-interface at http://192.168.11.1
- Go to “Administration” → “Firmware Upgrade”
- Upload the OpenWrt factory image
Tested:
- Ethernet (LAN, WAN)
- WiFi
- Installation
- via TFTP rescue
- via factory image
- on firmware v1.77 (28-05-2012)
- on pro firmware v24SP2 r30356 (26-03-2018)
- via sysupgrade from ar71xx
(wlan devices don't work because of new names)
- via sysupgrade from itself
- Buttons
- LEDS
- USB (Power control and device recognition)
Signed-off-by: Bernhard Frauendienst <openwrt@nospam.obeliks.de>
2018-08-18 16:28:02 +00:00
|
|
|
SUPPORTED_DEVICES += wzr-hp-ag300h
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += buffalo_wzr-hp-ag300h
|
|
|
|
|
|
2018-10-02 13:28:45 +00:00
|
|
|
define Device/buffalo_wzr-hp-g302h-a1a0
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7242
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Buffalo
|
|
|
|
|
DEVICE_MODEL := WZR-HP-G302H
|
|
|
|
|
DEVICE_VARIANT := A1A0
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport
|
2018-10-02 13:28:45 +00:00
|
|
|
IMAGE_SIZE := 32128k
|
|
|
|
|
IMAGES += factory.bin tftp.bin
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | append-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
pad-rootfs | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | buffalo-enc WZR-HP-G302H 1.99 | \
|
|
|
|
|
buffalo-tag WZR-HP-G302H 4
|
2018-10-02 13:28:45 +00:00
|
|
|
IMAGE/tftp.bin := $$(IMAGE/default) | buffalo-tftp-header
|
|
|
|
|
SUPPORTED_DEVICES += wzr-hp-g300nh2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += buffalo_wzr-hp-g302h-a1a0
|
|
|
|
|
|
2018-08-02 07:14:10 +00:00
|
|
|
define Device/buffalo_wzr-hp-g450h
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7242
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Buffalo
|
|
|
|
|
DEVICE_MODEL := WZR-HP-G450H/WZR-450HP
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport
|
2018-08-02 07:14:10 +00:00
|
|
|
IMAGE_SIZE := 32256k
|
2018-09-11 11:13:17 +00:00
|
|
|
IMAGES += factory.bin tftp.bin
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | append-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
pad-rootfs | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | buffalo-enc WZR-HP-G450H 1.99 | \
|
|
|
|
|
buffalo-tag WZR-HP-G450H 3
|
2018-09-11 11:13:17 +00:00
|
|
|
IMAGE/tftp.bin := $$(IMAGE/default) | buffalo-tftp-header
|
2018-08-02 07:14:10 +00:00
|
|
|
SUPPORTED_DEVICES += wzr-hp-g450h
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += buffalo_wzr-hp-g450h
|
|
|
|
|
|
ath79: add support for COMFAST CF-E110N
This patch adds support for the COMFAST CF-E110N, an outdoor wireless
CPE with two Ethernet ports and a 802.11bgn radio.
Specifications:
- 650/400/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, both with PoE-in support
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- 2T2R 2.4 GHz, up to 26 dBm
- 11 dBi built-in antenna
- POWER/LAN/WAN/WLAN green LEDs
- 4x RSSI LEDs (2x red, 2x green)
- UART (115200 8N1) and GPIO (J9) headers on PCB
Flashing instructions:
The original firmware is based on OpenWrt so a sysupgrade image can be
installed via the stock web GUI. Settings from the original firmware
will be saved and restored on the new want, so a factory reset will be
needed: once the new firmware is flashed, perform the factory reset by
pushing the reset button several times during the boot process, while the
WAN LED flashes, until it starts flashing quicker.
The U-boot bootloader contains a recovery HTTP server to upload the
firmware. Push the reset button while powering the device on and keep it
pressed for >10 seconds. The recovery page will be at http://192.168.1.1
Notes:
The device is advertised, sold and labeled as "CF-E110N", but the
bootloader and the stock firmware identify it as "v2".
Acknowledgments:
Petr Štetiar <ynezz@true.cz>
Sebastian Kemper <sebastian_ml@gmx.net>
Chuanhong Guo <gch981213@gmail.com>
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
[drop unused labels from devicetree source file]
Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
|
|
|
define Device/comfast_cf-e110n-v2
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9533
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-E110N
|
|
|
|
|
DEVICE_VARIANT := v2
|
ath79: add support for COMFAST CF-E110N
This patch adds support for the COMFAST CF-E110N, an outdoor wireless
CPE with two Ethernet ports and a 802.11bgn radio.
Specifications:
- 650/400/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, both with PoE-in support
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- 2T2R 2.4 GHz, up to 26 dBm
- 11 dBi built-in antenna
- POWER/LAN/WAN/WLAN green LEDs
- 4x RSSI LEDs (2x red, 2x green)
- UART (115200 8N1) and GPIO (J9) headers on PCB
Flashing instructions:
The original firmware is based on OpenWrt so a sysupgrade image can be
installed via the stock web GUI. Settings from the original firmware
will be saved and restored on the new want, so a factory reset will be
needed: once the new firmware is flashed, perform the factory reset by
pushing the reset button several times during the boot process, while the
WAN LED flashes, until it starts flashing quicker.
The U-boot bootloader contains a recovery HTTP server to upload the
firmware. Push the reset button while powering the device on and keep it
pressed for >10 seconds. The recovery page will be at http://192.168.1.1
Notes:
The device is advertised, sold and labeled as "CF-E110N", but the
bootloader and the stock firmware identify it as "v2".
Acknowledgments:
Petr Štetiar <ynezz@true.cz>
Sebastian Kemper <sebastian_ml@gmx.net>
Chuanhong Guo <gch981213@gmail.com>
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
[drop unused labels from devicetree source file]
Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
|
|
|
DEVICE_PACKAGES := rssileds kmod-leds-gpio -swconfig -uboot-envtools
|
|
|
|
|
IMAGE_SIZE := 16192k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-e110n-v2
|
|
|
|
|
|
ath79: add support for COMFAST CF-E120A v3
This patch adds support for the COMFAST CF-E120A v3, an outdoor wireless
CPE with two Ethernet ports and a 802.11an radio.
Specifications:
- AR9344 SoC
- 535/400/267 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, both with PoE-in support
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 5 GHz, up to 25 dBm
- 11 dBi built-in antenna
- POWER/LAN/WAN/WLAN green LEDs
- 4x RSSI LEDs (2x red, 2x green)
- UART (115200 8N1) and GPIO (J9) headers on PCB
Flashing instructions:
The original firmware is based on OpenWrt so a sysupgrade image can be
installed via the stock web GUI. Settings from the original firmware
will be saved and restored on the new one, so a factory reset will be
needed. To do so, once the new firmware is flashed, enter into failsafe
mode by pressing the reset button several times during the boot
process, while while the WAN LED flashes, until it starts flashing
faster. Once in failsafe mode, perform a factory reset as usual.
The U-boot bootloader contains a recovery HTTP server to upload the
firmware. Push the reset button while powering the device on and
keep it pressed for >10 seconds. The recovery page will be at
http://192.168.1.1
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
2018-12-29 19:44:43 +00:00
|
|
|
define Device/comfast_cf-e120a-v3
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-E120A
|
|
|
|
|
DEVICE_VARIANT := v3
|
ath79: add support for COMFAST CF-E120A v3
This patch adds support for the COMFAST CF-E120A v3, an outdoor wireless
CPE with two Ethernet ports and a 802.11an radio.
Specifications:
- AR9344 SoC
- 535/400/267 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, both with PoE-in support
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 5 GHz, up to 25 dBm
- 11 dBi built-in antenna
- POWER/LAN/WAN/WLAN green LEDs
- 4x RSSI LEDs (2x red, 2x green)
- UART (115200 8N1) and GPIO (J9) headers on PCB
Flashing instructions:
The original firmware is based on OpenWrt so a sysupgrade image can be
installed via the stock web GUI. Settings from the original firmware
will be saved and restored on the new one, so a factory reset will be
needed. To do so, once the new firmware is flashed, enter into failsafe
mode by pressing the reset button several times during the boot
process, while while the WAN LED flashes, until it starts flashing
faster. Once in failsafe mode, perform a factory reset as usual.
The U-boot bootloader contains a recovery HTTP server to upload the
firmware. Push the reset button while powering the device on and
keep it pressed for >10 seconds. The recovery page will be at
http://192.168.1.1
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
2018-12-29 19:44:43 +00:00
|
|
|
DEVICE_PACKAGES := rssileds kmod-leds-gpio -uboot-envtools
|
|
|
|
|
IMAGE_SIZE := 8000k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-e120a-v3
|
|
|
|
|
|
2020-03-27 03:32:55 +00:00
|
|
|
define Device/comfast_cf-e130n-v2
|
|
|
|
|
SOC := qca9531
|
|
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-E130N
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
DEVICE_PACKAGES := rssileds kmod-leds-gpio -swconfig -uboot-envtools
|
|
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-e130n-v2
|
|
|
|
|
|
ath79: add support for COMFAST CF-E313AC
This patch adds support for the COMFAST CF-E313AC, an outdoor wireless
CPE with two Ethernet ports and a 802.11ac radio.
Specifications:
- QCA9531 SoC
- 650/400/216 MHz (CPU/DDR/AHB)
- 1x 10/100 Mbps WAN Ethernet, 48V PoE-in
- 1x 10/100 Mbps LAN Ethernet, pass-through 48V PoE-out
- 1x manual pass-through PoE switch
- 64 MB RAM (DDR2)
- 16 MB FLASH
- QCA9886 2T2R 5 GHz 802.11ac, 23 dBm
- 12 dBi built-in antenna
- POWER/LAN/WAN/WLAN green LEDs
- 4x RSSI LEDs (2x red, 2x green)
- UART (115200 8N1)
Flashing instructions:
The original firmware is based on OpenWrt so a sysupgrade image can be
installed via the stock web GUI. Settings from the original firmware
will be saved and restored on the new one, so a factory reset will be
needed. To do so, once the new firmware is flashed, enter into failsafe
mode by pressing the reset button several times during the boot
process, while the WAN LED flashes, until it starts flashing faster.
Once in failsafe mode, perform a factory reset as usual.
Alternatively, the U-boot bootloader contains a recovery HTTP server
to upload the firmware. Push the reset button while powering the
device on and keep it pressed for >10 seconds. The device's LEDs will
blink several times and the recovery page will be at
http://192.168.1.1; use it to upload the sysupgrade image.
Note:
Four MAC addresses are stored in the "art" partition (read-only):
- 0x0000: 40:A5:EF:AA:AA:A0
- 0x0006: 40:A5:EF:AA:AA:A2
- 0x1002: 40:A5:EF:AA:AA:A1
- 0x5006: 40:A5:EF:AA.AA:A3 (inside the 5 GHz calibration data)
The stock firmware assigns MAC addresses to physical and virtual
interfaces in a very particular way:
- eth0 corresponds to the physical Ethernet port labeled as WAN
- eth1 corresponds to the physical Ethernet port labeled as LAN
- eth0 belongs to the bridge interface br-wan
- eth1 belongs to the bridge interface br-lan
- eth0 is assigned the MAC from 0x0 (*:A0)
- eth1 is assigned the MAC from 0x1002 (*:A1)
- br-wan is forced to use the MAC from 0x1002 (*:A1)
- br-lan is forced to use the MAC from 0x0 (*:A0)
- radio0 uses the calibration data from 0x5000 (which contains
a valid MAC address, *:A3). However, it is overwritten by the
one at 0x6 (*:A2)
This commit preserves the LAN/WAN roles of the physical Ethernet
ports (as labeled on the router) and the MAC addresses they expose
by default (i.e., *:A0 on LAN, *:A1 on WAN), but swaps the position
of the eth0/eth1 compared to the stock firmware:
- eth0 corresponds to the physical Ethernet port labeled as LAN
- eth1 corresponds to the physical Ethernet port labeled as WAN
- eth0 belongs to the bridge interface br-lan
- eth1 is the interface at @wan
- eth0 is assigned the MAC from 0x0 (*:A0)
- eth1 is assigned the MAC from 0x1002 (*:A1)
- br-lan inherits the MAC from eth0 (*:A0)
- @wan inherits the MAC from eth1 (*:A1)
- radio0's MAC is overwritten to the one at 0x6
This way, eth0/eth1's positions differ from the stock firmware, but
the weird MAC ressignations in br-lan/br-wan are avoided while the
external behaviour of the router is maintained. Additionally, WAN
port is connected to the PHY gmac, allowing to monitor the link
status (e.g., to restart DHCP negotiation when plugging a cable).
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
2019-03-18 12:20:47 +00:00
|
|
|
define Device/comfast_cf-e313ac
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9531
|
ath79: add support for COMFAST CF-E313AC
This patch adds support for the COMFAST CF-E313AC, an outdoor wireless
CPE with two Ethernet ports and a 802.11ac radio.
Specifications:
- QCA9531 SoC
- 650/400/216 MHz (CPU/DDR/AHB)
- 1x 10/100 Mbps WAN Ethernet, 48V PoE-in
- 1x 10/100 Mbps LAN Ethernet, pass-through 48V PoE-out
- 1x manual pass-through PoE switch
- 64 MB RAM (DDR2)
- 16 MB FLASH
- QCA9886 2T2R 5 GHz 802.11ac, 23 dBm
- 12 dBi built-in antenna
- POWER/LAN/WAN/WLAN green LEDs
- 4x RSSI LEDs (2x red, 2x green)
- UART (115200 8N1)
Flashing instructions:
The original firmware is based on OpenWrt so a sysupgrade image can be
installed via the stock web GUI. Settings from the original firmware
will be saved and restored on the new one, so a factory reset will be
needed. To do so, once the new firmware is flashed, enter into failsafe
mode by pressing the reset button several times during the boot
process, while the WAN LED flashes, until it starts flashing faster.
Once in failsafe mode, perform a factory reset as usual.
Alternatively, the U-boot bootloader contains a recovery HTTP server
to upload the firmware. Push the reset button while powering the
device on and keep it pressed for >10 seconds. The device's LEDs will
blink several times and the recovery page will be at
http://192.168.1.1; use it to upload the sysupgrade image.
Note:
Four MAC addresses are stored in the "art" partition (read-only):
- 0x0000: 40:A5:EF:AA:AA:A0
- 0x0006: 40:A5:EF:AA:AA:A2
- 0x1002: 40:A5:EF:AA:AA:A1
- 0x5006: 40:A5:EF:AA.AA:A3 (inside the 5 GHz calibration data)
The stock firmware assigns MAC addresses to physical and virtual
interfaces in a very particular way:
- eth0 corresponds to the physical Ethernet port labeled as WAN
- eth1 corresponds to the physical Ethernet port labeled as LAN
- eth0 belongs to the bridge interface br-wan
- eth1 belongs to the bridge interface br-lan
- eth0 is assigned the MAC from 0x0 (*:A0)
- eth1 is assigned the MAC from 0x1002 (*:A1)
- br-wan is forced to use the MAC from 0x1002 (*:A1)
- br-lan is forced to use the MAC from 0x0 (*:A0)
- radio0 uses the calibration data from 0x5000 (which contains
a valid MAC address, *:A3). However, it is overwritten by the
one at 0x6 (*:A2)
This commit preserves the LAN/WAN roles of the physical Ethernet
ports (as labeled on the router) and the MAC addresses they expose
by default (i.e., *:A0 on LAN, *:A1 on WAN), but swaps the position
of the eth0/eth1 compared to the stock firmware:
- eth0 corresponds to the physical Ethernet port labeled as LAN
- eth1 corresponds to the physical Ethernet port labeled as WAN
- eth0 belongs to the bridge interface br-lan
- eth1 is the interface at @wan
- eth0 is assigned the MAC from 0x0 (*:A0)
- eth1 is assigned the MAC from 0x1002 (*:A1)
- br-lan inherits the MAC from eth0 (*:A0)
- @wan inherits the MAC from eth1 (*:A1)
- radio0's MAC is overwritten to the one at 0x6
This way, eth0/eth1's positions differ from the stock firmware, but
the weird MAC ressignations in br-lan/br-wan are avoided while the
external behaviour of the router is maintained. Additionally, WAN
port is connected to the PHY gmac, allowing to monitor the link
status (e.g., to restart DHCP negotiation when plugging a cable).
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
2019-03-18 12:20:47 +00:00
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-E313AC
|
2019-12-22 20:05:13 +00:00
|
|
|
DEVICE_PACKAGES := rssileds kmod-leds-gpio kmod-ath10k-ct-smallbuffers \
|
2019-12-19 19:42:19 +00:00
|
|
|
ath10k-firmware-qca9888-ct -swconfig -uboot-envtools
|
ath79: add support for COMFAST CF-E313AC
This patch adds support for the COMFAST CF-E313AC, an outdoor wireless
CPE with two Ethernet ports and a 802.11ac radio.
Specifications:
- QCA9531 SoC
- 650/400/216 MHz (CPU/DDR/AHB)
- 1x 10/100 Mbps WAN Ethernet, 48V PoE-in
- 1x 10/100 Mbps LAN Ethernet, pass-through 48V PoE-out
- 1x manual pass-through PoE switch
- 64 MB RAM (DDR2)
- 16 MB FLASH
- QCA9886 2T2R 5 GHz 802.11ac, 23 dBm
- 12 dBi built-in antenna
- POWER/LAN/WAN/WLAN green LEDs
- 4x RSSI LEDs (2x red, 2x green)
- UART (115200 8N1)
Flashing instructions:
The original firmware is based on OpenWrt so a sysupgrade image can be
installed via the stock web GUI. Settings from the original firmware
will be saved and restored on the new one, so a factory reset will be
needed. To do so, once the new firmware is flashed, enter into failsafe
mode by pressing the reset button several times during the boot
process, while the WAN LED flashes, until it starts flashing faster.
Once in failsafe mode, perform a factory reset as usual.
Alternatively, the U-boot bootloader contains a recovery HTTP server
to upload the firmware. Push the reset button while powering the
device on and keep it pressed for >10 seconds. The device's LEDs will
blink several times and the recovery page will be at
http://192.168.1.1; use it to upload the sysupgrade image.
Note:
Four MAC addresses are stored in the "art" partition (read-only):
- 0x0000: 40:A5:EF:AA:AA:A0
- 0x0006: 40:A5:EF:AA:AA:A2
- 0x1002: 40:A5:EF:AA:AA:A1
- 0x5006: 40:A5:EF:AA.AA:A3 (inside the 5 GHz calibration data)
The stock firmware assigns MAC addresses to physical and virtual
interfaces in a very particular way:
- eth0 corresponds to the physical Ethernet port labeled as WAN
- eth1 corresponds to the physical Ethernet port labeled as LAN
- eth0 belongs to the bridge interface br-wan
- eth1 belongs to the bridge interface br-lan
- eth0 is assigned the MAC from 0x0 (*:A0)
- eth1 is assigned the MAC from 0x1002 (*:A1)
- br-wan is forced to use the MAC from 0x1002 (*:A1)
- br-lan is forced to use the MAC from 0x0 (*:A0)
- radio0 uses the calibration data from 0x5000 (which contains
a valid MAC address, *:A3). However, it is overwritten by the
one at 0x6 (*:A2)
This commit preserves the LAN/WAN roles of the physical Ethernet
ports (as labeled on the router) and the MAC addresses they expose
by default (i.e., *:A0 on LAN, *:A1 on WAN), but swaps the position
of the eth0/eth1 compared to the stock firmware:
- eth0 corresponds to the physical Ethernet port labeled as LAN
- eth1 corresponds to the physical Ethernet port labeled as WAN
- eth0 belongs to the bridge interface br-lan
- eth1 is the interface at @wan
- eth0 is assigned the MAC from 0x0 (*:A0)
- eth1 is assigned the MAC from 0x1002 (*:A1)
- br-lan inherits the MAC from eth0 (*:A0)
- @wan inherits the MAC from eth1 (*:A1)
- radio0's MAC is overwritten to the one at 0x6
This way, eth0/eth1's positions differ from the stock firmware, but
the weird MAC ressignations in br-lan/br-wan are avoided while the
external behaviour of the router is maintained. Additionally, WAN
port is connected to the PHY gmac, allowing to monitor the link
status (e.g., to restart DHCP negotiation when plugging a cable).
Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
2019-03-18 12:20:47 +00:00
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-e313ac
|
|
|
|
|
|
2019-03-30 13:27:17 +00:00
|
|
|
define Device/comfast_cf-e314n-v2
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9531
|
2019-03-30 13:27:17 +00:00
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-E314N
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
DEVICE_PACKAGES := rssileds
|
2019-08-09 11:53:49 +00:00
|
|
|
IMAGE_SIZE := 7936k
|
2019-03-30 13:27:17 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-e314n-v2
|
|
|
|
|
|
2019-03-21 11:50:01 +00:00
|
|
|
define Device/comfast_cf-e5
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9531
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-E5/E7
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := rssileds kmod-leds-gpio kmod-usb2 kmod-usb-net \
|
2019-03-21 11:50:01 +00:00
|
|
|
kmod-usb-net-qmi-wwan -swconfig -uboot-envtools
|
|
|
|
|
IMAGE_SIZE := 16192k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-e5
|
|
|
|
|
|
ath79: add support for COMFAST CF-E560AC
This commit adds support for the COMFAST CF-E560AC, an ap143 based
in-wall access point.
Specifications:
- SoC: Qualcomm Atheros QCA9531
- RAM: 128 MB DDR2 (Winbond W971GG6SB-25)
- Storage: 16 MB NOR (Winbond 25Q128JVSO)
- WAN: 1x 10/100 PoE ethernet (48v)
- LAN: 4x 10/100 ethernet
- WLAN1: QCA9531 - 802.11b/g/n - 2x SKY85303-21 FEM
- WLAN2: QCA9886 - 802.11ac/n/a - 2x SKY85735-11 FEM
- USB: one external USB2.0 port
- UART: 3.3v, 2.54mm headers already populated on board
- LED: 7x external
- Button: 1x external
- Boot: U-Boot 1.1.4 (pepe2k/u-boot_mod)
MAC addressing:
- stock
LAN *:40 (label)
WAN *:41
5G *:42
2.4G *:4a
- flash (art partition)
0x0 *:40 (label)
0x6 *:42
0x1002 *:41
0x5006 *:43
This device contains valid MAC addresses in art 0x0, 0x6, 0x1002 and
0x5006, however the vendor firmware only reads from art:0x0 for the LAN
interface and then increments in 02_network. They also jump 8 addresses
for the second wifi interface (2.4 GHz). This behavior has been duplicated
in the DTS and ath10k hotplug to align addresses with the vendor firmware
v2.6.0.
Recovery instructions:
This device contains built-in u-boot tftp recovery.
1. Configure PC with static IP 192.168.1.10/24 and tftp server.
2. Place desired image at /firmware_auto.bin at tftp root.
3. Connect device to PC, and power on.
4. Device will fetch flash from tftp, flash and reboot into new image.
Signed-off-by: August Huber <auh@google.com>
[move jtag_disable_pins, remove unnecessary statuses in DTS, remove
duplicate entry in 11-ath10k-caldata, remove hub_port0 label in DTS]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-01-26 16:55:11 +00:00
|
|
|
define Device/comfast_cf-e560ac
|
|
|
|
|
SOC := qca9531
|
|
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-E560AC
|
|
|
|
|
DEVICE_PACKAGES := kmod-leds-gpio kmod-usb2 kmod-ath10k-ct \
|
|
|
|
|
ath10k-firmware-qca9888-ct
|
|
|
|
|
IMAGE_SIZE := 16128k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-e560ac
|
|
|
|
|
|
ath79: add support for Comfast CF-EW72
Specifications:
Qualcomm/Atheros QCA9531 + QCA9886
2x 10/100 Mbps Ethernet, with 48v PoE
2T2R 2.4 GHz, 802.11b/g/n
2T2R 5 GHz, 802.11a/n/ac
128MB RAM
16MB SPI Flash
4x LED (Always On Power, LAN, WAN, WLAN)
Flashing Instructions:
Original firmware is based on OpenWRT, so flashing the sysupgrade image on
the factory firmware is sufficient.
Tested: Reset button, WAN LED, LAN LED, Power LED (always on, not much
to test), WLAN LED (one LED only for 2 interfaces, by default it gets
assigned to the first interface), MAC addresses (match factory firmware).
My LAN factory MAC address ends in F2.
use stock_mac art_loc
lan :f2 0x0
wan :f3 0x1002
5g :f4 0x6
2g :f5 0x5006
Since MAC address flash locations do not really match their use in vendor
firmware (e.g. address from 5 GHz calibration data is assigned to 2.4 GHz
WiFi), just calculate the MAC addresses with an offset based on 0x0 address.
Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
[add MAC address comment]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-03-11 21:00:42 +00:00
|
|
|
define Device/comfast_cf-ew72
|
|
|
|
|
SOC := qca9531
|
|
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-EW72
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca9888-ct \
|
|
|
|
|
-uboot-envtools -swconfig
|
|
|
|
|
IMAGE_SIZE := 16192k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-ew72
|
|
|
|
|
|
2019-03-31 04:26:22 +00:00
|
|
|
define Device/comfast_cf-wr650ac-v1
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-03-31 04:26:22 +00:00
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-WR650AC
|
|
|
|
|
DEVICE_VARIANT := v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
2019-08-09 15:40:42 +00:00
|
|
|
IMAGE_SIZE := 16128k
|
2019-03-31 04:26:22 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-wr650ac-v1
|
|
|
|
|
|
|
|
|
|
define Device/comfast_cf-wr650ac-v2
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-03-31 04:26:22 +00:00
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-WR650AC
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
2019-08-09 15:40:42 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
2019-03-31 04:26:22 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-wr650ac-v2
|
|
|
|
|
|
ath79: add support for Comfast CF-WR752AC v1
Specifications:
- Qualcomm QCA9531 + QCA9886
- dual band, antenna 2*3dBi
- Output power 50mW (17dBm)
- 1x 10/100 Mbps LAN RJ45
- 128 MB RAM / 16 MB FLASH (w25q128)
- 3 LEDs (red/green/blue)
incorporated in
"color wheel reset switch"
- UART 115200 8N1
Flashing instructions:
The U-boot bootloader contains a recovery HTTP server
to upload the firmware. Push the reset button while powering the
device on and keep it pressed for ~10 seconds. The device's LEDs will
blink several times and the recovery page will be at
http://192.168.1.1; use it to upload the sysupgrade image.
Alternatively, the original firmware is based on OpenWrt so a
sysupgrade image can be installed via the stock web GUI. Settings from
the original firmware will be saved and restored on the new one, so a
factory reset will be needed. To do so, once the new firmware is flashed,
enter into failsafe mode by pressing the reset button several times during
the boot process, until it starts flashing. Once in failsafe mode, perform
a factory reset as usual.
LED-Info:
The LEDs on the Comfast stock fw have a very proprietary behaviour,
corresponding to the user selected working mode (AP, ROUTER or REPEATER).
In the first two cases, only blue is used for status and LAN signaling. When
using the latter, blue is always off (except for sysupgrade), either red
signals bad rssi on master-link, or green good. Since the default working
mode of OpenWrt resembles that of a router/AP, the default behavior is
implemented accordingly.
MAC addresses (art partition):
location address (example) use in vendor firmware
0x0 xx:xx:xx:xx:xc:f8 -> eth0
0x6 xx:xx:xx:xx:xc:fa -> wlan5g (+2)
0x1002 xx:xx:xx:xx:xc:f9 -> not used
0x5006 xx:xx:xx:xx:xc:fb -> not used
--- xx:xx:xx:xx:xd:02 -> wlan2g (+10)
The same strange situation has already been observed and documented
for COMFAST CF-E560AC.
Signed-off-by: Roman Hampel <rhamp@arcor.de>
Co-developed-by: Joao Albuquerque <joaohccalbu@gmail.com>
Signed-off-by: Joao Albuquerque <joaohccalbu@gmail.com>
[adjust and extend commit message, rebase, minor DTS adjustments,
add correct MAC address for wmac, change RSSI LED names and behavior]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-03-20 16:32:30 +00:00
|
|
|
define Device/comfast_cf-wr752ac-v1
|
|
|
|
|
SOC := qca9531
|
|
|
|
|
DEVICE_VENDOR := COMFAST
|
|
|
|
|
DEVICE_MODEL := CF-WR752AC
|
|
|
|
|
DEVICE_VARIANT := v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca9888-ct \
|
|
|
|
|
-uboot-envtools
|
|
|
|
|
IMAGE_SIZE := 16192k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += comfast_cf-wr752ac-v1
|
|
|
|
|
|
2018-12-27 01:32:38 +00:00
|
|
|
define Device/devolo_dvl1200e
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := devolo
|
|
|
|
|
DEVICE_MODEL := WiFi pro 1200e
|
2018-12-27 01:32:38 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
IMAGE_SIZE := 15936k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += devolo_dvl1200e
|
|
|
|
|
|
2019-01-01 18:17:23 +00:00
|
|
|
define Device/devolo_dvl1200i
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := devolo
|
|
|
|
|
DEVICE_MODEL := WiFi pro 1200i
|
2019-01-01 18:17:23 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
IMAGE_SIZE := 15936k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += devolo_dvl1200i
|
|
|
|
|
|
2018-12-27 01:32:39 +00:00
|
|
|
define Device/devolo_dvl1750c
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := devolo
|
|
|
|
|
DEVICE_MODEL := WiFi pro 1750c
|
2018-12-27 01:32:39 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
IMAGE_SIZE := 15936k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += devolo_dvl1750c
|
|
|
|
|
|
2019-01-20 16:46:42 +00:00
|
|
|
define Device/devolo_dvl1750e
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := devolo
|
|
|
|
|
DEVICE_MODEL := WiFi pro 1750e
|
2019-01-20 16:46:42 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
IMAGE_SIZE := 15936k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += devolo_dvl1750e
|
|
|
|
|
|
2019-01-01 18:17:22 +00:00
|
|
|
define Device/devolo_dvl1750i
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := devolo
|
|
|
|
|
DEVICE_MODEL := WiFi pro 1750i
|
2019-01-01 18:17:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
IMAGE_SIZE := 15936k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += devolo_dvl1750i
|
|
|
|
|
|
2019-06-11 15:27:51 +00:00
|
|
|
define Device/devolo_dvl1750x
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-11 15:27:51 +00:00
|
|
|
DEVICE_VENDOR := devolo
|
|
|
|
|
DEVICE_MODEL := WiFi pro 1750x
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
IMAGE_SIZE := 15936k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += devolo_dvl1750x
|
|
|
|
|
|
ath79: add support for Devolo Magic 2 WIFI
This patch support Devolo Magic 2 WIFI, board devolo_dlan2-2400-ac.
This device is a plc wifi AC2400 router/extender with 2 Ethernet
ports, has a G.hn PLC and uses LCMP protocol from Home Grid Forum.
Hardware:
SoC: AR9344
CPU: 560 MHz
Flash: 16 MiB (W25Q128JVSIQ)
RAM: 128 MiB DDR2
Ethernet: 2xLAN 10/100/1000
PLC: 88LX5152 (MaxLinear G.hn)
PLC Flash: W25Q32JVSSIQ
PLC Uplink: 1Gbps MIMO
PLC Link: RGMII 1Gbps (WAN)
WiFi: Atheros AR9340 2.4GHz 802.11bgn
Atheros AR9882-BR4A 5GHz 802.11ac
Switch: QCA8337, Port0:CPU, Port2:PLC, Port3:LAN1, Port4:LAN2
Button: 3x Buttons (Reset, wifi and plc)
LED: 3x Leds (wifi, plc white, plc red)
GPIO Switch: 11-PLC Pairing (Active Low)
13-PLC Enable
21-WLAN power
MACs Details verified with the stock firmware:
Radio1: 2.4 GHz &wmac *:4c Art location: 0x1002
Radio0: 5.0 GHz &pcie *:4d Art location: 0x5006
Ethernet ðernet *:4e = 2.4 GHz + 2
PLC uplink --- *:4f = 2.4 GHz + 3
Label MAC address is from PLC uplink
OEM SSID: echo devolo-$(grep SerialNumber /dev/mtd1 | grep -o ...$)
OEM WiFi password: grep DlanSecurityID /dev/mtd1|tr -d -|cut -d'=' -f 2
Recommendations: Configure and link your PLC with OEM firmware
BEFORE you flash the device. PLC configuration/link should
remain in different memory and should work straight forward
after flashing.
Restrictions: PLC link detection to trigger plc red led is not
available. PLC G.hn chip is not compatible with open-plc-tools,
it uses LCMP protocol with AES-128 and requires different
software.
Notes: Pairing should be possible with gpio switch. Default
configuration will trigger wifi led with 2.4Ghz wifi traffic
and plc white led with wan traffic.
Flash instruction (TFTP):
1. Set PC to fixed ip address 192.168.0.100
2. Download the sysupgrade image and rename it to uploadfile
3. Start a tftp server with the image file in its root directory
4. Turn off the router
5. Press and hold Reset button
6. Turn on router with the reset button pressed and wait ~15 seconds
7. Release the reset button and after a short time
the firmware should be transferred from the tftp server
8. Allow 1-2 minutes for the first boot.
Signed-off-by: Manuel Giganto <mgigantoregistros@gmail.com>
2019-09-16 10:25:23 +00:00
|
|
|
define Device/devolo_magic-2-wifi
|
|
|
|
|
SOC := ar9344
|
|
|
|
|
DEVICE_VENDOR := Devolo
|
|
|
|
|
DEVICE_MODEL := Magic 2 WiFi
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
IMAGE_SIZE := 15872k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += devolo_magic-2-wifi
|
|
|
|
|
|
ath79: add support for D-Link DAP-2695-A1
Hardware:
* SoC: Qualcomm Atheros QCA9558
* RAM: 256MB
* Flash: 16MB SPI NOR
* Ethernet: 2x 10/100/1000 (1x 802.3at PoE-PD)
* WiFi 2.4GHz: Qualcomm Atheros QCA9558
* WiFi 5GHz: Qualcomm Ahteros QCA9880-2R4E
* LEDS: 1x 5GHz, 1x 2.4GHz, 1x LAN1(POE), 1x LAN2, 1x POWER
* Buttons: 1x RESET
* UART: 1x RJ45 RS-232 Console port
Installation via stock firmware:
* Install the factory image via the stock firmware web interface
Installation via bootloader Emergency Web Server:
* Connect your PC to the LAN1(PoE) port
* Configure your PC with IP address 192.168.0.90
* Open a serial console to the Console port (115200,8n1)
* Press "q" within 2s when "press 'q' to stop autoboot" appears
* Open http://192.168.0.50 in a browser
* Upload either the factory or the sysupgrade image
* Once you see "write image into flash...OK,dest addr=0x9f070000" you
can power-cycle the device. Ignore "checksum bad" messages.
Setting the MAC addresses for the ethernet interfaces via
/etc/board.d/02_network adds the following snippets to
/etc/config/network:
config device 'lan_eth0_1_dev'
option name 'eth0.1'
option macaddr 'xx:xx:xx:xx:xx:xx'
config device 'wan_eth1_2_dev'
option name 'eth1.2'
option macaddr 'xx:xx:xx:xx:xx:xx'
This would result in the proper MAC addresses being set for the VLAN
subinterfaces, but the parent interfaces would still have a random MAC
address. Using untagged VLANs could solve this, but would still leave
those extra snippets in /etc/config/network, and then the device VLAN
setup would differ from the one used in ar71xx. Therefore, the MAC
addresses of the ethernet interfaces are being set via preinit instead.
The bdcfg partition contains 4 MAC address labels:
- lanmac
- wanmac
- wlanmac
- wlanmac_a
The first 3 all contain the same MAC address, which is also the one on
the label.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
Reviewed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-06-07 23:11:34 +00:00
|
|
|
define Device/dlink_dap-2695-a1
|
|
|
|
|
SOC := qca9558
|
|
|
|
|
DEVICE_PACKAGES := ath10k-firmware-qca988x-ct kmod-ath10k-ct
|
|
|
|
|
DEVICE_VENDOR := D-Link
|
|
|
|
|
DEVICE_MODEL := DAP-2965
|
|
|
|
|
DEVICE_VARIANT := A1
|
|
|
|
|
IMAGES := factory.img sysupgrade.bin
|
|
|
|
|
IMAGE_SIZE := 15360k
|
|
|
|
|
IMAGE/default := append-kernel | pad-offset 65536 160
|
|
|
|
|
IMAGE/factory.img := $$(IMAGE/default) | append-rootfs | wrgg-pad-rootfs | \
|
|
|
|
|
mkwrggimg | check-size
|
|
|
|
|
IMAGE/sysupgrade.bin := $$(IMAGE/default) | mkwrggimg | append-rootfs | \
|
|
|
|
|
wrgg-pad-rootfs | append-metadata | check-size
|
|
|
|
|
KERNEL := kernel-bin | append-dtb | relocate-kernel | lzma
|
|
|
|
|
KERNEL_INITRAMFS := $$(KERNEL) | mkwrggimg
|
|
|
|
|
DAP_SIGNATURE := wapac02_dkbs_dap2695
|
|
|
|
|
SUPPORTED_DEVICES += dap-2695-a1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dap-2695-a1
|
|
|
|
|
|
2020-01-12 19:20:43 +00:00
|
|
|
define Device/dlink_dir-505
|
|
|
|
|
SOC := ar9330
|
|
|
|
|
DEVICE_VENDOR := D-Link
|
|
|
|
|
DEVICE_MODEL := DIR-505
|
|
|
|
|
IMAGE_SIZE := 7680k
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2
|
|
|
|
|
SUPPORTED_DEVICES += dir-505-a1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-505
|
|
|
|
|
|
2018-08-09 17:49:29 +00:00
|
|
|
define Device/dlink_dir-825-b1
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7161
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := D-Link
|
|
|
|
|
DEVICE_MODEL := DIR-825
|
|
|
|
|
DEVICE_VARIANT := B1
|
2018-08-09 17:49:29 +00:00
|
|
|
IMAGE_SIZE := 6208k
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-ohci kmod-usb2 kmod-usb-ledtrig-usbport \
|
|
|
|
|
kmod-leds-reset kmod-owl-loader
|
2018-08-09 17:49:29 +00:00
|
|
|
SUPPORTED_DEVICES += dir-825-b1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-825-b1
|
|
|
|
|
|
2018-12-01 18:41:34 +00:00
|
|
|
define Device/dlink_dir-825-c1
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := D-Link
|
|
|
|
|
DEVICE_MODEL := DIR-825
|
|
|
|
|
DEVICE_VARIANT := C1
|
2019-12-19 19:42:19 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport kmod-leds-reset \
|
|
|
|
|
kmod-owl-loader
|
2018-12-01 18:41:34 +00:00
|
|
|
SUPPORTED_DEVICES += dir-825-c1
|
|
|
|
|
IMAGE_SIZE := 15936k
|
|
|
|
|
IMAGES := factory.bin sysupgrade.bin
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | append-rootfs | \
|
|
|
|
|
pad-rootfs
|
2018-12-17 20:56:56 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | pad-offset $$$$(IMAGE_SIZE) 26 | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-string 00DB120AR9344-RT-101214-00 | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := $$(IMAGE/default) | append-metadata | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2018-12-01 18:41:34 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-825-c1
|
|
|
|
|
|
|
|
|
|
define Device/dlink_dir-835-a1
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := D-Link
|
|
|
|
|
DEVICE_MODEL := DIR-835
|
|
|
|
|
DEVICE_VARIANT := A1
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-leds-reset kmod-owl-loader
|
2018-12-01 18:41:34 +00:00
|
|
|
SUPPORTED_DEVICES += dir-835-a1
|
|
|
|
|
IMAGE_SIZE := 15936k
|
|
|
|
|
IMAGES := factory.bin sysupgrade.bin
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | append-rootfs | \
|
|
|
|
|
pad-rootfs
|
2018-12-17 20:56:56 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | pad-offset $$$$(IMAGE_SIZE) 26 | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-string 00DB120AR9344-RT-101214-00 | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := $$(IMAGE/default) | append-metadata | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2018-12-01 18:41:34 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-835-a1
|
|
|
|
|
|
2019-07-25 14:44:11 +00:00
|
|
|
define Device/dlink_dir-842-c
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
2019-07-20 07:37:12 +00:00
|
|
|
DEVICE_VENDOR := D-Link
|
|
|
|
|
DEVICE_MODEL := DIR-842
|
|
|
|
|
KERNEL := kernel-bin | append-dtb | relocate-kernel | lzma
|
|
|
|
|
KERNEL_INITRAMFS := $$(KERNEL) | seama
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
SEAMA_MTDBLOCK := 5
|
|
|
|
|
SEAMA_SIGNATURE := wrgac65_dlink.2015_dir842
|
|
|
|
|
# 64 bytes offset:
|
|
|
|
|
# - 28 bytes seama_header
|
|
|
|
|
# - 36 bytes of META data (4-bytes aligned)
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | uImage lzma | \
|
|
|
|
|
pad-offset $$$$(BLOCKSIZE) 64 | append-rootfs
|
|
|
|
|
IMAGE/sysupgrade.bin := $$(IMAGE/default) | seama | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | pad-rootfs -x 64 | seama | \
|
2020-03-10 13:58:27 +00:00
|
|
|
seama-seal | check-size
|
2019-07-20 07:37:12 +00:00
|
|
|
IMAGE_SIZE := 15680k
|
2019-07-25 14:44:11 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/dlink_dir-842-c1
|
2019-08-09 12:19:51 +00:00
|
|
|
$(Device/dlink_dir-842-c)
|
|
|
|
|
DEVICE_VARIANT := C1
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca9888-ct
|
2019-07-25 14:44:11 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-842-c1
|
|
|
|
|
|
|
|
|
|
define Device/dlink_dir-842-c2
|
2019-08-09 12:19:51 +00:00
|
|
|
$(Device/dlink_dir-842-c)
|
|
|
|
|
DEVICE_VARIANT := C2
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca9888-ct
|
2019-07-20 07:37:12 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-842-c2
|
|
|
|
|
|
2019-08-07 17:25:13 +00:00
|
|
|
define Device/dlink_dir-842-c3
|
2019-08-09 12:19:51 +00:00
|
|
|
$(Device/dlink_dir-842-c)
|
|
|
|
|
DEVICE_VARIANT := C3
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca9888-ct
|
2019-08-07 17:25:13 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-842-c3
|
|
|
|
|
|
2019-08-22 12:34:45 +00:00
|
|
|
define Device/dlink_dir-859-a1
|
|
|
|
|
$(Device/seama)
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
2019-08-22 12:34:45 +00:00
|
|
|
DEVICE_VENDOR := D-Link
|
|
|
|
|
DEVICE_MODEL := DIR-859
|
|
|
|
|
DEVICE_VARIANT := A1
|
|
|
|
|
IMAGE_SIZE := 15872k
|
2019-12-22 20:05:13 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct-smallbuffers ath10k-firmware-qca988x-ct
|
2019-08-22 12:34:45 +00:00
|
|
|
SEAMA_SIGNATURE := wrgac37_dlink.2013gui_dir859
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-859-a1
|
|
|
|
|
|
2018-12-29 15:55:35 +00:00
|
|
|
define Device/elecom_wrc-1750ghbk2-i
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := ELECOM
|
|
|
|
|
DEVICE_MODEL := WRC-1750GHBK2-I/C
|
2018-12-29 15:55:35 +00:00
|
|
|
IMAGE_SIZE := 15808k
|
|
|
|
|
KERNEL_INITRAMFS := $$(KERNEL) | pad-to 2 | \
|
2018-12-31 15:41:07 +00:00
|
|
|
add-elecom-factory-initramfs RN68 WRC-1750GHBK2
|
2018-12-29 15:55:35 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += elecom_wrc-1750ghbk2-i
|
|
|
|
|
|
2018-09-10 07:30:28 +00:00
|
|
|
define Device/elecom_wrc-300ghbk2-i
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := ELECOM
|
|
|
|
|
DEVICE_MODEL := WRC-300GHBK2-I
|
2018-09-10 07:30:28 +00:00
|
|
|
IMAGE_SIZE := 7616k
|
|
|
|
|
KERNEL_INITRAMFS := $$(KERNEL) | pad-to 2 | \
|
2018-12-31 15:41:07 +00:00
|
|
|
add-elecom-factory-initramfs RN51 WRC-300GHBK2-I
|
2018-09-10 07:30:28 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += elecom_wrc-300ghbk2-i
|
|
|
|
|
|
2018-05-08 05:22:38 +00:00
|
|
|
define Device/embeddedwireless_dorin
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9331
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Embedded Wireless
|
|
|
|
|
DEVICE_MODEL := Dorin
|
2018-05-06 08:20:11 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-chipidea2
|
2018-05-07 19:09:44 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
2018-05-06 08:20:11 +00:00
|
|
|
endef
|
2018-05-08 05:22:38 +00:00
|
|
|
TARGET_DEVICES += embeddedwireless_dorin
|
2018-05-06 08:20:11 +00:00
|
|
|
|
2019-03-26 21:35:05 +00:00
|
|
|
define Device/engenius_ecb1750
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := EnGenius
|
|
|
|
|
DEVICE_MODEL := ECB1750
|
2019-03-26 21:35:05 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
IMAGE_SIZE := 15680k
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-rootfs | pad-rootfs | check-size | \
|
2019-12-19 19:42:19 +00:00
|
|
|
senao-header -r 0x101 -p 0x6d -t 2
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2019-03-26 21:35:05 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += engenius_ecb1750
|
|
|
|
|
|
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>
2019-03-04 14:18:53 +00:00
|
|
|
define Device/engenius_epg5000
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := EnGenius
|
|
|
|
|
DEVICE_MODEL := 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>
2019-03-04 14:18:53 +00:00
|
|
|
DEVICE_PACKAGES := ath10k-firmware-qca988x-ct kmod-ath10k-ct kmod-usb2
|
|
|
|
|
IMAGE_SIZE := 14656k
|
|
|
|
|
IMAGES += factory.dlf
|
|
|
|
|
IMAGE/factory.dlf := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-rootfs | pad-rootfs | check-size | \
|
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>
2019-03-04 14:18:53 +00:00
|
|
|
senao-header -r 0x101 -p 0x71 -t 2
|
|
|
|
|
SUPPORTED_DEVICES += epg5000
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += engenius_epg5000
|
|
|
|
|
|
2018-12-18 08:35:30 +00:00
|
|
|
define Device/engenius_ews511ap
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9531
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := EnGenius
|
|
|
|
|
DEVICE_MODEL := EWS511AP
|
2018-12-18 08:35:30 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca9887-ct
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += engenius_ews511ap
|
|
|
|
|
|
2020-05-19 20:49:35 +00:00
|
|
|
define Device/enterasys_ws-ap3705i
|
|
|
|
|
SOC := ar9344
|
|
|
|
|
DEVICE_VENDOR := Enterasys
|
|
|
|
|
DEVICE_MODEL := WS-AP3705i
|
|
|
|
|
IMAGE_SIZE := 30528k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += enterasys_ws-ap3705i
|
|
|
|
|
|
2018-08-02 07:14:10 +00:00
|
|
|
define Device/etactica_eg200
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9331
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := eTactica
|
|
|
|
|
DEVICE_MODEL := EG200
|
2018-05-07 16:08:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-chipidea2 kmod-ledtrig-oneshot \
|
2019-12-19 19:42:19 +00:00
|
|
|
kmod-usb-serial kmod-usb-serial-ftdi kmod-usb-storage kmod-fs-ext4
|
2019-07-04 11:54:18 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
2018-08-02 07:14:10 +00:00
|
|
|
SUPPORTED_DEVICES += rme-eg200
|
2018-05-07 16:08:00 +00:00
|
|
|
endef
|
2018-08-02 07:14:10 +00:00
|
|
|
TARGET_DEVICES += etactica_eg200
|
2018-05-07 16:08:00 +00:00
|
|
|
|
2019-12-08 19:18:58 +00:00
|
|
|
define Device/glinet_6408
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
SOC := ar9331
|
|
|
|
|
DEVICE_VENDOR := GL.iNet
|
|
|
|
|
DEVICE_MODEL := 6408
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2
|
|
|
|
|
IMAGE_SIZE := 8000k
|
|
|
|
|
TPLINK_HWID := 0x08000001
|
|
|
|
|
IMAGES := sysupgrade.bin
|
|
|
|
|
SUPPORTED_DEVICES += gl-inet
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += glinet_6408
|
|
|
|
|
|
|
|
|
|
define Device/glinet_6416
|
|
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
SOC := ar9331
|
|
|
|
|
DEVICE_VENDOR := GL.iNet
|
|
|
|
|
DEVICE_MODEL := 6416
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2
|
|
|
|
|
IMAGE_SIZE := 16192k
|
|
|
|
|
TPLINK_HWID := 0x08000001
|
|
|
|
|
IMAGES := sysupgrade.bin
|
|
|
|
|
SUPPORTED_DEVICES += gl-inet
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += glinet_6416
|
|
|
|
|
|
2018-12-30 20:37:50 +00:00
|
|
|
define Device/glinet_gl-ar150
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9330
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := GL.iNet
|
|
|
|
|
DEVICE_MODEL := GL-AR150
|
2018-05-06 08:20:11 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-chipidea2
|
|
|
|
|
IMAGE_SIZE := 16000k
|
2018-05-07 20:41:04 +00:00
|
|
|
SUPPORTED_DEVICES += gl-ar150
|
2018-05-06 08:20:11 +00:00
|
|
|
endef
|
2018-12-30 20:37:50 +00:00
|
|
|
TARGET_DEVICES += glinet_gl-ar150
|
2018-05-06 08:20:11 +00:00
|
|
|
|
2019-03-07 04:44:33 +00:00
|
|
|
define Device/glinet_gl-ar300m-common-nor
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9531
|
2019-10-23 16:56:47 +00:00
|
|
|
DEVICE_VENDOR := GL.iNet
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2
|
2018-05-27 05:37:22 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
SUPPORTED_DEVICES += gl-ar300m
|
|
|
|
|
endef
|
2019-03-07 04:44:33 +00:00
|
|
|
|
|
|
|
|
define Device/glinet_gl-ar300m-lite
|
|
|
|
|
$(Device/glinet_gl-ar300m-common-nor)
|
2019-10-23 16:56:47 +00:00
|
|
|
DEVICE_MODEL := GL-AR300M
|
|
|
|
|
DEVICE_VARIANT := Lite
|
2019-03-07 04:44:33 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += glinet_gl-ar300m-lite
|
|
|
|
|
|
2019-06-02 13:43:00 +00:00
|
|
|
define Device/glinet_gl-ar300m16
|
|
|
|
|
$(Device/glinet_gl-ar300m-common-nor)
|
|
|
|
|
DEVICE_MODEL := GL-AR300M16
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += glinet_gl-ar300m16
|
|
|
|
|
|
2019-08-23 09:05:57 +00:00
|
|
|
define Device/glinet_gl-ar750
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9531
|
2019-08-23 09:05:57 +00:00
|
|
|
DEVICE_VENDOR := GL.iNet
|
|
|
|
|
DEVICE_MODEL := GL-AR750
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca9887-ct
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
SUPPORTED_DEVICES += gl-ar750
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += glinet_gl-ar750
|
|
|
|
|
|
2018-11-26 14:39:25 +00:00
|
|
|
define Device/glinet_gl-x750
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9531
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := GL.iNet
|
|
|
|
|
DEVICE_MODEL := GL-X750
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca9887-ct
|
2018-11-05 02:03:05 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
endef
|
2018-11-26 14:39:25 +00:00
|
|
|
TARGET_DEVICES += glinet_gl-x750
|
2018-11-05 02:03:05 +00:00
|
|
|
|
2018-08-20 07:32:42 +00:00
|
|
|
define Device/iodata_etg3-r
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9342
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := I-O DATA
|
|
|
|
|
DEVICE_MODEL := ETG3-R
|
2018-08-20 07:32:42 +00:00
|
|
|
IMAGE_SIZE := 7680k
|
2019-04-13 03:21:02 +00:00
|
|
|
DEVICE_PACKAGES := -iwinfo -kmod-ath9k -wpad-basic
|
2018-08-20 07:32:42 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_etg3-r
|
|
|
|
|
|
2018-08-16 08:08:28 +00:00
|
|
|
define Device/iodata_wn-ac1167dgr
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9557
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := I-O DATA
|
|
|
|
|
DEVICE_MODEL := WN-AC1167DGR
|
2018-08-16 08:08:28 +00:00
|
|
|
IMAGE_SIZE := 14656k
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-rootfs | pad-rootfs | check-size | \
|
2019-12-19 19:42:19 +00:00
|
|
|
senao-header -r 0x30a -p 0x61 -t 2
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
2018-08-16 08:08:28 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-ac1167dgr
|
|
|
|
|
|
2019-02-05 08:23:58 +00:00
|
|
|
define Device/iodata_wn-ac1600dgr
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9557
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := I-O DATA
|
|
|
|
|
DEVICE_MODEL := WN-AC1600DGR
|
2019-02-05 08:23:58 +00:00
|
|
|
IMAGE_SIZE := 14656k
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-rootfs | pad-rootfs | check-size | \
|
2019-12-19 19:42:19 +00:00
|
|
|
senao-header -r 0x30a -p 0x60 -t 2 -v 200
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
2019-02-05 08:23:58 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-ac1600dgr
|
|
|
|
|
|
2018-08-10 00:07:53 +00:00
|
|
|
define Device/iodata_wn-ac1600dgr2
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9557
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := I-O DATA
|
2019-06-16 16:23:32 +00:00
|
|
|
DEVICE_MODEL := WN-AC1600DGR2/DGR3
|
2018-08-10 00:07:53 +00:00
|
|
|
IMAGE_SIZE := 14656k
|
2019-06-16 16:23:32 +00:00
|
|
|
IMAGES += dgr2-dgr3-factory.bin
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/dgr2-dgr3-factory.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-rootfs | pad-rootfs | check-size | \
|
2019-12-19 19:42:19 +00:00
|
|
|
senao-header -r 0x30a -p 0x60 -t 2 -v 200
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
2018-08-10 00:07:53 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-ac1600dgr2
|
|
|
|
|
|
2018-11-30 10:04:23 +00:00
|
|
|
define Device/iodata_wn-ag300dgr
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar1022
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := I-O DATA
|
|
|
|
|
DEVICE_MODEL := WN-AG300DGR
|
2018-11-30 10:04:23 +00:00
|
|
|
IMAGE_SIZE := 15424k
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-rootfs | pad-rootfs | check-size | \
|
2019-12-19 19:42:19 +00:00
|
|
|
senao-header -r 0x30a -p 0x47 -t 2
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2
|
2018-11-30 10:04:23 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-ag300dgr
|
|
|
|
|
|
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>
2019-03-06 19:15:19 +00:00
|
|
|
define Device/jjplus_ja76pf2
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7161
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := jjPlus
|
|
|
|
|
DEVICE_MODEL := JA76PF2
|
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>
2019-03-06 19:15:19 +00:00
|
|
|
DEVICE_PACKAGES += -kmod-ath9k -swconfig -wpad-mini -uboot-envtools fconfig
|
2019-08-23 13:50:52 +00:00
|
|
|
IMAGES := kernel.bin rootfs.bin
|
|
|
|
|
IMAGE/kernel.bin := append-kernel
|
|
|
|
|
IMAGE/rootfs.bin := append-rootfs | pad-rootfs
|
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>
2019-03-06 19:15:19 +00:00
|
|
|
KERNEL := kernel-bin | append-dtb | lzma | pad-to $$(BLOCKSIZE)
|
|
|
|
|
KERNEL_INITRAMFS := kernel-bin | append-dtb
|
|
|
|
|
IMAGE_SIZE := 16000k
|
2019-08-23 13:50:50 +00:00
|
|
|
SUPPORTED_DEVICES += ja76pf2
|
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>
2019-03-06 19:15:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += jjplus_ja76pf2
|
|
|
|
|
|
2019-03-09 01:10:25 +00:00
|
|
|
define Device/librerouter_librerouter-v1
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Librerouter
|
|
|
|
|
DEVICE_MODEL := LibreRouter
|
|
|
|
|
DEVICE_VARIANT := v1
|
2019-03-09 01:10:25 +00:00
|
|
|
IMAGE_SIZE := 7936k
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2
|
2019-03-09 01:10:25 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += librerouter_librerouter-v1
|
|
|
|
|
|
2019-03-16 04:27:32 +00:00
|
|
|
define Device/nec_wg1200cr
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := NEC
|
|
|
|
|
DEVICE_MODEL := Aterm WG1200CR
|
2019-03-16 04:27:32 +00:00
|
|
|
IMAGE_SIZE := 7616k
|
|
|
|
|
SEAMA_MTDBLOCK := 6
|
|
|
|
|
SEAMA_SIGNATURE := wrgac72_necpf.2016gui_wg1200cr
|
|
|
|
|
IMAGES += factory.bin
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-offset $$$$(BLOCKSIZE) 64 | append-rootfs
|
|
|
|
|
IMAGE/sysupgrade.bin := $$(IMAGE/default) | seama | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | pad-rootfs -x 64 | seama | \
|
2020-03-10 13:58:27 +00:00
|
|
|
seama-seal | nec-enc 9gsiy9nzep452pad | check-size
|
2019-03-16 04:27:32 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca9888-ct
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += nec_wg1200cr
|
|
|
|
|
|
2018-12-08 06:18:17 +00:00
|
|
|
define Device/nec_wg800hp
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := NEC
|
|
|
|
|
DEVICE_MODEL := Aterm WG800HP
|
2018-12-08 06:18:17 +00:00
|
|
|
IMAGE_SIZE := 7104k
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-rootfs | pad-rootfs | check-size | \
|
2019-12-19 19:42:19 +00:00
|
|
|
xor-image -p 6A57190601121E4C004C1E1201061957 -x | nec-fw LASER_ATERM
|
2020-04-26 19:30:16 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct-smallbuffers ath10k-firmware-qca9887-ct-full-htt
|
2018-12-08 06:18:17 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += nec_wg800hp
|
|
|
|
|
|
2019-08-22 12:34:45 +00:00
|
|
|
define Device/netgear_ex6400_ex7300
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-08-22 12:34:45 +00:00
|
|
|
NETGEAR_KERNEL_MAGIC := 0x27051956
|
|
|
|
|
NETGEAR_BOARD_ID := EX7300series
|
|
|
|
|
NETGEAR_HW_ID := 29765104+16+0+128
|
|
|
|
|
IMAGE_SIZE := 15552k
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-offset $$$$(BLOCKSIZE) 64 | \
|
|
|
|
|
netgear-rootfs | pad-rootfs
|
2019-08-22 12:34:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca99x0-ct
|
|
|
|
|
$(Device/netgear_ath79)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/netgear_ex6400
|
|
|
|
|
$(Device/netgear_ex6400_ex7300)
|
|
|
|
|
DEVICE_MODEL := EX6400
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_ex6400
|
|
|
|
|
|
|
|
|
|
define Device/netgear_ex7300
|
|
|
|
|
$(Device/netgear_ex6400_ex7300)
|
|
|
|
|
DEVICE_MODEL := EX7300
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_ex7300
|
|
|
|
|
|
|
|
|
|
define Device/netgear_wndr3x00
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7161
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | netgear-squashfs | \
|
|
|
|
|
append-rootfs | pad-rootfs
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-ohci kmod-usb2 kmod-usb-ledtrig-usbport \
|
|
|
|
|
kmod-leds-reset kmod-owl-loader
|
2019-08-22 12:34:45 +00:00
|
|
|
$(Device/netgear_ath79)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/netgear_wndr3700
|
|
|
|
|
$(Device/netgear_wndr3x00)
|
|
|
|
|
DEVICE_MODEL := WNDR3700
|
|
|
|
|
DEVICE_VARIANT := v1
|
|
|
|
|
NETGEAR_KERNEL_MAGIC := 0x33373030
|
|
|
|
|
NETGEAR_BOARD_ID := WNDR3700
|
|
|
|
|
IMAGE_SIZE := 7680k
|
|
|
|
|
IMAGES += factory-NA.img
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/factory-NA.img := $$(IMAGE/default) | netgear-dni NA | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2019-08-22 12:34:45 +00:00
|
|
|
SUPPORTED_DEVICES += wndr3700
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_wndr3700
|
|
|
|
|
|
2020-01-20 20:19:29 +00:00
|
|
|
define Device/netgear_wndr3700-v2
|
2019-08-22 12:34:45 +00:00
|
|
|
$(Device/netgear_wndr3x00)
|
|
|
|
|
DEVICE_MODEL := WNDR3700
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
NETGEAR_KERNEL_MAGIC := 0x33373031
|
|
|
|
|
NETGEAR_BOARD_ID := WNDR3700v2
|
|
|
|
|
NETGEAR_HW_ID := 29763654+16+64
|
|
|
|
|
IMAGE_SIZE := 15872k
|
2020-01-20 20:19:29 +00:00
|
|
|
SUPPORTED_DEVICES += wndr3700 netgear,wndr3700v2
|
2019-08-22 12:34:45 +00:00
|
|
|
endef
|
2020-01-20 20:19:29 +00:00
|
|
|
TARGET_DEVICES += netgear_wndr3700-v2
|
2019-08-22 12:34:45 +00:00
|
|
|
|
|
|
|
|
define Device/netgear_wndr3800
|
|
|
|
|
$(Device/netgear_wndr3x00)
|
|
|
|
|
DEVICE_MODEL := WNDR3800
|
|
|
|
|
NETGEAR_KERNEL_MAGIC := 0x33373031
|
|
|
|
|
NETGEAR_BOARD_ID := WNDR3800
|
|
|
|
|
NETGEAR_HW_ID := 29763654+16+128
|
|
|
|
|
IMAGE_SIZE := 15872k
|
2019-11-14 16:26:44 +00:00
|
|
|
SUPPORTED_DEVICES += wndr3700
|
2019-08-22 12:34:45 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_wndr3800
|
|
|
|
|
|
2019-08-07 20:07:33 +00:00
|
|
|
define Device/netgear_wndr3800ch
|
|
|
|
|
$(Device/netgear_wndr3x00)
|
|
|
|
|
DEVICE_MODEL := WNDR3800CH
|
|
|
|
|
NETGEAR_KERNEL_MAGIC := 0x33373031
|
|
|
|
|
NETGEAR_BOARD_ID := WNDR3800CH
|
|
|
|
|
NETGEAR_HW_ID := 29763654+16+128
|
|
|
|
|
IMAGE_SIZE := 15872k
|
2019-11-14 16:26:44 +00:00
|
|
|
SUPPORTED_DEVICES += wndr3700
|
2019-08-07 20:07:33 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_wndr3800ch
|
|
|
|
|
|
2020-05-10 22:10:20 +00:00
|
|
|
define Device/netgear_wndrmac-v1
|
|
|
|
|
$(Device/netgear_wndr3x00)
|
|
|
|
|
DEVICE_MODEL := WNDRMAC
|
|
|
|
|
DEVICE_VARIANT := v1
|
|
|
|
|
NETGEAR_KERNEL_MAGIC := 0x33373031
|
|
|
|
|
NETGEAR_BOARD_ID := WNDRMAC
|
|
|
|
|
NETGEAR_HW_ID := 29763654+16+64
|
|
|
|
|
IMAGE_SIZE := 15872k
|
|
|
|
|
SUPPORTED_DEVICES += wndr3700
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_wndrmac-v1
|
|
|
|
|
|
2020-05-10 23:05:20 +00:00
|
|
|
define Device/netgear_wndrmac-v2
|
|
|
|
|
$(Device/netgear_wndr3x00)
|
|
|
|
|
DEVICE_MODEL := WNDRMAC
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
NETGEAR_KERNEL_MAGIC := 0x33373031
|
|
|
|
|
NETGEAR_BOARD_ID := WNDRMACv2
|
|
|
|
|
NETGEAR_HW_ID := 29763654+16+128
|
|
|
|
|
IMAGE_SIZE := 15872k
|
|
|
|
|
SUPPORTED_DEVICES += wndr3700
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_wndrmac-v2
|
|
|
|
|
|
2019-10-30 09:07:27 +00:00
|
|
|
define Device/netgear_wnr2200_common
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar7241
|
2019-10-30 09:07:27 +00:00
|
|
|
DEVICE_MODEL := WNR2200
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport
|
|
|
|
|
NETGEAR_KERNEL_MAGIC := 0x32323030
|
|
|
|
|
NETGEAR_BOARD_ID := wnr2200
|
|
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | netgear-squashfs | \
|
|
|
|
|
append-rootfs | pad-rootfs
|
|
|
|
|
$(Device/netgear_ath79)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/netgear_wnr2200-8m
|
|
|
|
|
$(Device/netgear_wnr2200_common)
|
|
|
|
|
DEVICE_VARIANT := 8M
|
|
|
|
|
NETGEAR_HW_ID := 29763600+08+64
|
|
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
IMAGES += factory-NA.img
|
|
|
|
|
IMAGE/factory-NA.img := $$(IMAGE/default) | netgear-dni NA | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2019-10-30 09:07:27 +00:00
|
|
|
SUPPORTED_DEVICES += wnr2200
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_wnr2200-8m
|
|
|
|
|
|
|
|
|
|
define Device/netgear_wnr2200-16m
|
|
|
|
|
$(Device/netgear_wnr2200_common)
|
|
|
|
|
DEVICE_VARIANT := 16M
|
|
|
|
|
DEVICE_ALT0_VENDOR := NETGEAR
|
|
|
|
|
DEVICE_ALT0_MODEL := WNR2200
|
|
|
|
|
DEVICE_ALT0_VARIANT := CN/RU
|
|
|
|
|
NETGEAR_HW_ID :=
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_wnr2200-16m
|
|
|
|
|
|
2018-08-08 20:13:44 +00:00
|
|
|
define Device/ocedo_koala
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Ocedo
|
|
|
|
|
DEVICE_MODEL := Koala
|
2018-09-05 12:51:44 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
2018-08-08 20:13:44 +00:00
|
|
|
SUPPORTED_DEVICES += koala
|
|
|
|
|
IMAGE_SIZE := 7424k
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2018-08-08 20:13:44 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ocedo_koala
|
|
|
|
|
|
2018-07-06 16:23:31 +00:00
|
|
|
define Device/ocedo_raccoon
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Ocedo
|
|
|
|
|
DEVICE_MODEL := Raccoon
|
2018-07-06 16:23:31 +00:00
|
|
|
IMAGE_SIZE := 7424k
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2018-07-06 16:23:31 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ocedo_raccoon
|
|
|
|
|
|
2019-03-21 15:43:27 +00:00
|
|
|
define Device/ocedo_ursus
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Ocedo
|
|
|
|
|
DEVICE_MODEL := Ursus
|
2019-03-21 15:43:27 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
|
|
|
|
IMAGE_SIZE := 7424k
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2019-03-21 15:43:27 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ocedo_ursus
|
|
|
|
|
|
2018-05-08 05:22:38 +00:00
|
|
|
define Device/openmesh_om5p-ac-v2
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := OpenMesh
|
|
|
|
|
DEVICE_MODEL := OM5P-AC
|
|
|
|
|
DEVICE_VARIANT := v2
|
2018-09-05 12:51:44 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct om-watchdog
|
2018-05-07 19:09:44 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
2018-05-07 20:41:04 +00:00
|
|
|
SUPPORTED_DEVICES += om5p-acv2
|
2018-05-06 08:20:11 +00:00
|
|
|
endef
|
2018-05-08 05:22:38 +00:00
|
|
|
TARGET_DEVICES += openmesh_om5p-ac-v2
|
2018-05-06 08:20:11 +00:00
|
|
|
|
2018-07-28 12:52:39 +00:00
|
|
|
define Device/pcs_cap324
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := PowerCloud Systems
|
|
|
|
|
DEVICE_MODEL := CAP324
|
2018-07-28 12:52:39 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
SUPPORTED_DEVICES += cap324
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += pcs_cap324
|
|
|
|
|
|
2018-07-28 12:57:22 +00:00
|
|
|
define Device/pcs_cr3000
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9341
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := PowerCloud Systems
|
|
|
|
|
DEVICE_MODEL := CR3000
|
2018-07-28 12:57:22 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
SUPPORTED_DEVICES += cr3000
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += pcs_cr3000
|
|
|
|
|
|
2018-07-20 20:52:46 +00:00
|
|
|
define Device/pcs_cr5000
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := PowerCloud Systems
|
|
|
|
|
DEVICE_MODEL := CR5000
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2
|
2018-07-20 20:52:46 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
SUPPORTED_DEVICES += cr5000
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += pcs_cr5000
|
|
|
|
|
|
2019-08-22 12:34:45 +00:00
|
|
|
define Device/phicomm_k2t
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
2019-08-22 12:34:45 +00:00
|
|
|
DEVICE_VENDOR := Phicomm
|
|
|
|
|
DEVICE_MODEL := K2T
|
|
|
|
|
IMAGE_SIZE := 15744k
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | pad-rootfs | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-metadata | check-size
|
2019-12-22 20:05:13 +00:00
|
|
|
DEVICE_PACKAGES := kmod-leds-reset kmod-ath10k-ct-smallbuffers ath10k-firmware-qca9888-ct
|
2018-08-11 22:18:53 +00:00
|
|
|
endef
|
2019-08-22 12:34:45 +00:00
|
|
|
TARGET_DEVICES += phicomm_k2t
|
2018-08-11 22:18:53 +00:00
|
|
|
|
2019-06-25 08:32:58 +00:00
|
|
|
define Device/pisen_ts-d084
|
|
|
|
|
$(Device/tplink-8mlzma)
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9331
|
2019-06-25 08:32:58 +00:00
|
|
|
DEVICE_VENDOR := PISEN
|
|
|
|
|
DEVICE_MODEL := TS-D084
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-chipidea2
|
2019-06-25 08:32:58 +00:00
|
|
|
TPLINK_HWID := 0x07030101
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += pisen_ts-d084
|
|
|
|
|
|
2019-08-04 14:13:45 +00:00
|
|
|
define Device/pisen_wmb001n
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9341
|
2019-08-04 14:13:45 +00:00
|
|
|
DEVICE_VENDOR := PISEN
|
|
|
|
|
DEVICE_MODEL := WMB001N
|
|
|
|
|
IMAGE_SIZE := 14080k
|
2020-03-05 14:42:18 +00:00
|
|
|
DEVICE_PACKAGES := kmod-i2c-gpio kmod-usb2
|
2019-08-04 14:13:45 +00:00
|
|
|
LOADER_TYPE := bin
|
|
|
|
|
LOADER_FLASH_OFFS := 0x20000
|
|
|
|
|
COMPILE := loader-$(1).bin loader-$(1).uImage
|
|
|
|
|
COMPILE/loader-$(1).bin := loader-okli-compile
|
2019-12-19 19:42:19 +00:00
|
|
|
COMPILE/loader-$(1).uImage := append-loader-okli $(1) | pad-to 64k | lzma | \
|
|
|
|
|
uImage lzma
|
2019-08-04 14:13:45 +00:00
|
|
|
KERNEL := kernel-bin | append-dtb | lzma | uImage lzma -M 0x4f4b4c49
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := $$(IMAGE/sysupgrade.bin) | pisen_wmb001n-factory $(1)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += pisen_wmb001n
|
|
|
|
|
|
2018-08-12 14:32:01 +00:00
|
|
|
define Device/pisen_wmm003n
|
|
|
|
|
$(Device/tplink-8mlzma)
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9331
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := PISEN
|
|
|
|
|
DEVICE_MODEL := Cloud Easy Power (WMM003N)
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-chipidea2
|
2018-08-12 14:32:01 +00:00
|
|
|
TPLINK_HWID := 0x07030101
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += pisen_wmm003n
|
|
|
|
|
|
2019-07-15 11:43:31 +00:00
|
|
|
define Device/qihoo_c301
|
|
|
|
|
$(Device/seama)
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-07-15 11:43:31 +00:00
|
|
|
DEVICE_VENDOR := Qihoo
|
|
|
|
|
DEVICE_MODEL := C301
|
2019-12-19 19:42:19 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca988x-ct \
|
|
|
|
|
uboot-envtools
|
2019-07-15 11:43:31 +00:00
|
|
|
IMAGE_SIZE := 15744k
|
|
|
|
|
SEAMA_SIGNATURE := wrgac26_qihoo360_360rg
|
|
|
|
|
SUPPORTED_DEVICES += qihoo-c301
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += qihoo_c301
|
|
|
|
|
|
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>
2018-10-07 04:04:54 +00:00
|
|
|
define Device/rosinson_wr818
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Rosinson
|
|
|
|
|
DEVICE_MODEL := WR818
|
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>
2018-10-07 04:04:54 +00:00
|
|
|
IMAGE_SIZE := 15872k
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport
|
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>
2018-10-07 04:04:54 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += rosinson_wr818
|
|
|
|
|
|
2020-02-08 11:58:25 +00:00
|
|
|
define Device/siemens_ws-ap3610
|
|
|
|
|
SOC := ar7161
|
|
|
|
|
DEVICE_VENDOR := Siemens
|
|
|
|
|
DEVICE_MODEL := WS-AP3610
|
|
|
|
|
IMAGE_SIZE := 14336k
|
2020-02-20 09:29:09 +00:00
|
|
|
BLOCKSIZE := 256k
|
2020-02-08 11:58:25 +00:00
|
|
|
LOADER_TYPE := bin
|
|
|
|
|
LOADER_FLASH_OFFS := 0x82000
|
|
|
|
|
COMPILE := loader-$(1).bin
|
|
|
|
|
COMPILE/loader-$(1).bin := loader-okli-compile
|
|
|
|
|
KERNEL := kernel-bin | append-dtb | lzma | uImage lzma -M 0x4f4b4c49 | loader-okli $(1) 8128 | uImage none
|
|
|
|
|
KERNEL_INITRAMFS := kernel-bin | append-dtb | uImage none
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += siemens_ws-ap3610
|
|
|
|
|
|
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>
2019-10-15 12:56:12 +00:00
|
|
|
define Device/sitecom_wlr-7100
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar1022
|
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>
2019-10-15 12:56:12 +00:00
|
|
|
DEVICE_VENDOR := Sitecom
|
|
|
|
|
DEVICE_MODEL := WLR-7100
|
|
|
|
|
DEVICE_VARIANT := v1 002
|
2020-01-14 16:40:04 +00:00
|
|
|
DEVICE_PACKAGES := ath10k-firmware-qca988x-ct kmod-ath10k-ct-smallbuffers kmod-usb2
|
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>
2019-10-15 12:56:12 +00:00
|
|
|
IMAGES += factory.dlf
|
|
|
|
|
IMAGE/factory.dlf := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-rootfs | pad-rootfs | check-size | \
|
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>
2019-10-15 12:56:12 +00:00
|
|
|
senao-header -r 0x222 -p 0x53 -t 2
|
|
|
|
|
IMAGE_SIZE := 7488k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += sitecom_wlr-7100
|
|
|
|
|
|
2019-11-04 17:05:38 +00:00
|
|
|
define Device/sitecom_wlr-8100
|
|
|
|
|
SOC := qca9558
|
|
|
|
|
DEVICE_VENDOR := Sitecom
|
|
|
|
|
DEVICE_MODEL := WLR-8100
|
|
|
|
|
DEVICE_ALT0_VENDOR := Sitecom
|
|
|
|
|
DEVICE_ALT0_MODEL := X8 AC1750
|
|
|
|
|
DEVICE_PACKAGES := ath10k-firmware-qca988x-ct kmod-ath10k-ct kmod-usb2 kmod-usb3
|
|
|
|
|
SUPPORTED_DEVICES += wlr8100
|
|
|
|
|
IMAGES += factory.dlf
|
|
|
|
|
IMAGE/factory.dlf := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-rootfs | pad-rootfs | check-size | \
|
2019-11-04 17:05:38 +00:00
|
|
|
senao-header -r 0x222 -p 0x56 -t 2
|
|
|
|
|
IMAGE_SIZE := 15424k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += sitecom_wlr-8100
|
|
|
|
|
|
2020-02-02 16:09:50 +00:00
|
|
|
define Device/teltonika_rut955
|
|
|
|
|
SOC := ar9344
|
|
|
|
|
DEVICE_VENDOR := Teltonika
|
|
|
|
|
DEVICE_MODEL := RUT955
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-acm kmod-usb-net-qmi-wwan \
|
|
|
|
|
kmod-usb-serial-option kmod-hwmon-mcp3021 uqmi -uboot-envtools
|
|
|
|
|
IMAGE_SIZE := 15552k
|
|
|
|
|
TPLINK_HWID := 0x35000001
|
|
|
|
|
TPLINK_HWREV := 0x1
|
|
|
|
|
TPLINK_HEADER_VERSION := 1
|
|
|
|
|
KERNEL := kernel-bin | append-dtb | lzma | tplink-v1-header
|
|
|
|
|
KERNEL_INITRAMFS := kernel-bin | append-dtb | lzma | uImage lzma
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | append-rootfs |\
|
|
|
|
|
pad-rootfs | teltonika-fw-fake-checksum | append-string master |\
|
2020-03-10 13:58:27 +00:00
|
|
|
append-md5sum-bin | check-size
|
2020-02-02 16:09:50 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to $$$$(BLOCKSIZE) |\
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata |\
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2020-02-02 16:09:50 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += teltonika_rut955
|
|
|
|
|
|
ath79: add support for Teltonika RUT955 H7V3C0
This board was previously supported in ar71xx as 'RUT9XX'. The
difference between that and the other RUT955 board already supported in
ath79 is that instead of the SPI shift registers driving the LEDs and
digital outputs that model got an I2C GPIO expander instead.
To support LEDs during early boot and interrupt-driven digital inputs,
I2C support as well as support for PCA953x has to be built-in and
cannot be kernel modules, hence select those symbols for ath79/generic.
Specification:
- 550/400/200 MHz (CPU/DDR/AHB)
- 128 MB of RAM (DDR2)
- 16 MB of FLASH (SPI NOR)
- 4x 10/100 Mbps Ethernet, with passive PoE support on LAN1
- 2T2R 2,4 GHz (AR9344)
- built-in 4G/3G module (example: Quectel EC-25EU)
- internal microSD slot (spi-mmc, buggy and disabled for now)
- RS232 on D-Sub9 port (Cypress ACM via USB, /dev/ttyACM0)
- RS422/RS485 (AR934x high speed UART, /dev/ttyATH1)
- analog 0-24V input (MCP3221)
- various digital inputs and outputs incl. a relay
- 11x LED (4 are driven by AR9344, 7 by PCA9539)
- 2x miniSIM slot (can be swapped via GPIO)
- 2x RP-SMA/F (Wi-Fi), 3x SMA/F (2x WWAN, GPS)
- 1x button (reset)
- DC jack for main power input (9-30 V)
- debugging UART available on PCB edge connector
Serial console (/dev/ttyS0) pinout:
- RX: pin1 (square) on top side of the main PCB (AR9344 is on top)
- TX: pin1 (square) on bottom side
Flash instruction:
Vendor firmware is based on OpenWrt CC release. Use the "factory" image
directly in GUI (make sure to uncheck "keep settings") or in U-Boot web
based recovery. To avoid any problems, make sure to first update vendor
firmware to latest version - "factory" image was successfully tested on
device running "RUT9XX_R_00.06.051" firmware and U-Boot "3.0.1".
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
2020-04-29 19:59:04 +00:00
|
|
|
define Device/teltonika_rut955-h7v3c0
|
|
|
|
|
$(Device/teltonika_rut955)
|
|
|
|
|
DEVICE_VARIANT := H7V3C0
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += teltonika_rut955-h7v3c0
|
|
|
|
|
|
2019-07-05 17:45:19 +00:00
|
|
|
define Device/trendnet_tew-823dru
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9558
|
2019-07-05 17:45:19 +00:00
|
|
|
DEVICE_VENDOR := Trendnet
|
|
|
|
|
DEVICE_MODEL := TEW-823DRU
|
|
|
|
|
DEVICE_VARIANT := v1.0R
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-ath10k-ct ath10k-firmware-qca988x-ct
|
2019-07-05 17:45:19 +00:00
|
|
|
SUPPORTED_DEVICES += tew-823dru
|
|
|
|
|
IMAGE_SIZE := 15296k
|
|
|
|
|
IMAGES := factory.bin sysupgrade.bin
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | append-rootfs | \
|
|
|
|
|
pad-rootfs
|
2019-07-05 17:45:19 +00:00
|
|
|
IMAGE/factory.bin := $$(IMAGE/default) | pad-offset $$$$(IMAGE_SIZE) 26 | \
|
2020-03-10 13:58:27 +00:00
|
|
|
append-string 00AP135AR9558-RT-131129-00 | check-size
|
2019-12-19 19:42:19 +00:00
|
|
|
IMAGE/sysupgrade.bin := $$(IMAGE/default) | append-metadata | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2019-07-05 17:45:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += trendnet_tew-823dru
|
|
|
|
|
|
2019-05-25 12:36:05 +00:00
|
|
|
define Device/wd_mynet-n750
|
|
|
|
|
$(Device/seama)
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Western Digital
|
|
|
|
|
DEVICE_MODEL := My Net N750
|
2019-05-25 12:36:05 +00:00
|
|
|
IMAGE_SIZE := 15872k
|
2019-09-22 10:06:25 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2
|
2019-05-25 12:36:05 +00:00
|
|
|
SEAMA_SIGNATURE := wrgnd13_wd_av
|
|
|
|
|
SUPPORTED_DEVICES += mynet-n750
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wd_mynet-n750
|
|
|
|
|
|
2018-09-04 21:27:02 +00:00
|
|
|
define Device/wd_mynet-wifi-rangeextender
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Western Digital
|
|
|
|
|
DEVICE_MODEL := My Net Wi-Fi Range Extender
|
2018-09-04 21:27:02 +00:00
|
|
|
DEVICE_PACKAGES := rssileds nvram -swconfig
|
|
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
ADDPATTERN_ID := mynet-rext
|
|
|
|
|
ADDPATTERN_VERSION := 1.00.01
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | pad-rootfs | cybertan-trx | \
|
|
|
|
|
addpattern | append-metadata
|
|
|
|
|
SUPPORTED_DEVICES += mynet-rext
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wd_mynet-wifi-rangeextender
|
2018-10-30 16:05:43 +00:00
|
|
|
|
|
|
|
|
define Device/winchannel_wb2000
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Winchannel
|
|
|
|
|
DEVICE_MODEL := WB2000
|
2018-10-30 16:05:43 +00:00
|
|
|
IMAGE_SIZE := 15872k
|
2020-03-05 14:42:18 +00:00
|
|
|
DEVICE_PACKAGES := kmod-i2c-gpio kmod-rtc-ds1307 kmod-usb2 \
|
2019-12-19 19:42:19 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2018-10-30 16:05:43 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += winchannel_wb2000
|
2019-02-01 19:48:41 +00:00
|
|
|
|
|
|
|
|
define Device/xiaomi_mi-router-4q
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9561
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := Xiaomi
|
|
|
|
|
DEVICE_MODEL := Mi Router 4Q
|
2019-02-01 19:48:41 +00:00
|
|
|
IMAGE_SIZE := 14336k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += xiaomi_mi-router-4q
|
ath79: add support for YunCore A770
YunCore A770 is a ceiling AC750 AP with 2 Fast Ethernet ports, PoE
(802.3at) support, based on QCA9531 + QCA9887.
Specification:
- 650/597/216 MHz (CPU/DDR/AHB)
- 128 MB of RAM (DDR2)
- 16 MB of flash (SPI NOR)
- 2x 10/100 Mbps Ethernet (PoE 802.3at support in WAN port)
- 2T2R 2.4 GHz (QCA9531), with ext. PA and LNA
- 1T1R 5 GHz (QCA9887), with ext. FEM (SKY85728-11)
- 2x regular LED, 1x RGB LED (all driven by GPIO)
- 1x button (reset)
- DC jack for main power input (12 V)
- UART header on PCB
Flash instruction:
1. First, gain root access to the device, following below steps:
- Login into web gui (default password/IP: admin/192.168.188.253).
- Go to 'Advanced' -> 'Management' -> 'System' and download backup of
configuration (bakfile.bin).
- Open the file as tar.gz archive, edit/update 'shadow' file and change
hash of root password to something known.
- Repack the archive, rename it back to 'bakfile.bin' and use to
restore configuration of the device.
- After that, device will reboot and can be accessed over SSH.
2. Then, install OpenWrt:
- Login over SSH and issue command:
fw_setenv bootcmd "bootm 0x9f050000 || bootm 0x9fe80000"
- Upload 'sysupgrade' image and install it (only if previous command
succeeded) with command: 'sysupgrade -n -F openwrt-...'.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-03-09 15:31:17 +00:00
|
|
|
|
|
|
|
|
define Device/yuncore_a770
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9531
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := YunCore
|
|
|
|
|
DEVICE_MODEL := A770
|
ath79: add support for YunCore A770
YunCore A770 is a ceiling AC750 AP with 2 Fast Ethernet ports, PoE
(802.3at) support, based on QCA9531 + QCA9887.
Specification:
- 650/597/216 MHz (CPU/DDR/AHB)
- 128 MB of RAM (DDR2)
- 16 MB of flash (SPI NOR)
- 2x 10/100 Mbps Ethernet (PoE 802.3at support in WAN port)
- 2T2R 2.4 GHz (QCA9531), with ext. PA and LNA
- 1T1R 5 GHz (QCA9887), with ext. FEM (SKY85728-11)
- 2x regular LED, 1x RGB LED (all driven by GPIO)
- 1x button (reset)
- DC jack for main power input (12 V)
- UART header on PCB
Flash instruction:
1. First, gain root access to the device, following below steps:
- Login into web gui (default password/IP: admin/192.168.188.253).
- Go to 'Advanced' -> 'Management' -> 'System' and download backup of
configuration (bakfile.bin).
- Open the file as tar.gz archive, edit/update 'shadow' file and change
hash of root password to something known.
- Repack the archive, rename it back to 'bakfile.bin' and use to
restore configuration of the device.
- After that, device will reboot and can be accessed over SSH.
2. Then, install OpenWrt:
- Login over SSH and issue command:
fw_setenv bootcmd "bootm 0x9f050000 || bootm 0x9fe80000"
- Upload 'sysupgrade' image and install it (only if previous command
succeeded) with command: 'sysupgrade -n -F openwrt-...'.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-03-09 15:31:17 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca9887-ct
|
|
|
|
|
IMAGE_SIZE := 16000k
|
2019-08-12 23:26:45 +00:00
|
|
|
IMAGES += tftp.bin
|
|
|
|
|
IMAGE/tftp.bin := $$(IMAGE/sysupgrade.bin) | yuncore-tftp-header-16m
|
ath79: add support for YunCore A770
YunCore A770 is a ceiling AC750 AP with 2 Fast Ethernet ports, PoE
(802.3at) support, based on QCA9531 + QCA9887.
Specification:
- 650/597/216 MHz (CPU/DDR/AHB)
- 128 MB of RAM (DDR2)
- 16 MB of flash (SPI NOR)
- 2x 10/100 Mbps Ethernet (PoE 802.3at support in WAN port)
- 2T2R 2.4 GHz (QCA9531), with ext. PA and LNA
- 1T1R 5 GHz (QCA9887), with ext. FEM (SKY85728-11)
- 2x regular LED, 1x RGB LED (all driven by GPIO)
- 1x button (reset)
- DC jack for main power input (12 V)
- UART header on PCB
Flash instruction:
1. First, gain root access to the device, following below steps:
- Login into web gui (default password/IP: admin/192.168.188.253).
- Go to 'Advanced' -> 'Management' -> 'System' and download backup of
configuration (bakfile.bin).
- Open the file as tar.gz archive, edit/update 'shadow' file and change
hash of root password to something known.
- Repack the archive, rename it back to 'bakfile.bin' and use to
restore configuration of the device.
- After that, device will reboot and can be accessed over SSH.
2. Then, install OpenWrt:
- Login over SSH and issue command:
fw_setenv bootcmd "bootm 0x9f050000 || bootm 0x9fe80000"
- Upload 'sysupgrade' image and install it (only if previous command
succeeded) with command: 'sysupgrade -n -F openwrt-...'.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-03-09 15:31:17 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += yuncore_a770
|
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>
2019-05-31 13:43:14 +00:00
|
|
|
|
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>
2019-11-12 21:36:28 +00:00
|
|
|
define Device/yuncore_a782
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
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>
2019-11-12 21:36:28 +00:00
|
|
|
DEVICE_VENDOR := YunCore
|
|
|
|
|
DEVICE_MODEL := A782
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca9888-ct
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
IMAGES += tftp.bin
|
|
|
|
|
IMAGE/tftp.bin := $$(IMAGE/sysupgrade.bin) | yuncore-tftp-header-16m
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += yuncore_a782
|
|
|
|
|
|
|
|
|
|
define Device/yuncore_xd4200
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := qca9563
|
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>
2019-11-12 21:36:28 +00:00
|
|
|
DEVICE_VENDOR := YunCore
|
|
|
|
|
DEVICE_MODEL := XD4200
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca9888-ct
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
IMAGES += tftp.bin
|
|
|
|
|
IMAGE/tftp.bin := $$(IMAGE/sysupgrade.bin) | yuncore-tftp-header-16m
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += yuncore_xd4200
|
|
|
|
|
|
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>
2019-05-31 13:43:14 +00:00
|
|
|
define Device/zbtlink_zbt-wd323
|
2019-12-20 00:12:42 +00:00
|
|
|
SOC := ar9344
|
2019-06-16 19:34:46 +00:00
|
|
|
DEVICE_VENDOR := ZBT
|
|
|
|
|
DEVICE_MODEL := WD323
|
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>
2019-05-31 13:43:14 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
2020-03-05 14:42:18 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-i2c-gpio kmod-rtc-pcf8563 \
|
2019-12-19 19:42:19 +00:00
|
|
|
kmod-usb-serial kmod-usb-serial-cp210x uqmi
|
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>
2019-05-31 13:43:14 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zbtlink_zbt-wd323
|
