ASUS RT-AX57M

Under Construction!
This page is currently under construction. You can edit the article to help completing it.

ASUS RT-AX57M, RT-AX54HP V2, RT-AX1800HP V2, RT-AX1800S V2, and RT-AX3000S all use the same firmware and have identical hardware (as per commit)

Getting started with a new Device Page

This is an empty template that suggests the information that should be present on a well-constructed Device Page. This means, that you have to fill it with life and information.
There are several “fixme” tags with text on a light background (like this text) throughout this template. As you fill in the page, remove those tags so that people can judge its completeness.
When there are no more “fixme” tags left, delete this one too, along with the <WRAP> that encloses it.

Keep the articles modular

Please include only model specific information, omit bla,bla and put everything generic into separate articles
If you have no time to write certain stuff, link to docs
base-system should lead the way, do not explain this again
DO NOT provide a complete howto here! Instead groom the general documentation.

Supported Versions

The tables below are automatically generated, once the correct filters for Brand and Model are set.
If the tables below show information for ASUS RT-AX57M , everything is OK and you can delete this text and the <WRAP> that encloses it.
If the tables below contain “Nothing found”, it means that either
1. the dataentry page for ASUS RT-AX57M is missing. Please create a new dataentry page first, then reload this page. The tables should then contain $something. If they do, delete this text and the <WRAP> that encloses it.
2. filters are not set correctly. Most common reason for “Nothing found”: The dataentry does not contain a Version, but we are filtering here for version → Please edit this section and adjust the filters with the proper Brand, Model and Version. In case the dataentry does not contain a version, delete the line filter : Versions~. Just try, it's easy. The tables should then contain $something. If they do, delete this text and the <WRAP> that encloses it.
If the tables still contain “Nothing found”: Don't panic, calm down, take a deep breath and contact a wiki admin (tmomas) for help.

Experimental Versions

None at this time.

Hardware Highlights

Installation

→ Install OpenWrt (generic explanation)

?p=openwrt/openwrt.git;a=commit;h=fafb36f865ce7406085f970adad36ff85ea860d9

As per commit above:

Installation
-----------------------------------------------------------
Vendor-UI Method
-----------------------------------------------------------
1. Download the OpenWrt initramfs.trx image.

2. Connect the PC via LAN to one of the yellow router ports and wait
   until your PC to get a DHCP lease.

3. Browse to http://192.168.1.1 (or whatever your router IP is configured as)

4. If your router is brand new, finish the setup process and log into
   the Web-UI.

5. Navigate to Administration -> Firmware Upgrade and upload the
   downloaded OpenWrt initramfs.trx image.

6. Wait for OpenWrt to boot. Open the default OpenWrt IP in a web browser and perform a system upgrade using the sysupgrade image as instructed in the top banner.

---------------------------------------------------------------------------
Revert to stock firmware:
1: Install package facinstall -> https://forum.openwrt.org/t/facinstall-package-for-easy-installation-factory-images/177587
2. Install Asus stock trx image via OpenWRT LuCI interface.

Flash Layout

(After installation)

cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 00400000 00020000 "bootloader"
mtd1: 07c00000 00020000 "UBI_DEV"

root@OpenWrt:~#  ubinfo  -a
UBI version:                    1
Count of UBI devices:           1
UBI control device major/minor: 10:127
Present UBI devices:            ubi0

ubi0
Volumes count:                           7
Logical eraseblock size:                 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks:     992 (125960192 bytes, 120.1 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  20
Current maximum erase counter value:     5
Minimum input/output unit size:          2048 bytes
Character device major/minor:            250:0
Present volumes:                         0, 1, 2, 3, 4, 5, 6

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        1 LEBs (126976 bytes, 124.0 KiB)
State:       OK
Name:        nvram
Character device major/minor: 250:1
-----------------------------------
Volume ID:   1 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        8 LEBs (1015808 bytes, 992.0 KiB)
State:       OK
Name:        Factory
Character device major/minor: 250:2
-----------------------------------
Volume ID:   2 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        8 LEBs (1015808 bytes, 992.0 KiB)
State:       OK
Name:        Factory2
Character device major/minor: 250:3
-----------------------------------
Volume ID:   3 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        33 LEBs (4190208 bytes, 3.9 MiB)
State:       OK
Name:        linux
Character device major/minor: 250:4
-----------------------------------
Volume ID:   4 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        2 LEBs (253952 bytes, 248.0 KiB)
State:       OK
Name:        jffs2
Character device major/minor: 250:5
-----------------------------------
Volume ID:   5 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        177 LEBs (22474752 bytes, 21.4 MiB)
State:       OK
Name:        rootfs
Character device major/minor: 250:6
-----------------------------------
Volume ID:   6 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        737 LEBs (93581312 bytes, 89.2 MiB)
State:       OK
Name:        rootfs_data
Character device major/minor: 250:7

OEM easy installation

See installation instructions above

OEM installation using the TFTP method

→ generic.flashing.tftp

Specific values needed for tftp

Enter values for “FILL-IN” below

Bootloader tftp server IPv4 address	FILL-IN
Bootloader MAC address (special)	FILL-IN
Firmware tftp image	Latest OpenWrt release (`NOTE:` Name must contain “tftp”)
TFTP transfer window	FILL-IN seconds
TFTP window start	approximately FILL-IN seconds after power on
TFTP client required IP address	FILL-IN

Upgrading OpenWrt

→ generic.sysupgrade

These are generic instructions. Update with your router's specifics.

LuCI Web Upgrade Process

Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL
Upload image file for sysupgrade to LuCI
Wait for reboot

Terminal Upgrade Process

If you don't have a GUI (LuCI) available, you can alternatively upgrade via the command line. There are two command line methods for upgrading:

sysupgrade
mtd

Note: It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.

sysupgrade

cd /tmp
wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc
sysupgrade /tmp/xxx.abc

mtd

If sysupgrade does not support this router, use mtd.

cd /tmp
wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc
mtd write /tmp/xxx.abc linux && reboot

Debricking

→ generic.debrick

Failsafe mode

→ failsafe_and_factory_reset

Basic configuration

→ Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.

Specific Configuration

Network interfaces

The default network configuration (as best can be told) is:

Interface Name	Description	Default configuration
br-lan	LAN & WiFi	192.168.1.1/24
eth0	2.5Gbit port marked WAN (NOTE ISSUE)	Setup for DHCP (external), not working
lan1-4	Default LAN 1Gbit port	DHCP (internal)
phy0-ap0	Default 2.4GHz Wifi ax/b/g/n	DHCP (internal)
phy1-ap0	Default 5GHz Wifi ac/ax/n	DHCP (internal)

NOTE ISSUE: On some versions of OpenWRT the wan port has NOT been supported, so the workaround is to move the wan port to the lan and one of the lan ports (in my case lan4) to the WAN.

Switch Ports (for VLANs)

Please fill in real values for this device, then remove the EXAMPLEs

Numbers 0-3 are Ports 1-4 as labeled on the unit, number 4 is the Internet (WAN) on the unit, 5 is the internal connection to the router itself. Don't be fooled: Port 1 on the unit is number 3 when configuring VLANs. vlan0 = eth0.0, vlan1 = eth0.1 and so on.

Port	Switch port
Internet (WAN)	EXAMPLE 4
LAN 1	EXAMPLE 3
LAN 2	EXAMPLE 2
LAN 3	EXAMPLE 1
LAN 4	EXAMPLE 0

Buttons

→ hardware.button on howto use and configure the hardware button(s). Here, we merely name the buttons, so we can use them in the above Howto.

Please fill in real values for this device, then remove the EXAMPLEs

The ASUS RT-AX57M has the following buttons:

BUTTON	Event
EXAMPLE Reset	reset
EXAMPLE Secure Easy Setup	ses
EXAMPLE No buttons at all.	-

Hardware

Info

This table is automatically generated, once the correct filters for Brand and Model are set.
If you see “Nothing.” instead of a table, please edit this section and adjust the filters with the proper Brand and Model. Just try, it's easy.
If you still don't see a table here, or a table filled with '¿': Is there already a Techdata page available for ASUS RT-AX57M ? If not: Create one.
If you see a table with the desired device data, everything is OK and you can delete this text and the <WRAP> that encloses it.
If it still doesn't work: Don't panic, calm down, take a deep breath and contact a wiki admin (tmomas) for help.

---- datatemplatelist dttpllist ---- template: meta:template_datatemplatelist cols : Brand, Model, Versions, Device Type, Availability, Supported Since Commit_git, Supported since Rel, Supported current Rel, Unsupported, Bootloader, CPU, Target, CPU MHz, Flash MBs, RAM MB, Switch, Ethernet 100M ports_, Ethernet Gbit ports_, Comments network ports_, Modem, VLAN, WLAN 2.4GHz, WLAN 5.0GHz, WLAN Hardwares, WLAN Comments_, Detachable Antennas_, USB ports_, SATA ports_, Comments USB SATA ports_, Serial, JTAG, LED count, Button count, Power supply, Device Techdata_pageid, Forum topic URL_url, wikidevi URL_url, OEM Device Homepage URL_url, Firmware OEM Stock URL_url, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Comments_ filter : Brand=ASUS filter : Model=RT-AX57M filter : Versions=

Photos

Front:
Insert photo of front of the casing

Back:
Insert photo of back of the casing

Backside label:
Insert photo of backside label

Opening the case

→ Warranty

Describe what needs to be done to open the device, e.g. remove rubber feet, adhesive labels, screws, ...

To remove the cover and open the device, do a/b/c

Main PCB:
Insert photo of PCB

Serial

→ port.serial general information about the serial port, serial port cable, etc.

How to connect to the Serial Port of this specific device:
Insert photo of PCB with markings for serial port

Replace EXAMPLE by real values.

Serial connection parameters for ASUS RT-AX57M @@Version@@	EXAMPLE 115200, 8N1, 3.3V

JTAG

→ port.jtag general information about the JTAG port, JTAG cable, etc.

How to connect to the JTAG Port of this specific device:
Insert photo of PCB with markings for JTAG port

Bootloader mods

→ bootloader

Hardware mods

None so far.

Bootlogs

OEM bootlog

COPY HERE THE BOOTLOG WITH THE ORIGINAL FIRMWARE

OpenWrt bootlog

COPY HERE THE BOOTLOG ONCE OPENWRT IS INSTALLED AND RUNNING

Notes

Space for additional notes, links to forum threads or other resources.

Table of Contents