Backups/immortalwrt-mt798x
1
0
Fork 0
mirror of https://github.com/hanwckf/immortalwrt-mt798x.git synced 2025-01-09 02:43:53 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
49,481 Commits 1 Branch 0 Tags 456 MiB
Go to file
Clone
Open with VS Code Open with VSCodium Open with Intellij IDEA
Download ZIP Download TAR.GZ Download BUNDLE
Sander Vanheule 4f86edf477 ath79: support for TP-Link EAP225-Outdoor v1 
TP-Link EAP225-Outdoor v1 is an AC1200 (802.11ac Wave-2) pole or wall
mount access point. Debricking requires access to the serial port, which
is non-trivial.

Device specifications:
* SoC: QCA9563 @ 775MHz
* Memory: 128MiB DDR2
* Flash: 16MiB SPI-NOR
* Wireless 2.4GHz (SoC): b/g/n 2x2
* Wireless 5GHz (QCA9886): a/n/ac 2x2 MU-MIMO
* Ethernet (AR8033): 1× 1GbE, PoE

Flashing instructions:
* ssh into target device with recent (>= v1.6.0) firmware
* run `cliclientd stopcs` on target device
* upload factory image via web interface

Debricking:
To recover the device, you need access to the serial port. This requires
fine soldering to test points, or the use of probe pins.
* Open the case and solder wires to the test points: RXD, TXD and TPGND4
  * Use a 3.3V UART, 115200 baud, 8n1
* Interrupt bootloader by holding ctrl+B during boot
* upload initramfs via built-in tftp client and perform sysupgrade
    setenv ipaddr 192.168.1.1 # default, change as required
    setenv serverip 192.168.1.10 # default, change as required
    tftp 0x80800000 initramfs.bin
    bootelf $fileaddr

MAC addresses:
MAC address (as on device label) is stored in device info partition at
an offset of 8 bytes. ath9k device has same address as ethernet, ath10k
uses address incremented by 1.
From stock ifconfig:

    ath0      Link encap:Ethernet  HWaddr D8:...:2E
    ath10     Link encap:Ethernet  HWaddr D8:...:2F
    br0       Link encap:Ethernet  HWaddr D8:...:2E
    eth0      Link encap:Ethernet  HWaddr D8:...:2E

Tested by forum user PolynomialDivision on firmware v1.7.0.
UART access tested by forum user arinc9.

Signed-off-by: Sander Vanheule <sander@svanheule.net>
2020-11-23 22:53:15 +01:00
.github
build: Update README & github help
2018-07-08 09:41:53 +01:00
config
Revert "refpolicy: add variant that builds modular policy"
2020-11-22 15:20:35 +00:00
include
build: create $(PKG_SYMVERS_DIR) if non-existent
2020-11-19 18:52:15 +01:00
package
mvebu: add initial support for Globalscale ESPRESSObin-Ultra
2020-11-23 22:53:15 +01:00
scripts
scripts: download.pl: retry download using filename
2020-11-20 02:35:43 +01:00
target
ath79: support for TP-Link EAP225-Outdoor v1
2020-11-23 22:53:15 +01:00
toolchain
musl: handle wcsnrtombs destination buffer overflow (CVE-2020-28928)
2020-11-20 13:24:48 +01:00
tools
ath79: support for TP-Link EAP225-Outdoor v1
2020-11-23 22:53:15 +01:00
.gitattributes
add .gitattributes to prevent the git autocrlf option from messing with CRLF/LF in files
2012-05-08 13:30:49 +00:00
.gitignore
build: improve ccache support
2020-07-11 15:19:53 +02:00
BSDmakefile
add missing copyright header
2007-02-26 01:05:09 +00:00
Config.in
merge: base: update base-files and basic config
2017-12-08 19:41:18 +01:00
feeds.conf.default
feeds: add freifunk feed
2020-06-24 14:58:17 +02:00
LICENSE
LICENSE: use updated GNU copy
2020-08-02 15:54:43 +02:00
logo.svg
README: port to 21st century
2020-08-02 15:44:40 +02:00
Makefile
build: improve ccache support
2020-07-11 15:19:53 +02:00
README.md
README: port to 21st century
2020-08-02 15:44:40 +02:00
rules.mk
rules.mk: simplify FAKEROOT command line
2020-10-30 00:39:09 +00:00

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!

Development

To build your own firmware you need a GNU/Linux, BSD or MacOSX 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.

gcc binutils bzip2 flex python3 perl make find grep diff unzip gawk getopt
subversion libz-dev libc-dev

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.

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 freenode.net.

Developer Community

License

OpenWrt is licensed under GPL-2.0

Description
An Immortalwrt variant fot mediatek mt798x routers.
Readme
Languages
C 70%
Makefile 12.4%
Shell 6%
Roff 3.9%
Perl 2%
Other 5.6%