Open-Mesh MR1750 v2

multiple revisions of this device, use caution

abgn+ac (AC1750)
MR Series Wireless-AC Access Point
3rd Party Firmware
dd-wrt	Status Unknown
OpenWrt	Supported
Tomato any flavor	Incompatible
Gargoyle	Status Unknown
Platform
Brand • Model • Rev	Open-Mesh MR1750 v2
FCC ID	none specified
Type	access point
CPU1 Y	Qualcomm Atheros QCA9558
CPU1 Type	MIPS 74Kc
CPU1 Speed	720 MHz
Flash1 Chip	Brand? Model?
Flash1 Size	16 MiB 16,777,216 B <br />131,072 Kib <br />16,384 KiB <br />128 Mib <br />0.0156 GiB <br />
RAM1 Size	128 MiB 134,217,728 B <br />1,048,576 Kib <br />131,072 KiB <br />1,024 Mib <br />0.125 GiB <br />
RAM1 Chip	Brand? Model?
ETH chip1	Qualcomm Atheros QCA9558
ETH chip2	Atheros AR8035
Ethernet Port Count	1-1GbE-LAN
Wired Standard	IEEE 802.3i/3u/3ab
802dot11 OUI: none specified
Stock bootloader	U-Boot
Expansion IF types	none specified
PoE	802.3af, standard
Power	12-24 VDC, 1.0 A
Serial Port (UART)	yes
Other
3rd Party Firmware Support	OpenWrt • (List | Dev | DLs)
Radio 1
Chip1	Qualcomm Atheros QCA9558
Wireless interface OUI	none specified
Antenna Connector Type	none specified
MIMO status	3x3:3
Wireless Standard	IEEE 802.11b/g/n
802.11n	up to 450 Mbps
802.11g	up to 54 Mbps
802.11b	up to 11 Mbps
WiFi Operating Frequency	2.4 GHz
Radio 2
Chip1	Qualcomm Atheros QCA9880
Wireless interface OUI	none specified
Antenna Connector Type	none specified
MIMO status	3x3:3
Wireless Standard	IEEE 802.11a/n/ac
802.11ac	up to 1300 Mbps
802.11n	up to 450 Mbps
802.11a	up to 54 Mbps
WiFi Operating Frequency	5 GHz
CPU1 brand Radio1 chip1 brand Radio2 chip1 brand Open-Mesh MR1750 v1 Qualcomm Atheros Qualcomm Atheros Qualcomm Atheros Open-Mesh MR1750 v2 Qualcomm Atheros Qualcomm Atheros Qualcomm Atheros

For a list of all currently documented Atheros (QCA) chipsets with specifications, see Atheros.
For a list of all currently documented Qualcomm Atheros (QCA) chipsets with specifications, see Qualcomm Atheros.

For a list of all currently documented Open-Mesh devices with specifications, see Open-Mesh.

• 450 Mbps - 3SS 2.4GHz 802.11n (40MHz chan.),

• 1300 Mbps - 3SS 5GHz 802.11ac (80MHz chan.) = AC1750 class

Flashing

Flashing OpenWrt

On the OpenWrt ToH (techdata entry)

Target: ath79
Subtarget: generic
Package architecture: mips_24kc
Supported Since Commit
Support started version: 17.01.0
Current supported version: 25.12.5

LAN Comment: Atheros AR8035 GbE Phy
WLAN Hardware: Qualcomm Atheros QCA9558, Atheros AR9880
WLAN Comment: 2.4Ghz 3x3:3 MIMO, 5Ghz 3x3:3 MIMO
Installation method(s):
U-Boot TFTP recovery, see git-commit
Recovery method(s):
U-Boot TFTP recovery

git • >>

ath79: Add support for OpenMesh MR1750 v2 Device specifications: ====================== * Qualcomm/Atheros QCA9558 ver 1 rev 0 * 720/600/240 MHz (CPU/DDR/AHB) * 128 MB of RAM * 16 MB of SPI NOR flash - 2x 7 MB available; but one of the 7 MB regions is the recovery image * 3T3R 2.4 GHz Wi-Fi (11n) * 3T3R 5 GHz Wi-Fi (11ac) * 6x GPIO-LEDs (2x wifi, 2x status, 1x lan, 1x power) * 1x GPIO-button (reset) * external h/w watchdog (enabled by default)) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 1x ethernet - AR8035 ethernet PHY (RGMII) - 10/100/1000 Mbps Ethernet - 802.3af POE - used as LAN interface * 12-24V 1A DC * internal antennas Flashing instructions: ====================== Various methods can be used to install the actual image on the flash. Two easy ones are: ap51-flash ---------- The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the image to the u-boot when the device boots up. initramfs from TFTP ------------------- The serial console must be used to access the u-boot shell during bootup. It can then be used to first boot up the initramfs image from a TFTP server (here with the IP 192.168.1.21): setenv serverip 192.168.1.21 setenv ipaddr 192.168.1.1 tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr The actual sysupgrade image can then be transferred (on the LAN port) to the device via scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/ On the device, the sysupgrade must then be started using sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin