2016-04-01 07:11:48 +00:00
|
|
|
#
|
2017-08-26 01:49:45 +00:00
|
|
|
# MT76x8 Profiles
|
2016-04-01 07:11:48 +00:00
|
|
|
#
|
|
|
|
|
|
2020-01-29 17:21:53 +00:00
|
|
|
include ./common-tp-link.mk
|
|
|
|
|
|
2020-01-21 20:54:50 +00:00
|
|
|
DEFAULT_SOC := mt7628an
|
|
|
|
|
|
2018-01-26 15:21:34 +00:00
|
|
|
define Device/alfa-network_awusfree1
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := ALFA Network
|
|
|
|
|
DEVICE_MODEL := AWUSFREE1
|
2018-01-26 15:21:34 +00:00
|
|
|
DEVICE_PACKAGES := uboot-envtools
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += alfa-network_awusfree1
|
|
|
|
|
|
2020-04-16 18:42:29 +00:00
|
|
|
define Device/asus_rt-n10p-v3
|
|
|
|
|
IMAGE_SIZE := 7872k
|
|
|
|
|
DEVICE_VENDOR := Asus
|
|
|
|
|
DEVICE_MODEL := RT-N10P
|
|
|
|
|
DEVICE_VARIANT := V3
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += asus_rt-n10p-v3
|
|
|
|
|
|
|
|
|
|
define Device/asus_rt-n11p-b1
|
|
|
|
|
IMAGE_SIZE := 7872k
|
|
|
|
|
DEVICE_VENDOR := Asus
|
|
|
|
|
DEVICE_MODEL := RT-N11P
|
|
|
|
|
DEVICE_VARIANT := B1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += asus_rt-n11p-b1
|
|
|
|
|
|
|
|
|
|
define Device/asus_rt-n12-vp-b1
|
|
|
|
|
IMAGE_SIZE := 7872k
|
|
|
|
|
DEVICE_VENDOR := Asus
|
|
|
|
|
DEVICE_MODEL := RT-N12 VP
|
|
|
|
|
DEVICE_VARIANT := B1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += asus_rt-n12-vp-b1
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/buffalo_wcr-1166ds
|
2019-07-15 12:55:28 +00:00
|
|
|
IMAGE_SIZE := 7936k
|
2019-07-07 14:27:51 +00:00
|
|
|
BUFFALO_TAG_PLATFORM := MTK
|
|
|
|
|
BUFFALO_TAG_VERSION := 9.99
|
|
|
|
|
BUFFALO_TAG_MINOR := 9.99
|
|
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := trx | pad-rootfs | append-metadata
|
2019-12-19 18:40:33 +00:00
|
|
|
IMAGE/factory.bin := trx -M 0x746f435c | pad-rootfs | append-metadata | \
|
2019-07-07 14:27:51 +00:00
|
|
|
buffalo-enc WCR-1166DS $$(BUFFALO_TAG_VERSION) -l | \
|
2019-12-19 18:40:33 +00:00
|
|
|
buffalo-tag-dhp WCR-1166DS JP JP | buffalo-enc-tag -l | buffalo-dhp-image
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Buffalo
|
|
|
|
|
DEVICE_MODEL := WCR-1166DS
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
SUPPORTED_DEVICES += wcr-1166ds
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += buffalo_wcr-1166ds
|
|
|
|
|
|
ramips: add CUDY WR1000 support
Cudy WR1200 is an AC1200 AP with 3-port FE and 2 non-detachable antennas
Specifications:
MT7628 (580 MHz)
64 MB of RAM (DDR2)
8 MB of FLASH
2T2R 2.4 GHz (MT7628)
2T2R 5 GHz (MT7612E)
3x 10/100 Mbps Ethernet (2 LAN + 1 WAN)
2x external, non-detachable antennas (5dbi)
UART header on PCB (57600 8n1)
7x LED, 2x button
Known issues:
The Power LED is always ON, probably because it is connected
directly to power.
Flash instructions
------------------
Load the ...-factory.bin image via the stock web interface.
Openwrt upgrade instructions
----------------------------
Use the ...-sysupgrade.bin image for future upgrades.
Revert to stock FW
------------------
Warning! This tutorial will work only with the following OEM FW:
WR1000_EU_92.122.2.4987.201806261618.bin
WR1000_US_92.122.2.4987.201806261609.bin
If in the future these firmwares will not be available anymore,
you have to find the new XOR key.
1) Download the original FW from the Cudy website.
(For example WR1000_EU_92.122.2.4987.201806261618.bin)
2) Remove the header.
dd if="WR1000_EU_92.122.2.4987.201806261618.bin" of="WR1000_EU_92.122.2.4987.201806261618.bin.mod" skip=8 bs=64
3) XOR the new file with the region key.
FOR EU: 7B76741E67594351555042461D625F4545514B1B03050208000603020803000D
FOR US: 7B76741E675943555D5442461D625F454555431F03050208000603060007010C
You can use OpenWrt's tools/firmware-utils/src/xorimage.c tool for this:
xorimage -i WR1000..bin.mod -o stock-firmware.bin -x -p 7B767..
Or, you can use this tool (CHANGE THE XOR KEY ACCORDINGLY!):
https://gchq.github.io/CyberChef/#recipe=XOR(%7B'option':'Hex','string':''%7D,'',false)
4) Check the resulting decrypted image.
Check if bytes from 0x20 to 0x3f are:
4C 69 6E 75 78 20 4B 65 72 6E 65 6C 20 49 6D 61 67 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Alternatively, you can use u-boot's tool dumpimage tool to check
if the decryption was successful. It should look like:
# dumpimage -l stock-firmware.bin
Image Name: Linux Kernel Image
Created: Tue Jun 26 10:24:54 2018
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 4406635 Bytes = 4303.35 KiB = 4.20 MiB
Load Address: 80000000
Entry Point: 8000c150
5) Flash it via forced firmware upgrade and don't "Keep Settings"
CLI: sysupgrade -F -n stock-firmware.bin
LuCI: make sure to click on the "Keep settings" checkbox
to disable it. You'll need to do this !TWICE! because
on the first try, LuCI will refuse the image and reset
the "Keep settings" to enable. However a new
"Force upgrade" checkbox will appear as well.
Make sure to do this very carefully!
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
[added wifi compatible, spiffed-up the returned to stock instructions]
2019-05-20 03:20:37 +00:00
|
|
|
define Device/cudy_wr1000
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
ramips: add CUDY WR1000 support
Cudy WR1200 is an AC1200 AP with 3-port FE and 2 non-detachable antennas
Specifications:
MT7628 (580 MHz)
64 MB of RAM (DDR2)
8 MB of FLASH
2T2R 2.4 GHz (MT7628)
2T2R 5 GHz (MT7612E)
3x 10/100 Mbps Ethernet (2 LAN + 1 WAN)
2x external, non-detachable antennas (5dbi)
UART header on PCB (57600 8n1)
7x LED, 2x button
Known issues:
The Power LED is always ON, probably because it is connected
directly to power.
Flash instructions
------------------
Load the ...-factory.bin image via the stock web interface.
Openwrt upgrade instructions
----------------------------
Use the ...-sysupgrade.bin image for future upgrades.
Revert to stock FW
------------------
Warning! This tutorial will work only with the following OEM FW:
WR1000_EU_92.122.2.4987.201806261618.bin
WR1000_US_92.122.2.4987.201806261609.bin
If in the future these firmwares will not be available anymore,
you have to find the new XOR key.
1) Download the original FW from the Cudy website.
(For example WR1000_EU_92.122.2.4987.201806261618.bin)
2) Remove the header.
dd if="WR1000_EU_92.122.2.4987.201806261618.bin" of="WR1000_EU_92.122.2.4987.201806261618.bin.mod" skip=8 bs=64
3) XOR the new file with the region key.
FOR EU: 7B76741E67594351555042461D625F4545514B1B03050208000603020803000D
FOR US: 7B76741E675943555D5442461D625F454555431F03050208000603060007010C
You can use OpenWrt's tools/firmware-utils/src/xorimage.c tool for this:
xorimage -i WR1000..bin.mod -o stock-firmware.bin -x -p 7B767..
Or, you can use this tool (CHANGE THE XOR KEY ACCORDINGLY!):
https://gchq.github.io/CyberChef/#recipe=XOR(%7B'option':'Hex','string':''%7D,'',false)
4) Check the resulting decrypted image.
Check if bytes from 0x20 to 0x3f are:
4C 69 6E 75 78 20 4B 65 72 6E 65 6C 20 49 6D 61 67 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Alternatively, you can use u-boot's tool dumpimage tool to check
if the decryption was successful. It should look like:
# dumpimage -l stock-firmware.bin
Image Name: Linux Kernel Image
Created: Tue Jun 26 10:24:54 2018
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 4406635 Bytes = 4303.35 KiB = 4.20 MiB
Load Address: 80000000
Entry Point: 8000c150
5) Flash it via forced firmware upgrade and don't "Keep Settings"
CLI: sysupgrade -F -n stock-firmware.bin
LuCI: make sure to click on the "Keep settings" checkbox
to disable it. You'll need to do this !TWICE! because
on the first try, LuCI will refuse the image and reset
the "Keep settings" to enable. However a new
"Force upgrade" checkbox will appear as well.
Make sure to do this very carefully!
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
[added wifi compatible, spiffed-up the returned to stock instructions]
2019-05-20 03:20:37 +00:00
|
|
|
IMAGES += factory.bin
|
2020-05-08 16:21:06 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | check-size | jcg-header 92.122
|
2019-12-12 19:26:06 +00:00
|
|
|
JCG_MAXSIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Cudy
|
|
|
|
|
DEVICE_MODEL := WR1000
|
ramips: add CUDY WR1000 support
Cudy WR1200 is an AC1200 AP with 3-port FE and 2 non-detachable antennas
Specifications:
MT7628 (580 MHz)
64 MB of RAM (DDR2)
8 MB of FLASH
2T2R 2.4 GHz (MT7628)
2T2R 5 GHz (MT7612E)
3x 10/100 Mbps Ethernet (2 LAN + 1 WAN)
2x external, non-detachable antennas (5dbi)
UART header on PCB (57600 8n1)
7x LED, 2x button
Known issues:
The Power LED is always ON, probably because it is connected
directly to power.
Flash instructions
------------------
Load the ...-factory.bin image via the stock web interface.
Openwrt upgrade instructions
----------------------------
Use the ...-sysupgrade.bin image for future upgrades.
Revert to stock FW
------------------
Warning! This tutorial will work only with the following OEM FW:
WR1000_EU_92.122.2.4987.201806261618.bin
WR1000_US_92.122.2.4987.201806261609.bin
If in the future these firmwares will not be available anymore,
you have to find the new XOR key.
1) Download the original FW from the Cudy website.
(For example WR1000_EU_92.122.2.4987.201806261618.bin)
2) Remove the header.
dd if="WR1000_EU_92.122.2.4987.201806261618.bin" of="WR1000_EU_92.122.2.4987.201806261618.bin.mod" skip=8 bs=64
3) XOR the new file with the region key.
FOR EU: 7B76741E67594351555042461D625F4545514B1B03050208000603020803000D
FOR US: 7B76741E675943555D5442461D625F454555431F03050208000603060007010C
You can use OpenWrt's tools/firmware-utils/src/xorimage.c tool for this:
xorimage -i WR1000..bin.mod -o stock-firmware.bin -x -p 7B767..
Or, you can use this tool (CHANGE THE XOR KEY ACCORDINGLY!):
https://gchq.github.io/CyberChef/#recipe=XOR(%7B'option':'Hex','string':''%7D,'',false)
4) Check the resulting decrypted image.
Check if bytes from 0x20 to 0x3f are:
4C 69 6E 75 78 20 4B 65 72 6E 65 6C 20 49 6D 61 67 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Alternatively, you can use u-boot's tool dumpimage tool to check
if the decryption was successful. It should look like:
# dumpimage -l stock-firmware.bin
Image Name: Linux Kernel Image
Created: Tue Jun 26 10:24:54 2018
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 4406635 Bytes = 4303.35 KiB = 4.20 MiB
Load Address: 80000000
Entry Point: 8000c150
5) Flash it via forced firmware upgrade and don't "Keep Settings"
CLI: sysupgrade -F -n stock-firmware.bin
LuCI: make sure to click on the "Keep settings" checkbox
to disable it. You'll need to do this !TWICE! because
on the first try, LuCI will refuse the image and reset
the "Keep settings" to enable. However a new
"Force upgrade" checkbox will appear as well.
Make sure to do this very carefully!
Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
[added wifi compatible, spiffed-up the returned to stock instructions]
2019-05-20 03:20:37 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
SUPPORTED_DEVICES += wr1000
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += cudy_wr1000
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/d-team_pbr-d1
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := PandoraBox
|
|
|
|
|
DEVICE_MODEL := PBR-D1
|
2018-02-19 05:35:42 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += pbr-d1
|
2018-02-19 05:35:42 +00:00
|
|
|
endef
|
2019-07-07 14:27:51 +00:00
|
|
|
TARGET_DEVICES += d-team_pbr-d1
|
2018-02-19 05:35:42 +00:00
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/duzun_dm06
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := DuZun
|
|
|
|
|
DEVICE_MODEL := DM06
|
2016-10-19 10:09:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += duzun-dm06
|
2016-05-11 10:21:45 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += duzun_dm06
|
2017-08-26 01:49:45 +00:00
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/glinet_gl-mt300n-v2
|
2017-08-26 01:49:45 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := GL.iNet
|
|
|
|
|
DEVICE_MODEL := GL-MT300N
|
|
|
|
|
DEVICE_VARIANT := V2
|
2017-08-26 01:49:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += gl-mt300n-v2
|
2017-08-26 01:49:45 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += glinet_gl-mt300n-v2
|
2016-04-01 07:11:48 +00:00
|
|
|
|
2020-01-05 23:31:24 +00:00
|
|
|
define Device/glinet_microuter-n300
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_VENDOR := GL.iNet
|
|
|
|
|
DEVICE_MODEL := microuter-N300
|
|
|
|
|
SUPPORTED_DEVICES += microuter-n300
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += glinet_microuter-n300
|
|
|
|
|
|
2019-04-12 22:05:47 +00:00
|
|
|
define Device/glinet_vixmini
|
|
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := GL.iNet
|
|
|
|
|
DEVICE_MODEL := VIXMINI
|
2019-04-12 22:05:47 +00:00
|
|
|
SUPPORTED_DEVICES += vixmini
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += glinet_vixmini
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/hilink_hlk-7628n
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := HILINK
|
|
|
|
|
DEVICE_MODEL := HLK-7628N
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += hilink_hlk-7628n
|
|
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/hiwifi_hc5661a
|
2019-07-15 12:55:28 +00:00
|
|
|
IMAGE_SIZE := 15808k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := HiWiFi
|
|
|
|
|
DEVICE_MODEL := HC5661A
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += hc5661a
|
2017-02-24 23:19:15 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += hiwifi_hc5661a
|
2017-02-24 23:19:15 +00:00
|
|
|
|
2019-07-23 12:12:48 +00:00
|
|
|
define Device/hiwifi_hc5761a
|
|
|
|
|
IMAGE_SIZE := 15808k
|
|
|
|
|
DEVICE_VENDOR := HiWiFi
|
|
|
|
|
DEVICE_MODEL := HC5761A
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += hiwifi_hc5761a
|
|
|
|
|
|
2018-08-09 17:22:46 +00:00
|
|
|
define Device/hiwifi_hc5861b
|
|
|
|
|
IMAGE_SIZE := 15808k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := HiWiFi
|
|
|
|
|
DEVICE_MODEL := HC5861B
|
2018-11-30 10:10:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2018-08-09 17:22:46 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += hiwifi_hc5861b
|
|
|
|
|
|
2019-08-18 05:50:20 +00:00
|
|
|
define Device/iptime_a3
|
|
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
UIMAGE_NAME := a3
|
|
|
|
|
DEVICE_VENDOR := ipTIME
|
|
|
|
|
DEVICE_MODEL := A3
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iptime_a3
|
|
|
|
|
|
2019-07-20 18:34:59 +00:00
|
|
|
define Device/iptime_a604m
|
|
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
UIMAGE_NAME := a604m
|
|
|
|
|
DEVICE_VENDOR := ipTIME
|
|
|
|
|
DEVICE_MODEL := A604M
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += iptime_a604m
|
|
|
|
|
|
ramips: add support for JS76x8 series DEV boards
This commit adds support for the Jotale JS76x8 series development boards.
These devices have the following specifications:
- SOC: MT7628AN/NN, MT7688AN, MT7628DAN
- RAM of MT7628AN/NN and MT7688AN: 64/128/256 MB (DDR2)
- RAM of MT7628DAN: 64 MB (DDR2)
- FLASH:8/16/32 MB (SPI NOR)
- Ethernet:3x 10/100 Mbps ethernet ports (MT76x8 built-in switch)
- WIFI:1x 2T2R 2.4 GHz Wi-Fi
- LEDs:1x system status green LED, 1x wifi green LED,
3x ethernet green LED
- Buttons:1x reset button
- 1x microSD slot
- 4x USB 2.0 port
- 1x mini-usb debug UART
- 1x DC jack for main power (DC 5V)
- 1x TTL/RS232 UART
- 1x TTL/RS485 UART
- 13x GPIO header
- 1x audio codec(wm8960)
Installation via OpenWrt:
The original firmware is OpenWrt, so both LuCI and sysupgrade can be used.
Installation via U-boot web:
1. Power on board with reset button pressed, release it
after wifi led start blinking.
2. Setup static IP 192.168.1.123/4 on your PC.
3. Go to 192.168.1.8 in browser and upload "sysupgrade" image.
Installation via U-boot tftp:
1. Connect to serial console at the mini usb, which has been connected to UART0
on board (115200 8N1)
2. Setup static IP 192.168.1.123/4 on your PC.
3. Place openwrt-firmware.bin on your PC tftp server (192.168.1.123).
3. Connect one of LAN ports on board to your PC.
4. Start terminal software (e.g. screen /dev/ttyUSB0 115200) on PC.
5. Apply power to board.
6. Interrupt U-boot with keypress of "2".
7. At u-boot prompts:
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) Y
Input device IP (192.168.1.8) ==:192.168.1.8
Input server IP (192.168.1.123) ==:192.168.1.123
Input Linux Kernel filename (root_uImage) ==:openwrt-firmware.bin
8. board will download file from tftp server, write it to flash and reboot.
Signed-off-by: Robinson Wu <wurobinson@qq.com>
[add license to DTS files, fix state_default and reduce to the mimimum,
move phy0tpt trigger to DTS, drop ucidef_set_led_timer, fix network ports]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-17 07:32:53 +00:00
|
|
|
define Device/jotale_js76x8
|
|
|
|
|
DEVICE_VENDOR := Jotale
|
|
|
|
|
DEVICE_MODEL := JS76x8
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Device/jotale_js76x8-8m
|
|
|
|
|
$(Device/jotale_js76x8)
|
|
|
|
|
IMAGE_SIZE := 7872k
|
|
|
|
|
DEVICE_VARIANT := 8M
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += jotale_js76x8-8m
|
|
|
|
|
|
|
|
|
|
define Device/jotale_js76x8-16m
|
|
|
|
|
$(Device/jotale_js76x8)
|
|
|
|
|
IMAGE_SIZE := 16064k
|
|
|
|
|
DEVICE_VARIANT := 16M
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += jotale_js76x8-16m
|
|
|
|
|
|
|
|
|
|
define Device/jotale_js76x8-32m
|
|
|
|
|
$(Device/jotale_js76x8)
|
|
|
|
|
IMAGE_SIZE := 32448k
|
|
|
|
|
DEVICE_VARIANT := 32M
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += jotale_js76x8-32m
|
|
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/mediatek_linkit-smart-7688
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := MediaTek
|
|
|
|
|
DEVICE_MODEL := LinkIt Smart 7688
|
2019-09-14 15:25:04 +00:00
|
|
|
DEVICE_PACKAGES:= kmod-usb2 kmod-usb-ohci uboot-envtools kmod-sdhci-mt7620
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += linkits7688 linkits7688d
|
2017-08-26 01:49:45 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += mediatek_linkit-smart-7688
|
2017-08-26 01:49:45 +00:00
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/mediatek_mt7628an-eval-board
|
2017-08-26 01:49:45 +00:00
|
|
|
BLOCKSIZE := 64k
|
2019-07-15 12:55:28 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := MediaTek
|
|
|
|
|
DEVICE_MODEL := MT7628 EVB
|
2017-08-26 01:49:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += mt7628
|
2017-08-26 01:49:45 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += mediatek_mt7628an-eval-board
|
2017-08-26 01:49:45 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/mercury_mac1200r-v2
|
2019-07-15 12:55:28 +00:00
|
|
|
IMAGE_SIZE := 7936k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Mercury
|
|
|
|
|
DEVICE_MODEL := MAC1200R
|
|
|
|
|
DEVICE_VARIANT := v2.0
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
SUPPORTED_DEVICES += mac1200rv2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += mercury_mac1200r-v2
|
|
|
|
|
|
2020-07-10 10:00:08 +00:00
|
|
|
define Device/netgear_r6020
|
2020-08-03 17:23:50 +00:00
|
|
|
$(Device/netgear_sercomm_nor)
|
2020-07-10 10:00:08 +00:00
|
|
|
IMAGE_SIZE := 7104k
|
|
|
|
|
DEVICE_MODEL := R6020
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
SERCOMM_HWNAME := R6020
|
|
|
|
|
SERCOMM_HWID := CFR
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x0040
|
2020-08-03 17:23:50 +00:00
|
|
|
SERCOMM_PAD := 576k
|
ramips: add support for Netgear R6020
This adds support for the Netgear R6020, aka Netgear AC750.
The R6020 appears to be the same hardware as the Netgear R6080,
aka Netgear AC1000, but it has a slightly different flash layout,
and no USB ports.
Specification:
SoC: MediaTek MT7628 (580 MHz)
Flash: 8 MiB
RAM: 64 MiB
Wireless: 2.4Ghz (builtin) and 5Ghz (MT7612E)
LAN speed: 10/100
LAN ports: 4
WAN speed: 10/100
WAN ports: 1
UART (57600 8N1) on PCB
MAC addresses based on vendor firmware:
LAN *:88 0x4
WAN *:89
WLAN2 *:88 0x4
WLAN5 *:8a 0x8004
The factory partition might have been corrupted beforehand. However,
the comparison of vendor firmware and OpenWrt still allowed to retrieve
a meaningful assignment that also matches the other similar devices.
Installation:
Flashing OpenWRT from stock firmware requires nmrpflash. Use an ethernet
cable to connect to LAN port 1 of the R6020, and power the R6020 off.
From the connected workstation, run
`nmrpflash -i eth0 -f openwrt-ramips-mt76x8-netgear_r6020-squashfs-factory.img`,
replacing eth0 with the appropriate interface (can be identified by
running `nmrpflash -L`). Then power on the R6020. After flashing has finished,
power cycle the R6020, and it will boot into OpenWRT. Once OpenWRT has been
installed, subsequent flashes can use the web interface and sysupgrade files.
Signed-off-by: Tim Thorpe <timfthorpe@gmail.com>
[slightly extend commit message, fix whitespaces in DTS, align From:
with Signed-off-by]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-07-09 03:07:35 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_r6020
|
|
|
|
|
|
ramips: add support for Netgear R6080
This adds support for the Netgear R6080, aka Netgear AC1000.
The R6080 has almost the same hardware as the Netgear R6120,
aka Netgear AC1200, but it lacks the USB port, has only 8 MiB flash and
uses a different SERCOMM_HWID.
Specification:
SoC: MediaTek MT7628 (580 MHz)
Flash: 8 MiB
RAM: 64 MiB
Wireless: 2.4Ghz (builtin) and 5Ghz (MT7612E)
LAN speed: 10/100
LAN ports: 4
WAN speed: 10/100
WAN ports: 1
UART (57600 8N1) on PCB
Installation:
Flashing OpenWRT from stock firmware requires nmrpflash. Use an ethernet
cable to connect to LAN port 1 of the R6080, and power the R6080 off.
From the connected workstation, run
`nmrpflash -i eth0 -f openwrt-ramips-mt76x8-netgear_r6080-squashfs-factory.img`,
replacing eth0 with the appropriate interface (can be identified by
running `nmrpflash -L`). Then power on the R6080. After flashing has finished,
power cycle the R6080, and it will boot into OpenWRT. Once OpenWRT has been
installed, subsequent flashes can use the web interface and sysupgrade files.
Signed-off-by: Alex Lewontin <alex.c.lewontin@gmail.com>
[rebase and adjust for 5.4]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-02-21 20:56:44 +00:00
|
|
|
define Device/netgear_r6080
|
2020-08-03 17:23:50 +00:00
|
|
|
$(Device/netgear_sercomm_nor)
|
ramips: add support for Netgear R6080
This adds support for the Netgear R6080, aka Netgear AC1000.
The R6080 has almost the same hardware as the Netgear R6120,
aka Netgear AC1200, but it lacks the USB port, has only 8 MiB flash and
uses a different SERCOMM_HWID.
Specification:
SoC: MediaTek MT7628 (580 MHz)
Flash: 8 MiB
RAM: 64 MiB
Wireless: 2.4Ghz (builtin) and 5Ghz (MT7612E)
LAN speed: 10/100
LAN ports: 4
WAN speed: 10/100
WAN ports: 1
UART (57600 8N1) on PCB
Installation:
Flashing OpenWRT from stock firmware requires nmrpflash. Use an ethernet
cable to connect to LAN port 1 of the R6080, and power the R6080 off.
From the connected workstation, run
`nmrpflash -i eth0 -f openwrt-ramips-mt76x8-netgear_r6080-squashfs-factory.img`,
replacing eth0 with the appropriate interface (can be identified by
running `nmrpflash -L`). Then power on the R6080. After flashing has finished,
power cycle the R6080, and it will boot into OpenWRT. Once OpenWRT has been
installed, subsequent flashes can use the web interface and sysupgrade files.
Signed-off-by: Alex Lewontin <alex.c.lewontin@gmail.com>
[rebase and adjust for 5.4]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-02-21 20:56:44 +00:00
|
|
|
IMAGE_SIZE := 7552k
|
|
|
|
|
DEVICE_MODEL := R6080
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2020-07-10 10:00:08 +00:00
|
|
|
SERCOMM_HWNAME := R6080
|
ramips: add support for Netgear R6080
This adds support for the Netgear R6080, aka Netgear AC1000.
The R6080 has almost the same hardware as the Netgear R6120,
aka Netgear AC1200, but it lacks the USB port, has only 8 MiB flash and
uses a different SERCOMM_HWID.
Specification:
SoC: MediaTek MT7628 (580 MHz)
Flash: 8 MiB
RAM: 64 MiB
Wireless: 2.4Ghz (builtin) and 5Ghz (MT7612E)
LAN speed: 10/100
LAN ports: 4
WAN speed: 10/100
WAN ports: 1
UART (57600 8N1) on PCB
Installation:
Flashing OpenWRT from stock firmware requires nmrpflash. Use an ethernet
cable to connect to LAN port 1 of the R6080, and power the R6080 off.
From the connected workstation, run
`nmrpflash -i eth0 -f openwrt-ramips-mt76x8-netgear_r6080-squashfs-factory.img`,
replacing eth0 with the appropriate interface (can be identified by
running `nmrpflash -L`). Then power on the R6080. After flashing has finished,
power cycle the R6080, and it will boot into OpenWRT. Once OpenWRT has been
installed, subsequent flashes can use the web interface and sysupgrade files.
Signed-off-by: Alex Lewontin <alex.c.lewontin@gmail.com>
[rebase and adjust for 5.4]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-02-21 20:56:44 +00:00
|
|
|
SERCOMM_HWID := CFR
|
|
|
|
|
SERCOMM_HWVER := A001
|
|
|
|
|
SERCOMM_SWVER := 0x0040
|
2020-08-03 17:23:50 +00:00
|
|
|
SERCOMM_PAD := 576k
|
ramips: add support for Netgear R6080
This adds support for the Netgear R6080, aka Netgear AC1000.
The R6080 has almost the same hardware as the Netgear R6120,
aka Netgear AC1200, but it lacks the USB port, has only 8 MiB flash and
uses a different SERCOMM_HWID.
Specification:
SoC: MediaTek MT7628 (580 MHz)
Flash: 8 MiB
RAM: 64 MiB
Wireless: 2.4Ghz (builtin) and 5Ghz (MT7612E)
LAN speed: 10/100
LAN ports: 4
WAN speed: 10/100
WAN ports: 1
UART (57600 8N1) on PCB
Installation:
Flashing OpenWRT from stock firmware requires nmrpflash. Use an ethernet
cable to connect to LAN port 1 of the R6080, and power the R6080 off.
From the connected workstation, run
`nmrpflash -i eth0 -f openwrt-ramips-mt76x8-netgear_r6080-squashfs-factory.img`,
replacing eth0 with the appropriate interface (can be identified by
running `nmrpflash -L`). Then power on the R6080. After flashing has finished,
power cycle the R6080, and it will boot into OpenWRT. Once OpenWRT has been
installed, subsequent flashes can use the web interface and sysupgrade files.
Signed-off-by: Alex Lewontin <alex.c.lewontin@gmail.com>
[rebase and adjust for 5.4]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-02-21 20:56:44 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_r6080
|
|
|
|
|
|
2018-06-12 19:17:23 +00:00
|
|
|
define Device/netgear_r6120
|
2020-08-03 17:23:50 +00:00
|
|
|
$(Device/netgear_sercomm_nor)
|
2019-07-15 12:55:02 +00:00
|
|
|
IMAGE_SIZE := 15744k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := R6120
|
2018-11-30 10:10:29 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci
|
2020-07-10 10:00:08 +00:00
|
|
|
SERCOMM_HWNAME := R6120
|
2018-06-12 19:17:23 +00:00
|
|
|
SERCOMM_HWID := CGQ
|
|
|
|
|
SERCOMM_HWVER := A001
|
2018-11-08 11:46:37 +00:00
|
|
|
SERCOMM_SWVER := 0x0040
|
2020-08-03 17:23:50 +00:00
|
|
|
SERCOMM_PAD := 576k
|
2018-06-12 19:17:23 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += netgear_r6120
|
|
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/onion_omega2
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Onion
|
|
|
|
|
DEVICE_MODEL := Omega2
|
2017-08-26 01:49:45 +00:00
|
|
|
DEVICE_PACKAGES:= kmod-usb2 kmod-usb-ohci uboot-envtools
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += omega2
|
2017-08-26 01:49:45 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += onion_omega2
|
2017-08-26 01:49:45 +00:00
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/onion_omega2p
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Onion
|
|
|
|
|
DEVICE_MODEL := Omega2+
|
2017-08-26 01:49:45 +00:00
|
|
|
DEVICE_PACKAGES:= kmod-usb2 kmod-usb-ohci uboot-envtools kmod-sdhci-mt7620
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += omega2p
|
2017-08-26 01:49:45 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += onion_omega2p
|
2017-08-26 01:49:45 +00:00
|
|
|
|
2019-02-26 22:04:53 +00:00
|
|
|
define Device/rakwireless_rak633
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Rakwireless
|
|
|
|
|
DEVICE_MODEL := RAK633
|
2019-02-26 22:04:53 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += rakwireless_rak633
|
|
|
|
|
|
2020-06-29 10:24:01 +00:00
|
|
|
define Device/ravpower_rp-wd009
|
|
|
|
|
IMAGE_SIZE := 14272k
|
|
|
|
|
DEVICE_VENDOR := RAVPower
|
|
|
|
|
DEVICE_MODEL := RP-WD009
|
|
|
|
|
UBOOT_PATH := $(STAGING_DIR_IMAGE)/ravpower_rp-wd009-u-boot.bin
|
2020-06-29 10:24:04 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci \
|
|
|
|
|
kmod-sdhci-mt7620 kmod-i2c-mt7628 ravpower-mcu
|
2020-06-29 10:24:01 +00:00
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | ravpower-wd009-factory
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += ravpower_rp-wd009
|
|
|
|
|
|
2018-11-26 11:34:48 +00:00
|
|
|
define Device/skylab_skw92a
|
ramips: add support for Skylab SKW92A in EVB
Specifically, SKW92A_E16, described here:
http://www.skylabmodule.com/wp-content/uploads/SkyLab_SKW92A_V1.04_datasheet.pdf
Specification:
- MediaTek MT7628N/N (580 Mhz)
- 64 MB of RAM
- 16 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x u.FL
- Power by micro-USB connector at USB1 on EVB
- UART via micro-USB connector at USB3 on EVB (57600 8n1)
- 5x Ethernet LEDs
- 1x WLAN LEDs
- 1x WPS LED connected by jumper wire from I2S_CK on J20 to WPS_LED pin hole next
to daughter board on EVB
- WPS/Reset button (S2 on EVB)
- RESET button (S1 on EVB) is *not* connected to RST hole next to daughter board
Flash instruction:
>From Skylab firmware:
1. Associate with SKYLAP_AP
2. In a browser, load: http://10.10.10.254/
3. Username/password: admin/admin
4. In web admin interface: Administration / Upload Firmware, browse to
sysupgrade image, apply, flash will fail with a message:
Not a valid firmware. *** Warning: "/var/tmpFW" has corrupted data!
5. Telnet to 10.10.10.254, drops you into a root shell with no credentials
6. # cd /var
7. # mtd_write -r write tmpFW mtd4
Unlocking mtd4 ...
Writing from tmpFW to mtd4 ... [e]
8. When flash has completed, you will have booted into your firmware.
>From U-boot via TFTP and initramfs:
1. Place openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin on a TFTP server
2. Connect to serial console at USB3 on EVB
3. Connect ethernet between port 1 (not WAN) and your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "1"
7. At u-boot prompts:
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin
8. Move ethernet to port 0 (WAN) on EVB
9. At new OpenWrt console shell, fetch squashfs-sysupgrade image and flash
with sysupgrade.
>From U-boot via TFTP direct flash:
1. Place openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin on a TFTP server
2. Connect to serial console at USB3 on EVB (57600 8N1)
3. Connect ethernet between port 1 (not WAN) an your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "2"
7. At u-boot prompts:
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) Y
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin
8. When transfer is complete or as OpenWrt begins booting, move ethernet to
port 0 (WAN).
Signed-off-by: Russell Senior <russell@personaltelco.net>
2018-11-25 11:39:19 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Skylab
|
|
|
|
|
DEVICE_MODEL := SKW92A
|
ramips: add support for Skylab SKW92A in EVB
Specifically, SKW92A_E16, described here:
http://www.skylabmodule.com/wp-content/uploads/SkyLab_SKW92A_V1.04_datasheet.pdf
Specification:
- MediaTek MT7628N/N (580 Mhz)
- 64 MB of RAM
- 16 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x u.FL
- Power by micro-USB connector at USB1 on EVB
- UART via micro-USB connector at USB3 on EVB (57600 8n1)
- 5x Ethernet LEDs
- 1x WLAN LEDs
- 1x WPS LED connected by jumper wire from I2S_CK on J20 to WPS_LED pin hole next
to daughter board on EVB
- WPS/Reset button (S2 on EVB)
- RESET button (S1 on EVB) is *not* connected to RST hole next to daughter board
Flash instruction:
>From Skylab firmware:
1. Associate with SKYLAP_AP
2. In a browser, load: http://10.10.10.254/
3. Username/password: admin/admin
4. In web admin interface: Administration / Upload Firmware, browse to
sysupgrade image, apply, flash will fail with a message:
Not a valid firmware. *** Warning: "/var/tmpFW" has corrupted data!
5. Telnet to 10.10.10.254, drops you into a root shell with no credentials
6. # cd /var
7. # mtd_write -r write tmpFW mtd4
Unlocking mtd4 ...
Writing from tmpFW to mtd4 ... [e]
8. When flash has completed, you will have booted into your firmware.
>From U-boot via TFTP and initramfs:
1. Place openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin on a TFTP server
2. Connect to serial console at USB3 on EVB
3. Connect ethernet between port 1 (not WAN) and your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "1"
7. At u-boot prompts:
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin
8. Move ethernet to port 0 (WAN) on EVB
9. At new OpenWrt console shell, fetch squashfs-sysupgrade image and flash
with sysupgrade.
>From U-boot via TFTP direct flash:
1. Place openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin on a TFTP server
2. Connect to serial console at USB3 on EVB (57600 8N1)
3. Connect ethernet between port 1 (not WAN) an your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "2"
7. At u-boot prompts:
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) Y
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin
8. When transfer is complete or as OpenWrt begins booting, move ethernet to
port 0 (WAN).
Signed-off-by: Russell Senior <russell@personaltelco.net>
2018-11-25 11:39:19 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
2018-11-26 11:34:48 +00:00
|
|
|
TARGET_DEVICES += skylab_skw92a
|
ramips: add support for Skylab SKW92A in EVB
Specifically, SKW92A_E16, described here:
http://www.skylabmodule.com/wp-content/uploads/SkyLab_SKW92A_V1.04_datasheet.pdf
Specification:
- MediaTek MT7628N/N (580 Mhz)
- 64 MB of RAM
- 16 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x u.FL
- Power by micro-USB connector at USB1 on EVB
- UART via micro-USB connector at USB3 on EVB (57600 8n1)
- 5x Ethernet LEDs
- 1x WLAN LEDs
- 1x WPS LED connected by jumper wire from I2S_CK on J20 to WPS_LED pin hole next
to daughter board on EVB
- WPS/Reset button (S2 on EVB)
- RESET button (S1 on EVB) is *not* connected to RST hole next to daughter board
Flash instruction:
>From Skylab firmware:
1. Associate with SKYLAP_AP
2. In a browser, load: http://10.10.10.254/
3. Username/password: admin/admin
4. In web admin interface: Administration / Upload Firmware, browse to
sysupgrade image, apply, flash will fail with a message:
Not a valid firmware. *** Warning: "/var/tmpFW" has corrupted data!
5. Telnet to 10.10.10.254, drops you into a root shell with no credentials
6. # cd /var
7. # mtd_write -r write tmpFW mtd4
Unlocking mtd4 ...
Writing from tmpFW to mtd4 ... [e]
8. When flash has completed, you will have booted into your firmware.
>From U-boot via TFTP and initramfs:
1. Place openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin on a TFTP server
2. Connect to serial console at USB3 on EVB
3. Connect ethernet between port 1 (not WAN) and your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "1"
7. At u-boot prompts:
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin
8. Move ethernet to port 0 (WAN) on EVB
9. At new OpenWrt console shell, fetch squashfs-sysupgrade image and flash
with sysupgrade.
>From U-boot via TFTP direct flash:
1. Place openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin on a TFTP server
2. Connect to serial console at USB3 on EVB (57600 8N1)
3. Connect ethernet between port 1 (not WAN) an your TFTP server (e.g.
192.168.11.20)
4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC
5. Apply power to EVB
6. Interrupt u-boot with keypress of "2"
7. At u-boot prompts:
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) Y
Input device IP (10.10.10.123) ==:192.168.11.21
Input server IP (10.10.10.3) ==:192.168.11.20
Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin
8. When transfer is complete or as OpenWrt begins booting, move ethernet to
port 0 (WAN).
Signed-off-by: Russell Senior <russell@personaltelco.net>
2018-11-25 11:39:19 +00:00
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/tama_w06
|
|
|
|
|
IMAGE_SIZE := 15040k
|
|
|
|
|
DEVICE_VENDOR := Tama
|
|
|
|
|
DEVICE_MODEL := W06
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tama_w06
|
|
|
|
|
|
2020-03-12 19:19:32 +00:00
|
|
|
define Device/totolink_a3
|
|
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
UIMAGE_NAME := za3
|
|
|
|
|
DEVICE_VENDOR := TOTOLINK
|
|
|
|
|
DEVICE_MODEL := A3
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += totolink_a3
|
|
|
|
|
|
2019-05-16 07:09:07 +00:00
|
|
|
define Device/totolink_lr1200
|
|
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := TOTOLINK
|
|
|
|
|
DEVICE_MODEL := LR1200
|
2019-05-16 07:09:07 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 uqmi
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += totolink_lr1200
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/tplink_archer-c20-v4
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
DEVICE_MODEL := Archer C20
|
|
|
|
|
DEVICE_VARIANT := v4
|
|
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0xc200004
|
|
|
|
|
TPLINK_HWREVADD := 0x4
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += tplink,c20-v4
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_archer-c20-v4
|
|
|
|
|
|
ramips: add support for TP-Link Archer C20 v5
TP-Link Archer C20 v5 is a router with 5-port FE switch and
non-detachable antennas. It's based on MediaTek MT7628N+MT7610EN.
Specification:
- MediaTek MT7628N/N (580 Mhz)
- 64 MB of RAM
- 8 MB of FLASH
- 2T2R 2.4 GHz and 1T1R 5 GHz
- 5x 10/100 Mbps Ethernet
- 3x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- 7x LED (GPIO-controlled*), 2x button, power input switch
* WAN LED in this devices is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Create Factory image
--------------------
As all installation methods require a U-Boot to be integrated into the
Image (and we do not ship one with the image) we are not able to create
an image in the OpenWRT build-process.
Download a TP-Link image from their Website and a OpenWRT sysupgrade
image for the device and build yourself a factory image like following:
TP-Link image: tpl.bin
OpenWRT sysupgrade image: owrt.bin
> dd if=tpl.bin of=boot.bin bs=131584 count=1
> cat owrt.bin >> boot.bin
Installing via Web-UI
---------------------
Upload the boot.bin via TP-Links firmware upgrade tool in the
web-interface.
Installing via Recovery
-----------------------
Activate Web-Recovery by beginning the upgrade Process with a
Firmware-Image from TP-Link. After starting the Firmware Upgrade,
wait ~3 seconds (When update status is switching to 0%), then
disconnect the power supply from the device. Upgrade flag (which
activates Web-Recovery) is written before the OS-image is touched and
removed after write is succesfull, so this procedure should be safe.
Plug the power back in. It will come up in Recovery-Mode on 192.168.0.1.
When active, all LEDs but the WPS LED are off.
Remeber to assign yourself a static IP-address as DHCP is not active in
this mode.
The boot.bin can now be uploaded and flashed using the web-recovery.
Installing via TFTP
-------------------
Prepare an image like following (Filenames from factory image steps
apply here)
> dd if=/dev/zero of=tp_recovery.bin bs=196608 count=1
> dd if=tpl.bin of=tmp.bin bs=131584 count=1
> dd if=tmp.bin of=boot.bin bs=512 skip=1
> cat boot.bin >> tp_recovery.bin
> cat owrt.bin >> tp_recovery.bin
Place tp_recovery.bin in root directory of TFTP server and listen on
192.168.0.66/24.
Connect router LAN ports with your computer and power up the router
while pressing the reset button. The router will download the image via
tftp and after ~1 Minute reboot into OpenWRT.
U-Boot CLI
----------
U-Boot CLI can be activated by holding down '4' on bootup.
Dual U-Boot
-----------
This is TP-Link MediaTek device with a split-uboot feature design like
a TP-Link Archer C50 v4. The first (factory-uboot) provides recovery via
TFTP and HTTP, jumping straight into the second (firmware-uboot) if no
recovery needs to be performed. The firmware-uboot unpacks and executed
the kernel.
Web-Recovery
------------
TP-Link integrated a new Web-Recovery like the one on the Archer C7v4 /
TL-WR1043v5 / Archer C50v4. Stock-firmware sets a flag in the "romfile"
partition before beginning to write and removes it afterwards. If the
router boots with this flag set, bootloader will automatically start
Web-recovery and listens on 192.168.0.1. This way, the vendor-firmware
or an OpenWRT factory image can be written.
By doing the same while performing sysupgrade, we can take advantage of
the Web-recovery in OpenWRT.
It is important to note that Web-Recovery is only based on this flag. It
can't detect e.g. a crashing kernel or other means. Once activated it
won't boot the OS before a recovery action (either via TFTP or HTTP) is
performed. This recovery-mode is indicated by an illuminated WPS-LED on
boot.
Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com>
[adjust some node names for LEDs in DTS]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-18 06:52:44 +00:00
|
|
|
define Device/tplink_archer-c20-v5
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
ramips: add support for TP-Link Archer C20 v5
TP-Link Archer C20 v5 is a router with 5-port FE switch and
non-detachable antennas. It's based on MediaTek MT7628N+MT7610EN.
Specification:
- MediaTek MT7628N/N (580 Mhz)
- 64 MB of RAM
- 8 MB of FLASH
- 2T2R 2.4 GHz and 1T1R 5 GHz
- 5x 10/100 Mbps Ethernet
- 3x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- 7x LED (GPIO-controlled*), 2x button, power input switch
* WAN LED in this devices is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Create Factory image
--------------------
As all installation methods require a U-Boot to be integrated into the
Image (and we do not ship one with the image) we are not able to create
an image in the OpenWRT build-process.
Download a TP-Link image from their Website and a OpenWRT sysupgrade
image for the device and build yourself a factory image like following:
TP-Link image: tpl.bin
OpenWRT sysupgrade image: owrt.bin
> dd if=tpl.bin of=boot.bin bs=131584 count=1
> cat owrt.bin >> boot.bin
Installing via Web-UI
---------------------
Upload the boot.bin via TP-Links firmware upgrade tool in the
web-interface.
Installing via Recovery
-----------------------
Activate Web-Recovery by beginning the upgrade Process with a
Firmware-Image from TP-Link. After starting the Firmware Upgrade,
wait ~3 seconds (When update status is switching to 0%), then
disconnect the power supply from the device. Upgrade flag (which
activates Web-Recovery) is written before the OS-image is touched and
removed after write is succesfull, so this procedure should be safe.
Plug the power back in. It will come up in Recovery-Mode on 192.168.0.1.
When active, all LEDs but the WPS LED are off.
Remeber to assign yourself a static IP-address as DHCP is not active in
this mode.
The boot.bin can now be uploaded and flashed using the web-recovery.
Installing via TFTP
-------------------
Prepare an image like following (Filenames from factory image steps
apply here)
> dd if=/dev/zero of=tp_recovery.bin bs=196608 count=1
> dd if=tpl.bin of=tmp.bin bs=131584 count=1
> dd if=tmp.bin of=boot.bin bs=512 skip=1
> cat boot.bin >> tp_recovery.bin
> cat owrt.bin >> tp_recovery.bin
Place tp_recovery.bin in root directory of TFTP server and listen on
192.168.0.66/24.
Connect router LAN ports with your computer and power up the router
while pressing the reset button. The router will download the image via
tftp and after ~1 Minute reboot into OpenWRT.
U-Boot CLI
----------
U-Boot CLI can be activated by holding down '4' on bootup.
Dual U-Boot
-----------
This is TP-Link MediaTek device with a split-uboot feature design like
a TP-Link Archer C50 v4. The first (factory-uboot) provides recovery via
TFTP and HTTP, jumping straight into the second (firmware-uboot) if no
recovery needs to be performed. The firmware-uboot unpacks and executed
the kernel.
Web-Recovery
------------
TP-Link integrated a new Web-Recovery like the one on the Archer C7v4 /
TL-WR1043v5 / Archer C50v4. Stock-firmware sets a flag in the "romfile"
partition before beginning to write and removes it afterwards. If the
router boots with this flag set, bootloader will automatically start
Web-recovery and listens on 192.168.0.1. This way, the vendor-firmware
or an OpenWRT factory image can be written.
By doing the same while performing sysupgrade, we can take advantage of
the Web-recovery in OpenWRT.
It is important to note that Web-Recovery is only based on this flag. It
can't detect e.g. a crashing kernel or other means. Once activated it
won't boot the OS before a recovery action (either via TFTP or HTTP) is
performed. This recovery-mode is indicated by an illuminated WPS-LED on
boot.
Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com>
[adjust some node names for LEDs in DTS]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-18 06:52:44 +00:00
|
|
|
IMAGE_SIZE := 7616k
|
|
|
|
|
DEVICE_MODEL := Archer C20
|
|
|
|
|
DEVICE_VARIANT := v5
|
|
|
|
|
TPLINK_FLASHLAYOUT := 8MSUmtk
|
|
|
|
|
TPLINK_HWID := 0xc200005
|
|
|
|
|
TPLINK_HWREVADD := 0x5
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
|
|
|
|
IMAGES := sysupgrade.bin
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_archer-c20-v5
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/tplink_archer-c50-v3
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
DEVICE_MODEL := Archer C50
|
|
|
|
|
DEVICE_VARIANT := v3
|
|
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0x001D9BA4
|
|
|
|
|
TPLINK_HWREV := 0x79
|
|
|
|
|
TPLINK_HWREVADD := 0x1
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += tplink,c50-v3
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_archer-c50-v3
|
|
|
|
|
|
|
|
|
|
define Device/tplink_archer-c50-v4
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 7616k
|
|
|
|
|
DEVICE_MODEL := Archer C50
|
|
|
|
|
DEVICE_VARIANT := v4
|
|
|
|
|
TPLINK_FLASHLAYOUT := 8MSUmtk
|
|
|
|
|
TPLINK_HWID := 0x001D589B
|
|
|
|
|
TPLINK_HWREV := 0x93
|
|
|
|
|
TPLINK_HWREVADD := 0x2
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
IMAGES := sysupgrade.bin
|
|
|
|
|
SUPPORTED_DEVICES += tplink,c50-v4
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_archer-c50-v4
|
|
|
|
|
|
2020-01-28 15:17:41 +00:00
|
|
|
define Device/tplink_re200-v2
|
|
|
|
|
$(Device/tplink-safeloader)
|
|
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
DEVICE_MODEL := RE200
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
|
|
|
|
TPLINK_BOARD_ID := RE200-V2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_re200-v2
|
|
|
|
|
|
2020-08-02 14:22:50 +00:00
|
|
|
define Device/tplink_re200-v3
|
|
|
|
|
$(Device/tplink-safeloader)
|
|
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
DEVICE_MODEL := RE200
|
|
|
|
|
DEVICE_VARIANT := v3
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
|
|
|
|
TPLINK_BOARD_ID := RE200-V3
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_re200-v3
|
|
|
|
|
|
2020-06-30 13:35:56 +00:00
|
|
|
define Device/tplink_re220-v2
|
|
|
|
|
$(Device/tplink-safeloader)
|
|
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
DEVICE_MODEL := RE220
|
|
|
|
|
DEVICE_VARIANT := v2
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
|
|
|
|
TPLINK_BOARD_ID := RE220-V2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_re220-v2
|
|
|
|
|
|
2019-12-23 21:48:06 +00:00
|
|
|
define Device/tplink_re305-v1
|
|
|
|
|
$(Device/tplink-safeloader)
|
|
|
|
|
IMAGE_SIZE := 6016k
|
|
|
|
|
DEVICE_MODEL := RE305
|
|
|
|
|
DEVICE_VARIANT := v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
TPLINK_BOARD_ID := RE305-V1
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_re305-v1
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/tplink_tl-mr3020-v3
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
DEVICE_MODEL := TL-MR3020
|
|
|
|
|
DEVICE_VARIANT := v3
|
|
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0x30200003
|
|
|
|
|
TPLINK_HWREV := 0x3
|
|
|
|
|
TPLINK_HWREVADD := 0x3
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2019-07-07 14:27:51 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_tl-mr3020-v3
|
|
|
|
|
|
|
|
|
|
define Device/tplink_tl-mr3420-v5
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2019-07-07 14:27:51 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
DEVICE_MODEL := TL-MR3420
|
|
|
|
|
DEVICE_VARIANT := v5
|
|
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0x34200005
|
|
|
|
|
TPLINK_HWREV := 0x5
|
|
|
|
|
TPLINK_HWREVADD := 0x5
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2019-07-07 14:27:51 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_tl-mr3420-v5
|
|
|
|
|
|
2018-06-26 23:24:39 +00:00
|
|
|
define Device/tplink_tl-wa801nd-v5
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2018-06-26 23:24:39 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := TL-WA801ND
|
|
|
|
|
DEVICE_VARIANT := v5
|
2018-06-26 23:24:39 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0x08010005
|
|
|
|
|
TPLINK_HWREVADD := 0x5
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2018-06-26 23:24:39 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_tl-wa801nd-v5
|
|
|
|
|
|
2018-12-18 07:00:52 +00:00
|
|
|
define Device/tplink_tl-wr802n-v4
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2018-12-18 07:00:52 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := TL-WR802N
|
|
|
|
|
DEVICE_VARIANT := v4
|
2018-12-18 07:00:52 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0x08020004
|
|
|
|
|
TPLINK_HWREVADD := 0x4
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2018-12-18 07:00:52 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_tl-wr802n-v4
|
|
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/tplink_tl-wr840n-v4
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13
TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with
5-port FE switch and non-detachable antennas. Both are very similar
and are based on MediaTek MT7628NN (aka MT7628N) WiSoC.
The difference between these two models is in number of available
LEDs, buttons and power input switch.
This work is partially based on GitHub PR#974.
Specification:
- MT7628N/N (580 MHz)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- TL-WR840N v4: 5x LED (GPIO-controlled), 1x button
- TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input
switch
* WAN LED in TL-WR841N v13 is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device ("0x4"/"0x13" for these devices) but it seems
that anything other than "0" is correct.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash.
Tests showed that the GUI upgrade routine copies value of "Additional
Hardware Version" from existing firmware into offset "0x2023c" in
provided file, _before_ storing it in flash. In case of vendor firmware
upgrade files (which all include U-Boot image and two headers), this
offset points to the matching field in kernel+rootfs firmware part
header. Unfortunately, in case of LEDE factory image file which contains
only one header, it points to the offset "0x2023c" in kernel image. This
leads to a corrupted kernel and ends up with a "soft-bricked" device.
The good news is that U-Boot in these devices contains well known tftp
recovery mode, which can be triggered with "reset" button. What's more,
in comparison to some of older MediaTek based TP-Link devices, this
recovery mode doesn't write whole file at offset "0x0" in flash, without
verifying provided file in advance. In case of recovery mode in these
devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes
from rest of the file are stored in flash at offset "0x20000".
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot:
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin"
to "tp_recovery.bin" and place it in tftp server directory.
3. Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
4. Router will download file from server, write it to flash and reboot.
To access U-Boot CLI, keep pressed "4" key during boot.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-06-21 12:16:15 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := TL-WR840N
|
|
|
|
|
DEVICE_VARIANT := v4
|
2017-10-03 10:46:09 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0x08400004
|
|
|
|
|
TPLINK_HWREVADD := 0x4
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += tl-wr840n-v4
|
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13
TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with
5-port FE switch and non-detachable antennas. Both are very similar
and are based on MediaTek MT7628NN (aka MT7628N) WiSoC.
The difference between these two models is in number of available
LEDs, buttons and power input switch.
This work is partially based on GitHub PR#974.
Specification:
- MT7628N/N (580 MHz)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- TL-WR840N v4: 5x LED (GPIO-controlled), 1x button
- TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input
switch
* WAN LED in TL-WR841N v13 is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device ("0x4"/"0x13" for these devices) but it seems
that anything other than "0" is correct.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash.
Tests showed that the GUI upgrade routine copies value of "Additional
Hardware Version" from existing firmware into offset "0x2023c" in
provided file, _before_ storing it in flash. In case of vendor firmware
upgrade files (which all include U-Boot image and two headers), this
offset points to the matching field in kernel+rootfs firmware part
header. Unfortunately, in case of LEDE factory image file which contains
only one header, it points to the offset "0x2023c" in kernel image. This
leads to a corrupted kernel and ends up with a "soft-bricked" device.
The good news is that U-Boot in these devices contains well known tftp
recovery mode, which can be triggered with "reset" button. What's more,
in comparison to some of older MediaTek based TP-Link devices, this
recovery mode doesn't write whole file at offset "0x0" in flash, without
verifying provided file in advance. In case of recovery mode in these
devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes
from rest of the file are stored in flash at offset "0x20000".
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot:
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin"
to "tp_recovery.bin" and place it in tftp server directory.
3. Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
4. Router will download file from server, write it to flash and reboot.
To access U-Boot CLI, keep pressed "4" key during boot.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-06-21 12:16:15 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += tplink_tl-wr840n-v4
|
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13
TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with
5-port FE switch and non-detachable antennas. Both are very similar
and are based on MediaTek MT7628NN (aka MT7628N) WiSoC.
The difference between these two models is in number of available
LEDs, buttons and power input switch.
This work is partially based on GitHub PR#974.
Specification:
- MT7628N/N (580 MHz)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- TL-WR840N v4: 5x LED (GPIO-controlled), 1x button
- TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input
switch
* WAN LED in TL-WR841N v13 is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device ("0x4"/"0x13" for these devices) but it seems
that anything other than "0" is correct.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash.
Tests showed that the GUI upgrade routine copies value of "Additional
Hardware Version" from existing firmware into offset "0x2023c" in
provided file, _before_ storing it in flash. In case of vendor firmware
upgrade files (which all include U-Boot image and two headers), this
offset points to the matching field in kernel+rootfs firmware part
header. Unfortunately, in case of LEDE factory image file which contains
only one header, it points to the offset "0x2023c" in kernel image. This
leads to a corrupted kernel and ends up with a "soft-bricked" device.
The good news is that U-Boot in these devices contains well known tftp
recovery mode, which can be triggered with "reset" button. What's more,
in comparison to some of older MediaTek based TP-Link devices, this
recovery mode doesn't write whole file at offset "0x0" in flash, without
verifying provided file in advance. In case of recovery mode in these
devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes
from rest of the file are stored in flash at offset "0x20000".
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot:
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin"
to "tp_recovery.bin" and place it in tftp server directory.
3. Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
4. Router will download file from server, write it to flash and reboot.
To access U-Boot CLI, keep pressed "4" key during boot.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-06-21 12:16:15 +00:00
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/tplink_tl-wr840n-v5
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2017-12-24 16:00:13 +00:00
|
|
|
IMAGE_SIZE := 3904k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := TL-WR840N
|
|
|
|
|
DEVICE_VARIANT := v5
|
2017-11-08 13:00:06 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 4Mmtk
|
|
|
|
|
TPLINK_HWID := 0x08400005
|
|
|
|
|
TPLINK_HWREVADD := 0x5
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += tl-wr840n-v5
|
2020-04-09 10:40:01 +00:00
|
|
|
DEFAULT := n
|
2017-11-08 13:00:06 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += tplink_tl-wr840n-v5
|
2017-11-08 13:00:06 +00:00
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/tplink_tl-wr841n-v13
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2017-12-17 09:44:41 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := TL-WR841N
|
|
|
|
|
DEVICE_VARIANT := v13
|
2017-12-17 09:44:41 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
2017-10-03 10:46:09 +00:00
|
|
|
TPLINK_HWID := 0x08410013
|
|
|
|
|
TPLINK_HWREV := 0x268
|
|
|
|
|
TPLINK_HWREVADD := 0x13
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += tl-wr841n-v13
|
ramips: add support for TP-Link TL-WR840N v4 and TL-WR841N v13
TP-Link TL-WR840N v4 and TL-WR841N v13 are simple N300 routers with
5-port FE switch and non-detachable antennas. Both are very similar
and are based on MediaTek MT7628NN (aka MT7628N) WiSoC.
The difference between these two models is in number of available
LEDs, buttons and power input switch.
This work is partially based on GitHub PR#974.
Specification:
- MT7628N/N (580 MHz)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz
- 5x 10/100 Mbps Ethernet
- 2x external, non-detachable antennas
- UART (J1) header on PCB (115200 8n1)
- TL-WR840N v4: 5x LED (GPIO-controlled), 1x button
- TL-WR841N v13: 8x LED (GPIO-controlled*), 2x button, power input
switch
* WAN LED in TL-WR841N v13 is a dual-color, dual-leads type which isn't
(fully) supported by gpio-leds driver. This type of LED requires both
GPIOs state change at the same time to select color or turn it off.
For now, we support/use only the green part of the LED.
Factory image notes:
These devices use version 3 of TP-Link header, fortunately without RSA
signature (at least in case of devices sold in Europe). The difference
lays in the requirement for a non-zero value in "Additional Hardware
Version" field. Ideally, it should match the value stored in vendor
firmware header on device ("0x4"/"0x13" for these devices) but it seems
that anything other than "0" is correct.
We are able to prepare factory firwmare file which is accepted and
(almost) correctly flashed from the vendor GUI. As it turned out, it
accepts files without U-Boot image with second header at the beginning
but due to some kind of bug in upgrade routine, flashed image gets
corrupted before it's written to flash.
Tests showed that the GUI upgrade routine copies value of "Additional
Hardware Version" from existing firmware into offset "0x2023c" in
provided file, _before_ storing it in flash. In case of vendor firmware
upgrade files (which all include U-Boot image and two headers), this
offset points to the matching field in kernel+rootfs firmware part
header. Unfortunately, in case of LEDE factory image file which contains
only one header, it points to the offset "0x2023c" in kernel image. This
leads to a corrupted kernel and ends up with a "soft-bricked" device.
The good news is that U-Boot in these devices contains well known tftp
recovery mode, which can be triggered with "reset" button. What's more,
in comparison to some of older MediaTek based TP-Link devices, this
recovery mode doesn't write whole file at offset "0x0" in flash, without
verifying provided file in advance. In case of recovery mode in these
devices, first "0x20000" bytes are always skipped and "0x7a0000" bytes
from rest of the file are stored in flash at offset "0x20000".
Flash instruction:
Until (if at all) TP-Link fixes described problem, the only way to flash
LEDE image in these devices is to use tftp recovery mode in U-Boot:
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ramips-mt7628-tl-wr84...-squashfs-tftp-recovery.bin"
to "tp_recovery.bin" and place it in tftp server directory.
3. Connect PC with one of LAN ports, press the reset button, power up
the router and keep button pressed for around 6-7 seconds, until
device starts downloading the file.
4. Router will download file from server, write it to flash and reboot.
To access U-Boot CLI, keep pressed "4" key during boot.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-06-21 12:16:15 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += tplink_tl-wr841n-v13
|
2017-05-17 10:18:45 +00:00
|
|
|
|
2018-11-27 14:32:18 +00:00
|
|
|
define Device/tplink_tl-wr841n-v14
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2020-07-22 16:49:09 +00:00
|
|
|
IMAGE_SIZE := 3968k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := TL-WR841N
|
|
|
|
|
DEVICE_VARIANT := v14
|
2020-08-03 10:02:48 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 4MLmtk
|
2018-11-27 14:32:18 +00:00
|
|
|
TPLINK_HWID := 0x08410014
|
|
|
|
|
TPLINK_HWREVADD := 0x14
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
2018-11-27 14:32:18 +00:00
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 64k | $$(IMAGE/factory.bin)
|
2020-04-09 10:40:01 +00:00
|
|
|
DEFAULT := n
|
2018-11-27 14:32:18 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_tl-wr841n-v14
|
|
|
|
|
|
2018-05-30 15:41:53 +00:00
|
|
|
define Device/tplink_tl-wr842n-v5
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2018-05-30 15:41:53 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := TL-WR842N
|
|
|
|
|
DEVICE_VARIANT := v5
|
2018-05-30 15:41:53 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0x08420005
|
|
|
|
|
TPLINK_HWREV := 0x5
|
|
|
|
|
TPLINK_HWREVADD := 0x5
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2018-05-30 15:41:53 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_tl-wr842n-v5
|
|
|
|
|
|
2018-03-17 17:47:51 +00:00
|
|
|
define Device/tplink_tl-wr902ac-v3
|
2020-01-29 17:21:53 +00:00
|
|
|
$(Device/tplink-v2)
|
2018-03-17 17:47:51 +00:00
|
|
|
IMAGE_SIZE := 7808k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := TL-WR902AC
|
|
|
|
|
DEVICE_VARIANT := v3
|
2018-03-17 17:47:51 +00:00
|
|
|
TPLINK_FLASHLAYOUT := 8Mmtk
|
|
|
|
|
TPLINK_HWID := 0x000dc88f
|
|
|
|
|
TPLINK_HWREV := 0x89
|
|
|
|
|
TPLINK_HWREVADD := 0x1
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e kmod-usb2 kmod-usb-ohci \
|
|
|
|
|
kmod-usb-ledtrig-usbport
|
2020-01-29 17:21:53 +00:00
|
|
|
IMAGES := sysupgrade.bin tftp-recovery.bin
|
|
|
|
|
IMAGE/tftp-recovery.bin := pad-extra 128k | $$(IMAGE/factory.bin)
|
2018-03-17 17:47:51 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += tplink_tl-wr902ac-v3
|
|
|
|
|
|
2019-08-16 12:05:53 +00:00
|
|
|
define Device/unielec_u7628-01-16m
|
ramips: add support for UniElec U7628-01
UniElec U7628-01 is a router platform board based on MediaTek MT7628AN.
The device has the following specifications:
- MT7628AN (580MHz)
- 64/128/256 MB of RAM (DDR2)
- 8/16 MB of flash (SPI NOR)
- 5x 10/100 Mbps Ethernet (MT7628 built-in switch)
- 1x 2T2R 2.4 GHz Wi-Fi (MT7628)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses)
- 1x miniSIM slot
- 1x microSD slot
- 1x USB 2.0 port
- 7x single-color LEDs (GPIO-controlled)
- 1x bi-color LED (green GPIO-controlled, red -> LED_WLAN# in miniPCIe)
- 1x reset button
- 1x UART header (4-pins)
- 1x SDXC/GPIO header (10-pins, connected with microSD slot)
- 1x DC jack for main power (12 V)
The following has been tested and is working:
- Ethernet switch
- miniPCIe slot (tested with modem and Wi-Fi card)
- miniSIM slot
- sysupgrade
- reset button
- USB 2.0 port*
Due to a missing driver (MMC over GPIO) this is not supported:
- microSD card reader
* Warning:
USB buses in miniPCIe and regular A-type socket are connected together,
without any proper analog switch or USB HUB.
Installation:
This board might come with a different firmware versions (MediaTek SDK,
PandoraBox, Padavan, etc.). If your board comes with PandoraBox, you can
install LEDE using sysupgrade. Just SSH to the router and perform forced
sysupgrade (due to a board name mismatch). The default IP of this board
should be: 192.168.1.1 and username/password: root/admin. In case of a
different firmware, you can use web based recovery described below.
Use the following command to perform the sysupgrade (for the 128MB
RAM/16MB flash version):
sysupgrade -n -F lede-ramips-mt76x8-u7628-01-128M-16M-squashfs-sysupgrade.bin
Recovery:
This board contains a Chinese, closed-source bootloader called Breed
(Boot and Recovery Environment for Embedded Devices). Breed supports web
recovery and to enter it, you keep the reset button pressed for around
5 seconds during boot. Your machine will be assigned an IP through DHCP
and the router will use IP address 192.168.1.1. The recovery website is
in Chinese, but is easy to use. Click on the second item in the list to
access the recovery page, then the second item on the next page is where
you select the firmware. In order to start the recovery, you click the
button at the bottom.
SDXC/GPIO header (J3):
1. SDXC_D3 / I2C_SCLK
2. SDXC_D2 / I2C_SD
3. SDXC_D1 / I2S_DI
4. SDXC_D0 / I2S_WS
5. SDXC_CMD / I2S_CLK
6. SDXC_CLK / GPIO0
7. SDXC_CD / UART_RXD1
8. UART_TXD1
9. 3V3
10. GND
Other notes:
1. The board is available with different amounts of RAM and flash. We
have only added support for the 128/16 MB configuration, as that seems
to be the default. However, all the required infrastructure is in place
for making support for the other configurations easy.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-11-03 20:12:49 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := UniElec
|
|
|
|
|
DEVICE_MODEL := U7628-01
|
2019-08-16 12:05:53 +00:00
|
|
|
DEVICE_VARIANT := 16M
|
ramips: add support for UniElec U7628-01
UniElec U7628-01 is a router platform board based on MediaTek MT7628AN.
The device has the following specifications:
- MT7628AN (580MHz)
- 64/128/256 MB of RAM (DDR2)
- 8/16 MB of flash (SPI NOR)
- 5x 10/100 Mbps Ethernet (MT7628 built-in switch)
- 1x 2T2R 2.4 GHz Wi-Fi (MT7628)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses)
- 1x miniSIM slot
- 1x microSD slot
- 1x USB 2.0 port
- 7x single-color LEDs (GPIO-controlled)
- 1x bi-color LED (green GPIO-controlled, red -> LED_WLAN# in miniPCIe)
- 1x reset button
- 1x UART header (4-pins)
- 1x SDXC/GPIO header (10-pins, connected with microSD slot)
- 1x DC jack for main power (12 V)
The following has been tested and is working:
- Ethernet switch
- miniPCIe slot (tested with modem and Wi-Fi card)
- miniSIM slot
- sysupgrade
- reset button
- USB 2.0 port*
Due to a missing driver (MMC over GPIO) this is not supported:
- microSD card reader
* Warning:
USB buses in miniPCIe and regular A-type socket are connected together,
without any proper analog switch or USB HUB.
Installation:
This board might come with a different firmware versions (MediaTek SDK,
PandoraBox, Padavan, etc.). If your board comes with PandoraBox, you can
install LEDE using sysupgrade. Just SSH to the router and perform forced
sysupgrade (due to a board name mismatch). The default IP of this board
should be: 192.168.1.1 and username/password: root/admin. In case of a
different firmware, you can use web based recovery described below.
Use the following command to perform the sysupgrade (for the 128MB
RAM/16MB flash version):
sysupgrade -n -F lede-ramips-mt76x8-u7628-01-128M-16M-squashfs-sysupgrade.bin
Recovery:
This board contains a Chinese, closed-source bootloader called Breed
(Boot and Recovery Environment for Embedded Devices). Breed supports web
recovery and to enter it, you keep the reset button pressed for around
5 seconds during boot. Your machine will be assigned an IP through DHCP
and the router will use IP address 192.168.1.1. The recovery website is
in Chinese, but is easy to use. Click on the second item in the list to
access the recovery page, then the second item on the next page is where
you select the firmware. In order to start the recovery, you click the
button at the bottom.
SDXC/GPIO header (J3):
1. SDXC_D3 / I2C_SCLK
2. SDXC_D2 / I2C_SD
3. SDXC_D1 / I2S_DI
4. SDXC_D0 / I2S_WS
5. SDXC_CMD / I2S_CLK
6. SDXC_CLK / GPIO0
7. SDXC_CD / UART_RXD1
8. UART_TXD1
9. 3V3
10. GND
Other notes:
1. The board is available with different amounts of RAM and flash. We
have only added support for the 128/16 MB configuration, as that seems
to be the default. However, all the required infrastructure is in place
for making support for the other configurations easy.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-11-03 20:12:49 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2019-08-16 12:05:53 +00:00
|
|
|
SUPPORTED_DEVICES += u7628-01-128M-16M unielec,u7628-01-128m-16m
|
ramips: add support for UniElec U7628-01
UniElec U7628-01 is a router platform board based on MediaTek MT7628AN.
The device has the following specifications:
- MT7628AN (580MHz)
- 64/128/256 MB of RAM (DDR2)
- 8/16 MB of flash (SPI NOR)
- 5x 10/100 Mbps Ethernet (MT7628 built-in switch)
- 1x 2T2R 2.4 GHz Wi-Fi (MT7628)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses)
- 1x miniSIM slot
- 1x microSD slot
- 1x USB 2.0 port
- 7x single-color LEDs (GPIO-controlled)
- 1x bi-color LED (green GPIO-controlled, red -> LED_WLAN# in miniPCIe)
- 1x reset button
- 1x UART header (4-pins)
- 1x SDXC/GPIO header (10-pins, connected with microSD slot)
- 1x DC jack for main power (12 V)
The following has been tested and is working:
- Ethernet switch
- miniPCIe slot (tested with modem and Wi-Fi card)
- miniSIM slot
- sysupgrade
- reset button
- USB 2.0 port*
Due to a missing driver (MMC over GPIO) this is not supported:
- microSD card reader
* Warning:
USB buses in miniPCIe and regular A-type socket are connected together,
without any proper analog switch or USB HUB.
Installation:
This board might come with a different firmware versions (MediaTek SDK,
PandoraBox, Padavan, etc.). If your board comes with PandoraBox, you can
install LEDE using sysupgrade. Just SSH to the router and perform forced
sysupgrade (due to a board name mismatch). The default IP of this board
should be: 192.168.1.1 and username/password: root/admin. In case of a
different firmware, you can use web based recovery described below.
Use the following command to perform the sysupgrade (for the 128MB
RAM/16MB flash version):
sysupgrade -n -F lede-ramips-mt76x8-u7628-01-128M-16M-squashfs-sysupgrade.bin
Recovery:
This board contains a Chinese, closed-source bootloader called Breed
(Boot and Recovery Environment for Embedded Devices). Breed supports web
recovery and to enter it, you keep the reset button pressed for around
5 seconds during boot. Your machine will be assigned an IP through DHCP
and the router will use IP address 192.168.1.1. The recovery website is
in Chinese, but is easy to use. Click on the second item in the list to
access the recovery page, then the second item on the next page is where
you select the firmware. In order to start the recovery, you click the
button at the bottom.
SDXC/GPIO header (J3):
1. SDXC_D3 / I2C_SCLK
2. SDXC_D2 / I2C_SD
3. SDXC_D1 / I2S_DI
4. SDXC_D0 / I2S_WS
5. SDXC_CMD / I2S_CLK
6. SDXC_CLK / GPIO0
7. SDXC_CD / UART_RXD1
8. UART_TXD1
9. 3V3
10. GND
Other notes:
1. The board is available with different amounts of RAM and flash. We
have only added support for the 128/16 MB configuration, as that seems
to be the default. However, all the required infrastructure is in place
for making support for the other configurations easy.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-11-03 20:12:49 +00:00
|
|
|
endef
|
2019-10-21 15:51:29 +00:00
|
|
|
TARGET_DEVICES += unielec_u7628-01-16m
|
ramips: add support for UniElec U7628-01
UniElec U7628-01 is a router platform board based on MediaTek MT7628AN.
The device has the following specifications:
- MT7628AN (580MHz)
- 64/128/256 MB of RAM (DDR2)
- 8/16 MB of flash (SPI NOR)
- 5x 10/100 Mbps Ethernet (MT7628 built-in switch)
- 1x 2T2R 2.4 GHz Wi-Fi (MT7628)
- 1x miniPCIe slot (with PCIe and USB 2.0 buses)
- 1x miniSIM slot
- 1x microSD slot
- 1x USB 2.0 port
- 7x single-color LEDs (GPIO-controlled)
- 1x bi-color LED (green GPIO-controlled, red -> LED_WLAN# in miniPCIe)
- 1x reset button
- 1x UART header (4-pins)
- 1x SDXC/GPIO header (10-pins, connected with microSD slot)
- 1x DC jack for main power (12 V)
The following has been tested and is working:
- Ethernet switch
- miniPCIe slot (tested with modem and Wi-Fi card)
- miniSIM slot
- sysupgrade
- reset button
- USB 2.0 port*
Due to a missing driver (MMC over GPIO) this is not supported:
- microSD card reader
* Warning:
USB buses in miniPCIe and regular A-type socket are connected together,
without any proper analog switch or USB HUB.
Installation:
This board might come with a different firmware versions (MediaTek SDK,
PandoraBox, Padavan, etc.). If your board comes with PandoraBox, you can
install LEDE using sysupgrade. Just SSH to the router and perform forced
sysupgrade (due to a board name mismatch). The default IP of this board
should be: 192.168.1.1 and username/password: root/admin. In case of a
different firmware, you can use web based recovery described below.
Use the following command to perform the sysupgrade (for the 128MB
RAM/16MB flash version):
sysupgrade -n -F lede-ramips-mt76x8-u7628-01-128M-16M-squashfs-sysupgrade.bin
Recovery:
This board contains a Chinese, closed-source bootloader called Breed
(Boot and Recovery Environment for Embedded Devices). Breed supports web
recovery and to enter it, you keep the reset button pressed for around
5 seconds during boot. Your machine will be assigned an IP through DHCP
and the router will use IP address 192.168.1.1. The recovery website is
in Chinese, but is easy to use. Click on the second item in the list to
access the recovery page, then the second item on the next page is where
you select the firmware. In order to start the recovery, you click the
button at the bottom.
SDXC/GPIO header (J3):
1. SDXC_D3 / I2C_SCLK
2. SDXC_D2 / I2C_SD
3. SDXC_D1 / I2S_DI
4. SDXC_D0 / I2S_WS
5. SDXC_CMD / I2S_CLK
6. SDXC_CLK / GPIO0
7. SDXC_CD / UART_RXD1
8. UART_TXD1
9. 3V3
10. GND
Other notes:
1. The board is available with different amounts of RAM and flash. We
have only added support for the 128/16 MB configuration, as that seems
to be the default. However, all the required infrastructure is in place
for making support for the other configurations easy.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
2017-11-03 20:12:49 +00:00
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/vocore_vocore2
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := VoCore
|
|
|
|
|
DEVICE_MODEL := VoCore2
|
2017-01-08 06:30:10 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport \
|
2019-12-19 18:40:33 +00:00
|
|
|
kmod-sdhci-mt7620
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += vocore2
|
2017-01-08 06:30:10 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += vocore_vocore2
|
2017-01-08 06:30:10 +00:00
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/vocore_vocore2-lite
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := VoCore
|
|
|
|
|
DEVICE_MODEL := VoCore2-Lite
|
2017-08-26 01:49:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport \
|
2019-12-19 18:40:33 +00:00
|
|
|
kmod-sdhci-mt7620
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += vocore2lite
|
2016-09-08 22:57:31 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += vocore_vocore2-lite
|
2017-01-28 16:05:56 +00:00
|
|
|
|
2018-10-22 15:21:16 +00:00
|
|
|
define Device/wavlink_wl-wn570ha1
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Wavlink
|
|
|
|
|
DEVICE_MODEL := WL-WN570HA1
|
2018-10-22 15:21:16 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wavlink_wl-wn570ha1
|
|
|
|
|
|
2019-02-17 12:21:42 +00:00
|
|
|
define Device/wavlink_wl-wn575a3
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Wavlink
|
|
|
|
|
DEVICE_MODEL := WL-WN575A3
|
2019-02-17 12:21:42 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
SUPPORTED_DEVICES += wl-wn575a3
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wavlink_wl-wn575a3
|
|
|
|
|
|
2020-06-25 19:09:59 +00:00
|
|
|
define Device/wavlink_wl-wn577a2
|
|
|
|
|
IMAGE_SIZE := 7872k
|
|
|
|
|
DEVICE_VENDOR := Wavlink
|
|
|
|
|
DEVICE_MODEL := WL-WN577A2
|
|
|
|
|
DEVICE_ALT0_VENDOR := Maginon
|
|
|
|
|
DEVICE_ALT0_MODEL := WLR-755
|
|
|
|
|
DEVICE_PACKAGES := kmod-mt76x0e
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wavlink_wl-wn577a2
|
|
|
|
|
|
2018-01-17 07:14:41 +00:00
|
|
|
define Device/widora_neo-16m
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Widora
|
|
|
|
|
DEVICE_MODEL := Widora-NEO
|
|
|
|
|
DEVICE_VARIANT := 16M
|
2017-08-26 01:49:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2018-01-17 07:14:41 +00:00
|
|
|
SUPPORTED_DEVICES += widora-neo
|
2017-08-26 01:49:45 +00:00
|
|
|
endef
|
2018-01-17 07:14:41 +00:00
|
|
|
TARGET_DEVICES += widora_neo-16m
|
2017-08-26 01:49:45 +00:00
|
|
|
|
2018-01-08 05:27:28 +00:00
|
|
|
define Device/widora_neo-32m
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Widora
|
|
|
|
|
DEVICE_MODEL := Widora-NEO
|
|
|
|
|
DEVICE_VARIANT := 32M
|
2018-01-08 05:27:28 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += widora_neo-32m
|
|
|
|
|
|
2019-01-11 23:37:43 +00:00
|
|
|
define Device/wiznet_wizfi630s
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := WIZnet
|
|
|
|
|
DEVICE_MODEL := WizFi630S
|
2020-08-03 19:28:31 +00:00
|
|
|
SUPPORTED_DEVICES += wizfi630s
|
2019-01-11 23:37:43 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += wiznet_wizfi630s
|
|
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/wrtnode_wrtnode2p
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := WRTnode
|
|
|
|
|
DEVICE_MODEL := WRTnode 2P
|
2017-08-26 01:49:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci kmod-usb-ledtrig-usbport
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += wrtnode2p
|
2017-08-26 01:49:45 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += wrtnode_wrtnode2p
|
2017-08-26 01:49:45 +00:00
|
|
|
|
2019-07-03 21:22:13 +00:00
|
|
|
define Device/wrtnode_wrtnode2r
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 32448k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := WRTnode
|
|
|
|
|
DEVICE_MODEL := WRTnode 2R
|
2017-08-26 01:49:45 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb2 kmod-usb-ohci
|
2019-07-03 21:22:13 +00:00
|
|
|
SUPPORTED_DEVICES += wrtnode2r
|
2017-08-26 01:49:45 +00:00
|
|
|
endef
|
2019-07-03 21:22:13 +00:00
|
|
|
TARGET_DEVICES += wrtnode_wrtnode2r
|
2018-01-23 01:46:36 +00:00
|
|
|
|
2019-05-27 17:25:22 +00:00
|
|
|
define Device/xiaomi_mir4a-100m
|
|
|
|
|
IMAGE_SIZE := 14976k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := Xiaomi
|
|
|
|
|
DEVICE_MODEL := Mi Router 4A
|
|
|
|
|
DEVICE_VARIANT := 100M Edition
|
2019-05-27 17:25:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += xiaomi_mir4a-100m
|
|
|
|
|
|
2019-07-07 14:27:51 +00:00
|
|
|
define Device/xiaomi_miwifi-nano
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 16064k
|
2019-07-07 14:27:51 +00:00
|
|
|
DEVICE_VENDOR := Xiaomi
|
|
|
|
|
DEVICE_MODEL := MiWiFi Nano
|
2019-09-03 15:58:07 +00:00
|
|
|
DEVICE_PACKAGES := uboot-envtools
|
2019-07-07 14:27:51 +00:00
|
|
|
SUPPORTED_DEVICES += miwifi-nano
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += xiaomi_miwifi-nano
|
|
|
|
|
|
2018-01-24 00:27:51 +00:00
|
|
|
define Device/zbtlink_zbt-we1226
|
2019-07-22 16:09:57 +00:00
|
|
|
IMAGE_SIZE := 7872k
|
2019-09-26 12:44:22 +00:00
|
|
|
DEVICE_VENDOR := Zbtlink
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_MODEL := ZBT-WE1226
|
2018-01-23 01:46:36 +00:00
|
|
|
endef
|
2018-01-24 00:27:51 +00:00
|
|
|
TARGET_DEVICES += zbtlink_zbt-we1226
|
2018-04-08 14:04:11 +00:00
|
|
|
|
|
|
|
|
define Device/zyxel_keenetic-extra-ii
|
|
|
|
|
IMAGE_SIZE := 14912k
|
|
|
|
|
BLOCKSIZE := 64k
|
2019-07-06 12:51:09 +00:00
|
|
|
DEVICE_VENDOR := ZyXEL
|
|
|
|
|
DEVICE_MODEL := Keenetic Extra II
|
2019-12-19 18:40:33 +00:00
|
|
|
DEVICE_PACKAGES := kmod-mt76x2 kmod-usb2 kmod-usb-ohci \
|
|
|
|
|
kmod-usb-ledtrig-usbport
|
2018-04-08 14:04:11 +00:00
|
|
|
IMAGES += factory.bin
|
2018-11-29 09:48:03 +00:00
|
|
|
IMAGE/factory.bin := $$(sysupgrade_bin) | pad-to $$$$(BLOCKSIZE) | \
|
2020-03-10 13:58:27 +00:00
|
|
|
check-size | zyimage -d 6162 -v "ZyXEL Keenetic Extra II"
|
2018-04-08 14:04:11 +00:00
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += zyxel_keenetic-extra-ii
|
