Hi Tomasz, On Wed, 2024-01-10 at 16:39 +0100, Tomasz Maciej Nowak wrote: > From: Tomasz Maciej Nowak <tmn...@gmail.com> > > TP-Link RE365 is a wireless range extender, hardware-wise resembles > RE305 with slight changes regarding buttons and LEDs. > > Specification > SoC: MediaTek MT7628AN > RAM: 64 MiB DDR2 > Flash: 8 MiB SPI NOR > WiFi: 2.4 GHz 2T2R integrated > 5 GHz 2T2R MediaTek MT7612EN conncted to PCIe lanes > Ethernet: 1x 10/100 Mbps integrated > LEDs: 6x GPIO controlled > Buttons: 4x GPIO controlled > UART: row of 4 holes marked on PCB as J1, starting count from white > triangle > 1. VCC (3.3V), 2. GND, 3. RX, 4. TX > baud: 57600, parity: none, flow control: none > > Installation > 1. Open web management interface. > 2. Go to Settings > System Tools > Firmware upgrade. > 3. Select "Browse" and select the OpenWrt image with factory.bin suffix. > 4. After selecting "Upgrade" firmware writing process will start. > 5. Wait till device reboots, power LED should stay solid when it's fully > booted, then it's ready for configuration through LAN port. > > Additional information > With how device manufacturer patrtitioned the flash memory, it's possible > that with default packages set, initial factory.bin image won't be > created. In such case, try to reduce packages amount or use older release > for initial conversion to OpenWrt. Later You can use sysupgrade.bin > image with full set of packages because OpenWrt uses unpartitioned flash > memory space unused by vendor firmware. > > Reverting to vendor firmware involves converting firmware using > tplink-safeloader with -z option (can be found in ImageBuilder or SDK) > and forcibly applying converted firmware as sysupgrade. > > Known issues > WARNING: after removing casing of the device one is exposed to high > voltage and is in a risk of being electrocuted. > > Caution when interfacing whith bootloader, saving its environment either > by issuing "saveenv" or selecting option "1: Load system code to SDRAM > via TFTP." in boot menu, any of those will lead to overwriting part of > kernel. This will lead to need of firmware recovery. The cause of this > issue is bootloader having environment offset on flash at 0x40000, > while kernel starts from 0x20000. > > Signed-off-by: Tomasz Maciej Nowak <tmn...@gmail.com> > --- > v2 -> v3 > - list virtual flash devices as separate objects > - add kernel size restriction
Thanks for the update! [...] > + groups = "refclk", "wdt", "p0led_an", "p1led_an", "p2led_an", > "p3led_an", "p4led_an"; I'll wrap this line (it's one measly character over the 100 limit) and apply the patch to main. Best, Sander _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel