2016-04-01 07:11:48 +00:00
|
|
|
#
|
|
|
|
|
# MT7621 Profiles
|
|
|
|
|
#
|
|
|
|
|
|
2020-01-29 17:21:53 +00:00
|
|
|
include ./common-tp-link.mk
|
|
|
|
|
|
2020-01-21 20:54:50 +00:00
|
|
|
DEFAULT_SOC := mt7621
|
|
|
|
|
|
2018-08-30 08:51:09 +00:00
|
|
|
KERNEL_DTB += -d21
|
2020-07-16 00:24:43 +00:00
|
|
|
DEVICE_VARS += UIMAGE_MAGIC ELECOM_HWNAME LINKSYS_HWNAME
|
2019-09-24 18:02:04 +00:00
|
|
|
|
|
|
|
|
# The OEM webinterface expects an kernel with initramfs which has the uImage
|
|
|
|
|
# header field ih_name.
|
|
|
|
|
# We don't want to set the header name field for the kernel include in the
|
|
|
|
|
# sysupgrade image as well, as this image shouldn't be accepted by the OEM
|
|
|
|
|
# webinterface. It will soft-brick the board.
|
|
|
|
|
define Build/custom-initramfs-uimage
|
|
|
|
|
mkimage -A $(LINUX_KARCH) \
|
|
|
|
|
-O linux -T kernel \
|
|
|
|
|
-C lzma -a $(KERNEL_LOADADDR) $(if $(UIMAGE_MAGIC),-M $(UIMAGE_MAGIC),) \
|
|
|
|
|
-e $(if $(KERNEL_ENTRY),$(KERNEL_ENTRY),$(KERNEL_LOADADDR)) \
|
|
|
|
|
-n '$(1)' -d $@ $@.new
|
|
|
|
|
mv $@.new $@
|
|
|
|
|
endef
|
2017-07-23 19:06:44 +00:00
|
|
|
|
2020-07-15 18:08:22 +00:00
|
|
|
define Build/elecom-wrc-gs-factory
|
2020-05-08 16:21:06 +00:00
|
|
|
$(eval product=$(word 1,$(1)))
|
|
|
|
|
$(eval version=$(word 2,$(1)))
|
|
|
|
|
( $(STAGING_DIR_HOST)/bin/mkhash md5 $@ | tr -d '\n' ) >> $@
|
|
|
|
|
( \
|
|
|
|
|
echo -n "ELECOM $(product) v$(version)" | \
|
|
|
|
|
dd bs=32 count=1 conv=sync; \
|
|
|
|
|
dd if=$@; \
|
|
|
|
|
) > $@.new
|
|
|
|
|
mv $@.new $@
|
|
|
|
|
echo -n "MT7621_ELECOM_$(product)" >> $@
|
2018-07-26 14:24:22 +00:00
|
|
|
endef
|
|
|
|
|
|
2018-06-15 15:27:51 +00:00
|
|
|
define Build/elecom-wrc-factory
|
2020-05-08 16:21:06 +00:00
|
|
|
$(eval product=$(word 1,$(1)))
|
|
|
|
|
$(eval version=$(word 2,$(1)))
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/mkhash md5 $@ >> $@
|
|
|
|
|
( \
|
|
|
|
|
echo -n "ELECOM $(product) v$(version)" | \
|
|
|
|
|
dd bs=32 count=1 conv=sync; \
|
|
|
|
|
dd if=$@; \
|
|
|
|
|
) > $@.new
|
|
|
|
|
mv $@.new $@
|
2018-06-15 15:27:51 +00:00
|
|
|
endef
|
|
|
|
|
|
ramips: add support for I-O DATA WN-AX1167GR
I-O DATA WN-AX1167GR is a 2.4/5 GHz band 11ac router, based on
MediaTek MT7621A.
Specification:
- MT7621A (2-Cores, 4-Threads)
- 64 MB of RAM (DDR2)
- 16 MB of Flash (SPI)
- 2T2R 2.4/5 GHz
- 5x 10/100/1000 Mbps Ethernet
- 2x LEDs, 4x keys (2x buttons, 1x slide switch)
- UART header on PCB
- Vcc, GND, TX, RX from ethernet port side
- baudrate: 115200 bps (U-Boot, OpenWrt)
Stock firmware:
In the stock firmware, WN-AX1167GR has two os images each composed of
Linux kernel and rootfs.
These images are stored in "Kernel" and "app" partition of the
following partitions, respectively.
(excerpt from dmesg):
MX25L12805D(c2 2018c220) (16384 Kbytes)
mtd .name = raspi, .size = 0x01000000 (16M) .erasesize = 0x00010000 (64K) .numeraseregions = 0
Creating 10 MTD partitions on "raspi":
0x000000000000-0x000001000000 : "ALL"
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config "
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000060000 : "iNIC_rf"
0x000000060000-0x0000007e0000 : "Kernel"
0x000000800000-0x000000f80000 : "app"
0x000000f90000-0x000000fa0000 : "Key"
0x000000fa0000-0x000000fb0000 : "backup"
0x000000fb0000-0x000001000000 : "storage"
The flag for boot partition is stored in "Key" partition, and U-Boot
reads this and determines the partition to boot.
If the image that U-Boot first reads according to the flag is
"Bad Magic Number", U-Boot then tries to boot from the other image.
If the second image is correct, change the flag to the number
corresponding to that image and boot from that image.
(example):
## Booting image at bc800000 ...
Bad Magic Number,FFFFFFFF
Boot from KERNEL 1 !!
## Booting image at bc060000 ...
Image Name: MIPS OpenWrt Linux-4.14.50
Image Type: MIPS Linux kernel Image (lzma compressed)
Data Size: 1865917 Bytes = 1.8 MB
Load Address: 80001000
Entry Point: 80001000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
raspi_erase_write: offs:f90000, count:34
.
.
Done!
Starting kernel ...
Flash instruction using factory image:
1. Connect the computer to the LAN port of WN-AX1167GR
2. Connect power cable to WN-AX1167GR and turn on it
3. Access to "192.168.0.1" on the web browser and open firmware
update page ("ファームウェア")
4. Select the OpenWrt factory image and perform firmware update
5. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-AX1167GR
6. Wait ~180 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-06-27 13:47:13 +00:00
|
|
|
define Build/iodata-factory
|
2020-05-08 16:21:06 +00:00
|
|
|
$(eval fw_size=$(word 1,$(1)))
|
|
|
|
|
$(eval fw_type=$(word 2,$(1)))
|
|
|
|
|
$(eval product=$(word 3,$(1)))
|
|
|
|
|
$(eval factory_bin=$(word 4,$(1)))
|
|
|
|
|
if [ -e $(KDIR)/tmp/$(KERNEL_INITRAMFS_IMAGE) -a "$$(stat -c%s $@)" -lt "$(fw_size)" ]; then \
|
|
|
|
|
$(CP) $(KDIR)/tmp/$(KERNEL_INITRAMFS_IMAGE) $(factory_bin); \
|
|
|
|
|
$(STAGING_DIR_HOST)/bin/mksenaofw \
|
|
|
|
|
-r 0x30a -p $(product) -t $(fw_type) \
|
|
|
|
|
-e $(factory_bin) -o $(factory_bin).new; \
|
|
|
|
|
mv $(factory_bin).new $(factory_bin); \
|
|
|
|
|
$(CP) $(factory_bin) $(BIN_DIR)/; \
|
ramips: add support for I-O DATA WN-AX1167GR
I-O DATA WN-AX1167GR is a 2.4/5 GHz band 11ac router, based on
MediaTek MT7621A.
Specification:
- MT7621A (2-Cores, 4-Threads)
- 64 MB of RAM (DDR2)
- 16 MB of Flash (SPI)
- 2T2R 2.4/5 GHz
- 5x 10/100/1000 Mbps Ethernet
- 2x LEDs, 4x keys (2x buttons, 1x slide switch)
- UART header on PCB
- Vcc, GND, TX, RX from ethernet port side
- baudrate: 115200 bps (U-Boot, OpenWrt)
Stock firmware:
In the stock firmware, WN-AX1167GR has two os images each composed of
Linux kernel and rootfs.
These images are stored in "Kernel" and "app" partition of the
following partitions, respectively.
(excerpt from dmesg):
MX25L12805D(c2 2018c220) (16384 Kbytes)
mtd .name = raspi, .size = 0x01000000 (16M) .erasesize = 0x00010000 (64K) .numeraseregions = 0
Creating 10 MTD partitions on "raspi":
0x000000000000-0x000001000000 : "ALL"
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config "
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000060000 : "iNIC_rf"
0x000000060000-0x0000007e0000 : "Kernel"
0x000000800000-0x000000f80000 : "app"
0x000000f90000-0x000000fa0000 : "Key"
0x000000fa0000-0x000000fb0000 : "backup"
0x000000fb0000-0x000001000000 : "storage"
The flag for boot partition is stored in "Key" partition, and U-Boot
reads this and determines the partition to boot.
If the image that U-Boot first reads according to the flag is
"Bad Magic Number", U-Boot then tries to boot from the other image.
If the second image is correct, change the flag to the number
corresponding to that image and boot from that image.
(example):
## Booting image at bc800000 ...
Bad Magic Number,FFFFFFFF
Boot from KERNEL 1 !!
## Booting image at bc060000 ...
Image Name: MIPS OpenWrt Linux-4.14.50
Image Type: MIPS Linux kernel Image (lzma compressed)
Data Size: 1865917 Bytes = 1.8 MB
Load Address: 80001000
Entry Point: 80001000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
raspi_erase_write: offs:f90000, count:34
.
.
Done!
Starting kernel ...
Flash instruction using factory image:
1. Connect the computer to the LAN port of WN-AX1167GR
2. Connect power cable to WN-AX1167GR and turn on it
3. Access to "192.168.0.1" on the web browser and open firmware
update page ("ファームウェア")
4. Select the OpenWrt factory image and perform firmware update
5. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-AX1167GR
6. Wait ~180 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-06-27 13:47:13 +00:00
|
|
|
else \
|
|
|
|
|
echo "WARNING: initramfs kernel image too big, cannot generate factory image" >&2; \
|
|
|
|
|
fi
|
|
|
|
|
endef
|
|
|
|
|
|
2019-04-09 05:48:31 +00:00
|
|
|
define Build/iodata-mstc-header
|
2020-05-08 16:21:06 +00:00
|
|
|
( \
|
|
|
|
|
data_size_crc="$$(dd if=$@ ibs=64 skip=1 2>/dev/null | gzip -c | \
|
|
|
|
|
tail -c 8 | od -An -tx8 --endian little | tr -d ' \n')"; \
|
|
|
|
|
echo -ne "$$(echo $$data_size_crc | sed 's/../\\x&/g')" | \
|
|
|
|
|
dd of=$@ bs=8 count=1 seek=7 conv=notrunc 2>/dev/null; \
|
|
|
|
|
)
|
|
|
|
|
dd if=/dev/zero of=$@ bs=4 count=1 seek=1 conv=notrunc 2>/dev/null
|
|
|
|
|
( \
|
|
|
|
|
header_crc="$$(dd if=$@ bs=64 count=1 2>/dev/null | gzip -c | \
|
|
|
|
|
tail -c 8 | od -An -N4 -tx4 --endian little | tr -d ' \n')"; \
|
|
|
|
|
echo -ne "$$(echo $$header_crc | sed 's/../\\x&/g')" | \
|
|
|
|
|
dd of=$@ bs=4 count=1 seek=1 conv=notrunc 2>/dev/null; \
|
|
|
|
|
)
|
2019-04-09 05:48:31 +00:00
|
|
|
endef
|
|
|
|
|
|
2016-04-09 10:24:29 +00:00
|
|
|
define Build/ubnt-erx-factory-image
|
2016-07-06 08:11:29 +00:00
|
|
|
if [ -e $(KDIR)/tmp/$(KERNEL_INITRAMFS_IMAGE) -a "$$(stat -c%s $@)" -lt "$(KERNEL_SIZE)" ]; then \
|
mt7621: Make ER-X-SFP factory image compatible with EP-R6
The version inside the compat file determines, if a firmware supports
a specific device. I have not yet fully understood, how this is checked,
but it only seems to indicate which devices are supported by a specific
version of the combined vendor firmware. Devices assume that subsequent
versions, starting with the version that initially added support for a
specific device, are always compatible.
The first compat version that added support for the EP-R6 was '21001:7',
but OpenWrt did use '21001:6' before. This is why the factory image could
not be flashed using the vendor software, but only using TFTP.
The compat version has been bumped by the vendor a few times, but more
devices have been added since (e.g. ER-10X). Because OpenWrt currently
only supports the ER-X, ER-X-SFP and EP-R6, the compat version is
incremented to the version that first supported the EP-R6, which is
'21001:7'.
This allows the factory image to be flashed on EP-R6 without TFTP.
Signed-off-by: Fabian Bläse <fabian@blaese.de>
2020-05-16 10:23:52 +00:00
|
|
|
echo '21001:7' > $(1).compat; \
|
2016-04-09 10:24:29 +00:00
|
|
|
$(TAR) -cf $(1) --transform='s/^.*/compat/' $(1).compat; \
|
|
|
|
|
\
|
|
|
|
|
$(TAR) -rf $(1) --transform='s/^.*/vmlinux.tmp/' $(KDIR)/tmp/$(KERNEL_INITRAMFS_IMAGE); \
|
2016-12-25 15:40:05 +00:00
|
|
|
mkhash md5 $(KDIR)/tmp/$(KERNEL_INITRAMFS_IMAGE) > $(1).md5; \
|
2016-04-09 10:24:29 +00:00
|
|
|
$(TAR) -rf $(1) --transform='s/^.*/vmlinux.tmp.md5/' $(1).md5; \
|
|
|
|
|
\
|
|
|
|
|
echo "dummy" > $(1).rootfs; \
|
|
|
|
|
$(TAR) -rf $(1) --transform='s/^.*/squashfs.tmp/' $(1).rootfs; \
|
2016-04-01 07:11:48 +00:00
|
|
|
\
|
2016-12-25 15:40:05 +00:00
|
|
|
mkhash md5 $(1).rootfs > $(1).md5; \
|
2016-04-09 10:24:29 +00:00
|
|
|
$(TAR) -rf $(1) --transform='s/^.*/squashfs.tmp.md5/' $(1).md5; \
|
|
|
|
|
\
|
|
|
|
|
echo '$(BOARD) $(VERSION_CODE) $(VERSION_NUMBER)' > $(1).version; \
|
|
|
|
|
$(TAR) -rf $(1) --transform='s/^.*/version.tmp/' $(1).version; \
|
|
|
|
|
\
|
|
|
|
|
$(CP) $(1) $(BIN_DIR)/; \
|
2016-07-06 08:11:29 +00:00
|
|
|
else \
|
|
|
|
|
echo "WARNING: initramfs kernel image too big, cannot generate factory image" >&2; \
|
2016-04-01 07:11:48 +00:00
|
|
|
fi
|
|
|
|
|
endef
|
|
|
|
|
|
2020-07-14 14:42:40 +00:00
|
|
|
define Device/dsa-migration
|
|
|
|
|
DEVICE_COMPAT_VERSION := 1.1
|
2020-08-08 19:30:44 +00:00
|
|
|
DEVICE_COMPAT_MESSAGE := Config cannot be migrated from swconfig to DSA
|
2020-07-14 14:42:40 +00:00
|
|
|
endef
|
|
|
|
|
|
2020-07-08 19:18:12 +00:00
|
|
|
define Device/adslr_g7
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-07-08 19:18:12 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_VENDOR := ADSLR
|
|
|
|
|
DEVICE_MODEL := G7
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2020-07-08 19:18:12 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += adslr_g7
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/afoundry_ew1200
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := AFOUNDRY
|
|
|
|
|
DEVICE_MODEL := EW1200
|
2020-03-05 13:57:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-mt76x2 kmod-mt7603 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += ew1200
|
2016-04-01 07:11:48 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += afoundry_ew1200
|
|
|
|
|
|
ramips: add support for ALFA Network Quad-E4G
ALFA Network Quad-E4G is a universal Wi-Fi/4G platform, which offers
three miniPCIe (PCIe, USB 2.0, SIM) and a single M.2 B-key (dual-SIM,
USB 3.0) slots, RTC and five Gigabit Ethernet ports with PoE support.
Specification:
- MT7621A (880 MHz)
- 256/512 MB of RAM (DDR3)
- 16/32+ MB of FLASH (SPI NOR)
- optional second SPI flash (8-pin WSON/SOIC)
- 1x microSD (SDXC) flash card reader
- 5x 10/100/100 Mbps Ethernet, with passive PoE support (24 V) in LAN1
- optional 802.3at/af PoE module for WAN
- 3x miniPCIe slot (with PCIe and USB 2.0 buses, micro SIM and 5 V)
- 1x M.2/NGFF B-key 3042 (USB 3.0/2.0, mini + micro SIM)
- RTC (TI BQ32002, I2C bus) with backup battery (CR2032)
- external hardware watchdog (EM Microelectronic EM6324)
- 1x USB 2.0 Type-A
- 1x micro USB Type-B for system serial console (Holtek HT42B534)
- 11x LED (5 for Ethernet, 5 driven by GPIO, 1x power indicator)
- 3x button (reset, user1, user2)
- 1x I2C (4-pin, 2.54 mm pitch) header on PCB
- 4x SIM (6-pin, 2.00 mm pitch) headers on PCB
- 2x UART2/3 (4-pin, 2.54 mm pitch) headers on PCB
- 1x mechanical power switch
- 1x DC jack with lock (24 V)
Other:
- U-Boot selects default SIM slot, based on value of 'default_sim' env
variable: '1' or unset -> SIM1 (mini), '2' -> SIM2 (micro). This board
has additional logic circuit for M.2 SIM switching. The 'sim-select'
will work only if both SIM slots are occupied. Otherwise, always slot
with SIM inside is selected, no matter 'sim-select' value.
- U-Boot enables power in all three miniPCIe and M.2 slots before
loading the kernel
- this board supports 'dual image' feature (controlled by 'dual_image'
U-Boot environment variable)
- all three miniPCIe slots have additional 5 V supply on pins 47 and 49
- the board allows to install up to two oversized miniPCIe cards (vendor
has dedicated MediaTek MT7615N/D cards for this board)
- this board has additional logic circuit controlling PERSTn pins inside
miniPCIe slots. By default, PERSTn (GPIO19) is routed to all miniPCIe
slots but setting GPIO22 to high allows PERSTn control per slot, using
GPIO23-25 (value is inverted)
You can use the 'sysupgrade' image directly in vendor firmware which is
based on OpenWrt (make sure to not preserve settings - use 'sysupgrade
-n -F ...' command). Alternatively, use web recovery mode in U-Boot:
1. Power the device with reset button pressed, the modem LED will start
blinking slowly and after ~3 seconds, when it starts blinking faster,
you can release the button.
2. Setup static IP 192.168.1.2/24 on your PC.
3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-11-03 11:12:44 +00:00
|
|
|
define Device/alfa-network_quad-e4g
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
ramips: add support for ALFA Network Quad-E4G
ALFA Network Quad-E4G is a universal Wi-Fi/4G platform, which offers
three miniPCIe (PCIe, USB 2.0, SIM) and a single M.2 B-key (dual-SIM,
USB 3.0) slots, RTC and five Gigabit Ethernet ports with PoE support.
Specification:
- MT7621A (880 MHz)
- 256/512 MB of RAM (DDR3)
- 16/32+ MB of FLASH (SPI NOR)
- optional second SPI flash (8-pin WSON/SOIC)
- 1x microSD (SDXC) flash card reader
- 5x 10/100/100 Mbps Ethernet, with passive PoE support (24 V) in LAN1
- optional 802.3at/af PoE module for WAN
- 3x miniPCIe slot (with PCIe and USB 2.0 buses, micro SIM and 5 V)
- 1x M.2/NGFF B-key 3042 (USB 3.0/2.0, mini + micro SIM)
- RTC (TI BQ32002, I2C bus) with backup battery (CR2032)
- external hardware watchdog (EM Microelectronic EM6324)
- 1x USB 2.0 Type-A
- 1x micro USB Type-B for system serial console (Holtek HT42B534)
- 11x LED (5 for Ethernet, 5 driven by GPIO, 1x power indicator)
- 3x button (reset, user1, user2)
- 1x I2C (4-pin, 2.54 mm pitch) header on PCB
- 4x SIM (6-pin, 2.00 mm pitch) headers on PCB
- 2x UART2/3 (4-pin, 2.54 mm pitch) headers on PCB
- 1x mechanical power switch
- 1x DC jack with lock (24 V)
Other:
- U-Boot selects default SIM slot, based on value of 'default_sim' env
variable: '1' or unset -> SIM1 (mini), '2' -> SIM2 (micro). This board
has additional logic circuit for M.2 SIM switching. The 'sim-select'
will work only if both SIM slots are occupied. Otherwise, always slot
with SIM inside is selected, no matter 'sim-select' value.
- U-Boot enables power in all three miniPCIe and M.2 slots before
loading the kernel
- this board supports 'dual image' feature (controlled by 'dual_image'
U-Boot environment variable)
- all three miniPCIe slots have additional 5 V supply on pins 47 and 49
- the board allows to install up to two oversized miniPCIe cards (vendor
has dedicated MediaTek MT7615N/D cards for this board)
- this board has additional logic circuit controlling PERSTn pins inside
miniPCIe slots. By default, PERSTn (GPIO19) is routed to all miniPCIe
slots but setting GPIO22 to high allows PERSTn control per slot, using
GPIO23-25 (value is inverted)
You can use the 'sysupgrade' image directly in vendor firmware which is
based on OpenWrt (make sure to not preserve settings - use 'sysupgrade
-n -F ...' command). Alternatively, use web recovery mode in U-Boot:
1. Power the device with reset button pressed, the modem LED will start
blinking slowly and after ~3 seconds, when it starts blinking faster,
you can release the button.
2. Setup static IP 192.168.1.2/24 on your PC.
3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-11-03 11:12:44 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_VENDOR := ALFA Network
|
|
|
|
|
DEVICE_MODEL := Quad-E4G
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-sdhci-mt7620 kmod-usb3 uboot-envtools \
|
2020-07-27 10:30:41 +00:00
|
|
|
-wpad-basic-wolfssl
|
ramips: add support for ALFA Network Quad-E4G
ALFA Network Quad-E4G is a universal Wi-Fi/4G platform, which offers
three miniPCIe (PCIe, USB 2.0, SIM) and a single M.2 B-key (dual-SIM,
USB 3.0) slots, RTC and five Gigabit Ethernet ports with PoE support.
Specification:
- MT7621A (880 MHz)
- 256/512 MB of RAM (DDR3)
- 16/32+ MB of FLASH (SPI NOR)
- optional second SPI flash (8-pin WSON/SOIC)
- 1x microSD (SDXC) flash card reader
- 5x 10/100/100 Mbps Ethernet, with passive PoE support (24 V) in LAN1
- optional 802.3at/af PoE module for WAN
- 3x miniPCIe slot (with PCIe and USB 2.0 buses, micro SIM and 5 V)
- 1x M.2/NGFF B-key 3042 (USB 3.0/2.0, mini + micro SIM)
- RTC (TI BQ32002, I2C bus) with backup battery (CR2032)
- external hardware watchdog (EM Microelectronic EM6324)
- 1x USB 2.0 Type-A
- 1x micro USB Type-B for system serial console (Holtek HT42B534)
- 11x LED (5 for Ethernet, 5 driven by GPIO, 1x power indicator)
- 3x button (reset, user1, user2)
- 1x I2C (4-pin, 2.54 mm pitch) header on PCB
- 4x SIM (6-pin, 2.00 mm pitch) headers on PCB
- 2x UART2/3 (4-pin, 2.54 mm pitch) headers on PCB
- 1x mechanical power switch
- 1x DC jack with lock (24 V)
Other:
- U-Boot selects default SIM slot, based on value of 'default_sim' env
variable: '1' or unset -> SIM1 (mini), '2' -> SIM2 (micro). This board
has additional logic circuit for M.2 SIM switching. The 'sim-select'
will work only if both SIM slots are occupied. Otherwise, always slot
with SIM inside is selected, no matter 'sim-select' value.
- U-Boot enables power in all three miniPCIe and M.2 slots before
loading the kernel
- this board supports 'dual image' feature (controlled by 'dual_image'
U-Boot environment variable)
- all three miniPCIe slots have additional 5 V supply on pins 47 and 49
- the board allows to install up to two oversized miniPCIe cards (vendor
has dedicated MediaTek MT7615N/D cards for this board)
- this board has additional logic circuit controlling PERSTn pins inside
miniPCIe slots. By default, PERSTn (GPIO19) is routed to all miniPCIe
slots but setting GPIO22 to high allows PERSTn control per slot, using
GPIO23-25 (value is inverted)
You can use the 'sysupgrade' image directly in vendor firmware which is
based on OpenWrt (make sure to not preserve settings - use 'sysupgrade
-n -F ...' command). Alternatively, use web recovery mode in U-Boot:
1. Power the device with reset button pressed, the modem LED will start
blinking slowly and after ~3 seconds, when it starts blinking faster,
you can release the button.
2. Setup static IP 192.168.1.2/24 on your PC.
3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2019-11-03 11:12:44 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += alfa-network_quad-e4g
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/asiarf_ap7621-001
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-15 12:55:24 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := AsiaRF
|
|
|
|
|
DEVICE_MODEL := AP7621-001
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-sdhci-mt7620 kmod-mt76x2 kmod-usb3 -wpad-basic-wolfssl
|
2019-07-07 14:27:51 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += asiarf_ap7621-001
|
|
|
|
|
|
2019-07-22 10:54:06 +00:00
|
|
|
define Device/asiarf_ap7621-nv1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 10:54:06 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
DEVICE_VENDOR := AsiaRF
|
|
|
|
|
DEVICE_MODEL := AP7621-NV1
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-sdhci-mt7620 kmod-mt76x2 kmod-usb3 -wpad-basic-wolfssl
|
2019-07-22 10:54:06 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += asiarf_ap7621-nv1
|
|
|
|
|
|
2019-07-11 15:15:48 +00:00
|
|
|
define Device/asus_rt-ac57u
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-11 15:15:48 +00:00
|
|
|
DEVICE_VENDOR := ASUS
|
|
|
|
|
DEVICE_MODEL := RT-AC57U
|
|
|
|
|
IMAGE_SIZE := 16064k
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-07-11 15:15:48 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += asus_rt-ac57u
|
|
|
|
|
|
2019-10-22 19:44:09 +00:00
|
|
|
define Device/asus_rt-ac65p
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-10-22 19:44:09 +00:00
|
|
|
DEVICE_VENDOR := ASUS
|
|
|
|
|
DEVICE_MODEL := RT-AC65P
|
|
|
|
|
IMAGE_SIZE := 51200k
|
|
|
|
|
UBINIZE_OPTS := -E 5
|
|
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
KERNEL_SIZE := 4096k
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
2019-12-19 18:40:33 +00:00
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$(KERNEL_SIZE) | append-ubi | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb3 kmod-mt7615e kmod-mt7615-firmware uboot-envtools
|
2019-10-22 19:44:09 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += asus_rt-ac65p
|
|
|
|
|
|
2019-09-15 14:20:11 +00:00
|
|
|
define Device/asus_rt-ac85p
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-09-15 14:20:11 +00:00
|
|
|
DEVICE_VENDOR := ASUS
|
|
|
|
|
DEVICE_MODEL := RT-AC85P
|
|
|
|
|
IMAGE_SIZE := 51200k
|
|
|
|
|
UBINIZE_OPTS := -E 5
|
|
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
KERNEL_SIZE := 4096k
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
2019-12-19 18:40:33 +00:00
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$(KERNEL_SIZE) | append-ubi | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb3 kmod-mt7615e kmod-mt7615-firmware uboot-envtools
|
2019-09-15 14:20:11 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += asus_rt-ac85p
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/buffalo_wsr-1166dhp
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-24 05:51:53 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE/sysupgrade.bin := trx | pad-rootfs | append-metadata
|
2019-07-15 12:55:24 +00:00
|
|
|
IMAGE_SIZE := 15936k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Buffalo
|
|
|
|
|
DEVICE_MODEL := WSR-1166DHP
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += wsr-1166
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += buffalo_wsr-1166dhp
|
|
|
|
|
|
2019-03-23 13:45:42 +00:00
|
|
|
define Device/buffalo_wsr-2533dhpl
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-24 05:51:53 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-03-23 13:45:42 +00:00
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
DEVICE_VENDOR := Buffalo
|
|
|
|
|
DEVICE_MODEL := WSR-2533DHPL
|
2020-05-23 22:33:48 +00:00
|
|
|
DEVICE_ALT0_VENDOR := Buffalo
|
|
|
|
|
DEVICE_ALT0_MODEL := WSR-2533DHP
|
2019-03-23 13:45:42 +00:00
|
|
|
IMAGE/sysupgrade.bin := trx | pad-rootfs | append-metadata
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2019-03-23 13:45:42 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += buffalo_wsr-2533dhpl
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/buffalo_wsr-600dhp
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Buffalo
|
|
|
|
|
DEVICE_MODEL := WSR-600DHP
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-rt2800-pci
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += wsr-600
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += buffalo_wsr-600dhp
|
2016-04-01 07:11:48 +00:00
|
|
|
|
ramips: add support for D-Link DIR-867/DIR-882 A1
This patch adds support for D-Link DIR-867 A1 and D-Link DIR-882 A1. Given
the similarity of these devices, this patch also introduces a common DTS
shared between DIR-867 A1, DIR-878 A1 and DIR-882 A1.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 128 MB (DDR3)
* Flash: 16 MB (SPI NOR)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 2.0, 1 USB 3.0
* Buttons: Reset, WiFi Toggle, WPS
* LEDs: Power (green/orange), Internet (green/orange), WiFi 2.4G (green),
WiFi 5G (green), USB 2.0 (green), USB 3.0 (green)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
* DIR-867 wireless chips are limited to 3x3 streams at hardware level
* USB ports and related LEDs available only on DIR-882
Serial port:
* Parameters: 57600, 8N1
* Location: J1 header (close to the Reset, WiFi and WPS buttons)
* Pinout: 1 - VCC
2 - RXD
3 - TXD
4 - GND
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
Signed-off-by: Mateus B. Cassiano <mbc07@live.com>
[move DEVICE_VARIANT to individual definitions]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-15 21:45:39 +00:00
|
|
|
define Device/dlink_dir-8xx-a1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
ramips: add support for D-Link DIR-867/DIR-882 A1
This patch adds support for D-Link DIR-867 A1 and D-Link DIR-882 A1. Given
the similarity of these devices, this patch also introduces a common DTS
shared between DIR-867 A1, DIR-878 A1 and DIR-882 A1.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 128 MB (DDR3)
* Flash: 16 MB (SPI NOR)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 2.0, 1 USB 3.0
* Buttons: Reset, WiFi Toggle, WPS
* LEDs: Power (green/orange), Internet (green/orange), WiFi 2.4G (green),
WiFi 5G (green), USB 2.0 (green), USB 3.0 (green)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
* DIR-867 wireless chips are limited to 3x3 streams at hardware level
* USB ports and related LEDs available only on DIR-882
Serial port:
* Parameters: 57600, 8N1
* Location: J1 header (close to the Reset, WiFi and WPS buttons)
* Pinout: 1 - VCC
2 - RXD
3 - TXD
4 - GND
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
Signed-off-by: Mateus B. Cassiano <mbc07@live.com>
[move DEVICE_VARIANT to individual definitions]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-15 21:45:39 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
DEVICE_VENDOR := D-Link
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
ramips: add support for D-Link DIR-867/DIR-882 A1
This patch adds support for D-Link DIR-867 A1 and D-Link DIR-882 A1. Given
the similarity of these devices, this patch also introduces a common DTS
shared between DIR-867 A1, DIR-878 A1 and DIR-882 A1.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 128 MB (DDR3)
* Flash: 16 MB (SPI NOR)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 2.0, 1 USB 3.0
* Buttons: Reset, WiFi Toggle, WPS
* LEDs: Power (green/orange), Internet (green/orange), WiFi 2.4G (green),
WiFi 5G (green), USB 2.0 (green), USB 3.0 (green)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
* DIR-867 wireless chips are limited to 3x3 streams at hardware level
* USB ports and related LEDs available only on DIR-882
Serial port:
* Parameters: 57600, 8N1
* Location: J1 header (close to the Reset, WiFi and WPS buttons)
* Pinout: 1 - VCC
2 - RXD
3 - TXD
4 - GND
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
Signed-off-by: Mateus B. Cassiano <mbc07@live.com>
[move DEVICE_VARIANT to individual definitions]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-15 21:45:39 +00:00
|
|
|
KERNEL_INITRAMFS := $$(KERNEL) | uimage-padhdr 96
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | uimage-padhdr 96 |\
|
|
|
|
|
pad-rootfs | append-metadata | check-size
|
|
|
|
|
IMAGE/factory.bin := append-kernel | append-rootfs | uimage-padhdr 96 |\
|
|
|
|
|
check-size
|
|
|
|
|
endef
|
|
|
|
|
|
ramips: add support for D-Link DIR-1960 A1
This patch adds support for D-Link DIR-1960 A1. Given the similarity with
the DIR-1760/2660 A1, this patch also introduces a common DTSI which can
be shared with these devices, with support to be added in future commits.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 256 MB (DDR3)
* Flash: 128 MB (NAND)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 3.0
* Buttons: Reset, WPS
* LEDs: Power (white/orange), Internet (white/orange), WiFi 2.4G (white),
WiFi 5G (white), USB 3.0 (white)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
MAC addresses:
lan factory 0xe000 *:EB (label)
wan factory 0xe006 *:EE
2.4 factory 0xe000 +1 *:EC
5.0 factory 0xe000 +2 *:ED
Seems like vendor didn't replace the dummy entrys in the calibration data.
Signed-off-by: Josh Bendavid <joshbendavid@gmail.com>
[fix whitespace issues, create patch to merge DIR-1960 first, move
special WiFi MAC settings to DTS, extend commit message]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-14 15:39:21 +00:00
|
|
|
define Device/dlink_dir-xx60-a1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
ramips: add support for D-Link DIR-1960 A1
This patch adds support for D-Link DIR-1960 A1. Given the similarity with
the DIR-1760/2660 A1, this patch also introduces a common DTSI which can
be shared with these devices, with support to be added in future commits.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 256 MB (DDR3)
* Flash: 128 MB (NAND)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 3.0
* Buttons: Reset, WPS
* LEDs: Power (white/orange), Internet (white/orange), WiFi 2.4G (white),
WiFi 5G (white), USB 3.0 (white)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
MAC addresses:
lan factory 0xe000 *:EB (label)
wan factory 0xe006 *:EE
2.4 factory 0xe000 +1 *:EC
5.0 factory 0xe000 +2 *:ED
Seems like vendor didn't replace the dummy entrys in the calibration data.
Signed-off-by: Josh Bendavid <joshbendavid@gmail.com>
[fix whitespace issues, create patch to merge DIR-1960 first, move
special WiFi MAC settings to DTS, extend commit message]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-14 15:39:21 +00:00
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
KERNEL_SIZE := 4096k
|
|
|
|
|
IMAGE_SIZE := 40960k
|
|
|
|
|
UBINIZE_OPTS := -E 5
|
|
|
|
|
DEVICE_VENDOR := D-Link
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware kmod-usb3 \
|
|
|
|
|
kmod-usb-ledtrig-usbport
|
ramips: add support for D-Link DIR-1960 A1
This patch adds support for D-Link DIR-1960 A1. Given the similarity with
the DIR-1760/2660 A1, this patch also introduces a common DTSI which can
be shared with these devices, with support to be added in future commits.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 256 MB (DDR3)
* Flash: 128 MB (NAND)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 3.0
* Buttons: Reset, WPS
* LEDs: Power (white/orange), Internet (white/orange), WiFi 2.4G (white),
WiFi 5G (white), USB 3.0 (white)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
MAC addresses:
lan factory 0xe000 *:EB (label)
wan factory 0xe006 *:EE
2.4 factory 0xe000 +1 *:EC
5.0 factory 0xe000 +2 *:ED
Seems like vendor didn't replace the dummy entrys in the calibration data.
Signed-off-by: Josh Bendavid <joshbendavid@gmail.com>
[fix whitespace issues, create patch to merge DIR-1960 first, move
special WiFi MAC settings to DTS, extend commit message]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-14 15:39:21 +00:00
|
|
|
KERNEL := $$(KERNEL) | uimage-padhdr 96
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$(KERNEL_SIZE) | append-ubi | \
|
|
|
|
|
check-size
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/dlink_dir-1960-a1
|
|
|
|
|
$(Device/dlink_dir-xx60-a1)
|
|
|
|
|
DEVICE_MODEL := DIR-1960
|
|
|
|
|
DEVICE_VARIANT := A1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-1960-a1
|
|
|
|
|
|
ramips: add support for D-Link DIR-2660 A1
This patch adds support for D-Link DIR-2660 A1.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 256 MB (DDR3)
* Flash: 128 MB (NAND)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 2.0, 1 USB 3.0
* Buttons: Reset, WPS
* LEDs: Power (white/orange), Internet (white/orange), WiFi 2.4G (white),
WiFi 5G (white), USB 3.0 (white), USB 2.0 (white)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
MAC addresses:
lan factory 0xe000 *:a7 (label)
wan factory 0xe006 *:aa
2.4 factory 0xe000 +1 *:a8
5.0 factory 0xe000 +2 *:a9
Seems like vendor didn't replace the dummy entries in the calibration data.
Signed-off-by: Josh Bendavid <joshbendavid@gmail.com>
[rebase onto already merged DIR-1960 A1, add MAC addresses to commit message]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-14 15:39:21 +00:00
|
|
|
define Device/dlink_dir-2660-a1
|
|
|
|
|
$(Device/dlink_dir-xx60-a1)
|
|
|
|
|
DEVICE_MODEL := DIR-2660
|
|
|
|
|
DEVICE_VARIANT := A1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-2660-a1
|
|
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/dlink_dir-860l-b1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2018-12-29 18:25:00 +00:00
|
|
|
$(Device/seama)
|
2016-09-14 17:11:19 +00:00
|
|
|
BLOCKSIZE := 64k
|
2018-12-29 18:25:00 +00:00
|
|
|
SEAMA_SIGNATURE := wrgac13_dlink.2013gui_dir860lb
|
2020-04-19 18:49:11 +00:00
|
|
|
LOADER_TYPE := bin
|
2020-05-08 16:21:06 +00:00
|
|
|
KERNEL := kernel-bin | append-dtb | lzma | loader-kernel | relocate-kernel | \
|
|
|
|
|
lzma -a0 | uImage lzma
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := D-Link
|
|
|
|
|
DEVICE_MODEL := DIR-860L
|
|
|
|
|
DEVICE_VARIANT := B1
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb3 kmod-usb-ledtrig-usbport
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += dir-860l-b1
|
2016-04-01 07:11:48 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += dlink_dir-860l-b1
|
2016-04-01 07:11:48 +00:00
|
|
|
|
ramips: add support for D-Link DIR-867/DIR-882 A1
This patch adds support for D-Link DIR-867 A1 and D-Link DIR-882 A1. Given
the similarity of these devices, this patch also introduces a common DTS
shared between DIR-867 A1, DIR-878 A1 and DIR-882 A1.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 128 MB (DDR3)
* Flash: 16 MB (SPI NOR)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 2.0, 1 USB 3.0
* Buttons: Reset, WiFi Toggle, WPS
* LEDs: Power (green/orange), Internet (green/orange), WiFi 2.4G (green),
WiFi 5G (green), USB 2.0 (green), USB 3.0 (green)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
* DIR-867 wireless chips are limited to 3x3 streams at hardware level
* USB ports and related LEDs available only on DIR-882
Serial port:
* Parameters: 57600, 8N1
* Location: J1 header (close to the Reset, WiFi and WPS buttons)
* Pinout: 1 - VCC
2 - RXD
3 - TXD
4 - GND
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
Signed-off-by: Mateus B. Cassiano <mbc07@live.com>
[move DEVICE_VARIANT to individual definitions]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-15 21:45:39 +00:00
|
|
|
define Device/dlink_dir-867-a1
|
|
|
|
|
$(Device/dlink_dir-8xx-a1)
|
|
|
|
|
DEVICE_MODEL := DIR-867
|
|
|
|
|
DEVICE_VARIANT := A1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-867-a1
|
|
|
|
|
|
2020-07-10 03:49:20 +00:00
|
|
|
define Device/dlink_dir-878-a1
|
ramips: add support for D-Link DIR-867/DIR-882 A1
This patch adds support for D-Link DIR-867 A1 and D-Link DIR-882 A1. Given
the similarity of these devices, this patch also introduces a common DTS
shared between DIR-867 A1, DIR-878 A1 and DIR-882 A1.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 128 MB (DDR3)
* Flash: 16 MB (SPI NOR)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 2.0, 1 USB 3.0
* Buttons: Reset, WiFi Toggle, WPS
* LEDs: Power (green/orange), Internet (green/orange), WiFi 2.4G (green),
WiFi 5G (green), USB 2.0 (green), USB 3.0 (green)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
* DIR-867 wireless chips are limited to 3x3 streams at hardware level
* USB ports and related LEDs available only on DIR-882
Serial port:
* Parameters: 57600, 8N1
* Location: J1 header (close to the Reset, WiFi and WPS buttons)
* Pinout: 1 - VCC
2 - RXD
3 - TXD
4 - GND
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
Signed-off-by: Mateus B. Cassiano <mbc07@live.com>
[move DEVICE_VARIANT to individual definitions]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-15 21:45:39 +00:00
|
|
|
$(Device/dlink_dir-8xx-a1)
|
2020-07-10 03:49:20 +00:00
|
|
|
DEVICE_MODEL := DIR-878
|
|
|
|
|
DEVICE_VARIANT := A1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-878-a1
|
|
|
|
|
|
ramips: add support for D-Link DIR-867/DIR-882 A1
This patch adds support for D-Link DIR-867 A1 and D-Link DIR-882 A1. Given
the similarity of these devices, this patch also introduces a common DTS
shared between DIR-867 A1, DIR-878 A1 and DIR-882 A1.
Specifications:
* Board: AP-MTKH7-0002
* SoC: MediaTek MT7621AT
* RAM: 128 MB (DDR3)
* Flash: 16 MB (SPI NOR)
* WiFi: MediaTek MT7615N (x2)
* Switch: 1 WAN, 4 LAN (Gigabit)
* Ports: 1 USB 2.0, 1 USB 3.0
* Buttons: Reset, WiFi Toggle, WPS
* LEDs: Power (green/orange), Internet (green/orange), WiFi 2.4G (green),
WiFi 5G (green), USB 2.0 (green), USB 3.0 (green)
Notes:
* WiFi 2.4G and WiFi 5G LEDs are wired directly to the wireless chips
* DIR-867 wireless chips are limited to 3x3 streams at hardware level
* USB ports and related LEDs available only on DIR-882
Serial port:
* Parameters: 57600, 8N1
* Location: J1 header (close to the Reset, WiFi and WPS buttons)
* Pinout: 1 - VCC
2 - RXD
3 - TXD
4 - GND
Installation:
* D-Link Recovery GUI: power down the router, press and hold the reset
button, then re-plug it. Keep the reset button pressed until the power
LED starts flashing orange, manually assign a static IP address under
the 192.168.0.xxx subnet (e.g. 192.168.0.2) and go to http://192.168.0.1
* Some modern browsers may have problems flashing via the Recovery GUI,
if that occurs consider uploading the firmware through cURL:
curl -v -i -F "firmware=@file.bin" 192.168.0.1
Signed-off-by: Mateus B. Cassiano <mbc07@live.com>
[move DEVICE_VARIANT to individual definitions]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-15 21:45:39 +00:00
|
|
|
define Device/dlink_dir-882-a1
|
|
|
|
|
$(Device/dlink_dir-8xx-a1)
|
|
|
|
|
DEVICE_MODEL := DIR-882
|
|
|
|
|
DEVICE_VARIANT := A1
|
|
|
|
|
DEVICE_PACKAGES += kmod-usb3 kmod-usb-ledtrig-usbport
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += dlink_dir-882-a1
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/d-team_newifi-d2
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-18 06:19:38 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Newifi
|
|
|
|
|
DEVICE_MODEL := D2
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2018-02-22 16:08:14 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += d-team_newifi-d2
|
2018-02-22 16:08:14 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/d-team_pbr-m1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-09-13 10:57:11 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := PandoraBox
|
|
|
|
|
DEVICE_MODEL := PBR-M1
|
2020-03-05 13:57:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-mt7603 kmod-mt76x2 kmod-sdhci-mt7620 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb3 kmod-usb-ledtrig-usbport
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += pbr-m1
|
2018-12-08 18:55:56 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += d-team_pbr-m1
|
2018-12-08 18:55:56 +00:00
|
|
|
|
2019-11-15 22:21:22 +00:00
|
|
|
define Device/edimax_ra21s
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-07-03 05:51:03 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-11-15 22:21:22 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_VENDOR := Edimax
|
|
|
|
|
DEVICE_MODEL := RA21S
|
|
|
|
|
DEVICE_ALT0_VENDOR := Edimax
|
|
|
|
|
DEVICE_ALT0_MODEL := Gemini RA21S
|
|
|
|
|
IMAGES += factory.bin
|
2020-03-10 13:58:27 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size | \
|
2019-11-15 22:21:22 +00:00
|
|
|
elx-header 02020040 8844A2D168B45A2D
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2019-11-15 22:21:22 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += edimax_ra21s
|
|
|
|
|
|
2020-05-19 23:27:56 +00:00
|
|
|
define Device/edimax_re23s
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-05-19 23:27:56 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
|
|
|
|
IMAGE_SIZE := 15680k
|
|
|
|
|
DEVICE_VENDOR := Edimax
|
|
|
|
|
DEVICE_MODEL := RE23S
|
|
|
|
|
DEVICE_ALT0_VENDOR := Edimax
|
|
|
|
|
DEVICE_ALT0_MODEL := Gemini RE23S
|
|
|
|
|
IMAGE/sysupgrade.bin := append-kernel | append-rootfs | \
|
|
|
|
|
edimax-header -s CSYS -m RN76 -f 0x70000 -S 0x01100000 | pad-rootfs | \
|
|
|
|
|
append-metadata | check-size
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := append-kernel | append-rootfs | \
|
|
|
|
|
edimax-header -s CSYS -m RN76 -f 0x70000 -S 0x01100000 | pad-rootfs | \
|
|
|
|
|
check-size
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2020-05-19 23:27:56 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += edimax_re23s
|
|
|
|
|
|
2019-09-19 19:33:59 +00:00
|
|
|
define Device/edimax_rg21s
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-07-03 05:51:03 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-09-19 19:33:59 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_VENDOR := Edimax
|
|
|
|
|
DEVICE_MODEL := Gemini AC2600 RG21S
|
|
|
|
|
IMAGES += factory.bin
|
2020-03-10 13:58:27 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size | \
|
2019-12-19 18:40:33 +00:00
|
|
|
elx-header 02020038 8844A2D168B45A2D
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2019-09-19 19:33:59 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += edimax_rg21s
|
|
|
|
|
|
2018-06-15 15:27:51 +00:00
|
|
|
define Device/elecom_wrc-1167ghbk2-s
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2018-06-15 15:27:51 +00:00
|
|
|
IMAGE_SIZE := 15488k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := ELECOM
|
|
|
|
|
DEVICE_MODEL := WRC-1167GHBK2-S
|
2018-06-15 15:27:51 +00:00
|
|
|
IMAGES += factory.bin
|
2020-03-10 13:58:27 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size | \
|
2019-12-19 18:40:33 +00:00
|
|
|
elecom-wrc-factory WRC-1167GHBK2-S 0.00
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2018-06-15 15:27:51 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += elecom_wrc-1167ghbk2-s
|
|
|
|
|
|
2020-07-15 18:08:22 +00:00
|
|
|
define Device/elecom_wrc-gs
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-07-15 04:13:01 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
|
|
|
|
DEVICE_VENDOR := ELECOM
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size | \
|
2020-07-15 18:08:22 +00:00
|
|
|
elecom-wrc-gs-factory $$$$(ELECOM_HWNAME) 0.00
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2020-07-15 04:13:01 +00:00
|
|
|
endef
|
2020-07-15 18:08:22 +00:00
|
|
|
|
|
|
|
|
define Device/elecom_wrc-1750gs
|
|
|
|
|
$(Device/elecom_wrc-gs)
|
|
|
|
|
IMAGE_SIZE := 11264k
|
|
|
|
|
DEVICE_MODEL := WRC-1750GS
|
|
|
|
|
ELECOM_HWNAME := WRC-1750GS
|
|
|
|
|
endef
|
2020-07-15 04:13:01 +00:00
|
|
|
TARGET_DEVICES += elecom_wrc-1750gs
|
|
|
|
|
|
|
|
|
|
define Device/elecom_wrc-1750gsv
|
2020-07-15 18:08:22 +00:00
|
|
|
$(Device/elecom_wrc-gs)
|
2020-07-15 04:13:01 +00:00
|
|
|
IMAGE_SIZE := 11264k
|
|
|
|
|
DEVICE_MODEL := WRC-1750GSV
|
2020-07-15 18:08:22 +00:00
|
|
|
ELECOM_HWNAME := WRC-1750GSV
|
2020-07-15 04:13:01 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += elecom_wrc-1750gsv
|
|
|
|
|
|
2018-08-18 23:05:15 +00:00
|
|
|
define Device/elecom_wrc-1900gst
|
2020-07-15 18:08:22 +00:00
|
|
|
$(Device/elecom_wrc-gs)
|
2018-08-18 23:05:15 +00:00
|
|
|
IMAGE_SIZE := 11264k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := WRC-1900GST
|
2020-07-15 18:08:22 +00:00
|
|
|
ELECOM_HWNAME := WRC-1900GST
|
2018-08-18 23:05:15 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += elecom_wrc-1900gst
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/elecom_wrc-2533gst
|
2020-07-15 18:08:22 +00:00
|
|
|
$(Device/elecom_wrc-gs)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 11264k
|
|
|
|
|
DEVICE_MODEL := WRC-2533GST
|
2020-07-15 18:08:22 +00:00
|
|
|
ELECOM_HWNAME := WRC-2533GST
|
2017-02-27 20:59:50 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += elecom_wrc-2533gst
|
2017-02-27 20:59:50 +00:00
|
|
|
|
2020-05-16 08:39:26 +00:00
|
|
|
define Device/elecom_wrc-2533gst2
|
2020-07-15 18:08:22 +00:00
|
|
|
$(Device/elecom_wrc-gs)
|
2020-05-16 08:39:26 +00:00
|
|
|
IMAGE_SIZE := 24576k
|
|
|
|
|
DEVICE_MODEL := WRC-2533GST2
|
2020-07-15 18:08:22 +00:00
|
|
|
ELECOM_HWNAME := WRC-2533GST2
|
2020-05-16 08:39:26 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += elecom_wrc-2533gst2
|
|
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/firefly_firewrt
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Firefly
|
|
|
|
|
DEVICE_MODEL := FireWRT
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb3 kmod-usb-ledtrig-usbport
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += firewrt
|
2016-04-01 07:11:48 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += firefly_firewrt
|
2016-04-01 07:11:48 +00:00
|
|
|
|
2018-12-27 05:39:16 +00:00
|
|
|
define Device/gehua_ghl-r-001
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := GeHua
|
|
|
|
|
DEVICE_MODEL := GHL-R-001
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2018-12-27 05:39:16 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += gehua_ghl-r-001
|
|
|
|
|
|
2018-05-27 00:26:14 +00:00
|
|
|
define Device/gnubee_gb-pc1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := GnuBee
|
|
|
|
|
DEVICE_MODEL := Personal Cloud One
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-usb3 kmod-sdhci-mt7620 -wpad-basic-wolfssl
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2017-07-22 01:15:56 +00:00
|
|
|
endef
|
2018-05-27 00:26:14 +00:00
|
|
|
TARGET_DEVICES += gnubee_gb-pc1
|
2017-07-22 01:15:56 +00:00
|
|
|
|
2018-02-17 08:54:57 +00:00
|
|
|
define Device/gnubee_gb-pc2
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := GnuBee
|
|
|
|
|
DEVICE_MODEL := Personal Cloud Two
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-usb3 kmod-sdhci-mt7620 -wpad-basic-wolfssl
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2018-02-05 00:24:15 +00:00
|
|
|
endef
|
2018-02-17 08:54:57 +00:00
|
|
|
TARGET_DEVICES += gnubee_gb-pc2
|
2018-02-05 00:24:15 +00:00
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/hiwifi_hc5962
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2017-02-22 12:47:22 +00:00
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
2020-04-06 05:17:43 +00:00
|
|
|
KERNEL_SIZE := 4096k
|
2017-02-22 12:47:22 +00:00
|
|
|
UBINIZE_OPTS := -E 5
|
2019-07-15 12:55:24 +00:00
|
|
|
IMAGE_SIZE := 32768k
|
2017-02-22 12:47:22 +00:00
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
2019-12-19 18:40:33 +00:00
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$(KERNEL_SIZE) | append-ubi | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := HiWiFi
|
|
|
|
|
DEVICE_MODEL := HC5962
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3
|
2017-02-22 12:47:22 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += hiwifi_hc5962
|
2017-02-22 12:47:22 +00:00
|
|
|
|
ramips: add support for I-O DATA WN-AX1167GR
I-O DATA WN-AX1167GR is a 2.4/5 GHz band 11ac router, based on
MediaTek MT7621A.
Specification:
- MT7621A (2-Cores, 4-Threads)
- 64 MB of RAM (DDR2)
- 16 MB of Flash (SPI)
- 2T2R 2.4/5 GHz
- 5x 10/100/1000 Mbps Ethernet
- 2x LEDs, 4x keys (2x buttons, 1x slide switch)
- UART header on PCB
- Vcc, GND, TX, RX from ethernet port side
- baudrate: 115200 bps (U-Boot, OpenWrt)
Stock firmware:
In the stock firmware, WN-AX1167GR has two os images each composed of
Linux kernel and rootfs.
These images are stored in "Kernel" and "app" partition of the
following partitions, respectively.
(excerpt from dmesg):
MX25L12805D(c2 2018c220) (16384 Kbytes)
mtd .name = raspi, .size = 0x01000000 (16M) .erasesize = 0x00010000 (64K) .numeraseregions = 0
Creating 10 MTD partitions on "raspi":
0x000000000000-0x000001000000 : "ALL"
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config "
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000060000 : "iNIC_rf"
0x000000060000-0x0000007e0000 : "Kernel"
0x000000800000-0x000000f80000 : "app"
0x000000f90000-0x000000fa0000 : "Key"
0x000000fa0000-0x000000fb0000 : "backup"
0x000000fb0000-0x000001000000 : "storage"
The flag for boot partition is stored in "Key" partition, and U-Boot
reads this and determines the partition to boot.
If the image that U-Boot first reads according to the flag is
"Bad Magic Number", U-Boot then tries to boot from the other image.
If the second image is correct, change the flag to the number
corresponding to that image and boot from that image.
(example):
## Booting image at bc800000 ...
Bad Magic Number,FFFFFFFF
Boot from KERNEL 1 !!
## Booting image at bc060000 ...
Image Name: MIPS OpenWrt Linux-4.14.50
Image Type: MIPS Linux kernel Image (lzma compressed)
Data Size: 1865917 Bytes = 1.8 MB
Load Address: 80001000
Entry Point: 80001000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
raspi_erase_write: offs:f90000, count:34
.
.
Done!
Starting kernel ...
Flash instruction using factory image:
1. Connect the computer to the LAN port of WN-AX1167GR
2. Connect power cable to WN-AX1167GR and turn on it
3. Access to "192.168.0.1" on the web browser and open firmware
update page ("ファームウェア")
4. Select the OpenWrt factory image and perform firmware update
5. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-AX1167GR
6. Wait ~180 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-06-27 13:47:13 +00:00
|
|
|
define Device/iodata_wn-ax1167gr
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-24 05:51:53 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
ramips: add support for I-O DATA WN-AX1167GR
I-O DATA WN-AX1167GR is a 2.4/5 GHz band 11ac router, based on
MediaTek MT7621A.
Specification:
- MT7621A (2-Cores, 4-Threads)
- 64 MB of RAM (DDR2)
- 16 MB of Flash (SPI)
- 2T2R 2.4/5 GHz
- 5x 10/100/1000 Mbps Ethernet
- 2x LEDs, 4x keys (2x buttons, 1x slide switch)
- UART header on PCB
- Vcc, GND, TX, RX from ethernet port side
- baudrate: 115200 bps (U-Boot, OpenWrt)
Stock firmware:
In the stock firmware, WN-AX1167GR has two os images each composed of
Linux kernel and rootfs.
These images are stored in "Kernel" and "app" partition of the
following partitions, respectively.
(excerpt from dmesg):
MX25L12805D(c2 2018c220) (16384 Kbytes)
mtd .name = raspi, .size = 0x01000000 (16M) .erasesize = 0x00010000 (64K) .numeraseregions = 0
Creating 10 MTD partitions on "raspi":
0x000000000000-0x000001000000 : "ALL"
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config "
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000060000 : "iNIC_rf"
0x000000060000-0x0000007e0000 : "Kernel"
0x000000800000-0x000000f80000 : "app"
0x000000f90000-0x000000fa0000 : "Key"
0x000000fa0000-0x000000fb0000 : "backup"
0x000000fb0000-0x000001000000 : "storage"
The flag for boot partition is stored in "Key" partition, and U-Boot
reads this and determines the partition to boot.
If the image that U-Boot first reads according to the flag is
"Bad Magic Number", U-Boot then tries to boot from the other image.
If the second image is correct, change the flag to the number
corresponding to that image and boot from that image.
(example):
## Booting image at bc800000 ...
Bad Magic Number,FFFFFFFF
Boot from KERNEL 1 !!
## Booting image at bc060000 ...
Image Name: MIPS OpenWrt Linux-4.14.50
Image Type: MIPS Linux kernel Image (lzma compressed)
Data Size: 1865917 Bytes = 1.8 MB
Load Address: 80001000
Entry Point: 80001000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
raspi_erase_write: offs:f90000, count:34
.
.
Done!
Starting kernel ...
Flash instruction using factory image:
1. Connect the computer to the LAN port of WN-AX1167GR
2. Connect power cable to WN-AX1167GR and turn on it
3. Access to "192.168.0.1" on the web browser and open firmware
update page ("ファームウェア")
4. Select the OpenWrt factory image and perform firmware update
5. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-AX1167GR
6. Wait ~180 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-06-27 13:47:13 +00:00
|
|
|
IMAGE_SIZE := 15552k
|
|
|
|
|
KERNEL_INITRAMFS := $$(KERNEL) | \
|
2019-12-19 18:40:33 +00:00
|
|
|
iodata-factory 7864320 4 0x1055 $(KDIR)/tmp/$$(KERNEL_INITRAMFS_PREFIX)-factory.bin
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := I-O DATA
|
|
|
|
|
DEVICE_MODEL := WN-AX1167GR
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2
|
ramips: add support for I-O DATA WN-AX1167GR
I-O DATA WN-AX1167GR is a 2.4/5 GHz band 11ac router, based on
MediaTek MT7621A.
Specification:
- MT7621A (2-Cores, 4-Threads)
- 64 MB of RAM (DDR2)
- 16 MB of Flash (SPI)
- 2T2R 2.4/5 GHz
- 5x 10/100/1000 Mbps Ethernet
- 2x LEDs, 4x keys (2x buttons, 1x slide switch)
- UART header on PCB
- Vcc, GND, TX, RX from ethernet port side
- baudrate: 115200 bps (U-Boot, OpenWrt)
Stock firmware:
In the stock firmware, WN-AX1167GR has two os images each composed of
Linux kernel and rootfs.
These images are stored in "Kernel" and "app" partition of the
following partitions, respectively.
(excerpt from dmesg):
MX25L12805D(c2 2018c220) (16384 Kbytes)
mtd .name = raspi, .size = 0x01000000 (16M) .erasesize = 0x00010000 (64K) .numeraseregions = 0
Creating 10 MTD partitions on "raspi":
0x000000000000-0x000001000000 : "ALL"
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config "
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000060000 : "iNIC_rf"
0x000000060000-0x0000007e0000 : "Kernel"
0x000000800000-0x000000f80000 : "app"
0x000000f90000-0x000000fa0000 : "Key"
0x000000fa0000-0x000000fb0000 : "backup"
0x000000fb0000-0x000001000000 : "storage"
The flag for boot partition is stored in "Key" partition, and U-Boot
reads this and determines the partition to boot.
If the image that U-Boot first reads according to the flag is
"Bad Magic Number", U-Boot then tries to boot from the other image.
If the second image is correct, change the flag to the number
corresponding to that image and boot from that image.
(example):
## Booting image at bc800000 ...
Bad Magic Number,FFFFFFFF
Boot from KERNEL 1 !!
## Booting image at bc060000 ...
Image Name: MIPS OpenWrt Linux-4.14.50
Image Type: MIPS Linux kernel Image (lzma compressed)
Data Size: 1865917 Bytes = 1.8 MB
Load Address: 80001000
Entry Point: 80001000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
raspi_erase_write: offs:f90000, count:34
.
.
Done!
Starting kernel ...
Flash instruction using factory image:
1. Connect the computer to the LAN port of WN-AX1167GR
2. Connect power cable to WN-AX1167GR and turn on it
3. Access to "192.168.0.1" on the web browser and open firmware
update page ("ファームウェア")
4. Select the OpenWrt factory image and perform firmware update
5. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-AX1167GR
6. Wait ~180 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-06-27 13:47:13 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-ax1167gr
|
|
|
|
|
|
2020-04-27 10:07:01 +00:00
|
|
|
define Device/iodata_nand
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-27 10:07:01 +00:00
|
|
|
DEVICE_VENDOR := I-O DATA
|
2019-08-26 11:27:22 +00:00
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
UBINIZE_OPTS := -E 5
|
|
|
|
|
KERNEL_SIZE := 4096k
|
|
|
|
|
IMAGE_SIZE := 51200k
|
2020-04-26 03:24:33 +00:00
|
|
|
LOADER_TYPE := bin
|
|
|
|
|
KERNEL := kernel-bin | append-dtb | lzma | loader-kernel | lzma | uImage lzma
|
2020-04-27 10:07:01 +00:00
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/iodata_wn-ax1167gr2
|
|
|
|
|
$(Device/iodata_nand)
|
|
|
|
|
UIMAGE_MAGIC := 0x434f4d42
|
|
|
|
|
DEVICE_MODEL := WN-AX1167GR2
|
2020-04-28 14:45:41 +00:00
|
|
|
KERNEL_INITRAMFS := $(KERNEL_DTB) | loader-kernel | lzma | \
|
|
|
|
|
custom-initramfs-uimage 3.10(XBC.1)b10 | iodata-mstc-header
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2019-08-26 11:27:22 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-ax1167gr2
|
|
|
|
|
|
ramips: add support for I-O DATA WN-AX2033GR
I-O DATA WN-AX2033GR is roughly the same as I-O DATA
WN-AX1167GR2. The difference is Wi-Fi feature.
Specification
=============
- SoC: MediaTek MT7621A
- RAM: DDR3 128 MiB
- Flash Memory: NAND 128 MiB (Spansion S34ML01G200TF100)
- Wi-Fi: MediaTek MT7603E
- Wi-Fi: MediaTek MT7615
- Ethernet: 5x 10 Mbps / 100 Mbps / 1000 Mbps (1x WAN, 4x LAN)
- LED: 2x green LED
- Input: 2x tactile switch, 1x slide switch
- Serial console: 57600bps, PCB through hole J5 (Vcc, TX, RX, NC, GND)
- Power: DC 12V
This device only supports channel 1-13 and 36-140.
Thus, narrower frequency limits compared to other devices are required
for limiting wi-fi frequency correctly.
Without this, non-supported frequencies are activated.
Flash instructions
==================
1. Open the router management page (192.168.0.1).
2. Update router firmware using "initramfs-kernel.bin".
3. After updating, run sysupgrade with "sysupgrade.bin".
Recovery instructions
=====================
WN-AX2033GR contains Zyxel Z-LOADER
1. Setup TFTP server (IP address: 10.10.10.3).
2. Put official firmware into TFTP server directory (distribution site:
https://www.iodata.jp/lib/software/w/2068.htm)
3. Connect WX-AX2033GR Ethernet port and computer that runs TFTP server.
4. Connect to serial console.
5. Interrupt booting by Esc key.
6. Flash firmware using "ATNR 1,[firmware filename]" command.
Signed-off-by: Yanase Yuki <dev@zpc.sakura.ne.jp>
[adjust for kernel 5.4, add recovery instructions/frequency comment]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-02-06 03:00:47 +00:00
|
|
|
define Device/iodata_wn-ax2033gr
|
2020-04-27 10:07:01 +00:00
|
|
|
$(Device/iodata_nand)
|
ramips: add support for I-O DATA WN-AX2033GR
I-O DATA WN-AX2033GR is roughly the same as I-O DATA
WN-AX1167GR2. The difference is Wi-Fi feature.
Specification
=============
- SoC: MediaTek MT7621A
- RAM: DDR3 128 MiB
- Flash Memory: NAND 128 MiB (Spansion S34ML01G200TF100)
- Wi-Fi: MediaTek MT7603E
- Wi-Fi: MediaTek MT7615
- Ethernet: 5x 10 Mbps / 100 Mbps / 1000 Mbps (1x WAN, 4x LAN)
- LED: 2x green LED
- Input: 2x tactile switch, 1x slide switch
- Serial console: 57600bps, PCB through hole J5 (Vcc, TX, RX, NC, GND)
- Power: DC 12V
This device only supports channel 1-13 and 36-140.
Thus, narrower frequency limits compared to other devices are required
for limiting wi-fi frequency correctly.
Without this, non-supported frequencies are activated.
Flash instructions
==================
1. Open the router management page (192.168.0.1).
2. Update router firmware using "initramfs-kernel.bin".
3. After updating, run sysupgrade with "sysupgrade.bin".
Recovery instructions
=====================
WN-AX2033GR contains Zyxel Z-LOADER
1. Setup TFTP server (IP address: 10.10.10.3).
2. Put official firmware into TFTP server directory (distribution site:
https://www.iodata.jp/lib/software/w/2068.htm)
3. Connect WX-AX2033GR Ethernet port and computer that runs TFTP server.
4. Connect to serial console.
5. Interrupt booting by Esc key.
6. Flash firmware using "ATNR 1,[firmware filename]" command.
Signed-off-by: Yanase Yuki <dev@zpc.sakura.ne.jp>
[adjust for kernel 5.4, add recovery instructions/frequency comment]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-02-06 03:00:47 +00:00
|
|
|
UIMAGE_MAGIC := 0x434f4d42
|
|
|
|
|
DEVICE_MODEL := WN-AX2033GR
|
2020-04-28 14:45:41 +00:00
|
|
|
KERNEL_INITRAMFS := $(KERNEL_DTB) | loader-kernel | lzma | \
|
|
|
|
|
custom-initramfs-uimage 3.10(VST.1)C10 | iodata-mstc-header
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt7615e kmod-mt7615-firmware
|
ramips: add support for I-O DATA WN-AX2033GR
I-O DATA WN-AX2033GR is roughly the same as I-O DATA
WN-AX1167GR2. The difference is Wi-Fi feature.
Specification
=============
- SoC: MediaTek MT7621A
- RAM: DDR3 128 MiB
- Flash Memory: NAND 128 MiB (Spansion S34ML01G200TF100)
- Wi-Fi: MediaTek MT7603E
- Wi-Fi: MediaTek MT7615
- Ethernet: 5x 10 Mbps / 100 Mbps / 1000 Mbps (1x WAN, 4x LAN)
- LED: 2x green LED
- Input: 2x tactile switch, 1x slide switch
- Serial console: 57600bps, PCB through hole J5 (Vcc, TX, RX, NC, GND)
- Power: DC 12V
This device only supports channel 1-13 and 36-140.
Thus, narrower frequency limits compared to other devices are required
for limiting wi-fi frequency correctly.
Without this, non-supported frequencies are activated.
Flash instructions
==================
1. Open the router management page (192.168.0.1).
2. Update router firmware using "initramfs-kernel.bin".
3. After updating, run sysupgrade with "sysupgrade.bin".
Recovery instructions
=====================
WN-AX2033GR contains Zyxel Z-LOADER
1. Setup TFTP server (IP address: 10.10.10.3).
2. Put official firmware into TFTP server directory (distribution site:
https://www.iodata.jp/lib/software/w/2068.htm)
3. Connect WX-AX2033GR Ethernet port and computer that runs TFTP server.
4. Connect to serial console.
5. Interrupt booting by Esc key.
6. Flash firmware using "ATNR 1,[firmware filename]" command.
Signed-off-by: Yanase Yuki <dev@zpc.sakura.ne.jp>
[adjust for kernel 5.4, add recovery instructions/frequency comment]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-02-06 03:00:47 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-ax2033gr
|
|
|
|
|
|
2019-04-09 05:48:31 +00:00
|
|
|
define Device/iodata_wn-dx1167r
|
2020-04-27 10:07:01 +00:00
|
|
|
$(Device/iodata_nand)
|
2019-04-09 05:48:31 +00:00
|
|
|
UIMAGE_MAGIC := 0x434f4d43
|
|
|
|
|
DEVICE_MODEL := WN-DX1167R
|
2020-04-28 14:45:41 +00:00
|
|
|
KERNEL_INITRAMFS := $(KERNEL_DTB) | loader-kernel | lzma | \
|
|
|
|
|
custom-initramfs-uimage 3.10(XIK.1)b10 | iodata-mstc-header
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2019-04-09 05:48:31 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-dx1167r
|
|
|
|
|
|
ramips: add support for I-O DATA WN-GX300GR
I-O DATA WN-GX300GR is a 2.4 GHz band 11n router, based on MediaTek
MT7621S.
Specification:
- MT7621S (1-Core, 2-Threads)
- 64 MB of RAM
- 8 MB of Flash (SPI)
- 2T2R 2.4 GHz
- 5x 10/100/1000 Mbps Ethernet
- 2x LEDs, 4x keys (2x buttons, 1x slide switch)
- UART header on PCB
- Vcc, GND, TX, RX from ethernet port side
- baudrate: 115200 bps (U-Boot, OpenWrt)
Flash instruction using initramfs image:
1. Connect serial cable to UART header
2. Rename OpenWrt initramfs image for WN-GX300GR to "uImageWN-GX300GR"
and place it in the TFTP directory
3. Set the IP address of the computer to 192.168.99.8, connect to the
LAN port of WN-GX300GR, and start the TFTP server on the computer
4. Connect power cable to WN-GX300GR and turn on the router
5. Press "1" key on the serial console to interrupt boot process on
U-Boot, press Enter key 3 times and start firmware download via TFTP
6. WN-GX300GR downloads initramfs image and boot with it
7. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-GX300GR
8. Wait ~150 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-05-16 12:42:48 +00:00
|
|
|
define Device/iodata_wn-gx300gr
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-24 05:51:53 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-15 12:55:40 +00:00
|
|
|
IMAGE_SIZE := 7616k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := I-O DATA
|
|
|
|
|
DEVICE_MODEL := WN-GX300GR
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603
|
ramips: add support for I-O DATA WN-GX300GR
I-O DATA WN-GX300GR is a 2.4 GHz band 11n router, based on MediaTek
MT7621S.
Specification:
- MT7621S (1-Core, 2-Threads)
- 64 MB of RAM
- 8 MB of Flash (SPI)
- 2T2R 2.4 GHz
- 5x 10/100/1000 Mbps Ethernet
- 2x LEDs, 4x keys (2x buttons, 1x slide switch)
- UART header on PCB
- Vcc, GND, TX, RX from ethernet port side
- baudrate: 115200 bps (U-Boot, OpenWrt)
Flash instruction using initramfs image:
1. Connect serial cable to UART header
2. Rename OpenWrt initramfs image for WN-GX300GR to "uImageWN-GX300GR"
and place it in the TFTP directory
3. Set the IP address of the computer to 192.168.99.8, connect to the
LAN port of WN-GX300GR, and start the TFTP server on the computer
4. Connect power cable to WN-GX300GR and turn on the router
5. Press "1" key on the serial console to interrupt boot process on
U-Boot, press Enter key 3 times and start firmware download via TFTP
6. WN-GX300GR downloads initramfs image and boot with it
7. On the initramfs image, execute "mtd erase firmware" to erase stock
firmware and execute sysupgrade with sysupgrade image for WN-GX300GR
8. Wait ~150 seconds to complete flasing
Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
2018-05-16 12:42:48 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wn-gx300gr
|
|
|
|
|
|
2019-07-11 05:41:08 +00:00
|
|
|
define Device/iodata_wnpr2600g
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-24 05:51:53 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-11 05:41:08 +00:00
|
|
|
DEVICE_VENDOR := I-O DATA
|
|
|
|
|
DEVICE_MODEL := WNPR2600G
|
|
|
|
|
IMAGE_SIZE := 13952k
|
|
|
|
|
IMAGES += factory.bin
|
2020-03-10 13:58:27 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size | \
|
2019-12-19 18:40:33 +00:00
|
|
|
elx-header 0104003a 8844A2D168B45A2D
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2019-07-11 05:41:08 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iodata_wnpr2600g
|
|
|
|
|
|
2019-11-11 16:25:31 +00:00
|
|
|
define Device/iptime_a6ns-m
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-11-11 16:25:31 +00:00
|
|
|
IMAGE_SIZE := 16128k
|
|
|
|
|
UIMAGE_NAME := a6nm
|
|
|
|
|
DEVICE_VENDOR := ipTIME
|
|
|
|
|
DEVICE_MODEL := A6ns-M
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware kmod-usb3 \
|
|
|
|
|
kmod-usb-ledtrig-usbport
|
2019-11-11 16:25:31 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iptime_a6ns-m
|
|
|
|
|
|
2019-10-06 20:06:31 +00:00
|
|
|
define Device/iptime_a8004t
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-10-06 20:06:31 +00:00
|
|
|
IMAGE_SIZE := 16128k
|
|
|
|
|
UIMAGE_NAME := a8004t
|
|
|
|
|
DEVICE_VENDOR := ipTIME
|
|
|
|
|
DEVICE_MODEL := A8004T
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware kmod-usb3
|
2019-10-06 20:06:31 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iptime_a8004t
|
|
|
|
|
|
2019-12-13 16:24:19 +00:00
|
|
|
define Device/jcg_jhr-ac876m
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-12-13 16:24:19 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
IMAGES += factory.bin
|
2020-05-08 16:21:06 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size | jcg-header 89.1
|
2019-12-13 16:24:19 +00:00
|
|
|
JCG_MAXSIZE := 16064k
|
|
|
|
|
DEVICE_VENDOR := JCG
|
|
|
|
|
DEVICE_MODEL := JHR-AC876M
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware kmod-usb3 \
|
|
|
|
|
kmod-usb-ledtrig-usbport
|
2019-12-13 16:24:19 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += jcg_jhr-ac876m
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/lenovo_newifi-d1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-18 06:19:38 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Newifi
|
|
|
|
|
DEVICE_MODEL := D1
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 kmod-sdhci-mt7620 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += newifi-d1
|
2019-06-25 15:32:20 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += lenovo_newifi-d1
|
2019-06-25 15:32:20 +00:00
|
|
|
|
2020-07-16 00:24:43 +00:00
|
|
|
define Device/linksys_ea7xxx
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
ramips: add support for Linksys EA7500 v2
The Linksys EA7500 v2 is advertised as AC1900, but its internal
hardware is AC2600 capable.
Hardware
--------
SoC: Mediatek MT7621AT (880 MHz, 2 cores 4 threads)
RAM: 256M (Nanya NT5CC128M16IP-DI)
FLASH: 128MB NAND (Macronix MX30LF1G18AC-TI)
ETH: 5x 10/100/1000 Mbps Ethernet (MT7530)
WIFI:
- 2.4GHz: 1x MT7615N (4x4:4)
- 5GHz: 1x MT7615N (4x4:4)
- 4 antennas: 3 external detachable antennas and 1 internal
USB:
- 1x USB 3.0
- 1x USB 2.0
BTN:
- 1x Reset button
- 1x WPS button
LEDS:
- 1x White led (Power)
- 6x Green leds (link lan1-lan4, link wan, wps)
- 5x Orange leds (act lan1-lan4, act wan) (working but unmodifiable)
Everything works correctly.
Installation
------------
The “factory” openwrt image can be flashed directly from OEM stock
firmware. After the flash the router will reboot automatically.
However, due to the dual boot system, the first installation could fail
(if you want to know why, read the footnotes).
If the flash succeed and you can reach OpenWrt through the web
interface or ssh, you are done.
Otherwise the router will try to boot 3 times and then will
automatically boot the OEM firmware (don’t turn off the router.
Simply wait and try to reach the router through the web interface
every now and then, it will take few minutes).
After this, you should be back in the OEM firmware.
Now you have to flash the OEM Firmware over itself using the OEM web
interface (I tested it using the FW_EA7500v2_2.0.8.194281_prod.img
downloaded from the Linksys website).
When the router reboots flash the “factory” OpenWrt image and this
time it should work.
After the OpenWrt installation you have to use the sysupgrade image
for future updates.
Restore OEM Firmware
--------------------
After the OpenWrt flash, the OEM firmware is still stored in the
second partition thanks to the dual boot system.
You can switch from OpenWrt to OEM firmware and vice-versa failing
the boot 3 times in a row:
1) power on the router
2) wait 15 seconds
3) power off the router
4) repeat steps 1-2-3 twice more.
5) power on the router and you should be in the “other” firmware
If you want to completely remove OpenWrt from your router, switch to
the OEM firmware and then flash OEM firmware from the web interface
as a normal update.
This procedure will overwrite the OpenWrt partition.
Footnotes
---------
The Linksys EA7500-v2 has a dual boot system to avoid bricks.
This system works using 2 pair of partitions:
1) "kernel" and "rootfs"
2) "alt_kernel" and "alt_rootfs".
After 3 failed boot attempts, the bootloader tries to boot the other
pair of partitions and so on.
This system is managed by the bootloader, which writes a bootcount in
the s_env partition, and if successfully booted, the system add a
"zero-bootcount" after the previous value.
A system update performed from OEM firmware, writes the firmware on the
other pair of partitions and sets the bootloader to boot the new pair
of partitions editing the “boot_part” variable in the bootloader vars.
Effectively it's a quick and safe system to switch the selected boot
partition.
Another way to switch the boot partition is:
1) power on the router
2) wait 15 seconds
3) power off the router
4) repeat steps 1-2-3 twice more.
5) power on the router and you should be in the “other” firmware
In this OpenWrt port, this dual boot system is partially working
because the bootloader sets the right rootfs partition in the cmdline
but unfortunately OpenWrt for ramips platform overwrites the cmdline
so is not possible to detect the right rootfs partition.
Because all of this, I preferred to simply use the first pair of
partitions and set read-only the other pair.
However this solution is not optimal because is not possible to know
without opening the case which is the current booted partition.
Let’s take for example a router booting the OEM firmware from the first
pair of partitions. If we flash the OpenWrt image, it will be written
on the second pair. In this situation the router will bootloop 3 times
and then will automatically come back to the first pair of partitions
containg the OEM firmware.
In this situation, to flash OpenWrt correctly is necessary to switch
the booting partition, flashing again the OEM firmware over itself.
At this point the OEM firmware is on both pair of partitions but the
current booted pair is the second one.
Now, flashing the OpenWrt factory image will write the firmware on
the first pair and then will boot correctly.
If this limitation in the ramips platform about the cmdline will be
fixed, the dual boot system can also be implemented in OpenWrt with
almost no effort.
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
Co-Developed-by: Jackson Lim <jackcolentern@gmail.com>
Signed-off-by: Jackson Lim <jackcolentern@gmail.com>
2020-05-11 23:27:50 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
|
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
KERNEL_SIZE := 4096k
|
|
|
|
|
IMAGE_SIZE := 36864k
|
|
|
|
|
DEVICE_VENDOR := Linksys
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb3 kmod-mt7615e kmod-mt7615-firmware \
|
2020-07-16 00:24:43 +00:00
|
|
|
uboot-envtools
|
ramips: add support for Linksys EA7500 v2
The Linksys EA7500 v2 is advertised as AC1900, but its internal
hardware is AC2600 capable.
Hardware
--------
SoC: Mediatek MT7621AT (880 MHz, 2 cores 4 threads)
RAM: 256M (Nanya NT5CC128M16IP-DI)
FLASH: 128MB NAND (Macronix MX30LF1G18AC-TI)
ETH: 5x 10/100/1000 Mbps Ethernet (MT7530)
WIFI:
- 2.4GHz: 1x MT7615N (4x4:4)
- 5GHz: 1x MT7615N (4x4:4)
- 4 antennas: 3 external detachable antennas and 1 internal
USB:
- 1x USB 3.0
- 1x USB 2.0
BTN:
- 1x Reset button
- 1x WPS button
LEDS:
- 1x White led (Power)
- 6x Green leds (link lan1-lan4, link wan, wps)
- 5x Orange leds (act lan1-lan4, act wan) (working but unmodifiable)
Everything works correctly.
Installation
------------
The “factory” openwrt image can be flashed directly from OEM stock
firmware. After the flash the router will reboot automatically.
However, due to the dual boot system, the first installation could fail
(if you want to know why, read the footnotes).
If the flash succeed and you can reach OpenWrt through the web
interface or ssh, you are done.
Otherwise the router will try to boot 3 times and then will
automatically boot the OEM firmware (don’t turn off the router.
Simply wait and try to reach the router through the web interface
every now and then, it will take few minutes).
After this, you should be back in the OEM firmware.
Now you have to flash the OEM Firmware over itself using the OEM web
interface (I tested it using the FW_EA7500v2_2.0.8.194281_prod.img
downloaded from the Linksys website).
When the router reboots flash the “factory” OpenWrt image and this
time it should work.
After the OpenWrt installation you have to use the sysupgrade image
for future updates.
Restore OEM Firmware
--------------------
After the OpenWrt flash, the OEM firmware is still stored in the
second partition thanks to the dual boot system.
You can switch from OpenWrt to OEM firmware and vice-versa failing
the boot 3 times in a row:
1) power on the router
2) wait 15 seconds
3) power off the router
4) repeat steps 1-2-3 twice more.
5) power on the router and you should be in the “other” firmware
If you want to completely remove OpenWrt from your router, switch to
the OEM firmware and then flash OEM firmware from the web interface
as a normal update.
This procedure will overwrite the OpenWrt partition.
Footnotes
---------
The Linksys EA7500-v2 has a dual boot system to avoid bricks.
This system works using 2 pair of partitions:
1) "kernel" and "rootfs"
2) "alt_kernel" and "alt_rootfs".
After 3 failed boot attempts, the bootloader tries to boot the other
pair of partitions and so on.
This system is managed by the bootloader, which writes a bootcount in
the s_env partition, and if successfully booted, the system add a
"zero-bootcount" after the previous value.
A system update performed from OEM firmware, writes the firmware on the
other pair of partitions and sets the bootloader to boot the new pair
of partitions editing the “boot_part” variable in the bootloader vars.
Effectively it's a quick and safe system to switch the selected boot
partition.
Another way to switch the boot partition is:
1) power on the router
2) wait 15 seconds
3) power off the router
4) repeat steps 1-2-3 twice more.
5) power on the router and you should be in the “other” firmware
In this OpenWrt port, this dual boot system is partially working
because the bootloader sets the right rootfs partition in the cmdline
but unfortunately OpenWrt for ramips platform overwrites the cmdline
so is not possible to detect the right rootfs partition.
Because all of this, I preferred to simply use the first pair of
partitions and set read-only the other pair.
However this solution is not optimal because is not possible to know
without opening the case which is the current booted partition.
Let’s take for example a router booting the OEM firmware from the first
pair of partitions. If we flash the OpenWrt image, it will be written
on the second pair. In this situation the router will bootloop 3 times
and then will automatically come back to the first pair of partitions
containg the OEM firmware.
In this situation, to flash OpenWrt correctly is necessary to switch
the booting partition, flashing again the OEM firmware over itself.
At this point the OEM firmware is on both pair of partitions but the
current booted pair is the second one.
Now, flashing the OpenWrt factory image will write the firmware on
the first pair and then will boot correctly.
If this limitation in the ramips platform about the cmdline will be
fixed, the dual boot system can also be implemented in OpenWrt with
almost no effort.
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
Co-Developed-by: Jackson Lim <jackcolentern@gmail.com>
Signed-off-by: Jackson Lim <jackcolentern@gmail.com>
2020-05-11 23:27:50 +00:00
|
|
|
UBINIZE_OPTS := -E 5
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata | check-size
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(KERNEL_SIZE) | \
|
2020-07-16 00:24:43 +00:00
|
|
|
append-ubi | check-size | linksys-image type=$$$$(LINKSYS_HWNAME)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/linksys_ea7300-v1
|
|
|
|
|
$(Device/linksys_ea7xxx)
|
|
|
|
|
DEVICE_MODEL := EA7300
|
|
|
|
|
DEVICE_VARIANT := v1
|
|
|
|
|
LINKSYS_HWNAME := EA7300
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += linksys_ea7300-v1
|
|
|
|
|
|
2020-09-23 02:30:45 +00:00
|
|
|
define Device/linksys_ea7300-v2
|
|
|
|
|
$(Device/linksys_ea7xxx)
|
|
|
|
|
DEVICE_MODEL := EA7300
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
LINKSYS_HWNAME := EA7300v2
|
|
|
|
|
DEVICE_PACKAGES += kmod-mt7603
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += linksys_ea7300-v2
|
|
|
|
|
|
2020-07-16 00:24:43 +00:00
|
|
|
define Device/linksys_ea7500-v2
|
|
|
|
|
$(Device/linksys_ea7xxx)
|
|
|
|
|
DEVICE_MODEL := EA7500
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
LINKSYS_HWNAME := EA7500v2
|
ramips: add support for Linksys EA7500 v2
The Linksys EA7500 v2 is advertised as AC1900, but its internal
hardware is AC2600 capable.
Hardware
--------
SoC: Mediatek MT7621AT (880 MHz, 2 cores 4 threads)
RAM: 256M (Nanya NT5CC128M16IP-DI)
FLASH: 128MB NAND (Macronix MX30LF1G18AC-TI)
ETH: 5x 10/100/1000 Mbps Ethernet (MT7530)
WIFI:
- 2.4GHz: 1x MT7615N (4x4:4)
- 5GHz: 1x MT7615N (4x4:4)
- 4 antennas: 3 external detachable antennas and 1 internal
USB:
- 1x USB 3.0
- 1x USB 2.0
BTN:
- 1x Reset button
- 1x WPS button
LEDS:
- 1x White led (Power)
- 6x Green leds (link lan1-lan4, link wan, wps)
- 5x Orange leds (act lan1-lan4, act wan) (working but unmodifiable)
Everything works correctly.
Installation
------------
The “factory” openwrt image can be flashed directly from OEM stock
firmware. After the flash the router will reboot automatically.
However, due to the dual boot system, the first installation could fail
(if you want to know why, read the footnotes).
If the flash succeed and you can reach OpenWrt through the web
interface or ssh, you are done.
Otherwise the router will try to boot 3 times and then will
automatically boot the OEM firmware (don’t turn off the router.
Simply wait and try to reach the router through the web interface
every now and then, it will take few minutes).
After this, you should be back in the OEM firmware.
Now you have to flash the OEM Firmware over itself using the OEM web
interface (I tested it using the FW_EA7500v2_2.0.8.194281_prod.img
downloaded from the Linksys website).
When the router reboots flash the “factory” OpenWrt image and this
time it should work.
After the OpenWrt installation you have to use the sysupgrade image
for future updates.
Restore OEM Firmware
--------------------
After the OpenWrt flash, the OEM firmware is still stored in the
second partition thanks to the dual boot system.
You can switch from OpenWrt to OEM firmware and vice-versa failing
the boot 3 times in a row:
1) power on the router
2) wait 15 seconds
3) power off the router
4) repeat steps 1-2-3 twice more.
5) power on the router and you should be in the “other” firmware
If you want to completely remove OpenWrt from your router, switch to
the OEM firmware and then flash OEM firmware from the web interface
as a normal update.
This procedure will overwrite the OpenWrt partition.
Footnotes
---------
The Linksys EA7500-v2 has a dual boot system to avoid bricks.
This system works using 2 pair of partitions:
1) "kernel" and "rootfs"
2) "alt_kernel" and "alt_rootfs".
After 3 failed boot attempts, the bootloader tries to boot the other
pair of partitions and so on.
This system is managed by the bootloader, which writes a bootcount in
the s_env partition, and if successfully booted, the system add a
"zero-bootcount" after the previous value.
A system update performed from OEM firmware, writes the firmware on the
other pair of partitions and sets the bootloader to boot the new pair
of partitions editing the “boot_part” variable in the bootloader vars.
Effectively it's a quick and safe system to switch the selected boot
partition.
Another way to switch the boot partition is:
1) power on the router
2) wait 15 seconds
3) power off the router
4) repeat steps 1-2-3 twice more.
5) power on the router and you should be in the “other” firmware
In this OpenWrt port, this dual boot system is partially working
because the bootloader sets the right rootfs partition in the cmdline
but unfortunately OpenWrt for ramips platform overwrites the cmdline
so is not possible to detect the right rootfs partition.
Because all of this, I preferred to simply use the first pair of
partitions and set read-only the other pair.
However this solution is not optimal because is not possible to know
without opening the case which is the current booted partition.
Let’s take for example a router booting the OEM firmware from the first
pair of partitions. If we flash the OpenWrt image, it will be written
on the second pair. In this situation the router will bootloop 3 times
and then will automatically come back to the first pair of partitions
containg the OEM firmware.
In this situation, to flash OpenWrt correctly is necessary to switch
the booting partition, flashing again the OEM firmware over itself.
At this point the OEM firmware is on both pair of partitions but the
current booted pair is the second one.
Now, flashing the OpenWrt factory image will write the firmware on
the first pair and then will boot correctly.
If this limitation in the ramips platform about the cmdline will be
fixed, the dual boot system can also be implemented in OpenWrt with
almost no effort.
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
Co-Developed-by: Jackson Lim <jackcolentern@gmail.com>
Signed-off-by: Jackson Lim <jackcolentern@gmail.com>
2020-05-11 23:27:50 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += linksys_ea7500-v2
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/linksys_re6500
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Linksys
|
|
|
|
|
DEVICE_MODEL := RE6500
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += re6500
|
ramips: add support for Xiaomi Mi Router 3 Pro
Hardware:
CPU: MediaTek MT7621AT (2x880MHz)
RAM: 512MB DDR3
FLASH: 256MB NAND
WiFi: 2.4GHz 4x4 MT7615 b/g/n (Needs driver, See Issues!)
WiFI: 5GHz 4x4 MT7615 a/n/ac (Needs driver, See Issues!)
USB: 1x 3.0
ETH: 1x WAN 10/100/1000 3x LAN 10/100/1000
LED: Power/Status
BTN: RESET
UART: 115200 8n1
Partition layout and boot:
Stock Xiaomi firmware has the MTD split into (among others)
- kernel0 (@0x200000)
- kernel1 (@0x600000)
- rootfs0
- rootfs1
- overlay (ubi)
Xiaomi uboot expects to find kernels at 0x200000 & 0x600000
referred to as system 1 & system 2 respectively.
a kernel is considered suitable for handing control over
if its linux magic number exists & uImage CRC are correct.
If either of those conditions fail, a matching sys'n'_fail flag
is set in uboot env & a restart performed in the hope that the
alternate kernel is okay.
If neither kernel checksums ok and both are marked failed, system 2
is booted anyway.
Note uboot's tftp flash install writes the transferred
image to both kernel partitions.
Installation:
Similar to the Xiaomi MIR3G, we keep stock Xiaomi firmware in
kernel0 for ease of recovery, and install OpenWRT into kernel1 and
after.
The installation file for OpenWRT is a *squashfs-factory.bin file that
contains the kernel and a ubi partition. This is flashed as follows:
nvram set flag_try_sys1_failed=1
nvram set flag_try_sys2_failed=0
nvram commit
dd if=factory.bin bs=1M count=4 | mtd write - kernel1
dd if=factory.bin bs=1M skip=4 | mtd write - rootfs0
reboot
Reverting to stock:
The part of stock firmware we've kept in kernel0 allows us to run stock
recovery, which will re-flash stock firmware from a *.bin file on a USB.
For this we do the following:
fw_setenv flag_try_sys1_failed 0
fw_setenv flag_try_sys2_failed 1
reboot
After reboot the LED status light will blink red, at which point pressing
the 'reset' button will cause stock firmware to be installed from USB.
Issues:
OpenWRT currently does not have support for the MT7615 wifi chips. There is
ongoing work to add mt7615 support to the open source mt76 driver. Until that
support is in place, there are closed-source kernel modules that can be used.
See: https://forum.openwrt.org/t/support-for-xiaomi-wifi-r3p-pro/20290/170
Signed-off-by: Ozgur Can Leonard <ozgurcan@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
[02_network remaps, Added link to notes]
2019-03-05 08:41:37 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += linksys_re6500
|
ramips: add support for Xiaomi Mi Router 3 Pro
Hardware:
CPU: MediaTek MT7621AT (2x880MHz)
RAM: 512MB DDR3
FLASH: 256MB NAND
WiFi: 2.4GHz 4x4 MT7615 b/g/n (Needs driver, See Issues!)
WiFI: 5GHz 4x4 MT7615 a/n/ac (Needs driver, See Issues!)
USB: 1x 3.0
ETH: 1x WAN 10/100/1000 3x LAN 10/100/1000
LED: Power/Status
BTN: RESET
UART: 115200 8n1
Partition layout and boot:
Stock Xiaomi firmware has the MTD split into (among others)
- kernel0 (@0x200000)
- kernel1 (@0x600000)
- rootfs0
- rootfs1
- overlay (ubi)
Xiaomi uboot expects to find kernels at 0x200000 & 0x600000
referred to as system 1 & system 2 respectively.
a kernel is considered suitable for handing control over
if its linux magic number exists & uImage CRC are correct.
If either of those conditions fail, a matching sys'n'_fail flag
is set in uboot env & a restart performed in the hope that the
alternate kernel is okay.
If neither kernel checksums ok and both are marked failed, system 2
is booted anyway.
Note uboot's tftp flash install writes the transferred
image to both kernel partitions.
Installation:
Similar to the Xiaomi MIR3G, we keep stock Xiaomi firmware in
kernel0 for ease of recovery, and install OpenWRT into kernel1 and
after.
The installation file for OpenWRT is a *squashfs-factory.bin file that
contains the kernel and a ubi partition. This is flashed as follows:
nvram set flag_try_sys1_failed=1
nvram set flag_try_sys2_failed=0
nvram commit
dd if=factory.bin bs=1M count=4 | mtd write - kernel1
dd if=factory.bin bs=1M skip=4 | mtd write - rootfs0
reboot
Reverting to stock:
The part of stock firmware we've kept in kernel0 allows us to run stock
recovery, which will re-flash stock firmware from a *.bin file on a USB.
For this we do the following:
fw_setenv flag_try_sys1_failed 0
fw_setenv flag_try_sys2_failed 1
reboot
After reboot the LED status light will blink red, at which point pressing
the 'reset' button will cause stock firmware to be installed from USB.
Issues:
OpenWRT currently does not have support for the MT7615 wifi chips. There is
ongoing work to add mt7615 support to the open source mt76 driver. Until that
support is in place, there are closed-source kernel modules that can be used.
See: https://forum.openwrt.org/t/support-for-xiaomi-wifi-r3p-pro/20290/170
Signed-off-by: Ozgur Can Leonard <ozgurcan@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
[02_network remaps, Added link to notes]
2019-03-05 08:41:37 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/mediatek_ap-mt7621a-v60
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Mediatek
|
|
|
|
|
DEVICE_MODEL := AP-MT7621A-V60 EVB
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb3 kmod-sdhci-mt7620 kmod-sound-mt7620 -wpad-basic-wolfssl
|
2017-08-12 14:56:11 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += mediatek_ap-mt7621a-v60
|
2017-08-12 14:56:11 +00:00
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/mediatek_mt7621-eval-board
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2016-11-19 17:27:22 +00:00
|
|
|
BLOCKSIZE := 64k
|
2019-07-15 12:55:24 +00:00
|
|
|
IMAGE_SIZE := 15104k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := MediaTek
|
|
|
|
|
DEVICE_MODEL := MT7621 EVB
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := -wpad-basic-wolfssl
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += mt7621
|
2016-11-19 17:27:22 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += mediatek_mt7621-eval-board
|
2016-11-19 17:27:22 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/MikroTik
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := MikroTik
|
|
|
|
|
BLOCKSIZE := 64k
|
|
|
|
|
IMAGE_SIZE := 16128k
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb3
|
|
|
|
|
LOADER_TYPE := elf
|
|
|
|
|
KERNEL := $(KERNEL_DTB) | loader-kernel
|
2019-12-19 18:40:33 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-kernel | kernel2minor -s 1024 | \
|
|
|
|
|
pad-to $$$$(BLOCKSIZE) | append-rootfs | pad-rootfs | append-metadata | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2016-09-27 06:25:04 +00:00
|
|
|
endef
|
|
|
|
|
|
2020-04-07 08:34:33 +00:00
|
|
|
define Device/mikrotik_routerboard-750gr3
|
2019-07-07 14:27:51 +00:00
|
|
|
$(Device/MikroTik)
|
2020-04-07 08:34:33 +00:00
|
|
|
DEVICE_MODEL := RouterBOARD 750Gr3
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES += -wpad-basic-wolfssl
|
2020-04-07 08:34:33 +00:00
|
|
|
SUPPORTED_DEVICES += mikrotik,rb750gr3
|
2019-07-07 14:27:51 +00:00
|
|
|
endef
|
2020-04-07 08:34:33 +00:00
|
|
|
TARGET_DEVICES += mikrotik_routerboard-750gr3
|
2019-07-07 14:27:51 +00:00
|
|
|
|
2020-06-10 22:15:40 +00:00
|
|
|
define Device/mikrotik_routerboard-760igs
|
|
|
|
|
$(Device/MikroTik)
|
|
|
|
|
DEVICE_MODEL := RouterBOARD 760iGS
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES += kmod-sfp -wpad-basic-wolfssl
|
2020-06-10 22:15:40 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mikrotik_routerboard-760igs
|
|
|
|
|
|
2020-04-07 08:34:33 +00:00
|
|
|
define Device/mikrotik_routerboard-m11g
|
2019-07-07 14:27:51 +00:00
|
|
|
$(Device/MikroTik)
|
|
|
|
|
DEVICE_MODEL := RouterBOARD M11G
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := -wpad-basic-wolfssl
|
2020-04-07 08:34:33 +00:00
|
|
|
SUPPORTED_DEVICES += mikrotik,rbm11g
|
2019-07-07 14:27:51 +00:00
|
|
|
endef
|
2020-04-07 08:34:33 +00:00
|
|
|
TARGET_DEVICES += mikrotik_routerboard-m11g
|
2019-07-07 14:27:51 +00:00
|
|
|
|
2020-04-07 08:34:33 +00:00
|
|
|
define Device/mikrotik_routerboard-m33g
|
2019-07-07 14:27:51 +00:00
|
|
|
$(Device/MikroTik)
|
|
|
|
|
DEVICE_MODEL := RouterBOARD M33G
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := -wpad-basic-wolfssl
|
2020-04-07 08:34:33 +00:00
|
|
|
SUPPORTED_DEVICES += mikrotik,rbm33g
|
2019-07-07 14:27:51 +00:00
|
|
|
endef
|
2020-04-07 08:34:33 +00:00
|
|
|
TARGET_DEVICES += mikrotik_routerboard-m33g
|
2019-07-07 14:27:51 +00:00
|
|
|
|
2019-07-10 15:57:36 +00:00
|
|
|
define Device/mqmaker_witi
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := MQmaker
|
|
|
|
|
DEVICE_MODEL := WiTi
|
2020-03-05 13:57:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-mt76x2 kmod-sdhci-mt7620 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-07-10 15:57:36 +00:00
|
|
|
SUPPORTED_DEVICES += witi mqmaker,witi-256m mqmaker,witi-512m
|
ramips: add support for newifi d2
Previously Newifi D2 could only use PandoraBox M1's firmware.
It works fine, but LED GPIO is different.
As a result, a separated DTS file for this device should be implemented.
Hardware spec:
* CPU: MTK MT7621A
* RAM: 512MB
* ROM: 32MB SPI Flash
* WiFi: MTK MT7603+MT7612
* Button: 2 buttons (reset, wps)
* LED: 3 single-color LEDs (USB, WiFi 2.4GHz, WiFi 5GHz) &
2 dual-color LEDs (Power, Internet)
* Ethernet: 5 ports, 4 LAN + 1 WAN
Installation method:
Same as Newifi D1, users may need to request unlock code from the device
manufacturer. Otherwise, a SPI flash programmer may be necessary to get
the firmware flashed. After the device is unlocked, press and hold reset
button before power cable plugs in. Then go to http://192.168.1.1 to
upload and flash the firmware package.
Signed-off-by: Jackson Ming Hu <huming2207@gmail.com>
2017-12-15 03:51:33 +00:00
|
|
|
endef
|
2019-07-10 15:57:36 +00:00
|
|
|
TARGET_DEVICES += mqmaker_witi
|
2016-04-01 07:11:48 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/mtc_wr1201
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 16000k
|
|
|
|
|
DEVICE_VENDOR := MTC
|
|
|
|
|
DEVICE_MODEL := Wireless Router WR1201
|
2019-09-24 18:02:04 +00:00
|
|
|
KERNEL_INITRAMFS := $(KERNEL_DTB) | custom-initramfs-uimage WR1201_8_128
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-sdhci-mt7620 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2017-03-11 07:44:33 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += mtc_wr1201
|
2017-03-11 07:44:33 +00:00
|
|
|
|
2019-03-21 14:55:09 +00:00
|
|
|
define Device/netgear_ex6150
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := NETGEAR
|
|
|
|
|
DEVICE_MODEL := EX6150
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2019-03-21 14:55:09 +00:00
|
|
|
NETGEAR_BOARD_ID := U12H318T00_NETGEAR
|
|
|
|
|
IMAGE_SIZE := 14848k
|
|
|
|
|
IMAGES += factory.chk
|
2020-05-08 16:21:06 +00:00
|
|
|
IMAGE/factory.chk := $$(sysupgrade_bin) | check-size | netgear-chk
|
2019-03-21 14:55:09 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_ex6150
|
|
|
|
|
|
2019-10-21 12:43:21 +00:00
|
|
|
define Device/netgear_sercomm_nand
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-15 01:32:02 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2018-08-24 01:36:13 +00:00
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
KERNEL_SIZE := 4096k
|
|
|
|
|
UBINIZE_OPTS := -E 5
|
2019-08-27 21:55:12 +00:00
|
|
|
IMAGES += factory.img kernel.bin rootfs.bin
|
2019-12-19 18:40:33 +00:00
|
|
|
IMAGE/factory.img := pad-extra 2048k | append-kernel | pad-to 6144k | \
|
|
|
|
|
append-ubi | pad-to $$$$(BLOCKSIZE) | sercom-footer | pad-to 128 | \
|
2019-10-21 12:43:21 +00:00
|
|
|
zip $$$$(SERCOMM_HWNAME).bin | sercom-seal
|
2018-08-24 01:36:13 +00:00
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
|
|
|
|
IMAGE/kernel.bin := append-kernel
|
2020-03-10 13:58:27 +00:00
|
|
|
IMAGE/rootfs.bin := append-ubi | check-size
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := NETGEAR
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-usb3 kmod-usb-ledtrig-usbport
|
2019-10-21 12:43:21 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/netgear_r6220
|
|
|
|
|
$(Device/netgear_sercomm_nand)
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_MODEL := R6220
|
2019-10-21 12:43:21 +00:00
|
|
|
SERCOMM_HWNAME := R6220
|
|
|
|
|
SERCOMM_HWID := AYA
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x0086
|
|
|
|
|
IMAGE_SIZE := 28672k
|
|
|
|
|
DEVICE_PACKAGES += kmod-mt76x2
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += r6220
|
2018-08-24 01:36:13 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += netgear_r6220
|
2018-08-24 01:36:13 +00:00
|
|
|
|
2019-08-29 08:08:38 +00:00
|
|
|
|
|
|
|
|
define Device/netgear_r6260
|
2019-10-21 12:43:21 +00:00
|
|
|
$(Device/netgear_sercomm_nand)
|
2019-08-29 08:08:38 +00:00
|
|
|
DEVICE_MODEL := R6260
|
2019-10-21 12:43:21 +00:00
|
|
|
SERCOMM_HWNAME := R6260
|
|
|
|
|
SERCOMM_HWID := CHJ
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x0052
|
|
|
|
|
IMAGE_SIZE := 40960k
|
2020-06-03 16:55:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-mt7615e kmod-mt7615-firmware
|
2019-08-29 08:08:38 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_r6260
|
|
|
|
|
|
|
|
|
|
define Device/netgear_r6350
|
2019-10-21 12:43:21 +00:00
|
|
|
$(Device/netgear_sercomm_nand)
|
2019-08-29 08:08:38 +00:00
|
|
|
DEVICE_MODEL := R6350
|
2019-10-21 12:43:21 +00:00
|
|
|
SERCOMM_HWNAME := R6350
|
|
|
|
|
SERCOMM_HWID := CHJ
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x0052
|
|
|
|
|
IMAGE_SIZE := 40960k
|
2020-06-03 16:55:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-mt7615e kmod-mt7615-firmware
|
2019-08-29 08:08:38 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += netgear_r6350
|
2018-06-25 20:51:43 +00:00
|
|
|
|
ramips: add support for NETGEAR R6700v2/AC2400
SoC: MediaTek MT7621AT
RAM: 256M DDR3
FLASH: 128M NAND
WiFi: MediaTek MT7615N an+ac
MediaTek MT7615N bgn
ETH: MediaTek MT7621AT
BTN: 1x Connect (WPS), 1x WLAN, 1x Reset
LED: Power (white/amber), WAN(white/amber), 2.4G(white), 5G(white),
USB(white) , GuestWifi(white) 4x LAN(white/amber), Wifi Button(white),
WPS Button(white)
Installation:
Login to netgear webinterface and flash factory.img
Based on a discontinued GitHub Pull Request by
kuyokushin <codenamezero@protonmail.com>
https://github.com/openwrt/openwrt/pull/2545
NOTE: Netgear R6700 v2 have five clones: R6900 v2, R7450, Nighthawk
AC2400, Nighthawk AC2100 and already added R6800. Rest of them should
be really easy supportable. Image for R6700v2 should work perfectly with
them. Please refer:
https://github.com/openwrt/openwrt/pull/2614
Tested-by: Víctor Gibrán <victorgibranmz@hotmail.com> [R6700v2]
Tested-by: John Landrum <jl31m10@yahoo.com> [AC2400]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
[add guest led to mt7621_netgear_r6700-v2.dts end edit commit message]
Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
2019-12-27 18:05:06 +00:00
|
|
|
define Device/netgear_r6700-v2
|
|
|
|
|
$(Device/netgear_sercomm_nand)
|
|
|
|
|
DEVICE_MODEL := R6700
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
DEVICE_ALT0_VENDOR := NETGEAR
|
|
|
|
|
DEVICE_ALT0_MODEL := Nighthawk AC2400
|
2020-04-15 13:43:51 +00:00
|
|
|
DEVICE_ALT0_VARIANT := v1
|
|
|
|
|
DEVICE_ALT1_VENDOR := NETGEAR
|
|
|
|
|
DEVICE_ALT1_MODEL := R7200
|
|
|
|
|
DEVICE_ALT1_VARIANT := v1
|
ramips: add support for NETGEAR R6700v2/AC2400
SoC: MediaTek MT7621AT
RAM: 256M DDR3
FLASH: 128M NAND
WiFi: MediaTek MT7615N an+ac
MediaTek MT7615N bgn
ETH: MediaTek MT7621AT
BTN: 1x Connect (WPS), 1x WLAN, 1x Reset
LED: Power (white/amber), WAN(white/amber), 2.4G(white), 5G(white),
USB(white) , GuestWifi(white) 4x LAN(white/amber), Wifi Button(white),
WPS Button(white)
Installation:
Login to netgear webinterface and flash factory.img
Based on a discontinued GitHub Pull Request by
kuyokushin <codenamezero@protonmail.com>
https://github.com/openwrt/openwrt/pull/2545
NOTE: Netgear R6700 v2 have five clones: R6900 v2, R7450, Nighthawk
AC2400, Nighthawk AC2100 and already added R6800. Rest of them should
be really easy supportable. Image for R6700v2 should work perfectly with
them. Please refer:
https://github.com/openwrt/openwrt/pull/2614
Tested-by: Víctor Gibrán <victorgibranmz@hotmail.com> [R6700v2]
Tested-by: John Landrum <jl31m10@yahoo.com> [AC2400]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
[add guest led to mt7621_netgear_r6700-v2.dts end edit commit message]
Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
2019-12-27 18:05:06 +00:00
|
|
|
SERCOMM_HWNAME := R6950
|
|
|
|
|
SERCOMM_HWID := BZV
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x1032
|
|
|
|
|
IMAGE_SIZE := 40960k
|
2020-06-03 16:55:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-mt7615e kmod-mt7615-firmware
|
ramips: add support for NETGEAR R6700v2/AC2400
SoC: MediaTek MT7621AT
RAM: 256M DDR3
FLASH: 128M NAND
WiFi: MediaTek MT7615N an+ac
MediaTek MT7615N bgn
ETH: MediaTek MT7621AT
BTN: 1x Connect (WPS), 1x WLAN, 1x Reset
LED: Power (white/amber), WAN(white/amber), 2.4G(white), 5G(white),
USB(white) , GuestWifi(white) 4x LAN(white/amber), Wifi Button(white),
WPS Button(white)
Installation:
Login to netgear webinterface and flash factory.img
Based on a discontinued GitHub Pull Request by
kuyokushin <codenamezero@protonmail.com>
https://github.com/openwrt/openwrt/pull/2545
NOTE: Netgear R6700 v2 have five clones: R6900 v2, R7450, Nighthawk
AC2400, Nighthawk AC2100 and already added R6800. Rest of them should
be really easy supportable. Image for R6700v2 should work perfectly with
them. Please refer:
https://github.com/openwrt/openwrt/pull/2614
Tested-by: Víctor Gibrán <victorgibranmz@hotmail.com> [R6700v2]
Tested-by: John Landrum <jl31m10@yahoo.com> [AC2400]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
[add guest led to mt7621_netgear_r6700-v2.dts end edit commit message]
Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
2019-12-27 18:05:06 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_r6700-v2
|
|
|
|
|
|
2019-12-11 20:54:24 +00:00
|
|
|
define Device/netgear_r6800
|
|
|
|
|
$(Device/netgear_sercomm_nand)
|
|
|
|
|
DEVICE_MODEL := R6800
|
|
|
|
|
SERCOMM_HWNAME := R6950
|
|
|
|
|
SERCOMM_HWID := BZV
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x0062
|
|
|
|
|
IMAGE_SIZE := 40960k
|
2020-06-03 16:55:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-mt7615e kmod-mt7615-firmware
|
2019-12-11 20:54:24 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_r6800
|
|
|
|
|
|
2019-08-29 08:08:38 +00:00
|
|
|
define Device/netgear_r6850
|
2019-10-21 12:43:21 +00:00
|
|
|
$(Device/netgear_sercomm_nand)
|
2019-08-29 08:08:38 +00:00
|
|
|
DEVICE_MODEL := R6850
|
2019-10-21 12:43:21 +00:00
|
|
|
SERCOMM_HWNAME := R6850
|
|
|
|
|
SERCOMM_HWID := CHJ
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x0052
|
|
|
|
|
IMAGE_SIZE := 40960k
|
2020-06-03 16:55:55 +00:00
|
|
|
DEVICE_PACKAGES += kmod-mt7615e kmod-mt7615-firmware
|
2019-08-29 08:08:38 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_r6850
|
|
|
|
|
|
2020-06-09 13:16:35 +00:00
|
|
|
define Device/netgear_wac104
|
|
|
|
|
$(Device/netgear_sercomm_nand)
|
|
|
|
|
DEVICE_MODEL := WAC104
|
|
|
|
|
SERCOMM_HWNAME := WAC104
|
|
|
|
|
SERCOMM_HWID := CAY
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x0006
|
|
|
|
|
IMAGE_SIZE := 28672k
|
|
|
|
|
DEVICE_PACKAGES += kmod-mt76x2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_wac104
|
|
|
|
|
|
2020-06-26 21:46:19 +00:00
|
|
|
define Device/netgear_wac124
|
|
|
|
|
$(Device/netgear_sercomm_nand)
|
|
|
|
|
DEVICE_MODEL := WAC124
|
|
|
|
|
SERCOMM_HWNAME := WAC124
|
|
|
|
|
SERCOMM_HWID := CTL
|
|
|
|
|
SERCOMM_HWVER := A003
|
|
|
|
|
SERCOMM_SWVER := 0x0402
|
|
|
|
|
IMAGE_SIZE := 40960k
|
|
|
|
|
DEVICE_PACKAGES += kmod-mt7615e kmod-mt7615-firmware
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_wac124
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/netgear_wndr3700-v5
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-08-03 17:23:50 +00:00
|
|
|
$(Device/netgear_sercomm_nor)
|
2020-04-15 01:32:02 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 15232k
|
2020-08-03 17:23:50 +00:00
|
|
|
DEVICE_MODEL := WNDR3700
|
|
|
|
|
DEVICE_VARIANT := v5
|
|
|
|
|
SERCOMM_HWNAME := WNDR3700v5
|
2019-07-07 14:27:51 +00:00
|
|
|
SERCOMM_HWID := AYB
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x1054
|
2020-08-03 17:23:50 +00:00
|
|
|
SERCOMM_PAD := 320k
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += wndr3700v5
|
2018-11-29 23:13:53 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += netgear_wndr3700-v5
|
2018-11-29 23:13:53 +00:00
|
|
|
|
2019-10-08 13:21:13 +00:00
|
|
|
define Device/netis_wf2881
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-07 14:27:51 +00:00
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
FILESYSTEMS := squashfs
|
2019-10-02 13:12:28 +00:00
|
|
|
KERNEL_SIZE := 4096k
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 129280k
|
|
|
|
|
UBINIZE_OPTS := -E 5
|
2020-02-07 11:26:05 +00:00
|
|
|
UIMAGE_NAME := WF2881_0.0.00
|
|
|
|
|
KERNEL_INITRAMFS := $(KERNEL_DTB) | netis-tail WF2881 | uImage lzma
|
2019-10-02 13:12:28 +00:00
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
|
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$$$(KERNEL_SIZE) | append-ubi | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := NETIS
|
2019-10-08 13:21:13 +00:00
|
|
|
DEVICE_MODEL := WF2881
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb3 kmod-usb-ledtrig-usbport
|
2017-07-23 19:06:44 +00:00
|
|
|
endef
|
2019-10-08 13:21:13 +00:00
|
|
|
TARGET_DEVICES += netis_wf2881
|
2017-07-23 19:06:44 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/phicomm_k2p
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-15 12:55:02 +00:00
|
|
|
IMAGE_SIZE := 15744k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Phicomm
|
|
|
|
|
DEVICE_MODEL := K2P
|
2019-10-06 19:07:33 +00:00
|
|
|
DEVICE_ALT0_VENDOR := Phicomm
|
|
|
|
|
DEVICE_ALT0_MODEL := KE 2P
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += k2p
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2016-11-19 17:27:22 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += phicomm_k2p
|
2016-11-19 17:27:22 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/planex_vr500
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-24 05:51:53 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-15 12:55:24 +00:00
|
|
|
IMAGE_SIZE := 65216k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Planex
|
|
|
|
|
DEVICE_MODEL := VR500
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb3 -wpad-basic-wolfssl
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += vr500
|
2016-04-01 07:11:48 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += planex_vr500
|
2016-04-01 07:11:48 +00:00
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/samknows_whitebox-v8
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := SamKnows
|
|
|
|
|
DEVICE_MODEL := Whitebox 8
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport uboot-envtools
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += sk-wb8
|
2016-11-19 17:27:22 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += samknows_whitebox-v8
|
2016-11-19 17:27:22 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/storylink_sap-g3200u3
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := STORYLiNK
|
|
|
|
|
DEVICE_MODEL := SAP-G3200U3
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb3 kmod-usb-ledtrig-usbport
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += sap-g3200u3
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += storylink_sap-g3200u3
|
|
|
|
|
|
2019-04-19 04:12:11 +00:00
|
|
|
define Device/telco-electronics_x1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-04-19 04:12:11 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Telco Electronics
|
|
|
|
|
DEVICE_MODEL := X1
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb3 kmod-mt76
|
2019-04-19 04:12:11 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += telco-electronics_x1
|
|
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/thunder_timecloud
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-18 06:19:38 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Thunder
|
|
|
|
|
DEVICE_MODEL := Timecloud
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb3 -wpad-basic-wolfssl
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += timecloud
|
2016-08-10 00:18:32 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += thunder_timecloud
|
2016-08-10 00:18:32 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/totolink_a7000r
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
UIMAGE_NAME := C8340R1C-9999
|
|
|
|
|
DEVICE_VENDOR := TOTOLINK
|
|
|
|
|
DEVICE_MODEL := A7000R
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
2019-07-07 14:27:51 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += totolink_a7000r
|
|
|
|
|
|
ramips: add support for TP-Link RE650 v1
TP-Link RE650 v1 is a dual-band AC2600 range extender,
based on MediaTek MT7621A and MT7615E. According to the
wikidevi entry for RE650 this device is identical with
TP-Link RE500 as hardware. This patch supports only RE650.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin
from the RE650 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com>
[re-added variables for kernel header]
Signed-off-by: David Bauer <mail@david-bauer.net>
2019-04-17 18:17:45 +00:00
|
|
|
define Device/tplink_re350-v1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
ramips: add support for TP-Link RE650 v1
TP-Link RE650 v1 is a dual-band AC2600 range extender,
based on MediaTek MT7621A and MT7615E. According to the
wikidevi entry for RE650 this device is identical with
TP-Link RE500 as hardware. This patch supports only RE650.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin
from the RE650 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com>
[re-added variables for kernel header]
Signed-off-by: David Bauer <mail@david-bauer.net>
2019-04-17 18:17:45 +00:00
|
|
|
$(Device/tplink-safeloader)
|
|
|
|
|
DEVICE_MODEL := RE350
|
|
|
|
|
DEVICE_VARIANT := v1
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2
|
ramips: add support for TP-Link RE650 v1
TP-Link RE650 v1 is a dual-band AC2600 range extender,
based on MediaTek MT7621A and MT7615E. According to the
wikidevi entry for RE650 this device is identical with
TP-Link RE500 as hardware. This patch supports only RE650.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin
from the RE650 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com>
[re-added variables for kernel header]
Signed-off-by: David Bauer <mail@david-bauer.net>
2019-04-17 18:17:45 +00:00
|
|
|
TPLINK_BOARD_ID := RE350-V1
|
|
|
|
|
IMAGE_SIZE := 6016k
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += re350-v1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_re350-v1
|
|
|
|
|
|
ramips: add support for TP-Link RE500 v1
This device uses the same hardware as RE650 v1 which got supported in
8c51dde.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re500-v1-squashfs-factory.bin
from the RE500 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Christoph Krapp <achterin@googlemail.com>
[remove dts-v1 in DTSI, do not touch WiFi LEDs for RE650, keep
state_default in DTS files, fix label-mac-device, use lower case
for WiFi LEDs]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-06 21:05:25 +00:00
|
|
|
define Device/tplink_re500-v1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
ramips: add support for TP-Link RE500 v1
This device uses the same hardware as RE650 v1 which got supported in
8c51dde.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re500-v1-squashfs-factory.bin
from the RE500 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Christoph Krapp <achterin@googlemail.com>
[remove dts-v1 in DTSI, do not touch WiFi LEDs for RE650, keep
state_default in DTS files, fix label-mac-device, use lower case
for WiFi LEDs]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-06 21:05:25 +00:00
|
|
|
$(Device/tplink-safeloader)
|
|
|
|
|
DEVICE_MODEL := RE500
|
|
|
|
|
DEVICE_VARIANT := v1
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
ramips: add support for TP-Link RE500 v1
This device uses the same hardware as RE650 v1 which got supported in
8c51dde.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re500-v1-squashfs-factory.bin
from the RE500 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Christoph Krapp <achterin@googlemail.com>
[remove dts-v1 in DTSI, do not touch WiFi LEDs for RE650, keep
state_default in DTS files, fix label-mac-device, use lower case
for WiFi LEDs]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-06 21:05:25 +00:00
|
|
|
TPLINK_BOARD_ID := RE500-V1
|
|
|
|
|
IMAGE_SIZE := 14208k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_re500-v1
|
|
|
|
|
|
ramips: add support for TP-Link RE650 v1
TP-Link RE650 v1 is a dual-band AC2600 range extender,
based on MediaTek MT7621A and MT7615E. According to the
wikidevi entry for RE650 this device is identical with
TP-Link RE500 as hardware. This patch supports only RE650.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin
from the RE650 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com>
[re-added variables for kernel header]
Signed-off-by: David Bauer <mail@david-bauer.net>
2019-04-17 18:17:45 +00:00
|
|
|
define Device/tplink_re650-v1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
ramips: add support for TP-Link RE650 v1
TP-Link RE650 v1 is a dual-band AC2600 range extender,
based on MediaTek MT7621A and MT7615E. According to the
wikidevi entry for RE650 this device is identical with
TP-Link RE500 as hardware. This patch supports only RE650.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin
from the RE650 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com>
[re-added variables for kernel header]
Signed-off-by: David Bauer <mail@david-bauer.net>
2019-04-17 18:17:45 +00:00
|
|
|
$(Device/tplink-safeloader)
|
|
|
|
|
DEVICE_MODEL := RE650
|
|
|
|
|
DEVICE_VARIANT := v1
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware
|
ramips: add support for TP-Link RE650 v1
TP-Link RE650 v1 is a dual-band AC2600 range extender,
based on MediaTek MT7621A and MT7615E. According to the
wikidevi entry for RE650 this device is identical with
TP-Link RE500 as hardware. This patch supports only RE650.
Hardware specification:
- SoC 880 MHz - MediaTek MT7621AT
- 128 MB of DDR3 RAM
- 16 MB - Winbond 25Q128FVSG
- 4T4R 2.4 GHz - MediaTek MT7615E
- 4T4R 5 GHz - MediaTek MT7615E
- 1x 1 Gbps Ethernet - MT7621AT integrated
- 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2))
- 4x buttons (Reset, Power, WPS, LED)
- UART header (J1) - 2:GND, 3:RX, 4:TX
Serial console @ 57600,8n1
Flash instructions:
Upload
openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin
from the RE650 web interface.
TFTP recovery to stock firmware:
Unfortunately, I can't find an easy way to recover the RE
without opening the device and using modified binaries. The
TFTP upload will only work if selected from u-boot, which
means you have to open the device and attach to the serial
console. The TFTP update procedure does *not* accept the
published vendor firmware binaries. However, it allows to
flash kernel + rootfs binaries, and this works if you have
a backup of the original contents of the flash. It's probably
possible to create special image out of the vendor binaries
and use that as recovery image.
Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com>
[re-added variables for kernel header]
Signed-off-by: David Bauer <mail@david-bauer.net>
2019-04-17 18:17:45 +00:00
|
|
|
TPLINK_BOARD_ID := RE650-V1
|
|
|
|
|
IMAGE_SIZE := 14208k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_re650-v1
|
|
|
|
|
|
2020-04-07 08:47:18 +00:00
|
|
|
define Device/ubnt_edgerouter_common
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-15 01:32:02 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2020-04-07 08:47:18 +00:00
|
|
|
DEVICE_VENDOR := Ubiquiti
|
2019-07-15 12:55:24 +00:00
|
|
|
IMAGE_SIZE := 256768k
|
2016-11-19 17:27:22 +00:00
|
|
|
FILESYSTEMS := squashfs
|
|
|
|
|
KERNEL_SIZE := 3145728
|
2019-12-19 18:40:33 +00:00
|
|
|
KERNEL_INITRAMFS := $$(KERNEL) | \
|
|
|
|
|
ubnt-erx-factory-image $(KDIR)/tmp/$$(KERNEL_INITRAMFS_PREFIX)-factory.tar
|
2018-11-29 09:48:03 +00:00
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES += -wpad-basic-wolfssl
|
2020-04-07 08:47:18 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/ubnt_edgerouter-x
|
|
|
|
|
$(Device/ubnt_edgerouter_common)
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := EdgeRouter X
|
2020-04-07 08:47:18 +00:00
|
|
|
SUPPORTED_DEVICES += ubnt-erx ubiquiti,edgerouterx
|
2016-04-01 07:11:48 +00:00
|
|
|
endef
|
2020-04-07 08:47:18 +00:00
|
|
|
TARGET_DEVICES += ubnt_edgerouter-x
|
2016-04-01 07:11:48 +00:00
|
|
|
|
2020-04-07 08:47:18 +00:00
|
|
|
define Device/ubnt_edgerouter-x-sfp
|
|
|
|
|
$(Device/ubnt_edgerouter_common)
|
|
|
|
|
DEVICE_MODEL := EdgeRouter X SFP
|
2020-04-07 21:50:31 +00:00
|
|
|
DEVICE_PACKAGES += kmod-i2c-algo-pca kmod-gpio-pca953x kmod-sfp
|
2020-04-07 08:47:18 +00:00
|
|
|
SUPPORTED_DEVICES += ubnt-erx-sfp ubiquiti,edgerouterx-sfp
|
2017-05-29 09:24:49 +00:00
|
|
|
endef
|
2020-04-07 08:47:18 +00:00
|
|
|
TARGET_DEVICES += ubnt_edgerouter-x-sfp
|
2017-05-29 09:24:49 +00:00
|
|
|
|
2020-03-08 20:39:19 +00:00
|
|
|
define Device/ubnt_unifi-nanohd
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-03-08 20:39:19 +00:00
|
|
|
DEVICE_VENDOR := Ubiquiti
|
|
|
|
|
DEVICE_MODEL := UniFi nanoHD
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES += kmod-mt7603 kmod-mt7615e kmod-mt7615-firmware
|
2020-03-08 20:39:19 +00:00
|
|
|
IMAGE_SIZE := 15552k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ubnt_unifi-nanohd
|
|
|
|
|
|
2019-08-16 12:05:53 +00:00
|
|
|
define Device/unielec_u7621-06-16m
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2018-11-27 23:31:10 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := UniElec
|
|
|
|
|
DEVICE_MODEL := U7621-06
|
2019-08-16 12:05:53 +00:00
|
|
|
DEVICE_VARIANT := 16M
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-sdhci-mt7620 kmod-usb3 -wpad-basic-wolfssl
|
2019-08-16 12:05:53 +00:00
|
|
|
SUPPORTED_DEVICES += u7621-06-256M-16M unielec,u7621-06-256m-16m
|
2018-11-27 23:31:10 +00:00
|
|
|
endef
|
2019-10-21 15:51:29 +00:00
|
|
|
TARGET_DEVICES += unielec_u7621-06-16m
|
2018-11-27 23:31:10 +00:00
|
|
|
|
2019-08-16 12:05:53 +00:00
|
|
|
define Device/unielec_u7621-06-64m
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2018-10-24 14:23:20 +00:00
|
|
|
IMAGE_SIZE := 65216k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := UniElec
|
|
|
|
|
DEVICE_MODEL := U7621-06
|
2019-08-16 12:05:53 +00:00
|
|
|
DEVICE_VARIANT := 64M
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-sdhci-mt7620 kmod-usb3 -wpad-basic-wolfssl
|
2019-08-16 12:05:53 +00:00
|
|
|
SUPPORTED_DEVICES += unielec,u7621-06-512m-64m
|
2018-10-24 14:23:20 +00:00
|
|
|
endef
|
2019-10-21 15:51:29 +00:00
|
|
|
TARGET_DEVICES += unielec_u7621-06-64m
|
2018-10-24 14:23:20 +00:00
|
|
|
|
ramips: add support for Wavlink WL-WN531A6
This patch adds support for Wavlink WL-WN531A6 (Quantum D6).
Specifications:
--------------
* SoC: Mediatek MT7621AT 2C2T, 880MHz
* RAM: 128MB DDR3, Nanya NT5CB64M16GP-EK
* Flash: 16MB SPI NOR flash, GigaDevice GD25Q127CSIG
* WiFi 5GHz: Mediatek MT7615N (4x4:4) on mini PCIE slot.
* WiFi 2.4GHz: Mediatek MT7603EN (2x2:2) on mini PCIE slot.
* Ethernet: MT7630, 5x 1000Base-T
* LED: Power, WAN, LAN(x4), WiFi, WPS, dual color
"WAVLINK" LED logo on the top cover.
* Buttons: Reset, WPS, "Turbo", touch button on the top
cover via RH6015C touch sensor.
* UART: UART1: serial console (57600 8n1) on the J4 header
located below the top heatsink.
UART2: J12 header, located on the right side of
the board.
* USB: One USB3 port.
* I2C: J9 header, located below the top heatsink.
Backup the OEM Firmware:
-----------------------
There isn't any firmware released for the WL-WN531A6 on
the Wavlink web site. Reverting back to the OEM firmware is
not possible unless we have a backup of the original OEM
firmware.
The OEM firmware is stored on /dev/mtd4 ("Kernel").
1) Plug a FAT32 formatted USB flash drive into the USB port.
2) Navigate to "Setup->USB Storage". Under the "Available
Network folder" you can see part of the mount point of
the newly mounted flash drive filesystem - e.g "sda1".
The full mount point is prefixed with "/media", so in
this case the mount point becomes "/media/sda1".
3) Go to http://192.168.10.1/webcmd.shtml .
4) Type the following line in the "Command" input box:
dd if=/dev/mtd4ro of=/media/sda1/firmware.bin
5) Click "Apply"
6) After few seconds, in the text area should appear this
output:
30080+0 records in
30080+0 records out
7) Type "sync" in the "Command" input box and click "Apply".
8) At this point the OEM firmware is stored on the flash
drive as "firmware.bin". The size of the file is 15040 KB.
Installation:
------------
* Flashing instructions (OEM web interface):
The OEM web interface accepts only files with names containing
"WN531A6". It's also impossible to flash the *-sysupgrade.bin
image, so we have to flash the *-initramfs-kernel.bin first and
use the OpenWrt's upgrade interface to write the sysupgrade
image.
1) Rename openwrt-ramips-mt7621-wavlink_wl-wn531a6-initramfs-kernel.bin
to WN531A6.bin.
2) Connect your computer to the one of the LAN ports of the
router with an Ethernet cable and open http://192.168.10.1
3) Browse to Setup -> Firmware Upgrade interface.
4) Upload the (renamed) OpenWrt image - WN531A6.bin.
5) Proceed with the firmware installation and give the device
a few minutes to finish and reboot.
6) After reboot wait for the "WAVLINK" logo on the top cover
to turn solid blue, and open http://192.168.1.1
7) Use the OpenWrt's "Flash Firmware" interface to write the
OpenWrt sysupgrade image:
openwrt-ramips-mt7621-wavlink_wl-wn531a6-squashfs-sysupgrade.bin
* Flashing instructions (u-boot TFTP):
1) Configure a TFTP server on your computer and set its IP
to 192.168.10.100
2) Rename the OpenWrt sysupgrade image to firmware.bin and
place it in the root folder of the TFTP server.
3) Power off the device and connect an Ethernet cable from
one of its LAN ports your computer.
4) Press the "Reset" button (and keep it pressed)
5) Power on the device.
6) After a few seconds, when the connected port LAN LED stops
blinking fast, release the "Reset" button.
7) Flashing OpenWrt takes less than a minute, system will
reboot automatically.
8) After reboot the WAVLINK logo on the top cover will indicate
the current OpenWrt running status (wait until the logo tunrs
solid blue).
Revert to the OEM Firmware:
--------------------------
* U-boot TFTP:
Follow "Flashing instructions (u-boot TFTP)" and use the
"firmware.bin" backup image.
* OpenWrt "Flash Firmware" interface:
Upload the "firmware.bin" backup image and select "Force update"
before continuing.
Notes:
-----
* The MAC address shown on the label at the back of the device
is assigned to the 2.4G WiFi adapter.
MAC addresses assigned by the OEM firmware:
2.4G: *:XX (label): factory@0x0004
5G: *:XX + 1 : factory@0x8004
WAN: *:XX - 1 : factory@0xe006
LAN: *:XX - 2 : factory@0xe000
* The I2C bus and UART2 are fully functional. The headers are
not populated.
Signed-off-by: Georgi Vlaev <georgi.vlaev@konsulko.com>
2020-08-25 08:26:21 +00:00
|
|
|
define Device/wavlink_wl-wn531a6
|
|
|
|
|
$(Device/dsa-migration)
|
|
|
|
|
DEVICE_VENDOR := Wavlink
|
|
|
|
|
DEVICE_MODEL := WL-WN531A6
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt7615e kmod-mt7615-firmware kmod-usb3
|
|
|
|
|
IMAGE_SIZE := 15040k
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wavlink_wl-wn531a6
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/wevo_11acnas
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-10-07 12:33:51 +00:00
|
|
|
UIMAGE_NAME := 11AC-NAS-Router(0.0.0)
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := WeVO
|
|
|
|
|
DEVICE_MODEL := 11AC NAS Router
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += 11acnas
|
2016-04-26 11:43:53 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += wevo_11acnas
|
2016-04-01 07:11:48 +00:00
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/wevo_w2914ns-v2
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-10-07 12:33:51 +00:00
|
|
|
UIMAGE_NAME := W2914NS-V2(0.0.0)
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := WeVO
|
|
|
|
|
DEVICE_MODEL := W2914NS
|
|
|
|
|
DEVICE_VARIANT := v2
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += w2914nsv2
|
2016-11-15 11:37:38 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += wevo_w2914ns-v2
|
2016-11-15 11:37:38 +00:00
|
|
|
|
ramips: add support for Winstars WS-WN583A6
The Winstars WS-WN583A6 is a wireless repeater with 2 gigabit ethernet
ports. Even if mine is branded as "Gemeita AC2100", the sticker on the
back says WS-WN583A6. So I will refer to it as Winstars WS-WN583A6.
Probably the real product name is the Wavlink WL-WN583A6 because of
the many references to Wavlink in the OEM firmware and bootlog.
Hardware
--------
SoC: Mediatek MT7621AT (880 MHz, 2 cores 4 threads)
RAM: 128MB
FLASH: 8MB NOR (GigaDevice GD25Q64B)
ETH: 2x 10/100/1000 Mbps Ethernet (MT7530)
WIFI:
- 2.4GHz: 1x MT7603E (2x2:2)
- 5GHz: 1x MT7615E (4x4:4)
- 6 internal antennas
BTN:
- 1x Reset button
- 1x WPS button
- 1x ON/OFF switch (working but unmodifiable)
- 1x Auto/Schedule switch (working but unmodifiable. Read Note #3)
LEDS:
- 1x White led
- 1x Red led
- 1x Amber led
- 1x Blue led
- 2x Blue leds (lan and wan port status: working but unmodifiable)
UART:
- 57600-8-N-1
Everything works correctly.
Currently there is no firmware update available. Because of this, in
order to restore the OEM firmware, you must firstly dump the OEM
firmware from your router before you flash the OpenWrt image.
Backup the OEM Firmware
-----------------------
The following steps are to be intended for users having little to none
experience in linux. Obviously there are many ways to backup the OEM
firmware, but probably this is the easiest way for this router.
Procedure tested on M83A6.V5030.191210 firmware version.
1) Go to http://192.168.10.1/webcmd.shtml
2) Type the following line in the "Command" input box:
mkdir /etc_ro/lighttpd/www/dev; for i in /dev/mtd*ro; do dd if=${i} of=/etc_ro/lighttpd/www${i}; done
3) Click "Apply"
4) After few seconds, in the textarea should appear this output:
16384+0 records in
16384+0 records out
8388608 bytes (8.0MB) copied, 4.038820 seconds, 2.0MB/s
384+0 records in
384+0 records out
196608 bytes (192.0KB) copied, 0.095180 seconds, 2.0MB/s
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.032020 seconds, 2.0MB/s
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.031760 seconds, 2.0MB/s
15744+0 records in
15744+0 records out
8060928 bytes (7.7MB) copied, 3.885280 seconds, 2.0MB/s
dd: can't open '/dev/mtd5ro': No such device
dd: can't open '/dev/mtd6ro': No such device
dd: can't open '/dev/mtd7ro': No such device
Excluding the "X.XXXXXX seconds" part, you should get the same
exact output. If your output doesn't match mine, stop reading
and ask for help in the forum.
5) Open the following links to download the partitions of the OEM FW:
http://192.168.10.1/dev/mtd0ro
http://192.168.10.1/dev/mtd1ro
http://192.168.10.1/dev/mtd2ro
http://192.168.10.1/dev/mtd3ro
http://192.168.10.1/dev/mtd4ro
If one (or more) of these files weight 0 byte, stop reading and ask
for help in the forum.
6) Store these downloaded files in a safe place.
7) Reboot your router to remove any temporary file from your router.
Installation
------------
Flash the initramfs image in the OEM firmware interface.
When openwrt boots, flash the sysupgrade image otherwise you won't be
able to keep configuration between reboots.
Restore OEM Firmware
--------------------
Flash the "mtd4ro" file you previously backed-up directly from LUCI.
Warning: Remember to not keep settings!
Warning2: Remember to force the flash.
Notes
-----
1) The "System Command" page allows to run every command as root.
For example you can use "dd" and "nc" to backup the OEM firmware.
PC (SERVER):
nc -l 5555 > ./mtdXro
ROUTER (CLIENT):
dd if=/dev/mtdXro | nc PC_IP_ADDRESS 5555
2) The OEM web interface accepts only images containing the string
"WN583A6" in the filename.
Currently the OEM interface accepts only the initramfs image
probably because it checks if the ih_size in the image header is
equal to the whole image size (instead of the kernel size)
Read more here:
https://forum.openwrt.org/t/support-for-strong-1200/22768/19
3) The white led (namely "Smart Night Light") can be controller by the
user only if the side switch is set to "Schedule" otherwise it will
be activated by the light condition (there is a photodiode on the
top side of the router)
4) Router mac addresses:
LAN XX:XX:XX:XX:XX:8F
WAN XX:XX:XX:XX:XX:90
WIFI 2G XX:XX:XX:XX:XX:91
WIFI 5G XX:XX:XX:XX:XX:92
LABEL XX:XX:XX:XX:XX:91
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
[remove chosen node, fix whitespace]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-16 21:29:27 +00:00
|
|
|
define Device/winstars_ws-wn583a6
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
ramips: add support for Winstars WS-WN583A6
The Winstars WS-WN583A6 is a wireless repeater with 2 gigabit ethernet
ports. Even if mine is branded as "Gemeita AC2100", the sticker on the
back says WS-WN583A6. So I will refer to it as Winstars WS-WN583A6.
Probably the real product name is the Wavlink WL-WN583A6 because of
the many references to Wavlink in the OEM firmware and bootlog.
Hardware
--------
SoC: Mediatek MT7621AT (880 MHz, 2 cores 4 threads)
RAM: 128MB
FLASH: 8MB NOR (GigaDevice GD25Q64B)
ETH: 2x 10/100/1000 Mbps Ethernet (MT7530)
WIFI:
- 2.4GHz: 1x MT7603E (2x2:2)
- 5GHz: 1x MT7615E (4x4:4)
- 6 internal antennas
BTN:
- 1x Reset button
- 1x WPS button
- 1x ON/OFF switch (working but unmodifiable)
- 1x Auto/Schedule switch (working but unmodifiable. Read Note #3)
LEDS:
- 1x White led
- 1x Red led
- 1x Amber led
- 1x Blue led
- 2x Blue leds (lan and wan port status: working but unmodifiable)
UART:
- 57600-8-N-1
Everything works correctly.
Currently there is no firmware update available. Because of this, in
order to restore the OEM firmware, you must firstly dump the OEM
firmware from your router before you flash the OpenWrt image.
Backup the OEM Firmware
-----------------------
The following steps are to be intended for users having little to none
experience in linux. Obviously there are many ways to backup the OEM
firmware, but probably this is the easiest way for this router.
Procedure tested on M83A6.V5030.191210 firmware version.
1) Go to http://192.168.10.1/webcmd.shtml
2) Type the following line in the "Command" input box:
mkdir /etc_ro/lighttpd/www/dev; for i in /dev/mtd*ro; do dd if=${i} of=/etc_ro/lighttpd/www${i}; done
3) Click "Apply"
4) After few seconds, in the textarea should appear this output:
16384+0 records in
16384+0 records out
8388608 bytes (8.0MB) copied, 4.038820 seconds, 2.0MB/s
384+0 records in
384+0 records out
196608 bytes (192.0KB) copied, 0.095180 seconds, 2.0MB/s
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.032020 seconds, 2.0MB/s
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.031760 seconds, 2.0MB/s
15744+0 records in
15744+0 records out
8060928 bytes (7.7MB) copied, 3.885280 seconds, 2.0MB/s
dd: can't open '/dev/mtd5ro': No such device
dd: can't open '/dev/mtd6ro': No such device
dd: can't open '/dev/mtd7ro': No such device
Excluding the "X.XXXXXX seconds" part, you should get the same
exact output. If your output doesn't match mine, stop reading
and ask for help in the forum.
5) Open the following links to download the partitions of the OEM FW:
http://192.168.10.1/dev/mtd0ro
http://192.168.10.1/dev/mtd1ro
http://192.168.10.1/dev/mtd2ro
http://192.168.10.1/dev/mtd3ro
http://192.168.10.1/dev/mtd4ro
If one (or more) of these files weight 0 byte, stop reading and ask
for help in the forum.
6) Store these downloaded files in a safe place.
7) Reboot your router to remove any temporary file from your router.
Installation
------------
Flash the initramfs image in the OEM firmware interface.
When openwrt boots, flash the sysupgrade image otherwise you won't be
able to keep configuration between reboots.
Restore OEM Firmware
--------------------
Flash the "mtd4ro" file you previously backed-up directly from LUCI.
Warning: Remember to not keep settings!
Warning2: Remember to force the flash.
Notes
-----
1) The "System Command" page allows to run every command as root.
For example you can use "dd" and "nc" to backup the OEM firmware.
PC (SERVER):
nc -l 5555 > ./mtdXro
ROUTER (CLIENT):
dd if=/dev/mtdXro | nc PC_IP_ADDRESS 5555
2) The OEM web interface accepts only images containing the string
"WN583A6" in the filename.
Currently the OEM interface accepts only the initramfs image
probably because it checks if the ih_size in the image header is
equal to the whole image size (instead of the kernel size)
Read more here:
https://forum.openwrt.org/t/support-for-strong-1200/22768/19
3) The white led (namely "Smart Night Light") can be controller by the
user only if the side switch is set to "Schedule" otherwise it will
be activated by the light condition (there is a photodiode on the
top side of the router)
4) Router mac addresses:
LAN XX:XX:XX:XX:XX:8F
WAN XX:XX:XX:XX:XX:90
WIFI 2G XX:XX:XX:XX:XX:91
WIFI 5G XX:XX:XX:XX:XX:92
LABEL XX:XX:XX:XX:XX:91
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
[remove chosen node, fix whitespace]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-16 21:29:27 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
|
|
|
|
IMAGE_SIZE := 7872k
|
|
|
|
|
DEVICE_VENDOR := Winstars
|
|
|
|
|
DEVICE_MODEL := WS-WN583A6
|
|
|
|
|
DEVICE_ALT0_VENDOR := Gemeita
|
|
|
|
|
DEVICE_ALT0_MODEL := AC2100
|
|
|
|
|
KERNEL_INITRAMFS_SUFFIX := -WN583A6$$(KERNEL_SUFFIX)
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt7615e kmod-mt7615-firmware
|
ramips: add support for Winstars WS-WN583A6
The Winstars WS-WN583A6 is a wireless repeater with 2 gigabit ethernet
ports. Even if mine is branded as "Gemeita AC2100", the sticker on the
back says WS-WN583A6. So I will refer to it as Winstars WS-WN583A6.
Probably the real product name is the Wavlink WL-WN583A6 because of
the many references to Wavlink in the OEM firmware and bootlog.
Hardware
--------
SoC: Mediatek MT7621AT (880 MHz, 2 cores 4 threads)
RAM: 128MB
FLASH: 8MB NOR (GigaDevice GD25Q64B)
ETH: 2x 10/100/1000 Mbps Ethernet (MT7530)
WIFI:
- 2.4GHz: 1x MT7603E (2x2:2)
- 5GHz: 1x MT7615E (4x4:4)
- 6 internal antennas
BTN:
- 1x Reset button
- 1x WPS button
- 1x ON/OFF switch (working but unmodifiable)
- 1x Auto/Schedule switch (working but unmodifiable. Read Note #3)
LEDS:
- 1x White led
- 1x Red led
- 1x Amber led
- 1x Blue led
- 2x Blue leds (lan and wan port status: working but unmodifiable)
UART:
- 57600-8-N-1
Everything works correctly.
Currently there is no firmware update available. Because of this, in
order to restore the OEM firmware, you must firstly dump the OEM
firmware from your router before you flash the OpenWrt image.
Backup the OEM Firmware
-----------------------
The following steps are to be intended for users having little to none
experience in linux. Obviously there are many ways to backup the OEM
firmware, but probably this is the easiest way for this router.
Procedure tested on M83A6.V5030.191210 firmware version.
1) Go to http://192.168.10.1/webcmd.shtml
2) Type the following line in the "Command" input box:
mkdir /etc_ro/lighttpd/www/dev; for i in /dev/mtd*ro; do dd if=${i} of=/etc_ro/lighttpd/www${i}; done
3) Click "Apply"
4) After few seconds, in the textarea should appear this output:
16384+0 records in
16384+0 records out
8388608 bytes (8.0MB) copied, 4.038820 seconds, 2.0MB/s
384+0 records in
384+0 records out
196608 bytes (192.0KB) copied, 0.095180 seconds, 2.0MB/s
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.032020 seconds, 2.0MB/s
128+0 records in
128+0 records out
65536 bytes (64.0KB) copied, 0.031760 seconds, 2.0MB/s
15744+0 records in
15744+0 records out
8060928 bytes (7.7MB) copied, 3.885280 seconds, 2.0MB/s
dd: can't open '/dev/mtd5ro': No such device
dd: can't open '/dev/mtd6ro': No such device
dd: can't open '/dev/mtd7ro': No such device
Excluding the "X.XXXXXX seconds" part, you should get the same
exact output. If your output doesn't match mine, stop reading
and ask for help in the forum.
5) Open the following links to download the partitions of the OEM FW:
http://192.168.10.1/dev/mtd0ro
http://192.168.10.1/dev/mtd1ro
http://192.168.10.1/dev/mtd2ro
http://192.168.10.1/dev/mtd3ro
http://192.168.10.1/dev/mtd4ro
If one (or more) of these files weight 0 byte, stop reading and ask
for help in the forum.
6) Store these downloaded files in a safe place.
7) Reboot your router to remove any temporary file from your router.
Installation
------------
Flash the initramfs image in the OEM firmware interface.
When openwrt boots, flash the sysupgrade image otherwise you won't be
able to keep configuration between reboots.
Restore OEM Firmware
--------------------
Flash the "mtd4ro" file you previously backed-up directly from LUCI.
Warning: Remember to not keep settings!
Warning2: Remember to force the flash.
Notes
-----
1) The "System Command" page allows to run every command as root.
For example you can use "dd" and "nc" to backup the OEM firmware.
PC (SERVER):
nc -l 5555 > ./mtdXro
ROUTER (CLIENT):
dd if=/dev/mtdXro | nc PC_IP_ADDRESS 5555
2) The OEM web interface accepts only images containing the string
"WN583A6" in the filename.
Currently the OEM interface accepts only the initramfs image
probably because it checks if the ih_size in the image header is
equal to the whole image size (instead of the kernel size)
Read more here:
https://forum.openwrt.org/t/support-for-strong-1200/22768/19
3) The white led (namely "Smart Night Light") can be controller by the
user only if the side switch is set to "Schedule" otherwise it will
be activated by the light condition (there is a photodiode on the
top side of the router)
4) Router mac addresses:
LAN XX:XX:XX:XX:XX:8F
WAN XX:XX:XX:XX:XX:90
WIFI 2G XX:XX:XX:XX:XX:91
WIFI 5G XX:XX:XX:XX:XX:92
LABEL XX:XX:XX:XX:XX:91
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
[remove chosen node, fix whitespace]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-16 21:29:27 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += winstars_ws-wn583a6
|
|
|
|
|
|
2020-05-30 09:18:50 +00:00
|
|
|
define Device/xiaomi-ac2100
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-05-30 09:18:50 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
|
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
KERNEL_SIZE := 4096k
|
|
|
|
|
IMAGE_SIZE := 120320k
|
|
|
|
|
UBINIZE_OPTS := -E 5
|
|
|
|
|
IMAGES += kernel1.bin rootfs0.bin
|
|
|
|
|
IMAGE/kernel1.bin := append-kernel
|
|
|
|
|
IMAGE/rootfs0.bin := append-ubi | check-size
|
|
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
|
|
|
|
DEVICE_VENDOR := Xiaomi
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt7615e kmod-mt7615-firmware \
|
|
|
|
|
uboot-envtools
|
2020-05-30 09:18:50 +00:00
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/xiaomi_mi-router-ac2100
|
|
|
|
|
$(Device/xiaomi-ac2100)
|
|
|
|
|
DEVICE_MODEL := Mi Router AC2100
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += xiaomi_mi-router-ac2100
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/xiaomi_mir3g
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-15 01:32:02 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2016-09-04 06:56:05 +00:00
|
|
|
BLOCKSIZE := 128k
|
2016-04-01 07:11:48 +00:00
|
|
|
PAGESIZE := 2048
|
2019-07-07 14:27:51 +00:00
|
|
|
KERNEL_SIZE := 4096k
|
2019-07-15 12:55:24 +00:00
|
|
|
IMAGE_SIZE := 124416k
|
2016-09-12 16:20:50 +00:00
|
|
|
UBINIZE_OPTS := -E 5
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGES += kernel1.bin rootfs0.bin
|
|
|
|
|
IMAGE/kernel1.bin := append-kernel
|
2020-03-10 13:58:27 +00:00
|
|
|
IMAGE/rootfs0.bin := append-ubi | check-size
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
|
|
|
|
DEVICE_VENDOR := Xiaomi
|
|
|
|
|
DEVICE_MODEL := Mi Router 3G
|
|
|
|
|
SUPPORTED_DEVICES += R3G
|
|
|
|
|
SUPPORTED_DEVICES += mir3g
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport uboot-envtools
|
2016-04-01 07:11:48 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += xiaomi_mir3g
|
2018-05-03 15:59:27 +00:00
|
|
|
|
2019-10-25 10:18:43 +00:00
|
|
|
define Device/xiaomi_mir3g-v2
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-15 01:32:02 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-10-25 10:18:43 +00:00
|
|
|
IMAGE_SIZE := 14848k
|
|
|
|
|
DEVICE_VENDOR := Xiaomi
|
|
|
|
|
DEVICE_MODEL := Mi Router 3G
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
DEVICE_ALT0_VENDOR := Xiaomi
|
|
|
|
|
DEVICE_ALT0_MODEL := Mi Router 4A
|
|
|
|
|
DEVICE_ALT0_VARIANT := Gigabit Edition
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2
|
2019-10-25 10:18:43 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += xiaomi_mir3g-v2
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/xiaomi_mir3p
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-04-15 01:32:02 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-07 14:27:51 +00:00
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
KERNEL_SIZE:= 4096k
|
|
|
|
|
UBINIZE_OPTS := -E 5
|
2019-07-15 12:55:24 +00:00
|
|
|
IMAGE_SIZE := 255488k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Xiaomi
|
|
|
|
|
DEVICE_MODEL := Mi Router 3 Pro
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
2019-12-19 18:40:33 +00:00
|
|
|
IMAGE/factory.bin := append-kernel | pad-to $$(KERNEL_SIZE) | append-ubi | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7615e kmod-mt7615-firmware kmod-usb3 \
|
|
|
|
|
kmod-usb-ledtrig-usbport uboot-envtools
|
2018-05-03 15:59:27 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += xiaomi_mir3p
|
2016-04-01 07:11:48 +00:00
|
|
|
|
2020-04-23 02:50:21 +00:00
|
|
|
define Device/xiaomi_redmi-router-ac2100
|
2020-05-30 09:18:50 +00:00
|
|
|
$(Device/xiaomi-ac2100)
|
2020-04-23 02:50:21 +00:00
|
|
|
DEVICE_MODEL := Redmi Router AC2100
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += xiaomi_redmi-router-ac2100
|
|
|
|
|
|
2019-09-08 01:52:07 +00:00
|
|
|
define Device/xiaoyu_xy-c5
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-09-08 01:52:07 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
|
|
|
|
DEVICE_VENDOR := XiaoYu
|
|
|
|
|
DEVICE_MODEL := XY-C5
|
2020-07-27 10:30:41 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-usb3 -wpad-basic-wolfssl
|
2019-09-08 01:52:07 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += xiaoyu_xy-c5
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/xzwifi_creativebox-v1
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := CreativeBox
|
|
|
|
|
DEVICE_MODEL := v1
|
2020-03-05 13:57:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-mt7603 kmod-mt76x2 kmod-sdhci-mt7620 \
|
2020-07-27 10:30:41 +00:00
|
|
|
kmod-usb3 -wpad-basic-wolfssl
|
2016-05-10 16:17:54 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += xzwifi_creativebox-v1
|
2016-05-10 16:17:54 +00:00
|
|
|
|
2018-03-29 10:33:02 +00:00
|
|
|
define Device/youhua_wr1200js
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2018-03-29 10:33:02 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := YouHua
|
|
|
|
|
DEVICE_MODEL := WR1200JS
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2018-03-29 10:33:02 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += youhua_wr1200js
|
|
|
|
|
|
2019-03-11 16:21:58 +00:00
|
|
|
define Device/youku_yk-l2
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Youku
|
|
|
|
|
DEVICE_MODEL := YK-L2
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-03-11 16:21:58 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += youku_yk-l2
|
|
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/zbtlink_zbt-we1326
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-09-26 12:44:22 +00:00
|
|
|
DEVICE_VENDOR := Zbtlink
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := ZBT-WE1326
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 kmod-sdhci-mt7620
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += zbt-we1326
|
2017-04-20 03:07:26 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += zbtlink_zbt-we1326
|
2017-04-20 03:07:26 +00:00
|
|
|
|
2017-12-16 23:30:21 +00:00
|
|
|
define Device/zbtlink_zbt-we3526
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-09-26 12:44:22 +00:00
|
|
|
DEVICE_VENDOR := Zbtlink
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := ZBT-WE3526
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-sdhci-mt7620 kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2017-11-07 12:17:06 +00:00
|
|
|
endef
|
2017-12-16 23:30:21 +00:00
|
|
|
TARGET_DEVICES += zbtlink_zbt-we3526
|
2017-11-07 12:17:06 +00:00
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/zbtlink_zbt-wg2626
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-09-26 12:44:22 +00:00
|
|
|
DEVICE_VENDOR := Zbtlink
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := ZBT-WG2626
|
2020-03-05 13:57:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-sdhci-mt7620 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += zbt-wg2626
|
2016-11-18 11:46:27 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += zbtlink_zbt-wg2626
|
2016-11-18 11:46:27 +00:00
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/zbtlink_zbt-wg3526-16m
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-08-23 10:02:48 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-09-26 12:44:22 +00:00
|
|
|
DEVICE_VENDOR := Zbtlink
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := ZBT-WG3526
|
|
|
|
|
DEVICE_VARIANT := 16M
|
2020-03-05 13:57:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-sdhci-mt7620 kmod-mt7603 kmod-mt76x2 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb3 kmod-usb-ledtrig-usbport
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += zbt-wg3526 zbt-wg3526-16M
|
2016-11-18 11:46:27 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += zbtlink_zbt-wg3526-16m
|
2016-11-18 11:46:27 +00:00
|
|
|
|
2019-07-03 21:22:08 +00:00
|
|
|
define Device/zbtlink_zbt-wg3526-32m
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2020-08-23 10:02:48 +00:00
|
|
|
$(Device/uimage-lzma-loader)
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-09-26 12:44:22 +00:00
|
|
|
DEVICE_VENDOR := Zbtlink
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := ZBT-WG3526
|
|
|
|
|
DEVICE_VARIANT := 32M
|
2020-03-05 13:57:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ata-ahci kmod-sdhci-mt7620 kmod-mt7603 kmod-mt76x2 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb3 kmod-usb-ledtrig-usbport
|
2019-07-03 21:22:08 +00:00
|
|
|
SUPPORTED_DEVICES += ac1200pro zbt-wg3526-32M
|
2017-04-01 08:46:44 +00:00
|
|
|
endef
|
2019-07-03 21:22:08 +00:00
|
|
|
TARGET_DEVICES += zbtlink_zbt-wg3526-32m
|
2019-11-11 16:26:44 +00:00
|
|
|
|
|
|
|
|
define Device/zio_freezio
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
2019-11-11 16:26:44 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_VENDOR := ZIO
|
|
|
|
|
DEVICE_MODEL := FREEZIO
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt76x2 kmod-usb3 \
|
2020-08-07 09:56:43 +00:00
|
|
|
kmod-usb-ledtrig-usbport
|
2019-11-11 16:26:44 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zio_freezio
|
ramips: add support for ZyXEL WAP6805 (Altibox WiFi+)
Hardware
--------
SoC: MediaTek MT7621ST
WiFi: MediaTek MT7603
Quantenna QT3840BC
Flash: 128M NAND
RAM: 64M
LED: Dual colour red and green
BTN: Reset
WPS
Eth: 4 x 10/100/1000 connected to MT7621 internal switch
MT7621 RGMII port connected to Quantenna module
GPIO: Power/reset of Quantenna module
Quantenna module
----------------
The Quantenna QT3840BC (or QV840) is a separate SoC running
another Linux installation. It is mounted on a wide mini-PCIe
form factor module, but is connected to the RGMII port of
the MT7621. It loads both a second uboot stage and an os
image from the MT7621 using tftp. The module is configured
using Quantenna specific RPC calls over IP, using 802.1q
over the RGMII link to support multiple SSIDs.
There is no support for using this module as a WiFi device
in OpenWrt. A package with basic firmware and management
tools is being prepared.
Serial ports
------------
Two serial ports with headers:
RRJ1 - 115200 8N1 - Connected to the Quantenna console
J1 - 57600 8N1 - Connected to the MT7621 console
Both share pinout with many other Zyxel/Mitrastar devices:
1 - NC (VDD)
2 - TX
3 - RX
4 - NC (no pin)
5 - GND
Dual system partitions
----------------------
The vendor firmware and boot loader use a dual partition
scheme storing a counter in the header of each partition. The
partition with the highest number will be selected for boot.
OpenWrt does not support this scheme and will always use the
first OS partition. It will reset both counters to zero the
first time sysupgrade is run, making sure the first partition
is selected by the boot loader.
Installation from vendor firmware
---------------------------------
1. Run a DHCP server. The WAP6805 is configured as a client device
and does not have a default static IP address. Make a note of
which address it is assigned
2. tftp the OpenWrt initramfs-kernel.bin image to this address.
Wait for the WAP6805 to reboot.
3. ssh to the OpenWrt initramfs system on 192.168.1.1. Make a
backup of all mtd partitions now. The last used OEM image is
still present in either "Kernel" or "Kernel2" at this point,
and can be restored later if you save a copy.
4. sysupgrade to the OpenWrt sysupgrade.bin image.
Installation from U-Boot
------------------------
This requires serial console access
1. Copy the OpenWrt initramfs-kernel.bin image as "ras.bin" to
your tftp server directory. Configure the server address as
192.168.0.33/24
2. Hit ESC when the message "Hit ESC key to stop autoboot"
appears
3. Type "ATGU" + Enter, and then "2" immediately after pressing enter.
4. Answer Y to the question "Erase Linux in Flash then burn new
one. Are you sure?", and answer the address/filename questions.
Defaults:
Input device IP (192.168.0.2)
Input server IP (192.168.0.33)
Input Linux Kernel filename ("ras.bin")
5. Wait until after you see the message "Done!" and power cycle
the device. It will hang after flashing.
6. Continue with step 3 and 4 from the vendor firmware procedure.
Notes on the WAP6805 U-Boot
---------------------------
The bootloader has been modified with both ZyXELs zyloader and the
device specific dual partition scheme. These changes appear to have
broken a few things. The zyloader shell claims to support a number
of ZyXEL AT commands, but not all of them work. The image selection
scheme is unreliable and inconsistent. A limited U-Boot menu is
available - and used by the above U-Boot install procedure. But
direct booting into an uploaded image does not work, neither with
ram nor with flash. Flashing works, but requires a hard reset after
it is finished.
Reverting to OEM firmware
-------------------------
The OEM firmware can be restored by using mtd write from OpenWrt,
flashing it to the "Kernel" partition. E.g.
ssh root@192.168.1.1 "mtd -r -e Kernel write - Kernel" < oem.bin
OEM firmwares for the WAP6805 are not avaible for public download,
so a backup of the original installation is required. See above.
Alternatively, firmware for the WAP6806 (Armor X1) may be used. This
is exactly the same hardware. But the branding features do obviously
differ.
LED controller
--------------
Hardware implementation is unknown. The dual-color LED is controlled
by 3 GPIOs:
4: red
7: blinking green
13: green
Enabling both red and green makes the LED appear yellow.
The boot loader enables hardware blinking, causing the green LED to blink
slowly on power-on, until the OpenWrt boot mode starts a faster software
blink.
Signed-off-by: Bjørn Mork <bjorn@mork.no>
[fix alphabetic sorting for image build statement]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
2018-04-18 19:57:52 +00:00
|
|
|
|
|
|
|
|
define Device/zyxel_wap6805
|
2020-07-14 14:42:40 +00:00
|
|
|
$(Device/dsa-migration)
|
ramips: add support for ZyXEL WAP6805 (Altibox WiFi+)
Hardware
--------
SoC: MediaTek MT7621ST
WiFi: MediaTek MT7603
Quantenna QT3840BC
Flash: 128M NAND
RAM: 64M
LED: Dual colour red and green
BTN: Reset
WPS
Eth: 4 x 10/100/1000 connected to MT7621 internal switch
MT7621 RGMII port connected to Quantenna module
GPIO: Power/reset of Quantenna module
Quantenna module
----------------
The Quantenna QT3840BC (or QV840) is a separate SoC running
another Linux installation. It is mounted on a wide mini-PCIe
form factor module, but is connected to the RGMII port of
the MT7621. It loads both a second uboot stage and an os
image from the MT7621 using tftp. The module is configured
using Quantenna specific RPC calls over IP, using 802.1q
over the RGMII link to support multiple SSIDs.
There is no support for using this module as a WiFi device
in OpenWrt. A package with basic firmware and management
tools is being prepared.
Serial ports
------------
Two serial ports with headers:
RRJ1 - 115200 8N1 - Connected to the Quantenna console
J1 - 57600 8N1 - Connected to the MT7621 console
Both share pinout with many other Zyxel/Mitrastar devices:
1 - NC (VDD)
2 - TX
3 - RX
4 - NC (no pin)
5 - GND
Dual system partitions
----------------------
The vendor firmware and boot loader use a dual partition
scheme storing a counter in the header of each partition. The
partition with the highest number will be selected for boot.
OpenWrt does not support this scheme and will always use the
first OS partition. It will reset both counters to zero the
first time sysupgrade is run, making sure the first partition
is selected by the boot loader.
Installation from vendor firmware
---------------------------------
1. Run a DHCP server. The WAP6805 is configured as a client device
and does not have a default static IP address. Make a note of
which address it is assigned
2. tftp the OpenWrt initramfs-kernel.bin image to this address.
Wait for the WAP6805 to reboot.
3. ssh to the OpenWrt initramfs system on 192.168.1.1. Make a
backup of all mtd partitions now. The last used OEM image is
still present in either "Kernel" or "Kernel2" at this point,
and can be restored later if you save a copy.
4. sysupgrade to the OpenWrt sysupgrade.bin image.
Installation from U-Boot
------------------------
This requires serial console access
1. Copy the OpenWrt initramfs-kernel.bin image as "ras.bin" to
your tftp server directory. Configure the server address as
192.168.0.33/24
2. Hit ESC when the message "Hit ESC key to stop autoboot"
appears
3. Type "ATGU" + Enter, and then "2" immediately after pressing enter.
4. Answer Y to the question "Erase Linux in Flash then burn new
one. Are you sure?", and answer the address/filename questions.
Defaults:
Input device IP (192.168.0.2)
Input server IP (192.168.0.33)
Input Linux Kernel filename ("ras.bin")
5. Wait until after you see the message "Done!" and power cycle
the device. It will hang after flashing.
6. Continue with step 3 and 4 from the vendor firmware procedure.
Notes on the WAP6805 U-Boot
---------------------------
The bootloader has been modified with both ZyXELs zyloader and the
device specific dual partition scheme. These changes appear to have
broken a few things. The zyloader shell claims to support a number
of ZyXEL AT commands, but not all of them work. The image selection
scheme is unreliable and inconsistent. A limited U-Boot menu is
available - and used by the above U-Boot install procedure. But
direct booting into an uploaded image does not work, neither with
ram nor with flash. Flashing works, but requires a hard reset after
it is finished.
Reverting to OEM firmware
-------------------------
The OEM firmware can be restored by using mtd write from OpenWrt,
flashing it to the "Kernel" partition. E.g.
ssh root@192.168.1.1 "mtd -r -e Kernel write - Kernel" < oem.bin
OEM firmwares for the WAP6805 are not avaible for public download,
so a backup of the original installation is required. See above.
Alternatively, firmware for the WAP6806 (Armor X1) may be used. This
is exactly the same hardware. But the branding features do obviously
differ.
LED controller
--------------
Hardware implementation is unknown. The dual-color LED is controlled
by 3 GPIOs:
4: red
7: blinking green
13: green
Enabling both red and green makes the LED appear yellow.
The boot loader enables hardware blinking, causing the green LED to blink
slowly on power-on, until the OpenWrt boot mode starts a faster software
blink.
Signed-off-by: Bjørn Mork <bjorn@mork.no>
[fix alphabetic sorting for image build statement]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
2018-04-18 19:57:52 +00:00
|
|
|
BLOCKSIZE := 128k
|
|
|
|
|
PAGESIZE := 2048
|
|
|
|
|
KERNEL_SIZE := 4096k
|
|
|
|
|
UBINIZE_OPTS := -E 5
|
|
|
|
|
IMAGE_SIZE := 32448k
|
|
|
|
|
DEVICE_VENDOR := ZyXEL
|
|
|
|
|
DEVICE_MODEL := WAP6805
|
2020-08-07 09:56:43 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt7603 kmod-mt7621-qtn-rgmii
|
2020-07-10 12:16:23 +00:00
|
|
|
KERNEL := $(KERNEL_DTB) | uImage lzma | uimage-padhdr 160
|
ramips: add support for ZyXEL WAP6805 (Altibox WiFi+)
Hardware
--------
SoC: MediaTek MT7621ST
WiFi: MediaTek MT7603
Quantenna QT3840BC
Flash: 128M NAND
RAM: 64M
LED: Dual colour red and green
BTN: Reset
WPS
Eth: 4 x 10/100/1000 connected to MT7621 internal switch
MT7621 RGMII port connected to Quantenna module
GPIO: Power/reset of Quantenna module
Quantenna module
----------------
The Quantenna QT3840BC (or QV840) is a separate SoC running
another Linux installation. It is mounted on a wide mini-PCIe
form factor module, but is connected to the RGMII port of
the MT7621. It loads both a second uboot stage and an os
image from the MT7621 using tftp. The module is configured
using Quantenna specific RPC calls over IP, using 802.1q
over the RGMII link to support multiple SSIDs.
There is no support for using this module as a WiFi device
in OpenWrt. A package with basic firmware and management
tools is being prepared.
Serial ports
------------
Two serial ports with headers:
RRJ1 - 115200 8N1 - Connected to the Quantenna console
J1 - 57600 8N1 - Connected to the MT7621 console
Both share pinout with many other Zyxel/Mitrastar devices:
1 - NC (VDD)
2 - TX
3 - RX
4 - NC (no pin)
5 - GND
Dual system partitions
----------------------
The vendor firmware and boot loader use a dual partition
scheme storing a counter in the header of each partition. The
partition with the highest number will be selected for boot.
OpenWrt does not support this scheme and will always use the
first OS partition. It will reset both counters to zero the
first time sysupgrade is run, making sure the first partition
is selected by the boot loader.
Installation from vendor firmware
---------------------------------
1. Run a DHCP server. The WAP6805 is configured as a client device
and does not have a default static IP address. Make a note of
which address it is assigned
2. tftp the OpenWrt initramfs-kernel.bin image to this address.
Wait for the WAP6805 to reboot.
3. ssh to the OpenWrt initramfs system on 192.168.1.1. Make a
backup of all mtd partitions now. The last used OEM image is
still present in either "Kernel" or "Kernel2" at this point,
and can be restored later if you save a copy.
4. sysupgrade to the OpenWrt sysupgrade.bin image.
Installation from U-Boot
------------------------
This requires serial console access
1. Copy the OpenWrt initramfs-kernel.bin image as "ras.bin" to
your tftp server directory. Configure the server address as
192.168.0.33/24
2. Hit ESC when the message "Hit ESC key to stop autoboot"
appears
3. Type "ATGU" + Enter, and then "2" immediately after pressing enter.
4. Answer Y to the question "Erase Linux in Flash then burn new
one. Are you sure?", and answer the address/filename questions.
Defaults:
Input device IP (192.168.0.2)
Input server IP (192.168.0.33)
Input Linux Kernel filename ("ras.bin")
5. Wait until after you see the message "Done!" and power cycle
the device. It will hang after flashing.
6. Continue with step 3 and 4 from the vendor firmware procedure.
Notes on the WAP6805 U-Boot
---------------------------
The bootloader has been modified with both ZyXELs zyloader and the
device specific dual partition scheme. These changes appear to have
broken a few things. The zyloader shell claims to support a number
of ZyXEL AT commands, but not all of them work. The image selection
scheme is unreliable and inconsistent. A limited U-Boot menu is
available - and used by the above U-Boot install procedure. But
direct booting into an uploaded image does not work, neither with
ram nor with flash. Flashing works, but requires a hard reset after
it is finished.
Reverting to OEM firmware
-------------------------
The OEM firmware can be restored by using mtd write from OpenWrt,
flashing it to the "Kernel" partition. E.g.
ssh root@192.168.1.1 "mtd -r -e Kernel write - Kernel" < oem.bin
OEM firmwares for the WAP6805 are not avaible for public download,
so a backup of the original installation is required. See above.
Alternatively, firmware for the WAP6806 (Armor X1) may be used. This
is exactly the same hardware. But the branding features do obviously
differ.
LED controller
--------------
Hardware implementation is unknown. The dual-color LED is controlled
by 3 GPIOs:
4: red
7: blinking green
13: green
Enabling both red and green makes the LED appear yellow.
The boot loader enables hardware blinking, causing the green LED to blink
slowly on power-on, until the OpenWrt boot mode starts a faster software
blink.
Signed-off-by: Bjørn Mork <bjorn@mork.no>
[fix alphabetic sorting for image build statement]
Signed-off-by: Petr Štetiar <ynezz@true.cz>
2018-04-18 19:57:52 +00:00
|
|
|
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zyxel_wap6805
|
