<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/ynezz/tools, branch master</title>
<subtitle>Staging tree of Petr Stetiar</subtitle>
<id>https://git.openwrt.org/openwrt/staging/ynezz/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/ynezz/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/'/>
<updated>2021-05-26T21:10:25Z</updated>
<entry>
<title>ramips: add support for TP-Link Archer C6U v1 (EU)</title>
<updated>2021-05-26T21:10:25Z</updated>
<author>
<name>Georgi Vlaev</name>
</author>
<published>2020-07-31T11:02:21Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=a46ad596a3e076599f38a4132b5d6dfee8a3102a'/>
<id>urn:sha1:a46ad596a3e076599f38a4132b5d6dfee8a3102a</id>
<content type='text'>
This patch adds support for TP-Link Archer C6U v1 (EU).
The device is also known in some market as Archer C6 v3.
This patch supports only Archer C6U v1 (EU).

Specifications:
--------------

* SoC: Mediatek MT7621AT 2C2T, 880MHz
* RAM: 128MB DDR3
* Flash: 16MB SPI NOR flash (Winbond 25Q128)
* WiFi 5GHz: Mediatek MT7613BEN (2x2:2)
* WiFi 2.4GHz: Mediatek MT7603EN (2x2:2)
* Ethernet: MT7630, 5x 1000Base-T.
* LED: Power, WAN, LAN, WiFi 2GHz and 5GHz, USB
* Buttons: Reset, WPS.
* UART: Serial console (115200 8n1), J1(GND:3)
* USB: One USB2 port.

Installation:
------------

Install the OpenWrt factory image for C6U is from the
TP-Link web interface.

1) Go to "Advanced/System Tools/Firmware Update".
2) Click "Browse" and upload the OpenWrt factory image:
openwrt-ramips-mt7621-tplink_archer-c6u-v1-squashfs-factory.bin.
3) Click the "Upgrade" button, and select "Yes" when prompted.

Recovery to stock firmware:
--------------------------

The C6U bootloader has a failsafe mode that provides a web
interface (running at 192.168.0.1) for reverting back to the
stock TP-Link firmware. The failsafe interface is triggered
from the serial console or on failed kernel boot. Unfortunately,
there's no key combination that enables the failsafe mode. This
gives us two options for recovery:

1) Recover using the serial console (J1 header).
The recovery interface can be selected by hitting 'x' when
prompted on boot.

2) Trigger the bootloader failsafe mode.
A more dangerous option is force the bootloader into
recovery mode by erasing the OpenWrt partition from the
OpenWrt's shell - e.g "mtd erase firmware". Please be
careful, since erasing the wrong partition can brick
your device.

MAC addresses:
-------------

OEM firmware configuration:
D8:07:B6:xx:xx:83 : 5G
D8:07:B6:xx:xx:84 : LAN (label)
D8:07:B6:xx:xx:84 : 2.4G
D8:07:B6:xx:xx:85 : WAN

Signed-off-by: Georgi Vlaev &lt;georgi.vlaev@konsulko.com&gt;
</content>
</entry>
<entry>
<title>ramips: add support for TP-Link Archer A6 v3</title>
<updated>2021-05-26T21:10:14Z</updated>
<author>
<name>Vinay Patil</name>
</author>
<published>2021-04-19T01:22:51Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=f8f8935adb2be1ebce46a8d7058c76a8d3a9bd89'/>
<id>urn:sha1:f8f8935adb2be1ebce46a8d7058c76a8d3a9bd89</id>
<content type='text'>
The patch adds support for the TP-Link Archer A6 v3
The router is sold in US and India with FCC ID TE7A6V3

Specification
-------------
MediaTek MT7621 SOC
RAM:         128MB DDR3
SPI Flash:   W25Q128 (16MB)
Ethernet:    MT7530 5x 1000Base-T
WiFi 5GHz:   Mediatek MT7613BE
WiFi 2.4GHz: Mediatek MT7603E
UART/Serial: 115200 8n1

Device Configuration &amp; Serial Port Pins
---------------------------------------
ETH Ports:    LAN4 LAN3 LAN2 LAN1 WAN
             _______________________
             |                     |
Serial Pins: |   VCC GND TXD RXD   |
             |_____________________|

LEDs:         Power Wifi2G Wifi5G LAN WAN

Build Output
------------
The build will generate following set of files
[1] openwrt-ramips-mt7621-tplink_archer-a6-v3-initramfs-kernel.bin
[2] openwrt-ramips-mt7621-tplink_archer-a6-v3-squashfs-factory.bin
[3] openwrt-ramips-mt7621-tplink_archer-a6-v3-squashfs-sysupgrade.bin

How to Use - Flashing from TP-Link Web Interface
------------------------------------------------
* Go to "Advanced/System Tools/Firmware Update".
* Click "Browse" and upload the OpenWrt factory image: factory.bin[2]
* Click the "Upgrade" button, and select "Yes" when prompted.

TFTP Booting
------------
Setup a TFTP boot server with address 192.168.0.5.
While starting U-boot press '4' key to stop autoboot.
Copy the initramfs-kernel.bin[1] to TFTP server folder, rename as test.bin
From u-boot command prompt run tftpboot followed by bootm.

Recovery
--------
Archer A6 V3 has recovery page activated if SPI booting from flash fails.
Recovery page can be activated from serial console only.
Press 'x' while u-boot is starting
Note: TFTP boot can be activated only from u-boot serial console.
Device recovery address: 192.168.0.1

Thanks to: Frankis for Randmon MAC address fix.

Signed-off-by: Vinay Patil &lt;post2vinay@gmail.com&gt;
[remove superfluous factory image definition, whitespacing]
Signed-off-by: David Bauer &lt;mail@david-bauer.net&gt;
</content>
</entry>
<entry>
<title>ccache: Build with ENABLE_DOCUMENTATION=OFF</title>
<updated>2021-05-23T13:11:38Z</updated>
<author>
<name>David Adair</name>
</author>
<published>2021-05-14T23:04:27Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=2d1546832357a3a8bd18680bd31dd92050e739b2'/>
<id>urn:sha1:2d1546832357a3a8bd18680bd31dd92050e739b2</id>
<content type='text'>
This adjusts the Makefile to use the new option to turn off the
doc builds. It will not cause any problems except a warning
about unused options if combined with a ccache source missing
the upstream patch.

Since a config setting is required to re-enable the doc build this
is equivalent to unconditionally disabling the docs if the config
setting is not created.

Signed-off-by: David Adair &lt;djabhead@aol.com&gt;
</content>
</entry>
<entry>
<title>fakeroot: Alpine linux libc.musl build error fix</title>
<updated>2021-05-23T13:11:19Z</updated>
<author>
<name>Ruslan Isaev</name>
</author>
<published>2021-05-10T14:56:59Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=7a70f78fb7da4dc3e8c58e7662f4dc623274a78b'/>
<id>urn:sha1:7a70f78fb7da4dc3e8c58e7662f4dc623274a78b</id>
<content type='text'>
Prevent build error on Alpine Linux host:
libfakeroot.c error: conflicting types for 'id_t'
Error relocating openwrt/staging_dir/host/lib/libfakeroot.so: SEND_GET_XATTR: symbol not found

Signed-off-by: Ruslan Isaev &lt;legale.legale@gmail.com&gt;
</content>
</entry>
<entry>
<title>firmware-utils: fix coverity zytrx.c resource leak</title>
<updated>2021-05-20T10:56:38Z</updated>
<author>
<name>Kevin Darbyshire-Bryant</name>
</author>
<published>2021-05-16T10:46:32Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=baf2a50ef3cf34574e12d2ab1b23578310f0d527'/>
<id>urn:sha1:baf2a50ef3cf34574e12d2ab1b23578310f0d527</id>
<content type='text'>
fix coverity resource leak warning:

    	*len = stat.st_size;
    	mapped = mmap(NULL, stat.st_size, PROT_READ, MAP_SHARED, fd, 0);
    	if (close(fd) &lt; 0)
CID 1484880:  Resource leaks  (RESOURCE_LEAK)
Variable "mapped" going out of scope leaks the storage it points to.
    		return NULL;
    	return mapped;
    }

Signed-off-by: Kevin Darbyshire-Bryant &lt;ldir@darbyshire-bryant.me.uk&gt;
</content>
</entry>
<entry>
<title>firmware-utils: zytrx: Add util for ZyXEL specific header</title>
<updated>2021-05-09T07:15:44Z</updated>
<author>
<name>Bjørn Mork</name>
</author>
<published>2021-04-19T11:00:55Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=48cad07a55246317d66fee4ced25cb62a2bae3d3'/>
<id>urn:sha1:48cad07a55246317d66fee4ced25cb62a2bae3d3</id>
<content type='text'>
The ZyXEL NR7101 prepend an additional header to U-Boot images. This
header use the TRX magic 0x30524448 (HDR0), but is incompatible with
TRX images.

This code is reverse-engineered based on matching 32 bit numbers
found in the header with lengths and different checksum
calculations of the vendor images found on the device.  The result
was matched against the validation output produced by the
bootloader to name the associated header fields.

Example bootloader validation output:

 Zyxel TRX Image 1 --&gt; Found!  Header Checksum OK
 ============ZyXEL header information==================
         chipId             : MT7621A
         boardId            : NR7101
         modelId            : 07 01 00 01
         kernel_len         : (14177560)
         kernelChksum       : (0x8DD31F69)
         swVersionInt       : 1.00(ABUV.0)D1
         swVersionExt       : 1.00(ABUV.0)D1

 Zyxel TRX Image 2 --&gt; Found!  Header Checksum OK
 ============ZyXEL header information==================
         chipId             : MT7621A
         boardId            : NR7101
         modelId            : 07 01 00 01
         kernel_len         : (14176660)
         kernelChksum       : (0x951A7637)
         swVersionInt       : 1.00(ABUV.0)D0
         swVersionExt       : 1.00(ABUV.0)D0

 =================================================
 Check image validation:
 Image1 Header Magic Number --&gt; OK
 Image2 Header Magic Number --&gt; OK
 Image1 Header Checksum --&gt; OK
 Image2 Header Checksum --&gt; OK
 Image1 Data Checksum --&gt; OK
 Image2 Data Checksum --&gt; OK
 Image1 Stable Flag --&gt; Stable
 Image1 Try Counter --&gt; 0
 Image1: OK
 Image2: OK

The coverage and algorithm for the kernelChksum field is unknown.
This field is not validated by the bootloader or the OEM firmware
upgrade tool. It is therefore set to a static value for now.

The swVersion fields contain free form string values.  The OEM firmware
use ZyXEL structured version numbers as shown above.  The strings are
not interpreted or validated on boot, so they can be repurposed for
anything we want the bootloader to display to the user.  But the OEM
web GUI fails to flash images with freeform strings.

The purpose of the other strings in the header is not known.  The
values appear to be static.  We assume they are fixed for now, until
we have other examples.  One of these strings is the platform name,
which is taken as an input parameter for support other members of
the device family.

Signed-off-by: Bjørn Mork &lt;bjorn@mork.no&gt;
</content>
</entry>
<entry>
<title>tplink-safeloader: fix product_name of TP-Link AD7200</title>
<updated>2021-05-06T07:51:58Z</updated>
<author>
<name>Alex Henrie</name>
</author>
<published>2021-05-04T03:07:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=dfef88b6cacceec151ca4ce4bb3dc50c1c5cf1d2'/>
<id>urn:sha1:dfef88b6cacceec151ca4ce4bb3dc50c1c5cf1d2</id>
<content type='text'>
The stock firmware does not accept firmware with "Talon" in the name.

Tested on firmware version 1.0.10 Build 20160902 rel. 57400 which came
preinstalled, as well as latest firmware version 2.0.1 Build 20170103
rel.71053 flashed from
AD7200v1-up-ver2-0-1-P1[20170103-rel71053]_2017-01-04_10.08.28.bin.

Fixes: 1a775a4fd033 ("ipq806x: add support for TP-Link Talon AD7200")
Signed-off-by: Alex Henrie &lt;alexhenrie24@gmail.com&gt;
[added details about vendor firmware]
Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>ccache: update to 4.2.1</title>
<updated>2021-04-23T18:57:33Z</updated>
<author>
<name>DENG Qingfang</name>
</author>
<published>2021-04-22T04:28:39Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=3ebfd0078d6aa4848ee8f72640266bd0390f790a'/>
<id>urn:sha1:3ebfd0078d6aa4848ee8f72640266bd0390f790a</id>
<content type='text'>
Update ccache to 4.2.1

Signed-off-by: DENG Qingfang &lt;dqfext@gmail.com&gt;
Signed-off-by: Hans Dedecker &lt;dedeckeh@gmail.com&gt; [refresh patch]
</content>
</entry>
<entry>
<title>firmware-utils: tplink-safeloader: support displaying fw info</title>
<updated>2021-04-14T12:04:04Z</updated>
<author>
<name>Rafał Miłecki</name>
</author>
<published>2021-04-08T21:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=5eb3508ad21e111ecea8c44cb9c6c896ce7c71b3'/>
<id>urn:sha1:5eb3508ad21e111ecea8c44cb9c6c896ce7c71b3</id>
<content type='text'>
Add "-i" option for reading &amp; displaying firmware info. First it lists
in-firmware partitions ("fwup-ptn"). Then it checks for human
understandable partitions and prints data found in each of them.

This new feature is meant for development &amp; debug purposes.

Signed-off-by: Rafał Miłecki &lt;rafal@milecki.pl&gt;
</content>
</entry>
<entry>
<title>firmware-utils: mkmylofw: fix blocks padding</title>
<updated>2021-04-13T12:00:49Z</updated>
<author>
<name>Rafał Miłecki</name>
</author>
<published>2021-04-13T11:53:57Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/ynezz/commit/?id=d4f2c2914a6547ef6067dd0968c4970e913f17f0'/>
<id>urn:sha1:d4f2c2914a6547ef6067dd0968c4970e913f17f0</id>
<content type='text'>
The old code didn't make sense as it was using "len" variable which was
guaranteed to be always 0. Loop right above broken code is:
while (len &gt; 0) { }

With this recent ALIGN macro fix this resulted in subtracting block size
from 0 and calling write_out_padding() with a negative length.

To calculate amount of bytes needed for padding &amp; alignment it should be
enough to use % 4.

Fixes: a2f66229450d ("firmware-utils: fix few random warnings")
Signed-off-by: Rafał Miłecki &lt;rafal@milecki.pl&gt;
</content>
</entry>
</feed>
