4ff02b46b9
Add an OpenWrt-based U-Boot build for this device, allowing for more flexibility and customization. Expected behaviour ------------------ When plugging the device, keeping the reset button pressed will enter TFTP recovery mode: the board will send requests for the initramfs file (openwrt-mediatek-filogic-glinet_gl-mt2500-initramfs-kernel.bin) from IP 192.168.1.1 to 192.168.1.10 TFTP server. The bootloader will populate the environment with the unit serial number as reported by the "sn" value in eMMC, the "sn_bak" value, the country code and ddns. WAN and LAN MAC addresses are reported in the environment as well. Limitations ----------- No web interface is available, and only the LAN port can be used for system recovery. Notes ----- This port has been tested with the Maxlinear version only, and with a board that does not exhibit eMMC communication problems. Even though eMMC frequency has been lowered, some testing is probably needed and always very welcome. A -factory image has been introduced, and is only needed when using the "Load Firmware via TFTP then write to eMMC." boot menu function. The device has not been converted to use uImage.FIT including the rootfs to keep compatibility with stock bootloader and firmware. Installation ------------ From a Linux root shell: 0. Transfer the needed files to the board, placing them in /tmp. 1. Make sure your U-Boot environment is erased: all of my units came with unpopulated environment, but I am not sure this is always the case. Issue the command cat /dev/zero >/dev/mmcblk0p2 (you will get a "no space left" error, which is reasonable and expected). 2. Unlock the eMMC boot area where BL2 is located: echo 0 >/sys/block/mmcblk0boot0/force_ro 3. Write the new BL2 code: cat openwrt-mediatek-filogic-glinet_gl-mt2500-emmc-preloader.bin >/dev/mmcblk0boot0 4. Write new BL31+U-Boot image: cat openwrt-mediatek-filogic-glinet_gl-mt2500-emmc-bl31-uboot.fip >/dev/mmcblk0p4 5. Reboot. Signed-off-by: Enrico Mioso <mrkiko.rs@gmail.com> |
||
|---|---|---|
| .devcontainer/ci-env | ||
| .github | ||
| .vscode | ||
| config | ||
| include | ||
| LICENSES | ||
| package | ||
| scripts | ||
| target | ||
| toolchain | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| BSDmakefile | ||
| Config.in | ||
| COPYING | ||
| feeds.conf.default | ||
| Makefile | ||
| README.md | ||
| rules.mk | ||
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.7+ 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