OpenWRT
/
openwrt
mirror of https://github.com/openwrt/openwrt.git
1
0
Fork 0
Code Issues Releases Wiki Activity
OpenWRT Github source
70,811 Commits
11 Branches
76 Tags
869 MiB
C 61.2%
Makefile 19.3%
Shell 6.8%
Roff 6.7%
Perl 2.5%
Other 3.3%
 
 
 
 
 
 
Go to file
Carlo Szelinsky 3a117c0c53
ramips: mt7621: add support for Cudy LT700 Outdoor v1 
Cudy LT700 Outdoor v1 is an outdoor 4G LTE Wi-Fi 5 router (Cudy board
ID R43).

Hardware:
 - SoC: MediaTek MT7621AT
 - Flash: 16 MiB SPI NOR (XM25QH128C)
 - RAM: 128 MiB DDR3
 - WLAN: 2.4 GHz (MediaTek MT7603E, 11n), 5 GHz (MediaTek MT7663, 11ac)
 - Ethernet: 1x 10/100/1000 Mbps LAN
 - Power: 48-57 V passive PoE
 - Buttons: 1x Reset button
 - LEDs: 8x Green
 - LTE: internal USB modem Quectel EG060W (Cat 6)
 - Serial console: 3.3V, 115200 8N1, unpopulated 4-pin header left of the
   SoC; pinout from top: VCC, GND, TX, RX

MAC addresses:
+---------+-------------------+-----------+
|         | MAC               | Algorithm |
+---------+-------------------+-----------+
| LAN     | d4:0d:ab:xx:xx:xx | label     |
| WLAN 2g | d4:0d:ab:xx:xx:xx | label     |
| WLAN 5g | d4:0d:ab:xx:xx:xx | label +1  |
+---------+-------------------+-----------+

The internal LTE modem is a Quectel EG060W and needs the option driver
IDs added in a separate commit. gpio-export applies the initial output
value raw, ignoring the active-low flag, so output = <0> is what pulls
the modem power enable low and powers it at boot.

Migration to OpenWrt:
- Obtain the RSA signed intermediate firmware from Cudy:
  openwrt-ramips-mt7621-cudy_lt700-outdoor-v1-squashfs-flash.bin
- Connect a computer to the LAN port and flash the intermediate firmware
  via the OEM web interface
- OpenWrt is now accessible via 192.168.1.1
- Install the regular OpenWrt sysupgrade image from LuCI or over SSH

Revert back to OEM firmware:
- Configure a computer with IP 192.168.1.88 and run a TFTP server that
  serves the OEM recovery image as recovery.bin
- Hold the reset button while powering on the device; the bootloader
  fetches recovery.bin and restores the OEM firmware

Signed-off-by: Carlo Szelinsky <github@szelinsky.de>
Tested-by: achim <achim@cloudystars.net>
Link: https://github.com/openwrt/openwrt/pull/24689
Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>
 		2026-09-17 18:19:17 +02:00
.devcontainer/ci-env
…
.github
…
.vscode
…
LICENSES
…
config
…
include build: add ATOMIC64_DEPENDS 2026-09-13 20:46:35 +01:00
package comgt: ncm: allow model specific ncm.json profiles 2026-09-17 18:19:17 +02:00
scripts
…
target ramips: mt7621: add support for Cudy LT700 Outdoor v1 2026-09-17 18:19:17 +02:00
toolchain toolchain: gcc: fix SHF_MERGE check with binutils 2.46 2026-09-14 12:09:01 +01:00
tools tools/expat: update to 2.8.4 2026-09-12 16:49:17 +02:00
.gitattributes
…
.gitignore
…
BSDmakefile
…
COPYING
…
Config.in
…
Makefile
…
README.md
…
feeds.conf.default
…
rules.mk
…

README.md

OpenWrt logo

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

  1. Run ./scripts/feeds update -a to obtain all the latest package definitions defined in feeds.conf / feeds.conf.default

  2. Run ./scripts/feeds install -a to install symlinks for all obtained packages into package/feeds/

  3. Run make menuconfig to select your preferred configuration for the toolchain, target system & firmware packages.

  4. Run make to 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 #openwrt on oftc.net.

Developer Community

License

OpenWrt is licensed under GPL-2.0