Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for TP-Link Archer A7
Hello Karl,
just as a heads-up for your v3:
On 23.11.18 22:00, Karl-Felix Glatzer wrote:
> --- a/target/linux/ath79/image/common-tp-link.mk
> +++ b/target/linux/ath79/image/common-tp-link.mk
> @@ -39,6 +39,15 @@ define Build/mktplinkfw-combined
> @mv $@.new $@
> endef
>
> +define Build/uImageArcher
> + ${STAGING_DIR_HOST}/bin/mkimage \
> + -A $(LINUX_KARCH) \
> + -O linux -T kernel \
> + -C $(1) -a $(KERNEL_LOADADDR) -e $(if
> $(KERNEL_ENTRY),$(KERNEL_ENTRY),$(KERNEL_LOADADDR)) \
> + -n '$(call toupper,$(LINUX_KARCH)) OpenWrt
> Linux-$(LINUX_VERSION)' -d $@ $@.new
> + @mv $@.new $@
> +endef
> +
This was added in
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=946ffe470d923fdde53db68592437194e0c276fc
> --- a/target/linux/ath79/image/generic-tp-link.mk
> +++ b/target/linux/ath79/image/generic-tp-link.mk
> @@ -1,5 +1,21 @@
> include ./common-tp-link.mk
>
> +define Device/tplink_archer-a7-v5
> + $(Device/tplink)
Added a definition for the safeloader-uimage with the same commit, replace
$(Device/tplink)
with
$(Device/tplink-safeloader-uimage)
> + ATH_SOC := qca9563
> + DEVICE_TITLE := TP-LINK Archer A7 v5
> + DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
> kmod-ath10k-ct ath10k-firmware-qca988x-ct
> + SUPPORTED_DEVICES := tplink,archer-a7-v5
> + BOARDNAME := ARCHER-A7-V5
> + TPLINK_BOARD_ID := ARCHER-A7-V5
> + IMAGE_SIZE := 15104k
> + KERNEL := kernel-bin | append-dtb | lzma | uImageArcher lzma
Can be dropped, defined in tplink-safeloader, inherited by
tplink-safeloader-uimage
> + IMAGE/sysupgrade.bin := append-rootfs | tplink-safeloader sysupgrade | \
> +append-metadata | check-size (IMAGE_SIZE)
Can be dropped also. tplink-safeloader is missing the size check, this
is already performed within tplink-safeloader.c
> + IMAGE/factory.bin := append-rootfs | tplink-safeloader factory
Can be dropped also.
Best wishes
David
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for TP-Link Archer A7
Hi, i think the ordering in the 02_network file is correct since the device is an "a7" not "c7". However there was an ordering error in the 01_leds file. I'll send the next revision when there is confirmation on which ordering is correct. On 2018-11-26 10:07:41, John Crispin wrote: > Hi, > > looks good, nitpicks inline > > On 23/11/2018 22:00, Karl-Felix Glatzer wrote: > > This patch adds support for TP-Link Archer A7 > > > > Specification: > > - SOC: QCA9563 > > - Flash: 16 MiB (SPI) > > - RAM: 128 MiB (DDR2) > > - Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN > > - Wireless: > >- 2.4GHz (bgn) SoC internal > >- 5GHz (ac) QCA988x > > - USB: 1x USB 2.0 port > > - Button: 1x power, 1x reset, 1x wps > > - LED: 10x LEDs > > - UART: holes in PCB > >- Vcc, GND, RX, TX from ethernet port side > >- 115200n8 > > > > Flash instructions: > > > > Upload openwrt-ath79-generic-tplink_archer-a7-v5-squashfs-factory.bin > > via the Webinterface. > > > > Flash instruction using tftp recovery: > > > > 1. Connect the computer to one of the LAN ports of the Archer A7 > > 2. Set the computer IP to 192.168.0.66 > > 3. Start a tftp server with the OpenWrt factory image in the tftp > > root directory renamed to ArcherC7v5_tp_recovery.bin > > 2. Connect power cable to Archer A7, press and hold the reset button > > and turn the router on > > 3. Keep the reset button pressed for ~5 seconds > > 4. Wait ~150 seconds to complete flashing > > > > Changes since first revision: > > > >- Flash instructions using stock image webinterface > >- Changed "Version 5" in model string to "v5" > >- Split DTS file in qca9563_tplink_archer-x7-v5.dtsi > > and qca9563_tplink_archer-a7-v5.dts > >- Firmware image is now build with dynamic partitioning > >- Default to ath10k-ct > > > > Signed-off-by: Karl-Felix Glatzer > > --- > > .../ath79/base-files/etc/board.d/01_leds | 7 + > > .../ath79/base-files/etc/board.d/02_network | 4 + > > .../etc/hotplug.d/firmware/11-ath10k-caldata | 1 + > > .../ath79/dts/qca9563_tplink_archer-a7-v5.dts | 49 + > > .../dts/qca9563_tplink_archer-x7-v5.dtsi | 202 ++ > > target/linux/ath79/image/common-tp-link.mk| 9 + > > target/linux/ath79/image/generic-tp-link.mk | 16 ++ > > tools/firmware-utils/src/tplink-safeloader.c | 42 +++- > > 8 files changed, 329 insertions(+), 1 deletion(-) > > create mode 100644 target/linux/ath79/dts/qca9563_tplink_archer-a7-v5.dts > > create mode 100644 target/linux/ath79/dts/qca9563_tplink_archer-x7-v5.dtsi > > > > diff --git a/target/linux/ath79/base-files/etc/board.d/01_leds > > b/target/linux/ath79/base-files/etc/board.d/01_leds > > index f04eb7f5c6..4ddf04ef84 100755 > > --- a/target/linux/ath79/base-files/etc/board.d/01_leds > > +++ b/target/linux/ath79/base-files/etc/board.d/01_leds > > @@ -57,6 +57,13 @@ tplink,tl-mr3020-v1|\ > > tplink,tl-mr3040-v2) > > ucidef_set_led_netdev "lan" "LAN" "tp-link:green:lan" "eth0" > > ;; > > +tplink,archer-a7-v5) > > + ucidef_set_led_switch "wan" "WAN" "tp-link:green:wan" "switch0" "0x02" > > + ucidef_set_led_switch "lan1" "LAN1" "tp-link:green:lan1" "switch0" > > "0x04" > > + ucidef_set_led_switch "lan2" "LAN2" "tp-link:green:lan2" "switch0" > > "0x08" > > + ucidef_set_led_switch "lan3" "LAN3" "tp-link:green:lan3" "switch0" > > "0x10" > > + ucidef_set_led_switch "lan4" "LAN4" "tp-link:green:lan4" "switch0" > > "0x20" > > + ;; > > tplink,tl-wr1043nd-v4) > > ucidef_set_led_switch "wan" "WAN" "tp-link:green:wan" "switch0" "0x20" > > ucidef_set_led_switch "lan1" "LAN1" "tp-link:green:lan1" "switch0" > > "0x10" > > diff --git a/target/linux/ath79/base-files/etc/board.d/02_network > > b/target/linux/ath79/base-files/etc/board.d/02_network > > index 5f02c5769a..7c7c9e14e1 100755 > > --- a/target/linux/ath79/base-files/etc/board.d/02_network > > +++ b/target/linux/ath79/base-files/etc/board.d/02_network > > @@ -107,6 +107,10 @@ ath79_setup_interfaces() > > ucidef_add_switch "switch0" \ > > "0@eth0" "3:lan:1" "5:lan:2" "4:wan" > > ;; > > + tplink,archer-a7-v5) > > + ucidef_add_switch "switch0" \ > > + "0@eth0" "2:lan:1" "3:lan:2" "4:lan:3" "5:lan:4" "1:wan" > > + ;; > > i am pretty sure that v5 is ordered after and not before v1 and v2 :-). > please fix this. there is at least 1 more instance of such an ordering error > in the patch. > > John > > > > > tplink,archer-c7-v1|\ > > tplink,archer-c7-v2|\ > > tplink,tl-wdr4900-v2) > > diff --git > > a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata > > b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata > > index dfe2d3ef31..6001df07bb 100644 > > --- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata > > +++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata >
Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for TP-Link Archer A7
On Sun, 25 Nov 2018 at 16:43, Karl-Felix Glatzer wrote: > On 2018-11-24 10:30:59, Rafał Miłecki wrote: > > On Fri, 23 Nov 2018 at 22:03, Karl-Felix Glatzer > > wrote: > > > This patch adds support for TP-Link Archer A7 > > > > > > Specification: > > > - SOC: QCA9563 > > > - Flash: 16 MiB (SPI) > > > - RAM: 128 MiB (DDR2) > > > - Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN > > > - Wireless: > > > - 2.4GHz (bgn) SoC internal > > > - 5GHz (ac) QCA988x > > > - USB: 1x USB 2.0 port > > > - Button: 1x power, 1x reset, 1x wps > > > - LED: 10x LEDs > > > - UART: holes in PCB > > > - Vcc, GND, RX, TX from ethernet port side > > > - 115200n8 > > > > > > Flash instructions: > > > > > > Upload openwrt-ath79-generic-tplink_archer-a7-v5-squashfs-factory.bin > > > via the Webinterface. > > > > > > Flash instruction using tftp recovery: > > > > > > 1. Connect the computer to one of the LAN ports of the Archer A7 > > > 2. Set the computer IP to 192.168.0.66 > > > 3. Start a tftp server with the OpenWrt factory image in the tftp > > >root directory renamed to ArcherC7v5_tp_recovery.bin > > > 2. Connect power cable to Archer A7, press and hold the reset button > > >and turn the router on > > > 3. Keep the reset button pressed for ~5 seconds > > > 4. Wait ~150 seconds to complete flashing > > > > > > Changes since first revision: > > > > > > - Flash instructions using stock image webinterface > > > - Changed "Version 5" in model string to "v5" > > > - Split DTS file in qca9563_tplink_archer-x7-v5.dtsi > > > and qca9563_tplink_archer-a7-v5.dts > > > - Firmware image is now build with dynamic partitioning > > > - Default to ath10k-ct > > > > Looks pretty nice. > > > > Could you provide me a boot log with mtd partitioning messages? I'd > > like to see how mtd creates partitions on this device. > > > > Sure. I've attached the output of dmesg as dmesg.log. > > These seem to be all the messages related to the spi flash and mtd > partitioning: > > [0.391041] m25p80 spi0.0: w25q128 (16384 Kbytes) > [0.395992] 7 fixed-partitions partitions found on MTD device spi0.0 > [0.402546] Creating 7 MTD partitions on "spi0.0": > [0.407521] 0x-0x0002 : "factory-uboot" > [0.414019] 0x0002-0x0004 : "u-boot" > [0.419760] 0x0004-0x00f0 : "firmware" > [0.451110] 2 uimage-fw partitions found on MTD device firmware > [0.457262] 0x0004-0x001c6955 : "kernel" > [0.462973] 0x001c6955-0x00f0 : "rootfs" > [0.468741] mtd: device 4 (rootfs) set to be root filesystem > [0.474676] 1 squashfs-split partitions found on MTD device rootfs > [0.481063] 0x004c-0x00f0 : "rootfs_data" > [0.487266] 0x00f4-0x00f6 : "info" > [0.492805] 0x00f6-0x00fb : "config" > [0.498596] 0x00fc-0x00fd : "partition-table" > [0.505209] 0x00ff-0x0100 : "art" Thanks! Please kindly add compatible = "denx,uimage"; to the "firmware" partition node, for details you can see: [OpenWrt-Devel] Specifying "firmware" partition format on all DTS targets http://lists.infradead.org/pipermail/openwrt-devel/2018-November/014706.html -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for TP-Link Archer A7
Hi, looks good, nitpicks inline On 23/11/2018 22:00, Karl-Felix Glatzer wrote: This patch adds support for TP-Link Archer A7 Specification: - SOC: QCA9563 - Flash: 16 MiB (SPI) - RAM: 128 MiB (DDR2) - Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN - Wireless: - 2.4GHz (bgn) SoC internal - 5GHz (ac) QCA988x - USB: 1x USB 2.0 port - Button: 1x power, 1x reset, 1x wps - LED: 10x LEDs - UART: holes in PCB - Vcc, GND, RX, TX from ethernet port side - 115200n8 Flash instructions: Upload openwrt-ath79-generic-tplink_archer-a7-v5-squashfs-factory.bin via the Webinterface. Flash instruction using tftp recovery: 1. Connect the computer to one of the LAN ports of the Archer A7 2. Set the computer IP to 192.168.0.66 3. Start a tftp server with the OpenWrt factory image in the tftp root directory renamed to ArcherC7v5_tp_recovery.bin 2. Connect power cable to Archer A7, press and hold the reset button and turn the router on 3. Keep the reset button pressed for ~5 seconds 4. Wait ~150 seconds to complete flashing Changes since first revision: - Flash instructions using stock image webinterface - Changed "Version 5" in model string to "v5" - Split DTS file in qca9563_tplink_archer-x7-v5.dtsi and qca9563_tplink_archer-a7-v5.dts - Firmware image is now build with dynamic partitioning - Default to ath10k-ct Signed-off-by: Karl-Felix Glatzer --- .../ath79/base-files/etc/board.d/01_leds | 7 + .../ath79/base-files/etc/board.d/02_network | 4 + .../etc/hotplug.d/firmware/11-ath10k-caldata | 1 + .../ath79/dts/qca9563_tplink_archer-a7-v5.dts | 49 + .../dts/qca9563_tplink_archer-x7-v5.dtsi | 202 ++ target/linux/ath79/image/common-tp-link.mk| 9 + target/linux/ath79/image/generic-tp-link.mk | 16 ++ tools/firmware-utils/src/tplink-safeloader.c | 42 +++- 8 files changed, 329 insertions(+), 1 deletion(-) create mode 100644 target/linux/ath79/dts/qca9563_tplink_archer-a7-v5.dts create mode 100644 target/linux/ath79/dts/qca9563_tplink_archer-x7-v5.dtsi diff --git a/target/linux/ath79/base-files/etc/board.d/01_leds b/target/linux/ath79/base-files/etc/board.d/01_leds index f04eb7f5c6..4ddf04ef84 100755 --- a/target/linux/ath79/base-files/etc/board.d/01_leds +++ b/target/linux/ath79/base-files/etc/board.d/01_leds @@ -57,6 +57,13 @@ tplink,tl-mr3020-v1|\ tplink,tl-mr3040-v2) ucidef_set_led_netdev "lan" "LAN" "tp-link:green:lan" "eth0" ;; +tplink,archer-a7-v5) + ucidef_set_led_switch "wan" "WAN" "tp-link:green:wan" "switch0" "0x02" + ucidef_set_led_switch "lan1" "LAN1" "tp-link:green:lan1" "switch0" "0x04" + ucidef_set_led_switch "lan2" "LAN2" "tp-link:green:lan2" "switch0" "0x08" + ucidef_set_led_switch "lan3" "LAN3" "tp-link:green:lan3" "switch0" "0x10" + ucidef_set_led_switch "lan4" "LAN4" "tp-link:green:lan4" "switch0" "0x20" + ;; tplink,tl-wr1043nd-v4) ucidef_set_led_switch "wan" "WAN" "tp-link:green:wan" "switch0" "0x20" ucidef_set_led_switch "lan1" "LAN1" "tp-link:green:lan1" "switch0" "0x10" diff --git a/target/linux/ath79/base-files/etc/board.d/02_network b/target/linux/ath79/base-files/etc/board.d/02_network index 5f02c5769a..7c7c9e14e1 100755 --- a/target/linux/ath79/base-files/etc/board.d/02_network +++ b/target/linux/ath79/base-files/etc/board.d/02_network @@ -107,6 +107,10 @@ ath79_setup_interfaces() ucidef_add_switch "switch0" \ "0@eth0" "3:lan:1" "5:lan:2" "4:wan" ;; + tplink,archer-a7-v5) + ucidef_add_switch "switch0" \ + "0@eth0" "2:lan:1" "3:lan:2" "4:lan:3" "5:lan:4" "1:wan" + ;; i am pretty sure that v5 is ordered after and not before v1 and v2 :-). please fix this. there is at least 1 more instance of such an ordering error in the patch. John tplink,archer-c7-v1|\ tplink,archer-c7-v2|\ tplink,tl-wdr4900-v2) diff --git a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata index dfe2d3ef31..6001df07bb 100644 --- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata +++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath10k-caldata @@ -100,6 +100,7 @@ case "$FIRMWARE" in ath10kcal_extract "ART" 20480 2116 ath10kcal_patch_mac $(macaddr_add $(cat /sys/class/net/eth0/address) +16) ;; + tplink,archer-a7-v5|\ tplink,archer-c7-v2) ath10kcal_extract "art" 20480 2116 ath10kcal_patch_mac $(macaddr_add $(cat /sys/class/net/eth1/address) -1) diff --git a/target/linux/ath79/dts/qca9563_tplink_archer-a7-v5.dts b/target/linux/ath79/dts/qca9563_tplink_archer-a7-v5.dts new file mode 100644 index 00..4cc4aaf409 --- /dev/null +++ b/target/linux/ath79/dts/qca9563_tplink_arch
Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for TP-Link Archer A7
On 2018-11-24 10:30:59, Rafał Miłecki wrote:
> On Fri, 23 Nov 2018 at 22:03, Karl-Felix Glatzer wrote:
> > This patch adds support for TP-Link Archer A7
> >
> > Specification:
> > - SOC: QCA9563
> > - Flash: 16 MiB (SPI)
> > - RAM: 128 MiB (DDR2)
> > - Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN
> > - Wireless:
> > - 2.4GHz (bgn) SoC internal
> > - 5GHz (ac) QCA988x
> > - USB: 1x USB 2.0 port
> > - Button: 1x power, 1x reset, 1x wps
> > - LED: 10x LEDs
> > - UART: holes in PCB
> > - Vcc, GND, RX, TX from ethernet port side
> > - 115200n8
> >
> > Flash instructions:
> >
> > Upload openwrt-ath79-generic-tplink_archer-a7-v5-squashfs-factory.bin
> > via the Webinterface.
> >
> > Flash instruction using tftp recovery:
> >
> > 1. Connect the computer to one of the LAN ports of the Archer A7
> > 2. Set the computer IP to 192.168.0.66
> > 3. Start a tftp server with the OpenWrt factory image in the tftp
> >root directory renamed to ArcherC7v5_tp_recovery.bin
> > 2. Connect power cable to Archer A7, press and hold the reset button
> >and turn the router on
> > 3. Keep the reset button pressed for ~5 seconds
> > 4. Wait ~150 seconds to complete flashing
> >
> > Changes since first revision:
> >
> > - Flash instructions using stock image webinterface
> > - Changed "Version 5" in model string to "v5"
> > - Split DTS file in qca9563_tplink_archer-x7-v5.dtsi
> > and qca9563_tplink_archer-a7-v5.dts
> > - Firmware image is now build with dynamic partitioning
> > - Default to ath10k-ct
>
> Looks pretty nice.
>
> Could you provide me a boot log with mtd partitioning messages? I'd
> like to see how mtd creates partitions on this device.
>
Sure. I've attached the output of dmesg as dmesg.log.
These seem to be all the messages related to the spi flash and mtd partitioning:
[0.391041] m25p80 spi0.0: w25q128 (16384 Kbytes)
[0.395992] 7 fixed-partitions partitions found on MTD device spi0.0
[0.402546] Creating 7 MTD partitions on "spi0.0":
[0.407521] 0x-0x0002 : "factory-uboot"
[0.414019] 0x0002-0x0004 : "u-boot"
[0.419760] 0x0004-0x00f0 : "firmware"
[0.451110] 2 uimage-fw partitions found on MTD device firmware
[0.457262] 0x0004-0x001c6955 : "kernel"
[0.462973] 0x001c6955-0x00f0 : "rootfs"
[0.468741] mtd: device 4 (rootfs) set to be root filesystem
[0.474676] 1 squashfs-split partitions found on MTD device rootfs
[0.481063] 0x004c-0x00f0 : "rootfs_data"
[0.487266] 0x00f4-0x00f6 : "info"
[0.492805] 0x00f6-0x00fb : "config"
[0.498596] 0x00fc-0x00fd : "partition-table"
[0.505209] 0x00ff-0x0100 : "art"
>
> > +&mtdparts {
> > + factory-uboot@0 {
> > + label = "factory-uboot";
> > + reg = <0x00 0x02>;
> > + read-only;
> > + };
> > +
> > + uboot: u-boot@0 {
> > + label = "u-boot";
> > + reg = <0x02 0x02>;
> > + read-only;
> > + };
>
> u-boot@2 but its' a minor thing, can be fixed later / by commiter.
[0.00] Linux version 4.14.81 (kfg@kfg-g74s) (gcc version 7.3.0 (OpenWrt
GCC 7.3.0 r8473+1-8184bdddc4)) #0 Wed Nov 21 13:57:08 2018
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 00019750 (MIPS 74Kc)
[0.00] MIPS: machine is TP-Link Archer A7 v5
[0.00] SoC: Qualcomm Atheros QCA956X ver 1 rev 0
[0.00] Determined physical RAM map:
[0.00] memory: 0800 @ (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[0.00] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32
bytes
[0.00] Zone ranges:
[0.00] Normal [mem 0x-0x07ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00] node 0: [mem 0x-0x07ff]
[0.00] Initmem setup node 0 [mem 0x-0x07ff]
[0.00] On node 0 totalpages: 32768
[0.00] free_area_init_node: node 0, pgdat 805094a0, node_mem_map
81008ee0
[0.00] Normal zone: 256 pages used for memmap
[0.00] Normal zone: 0 pages reserved
[0.00] Normal zone: 32768 pages, LIFO batch:7
[0.00] random: get_random_bytes called from start_kernel+0x8c/0x474
with crng_init=0
[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists, mobility grouping on. Total pages: 32512
[0.00] Kernel command line: console=ttyS0,115200n8
rootfstype=squashfs,jffs2
[0.00] PID hash table entries: 512 (order: -1, 2048 bytes)
[0.00] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[
Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for TP-Link Archer A7
On Fri, 23 Nov 2018 at 22:03, Karl-Felix Glatzer wrote:
> This patch adds support for TP-Link Archer A7
>
> Specification:
> - SOC: QCA9563
> - Flash: 16 MiB (SPI)
> - RAM: 128 MiB (DDR2)
> - Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN
> - Wireless:
> - 2.4GHz (bgn) SoC internal
> - 5GHz (ac) QCA988x
> - USB: 1x USB 2.0 port
> - Button: 1x power, 1x reset, 1x wps
> - LED: 10x LEDs
> - UART: holes in PCB
> - Vcc, GND, RX, TX from ethernet port side
> - 115200n8
>
> Flash instructions:
>
> Upload openwrt-ath79-generic-tplink_archer-a7-v5-squashfs-factory.bin
> via the Webinterface.
>
> Flash instruction using tftp recovery:
>
> 1. Connect the computer to one of the LAN ports of the Archer A7
> 2. Set the computer IP to 192.168.0.66
> 3. Start a tftp server with the OpenWrt factory image in the tftp
>root directory renamed to ArcherC7v5_tp_recovery.bin
> 2. Connect power cable to Archer A7, press and hold the reset button
>and turn the router on
> 3. Keep the reset button pressed for ~5 seconds
> 4. Wait ~150 seconds to complete flashing
>
> Changes since first revision:
>
> - Flash instructions using stock image webinterface
> - Changed "Version 5" in model string to "v5"
> - Split DTS file in qca9563_tplink_archer-x7-v5.dtsi
> and qca9563_tplink_archer-a7-v5.dts
> - Firmware image is now build with dynamic partitioning
> - Default to ath10k-ct
Looks pretty nice.
Could you provide me a boot log with mtd partitioning messages? I'd
like to see how mtd creates partitions on this device.
> +&mtdparts {
> + factory-uboot@0 {
> + label = "factory-uboot";
> + reg = <0x00 0x02>;
> + read-only;
> + };
> +
> + uboot: u-boot@0 {
> + label = "u-boot";
> + reg = <0x02 0x02>;
> + read-only;
> + };
u-boot@2 but its' a minor thing, can be fixed later / by commiter.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
