Kaloyan Naumov
46309f1396
Add support for the Horaco ZX-SWTGW2C48NS, also sold as the HRUI HR-SWTGW2C48NS and the SODOLA SL-SWTGW2C48NS. Hardware -------- * SoC: Realtek RTL9313 * RAM: 512 MiB (2 x 256 MiB window, as in the DTS) * Flash: 32 MiB SPI NOR; U-Boot, two environment blocks, two stock configuration partitions (jffs, jffs2), the 28 MiB firmware partition (RUNTIME1) and a 1 MiB OEMINFO partition * Ethernet: 4 x 10GBASE-T (RTL8264B PHY), 8 x SFP+ (10GBASE-R) * Fan and temperature controller: ADT7476 on I2C * Console: internal UART header, 38400n8 in the kernel (U-Boot itself uses 115200). The exact location and pinout were not recorded. * Power: internal AC power supply * Buttons: reset * LEDs: per-port LEDs through the SoC LED controller; system LED The ports are wired for three LEDs each, of which two are fitted, so the LED set carries an unused first entry. The port LEDs also need the controller in single-colour scan mode, set through realtek,led-mode; the rtl931x driver reads that property since "realtek: rtl931x: set the LED interface mode from realtek,led-mode". The system LED is taken off hardware control and driven as a GPIO LED. The SFP+ transmit pairs are polarity-inverted. The SFP LOS signals are not wired to a known GPIO. The four copper PHYs need the rtl826x firmware; without it their ports do not come up. The fan is left to the ADT7476 closed loop. hwmon_fancontrol now has one function for the ADT747x, shared with the PlasmaCloud ESX28/PSX28 (their values are unchanged), which finds the chip on whichever I2C bus it sits. On this board it uses all three temperature channels, duty 40 (the stock idle speed; the fan is not stable lower) from 45 C up to full duty at 71.67 C (the chip's range step nearest 70 C), keeps the fan at duty 40 below 45 C, and sets the critical limit to 85 C. MAC address layout ------------------ A single address is stored in the U-Boot environment (ethaddr) and is read through nvmem for ethernet0, which is also the label MAC. It is applied to all ports, as the stock firmware does. Installation ------------ The bootloader and the stock updater require the Realtek SDK uImage magic 0x83800000, which factory.bin carries. Upload the factory image through the stock web UI's manual firmware upgrade page (its TFTP-client upgrade accepts the same image), then reboot from Diagnostics > Reboot: the stock firmware does not reboot by itself. Only the RUNTIME1 partition is written; U-Boot, its environment and OEMINFO are kept. Later upgrades use the sysupgrade image. To return to stock, run "sysupgrade -F -n" with a vendor image. -F is needed because a vendor image carries no OpenWrt metadata; it also skips every image check, so first confirm the image starts with the uImage magic 0x83800000 (for example with "hexdump -C -n 4"). Assisted-by: Claude:claude-opus-5 Assisted-by: Claude:claude-fable-5 Assisted-by: Claude:claude-sonnet-5-5 Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Kaloyan Naumov <knaumov@gmail.com> Link: https://github.com/openwrt/openwrt/pull/25575 Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.8+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0