2016-04-01 07:11:48 +00:00
|
|
|
#
|
|
|
|
|
# MT7620A Profiles
|
|
|
|
|
#
|
|
|
|
|
|
2018-01-20 08:27:03 +00:00
|
|
|
DEVICE_VARS += TPLINK_FLASHLAYOUT TPLINK_HWID TPLINK_HWREV TPLINK_HWREVADD TPLINK_HVERSION \
|
2018-04-19 17:36:55 +00:00
|
|
|
DLINK_ROM_ID DLINK_FAMILY_MEMBER DLINK_FIRMWARE_SIZE DLINK_IMAGE_OFFSET
|
2016-05-11 12:04:40 +00:00
|
|
|
|
|
|
|
|
define Build/elecom-header
|
|
|
|
|
cp $@ $(KDIR)/v_0.0.0.bin
|
2016-04-21 19:46:59 +00:00
|
|
|
( \
|
2016-12-25 15:40:05 +00:00
|
|
|
mkhash md5 $(KDIR)/v_0.0.0.bin && \
|
2016-04-21 19:46:59 +00:00
|
|
|
echo 458 \
|
2016-12-25 15:40:05 +00:00
|
|
|
) | mkhash md5 > $(KDIR)/v_0.0.0.md5
|
2017-11-03 01:45:45 +00:00
|
|
|
$(STAGING_DIR_HOST)/bin/tar -c \
|
|
|
|
|
$(if $(SOURCE_DATE_EPOCH),--mtime=@$(SOURCE_DATE_EPOCH)) \
|
|
|
|
|
-f $@ -C $(KDIR) v_0.0.0.bin v_0.0.0.md5
|
2016-04-21 19:46:59 +00:00
|
|
|
endef
|
|
|
|
|
|
2019-01-08 15:20:18 +00:00
|
|
|
define Build/elx-header
|
|
|
|
|
$(eval hw_id=$(word 1,$(1)))
|
|
|
|
|
$(eval xor_pattern=$(word 2,$(1)))
|
|
|
|
|
( \
|
|
|
|
|
echo -ne "\x00\x00\x00\x00\x00\x00\x00\x03" | \
|
|
|
|
|
dd bs=42 count=1 conv=sync; \
|
|
|
|
|
hw_id="$(hw_id)"; \
|
|
|
|
|
echo -ne "\x$${hw_id:0:2}\x$${hw_id:2:2}\x$${hw_id:4:2}\x$${hw_id:6:2}" | \
|
|
|
|
|
dd bs=20 count=1 conv=sync; \
|
|
|
|
|
echo -ne "$$(printf '%08x' $$(stat -c%s $@) | fold -s2 | xargs -I {} echo \\x{} | tr -d '\n')" | \
|
|
|
|
|
dd bs=8 count=1 conv=sync; \
|
|
|
|
|
echo -ne "$$($(STAGING_DIR_HOST)/bin/mkhash md5 $@ | fold -s2 | xargs -I {} echo \\x{} | tr -d '\n')" | \
|
|
|
|
|
dd bs=58 count=1 conv=sync; \
|
|
|
|
|
) > $(KDIR)/tmp/$(DEVICE_NAME).header
|
|
|
|
|
$(call Build/xor-image,-p $(xor_pattern) -x)
|
|
|
|
|
cat $(KDIR)/tmp/$(DEVICE_NAME).header $@ > $@.new
|
|
|
|
|
mv $@.new $@
|
|
|
|
|
endef
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/ai-br100
|
|
|
|
|
DTS := AI-BR100
|
|
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
DEVICE_TITLE := Aigale Ai-BR100
|
|
|
|
|
DEVICE_PACKAGES:= kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ai-br100
|
|
|
|
|
|
2017-10-14 08:44:39 +00:00
|
|
|
define Device/alfa-network_ac1200rm
|
|
|
|
|
DTS := AC1200RM
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_TITLE := ALFA Network AC1200RM
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci uboot-envtools
|
2017-10-14 08:44:39 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += alfa-network_ac1200rm
|
|
|
|
|
|
ramips: add support for ALFA Network R36M-E4G
ALFA Network R36M-E4G is a dual-SIM, N300 Wi-Fi, compact size platform
based on MediaTek MT7620A WiSoC. This product is designed for operation
with 4G modem (can be bought in bundle with Quectel EC25, EG25 or EP06)
but supports also Wi-Fi modules (miniPCIe slot has USB and PCIe buses).
Specification:
- MT7620A (580 MHz)
- 64/128/256 MB of RAM (DDR2)
- 16/32+ MB of FLASH (SPI NOR)
- 2x 10/100 Mbps Ethernet, with passive PoE support (24 V)
- 2T2R 2.4 GHz (MT7620A), with ext. LNA (RFFM4227)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses and optional 5 V)
- 2x SIM slot (mini, micro) with detect and switch driven by GPIO
- 2x u.fl antenna connectors (for Wi-Fi)
- 8x LED (7 driven by GPIO)
- 2x button (reset, wifi)
- 2x UART (4-pin/2.54 mm pitch, 10-pin/1.27 mm pitch) headers on PCB
- 1x I2C (4-pin, 1.27 mm pitch) header on PCB
- 1x LED (8-pin, 1.27 mm pitch) header on PCB
- 1x DC jack with lock (12 V)
Other:
- there is a dedicated, 4-pin connector for optional RTC module (Holtek
HT138x) with 'enable' input, not available at the time of preparing
support for this board
- miniPCIe slot supports additional 5 V supply on pins 47 and 49 but a
jumper resistor (R174) is not installed by default
- U-Boot selects default SIM slot, based on value of 'default_sim' env
variable: '1' or unset -> SIM1 (mini), '2' -> SIM2 (micro). This will
work only if both slots are occupied, otherwise U-Boot will always
select slot with SIM card inside (user can override it later, in
user-space)
- U-Boot resets the modem, using PERSTn signal, before starting kernel
- this board supports 'dual image' feature (controlled by 'dual_image'
U-Boot environment variable)
Flash instruction:
You can use the 'sysupgrade' image directly in vendor firmware which is
based on OpenWrt (make sure to not preserve settings - use 'sysupgrade
-n -F ...' command). Alternatively, use web recovery mode in U-Boot:
1. Power the device with reset button pressed, the modem LED will start
blinking slowly and after ~3 seconds, when it starts blinking faster,
you can release the button.
2. Setup static IP 192.168.1.2/24 on your PC.
3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
(backported from commit dfecf94c2059998411f95067de3866aa7cdf5ec9)
2019-10-29 23:10:40 +00:00
|
|
|
define Device/alfa-network_r36m-e4g
|
|
|
|
|
DTS := R36M-E4G
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_TITLE := ALFA Network R36M-E4G
|
|
|
|
|
DEVICE_PACKAGES := kmod-i2c-ralink kmod-usb2 kmod-usb-ohci uboot-envtools uqmi
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += alfa-network_r36m-e4g
|
|
|
|
|
|
ramips: add support for ALFA Network Tube-E4G
ALFA Network Tube-E4G is an outdoor, dual-SIM LTE Cat. 4 CPE, based on
MediaTek MT7620A, equipped with Quectel EC25 miniPCIe modem.
Specification:
- MT7620A (580 MHz)
- 64/128/256 MB of RAM (DDR2)
- 16/32 MB of flash (SPI NOR)
- 1x 10/100 Mbps Ethernet, with passive PoE support (24 V)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses)
- 2x SIM slot (mini, micro) with detect and switch driven by GPIO
- 1x detachable antenna (modem main)
- 1x internal antenna (modem div)
- 1x GPS passive antenna (optional)
- 5x LED (all driven by GPIO)
- 1x button (reset)
- UART (4-pin, 2.54 mm pitch) header on PCB
Other:
Default SIM slot is selected at an early stage by U-Boot, based on
'default_sim' environment value: 1 or unset = SIM1 (mini), 2 = SIM2
(micro). U-Boot also resets the modem, using #PERST signal, before
starting kernel.
Flash instruction:
You can use the 'sysupgrade' image directly in vendor firmware which is
based on OpenWrt (make sure to not preserve settings - use 'sysupgrade
-n -F ...' command). Alternatively, use web recovery mode in U-Boot:
1. Power the device with reset button pressed, the LAN LED will start
blinking slowly and after ~3 seconds, when it starts blinking faster,
you can release the button.
2. Setup static IP 192.168.1.2/24 on your PC.
3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-03-10 00:28:28 +00:00
|
|
|
define Device/alfa-network_tube-e4g
|
|
|
|
|
DTS := TUBE-E4G
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_TITLE := ALFA Network Tube-E4G
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci uboot-envtools uqmi \
|
2019-06-07 16:40:32 +00:00
|
|
|
-iwinfo -kmod-rt2800-soc -wpad-basic
|
ramips: add support for ALFA Network Tube-E4G
ALFA Network Tube-E4G is an outdoor, dual-SIM LTE Cat. 4 CPE, based on
MediaTek MT7620A, equipped with Quectel EC25 miniPCIe modem.
Specification:
- MT7620A (580 MHz)
- 64/128/256 MB of RAM (DDR2)
- 16/32 MB of flash (SPI NOR)
- 1x 10/100 Mbps Ethernet, with passive PoE support (24 V)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses)
- 2x SIM slot (mini, micro) with detect and switch driven by GPIO
- 1x detachable antenna (modem main)
- 1x internal antenna (modem div)
- 1x GPS passive antenna (optional)
- 5x LED (all driven by GPIO)
- 1x button (reset)
- UART (4-pin, 2.54 mm pitch) header on PCB
Other:
Default SIM slot is selected at an early stage by U-Boot, based on
'default_sim' environment value: 1 or unset = SIM1 (mini), 2 = SIM2
(micro). U-Boot also resets the modem, using #PERST signal, before
starting kernel.
Flash instruction:
You can use the 'sysupgrade' image directly in vendor firmware which is
based on OpenWrt (make sure to not preserve settings - use 'sysupgrade
-n -F ...' command). Alternatively, use web recovery mode in U-Boot:
1. Power the device with reset button pressed, the LAN LED will start
blinking slowly and after ~3 seconds, when it starts blinking faster,
you can release the button.
2. Setup static IP 192.168.1.2/24 on your PC.
3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-03-10 00:28:28 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += alfa-network_tube-e4g
|
|
|
|
|
|
2018-04-19 17:36:55 +00:00
|
|
|
define Device/amit_jboot
|
|
|
|
|
DLINK_IMAGE_OFFSET := 0x10000
|
|
|
|
|
KERNEL := $(KERNEL_DTB)
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := mkdlinkfw | pad-rootfs | append-metadata
|
|
|
|
|
IMAGE/factory.bin := mkdlinkfw | pad-rootfs | mkdlinkfw-factory
|
|
|
|
|
DEVICE_PACKAGES := jboot-tools kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
|
|
|
|
|
2017-06-23 21:20:53 +00:00
|
|
|
define Device/Archer
|
2017-10-03 10:46:09 +00:00
|
|
|
TPLINK_HWREVADD := 0
|
|
|
|
|
TPLINK_HVERSION := 3
|
2016-05-11 12:04:40 +00:00
|
|
|
KERNEL := $(KERNEL_DTB)
|
2017-10-03 10:46:09 +00:00
|
|
|
KERNEL_INITRAMFS := $(KERNEL_DTB) | tplink-v2-header -e
|
|
|
|
|
IMAGE/factory.bin := tplink-v2-image -e
|
|
|
|
|
IMAGE/sysupgrade.bin := tplink-v2-image -s -e | append-metadata
|
2017-06-23 21:20:53 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/ArcherC20i
|
|
|
|
|
$(Device/Archer)
|
|
|
|
|
DTS := ArcherC20i
|
|
|
|
|
SUPPORTED_DEVICES := c20i
|
2017-10-03 10:46:09 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0xc2000001
|
|
|
|
|
TPLINK_HWREV := 58
|
2017-05-05 15:07:28 +00:00
|
|
|
IMAGES += factory.bin
|
2018-11-25 13:35:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
2016-05-11 12:04:40 +00:00
|
|
|
DEVICE_TITLE := TP-Link ArcherC20i
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ArcherC20i
|
2016-04-01 07:11:48 +00:00
|
|
|
|
2017-07-28 11:00:54 +00:00
|
|
|
define Device/ArcherC50v1
|
2017-06-23 21:20:53 +00:00
|
|
|
$(Device/Archer)
|
2016-06-12 21:46:35 +00:00
|
|
|
DTS := ArcherC50
|
2016-12-01 06:37:03 +00:00
|
|
|
SUPPORTED_DEVICES := c50
|
2017-10-03 10:46:09 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0xc7500001
|
|
|
|
|
TPLINK_HWREV := 69
|
2017-07-28 11:00:54 +00:00
|
|
|
IMAGES += factory-us.bin factory-eu.bin
|
2017-10-03 10:46:09 +00:00
|
|
|
IMAGE/factory-us.bin := tplink-v2-image -e -w 0
|
|
|
|
|
IMAGE/factory-eu.bin := tplink-v2-image -e -w 2
|
2017-07-28 11:00:54 +00:00
|
|
|
DEVICE_TITLE := TP-Link ArcherC50v1
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci
|
2016-06-12 21:46:35 +00:00
|
|
|
endef
|
2017-07-28 11:00:54 +00:00
|
|
|
TARGET_DEVICES += ArcherC50v1
|
2016-06-12 21:46:35 +00:00
|
|
|
|
2016-09-24 19:41:43 +00:00
|
|
|
define Device/ArcherMR200
|
2017-06-23 21:20:53 +00:00
|
|
|
$(Device/Archer)
|
2016-09-24 19:41:43 +00:00
|
|
|
DTS := ArcherMR200
|
2016-12-23 17:04:16 +00:00
|
|
|
SUPPORTED_DEVICES := mr200
|
2017-10-03 10:46:09 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 8MLmtk
|
|
|
|
|
TPLINK_HWID := 0xd7500001
|
|
|
|
|
TPLINK_HWREV := 0x4a
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-net kmod-usb-net-rndis kmod-usb-serial kmod-usb-serial-option adb-enablemodem
|
2016-09-24 19:41:43 +00:00
|
|
|
DEVICE_TITLE := TP-Link ArcherMR200
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ArcherMR200
|
|
|
|
|
|
2018-11-26 12:26:06 +00:00
|
|
|
define Device/bdcom_wap2100-sk
|
ramips: Add support for ZTE ZXECS EBG3130 aka BDCOM WAP2100-SK
On the bottom sticker it's branded as ZTE ZXECS EBG3130 device, but in factory
OpenWrt image it's referenced as BDCOM WAP2100-SK device.
Specifications:
- SoC: MediaTek MT7620A
- RAM: 128 MB
- Flash: 16 MB
- Ethernet: 5 FE ports
- Wireless radio: 2T2R 2.4 GHz and 1T1R 5 GHz (MT7610EN, unsupported)
- UART: 1 x UART on PCB marked as J2 (R=RX, T=TX, G=GND) with 115200 8N1 config
- LEDs: Power, FE ports 1-5, WPS, USB, RF 2.4G, RF 5G
- Other: USB port, SD card slot and 2x external antennas (non-detachable)
Flashing instructions:
A) The U-Boot has HTTP based firmware upgrade
A1) Flashing notes
We've identified so far two different batches of units, unfortunately
each batch has different U-Boot bootloader flashed with different
default environment variables, thus each batch has different IP address
for accessing web based firmware updater.
* First batch has web based bootloader IP address 1.1.1.1
* Second batch has web based bootloader IP address 192.168.1.250
In case you can't connect to either of those IPs, you can try to get
the default IP address via two methods:
A1.1) Serial console, then the IP address is visible during the boot
...
HTTP server is starting at IP: 1.1.1.1
raspi_read: from:40004 len:6
HTTP server is ready!
...
A1.2) Over telnet/SSH using this command:
root@bdcom:/# grep ipaddr= /dev/mtd0
ipaddr=1.1.1.1
A2) Flashing with browser
* Change IP address of PC to 1.1.1.2 with 255.255.255.0 netmask
* Reboot the device and try to reach web based bootloader in the
browser with the following URL http://1.1.1.1
* Quickly select the firmware sysupgrade file and click on the
`Update firmware` button, this all has to be done within 10 seconds,
bootloader doesn't wait any longer
If done correctly, the web page should show UPDATE IN PROGRESS page
with progress indicator. Once the flashing completes (it takes roughly
around 1 minute), the device will reboot to the OpenWrt firmware
A3) Flashing with curl
sudo ip addr add 1.1.1.2/24 dev eth0
curl \
--verbose \
--retry 3 \
--retry-delay 1 \
--retry-max-time 30 \
--connect-timeout 30 \
--form "firmware=@openwrt-ramips-mt7620-BDCOM-WAP2100-SK-squashfs-sysupgrade.bin" \
http://1.1.1.1
Now power on the router.
B) The U-boot is based on Ralink SDK so we can flash the firmware using UART.
1. Configure PC with a static IP address and setup an TFTP server.
2. Put the firmware into the tftp directory.
3. Connect the UART line as described on the PCB (G=GND, R=RX, T=TX)
4. Power up the device and press 2, follow the instruction to set device and
tftp server IP address and input the firmware file name. U-boot will then load
the firmware and write it into the flash.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
2018-11-13 12:10:40 +00:00
|
|
|
DTS := BDCOM-WAP2100-SK
|
2018-11-26 12:26:06 +00:00
|
|
|
IMAGE_SIZE := 15808k
|
ramips: Add support for ZTE ZXECS EBG3130 aka BDCOM WAP2100-SK
On the bottom sticker it's branded as ZTE ZXECS EBG3130 device, but in factory
OpenWrt image it's referenced as BDCOM WAP2100-SK device.
Specifications:
- SoC: MediaTek MT7620A
- RAM: 128 MB
- Flash: 16 MB
- Ethernet: 5 FE ports
- Wireless radio: 2T2R 2.4 GHz and 1T1R 5 GHz (MT7610EN, unsupported)
- UART: 1 x UART on PCB marked as J2 (R=RX, T=TX, G=GND) with 115200 8N1 config
- LEDs: Power, FE ports 1-5, WPS, USB, RF 2.4G, RF 5G
- Other: USB port, SD card slot and 2x external antennas (non-detachable)
Flashing instructions:
A) The U-Boot has HTTP based firmware upgrade
A1) Flashing notes
We've identified so far two different batches of units, unfortunately
each batch has different U-Boot bootloader flashed with different
default environment variables, thus each batch has different IP address
for accessing web based firmware updater.
* First batch has web based bootloader IP address 1.1.1.1
* Second batch has web based bootloader IP address 192.168.1.250
In case you can't connect to either of those IPs, you can try to get
the default IP address via two methods:
A1.1) Serial console, then the IP address is visible during the boot
...
HTTP server is starting at IP: 1.1.1.1
raspi_read: from:40004 len:6
HTTP server is ready!
...
A1.2) Over telnet/SSH using this command:
root@bdcom:/# grep ipaddr= /dev/mtd0
ipaddr=1.1.1.1
A2) Flashing with browser
* Change IP address of PC to 1.1.1.2 with 255.255.255.0 netmask
* Reboot the device and try to reach web based bootloader in the
browser with the following URL http://1.1.1.1
* Quickly select the firmware sysupgrade file and click on the
`Update firmware` button, this all has to be done within 10 seconds,
bootloader doesn't wait any longer
If done correctly, the web page should show UPDATE IN PROGRESS page
with progress indicator. Once the flashing completes (it takes roughly
around 1 minute), the device will reboot to the OpenWrt firmware
A3) Flashing with curl
sudo ip addr add 1.1.1.2/24 dev eth0
curl \
--verbose \
--retry 3 \
--retry-delay 1 \
--retry-max-time 30 \
--connect-timeout 30 \
--form "firmware=@openwrt-ramips-mt7620-BDCOM-WAP2100-SK-squashfs-sysupgrade.bin" \
http://1.1.1.1
Now power on the router.
B) The U-boot is based on Ralink SDK so we can flash the firmware using UART.
1. Configure PC with a static IP address and setup an TFTP server.
2. Put the firmware into the tftp directory.
3. Connect the UART line as described on the PCB (G=GND, R=RX, T=TX)
4. Power up the device and press 2, follow the instruction to set device and
tftp server IP address and input the firmware file name. U-boot will then load
the firmware and write it into the flash.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
2018-11-13 12:10:40 +00:00
|
|
|
DEVICE_TITLE := BDCOM WAP2100-SK (ZTE ZXECS EBG3130)
|
2018-11-28 20:53:02 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-mt76x2 kmod-mt76x0e kmod-sdhci-mt7620 kmod-usb-ledtrig-usbport
|
ramips: Add support for ZTE ZXECS EBG3130 aka BDCOM WAP2100-SK
On the bottom sticker it's branded as ZTE ZXECS EBG3130 device, but in factory
OpenWrt image it's referenced as BDCOM WAP2100-SK device.
Specifications:
- SoC: MediaTek MT7620A
- RAM: 128 MB
- Flash: 16 MB
- Ethernet: 5 FE ports
- Wireless radio: 2T2R 2.4 GHz and 1T1R 5 GHz (MT7610EN, unsupported)
- UART: 1 x UART on PCB marked as J2 (R=RX, T=TX, G=GND) with 115200 8N1 config
- LEDs: Power, FE ports 1-5, WPS, USB, RF 2.4G, RF 5G
- Other: USB port, SD card slot and 2x external antennas (non-detachable)
Flashing instructions:
A) The U-Boot has HTTP based firmware upgrade
A1) Flashing notes
We've identified so far two different batches of units, unfortunately
each batch has different U-Boot bootloader flashed with different
default environment variables, thus each batch has different IP address
for accessing web based firmware updater.
* First batch has web based bootloader IP address 1.1.1.1
* Second batch has web based bootloader IP address 192.168.1.250
In case you can't connect to either of those IPs, you can try to get
the default IP address via two methods:
A1.1) Serial console, then the IP address is visible during the boot
...
HTTP server is starting at IP: 1.1.1.1
raspi_read: from:40004 len:6
HTTP server is ready!
...
A1.2) Over telnet/SSH using this command:
root@bdcom:/# grep ipaddr= /dev/mtd0
ipaddr=1.1.1.1
A2) Flashing with browser
* Change IP address of PC to 1.1.1.2 with 255.255.255.0 netmask
* Reboot the device and try to reach web based bootloader in the
browser with the following URL http://1.1.1.1
* Quickly select the firmware sysupgrade file and click on the
`Update firmware` button, this all has to be done within 10 seconds,
bootloader doesn't wait any longer
If done correctly, the web page should show UPDATE IN PROGRESS page
with progress indicator. Once the flashing completes (it takes roughly
around 1 minute), the device will reboot to the OpenWrt firmware
A3) Flashing with curl
sudo ip addr add 1.1.1.2/24 dev eth0
curl \
--verbose \
--retry 3 \
--retry-delay 1 \
--retry-max-time 30 \
--connect-timeout 30 \
--form "firmware=@openwrt-ramips-mt7620-BDCOM-WAP2100-SK-squashfs-sysupgrade.bin" \
http://1.1.1.1
Now power on the router.
B) The U-boot is based on Ralink SDK so we can flash the firmware using UART.
1. Configure PC with a static IP address and setup an TFTP server.
2. Put the firmware into the tftp directory.
3. Connect the UART line as described on the PCB (G=GND, R=RX, T=TX)
4. Power up the device and press 2, follow the instruction to set device and
tftp server IP address and input the firmware file name. U-boot will then load
the firmware and write it into the flash.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
2018-11-13 12:10:40 +00:00
|
|
|
endef
|
2018-11-26 12:26:06 +00:00
|
|
|
TARGET_DEVICES += bdcom_wap2100-sk
|
ramips: Add support for ZTE ZXECS EBG3130 aka BDCOM WAP2100-SK
On the bottom sticker it's branded as ZTE ZXECS EBG3130 device, but in factory
OpenWrt image it's referenced as BDCOM WAP2100-SK device.
Specifications:
- SoC: MediaTek MT7620A
- RAM: 128 MB
- Flash: 16 MB
- Ethernet: 5 FE ports
- Wireless radio: 2T2R 2.4 GHz and 1T1R 5 GHz (MT7610EN, unsupported)
- UART: 1 x UART on PCB marked as J2 (R=RX, T=TX, G=GND) with 115200 8N1 config
- LEDs: Power, FE ports 1-5, WPS, USB, RF 2.4G, RF 5G
- Other: USB port, SD card slot and 2x external antennas (non-detachable)
Flashing instructions:
A) The U-Boot has HTTP based firmware upgrade
A1) Flashing notes
We've identified so far two different batches of units, unfortunately
each batch has different U-Boot bootloader flashed with different
default environment variables, thus each batch has different IP address
for accessing web based firmware updater.
* First batch has web based bootloader IP address 1.1.1.1
* Second batch has web based bootloader IP address 192.168.1.250
In case you can't connect to either of those IPs, you can try to get
the default IP address via two methods:
A1.1) Serial console, then the IP address is visible during the boot
...
HTTP server is starting at IP: 1.1.1.1
raspi_read: from:40004 len:6
HTTP server is ready!
...
A1.2) Over telnet/SSH using this command:
root@bdcom:/# grep ipaddr= /dev/mtd0
ipaddr=1.1.1.1
A2) Flashing with browser
* Change IP address of PC to 1.1.1.2 with 255.255.255.0 netmask
* Reboot the device and try to reach web based bootloader in the
browser with the following URL http://1.1.1.1
* Quickly select the firmware sysupgrade file and click on the
`Update firmware` button, this all has to be done within 10 seconds,
bootloader doesn't wait any longer
If done correctly, the web page should show UPDATE IN PROGRESS page
with progress indicator. Once the flashing completes (it takes roughly
around 1 minute), the device will reboot to the OpenWrt firmware
A3) Flashing with curl
sudo ip addr add 1.1.1.2/24 dev eth0
curl \
--verbose \
--retry 3 \
--retry-delay 1 \
--retry-max-time 30 \
--connect-timeout 30 \
--form "firmware=@openwrt-ramips-mt7620-BDCOM-WAP2100-SK-squashfs-sysupgrade.bin" \
http://1.1.1.1
Now power on the router.
B) The U-boot is based on Ralink SDK so we can flash the firmware using UART.
1. Configure PC with a static IP address and setup an TFTP server.
2. Put the firmware into the tftp directory.
3. Connect the UART line as described on the PCB (G=GND, R=RX, T=TX)
4. Power up the device and press 2, follow the instruction to set device and
tftp server IP address and input the firmware file name. U-boot will then load
the firmware and write it into the flash.
Signed-off-by: Petr Štetiar <ynezz@true.cz>
2018-11-13 12:10:40 +00:00
|
|
|
|
2018-02-22 16:58:23 +00:00
|
|
|
define Device/bocco
|
|
|
|
|
DTS := BOCCO
|
|
|
|
|
DEVICE_TITLE := YUKAI Engineering BOCCO
|
|
|
|
|
DEVICE_PACKAGES := kmod-sound-core kmod-sound-mt7620 kmod-i2c-ralink
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += bocco
|
|
|
|
|
|
2017-09-06 09:14:16 +00:00
|
|
|
define Device/c108
|
|
|
|
|
DTS := C108
|
|
|
|
|
IMAGE_SIZE := 16777216
|
|
|
|
|
DEVICE_TITLE := HNET C108
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += c108
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/cf-wr800n
|
|
|
|
|
DTS := CF-WR800N
|
|
|
|
|
DEVICE_TITLE := Comfast CF-WR800N
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cf-wr800n
|
|
|
|
|
|
|
|
|
|
define Device/cs-qr10
|
|
|
|
|
DTS := CS-QR10
|
|
|
|
|
DEVICE_TITLE := Planex CS-QR10
|
2017-11-18 11:19:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci \
|
|
|
|
|
kmod-sound-core kmod-sound-mt7620 \
|
|
|
|
|
kmod-i2c-ralink kmod-sdhci-mt7620
|
2017-03-11 23:07:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cs-qr10
|
|
|
|
|
|
|
|
|
|
define Device/d240
|
|
|
|
|
DTS := D240
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := Sanlinking Technologies D240
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620
|
2017-03-11 23:07:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += d240
|
|
|
|
|
|
|
|
|
|
define Device/db-wrt01
|
|
|
|
|
DTS := DB-WRT01
|
|
|
|
|
DEVICE_TITLE := Planex DB-WRT01
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += db-wrt01
|
|
|
|
|
|
|
|
|
|
define Device/dch-m225
|
2018-12-29 18:25:00 +00:00
|
|
|
$(Device/seama)
|
2017-03-11 23:07:19 +00:00
|
|
|
DTS := DCH-M225
|
|
|
|
|
BLOCKSIZE := 4k
|
2018-12-29 18:25:00 +00:00
|
|
|
SEAMA_SIGNATURE := wapn22_dlink.2013gui_dap1320b
|
2017-03-11 23:07:19 +00:00
|
|
|
IMAGE_SIZE := 6848k
|
|
|
|
|
DEVICE_TITLE := D-Link DCH-M225
|
2018-11-30 11:25:39 +00:00
|
|
|
DEVICE_PACKAGES := kmod-sound-core kmod-sound-mt7620 kmod-i2c-ralink
|
2017-03-11 23:07:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dch-m225
|
|
|
|
|
|
|
|
|
|
define Device/dir-810l
|
|
|
|
|
DTS := DIR-810L
|
2018-10-24 16:07:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
2017-03-11 23:07:19 +00:00
|
|
|
DEVICE_TITLE := D-Link DIR-810L
|
2018-10-24 16:07:43 +00:00
|
|
|
IMAGE_SIZE := 6720k
|
2017-03-11 23:07:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dir-810l
|
|
|
|
|
|
2018-03-19 18:15:29 +00:00
|
|
|
define Device/dlink_dir-510l
|
|
|
|
|
$(Device/amit_jboot)
|
|
|
|
|
DTS := DIR-510L
|
|
|
|
|
DEVICE_TITLE := D-Link DIR-510L
|
|
|
|
|
DEVICE_PACKAGES += kmod-mt76x0e
|
|
|
|
|
DLINK_ROM_ID := DLK6E3805001
|
|
|
|
|
DLINK_FAMILY_MEMBER := 0x6E38
|
|
|
|
|
DLINK_FIRMWARE_SIZE := 0xDE0000
|
|
|
|
|
DLINK_IMAGE_OFFSET := 0x210000
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-510l
|
|
|
|
|
|
2018-01-20 08:27:03 +00:00
|
|
|
define Device/dlink_dwr-116-a1
|
2018-04-19 17:36:55 +00:00
|
|
|
$(Device/amit_jboot)
|
2018-01-20 08:27:03 +00:00
|
|
|
DTS := DWR-116-A1
|
|
|
|
|
DEVICE_TITLE := D-Link DWR-116 A1/A2
|
|
|
|
|
DLINK_ROM_ID := DLK6E3803001
|
|
|
|
|
DLINK_FAMILY_MEMBER := 0x6E38
|
|
|
|
|
DLINK_FIRMWARE_SIZE := 0x7E0000
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dwr-116-a1
|
|
|
|
|
|
2018-10-24 12:06:35 +00:00
|
|
|
define Device/dlink_dwr-118-a1
|
2018-04-19 17:36:55 +00:00
|
|
|
$(Device/amit_jboot)
|
2018-10-24 12:06:35 +00:00
|
|
|
DTS := DWR-118-A1
|
|
|
|
|
DEVICE_TITLE := D-Link DWR-118 A1
|
2018-04-19 17:36:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-mt76x0e
|
2018-10-24 12:06:35 +00:00
|
|
|
DLINK_ROM_ID := DLK6E3811001
|
|
|
|
|
DLINK_FAMILY_MEMBER := 0x6E38
|
|
|
|
|
DLINK_FIRMWARE_SIZE := 0xFE0000
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dwr-118-a1
|
|
|
|
|
|
2018-04-19 17:34:22 +00:00
|
|
|
define Device/dlink_dwr-118-a2
|
2018-04-19 17:36:55 +00:00
|
|
|
$(Device/amit_jboot)
|
2018-04-19 17:34:22 +00:00
|
|
|
DTS := DWR-118-A2
|
|
|
|
|
DEVICE_TITLE := D-Link DWR-118 A2
|
2018-04-19 17:36:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-mt76x2
|
2018-04-19 17:34:22 +00:00
|
|
|
DLINK_ROM_ID := DLK6E3814001
|
|
|
|
|
DLINK_FAMILY_MEMBER := 0x6E38
|
|
|
|
|
DLINK_FIRMWARE_SIZE := 0xFE0000
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dwr-118-a2
|
|
|
|
|
|
2018-03-10 09:34:38 +00:00
|
|
|
define Device/dlink_dwr-921-c1
|
2018-04-19 17:36:55 +00:00
|
|
|
$(Device/amit_jboot)
|
2018-03-10 09:34:38 +00:00
|
|
|
DTS := DWR-921-C1
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := D-Link DWR-921 C1
|
|
|
|
|
DLINK_ROM_ID := DLK6E2414001
|
|
|
|
|
DLINK_FAMILY_MEMBER := 0x6E24
|
|
|
|
|
DLINK_FIRMWARE_SIZE := 0xFE0000
|
2018-04-19 17:36:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-usb-net-qmi-wwan kmod-usb-serial-option uqmi
|
2018-03-10 09:34:38 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dwr-921-c1
|
|
|
|
|
|
2018-03-22 20:47:17 +00:00
|
|
|
define Device/dlink_dwr-921-c3
|
|
|
|
|
$(Device/dlink_dwr-921-c1)
|
|
|
|
|
DEVICE_TITLE := D-Link DWR-921 C3
|
|
|
|
|
DLINK_ROM_ID := DLK6E2414009
|
|
|
|
|
SUPPORTED_DEVICES := dlink,dwr-921-c1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dwr-921-c3
|
|
|
|
|
|
ramips: add support for DLINK DWR-922-E2
Very similar to the DWR-921-C1, except has a telephony/RJ11 port (not
sure if supported, I didn't try), wireless router with QMI LTE embedded
modem is based on the MT7620N SoC.
Specification:
* MediaTek MT7620N (580 Mhz)
* 64 MB of RAM
* 16 MB of FLASH
* 802.11bgn radio
* 5x 10/100 Mbps Ethernet (1 WAN and 4 LAN)
* 2x external, detachable (LTE) antennas
* UART header on PCB (57600 8n1)
* 6x LED (GPIO-controlled)
* 1x bi-color Signal Strength LED (GPIO-controlled)
* 2x button
* JBOOT bootloader
The status led has been assigned to the dwr-922-e2:green:signalstrength
(lte signal strength) led. At the end of the boot it is switched off and
is available for lte operation. Works correctly also during sysupgrade
operation.
Installation:
Apply factory image via d-link http web-gui, or via recovery interface:
How to recover/revert to OEM firmware:
1.) Push and hold the reset button and turn on the power. Wait until all
LEDs start rapidly blinking (~10sec.)
2.) DHCP should give you an IP in the 192.168.123.0/24 subnet, or set
one manually
3.) Upload original factory image via JBOOT http interface at IP
192.168.123.254
4.) If http doesn't work, it can be done with curl command:
curl -F FN=@XXXXX.bin http://192.168.123.254/upg
where XXXXX.bin is name of firmware file.
5.) You can optionally telnet to 192.168.123.254 before or during the
upload and it will report the flashing status, memory address etc.
6.) Once web UI and/or telnet says "Success", power cycle the router, or
type "reboot" into the telnet session.
Signed-off-by: Simon Quigley <squigley@squigley.net>
[squashed commits, word wrap commit message, rename signal strenght led
name to match what is used for the DWR-921-C1 since they share the led
configuration, add label referenced in the aliases node]
Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-20 16:47:52 +00:00
|
|
|
define Device/dlink_dwr-922-e2
|
2018-04-19 17:36:55 +00:00
|
|
|
$(Device/amit_jboot)
|
ramips: add support for DLINK DWR-922-E2
Very similar to the DWR-921-C1, except has a telephony/RJ11 port (not
sure if supported, I didn't try), wireless router with QMI LTE embedded
modem is based on the MT7620N SoC.
Specification:
* MediaTek MT7620N (580 Mhz)
* 64 MB of RAM
* 16 MB of FLASH
* 802.11bgn radio
* 5x 10/100 Mbps Ethernet (1 WAN and 4 LAN)
* 2x external, detachable (LTE) antennas
* UART header on PCB (57600 8n1)
* 6x LED (GPIO-controlled)
* 1x bi-color Signal Strength LED (GPIO-controlled)
* 2x button
* JBOOT bootloader
The status led has been assigned to the dwr-922-e2:green:signalstrength
(lte signal strength) led. At the end of the boot it is switched off and
is available for lte operation. Works correctly also during sysupgrade
operation.
Installation:
Apply factory image via d-link http web-gui, or via recovery interface:
How to recover/revert to OEM firmware:
1.) Push and hold the reset button and turn on the power. Wait until all
LEDs start rapidly blinking (~10sec.)
2.) DHCP should give you an IP in the 192.168.123.0/24 subnet, or set
one manually
3.) Upload original factory image via JBOOT http interface at IP
192.168.123.254
4.) If http doesn't work, it can be done with curl command:
curl -F FN=@XXXXX.bin http://192.168.123.254/upg
where XXXXX.bin is name of firmware file.
5.) You can optionally telnet to 192.168.123.254 before or during the
upload and it will report the flashing status, memory address etc.
6.) Once web UI and/or telnet says "Success", power cycle the router, or
type "reboot" into the telnet session.
Signed-off-by: Simon Quigley <squigley@squigley.net>
[squashed commits, word wrap commit message, rename signal strenght led
name to match what is used for the DWR-921-C1 since they share the led
configuration, add label referenced in the aliases node]
Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-20 16:47:52 +00:00
|
|
|
DTS := DWR-922-E2
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := D-Link DWR-922 E2
|
|
|
|
|
DLINK_ROM_ID := DLK6E2414005
|
|
|
|
|
DLINK_FAMILY_MEMBER := 0x6E24
|
|
|
|
|
DLINK_FIRMWARE_SIZE := 0xFE0000
|
2018-04-19 17:36:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-usb-net-qmi-wwan kmod-usb-serial-option uqmi
|
ramips: add support for DLINK DWR-922-E2
Very similar to the DWR-921-C1, except has a telephony/RJ11 port (not
sure if supported, I didn't try), wireless router with QMI LTE embedded
modem is based on the MT7620N SoC.
Specification:
* MediaTek MT7620N (580 Mhz)
* 64 MB of RAM
* 16 MB of FLASH
* 802.11bgn radio
* 5x 10/100 Mbps Ethernet (1 WAN and 4 LAN)
* 2x external, detachable (LTE) antennas
* UART header on PCB (57600 8n1)
* 6x LED (GPIO-controlled)
* 1x bi-color Signal Strength LED (GPIO-controlled)
* 2x button
* JBOOT bootloader
The status led has been assigned to the dwr-922-e2:green:signalstrength
(lte signal strength) led. At the end of the boot it is switched off and
is available for lte operation. Works correctly also during sysupgrade
operation.
Installation:
Apply factory image via d-link http web-gui, or via recovery interface:
How to recover/revert to OEM firmware:
1.) Push and hold the reset button and turn on the power. Wait until all
LEDs start rapidly blinking (~10sec.)
2.) DHCP should give you an IP in the 192.168.123.0/24 subnet, or set
one manually
3.) Upload original factory image via JBOOT http interface at IP
192.168.123.254
4.) If http doesn't work, it can be done with curl command:
curl -F FN=@XXXXX.bin http://192.168.123.254/upg
where XXXXX.bin is name of firmware file.
5.) You can optionally telnet to 192.168.123.254 before or during the
upload and it will report the flashing status, memory address etc.
6.) Once web UI and/or telnet says "Success", power cycle the router, or
type "reboot" into the telnet session.
Signed-off-by: Simon Quigley <squigley@squigley.net>
[squashed commits, word wrap commit message, rename signal strenght led
name to match what is used for the DWR-921-C1 since they share the led
configuration, add label referenced in the aliases node]
Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-20 16:47:52 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dwr-922-e2
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/e1700
|
|
|
|
|
DTS := E1700
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
umedia-header 0x013326
|
|
|
|
|
DEVICE_TITLE := Linksys E1700
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += e1700
|
|
|
|
|
|
2016-05-11 12:04:40 +00:00
|
|
|
define Device/ex2700
|
2017-01-23 13:41:15 +00:00
|
|
|
NETGEAR_HW_ID := 29764623+4+0+32+2x2+0
|
|
|
|
|
NETGEAR_BOARD_ID := EX2700
|
2016-05-11 12:04:40 +00:00
|
|
|
DTS := EX2700
|
2016-09-03 07:56:35 +00:00
|
|
|
BLOCKSIZE := 4k
|
2016-09-04 07:58:02 +00:00
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_4M)
|
2016-05-11 12:04:40 +00:00
|
|
|
IMAGES += factory.bin
|
2018-04-20 04:30:46 +00:00
|
|
|
KERNEL := $(KERNEL_DTB) | uImage lzma | pad-offset 64k 64 | append-uImage-fakehdr filesystem
|
2016-11-26 09:43:34 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | \
|
2017-01-23 13:41:15 +00:00
|
|
|
netgear-dni
|
2016-05-11 12:04:40 +00:00
|
|
|
DEVICE_TITLE := Netgear EX2700
|
|
|
|
|
endef
|
2019-07-20 21:40:20 +00:00
|
|
|
#TARGET_DEVICES += ex2700
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-07-30 10:17:44 +00:00
|
|
|
define Device/ex3700-ex3800
|
2017-03-03 14:36:51 +00:00
|
|
|
NETGEAR_BOARD_ID := U12H319T00_NETGEAR
|
|
|
|
|
DTS := EX3700
|
|
|
|
|
BLOCKSIZE := 4k
|
|
|
|
|
IMAGE_SIZE := 7744k
|
2017-07-30 10:02:55 +00:00
|
|
|
IMAGES += factory.chk
|
|
|
|
|
IMAGE/factory.chk := $$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | netgear-chk
|
2018-12-04 19:40:27 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2017-07-30 10:17:44 +00:00
|
|
|
DEVICE_TITLE := Netgear EX3700/EX3800
|
|
|
|
|
SUPPORTED_DEVICES := ex3700
|
2017-03-03 14:36:51 +00:00
|
|
|
endef
|
2017-07-30 10:17:44 +00:00
|
|
|
TARGET_DEVICES += ex3700-ex3800
|
2017-03-03 14:36:51 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/gl-mt300a
|
|
|
|
|
DTS := GL-MT300A
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := GL-Inet GL-MT300A
|
2018-11-30 11:25:39 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += gl-mt300a
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-02-19 08:46:44 +00:00
|
|
|
define Device/u25awf-h1
|
|
|
|
|
DTS := U25AWF-H1
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_TITLE := Kimax U25AWF-H1
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2017-02-19 08:46:44 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += u25awf-h1
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/gl-mt300n
|
|
|
|
|
DTS := GL-MT300N
|
2016-05-11 12:04:40 +00:00
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
2017-03-11 23:07:19 +00:00
|
|
|
DEVICE_TITLE := GL-Inet GL-MT300N
|
2018-11-30 11:25:39 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += gl-mt300n
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/gl-mt750
|
|
|
|
|
DTS := GL-MT750
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := GL-Inet GL-MT750
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += gl-mt750
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/hc5661
|
|
|
|
|
DTS := HC5661
|
2018-12-14 10:15:52 +00:00
|
|
|
IMAGE_SIZE := 15872k
|
2017-03-11 23:07:19 +00:00
|
|
|
DEVICE_TITLE := HiWiFi HC5661
|
2018-12-14 10:15:52 +00:00
|
|
|
DEVICE_PACKAGES := kmod-sdhci-mt7620
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += hc5661
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/hc5761
|
|
|
|
|
DTS := HC5761
|
2018-12-14 10:15:52 +00:00
|
|
|
IMAGE_SIZE := 15872k
|
2017-03-11 23:07:19 +00:00
|
|
|
DEVICE_TITLE := HiWiFi HC5761
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620 kmod-usb-ledtrig-usbport
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += hc5761
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/hc5861
|
|
|
|
|
DTS := HC5861
|
2018-12-14 10:15:52 +00:00
|
|
|
IMAGE_SIZE := 15872k
|
2017-03-11 23:07:19 +00:00
|
|
|
DEVICE_TITLE := HiWiFi HC5861
|
2018-12-14 10:15:52 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620 kmod-usb-ledtrig-usbport
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += hc5861
|
2016-05-11 12:04:40 +00:00
|
|
|
|
ramips: Add support for Head Weblink HDRM200
Head Weblink HDRM200 is a dual-sim router based on MT7620A. The detailed
specifications are:
- MT7620A (580MHz)
- 64MB RAM
- 16MB of flash (SPI NOR)
- 6x 10/100Mbps Ethernet (MT7620A built-in switch)
- 1x microSD slot
- 1x miniPCIe slot (only USB2.0 bus). Device is shipped with a SIMCOM
SIM7100E LTE modem.
- 2x SIM slots (standard size)
- 1x USB2.0 port
- 1x 2.4GHz wifi (rt2800)
- 1x 5GHz wifi (mt7612)
- 1x reset button
- 1x WPS button
- 3x GPIO-controllable LEDs
- 1x 10 pin terminal block (RS232, RS485, 4 x GPIO)
Tested:
- Ethernet switch
- Wifi
- USB slot
- SD card slot
- miniPCIe-slot
- sysupgrade
- reset button
Installation instructions:
Installing OpenWRT for the first time requires a bit of work, as the
board does not ship with OpenWRT. In addition, the bootloader
automatically reboots when installing an image over tftp. In order to
install OpenWRT on the HDRM200, you need to do the following:
* Copy the initramfs-image to your tftp-root (default filename is
test.bin) and configure networking accordingly (default server IP is
10.10.10.3, client 10.10.10.123). Start your tftp server.
* Open the board and connect to UART. The pins are exposed and clearly
marked.
* Boot the board and press 1.
* Either use the default filename and client/server IP-addresses, or
specify your own.
The image should now be loaded to memory and board boot. If the router
reboots while the image is loading, you need to try again. Once the
board has booted, copy the sysupgrade-image to the router and run
sysupgrade in order to install OpenWRT to the flash.
Notes:
- You control which SIM slot to use by writing 0/1 to
/sys/class/gpio/gpio0/value. In order for the change to take
effect, you can either use AT-commands (AT+CFUN) or power-cycle the
modem (write 0/1 to /sys/class/gpio/gpio21/value).
- RS485 is available on /dev/ttyS0.
- RS232 is available on /dev/ttyS1.
- The name of the ioX-gpios map to the labels on the casing.
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
[fixed whitespace issue and merge conflict in target.mk]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
2019-05-15 18:50:45 +00:00
|
|
|
define Device/head-weblink_hdrm200
|
|
|
|
|
DTS := HDRM200
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_TITLE := Head Weblink HDRM2000
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620 \
|
|
|
|
|
uqmi kmod-usb-serial kmod-usb-serial-option
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += head-weblink_hdrm200
|
|
|
|
|
|
2019-01-08 15:20:18 +00:00
|
|
|
define Device/iodata_wn-ac1167gr
|
|
|
|
|
DTS := WN-AC1167GR
|
|
|
|
|
DEVICE_TITLE := I-O DATA WN-AC1167GR
|
|
|
|
|
IMAGE_SIZE := 6864k
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := \
|
|
|
|
|
$$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
elx-header 01040016 8844A2D168B45A2D
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-ac1167gr
|
|
|
|
|
|
2019-03-14 14:46:43 +00:00
|
|
|
define Device/iodata_wn-ac733gr3
|
|
|
|
|
DTS := WN-AC733GR3
|
|
|
|
|
DEVICE_TITLE := I-O DATA WN-AC733GR3
|
|
|
|
|
IMAGE_SIZE := 6992k
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := \
|
|
|
|
|
$$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
elx-header 01040006 8844A2D168B45A2D
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-switch-rtl8367b
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-ac733gr3
|
|
|
|
|
|
2018-07-04 01:29:36 +00:00
|
|
|
define Device/kimax_u35wf
|
|
|
|
|
DTS := U35WF
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_TITLE := Kimax U35WF
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2018-07-04 01:29:36 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += kimax_u35wf
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/kng_rc
|
|
|
|
|
DTS := kng_rc
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := ZyXEL Keenetic Viva
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport kmod-switch-rtl8366-smi kmod-switch-rtl8367b
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | pad-to 64k | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
zyimage -d 8997 -v "ZyXEL Keenetic Viva"
|
2017-12-16 23:30:21 +00:00
|
|
|
SUPPORTED_DEVICES := kng_rc
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += kng_rc
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/kn_rc
|
|
|
|
|
DTS := kn_rc
|
|
|
|
|
DEVICE_TITLE := ZyXEL Keenetic Omni
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := $$(IMAGE/sysupgrade.bin) | pad-to 64k | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
zyimage -d 4882 -v "ZyXEL Keenetic Omni"
|
2017-12-16 23:30:21 +00:00
|
|
|
SUPPORTED_DEVICES := kn_rc
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += kn_rc
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/kn_rf
|
|
|
|
|
DTS := kn_rf
|
|
|
|
|
DEVICE_TITLE := ZyXEL Keenetic Omni II
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := $$(IMAGE/sysupgrade.bin) | pad-to 64k | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
zyimage -d 2102034 -v "ZyXEL Keenetic Omni II"
|
2017-12-16 23:30:21 +00:00
|
|
|
SUPPORTED_DEVICES := kn_rf
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += kn_rf
|
2016-05-11 12:04:40 +00:00
|
|
|
|
|
|
|
|
define Device/microwrt
|
|
|
|
|
DTS := MicroWRT
|
2016-09-04 07:58:02 +00:00
|
|
|
IMAGE_SIZE := 16128k
|
2016-05-11 12:04:40 +00:00
|
|
|
DEVICE_TITLE := Microduino MicroWRT
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += microwrt
|
|
|
|
|
|
2018-11-17 08:47:40 +00:00
|
|
|
define Device/lava_lr-25g001
|
2018-04-19 17:36:55 +00:00
|
|
|
$(Device/amit_jboot)
|
2018-11-17 08:47:40 +00:00
|
|
|
DTS := LR-25G001
|
|
|
|
|
DEVICE_TITLE := LAVA LR-25G001
|
|
|
|
|
DLINK_ROM_ID := LVA6E3804001
|
|
|
|
|
DLINK_FAMILY_MEMBER := 0x6E38
|
|
|
|
|
DLINK_FIRMWARE_SIZE := 0xFE0000
|
2018-04-19 17:36:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-mt76x0e
|
2018-11-17 08:47:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += lava_lr-25g001
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/miwifi-mini
|
|
|
|
|
DTS := MIWIFI-MINI
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := Xiaomi MiWiFi Mini
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci
|
2017-03-11 23:07:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += miwifi-mini
|
|
|
|
|
|
|
|
|
|
define Device/mlw221
|
|
|
|
|
DTS := MLW221
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := Kingston MLW221
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci
|
2017-03-11 23:07:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mlw221
|
|
|
|
|
|
|
|
|
|
define Device/mlwg2
|
|
|
|
|
DTS := MLWG2
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := Kingston MLWG2
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci
|
2017-03-11 23:07:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mlwg2
|
|
|
|
|
|
2016-05-11 12:04:40 +00:00
|
|
|
define Device/mt7620a
|
|
|
|
|
DTS := MT7620a
|
|
|
|
|
DEVICE_TITLE := MediaTek MT7620a EVB
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mt7620a
|
|
|
|
|
|
|
|
|
|
define Device/mt7620a_mt7530
|
|
|
|
|
DTS := MT7620a_MT7530
|
|
|
|
|
DEVICE_TITLE := MediaTek MT7620a + MT7530 EVB
|
2017-12-16 23:30:21 +00:00
|
|
|
SUPPORTED_DEVICES := mt7620a_mt7530
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mt7620a_mt7530
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/mt7620a_mt7610e
|
|
|
|
|
DTS := MT7620a_MT7610e
|
|
|
|
|
DEVICE_TITLE := MediaTek MT7620a + MT7610e EVB
|
2019-01-09 12:54:34 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
2017-12-16 23:30:21 +00:00
|
|
|
SUPPORTED_DEVICES := mt7620a_mt7610e
|
2017-03-11 23:07:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mt7620a_mt7610e
|
|
|
|
|
|
2016-05-11 12:04:40 +00:00
|
|
|
define Device/mt7620a_v22sg
|
|
|
|
|
DTS := MT7620a_V22SG
|
|
|
|
|
DEVICE_TITLE := MediaTek MT7620a V22SG
|
2017-12-16 23:30:21 +00:00
|
|
|
SUPPORTED_DEVICES := mt7620a_v22sg
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mt7620a_v22sg
|
|
|
|
|
|
|
|
|
|
define Device/mzk-750dhp
|
|
|
|
|
DTS := MZK-750DHP
|
|
|
|
|
DEVICE_TITLE := Planex MZK-750DHP
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mzk-750dhp
|
|
|
|
|
|
|
|
|
|
define Device/mzk-ex300np
|
|
|
|
|
DTS := MZK-EX300NP
|
|
|
|
|
DEVICE_TITLE := Planex MZK-EX300NP
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mzk-ex300np
|
|
|
|
|
|
|
|
|
|
define Device/mzk-ex750np
|
|
|
|
|
DTS := MZK-EX750NP
|
|
|
|
|
DEVICE_TITLE := Planex MZK-EX750NP
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mzk-ex750np
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/na930
|
|
|
|
|
DTS := NA930
|
|
|
|
|
IMAGE_SIZE := 20m
|
|
|
|
|
DEVICE_TITLE := Sercomm NA930
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += na930
|
2016-05-11 12:04:40 +00:00
|
|
|
|
|
|
|
|
define Device/oy-0001
|
|
|
|
|
DTS := OY-0001
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := Oh Yeah OY-0001
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += oy-0001
|
|
|
|
|
|
|
|
|
|
define Device/psg1208
|
|
|
|
|
DTS := PSG1208
|
|
|
|
|
DEVICE_TITLE := Phicomm PSG1208
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += psg1208
|
|
|
|
|
|
2017-04-21 00:47:44 +00:00
|
|
|
define Device/psg1218a
|
|
|
|
|
DTS := PSG1218A
|
|
|
|
|
DEVICE_TITLE := Phicomm PSG1218 rev.Ax
|
2017-04-20 22:53:03 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2017-04-21 12:51:58 +00:00
|
|
|
SUPPORTED_DEVICES += psg1218
|
2016-09-30 11:41:12 +00:00
|
|
|
endef
|
2017-04-21 00:47:44 +00:00
|
|
|
TARGET_DEVICES += psg1218a
|
2016-09-30 11:41:12 +00:00
|
|
|
|
2017-04-21 00:47:44 +00:00
|
|
|
define Device/psg1218b
|
|
|
|
|
DTS := PSG1218B
|
|
|
|
|
DEVICE_TITLE := Phicomm PSG1218 rev.Bx
|
2017-04-20 22:53:03 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2017-04-21 12:51:58 +00:00
|
|
|
SUPPORTED_DEVICES += psg1218
|
2017-04-20 22:53:03 +00:00
|
|
|
endef
|
2017-04-21 00:47:44 +00:00
|
|
|
TARGET_DEVICES += psg1218b
|
2017-04-20 22:53:03 +00:00
|
|
|
|
2018-06-20 16:56:38 +00:00
|
|
|
define Device/phicomm_k2g
|
|
|
|
|
DTS := K2G
|
|
|
|
|
IMAGE_SIZE := 7552k
|
|
|
|
|
DEVICE_TITLE := Phicomm K2G
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += phicomm_k2g
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/rp-n53
|
|
|
|
|
DTS := RP-N53
|
|
|
|
|
DEVICE_TITLE := Asus RP-N53
|
2019-06-07 16:40:32 +00:00
|
|
|
DEVICE_PACKAGES := kmod-rt2800-pci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += rp-n53
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-12-06 14:43:55 +00:00
|
|
|
define Device/rt-n12p
|
|
|
|
|
DTS := RT-N12-PLUS
|
|
|
|
|
DEVICE_TITLE := Asus RT-N11P/RT-N12+/RT-N12Eb1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += rt-n12p
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/rt-n14u
|
|
|
|
|
DTS := RT-N14U
|
|
|
|
|
DEVICE_TITLE := Asus RT-N14u
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += rt-n14u
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-05-05 15:54:26 +00:00
|
|
|
define Device/rt-ac51u
|
|
|
|
|
DTS := RT-AC51U
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := Asus RT-AC51U
|
2018-12-08 10:48:47 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2017-05-05 15:54:26 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += rt-ac51u
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/tiny-ac
|
|
|
|
|
DTS := TINY-AC
|
|
|
|
|
DEVICE_TITLE := Dovado Tiny AC
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += tiny-ac
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2018-08-06 17:52:28 +00:00
|
|
|
define Device/edimax_br-6478ac-v2
|
2018-07-16 14:19:19 +00:00
|
|
|
DTS := BR-6478AC-V2
|
|
|
|
|
DEVICE_TITLE := Edimax BR-6478AC V2
|
|
|
|
|
BLOCKSIZE := 64k
|
|
|
|
|
IMAGE_SIZE := 7616k
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | \
|
|
|
|
|
edimax-header -s CSYS -m RN68 -f 0x70000 -S 0x01100000 | pad-rootfs | \
|
|
|
|
|
append-metadata | check-size $$$$(IMAGE_SIZE)
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2018-07-16 14:19:19 +00:00
|
|
|
endef
|
2018-08-06 17:52:28 +00:00
|
|
|
TARGET_DEVICES += edimax_br-6478ac-v2
|
2018-07-16 14:19:19 +00:00
|
|
|
|
2018-05-17 09:57:00 +00:00
|
|
|
define Device/tplink_c2-v1
|
|
|
|
|
$(Device/Archer)
|
|
|
|
|
DTS := ArcherC2-v1
|
|
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0xc7500001
|
|
|
|
|
TPLINK_HWREV := 50
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
DEVICE_TITLE := TP-Link Archer C2 v1
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport kmod-switch-rtl8366-smi kmod-switch-rtl8367b
|
2018-05-17 09:57:00 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_c2-v1
|
|
|
|
|
|
2018-01-13 07:16:20 +00:00
|
|
|
define Device/tplink_c20-v1
|
|
|
|
|
$(Device/Archer)
|
|
|
|
|
DTS := ArcherC20v1
|
|
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0xc2000001
|
|
|
|
|
TPLINK_HWREV := 0x44
|
|
|
|
|
TPLINK_HWREVADD := 0x1
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
DEVICE_TITLE := TP-Link ArcherC20 v1
|
2018-12-08 10:48:47 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2018-01-13 07:16:20 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_c20-v1
|
|
|
|
|
|
ramips: add support for Vonets VAR11N-300
The VAR11N-300 is a tiny wireless-N device with a hardwired Ethernet
cable, one extra Ethernet port, and an internal antenna, based on the
MediaTek MT7620n chipset.
Specs:
- MT7620n WiSoC @ 600MHz
- 32 MB SDRAM
- 4 MB SPI flash
- 2T2R 2.4GHz WiFi-N
- 1 attached 10/100 Ethernet cable (LAN)
- 1 10/100 Ethernet port (WAN)
- 1 attached USB / barrel 5vdc power cable
- 5 LEDs (see notes below)
- 1 reset button
- 1 UART (3 pads on board)
Installation:
The stock firmware does not support uploading new firmware directly,
only checking the manufacturer's site for updates. This process may be
possible to spoof, but the update check uses some kind of homebrew
encryption that I didn't investigate. Instead, you can install via a
backdoor:
1. Set up a TFTP server to serve the firmware binary
(lede-ramips-mt7620-var11n-300-squashfs-sysupgrade.bin)
2. Factory reset the device by holding the reset button for a few
seconds.
3. Open the web interface (default IP: 192.168.253.254)
4. Log in with the "super admin" credentials: username `vonets`,
password `vonets26642519`.
5. On the "Operative Status" page, click the text "System Uptime", then
quickly click the uptime value.
6. If successful, an alert dialog will appear reading "Ated start", and
the device will now accept telnet connections. If the alert does not
appear, repeat step 5 until it works (the timing is a bit tricky).
7. Telnet to the device using credentials "admin / admin"
8. Retrieve the firmware binary from the tftp server: `tftp -l lede.bin
-r lede-ramips-mt7620-var11n-300-squashfs-sysupgrade.bin -g
<tftp-server-ip>`
9. Write the firmware to flash: `mtd_write write lede.bin /dev/mtd4`
10. Reboot
Tested:
- LAN / WAN ethernet
- WiFi
- LAN / WAN / status LED GPIOs (see notes below)
- Reset button
- Sysupgrade
Notes:
LEDs:
The board has 5 LEDs - two green LEDs for LAN / WAN activity, one blue
LED for WiFi, and a pair of "status" LEDs connected to the same GPIO
(the blue LED lights when the GPIO is low, and the green when it's
high). I was unable to determine how to operate the WiFi LED, as it
does not appear to be controlled by a GPIO directly.
Recovery:
The default U-boot installation will only boot from flash due to a
missing environment block. I generated a valid 4KB env block using
U-boot's `fw_setenv` tool and wrote it to flash at 0x30000 using an
external programmer. After this, it was possible to enter the U-boot
commandline interface and download a new image via TFTP (`tftpboot
81b00000 <image-filename>`), but while I could boot this image
sucessfully (`bootm`), writing it to flash (`cp.linux`) just corrupted
the flash chip. The sysupgrade file can be written to flash at 0x50000
using an external programmer.
Signed-off-by: Andrew Crawley <acrawley@gmail.com>
2017-11-23 23:52:13 +00:00
|
|
|
define Device/vonets_var11n-300
|
|
|
|
|
DTS := VAR11N-300
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_4M)
|
|
|
|
|
BLOCKSIZE := 4k
|
|
|
|
|
DEVICE_TITLE := Vonets VAR11N-300
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += vonets_var11n-300
|
|
|
|
|
|
2018-04-15 20:34:05 +00:00
|
|
|
define Device/ravpower_wd03
|
|
|
|
|
DTS := WD03
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_8M)
|
|
|
|
|
DEVICE_TITLE := Ravpower WD03
|
2018-12-08 10:48:47 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2018-04-15 20:34:05 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ravpower_wd03
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/whr-1166d
|
|
|
|
|
DTS := WHR-1166D
|
|
|
|
|
IMAGE_SIZE := 15040k
|
|
|
|
|
DEVICE_TITLE := Buffalo WHR-1166D
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += whr-1166d
|
|
|
|
|
|
|
|
|
|
define Device/whr-300hp2
|
|
|
|
|
DTS := WHR-300HP2
|
|
|
|
|
IMAGE_SIZE := 6848k
|
|
|
|
|
DEVICE_TITLE := Buffalo WHR-300HP2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += whr-300hp2
|
|
|
|
|
|
|
|
|
|
define Device/whr-600d
|
|
|
|
|
DTS := WHR-600D
|
|
|
|
|
IMAGE_SIZE := 6848k
|
|
|
|
|
DEVICE_TITLE := Buffalo WHR-600D
|
2019-06-07 16:40:32 +00:00
|
|
|
DEVICE_PACKAGES := kmod-rt2800-pci
|
2017-03-11 23:07:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += whr-600d
|
2016-05-11 12:04:40 +00:00
|
|
|
|
|
|
|
|
define Device/wmr-300
|
|
|
|
|
DTS := WMR-300
|
|
|
|
|
DEVICE_TITLE := Buffalo WMR-300
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wmr-300
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/wn3000rpv3
|
|
|
|
|
NETGEAR_HW_ID := 29764836+8+0+32+2x2+0
|
|
|
|
|
NETGEAR_BOARD_ID := WN3000RPv3
|
|
|
|
|
DTS := WN3000RPV3
|
|
|
|
|
BLOCKSIZE := 4k
|
|
|
|
|
IMAGES += factory.bin
|
2018-04-20 04:30:46 +00:00
|
|
|
KERNEL := $(KERNEL_DTB) | uImage lzma | pad-offset 64k 64 | append-uImage-fakehdr filesystem
|
2017-03-11 23:07:19 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
netgear-dni
|
|
|
|
|
DEVICE_TITLE := Netgear WN3000RPv3
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += wn3000rpv3
|
|
|
|
|
|
|
|
|
|
define Device/wrh-300cr
|
|
|
|
|
DTS := WRH-300CR
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
elecom-header
|
|
|
|
|
DEVICE_TITLE := Elecom WRH-300CR
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wrh-300cr
|
2016-05-11 12:04:40 +00:00
|
|
|
|
|
|
|
|
define Device/wrtnode
|
|
|
|
|
DTS := WRTNODE
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
|
|
|
|
DEVICE_TITLE := WRTNode
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wrtnode
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/wt3020-4M
|
|
|
|
|
DTS := WT3020-4M
|
|
|
|
|
BLOCKSIZE := 4k
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_4M)
|
|
|
|
|
IMAGES += factory.bin
|
2017-04-01 10:27:46 +00:00
|
|
|
SUPPORTED_DEVICES += wt3020
|
2017-03-11 23:07:19 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
poray-header -B WT3020 -F 4M
|
|
|
|
|
DEVICE_TITLE := Nexx WT3020 (4MB)
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2019-09-08 19:08:22 +00:00
|
|
|
#TARGET_DEVICES += wt3020-4M
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/wt3020-8M
|
|
|
|
|
DTS := WT3020-8M
|
|
|
|
|
IMAGES += factory.bin
|
2017-04-01 10:27:46 +00:00
|
|
|
SUPPORTED_DEVICES += wt3020
|
2017-03-11 23:07:19 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size $$$$(IMAGE_SIZE) | \
|
|
|
|
|
poray-header -B WT3020 -F 8M
|
|
|
|
|
DEVICE_TITLE := Nexx WT3020 (8MB)
|
2017-10-21 21:53:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += wt3020-8M
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/y1
|
|
|
|
|
DTS := Y1
|
2016-05-11 12:04:40 +00:00
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
2017-03-11 23:07:19 +00:00
|
|
|
DEVICE_TITLE := Lenovo Y1
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += y1
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/y1s
|
|
|
|
|
DTS := Y1S
|
2016-05-11 12:04:40 +00:00
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
2017-03-11 23:07:19 +00:00
|
|
|
DEVICE_TITLE := Lenovo Y1S
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += y1s
|
2016-05-11 12:04:40 +00:00
|
|
|
|
|
|
|
|
define Device/youku-yk1
|
|
|
|
|
DTS := YOUKU-YK1
|
2017-10-21 09:07:43 +00:00
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_32M)
|
2016-05-11 12:04:40 +00:00
|
|
|
DEVICE_TITLE := YOUKU YK1
|
2017-10-21 09:07:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620 kmod-usb-ledtrig-usbport
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += youku-yk1
|
|
|
|
|
|
ramips: Add support for ZBT WE1026-5G
The ZBT WE1026-5G
(http://www.zbtlink.com/products/router/WE1026-5G.html) is the follow-up
to the ZBT WE1026 and is based on MT7620. For the previous WE1026, the
ZBT WE826 image could be used. However, as the name implies, the -5G
comes equipped with a 5GHz wifi radio. As the WE826 only has a 2.4GHz
radio, the addition of 5GHz means that a separate image is needed for
the WE1026-5G. I suspect that this image will also work on the previous
WE1026, but I don't have a device to test with.
The WE1026-5G has following specifications:
* CPU: MT7620A
* 1x 10/100Mbps Ethernet.
* 16 MB Flash.
* 64 MB RAM.
* 1x USB 2.0 port.
* 1x mini-PCIe slots.
* 1x SIM slots.
* 1x 2.4Ghz WIFI.
* 1x 5GHz wifi (MT7612)
* 1x button.
* 3x controllable LEDs.
Works:
* Wifi.
* Switch.
* mini-PCIe slot. Only tested with a USB device (a modem).
* SIM slot.
* Sysupgrade.
* Button (reset).
Not working:
* The 5GHz WIFI LED is completely dead. I suspect the issue is the same
as on other devices with Mediatek 5Ghz wifi-cards/chips. The LED is
controlled by the driver, and mt76 (currently) does not support this.
Not tested:
* SD card reader.
Notes:
* The modem (labeled 3G/4G) and power LEDs are controlled by the
hardware.
* There is a 32MB version of this device available, but I do not have
access to it. I have therefor only added support for the 16MB version,
but added all the required infrastructure to make adding support for the
32MB version easy.
Installation:
The router comes pre-installed with OpenWRT, including a variant of
Luci. The initial firmware install can be done through this UI,
following normal procedure. I.e., access the UI and update the firmware
using the sysupgrade-image. Remember to select that you do not want to
keep existing settings.
Recovery:
If you brick the device, the WE1026-5G supports recovery using HTTP. Keep the
reset button pressed for ~5sec when booting to start the web server. Set the
address of the network interface on your machine to 192.168.1.2/24, and
point your browser to 192.168.1.1 to access the recovery UI. From the
recovery UI you can upload a firmware image.
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-09-10 12:44:47 +00:00
|
|
|
define Device/we1026-5g-16m
|
|
|
|
|
DTS := WE1026-5G-16M
|
|
|
|
|
IMAGE_SIZE := 16777216
|
|
|
|
|
SUPPORTED_DEVICES += we1026-5g-16m
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-WE1026-5G (16M)
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620
|
ramips: Add support for ZBT WE1026-5G
The ZBT WE1026-5G
(http://www.zbtlink.com/products/router/WE1026-5G.html) is the follow-up
to the ZBT WE1026 and is based on MT7620. For the previous WE1026, the
ZBT WE826 image could be used. However, as the name implies, the -5G
comes equipped with a 5GHz wifi radio. As the WE826 only has a 2.4GHz
radio, the addition of 5GHz means that a separate image is needed for
the WE1026-5G. I suspect that this image will also work on the previous
WE1026, but I don't have a device to test with.
The WE1026-5G has following specifications:
* CPU: MT7620A
* 1x 10/100Mbps Ethernet.
* 16 MB Flash.
* 64 MB RAM.
* 1x USB 2.0 port.
* 1x mini-PCIe slots.
* 1x SIM slots.
* 1x 2.4Ghz WIFI.
* 1x 5GHz wifi (MT7612)
* 1x button.
* 3x controllable LEDs.
Works:
* Wifi.
* Switch.
* mini-PCIe slot. Only tested with a USB device (a modem).
* SIM slot.
* Sysupgrade.
* Button (reset).
Not working:
* The 5GHz WIFI LED is completely dead. I suspect the issue is the same
as on other devices with Mediatek 5Ghz wifi-cards/chips. The LED is
controlled by the driver, and mt76 (currently) does not support this.
Not tested:
* SD card reader.
Notes:
* The modem (labeled 3G/4G) and power LEDs are controlled by the
hardware.
* There is a 32MB version of this device available, but I do not have
access to it. I have therefor only added support for the 16MB version,
but added all the required infrastructure to make adding support for the
32MB version easy.
Installation:
The router comes pre-installed with OpenWRT, including a variant of
Luci. The initial firmware install can be done through this UI,
following normal procedure. I.e., access the UI and update the firmware
using the sysupgrade-image. Remember to select that you do not want to
keep existing settings.
Recovery:
If you brick the device, the WE1026-5G supports recovery using HTTP. Keep the
reset button pressed for ~5sec when booting to start the web server. Set the
address of the network interface on your machine to 192.168.1.2/24, and
point your browser to 192.168.1.1 to access the recovery UI. From the
recovery UI you can upload a firmware image.
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-09-10 12:44:47 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += we1026-5g-16m
|
|
|
|
|
|
2016-06-23 08:58:08 +00:00
|
|
|
define Device/zbt-ape522ii
|
|
|
|
|
DTS := ZBT-APE522II
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-APE522II
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2016-06-23 08:58:08 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zbt-ape522ii
|
|
|
|
|
|
2016-09-25 19:09:31 +00:00
|
|
|
define Device/zbt-cpe102
|
|
|
|
|
DTS := ZBT-CPE102
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-CPE102
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zbt-cpe102
|
|
|
|
|
|
2016-05-11 12:04:40 +00:00
|
|
|
define Device/zbt-wa05
|
|
|
|
|
DTS := ZBT-WA05
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-WA05
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zbt-wa05
|
|
|
|
|
|
2017-03-15 08:37:05 +00:00
|
|
|
define Device/zbt-we2026
|
|
|
|
|
DTS := ZBT-WE2026
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-WE2026
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zbt-we2026
|
|
|
|
|
|
2017-04-12 05:53:56 +00:00
|
|
|
define Device/zbt-we826-16M
|
|
|
|
|
DTS := ZBT-WE826-16M
|
2016-05-11 12:04:40 +00:00
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_16M)
|
2017-04-12 05:53:56 +00:00
|
|
|
SUPPORTED_DEVICES += zbt-we826
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-WE826 (16M)
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
2017-04-12 05:53:56 +00:00
|
|
|
TARGET_DEVICES += zbt-we826-16M
|
|
|
|
|
|
|
|
|
|
define Device/zbt-we826-32M
|
|
|
|
|
DTS := ZBT-WE826-32M
|
|
|
|
|
IMAGE_SIZE := $(ralink_default_fw_size_32M)
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-WE826 (32M)
|
2018-11-30 10:48:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620
|
2017-04-12 05:53:56 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zbt-we826-32M
|
2016-05-11 12:04:40 +00:00
|
|
|
|
2019-05-16 13:38:00 +00:00
|
|
|
define Device/zbtlink_zbt-we826-e
|
|
|
|
|
DTS := ZBT-WE826-E
|
|
|
|
|
IMAGE_SIZE := 32448k
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-WE826-E
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-sdhci-mt7620 uqmi \
|
|
|
|
|
kmod-usb-serial kmod-usb-serial-option
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zbtlink_zbt-we826-e
|
|
|
|
|
|
2016-05-11 12:04:40 +00:00
|
|
|
define Device/zbt-wr8305rt
|
|
|
|
|
DTS := ZBT-WR8305RT
|
|
|
|
|
DEVICE_TITLE := Zbtlink ZBT-WR8305RT
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2016-05-11 12:04:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zbt-wr8305rt
|
|
|
|
|
|
2017-03-11 23:07:19 +00:00
|
|
|
define Device/zte-q7
|
|
|
|
|
DTS := ZTE-Q7
|
|
|
|
|
DEVICE_TITLE := ZTE Q7
|
2018-12-08 11:25:00 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2017-02-04 20:28:52 +00:00
|
|
|
endef
|
2017-03-11 23:07:19 +00:00
|
|
|
TARGET_DEVICES += zte-q7
|
