2017-05-31 18:02:36 +00:00
|
|
|
DEVICE_VARS += DAP_SIGNATURE NETGEAR_BOARD_ID NETGEAR_HW_ID NETGEAR_KERNEL_MAGIC ROOTFS_SIZE SEAMA_SIGNATURE
|
2017-05-31 09:16:22 +00:00
|
|
|
|
2017-12-18 13:51:28 +00:00
|
|
|
define Build/alfa-network-rootfs-header
|
|
|
|
|
mkimage \
|
|
|
|
|
-A mips -O linux -T filesystem -C lzma -a 0 -e 0 \
|
|
|
|
|
-n 'RootfsImage' -d $@ $@.new
|
|
|
|
|
@mv $@.new $@
|
|
|
|
|
endef
|
|
|
|
|
|
ar71xx: add support for Teltonika RUT900
Teltonika RUT900 is an industrial 3G router based on Atheros AR9344.
There are available 3 other models in RUT9xx series: RUT905, RUT950 and
RUT955, which differ in availability of additional I/O ports, built-in
GSM modem type, GPS antenna and other features. FCC ID of the RUT950
model (LTE module built-in): 2AET4-RUT950.
This patch adds support for the RUT900 model only but can be easily
extended to cover whole series. Also, as there are several different
3/4G modules (Huawei, Quectel, Telit) used in whole series, packages
required for WWAN support are not included by default. It is up to the
user to install required software for built-in modem.
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), with ext. PA (MGA-22103) and LNA
- built-in 3G module (example: Telit HE910-D)
- 2x miniSIM slot
- 2x RP-SMA/F (Wi-Fi), 2x SMA/F (3G)
- PCA9539 16-bit GPIO I2C expander
- 12x LED (4 are driven by AR9344, 7 by PCA9539)
- 1x button (reset)
- DC jack for main power input (9-30 V)
- UART available on PCB edge connector
Serial console 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.03.960" firmware and U-Boot "3.0.1".
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-10-15 11:24:02 +00:00
|
|
|
define Build/append-md5sum-bin
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/mkhash md5 $@ | sed 's/../\\\\x&/g' |\
|
|
|
|
|
xargs echo -ne >> $@
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Build/append-string
|
|
|
|
|
echo -n $(1) >> $@
|
|
|
|
|
endef
|
|
|
|
|
|
2017-05-31 09:16:22 +00:00
|
|
|
define Build/mkbuffaloimg
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/mkbuffaloimg -B $(BOARDNAME) \
|
|
|
|
|
-R $$(($(subst k, * 1024,$(ROOTFS_SIZE)))) \
|
|
|
|
|
-K $$(($(subst k, * 1024,$(KERNEL_SIZE)))) \
|
|
|
|
|
-i $@ -o $@.new
|
|
|
|
|
mv $@.new $@
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Build/mkwrggimg
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/mkwrggimg -b \
|
|
|
|
|
-i $@ -o $@.imghdr -d /dev/mtdblock/1 \
|
|
|
|
|
-m $(BOARDNAME) -s $(DAP_SIGNATURE) \
|
2017-11-07 08:45:52 +00:00
|
|
|
-v OpenWrt -B $(REVISION)
|
2017-05-31 09:16:22 +00:00
|
|
|
mv $@.imghdr $@
|
|
|
|
|
endef
|
|
|
|
|
|
2017-05-31 14:31:44 +00:00
|
|
|
define Build/netgear-squashfs
|
|
|
|
|
rm -rf $@.fs $@.squashfs
|
|
|
|
|
mkdir -p $@.fs/image
|
|
|
|
|
cp $@ $@.fs/image/uImage
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/mksquashfs-lzma \
|
|
|
|
|
$@.fs $@.squashfs \
|
|
|
|
|
-noappend -root-owned -be -b 65536 \
|
|
|
|
|
$(if $(SOURCE_DATE_EPOCH),-fixed-time $(SOURCE_DATE_EPOCH))
|
|
|
|
|
|
|
|
|
|
dd if=/dev/zero bs=1k count=1 >> $@.squashfs
|
|
|
|
|
mkimage \
|
|
|
|
|
-A mips -O linux -T filesystem -C none \
|
|
|
|
|
-M $(NETGEAR_KERNEL_MAGIC) \
|
|
|
|
|
-a 0xbf070000 -e 0xbf070000 \
|
|
|
|
|
-n 'MIPS OpenWrt Linux-$(LINUX_VERSION)' \
|
|
|
|
|
-d $@.squashfs $@
|
|
|
|
|
rm -rf $@.squashfs $@.fs
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Build/netgear-uImage
|
|
|
|
|
$(call Build/uImage,$(1) -M $(NETGEAR_KERNEL_MAGIC))
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Build/relocate-kernel
|
|
|
|
|
rm -rf $@.relocate
|
|
|
|
|
$(CP) ../../generic/image/relocate $@.relocate
|
|
|
|
|
$(MAKE) -j1 -C $@.relocate KERNEL_ADDR=$(KERNEL_LOADADDR) CROSS_COMPILE=$(TARGET_CROSS)
|
|
|
|
|
( \
|
|
|
|
|
dd if=$@.relocate/loader.bin bs=32 conv=sync && \
|
|
|
|
|
perl -e '@s = stat("$@"); print pack("N", @s[7])' && \
|
|
|
|
|
cat "$@" \
|
|
|
|
|
) > "$@.new"
|
|
|
|
|
mv "$@.new" "$@"
|
|
|
|
|
rm -rf $@.relocate
|
|
|
|
|
endef
|
|
|
|
|
|
2017-05-31 09:16:22 +00:00
|
|
|
define Build/seama
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/seama -i $@ $(if $(1),$(1),-m "dev=/dev/mtdblock/1" -m "type=firmware")
|
|
|
|
|
mv $@.seama $@
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Build/seama-seal
|
|
|
|
|
$(call Build/seama,-s $@.seama $(1))
|
|
|
|
|
endef
|
|
|
|
|
|
ar71xx: add support for Teltonika RUT900
Teltonika RUT900 is an industrial 3G router based on Atheros AR9344.
There are available 3 other models in RUT9xx series: RUT905, RUT950 and
RUT955, which differ in availability of additional I/O ports, built-in
GSM modem type, GPS antenna and other features. FCC ID of the RUT950
model (LTE module built-in): 2AET4-RUT950.
This patch adds support for the RUT900 model only but can be easily
extended to cover whole series. Also, as there are several different
3/4G modules (Huawei, Quectel, Telit) used in whole series, packages
required for WWAN support are not included by default. It is up to the
user to install required software for built-in modem.
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), with ext. PA (MGA-22103) and LNA
- built-in 3G module (example: Telit HE910-D)
- 2x miniSIM slot
- 2x RP-SMA/F (Wi-Fi), 2x SMA/F (3G)
- PCA9539 16-bit GPIO I2C expander
- 12x LED (4 are driven by AR9344, 7 by PCA9539)
- 1x button (reset)
- DC jack for main power input (9-30 V)
- UART available on PCB edge connector
Serial console 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.03.960" firmware and U-Boot "3.0.1".
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-10-15 11:24:02 +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
|
|
|
|
|
|
2017-05-31 09:16:22 +00:00
|
|
|
define Build/uImageHiWiFi
|
|
|
|
|
# Field ih_name needs to start with "tw150v1"
|
|
|
|
|
mkimage -A $(LINUX_KARCH) \
|
|
|
|
|
-O linux -T kernel \
|
|
|
|
|
-C $(1) -a $(KERNEL_LOADADDR) -e $(if $(KERNEL_ENTRY),$(KERNEL_ENTRY),$(KERNEL_LOADADDR)) \
|
2017-11-07 08:45:52 +00:00
|
|
|
-n 'tw150v1 $(call toupper,$(LINUX_KARCH)) OpenWrt Linux-$(LINUX_VERSION)' -d $@ $@.new
|
2017-05-31 09:16:22 +00:00
|
|
|
@mv $@.new $@
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Build/wrgg-pad-rootfs
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/padjffs2 $(IMAGE_ROOTFS) -c 64 >>$@
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
|
2017-03-31 11:37:31 +00:00
|
|
|
define Device/ap121f
|
|
|
|
|
DEVICE_TITLE := ALFA Network AP121F
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-storage -swconfig
|
|
|
|
|
BOARDNAME := AP121F
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:192k(u-boot)ro,64k(u-boot-env),64k(art)ro,-(firmware)
|
|
|
|
|
SUPPORTED_DEVICES := ap121f
|
|
|
|
|
IMAGE/sysupgrade.bin = append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ap121f
|
|
|
|
|
|
2017-03-02 17:23:50 +00:00
|
|
|
define Device/ap531b0
|
|
|
|
|
DEVICE_TITLE := Rockeetech AP531B0
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := AP531B0
|
2017-03-02 17:23:50 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ap531b0
|
|
|
|
|
|
2016-10-06 00:19:17 +00:00
|
|
|
define Device/ap90q
|
|
|
|
|
DEVICE_TITLE := YunCore AP90Q
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := AP90Q
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),16000k(firmware),64k(art)ro
|
2016-10-06 00:19:17 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ap90q
|
|
|
|
|
|
2017-12-18 13:51:28 +00:00
|
|
|
define Device/ap91-5g
|
|
|
|
|
DEVICE_TITLE := ALFA Network AP91-5G
|
|
|
|
|
DEVICE_PACKAGES := rssileds -swconfig
|
|
|
|
|
BOARDNAME := AP91-5G
|
|
|
|
|
IMAGE_SIZE := 7744k
|
|
|
|
|
KERNEL_SIZE := 1600k
|
|
|
|
|
ROOTFS_SIZE := 6144k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),6144k(rootfs),1600k(kernel),64k(config)ro,64k(art)ro,7744k@0x50000(firmware)
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
|
|
|
|
IMAGE/factory.bin := append-rootfs | pad-rootfs |\
|
|
|
|
|
alfa-network-rootfs-header | append-kernel | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | pad-rootfs |\
|
|
|
|
|
pad-to $$$$(ROOTFS_SIZE) | append-kernel | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ap91-5g
|
|
|
|
|
|
2017-06-13 08:05:13 +00:00
|
|
|
define Device/arduino-yun
|
|
|
|
|
DEVICE_TITLE := Arduino Yun
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := Yun
|
|
|
|
|
IMAGE_SIZE := 15936k
|
|
|
|
|
CONSOLE = ttyATH0,250000
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),15936k(firmware),64k(nvram),64k(art)ro
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += arduino-yun
|
|
|
|
|
|
2016-05-22 21:10:02 +00:00
|
|
|
define Device/bsb
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := Smart Electronics Black Swift board
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := BSB
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,64k(u-boot-env)ro,16128k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += bsb
|
|
|
|
|
|
|
|
|
|
define Device/carambola2
|
2017-05-31 19:56:10 +00:00
|
|
|
DEVICE_TITLE := 8devices Carambola2
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CARAMBOLA2
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += carambola2
|
|
|
|
|
|
|
|
|
|
define Device/cf-e316n-v2
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := COMFAST CF-E316N v2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CF-E316N-V2
|
|
|
|
|
IMAGE_SIZE := 16192k
|
|
|
|
|
MTDPARTS := spi0.0:64k(u-boot)ro,64k(art)ro,16192k(firmware),64k(art-backup)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cf-e316n-v2
|
|
|
|
|
|
ar71xx: add support for COMFAST CF-E320N v2 and CF-E520N/CF-E530N
As we already have support for CF-E316N v2 and many devices from
this vendor look similar, the support was included in existing
mach-*.c file, with few cleanups and fixes.
All 3 devices are based on Qualcomm/Atheros QCA9531 v2.
COMFAST CF-E320N v2 is a ceiling mount AP with PoE support.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, both with PoE support
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x RGB LED, 1x button
- UART (J1), GPIO (J9) and USB (J2) headers on PCB
- external watchdog (Pericon Technology PT7A7514)
COMFAST CF-E520N/CF-E530N are in-wall APs with USB and PoE support.
They seem to have different only the front panel.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, WAN with PoE support
- 1x USB 2.0 (in CF-E520N covered by panel, available on PCB)
- 32 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x LED, 1x button
- UART (J1) headers on PCB
Flash instruction:
Original firmware is based on OpenWrt.
Use sysupgrade image directly in vendor GUI.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-10-05 00:24:58 +00:00
|
|
|
define Device/cf-e320n-v2
|
|
|
|
|
$(Device/cf-e316n-v2)
|
|
|
|
|
DEVICE_TITLE := COMFAST CF-E320N v2
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CF-E320N-V2
|
ar71xx: add support for COMFAST CF-E320N v2 and CF-E520N/CF-E530N
As we already have support for CF-E316N v2 and many devices from
this vendor look similar, the support was included in existing
mach-*.c file, with few cleanups and fixes.
All 3 devices are based on Qualcomm/Atheros QCA9531 v2.
COMFAST CF-E320N v2 is a ceiling mount AP with PoE support.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, both with PoE support
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x RGB LED, 1x button
- UART (J1), GPIO (J9) and USB (J2) headers on PCB
- external watchdog (Pericon Technology PT7A7514)
COMFAST CF-E520N/CF-E530N are in-wall APs with USB and PoE support.
They seem to have different only the front panel.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, WAN with PoE support
- 1x USB 2.0 (in CF-E520N covered by panel, available on PCB)
- 32 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x LED, 1x button
- UART (J1) headers on PCB
Flash instruction:
Original firmware is based on OpenWrt.
Use sysupgrade image directly in vendor GUI.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-10-05 00:24:58 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cf-e320n-v2
|
|
|
|
|
|
2017-06-29 10:03:03 +00:00
|
|
|
define Device/cf-e355ac
|
|
|
|
|
DEVICE_TITLE := COMFAST CF-E355AC
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
BOARDNAME := CF-E355AC
|
|
|
|
|
IMAGE_SIZE := 16192k
|
|
|
|
|
MTDPARTS := spi0.0:64k(u-boot)ro,64k(art)ro,16192k(firmware),64k(art-backup)ro
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cf-e355ac
|
|
|
|
|
|
ar71xx: add support for COMFAST CF-E380AC v1 and v2
COMFAST CF-E380AC v1/v2 is a ceiling mount AP with PoE
support, based on Qualcomm/Atheros QCA9558+QCA9880+AR8035.
There are two versions of this model, with different RAM
and U-Boot mtd partition sizes:
- v1: 128 MB of RAM, 128 KB U-Boot image size
- v2: 256 MB of RAM, 256 KB U-Boot image size
Version number is available only inside vendor GUI,
hardware and markings are the same.
Short specification:
- 720/600/200 MHz (CPU/DDR/AHB)
- 1x 10/100/1000 Mbps Ethernet, with PoE support
- 128 or 256 MB of RAM (DDR2)
- 16 MB of FLASH
- 3T3R 2.4 GHz, with external PA (SE2576L), up to 28 dBm
- 3T3R 5 GHz, with external PA (SE5003L1), up to 30 dBm
- 6x internal antennas
- 1x RGB LED, 1x button
- UART (T11), LEDs/GPIO (J7) and USB (T12) headers on PCB
- external watchdog (Pericon Technology PT7A7514)
Flash instruction:
Original firmware is based on OpenWrt.
Use sysupgrade image directly in vendor GUI.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-11-14 16:38:23 +00:00
|
|
|
define Device/cf-e380ac-v1
|
|
|
|
|
DEVICE_TITLE := COMFAST CF-E380AC v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-ath10k ath10k-firmware-qca988x
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CF-E380AC-V1
|
|
|
|
|
IMAGE_SIZE := 16128k
|
|
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,64k(art)ro,16128k(firmware),64k(art-backup)ro
|
ar71xx: add support for COMFAST CF-E380AC v1 and v2
COMFAST CF-E380AC v1/v2 is a ceiling mount AP with PoE
support, based on Qualcomm/Atheros QCA9558+QCA9880+AR8035.
There are two versions of this model, with different RAM
and U-Boot mtd partition sizes:
- v1: 128 MB of RAM, 128 KB U-Boot image size
- v2: 256 MB of RAM, 256 KB U-Boot image size
Version number is available only inside vendor GUI,
hardware and markings are the same.
Short specification:
- 720/600/200 MHz (CPU/DDR/AHB)
- 1x 10/100/1000 Mbps Ethernet, with PoE support
- 128 or 256 MB of RAM (DDR2)
- 16 MB of FLASH
- 3T3R 2.4 GHz, with external PA (SE2576L), up to 28 dBm
- 3T3R 5 GHz, with external PA (SE5003L1), up to 30 dBm
- 6x internal antennas
- 1x RGB LED, 1x button
- UART (T11), LEDs/GPIO (J7) and USB (T12) headers on PCB
- external watchdog (Pericon Technology PT7A7514)
Flash instruction:
Original firmware is based on OpenWrt.
Use sysupgrade image directly in vendor GUI.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-11-14 16:38:23 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cf-e380ac-v1
|
|
|
|
|
|
|
|
|
|
define Device/cf-e380ac-v2
|
|
|
|
|
$(Device/cf-e380ac-v1)
|
|
|
|
|
DEVICE_TITLE := COMFAST CF-E380AC v2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CF-E380AC-V2
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(art)ro,16000k(firmware),64k(art-backup)ro
|
ar71xx: add support for COMFAST CF-E380AC v1 and v2
COMFAST CF-E380AC v1/v2 is a ceiling mount AP with PoE
support, based on Qualcomm/Atheros QCA9558+QCA9880+AR8035.
There are two versions of this model, with different RAM
and U-Boot mtd partition sizes:
- v1: 128 MB of RAM, 128 KB U-Boot image size
- v2: 256 MB of RAM, 256 KB U-Boot image size
Version number is available only inside vendor GUI,
hardware and markings are the same.
Short specification:
- 720/600/200 MHz (CPU/DDR/AHB)
- 1x 10/100/1000 Mbps Ethernet, with PoE support
- 128 or 256 MB of RAM (DDR2)
- 16 MB of FLASH
- 3T3R 2.4 GHz, with external PA (SE2576L), up to 28 dBm
- 3T3R 5 GHz, with external PA (SE5003L1), up to 30 dBm
- 6x internal antennas
- 1x RGB LED, 1x button
- UART (T11), LEDs/GPIO (J7) and USB (T12) headers on PCB
- external watchdog (Pericon Technology PT7A7514)
Flash instruction:
Original firmware is based on OpenWrt.
Use sysupgrade image directly in vendor GUI.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-11-14 16:38:23 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cf-e380ac-v2
|
|
|
|
|
|
ar71xx: add support for COMFAST CF-E320N v2 and CF-E520N/CF-E530N
As we already have support for CF-E316N v2 and many devices from
this vendor look similar, the support was included in existing
mach-*.c file, with few cleanups and fixes.
All 3 devices are based on Qualcomm/Atheros QCA9531 v2.
COMFAST CF-E320N v2 is a ceiling mount AP with PoE support.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, both with PoE support
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x RGB LED, 1x button
- UART (J1), GPIO (J9) and USB (J2) headers on PCB
- external watchdog (Pericon Technology PT7A7514)
COMFAST CF-E520N/CF-E530N are in-wall APs with USB and PoE support.
They seem to have different only the front panel.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, WAN with PoE support
- 1x USB 2.0 (in CF-E520N covered by panel, available on PCB)
- 32 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x LED, 1x button
- UART (J1) headers on PCB
Flash instruction:
Original firmware is based on OpenWrt.
Use sysupgrade image directly in vendor GUI.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-10-05 00:24:58 +00:00
|
|
|
define Device/cf-e520n
|
|
|
|
|
DEVICE_TITLE := COMFAST CF-E520N
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CF-E520N
|
|
|
|
|
IMAGE_SIZE := 8000k
|
|
|
|
|
MTDPARTS := spi0.0:64k(u-boot)ro,64k(art)ro,8000k(firmware),64k(art-backup)ro
|
ar71xx: add support for COMFAST CF-E320N v2 and CF-E520N/CF-E530N
As we already have support for CF-E316N v2 and many devices from
this vendor look similar, the support was included in existing
mach-*.c file, with few cleanups and fixes.
All 3 devices are based on Qualcomm/Atheros QCA9531 v2.
COMFAST CF-E320N v2 is a ceiling mount AP with PoE support.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, both with PoE support
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x RGB LED, 1x button
- UART (J1), GPIO (J9) and USB (J2) headers on PCB
- external watchdog (Pericon Technology PT7A7514)
COMFAST CF-E520N/CF-E530N are in-wall APs with USB and PoE support.
They seem to have different only the front panel.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, WAN with PoE support
- 1x USB 2.0 (in CF-E520N covered by panel, available on PCB)
- 32 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x LED, 1x button
- UART (J1) headers on PCB
Flash instruction:
Original firmware is based on OpenWrt.
Use sysupgrade image directly in vendor GUI.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-10-05 00:24:58 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cf-e520n
|
|
|
|
|
|
|
|
|
|
define Device/cf-e530n
|
|
|
|
|
$(Device/cf-e520n)
|
|
|
|
|
DEVICE_TITLE := COMFAST CF-E530N
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CF-E530N
|
ar71xx: add support for COMFAST CF-E320N v2 and CF-E520N/CF-E530N
As we already have support for CF-E316N v2 and many devices from
this vendor look similar, the support was included in existing
mach-*.c file, with few cleanups and fixes.
All 3 devices are based on Qualcomm/Atheros QCA9531 v2.
COMFAST CF-E320N v2 is a ceiling mount AP with PoE support.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, both with PoE support
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x RGB LED, 1x button
- UART (J1), GPIO (J9) and USB (J2) headers on PCB
- external watchdog (Pericon Technology PT7A7514)
COMFAST CF-E520N/CF-E530N are in-wall APs with USB and PoE support.
They seem to have different only the front panel.
Short specification:
- 650/393/216 MHz (CPU/DDR/AHB)
- 2x 10/100 Mbps Ethernet, WAN with PoE support
- 1x USB 2.0 (in CF-E520N covered by panel, available on PCB)
- 32 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz, up to 22 dBm
- 2x internal antennas
- 1x LED, 1x button
- UART (J1) headers on PCB
Flash instruction:
Original firmware is based on OpenWrt.
Use sysupgrade image directly in vendor GUI.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-10-05 00:24:58 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cf-e530n
|
|
|
|
|
|
ar71xx: add support for P&W R602N and CPE505N
P&W (full name: Shenzhen Progress&Win Technologies) R602N (could be also
labeled as R602F, R602, etc.) is a simple N300 router with 5-port
10/100 Mbps switch, non-detachable antennas and USB.
CPE505 is an outdoor CPE with PoE support and detachable antennas.
Both devices are based on Qualcomm/Atheros QCA9531 v2.
Common specification:
- 650/597/216 MHz (CPU/DDR/AHB)
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- UART (J2) header on PCB
R602N specification:
- 5x 10/100 Mbps Ethernet
- 1x USB 2.0
- 2T2R 2.4 GHz with external LNA and PA (SE2576L), up to 28 dBm
- 2x external, non-detachable antennas
- 7x LED, 1x button
CPE505N specification:
- 2x 10/100 Mbps Ethernet (both ports support passive PoE 12-24 V)
- 2T2R 2.4 GHz with external LNA and PA (SKY65174-21), up to 30 dBm
- 2x external, detachable antennas (RP-SMA connectors)
- 1x RGB LED, 2x LEDs (in RJ45 sockets), 1x button
Flash instructions:
It seems that there are many different versions of the firmware which
these devices are shipped with. The generic/standard one is based on
some modified OpenWrt and LEDE firmware can be flashed directly from
vendor's webgui or with sysupgrade (root password is "admin123").
Before flashing, make sure (use "fw_printenv") that the kernel load
address in your device is set to "0x9f050000" (bootcmd variable is
"bootm 0x9f050000"). If your device uses different load address, you
should first change it, under vendor's firmware, with command:
fw_setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS"
Where OLD_ADDRESS is previous kernel load address (in CPE505 version
I got access to, it was "0x9fe80000"). This will allow you to use
both the vendor's and LEDE firmware.
If version of your device contains empty U-Boot environment (you will
get information about this after issuing "fw_printenv"), you should
use U-Boot, serial line access and TFTP to perform firmware upgrade:
1. tftp 0x80060000 lede-ar71xx-generic-...-squashfs-sysupgrade.bin
2. erase 0x9f050000 +$filesize
3. cp.b $fileaddr 0x9f050000 $filesize
4. setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS"
5. saveenv && reset
These devices contain also web recovery mode inside U-Boot. It can be
started with pressing the reset button for around 3 seconds just after
the device powerup. Web recovery panel is available on "192.168.10.9"
and to be able to use it, IP on your PC must be set to "192.168.10.10".
Make sure to change kernel load address before using recovery mode or
the U-Boot will not be able to load LEDE firmware.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-03-15 23:54:08 +00:00
|
|
|
define Device/cpe505n
|
|
|
|
|
DEVICE_TITLE := P&W CPE505N
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CPE505N
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
ar71xx: add support for P&W R602N and CPE505N
P&W (full name: Shenzhen Progress&Win Technologies) R602N (could be also
labeled as R602F, R602, etc.) is a simple N300 router with 5-port
10/100 Mbps switch, non-detachable antennas and USB.
CPE505 is an outdoor CPE with PoE support and detachable antennas.
Both devices are based on Qualcomm/Atheros QCA9531 v2.
Common specification:
- 650/597/216 MHz (CPU/DDR/AHB)
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- UART (J2) header on PCB
R602N specification:
- 5x 10/100 Mbps Ethernet
- 1x USB 2.0
- 2T2R 2.4 GHz with external LNA and PA (SE2576L), up to 28 dBm
- 2x external, non-detachable antennas
- 7x LED, 1x button
CPE505N specification:
- 2x 10/100 Mbps Ethernet (both ports support passive PoE 12-24 V)
- 2T2R 2.4 GHz with external LNA and PA (SKY65174-21), up to 30 dBm
- 2x external, detachable antennas (RP-SMA connectors)
- 1x RGB LED, 2x LEDs (in RJ45 sockets), 1x button
Flash instructions:
It seems that there are many different versions of the firmware which
these devices are shipped with. The generic/standard one is based on
some modified OpenWrt and LEDE firmware can be flashed directly from
vendor's webgui or with sysupgrade (root password is "admin123").
Before flashing, make sure (use "fw_printenv") that the kernel load
address in your device is set to "0x9f050000" (bootcmd variable is
"bootm 0x9f050000"). If your device uses different load address, you
should first change it, under vendor's firmware, with command:
fw_setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS"
Where OLD_ADDRESS is previous kernel load address (in CPE505 version
I got access to, it was "0x9fe80000"). This will allow you to use
both the vendor's and LEDE firmware.
If version of your device contains empty U-Boot environment (you will
get information about this after issuing "fw_printenv"), you should
use U-Boot, serial line access and TFTP to perform firmware upgrade:
1. tftp 0x80060000 lede-ar71xx-generic-...-squashfs-sysupgrade.bin
2. erase 0x9f050000 +$filesize
3. cp.b $fileaddr 0x9f050000 $filesize
4. setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS"
5. saveenv && reset
These devices contain also web recovery mode inside U-Boot. It can be
started with pressing the reset button for around 3 seconds just after
the device powerup. Web recovery panel is available on "192.168.10.9"
and to be able to use it, IP on your PC must be set to "192.168.10.10".
Make sure to change kernel load address before using recovery mode or
the U-Boot will not be able to load LEDE firmware.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-03-15 23:54:08 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cpe505n
|
|
|
|
|
|
2016-10-08 01:36:35 +00:00
|
|
|
define Device/cpe830
|
|
|
|
|
$(Device/ap90q)
|
|
|
|
|
DEVICE_TITLE := YunCore CPE830
|
|
|
|
|
DEVICE_PACKAGES := rssileds
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CPE830
|
2016-10-08 01:36:35 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cpe830
|
|
|
|
|
|
2016-10-07 23:17:04 +00:00
|
|
|
define Device/cpe870
|
|
|
|
|
DEVICE_TITLE := YunCore CPE870
|
|
|
|
|
DEVICE_PACKAGES := rssileds
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := CPE870
|
|
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
MTDPARTS := spi0.0:64k(u-boot)ro,64k(u-boot-env),7936k(firmware),64k(config)ro,64k(art)ro
|
2016-10-07 23:17:04 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cpe870
|
|
|
|
|
|
2016-10-06 12:08:24 +00:00
|
|
|
define Device/dragino2
|
|
|
|
|
BOARDNAME := DRAGINO2
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2017-05-30 20:55:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
2016-10-06 12:08:24 +00:00
|
|
|
DEVICE_TITLE := Dragino 2 (MS14)
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,16000k(firmware),64k(config)ro,64k(art)ro
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dragino2
|
2017-07-19 09:44:57 +00:00
|
|
|
|
|
|
|
|
define Device/ew-dorin
|
|
|
|
|
DEVICE_TITLE := Embedded Wireless Dorin Platform
|
2018-01-12 15:36:13 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb-chipidea
|
2017-07-19 09:44:57 +00:00
|
|
|
BOARDNAME = EW-DORIN
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
IMAGE_SIZE = 16000k
|
|
|
|
|
MTDPARTS = spi0.0:256k(u-boot)ro,64k(u-boot-env),16000k(firmware),64k(art)ro
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ew-dorin
|
|
|
|
|
|
|
|
|
|
define Device/ew-dorin-router
|
|
|
|
|
DEVICE_TITLE := Embedded Wireless Dorin Router Platform
|
2018-01-12 15:36:13 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb-chipidea
|
2017-07-19 09:44:57 +00:00
|
|
|
BOARDNAME = EW-DORIN-ROUTER
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
IMAGE_SIZE = 16000k
|
|
|
|
|
MTDPARTS = spi0.0:256k(u-boot)ro,64k(u-boot-env),16000k(firmware),64k(art)ro
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ew-dorin-router
|
2016-10-06 12:08:24 +00:00
|
|
|
|
2016-05-22 21:10:02 +00:00
|
|
|
define Device/weio
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := WeIO
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := WEIO
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += weio
|
|
|
|
|
|
|
|
|
|
define Device/gl-ar150
|
2017-05-31 20:12:51 +00:00
|
|
|
DEVICE_TITLE := GL.iNet GL-AR150
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := GL-AR150
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += gl-ar150
|
|
|
|
|
|
|
|
|
|
define Device/gl-ar300
|
2017-05-31 20:12:51 +00:00
|
|
|
DEVICE_TITLE := GL.iNet GL-AR300
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := GL-AR300
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += gl-ar300
|
|
|
|
|
|
2016-07-15 10:00:04 +00:00
|
|
|
define Device/gl-ar300m
|
2017-05-31 20:12:51 +00:00
|
|
|
DEVICE_TITLE := GL.iNet GL-AR300M
|
2017-05-30 20:25:02 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := GL-AR300M
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),16000k(firmware),64k(art)ro
|
2016-07-15 10:00:04 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += gl-ar300m
|
|
|
|
|
|
2017-10-17 21:30:01 +00:00
|
|
|
define Device/gl-ar750
|
|
|
|
|
DEVICE_TITLE := GL.iNet GL-AR750
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca9887 kmod-usb-core \
|
|
|
|
|
kmod-usb2 kmod-usb-storage
|
|
|
|
|
BOARDNAME := GL-AR750
|
|
|
|
|
SUPPORTED_DEVICES := gl-ar750
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),64k(art)ro,-(firmware)
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += gl-ar750
|
|
|
|
|
|
2016-05-22 21:10:02 +00:00
|
|
|
define Device/gl-domino
|
2017-05-31 20:12:51 +00:00
|
|
|
DEVICE_TITLE := GL.iNet Domino Pi
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := DOMINO
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += gl-domino
|
|
|
|
|
|
2016-07-19 02:54:11 +00:00
|
|
|
define Device/gl-mifi
|
2017-05-31 20:12:51 +00:00
|
|
|
DEVICE_TITLE := GL.iNet GL-MiFi
|
2016-07-19 02:54:11 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := GL-MIFI
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
2016-07-19 02:54:11 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += gl-mifi
|
|
|
|
|
|
2017-08-19 16:26:46 +00:00
|
|
|
define Device/gl-usb150
|
|
|
|
|
DEVICE_TITLE := GL.iNet GL-USB150
|
|
|
|
|
DEVICE_PACKAGES := -swconfig
|
|
|
|
|
BOARDNAME := GL-USB150
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
|
|
|
|
SUPPORTED_DEVICES := gl-usb150
|
|
|
|
|
IMAGE/sysupgrade.bin = append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += gl-usb150
|
|
|
|
|
|
2017-02-12 17:34:36 +00:00
|
|
|
define Device/lima
|
2017-05-31 19:56:10 +00:00
|
|
|
DEVICE_TITLE := 8devices Lima
|
2017-02-12 17:34:36 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := LIMA
|
|
|
|
|
IMAGE_SIZE := 15616k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,256k(u-boot-env)ro,256k(art)ro,-(firmware)
|
2017-02-12 17:34:36 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += lima
|
|
|
|
|
|
2016-10-24 19:05:53 +00:00
|
|
|
define Device/mr12
|
|
|
|
|
DEVICE_TITLE := Meraki MR12
|
|
|
|
|
DEVICE_PACKAGES := kmod-spi-gpio
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := MR12
|
2017-05-31 18:02:36 +00:00
|
|
|
ROOTFS_SIZE := 13440k
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE_SIZE := 15680k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,256k(u-boot-env)ro,13440k(rootfs),2240k(kernel),64k(mac),128k(art)ro,15680k@0x80000(firmware)
|
|
|
|
|
IMAGE/kernel.bin := append-kernel
|
|
|
|
|
IMAGE/rootfs.bin := append-rootfs | pad-rootfs
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | pad-rootfs | pad-to $$$$(ROOTFS_SIZE) | append-kernel | check-size $$$$(IMAGE_SIZE)
|
2016-10-24 19:05:53 +00:00
|
|
|
IMAGES := kernel.bin rootfs.bin sysupgrade.bin
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += mr12
|
2016-10-24 19:05:53 +00:00
|
|
|
|
|
|
|
|
define Device/mr16
|
2017-07-07 16:51:26 +00:00
|
|
|
$(Device/mr12)
|
2016-10-24 19:05:53 +00:00
|
|
|
DEVICE_TITLE := Meraki MR16
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := MR16
|
2016-10-24 19:05:53 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += mr16
|
2016-10-24 19:05:53 +00:00
|
|
|
|
2017-10-23 11:30:20 +00:00
|
|
|
define Device/dr342
|
|
|
|
|
DEVICE_TITLE := Wallys DR342
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 -swconfig
|
|
|
|
|
BOARDNAME := DR342
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:192k(u-boot)ro,64k(u-boot-env),64k(partition-table)ro,16000k(firmware),64k(art)ro
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dr342
|
|
|
|
|
|
2017-05-29 20:07:04 +00:00
|
|
|
define Device/dr344
|
|
|
|
|
DEVICE_TITLE := Wallys DR344
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := DR344
|
2017-05-29 20:07:04 +00:00
|
|
|
KERNEL_SIZE := 1408k
|
2017-05-31 18:02:36 +00:00
|
|
|
ROOTFS_SIZE := 6336k
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE_SIZE := 7744k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,6336k(rootfs),1408k(kernel),64k(nvram),64k(art)ro,7744k@0x50000(firmware)
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | pad-rootfs | pad-to $$$$(ROOTFS_SIZE) | append-kernel | check-size $$$$(IMAGE_SIZE)
|
2017-05-29 20:07:04 +00:00
|
|
|
endef
|
|
|
|
|
|
2016-06-16 16:08:03 +00:00
|
|
|
define Device/dr531
|
|
|
|
|
DEVICE_TITLE := Wallys DR531
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := DR531
|
|
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
MTDPARTS := spi0.0:192k(u-boot)ro,64k(u-boot-env),64k(partition-table)ro,7808k(firmware),64k(art)ro
|
2016-06-16 16:08:03 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dr531
|
|
|
|
|
|
2016-05-22 21:10:02 +00:00
|
|
|
define Device/wndr3700
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := NETGEAR WNDR3700
|
2016-10-19 10:09:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-usb-ledtrig-usbport kmod-leds-wndr3700-usb
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := WNDR3700
|
|
|
|
|
NETGEAR_KERNEL_MAGIC := 0x33373030
|
|
|
|
|
NETGEAR_BOARD_ID := WNDR3700
|
|
|
|
|
IMAGE_SIZE := 7680k
|
|
|
|
|
MTDPARTS := spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,7680k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
IMAGES := sysupgrade.bin factory.img factory-NA.img
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma -d20 | netgear-uImage lzma
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE/default := append-kernel | pad-to $$$$(BLOCKSIZE) | netgear-squashfs | append-rootfs | pad-rootfs
|
|
|
|
|
IMAGE/sysupgrade.bin := $$(IMAGE/default) | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
IMAGE/factory.img := $$(IMAGE/default) | netgear-dni | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
IMAGE/factory-NA.img := $$(IMAGE/default) | netgear-dni NA | check-size $$$$(IMAGE_SIZE)
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wndr3700
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/wndr3700v2
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/wndr3700)
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := NETGEAR WNDR3700 v2
|
2017-06-08 13:18:34 +00:00
|
|
|
NETGEAR_BOARD_ID := WNDR3700v2
|
|
|
|
|
NETGEAR_KERNEL_MAGIC := 0x33373031
|
|
|
|
|
NETGEAR_HW_ID := 29763654+16+64
|
|
|
|
|
IMAGE_SIZE := 15872k
|
|
|
|
|
MTDPARTS := spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,15872k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
IMAGES := sysupgrade.bin factory.img
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wndr3700v2
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/wndr3800
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/wndr3700v2)
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := NETGEAR WNDR3800
|
2017-06-08 13:18:34 +00:00
|
|
|
NETGEAR_BOARD_ID := WNDR3800
|
|
|
|
|
NETGEAR_HW_ID := 29763654+16+128
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wndr3800
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/wndr3800ch
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/wndr3800)
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := NETGEAR WNDR3800 (Ch)
|
2017-06-08 13:18:34 +00:00
|
|
|
NETGEAR_BOARD_ID := WNDR3800CH
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wndr3800ch
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/wndrmac
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/wndr3700v2)
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := NETGEAR WNDRMAC
|
2017-06-08 13:18:34 +00:00
|
|
|
NETGEAR_BOARD_ID := WNDRMAC
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wndrmac
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/wndrmacv2
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/wndr3800)
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := NETGEAR WNDRMAC v2
|
2017-06-08 13:18:34 +00:00
|
|
|
NETGEAR_BOARD_ID := WNDRMACv2
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wndrmacv2
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/cap324
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := PowerCloud CAP324 Cloud AP
|
2016-05-22 21:10:02 +00:00
|
|
|
BOARDNAME := CAP324
|
|
|
|
|
DEVICE_PROFILE := CAP324
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE_SIZE := 15296k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,15296k(firmware),640k(certs),64k(nvram),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cap324
|
|
|
|
|
|
|
|
|
|
define Device/cap324-nocloud
|
2016-07-07 08:24:03 +00:00
|
|
|
DEVICE_TITLE := PowerCloud CAP324 Cloud AP (No-Cloud)
|
2016-05-22 21:10:02 +00:00
|
|
|
BOARDNAME := CAP324
|
|
|
|
|
DEVICE_PROFILE := CAP324
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cap324-nocloud
|
|
|
|
|
|
|
|
|
|
define Device/cr3000
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := PowerCloud CR3000 Cloud Router
|
2016-05-22 21:10:02 +00:00
|
|
|
BOARDNAME := CR3000
|
|
|
|
|
DEVICE_PROFILE := CR3000
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE_SIZE := 7104k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,7104k(firmware),640k(certs),64k(nvram),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cr3000
|
|
|
|
|
|
|
|
|
|
define Device/cr3000-nocloud
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := PowerCloud CR3000 (No-Cloud)
|
2016-05-22 21:10:02 +00:00
|
|
|
BOARDNAME := CR3000
|
|
|
|
|
DEVICE_PROFILE := CR3000
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,7808k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cr3000-nocloud
|
|
|
|
|
|
|
|
|
|
define Device/cr5000
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := PowerCloud CR5000 Cloud Router
|
2017-05-30 20:55:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport kmod-usb-core
|
2016-05-22 21:10:02 +00:00
|
|
|
BOARDNAME := CR5000
|
|
|
|
|
DEVICE_PROFILE := CR5000
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE_SIZE := 7104k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,7104k(firmware),640k(certs),64k(nvram),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cr5000
|
|
|
|
|
|
|
|
|
|
define Device/cr5000-nocloud
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := PowerCloud CR5000 (No-Cloud)
|
2017-05-30 20:55:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ledtrig-usbport kmod-usb-core
|
2016-05-22 21:10:02 +00:00
|
|
|
BOARDNAME := CR5000
|
|
|
|
|
DEVICE_PROFILE := CR5000
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,7808k(firmware),64k(art)ro
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cr5000-nocloud
|
|
|
|
|
|
2017-01-10 09:47:19 +00:00
|
|
|
define Device/pqi-air-pen
|
|
|
|
|
DEVICE_TITLE := PQI Air Pen
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-storage
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := PQI-AIR-PEN
|
|
|
|
|
IMAGE_SIZE := 7744k
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,64k(art)ro,64k(NVRAM)ro,7680k(firmware),64k(CONF)
|
2017-01-10 09:47:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += pqi-air-pen
|
|
|
|
|
|
2016-05-22 21:10:02 +00:00
|
|
|
define Device/antminer-s1
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := Antminer-S1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-crypto-manager kmod-i2c-gpio-custom kmod-usb-hid
|
|
|
|
|
BOARDNAME := ANTMINER-S1
|
|
|
|
|
DEVICE_PROFILE := ANTMINERS1
|
|
|
|
|
TPLINK_HWID := 0x04440101
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += antminer-s1
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/antminer-s3
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := Antminer-S3
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-crypto-manager kmod-i2c-gpio-custom kmod-usb-hid
|
|
|
|
|
BOARDNAME := ANTMINER-S3
|
|
|
|
|
DEVICE_PROFILE := ANTMINERS3
|
|
|
|
|
TPLINK_HWID := 0x04440301
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += antminer-s3
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/antrouter-r1
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := Antrouter-R1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := ANTROUTER-R1
|
|
|
|
|
DEVICE_PROFILE := ANTROUTERR1
|
|
|
|
|
TPLINK_HWID := 0x44440101
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += antrouter-r1
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/el-m150
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := EasyLink EL-M150
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := EL-M150
|
|
|
|
|
DEVICE_PROFILE := ELM150
|
|
|
|
|
TPLINK_HWID := 0x01500101
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += el-m150
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/el-mini
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := EasyLink EL-MINI
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := EL-MINI
|
|
|
|
|
DEVICE_PROFILE := ELMINI
|
|
|
|
|
TPLINK_HWID := 0x01530001
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += el-mini
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/gl-inet-6408A-v1
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := GL.iNet 6408
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := GL-INET
|
|
|
|
|
DEVICE_PROFILE := GLINET
|
|
|
|
|
TPLINK_HWID := 0x08000001
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += gl-inet-6408A-v1
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/gl-inet-6416A-v1
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := GL.iNet 6416
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := GL-INET
|
|
|
|
|
DEVICE_PROFILE := GLINET
|
|
|
|
|
TPLINK_HWID := 0x08000001
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += gl-inet-6416A-v1
|
2016-05-22 21:10:02 +00:00
|
|
|
|
2016-07-08 13:03:00 +00:00
|
|
|
define Device/jwap230
|
|
|
|
|
DEVICE_TITLE := jjPlus JWAP230
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := JWAP230
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),16000k(firmware),64k(art)ro
|
2016-07-08 13:03:00 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += jwap230
|
|
|
|
|
|
ar71xx: add support for ALFA Network R36A
ALFA Network R36A is a successor of the previous model, the R36 (Ralink
RT3050F based). New version is based on Qualcomm/Atheros QCA9531 v2.
Specification:
- 650/400/200 MHz (CPU/DDR/AHB)
- 64 MB of RAM (DDR2)
- 16 MB of FLASH (SPI NOR)
- 2x 10/100 Mbps Ethernet, with passive PoE support (24 V)
- 2T2R (QCA9531) 2.4 GHz, 2x u.fl connectors on PCB
- 1x USB 2.0 (power controlled by GPIO)
- 6x LED (5 of them are driven by GPIO)
- 2x button (reset, wifi/wps)
- external h/w watchdog (EM6324QYSP5B, disabled and not used)
- DC jack for main power input (12 V)
- UART header on PCB
Flash instruction:
You can use sysupgrade image directly in vendor firmware which is based
on LEDE/OpenWrt. Alternatively, you can use web recovery mode in U-Boot:
1. Configure PC with static IP 192.168.1.2/24.
2. Connect PC with one of RJ45 ports, press the reset button, power up
device, wait for first blink of all LEDs (indicates network setup),
then keep button for 3 following blinks and release it.
3. Open 192.168.1.1 address in your browser and upload sysupgrade image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-12-28 10:07:54 +00:00
|
|
|
define Device/r36a
|
|
|
|
|
DEVICE_TITLE := ALFA Network R36A
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport -swconfig
|
|
|
|
|
BOARDNAME := R36A
|
|
|
|
|
SUPPORTED_DEVICES := r36a
|
|
|
|
|
IMAGE_SIZE := 15872k
|
|
|
|
|
MTDPARTS := spi0.0:384k(u-boot)ro,64k(u-boot-env),64k(art)ro,-(firmware)
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += r36a
|
|
|
|
|
|
ar71xx: add support for P&W R602N and CPE505N
P&W (full name: Shenzhen Progress&Win Technologies) R602N (could be also
labeled as R602F, R602, etc.) is a simple N300 router with 5-port
10/100 Mbps switch, non-detachable antennas and USB.
CPE505 is an outdoor CPE with PoE support and detachable antennas.
Both devices are based on Qualcomm/Atheros QCA9531 v2.
Common specification:
- 650/597/216 MHz (CPU/DDR/AHB)
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- UART (J2) header on PCB
R602N specification:
- 5x 10/100 Mbps Ethernet
- 1x USB 2.0
- 2T2R 2.4 GHz with external LNA and PA (SE2576L), up to 28 dBm
- 2x external, non-detachable antennas
- 7x LED, 1x button
CPE505N specification:
- 2x 10/100 Mbps Ethernet (both ports support passive PoE 12-24 V)
- 2T2R 2.4 GHz with external LNA and PA (SKY65174-21), up to 30 dBm
- 2x external, detachable antennas (RP-SMA connectors)
- 1x RGB LED, 2x LEDs (in RJ45 sockets), 1x button
Flash instructions:
It seems that there are many different versions of the firmware which
these devices are shipped with. The generic/standard one is based on
some modified OpenWrt and LEDE firmware can be flashed directly from
vendor's webgui or with sysupgrade (root password is "admin123").
Before flashing, make sure (use "fw_printenv") that the kernel load
address in your device is set to "0x9f050000" (bootcmd variable is
"bootm 0x9f050000"). If your device uses different load address, you
should first change it, under vendor's firmware, with command:
fw_setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS"
Where OLD_ADDRESS is previous kernel load address (in CPE505 version
I got access to, it was "0x9fe80000"). This will allow you to use
both the vendor's and LEDE firmware.
If version of your device contains empty U-Boot environment (you will
get information about this after issuing "fw_printenv"), you should
use U-Boot, serial line access and TFTP to perform firmware upgrade:
1. tftp 0x80060000 lede-ar71xx-generic-...-squashfs-sysupgrade.bin
2. erase 0x9f050000 +$filesize
3. cp.b $fileaddr 0x9f050000 $filesize
4. setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS"
5. saveenv && reset
These devices contain also web recovery mode inside U-Boot. It can be
started with pressing the reset button for around 3 seconds just after
the device powerup. Web recovery panel is available on "192.168.10.9"
and to be able to use it, IP on your PC must be set to "192.168.10.10".
Make sure to change kernel load address before using recovery mode or
the U-Boot will not be able to load LEDE firmware.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-03-15 23:54:08 +00:00
|
|
|
define Device/r602n
|
|
|
|
|
DEVICE_TITLE := P&W R602N
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := R602N
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro
|
ar71xx: add support for P&W R602N and CPE505N
P&W (full name: Shenzhen Progress&Win Technologies) R602N (could be also
labeled as R602F, R602, etc.) is a simple N300 router with 5-port
10/100 Mbps switch, non-detachable antennas and USB.
CPE505 is an outdoor CPE with PoE support and detachable antennas.
Both devices are based on Qualcomm/Atheros QCA9531 v2.
Common specification:
- 650/597/216 MHz (CPU/DDR/AHB)
- 64 MB of RAM (DDR2)
- 16 MB of FLASH
- UART (J2) header on PCB
R602N specification:
- 5x 10/100 Mbps Ethernet
- 1x USB 2.0
- 2T2R 2.4 GHz with external LNA and PA (SE2576L), up to 28 dBm
- 2x external, non-detachable antennas
- 7x LED, 1x button
CPE505N specification:
- 2x 10/100 Mbps Ethernet (both ports support passive PoE 12-24 V)
- 2T2R 2.4 GHz with external LNA and PA (SKY65174-21), up to 30 dBm
- 2x external, detachable antennas (RP-SMA connectors)
- 1x RGB LED, 2x LEDs (in RJ45 sockets), 1x button
Flash instructions:
It seems that there are many different versions of the firmware which
these devices are shipped with. The generic/standard one is based on
some modified OpenWrt and LEDE firmware can be flashed directly from
vendor's webgui or with sysupgrade (root password is "admin123").
Before flashing, make sure (use "fw_printenv") that the kernel load
address in your device is set to "0x9f050000" (bootcmd variable is
"bootm 0x9f050000"). If your device uses different load address, you
should first change it, under vendor's firmware, with command:
fw_setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS"
Where OLD_ADDRESS is previous kernel load address (in CPE505 version
I got access to, it was "0x9fe80000"). This will allow you to use
both the vendor's and LEDE firmware.
If version of your device contains empty U-Boot environment (you will
get information about this after issuing "fw_printenv"), you should
use U-Boot, serial line access and TFTP to perform firmware upgrade:
1. tftp 0x80060000 lede-ar71xx-generic-...-squashfs-sysupgrade.bin
2. erase 0x9f050000 +$filesize
3. cp.b $fileaddr 0x9f050000 $filesize
4. setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS"
5. saveenv && reset
These devices contain also web recovery mode inside U-Boot. It can be
started with pressing the reset button for around 3 seconds just after
the device powerup. Web recovery panel is available on "192.168.10.9"
and to be able to use it, IP on your PC must be set to "192.168.10.10".
Make sure to change kernel load address before using recovery mode or
the U-Boot will not be able to load LEDE firmware.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-03-15 23:54:08 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += r602n
|
|
|
|
|
|
ar71xx: add support for Teltonika RUT900
Teltonika RUT900 is an industrial 3G router based on Atheros AR9344.
There are available 3 other models in RUT9xx series: RUT905, RUT950 and
RUT955, which differ in availability of additional I/O ports, built-in
GSM modem type, GPS antenna and other features. FCC ID of the RUT950
model (LTE module built-in): 2AET4-RUT950.
This patch adds support for the RUT900 model only but can be easily
extended to cover whole series. Also, as there are several different
3/4G modules (Huawei, Quectel, Telit) used in whole series, packages
required for WWAN support are not included by default. It is up to the
user to install required software for built-in modem.
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), with ext. PA (MGA-22103) and LNA
- built-in 3G module (example: Telit HE910-D)
- 2x miniSIM slot
- 2x RP-SMA/F (Wi-Fi), 2x SMA/F (3G)
- PCA9539 16-bit GPIO I2C expander
- 12x LED (4 are driven by AR9344, 7 by PCA9539)
- 1x button (reset)
- DC jack for main power input (9-30 V)
- UART available on PCB edge connector
Serial console 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.03.960" firmware and U-Boot "3.0.1".
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-10-15 11:24:02 +00:00
|
|
|
define Device/rut900
|
|
|
|
|
DEVICE_TITLE := Teltonika RUT900
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 -uboot-envtools
|
|
|
|
|
BOARDNAME := RUT900
|
|
|
|
|
SUPPORTED_DEVICES := rut900
|
|
|
|
|
IMAGE_SIZE := 15552k
|
|
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,64k(config)ro,64k(art)ro,15552k(firmware),576k(event-log)ro
|
|
|
|
|
TPLINK_HWID := 0x35000001
|
|
|
|
|
TPLINK_HWREV := 0x1
|
|
|
|
|
TPLINK_HEADER_VERSION := 1
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | tplink-v1-header
|
|
|
|
|
KERNEL_INITRAMFS := kernel-bin | patch-cmdline | lzma | uImage lzma
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | append-rootfs |\
|
|
|
|
|
pad-rootfs | teltonika-fw-fake-checksum | append-string master |\
|
|
|
|
|
append-md5sum-bin | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to $$$$(BLOCKSIZE) |\
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata |\
|
|
|
|
|
check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += rut900
|
|
|
|
|
|
2016-05-22 21:10:02 +00:00
|
|
|
define Device/mc-mac1200r
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
2017-01-31 21:26:39 +00:00
|
|
|
DEVICE_TITLE := Mercury MAC1200R
|
2016-07-22 13:57:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca988x
|
2016-06-30 01:54:20 +00:00
|
|
|
BOARDNAME := MC-MAC1200R
|
|
|
|
|
DEVICE_PROFILE := MAC1200R
|
|
|
|
|
TPLINK_HWID := 0x12000001
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mc-mac1200r
|
|
|
|
|
|
|
|
|
|
define Device/minibox-v1
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := Gainstrong MiniBox V1.0
|
2016-10-19 10:09:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
2016-06-30 01:54:20 +00:00
|
|
|
BOARDNAME := MINIBOX-V1
|
|
|
|
|
DEVICE_PROFILE := MINIBOXV1
|
|
|
|
|
TPLINK_HWID := 0x3C000201
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += minibox-v1
|
|
|
|
|
|
|
|
|
|
define Device/omy-g1
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := OMYlink OMY-G1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := OMY-G1
|
|
|
|
|
DEVICE_PROFILE := OMYG1
|
|
|
|
|
TPLINK_HWID := 0x06660101
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += omy-g1
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/omy-x1
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := OMYlink OMY-X1
|
|
|
|
|
BOARDNAME := OMY-X1
|
|
|
|
|
DEVICE_PROFILE := OMYX1
|
|
|
|
|
TPLINK_HWID := 0x06660201
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += omy-x1
|
2016-05-22 21:10:02 +00:00
|
|
|
|
|
|
|
|
define Device/onion-omega
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := Onion Omega
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-storage kmod-i2c-core kmod-i2c-gpio-custom kmod-spi-bitbang kmod-spi-dev kmod-spi-gpio kmod-spi-gpio-custom kmod-usb-serial
|
|
|
|
|
BOARDNAME := ONION-OMEGA
|
|
|
|
|
DEVICE_PROFILE := OMEGA
|
|
|
|
|
TPLINK_HWID := 0x04700001
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += onion-omega
|
|
|
|
|
|
2017-01-15 22:01:05 +00:00
|
|
|
define Device/sc1750
|
|
|
|
|
DEVICE_TITLE := Abicom SC1750
|
2017-05-30 20:55:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := SC1750
|
|
|
|
|
IMAGE_SIZE := 15744k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),15744k(firmware),128k(APConfig),128k(kplog),64k(ART)
|
2017-01-15 22:01:05 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += sc1750
|
|
|
|
|
|
2017-01-15 22:01:03 +00:00
|
|
|
define Device/sc300m
|
|
|
|
|
DEVICE_TITLE := Abicom SC300M
|
2017-05-30 20:55:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := SC300M
|
|
|
|
|
IMAGE_SIZE := 15744k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),15744k(firmware),128k(APConfig),128k(kplog),64k(ART)
|
2017-01-15 22:01:03 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += sc300m
|
|
|
|
|
|
2017-01-15 22:01:04 +00:00
|
|
|
define Device/sc450
|
|
|
|
|
DEVICE_TITLE := Abicom SC450
|
2017-05-30 20:55:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := SC450
|
|
|
|
|
IMAGE_SIZE := 15744k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),15744k(firmware),128k(APConfig),128k(kplog),64k(ART)
|
2017-01-15 22:01:04 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += sc450
|
|
|
|
|
|
2016-05-22 21:10:02 +00:00
|
|
|
define Device/smart-300
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := NC-LINK SMART-300
|
|
|
|
|
BOARDNAME := SMART-300
|
|
|
|
|
DEVICE_PROFILE := SMART-300
|
|
|
|
|
TPLINK_HWID := 0x93410001
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += smart-300
|
|
|
|
|
|
2016-05-29 22:26:03 +00:00
|
|
|
define Device/som9331
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := OpenEmbed SOM9331
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-storage kmod-i2c-core kmod-i2c-gpio-custom kmod-spi-bitbang kmod-spi-dev kmod-spi-gpio kmod-spi-gpio-custom kmod-usb-serial
|
|
|
|
|
BOARDNAME := SOM9331
|
|
|
|
|
DEVICE_PROFILE := SOM9331
|
|
|
|
|
TPLINK_HWID := 0x04800054
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-29 22:26:03 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += som9331
|
|
|
|
|
|
ar71xx: add support for YunCore SR3200 and XD3200
YunCore SR3200 is a dual-band AC1200 router, based on Qualcomm/Atheros
QCA9563+QCA9882+QCA8337N.
YunCore XD3200 (FCC ID: 2ADUG-XD3200) is a dual-band AC1200 ceiling mount
AP with PoE support, based on Qualcomm/Atheros QCA9563+QCA9882+QCA8334.
Common specification:
- 775/650/258 MHz (CPU/DDR/AHB)
- 128 MB or RAM (DDR2)
- 16 MB of FLASH (SPI NOR)
- 2T2R 2.4 GHz, with ext. PA (SKY65174-21), up to 30 dBm
- 2T2R 5 GHz, with ext. PA (SKY85405-11) and LNA (SKY85601-11), up to 30 dBm
SR3200 specification:
- 5x 10/100/1000 Mbps Ethernet
- 6x ext. RP-SMA antennas (actually, only 4 are connected with radio chips)
- 3x LED (+ 5x LED in RJ45 sockets), 1x button
- UART header on PCB
XD3200 specification:
- 2x 10/100/1000 Mbps Ethernet, with 802.3at PoE support (WAN port)
- 4x internal antennas
- 3 sets of LEDs on external PCB (+ 2x LED near RJ45 sockets), 1x button
- UART and JTAG (custom 6-pin, 2 mm pitch) headers on PCB
LED for 5 GHz WLAN is currently not supported on both devices as it is
connected directly to the QCA9882 radio chip.
Flash instruction under vendor firmware, using telnet/SSH:
1. If your firmware does not have root password, go to point 5
2. Connect PC with 192.168.1.x address to LAN or WAN port
3. Power up device, enter failsafe mode with button (no LED indicator!)
4. Change root password and reboot (mount_root, passwd ..., reboot -f)
5. Upload lede-ar71xx-...-sysupgrade.bin to /tmp using SCP
6. Connect PC with 192.168.188.x address to LAN port, SSH to 192.168.188.253
7. Invoke:
- cd /tmp
- fw_setenv bootcmd "bootm 0x9fe80000 || bootm 0x9f050000"
- mtd -e firmware -r write lede-ar71xx-...-sysupgrade.bin firmware
Flash instruction under U-Boot, using UART:
1. tftp 0x80060000 lede-ar71xx-...-sysupgrade.bin
2. erase 0x9f050000 +$filesize
3. cp.b $fileaddr 0x9f050000 $filesize
4. setenv bootcmd "bootm 0x9fe80000 || bootm 0x9f050000"
5. saveenv && reset
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-12-02 21:42:41 +00:00
|
|
|
define Device/sr3200
|
|
|
|
|
DEVICE_TITLE := YunCore SR3200
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-ath10k ath10k-firmware-qca988x
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := SR3200
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),16000k(firmware),64k(art)ro
|
ar71xx: add support for YunCore SR3200 and XD3200
YunCore SR3200 is a dual-band AC1200 router, based on Qualcomm/Atheros
QCA9563+QCA9882+QCA8337N.
YunCore XD3200 (FCC ID: 2ADUG-XD3200) is a dual-band AC1200 ceiling mount
AP with PoE support, based on Qualcomm/Atheros QCA9563+QCA9882+QCA8334.
Common specification:
- 775/650/258 MHz (CPU/DDR/AHB)
- 128 MB or RAM (DDR2)
- 16 MB of FLASH (SPI NOR)
- 2T2R 2.4 GHz, with ext. PA (SKY65174-21), up to 30 dBm
- 2T2R 5 GHz, with ext. PA (SKY85405-11) and LNA (SKY85601-11), up to 30 dBm
SR3200 specification:
- 5x 10/100/1000 Mbps Ethernet
- 6x ext. RP-SMA antennas (actually, only 4 are connected with radio chips)
- 3x LED (+ 5x LED in RJ45 sockets), 1x button
- UART header on PCB
XD3200 specification:
- 2x 10/100/1000 Mbps Ethernet, with 802.3at PoE support (WAN port)
- 4x internal antennas
- 3 sets of LEDs on external PCB (+ 2x LED near RJ45 sockets), 1x button
- UART and JTAG (custom 6-pin, 2 mm pitch) headers on PCB
LED for 5 GHz WLAN is currently not supported on both devices as it is
connected directly to the QCA9882 radio chip.
Flash instruction under vendor firmware, using telnet/SSH:
1. If your firmware does not have root password, go to point 5
2. Connect PC with 192.168.1.x address to LAN or WAN port
3. Power up device, enter failsafe mode with button (no LED indicator!)
4. Change root password and reboot (mount_root, passwd ..., reboot -f)
5. Upload lede-ar71xx-...-sysupgrade.bin to /tmp using SCP
6. Connect PC with 192.168.188.x address to LAN port, SSH to 192.168.188.253
7. Invoke:
- cd /tmp
- fw_setenv bootcmd "bootm 0x9fe80000 || bootm 0x9f050000"
- mtd -e firmware -r write lede-ar71xx-...-sysupgrade.bin firmware
Flash instruction under U-Boot, using UART:
1. tftp 0x80060000 lede-ar71xx-...-sysupgrade.bin
2. erase 0x9f050000 +$filesize
3. cp.b $fileaddr 0x9f050000 $filesize
4. setenv bootcmd "bootm 0x9fe80000 || bootm 0x9f050000"
5. saveenv && reset
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-12-02 21:42:41 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += sr3200
|
|
|
|
|
|
|
|
|
|
define Device/xd3200
|
|
|
|
|
$(Device/sr3200)
|
|
|
|
|
DEVICE_TITLE := YunCore XD3200
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca988x
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := XD3200
|
ar71xx: add support for YunCore SR3200 and XD3200
YunCore SR3200 is a dual-band AC1200 router, based on Qualcomm/Atheros
QCA9563+QCA9882+QCA8337N.
YunCore XD3200 (FCC ID: 2ADUG-XD3200) is a dual-band AC1200 ceiling mount
AP with PoE support, based on Qualcomm/Atheros QCA9563+QCA9882+QCA8334.
Common specification:
- 775/650/258 MHz (CPU/DDR/AHB)
- 128 MB or RAM (DDR2)
- 16 MB of FLASH (SPI NOR)
- 2T2R 2.4 GHz, with ext. PA (SKY65174-21), up to 30 dBm
- 2T2R 5 GHz, with ext. PA (SKY85405-11) and LNA (SKY85601-11), up to 30 dBm
SR3200 specification:
- 5x 10/100/1000 Mbps Ethernet
- 6x ext. RP-SMA antennas (actually, only 4 are connected with radio chips)
- 3x LED (+ 5x LED in RJ45 sockets), 1x button
- UART header on PCB
XD3200 specification:
- 2x 10/100/1000 Mbps Ethernet, with 802.3at PoE support (WAN port)
- 4x internal antennas
- 3 sets of LEDs on external PCB (+ 2x LED near RJ45 sockets), 1x button
- UART and JTAG (custom 6-pin, 2 mm pitch) headers on PCB
LED for 5 GHz WLAN is currently not supported on both devices as it is
connected directly to the QCA9882 radio chip.
Flash instruction under vendor firmware, using telnet/SSH:
1. If your firmware does not have root password, go to point 5
2. Connect PC with 192.168.1.x address to LAN or WAN port
3. Power up device, enter failsafe mode with button (no LED indicator!)
4. Change root password and reboot (mount_root, passwd ..., reboot -f)
5. Upload lede-ar71xx-...-sysupgrade.bin to /tmp using SCP
6. Connect PC with 192.168.188.x address to LAN port, SSH to 192.168.188.253
7. Invoke:
- cd /tmp
- fw_setenv bootcmd "bootm 0x9fe80000 || bootm 0x9f050000"
- mtd -e firmware -r write lede-ar71xx-...-sysupgrade.bin firmware
Flash instruction under U-Boot, using UART:
1. tftp 0x80060000 lede-ar71xx-...-sysupgrade.bin
2. erase 0x9f050000 +$filesize
3. cp.b $fileaddr 0x9f050000 $filesize
4. setenv bootcmd "bootm 0x9fe80000 || bootm 0x9f050000"
5. saveenv && reset
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2016-12-02 21:42:41 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += xd3200
|
|
|
|
|
|
2016-05-22 21:10:02 +00:00
|
|
|
define Device/tellstick-znet-lite
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := TellStick ZNet Lite
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-acm kmod-usb-serial kmod-usb-serial-pl2303
|
|
|
|
|
BOARDNAME := TELLSTICK-ZNET-LITE
|
|
|
|
|
DEVICE_PROFILE := TELLSTICKZNETLITE
|
|
|
|
|
TPLINK_HWID := 0x00726001
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tellstick-znet-lite
|
|
|
|
|
|
|
|
|
|
define Device/oolite
|
2016-06-30 01:54:20 +00:00
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := Gainstrong OOLITE
|
2016-10-19 10:09:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
2016-06-30 01:54:20 +00:00
|
|
|
BOARDNAME := GS-OOLITE
|
|
|
|
|
DEVICE_PROFILE := OOLITE
|
|
|
|
|
TPLINK_HWID := 0x3C000101
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += oolite
|
|
|
|
|
|
ar71xx: add support for ALFA Network N5Q
ALFA Network N5Q is a successor of previous model, the N5 (outdoor
CPE/AP, based on Atheros AR7240 + AR9280). New version is based on
Atheros AR9344.
Specification:
- 550/400/200 MHz (CPU/DDR/AHB)
- 64 MB of RAM (DDR2)
- 16 MB of FLASH (SPI NOR)
- 2x 10/100 Mbps Ethernet, with passive PoE support (24 V)
- 2T2R 5 GHz (AR9344), with ext. PA (RFPA5542) and LNA, up to 27 dBm
- 8x LED (7 are driven by GPIO)
- 1x button (reset)
- external h/w watchdog (EM6324QYSP5B, disabled and not used)
- header for optional 802.3at/af PoE module
- DC jack for main power input (optional, not installed by default)
- UART header on PCB
Flash instruction:
You can use sysupgrade image directly in vendor firmare which is based
on OpenWrt/LEDE. Alternatively, you can use web recovery mode in U-Boot:
1. Configure PC with static IP 192.168.1.2/24.
2. Connect PC with one of RJ45 ports, press the reset button, power up
device, wait for first blink of all LEDs (indicates network setup),
then keep button for 3 following blinks and release it.
3. Open 192.168.1.1 address in your browser and upload sysupgrade image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2018-01-05 10:35:45 +00:00
|
|
|
define Device/n5q
|
|
|
|
|
DEVICE_TITLE := ALFA Network N5Q
|
|
|
|
|
DEVICE_PACKAGES := rssileds -swconfig
|
|
|
|
|
BOARDNAME := N5Q
|
|
|
|
|
SUPPORTED_DEVICES := n5q
|
|
|
|
|
IMAGE_SIZE := 15872k
|
|
|
|
|
MTDPARTS := spi0.0:384k(u-boot)ro,64k(u-boot-env),64k(art)ro,-(firmware)
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += n5q
|
|
|
|
|
|
2016-05-22 21:10:02 +00:00
|
|
|
define Device/NBG6616
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := ZyXEL NBG6616
|
2016-10-19 10:09:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-usb-storage kmod-rtc-pcf8563 kmod-ath10k ath10k-firmware-qca988x
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := NBG6616
|
|
|
|
|
KERNEL_SIZE := 2048k
|
|
|
|
|
IMAGE_SIZE := 15323k
|
|
|
|
|
MTDPARTS := spi0.0:192k(u-boot)ro,64k(env)ro,64k(RFdata)ro,384k(zyxel_rfsd),384k(romd),64k(header),2048k(kernel),13184k(rootfs),15232k@0x120000(firmware)
|
2016-06-17 04:53:22 +00:00
|
|
|
CMDLINE += mem=128M
|
|
|
|
|
IMAGES := sysupgrade.bin
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | uImage lzma | jffs2 boot/vmlinux.lzma.uImage
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to $$$$(KERNEL_SIZE) | append-rootfs | pad-rootfs | check-size $$$$(IMAGE_SIZE)
|
2016-06-17 04:53:22 +00:00
|
|
|
# We cannot currently build a factory image. It is the sysupgrade image
|
|
|
|
|
# prefixed with a header (which is actually written into the MTD device).
|
|
|
|
|
# The header is 2kiB and is filled with 0xff. The format seems to be:
|
|
|
|
|
# 2 bytes: 0x0000
|
|
|
|
|
# 2 bytes: checksum of the data partition (big endian)
|
|
|
|
|
# 4 bytes: length of the contained image file (big endian)
|
|
|
|
|
# 32 bytes: Firmware Version string (NUL terminated, 0xff padded)
|
|
|
|
|
# 2 bytes: 0x0000
|
|
|
|
|
# 2 bytes: checksum over the header partition (big endian)
|
|
|
|
|
# 32 bytes: Model (e.g. "NBG6616", NUL termiated, 0xff padded)
|
|
|
|
|
# rest: 0xff padding
|
|
|
|
|
#
|
|
|
|
|
# The checksums are calculated by adding up all bytes and if a 16bit
|
|
|
|
|
# overflow occurs, one is added and the sum is masked to 16 bit:
|
|
|
|
|
# csum = csum + databyte; if (csum > 0xffff) { csum += 1; csum &= 0xffff };
|
|
|
|
|
# Should the file have an odd number of bytes then the byte len-0x800 is
|
|
|
|
|
# used additionally.
|
|
|
|
|
# The checksum for the header is calcualted over the first 2048 bytes with
|
|
|
|
|
# the firmware checksum as the placeholder during calculation.
|
|
|
|
|
#
|
|
|
|
|
# The header is padded with 0xff to the erase block size of the device.
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += NBG6616
|
|
|
|
|
|
|
|
|
|
define Device/c-55
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_TITLE := AirTight Networks C-55
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath9k
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := C-55
|
|
|
|
|
KERNEL_SIZE := 2048k
|
|
|
|
|
IMAGE_SIZE := 15872k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,128k(u-boot-env)ro,2048k(kernel),13824k(rootfs),13824k(opt)ro,2624k(failsafe)ro,64k(art)ro,15872k@0x60000(firmware)
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to $$$$(KERNEL_SIZE) | append-rootfs | pad-rootfs | check-size $$$$(IMAGE_SIZE)
|
2016-05-22 21:10:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += c-55
|
2016-06-20 14:25:50 +00:00
|
|
|
|
|
|
|
|
define Device/hiwifi-hc6361
|
2016-06-30 01:54:18 +00:00
|
|
|
DEVICE_TITLE := HiWiFi HC6361
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-storage \
|
|
|
|
|
kmod-fs-ext4 kmod-nls-iso8859-1 e2fsprogs
|
|
|
|
|
BOARDNAME := HiWiFi-HC6361
|
|
|
|
|
DEVICE_PROFILE := HIWIFI_HC6361
|
|
|
|
|
IMAGE_SIZE := 16128k
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | uImageHiWiFi lzma
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
|
|
|
|
MTDPARTS := spi0.0:64k(u-boot)ro,64k(bdinfo)ro,16128k(firmware),64k(backup)ro,64k(art)ro
|
2016-06-20 14:25:50 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += hiwifi-hc6361
|
2016-06-30 01:54:21 +00:00
|
|
|
|
|
|
|
|
define Device/seama
|
2016-07-09 12:15:58 +00:00
|
|
|
LOADER_TYPE := bin
|
2016-10-11 18:32:24 +00:00
|
|
|
BLOCKSIZE := 64k
|
2016-10-11 18:32:25 +00:00
|
|
|
KERNEL := kernel-bin | patch-cmdline | relocate-kernel | lzma
|
2016-10-11 18:32:24 +00:00
|
|
|
KERNEL_INITRAMFS := kernel-bin | patch-cmdline | lzma | seama
|
2016-06-30 01:54:21 +00:00
|
|
|
KERNEL_INITRAMFS_SUFFIX = $$(KERNEL_SUFFIX).seama
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
2016-10-11 18:32:24 +00:00
|
|
|
|
|
|
|
|
# 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
|
|
|
|
|
IMAGE/sysupgrade.bin := \
|
|
|
|
|
$$(IMAGE/default) | seama | pad-rootfs | \
|
|
|
|
|
check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
IMAGE/factory.bin := \
|
|
|
|
|
$$(IMAGE/default) | seama | pad-rootfs | \
|
|
|
|
|
seama-seal -m "signature=$$$$(SEAMA_SIGNATURE)" | \
|
|
|
|
|
check-size $$$$(IMAGE_SIZE)
|
2016-06-30 01:54:21 +00:00
|
|
|
SEAMA_SIGNATURE :=
|
|
|
|
|
endef
|
|
|
|
|
|
2016-10-11 18:32:26 +00:00
|
|
|
define Device/dir-869-a1
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/seama)
|
2016-10-11 18:32:26 +00:00
|
|
|
DEVICE_TITLE := D-Link DIR-869 rev. A1
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca988x
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := DIR-869-A1
|
|
|
|
|
IMAGE_SIZE := 15872k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,64k(devdata)ro,64k(devconf)ro,15872k(firmware),64k(radiocfg)ro
|
2016-10-11 18:32:26 +00:00
|
|
|
SEAMA_SIGNATURE := wrgac54_dlink.2015_dir869
|
|
|
|
|
IMAGE/factory.bin := \
|
|
|
|
|
$$(IMAGE/default) | pad-rootfs -x 64 | \
|
|
|
|
|
seama | seama-seal -m "signature=$$$$(SEAMA_SIGNATURE)" | \
|
|
|
|
|
check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += dir-869-a1
|
2016-10-11 18:32:26 +00:00
|
|
|
|
2016-06-30 01:54:21 +00:00
|
|
|
define Device/mynet-n600
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/seama)
|
2016-06-30 01:54:21 +00:00
|
|
|
DEVICE_TITLE := Western Digital My Net N600
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := MYNET-N600
|
|
|
|
|
IMAGE_SIZE := 15808k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,64k(devdata)ro,64k(devconf)ro,15872k(firmware),64k(radiocfg)ro
|
2016-06-30 01:54:21 +00:00
|
|
|
SEAMA_SIGNATURE := wrgnd16_wd_db600
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += mynet-n600
|
2016-06-30 01:54:21 +00:00
|
|
|
|
|
|
|
|
define Device/mynet-n750
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/seama)
|
2016-06-30 01:54:21 +00:00
|
|
|
DEVICE_TITLE := Western Digital My Net N750
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := MYNET-N750
|
|
|
|
|
IMAGE_SIZE := 15808k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,64k(devdata)ro,64k(devconf)ro,15872k(firmware),64k(radiocfg)ro
|
2016-06-30 01:54:21 +00:00
|
|
|
SEAMA_SIGNATURE := wrgnd13_wd_av
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += mynet-n750
|
2016-06-30 01:54:21 +00:00
|
|
|
|
|
|
|
|
define Device/qihoo-c301
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/seama)
|
2016-06-30 01:54:21 +00:00
|
|
|
DEVICE_TITLE := Qihoo C301
|
2016-10-19 10:09:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k ath10k-firmware-qca988x
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := QIHOO-C301
|
|
|
|
|
IMAGE_SIZE := 15744k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env),64k(devdata),64k(devconf),15744k(firmware),64k(warm_start),64k(action_image_config),64k(radiocfg)ro;spi0.1:15360k(upgrade2),1024k(privatedata)
|
2016-06-30 01:54:21 +00:00
|
|
|
SEAMA_SIGNATURE := wrgac26_qihoo360_360rg
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += qihoo-c301
|
2016-07-18 17:39:57 +00:00
|
|
|
|
|
|
|
|
define Device/dap-2695-a1
|
|
|
|
|
DEVICE_TITLE := D-Link DAP-2695 rev. A1
|
2017-05-30 20:25:02 +00:00
|
|
|
DEVICE_PACKAGES := ath10k-firmware-qca988x kmod-ath10k
|
2017-06-08 13:18:34 +00:00
|
|
|
BOARDNAME := DAP-2695-A1
|
2016-07-18 17:39:57 +00:00
|
|
|
IMAGES := factory.img sysupgrade.bin
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE_SIZE := 15360k
|
|
|
|
|
IMAGE/factory.img := append-kernel | pad-offset 65536 160 | append-rootfs | wrgg-pad-rootfs | mkwrggimg | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-offset 65536 160 | mkwrggimg | append-rootfs | wrgg-pad-rootfs | check-size $$$$(IMAGE_SIZE)
|
2016-07-18 17:39:57 +00:00
|
|
|
KERNEL := kernel-bin | patch-cmdline | relocate-kernel | lzma
|
|
|
|
|
KERNEL_INITRAMFS := $$(KERNEL) | mkwrggimg
|
2017-06-08 13:18:34 +00:00
|
|
|
MTDPARTS := spi0.0:256k(bootloader)ro,64k(bdcfg)ro,64k(rgdb)ro,64k(langpack)ro,15360k(firmware),448k(captival)ro,64k(certificate)ro,64k(radiocfg)ro
|
2016-07-18 17:39:57 +00:00
|
|
|
DAP_SIGNATURE := wapac02_dkbs_dap2695
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dap-2695-a1
|
2016-11-08 13:45:00 +00:00
|
|
|
|
|
|
|
|
define Device/bhr-4grv2
|
|
|
|
|
DEVICE_TITLE := Buffalo BHR-4GRV2
|
|
|
|
|
BOARDNAME := BHR-4GRV2
|
|
|
|
|
ROOTFS_SIZE := 14528k
|
|
|
|
|
KERNEL_SIZE := 1472k
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,14528k(rootfs),1472k(kernel),64k(art)ro,16000k@0x50000(firmware)
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | pad-rootfs | pad-to $$$$(ROOTFS_SIZE) | append-kernel | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(KERNEL_SIZE) | append-rootfs | pad-rootfs | mkbuffaloimg
|
2016-11-08 13:45:00 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += bhr-4grv2
|
2017-03-28 19:09:37 +00:00
|
|
|
|
2017-11-23 13:27:39 +00:00
|
|
|
define Device/wlr8100
|
|
|
|
|
DEVICE_TITLE := Sitecom WLR-8100
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-usb3 \
|
|
|
|
|
kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
BOARDNAME := WLR8100
|
|
|
|
|
IMAGE_SIZE := 15424k
|
|
|
|
|
MTDPARTS := spi0.0:192k(u-boot)ro,64k(u-boot-env)ro,15424k(firmware),256k(manufacture)ro,64k(backup)ro,320k(storage)ro,64k(art)ro
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wlr8100
|
|
|
|
|
|
2017-05-30 21:20:16 +00:00
|
|
|
define Device/wpj-16m
|
2017-05-30 20:55:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
2017-03-28 19:16:43 +00:00
|
|
|
MTDPARTS := spi0.0:192k(u-boot)ro,16128k(firmware),64k(art)ro
|
|
|
|
|
IMAGE_SIZE := 16128k
|
|
|
|
|
endef
|
2017-05-30 21:20:16 +00:00
|
|
|
|
|
|
|
|
define Device/wpj342
|
|
|
|
|
$(Device/wpj-16m)
|
|
|
|
|
DEVICE_TITLE := Compex WPJ342 (16MB flash)
|
|
|
|
|
BOARDNAME := WPJ342
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wpj342
|
2017-03-28 19:16:43 +00:00
|
|
|
|
2017-03-28 19:14:49 +00:00
|
|
|
define Device/wpj344
|
2017-05-30 21:20:16 +00:00
|
|
|
$(Device/wpj-16m)
|
2017-03-28 19:14:49 +00:00
|
|
|
DEVICE_TITLE := Compex WPJ344 (16MB flash)
|
|
|
|
|
BOARDNAME := WPJ344
|
2017-08-02 15:08:32 +00:00
|
|
|
SUPPORTED_DEVICES := wpj344
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata | check-size $$$$(IMAGE_SIZE)
|
2017-03-28 19:14:49 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wpj344
|
2017-03-28 19:14:49 +00:00
|
|
|
|
2017-03-28 19:12:48 +00:00
|
|
|
define Device/wpj531
|
2017-05-30 21:20:16 +00:00
|
|
|
$(Device/wpj-16m)
|
2017-03-28 19:12:48 +00:00
|
|
|
DEVICE_TITLE := Compex WPJ531 (16MB flash)
|
|
|
|
|
BOARDNAME := WPJ531
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wpj531
|
2017-03-28 19:12:48 +00:00
|
|
|
|
2017-03-28 19:09:37 +00:00
|
|
|
define Device/wpj558
|
2017-05-30 21:20:16 +00:00
|
|
|
$(Device/wpj-16m)
|
2017-03-28 19:09:37 +00:00
|
|
|
DEVICE_TITLE := Compex WPJ558 (16MB flash)
|
|
|
|
|
BOARDNAME := WPJ558
|
2017-08-02 15:08:32 +00:00
|
|
|
SUPPORTED_DEVICES := wpj558
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to $$$$(BLOCKSIZE) | \
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata | check-size $$$$(IMAGE_SIZE)
|
2017-03-28 19:09:37 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wpj558
|
2017-02-26 11:25:57 +00:00
|
|
|
|
|
|
|
|
define Device/wpj563
|
2017-05-30 21:20:16 +00:00
|
|
|
$(Device/wpj-16m)
|
2017-02-26 11:25:57 +00:00
|
|
|
DEVICE_TITLE := Compex WPJ563 (16MB flash)
|
|
|
|
|
BOARDNAME := WPJ563
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wpj563
|
2017-03-30 19:52:20 +00:00
|
|
|
|
2017-06-09 17:56:09 +00:00
|
|
|
define Device/wrtnode2q
|
|
|
|
|
DEVICE_TITLE := WRTnode2Q
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-storage
|
|
|
|
|
BOARDNAME := WRTNODE2Q
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
MTDPARTS := spi0.0:192k(u-boot)ro,64k(u-boot-env),64k(art)ro,16064k(firmware),16384k@0x0(fullflash)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wrtnode2q
|
|
|
|
|
|
2017-03-30 19:52:20 +00:00
|
|
|
define Device/zbt-we1526
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-WE1526
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := ZBT-WE1526
|
|
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
KERNEL_SIZE := 1472k
|
|
|
|
|
ROOTFS_SIZE := 14528k
|
|
|
|
|
MTDPARTS := spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,14528k(rootfs),1472k(kernel),64k(art)ro,16000k@0x50000(firmware)
|
2017-06-08 13:18:34 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | pad-rootfs | pad-to $$$$(ROOTFS_SIZE) | append-kernel | check-size $$$$(IMAGE_SIZE)
|
2017-03-30 19:52:20 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zbt-we1526
|
2016-12-30 10:53:21 +00:00
|
|
|
|
|
|
|
|
define Device/fritz300e
|
|
|
|
|
DEVICE_TITLE := AVM FRITZ!WLAN Repeater 300E
|
|
|
|
|
DEVICE_PACKAGES := fritz-tffs rssileds -swconfig -uboot-envtools
|
|
|
|
|
BOARDNAME := FRITZ300E
|
|
|
|
|
SUPPORTED_DEVICES := fritz300e
|
|
|
|
|
IMAGE_SIZE := 15232k
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | eva-image
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | pad-to 64k | \
|
|
|
|
|
append-squashfs-fakeroot-be | pad-to 256 | \
|
|
|
|
|
append-rootfs | pad-rootfs | append-metadata | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += fritz300e
|