Open-Mesh MR600 v2

From TechInfoDepot
Jump to navigationJump to search
multiple revisions of this device, use caution
abgn (AN600)
4G LTE Router
3rd Party Firmware
dd-wrt Status Unknown
OpenWrt Supported
Tomato any flavor Incompatible
Gargoyle Status Unknown
Platform
BrandModelRev Open-Mesh MR600 v2
FCC ID A8J-EAP600
Type access point
CPU1 checkY Atheros AR9344
CPU1 Type MIPS 74Kc
CPU1 Speed 560 MHz 32-bit
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 Atheros AR9344
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 A
Serial Port (UART) yes
Other
3rd Party Firmware Support OpenWrt • (List | Dev | DLs)
Retail
Availability End of Life
Radio 1
Chip1 Atheros AR9344
Wireless interface OUI none specified
Antenna Connector Type U.FL
MIMO status 2x2:2
Wireless Standard IEEE 802.11b/g/n
802.11n up to 300 Mbps
802.11g up to 54 Mbps
802.11b up to 11 Mbps
WiFi Operating Frequency 2.4 GHz
Radio 2
Chip1 Atheros AR9382
Wireless interface OUI none specified
Antenna Connector Type U.FL
MIMO status 2x2:2
Wireless Standard IEEE 802.11a/n
802.11n up to 300 Mbps
802.11a up to 54 Mbps
WiFi Operating Frequency 5 GHz
 FCC ID
EnGenius EAP600A8J-EAP600
Open-Mesh MR600 v1A8J-EAP600
 CPU1 brandRadio1 chip1 brandRadio2 chip1 brand
Open-Mesh MR600 v1AtherosAtherosAtheros
Open-Mesh MR600 v2AtherosAtherosAtheros

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

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

300 Mbps - 2SS 2.4GHz 802.11n (40MHz chan.),
300 Mbps - 2SS 5GHz 802.11n (40MHz chan.) = AN600 class

Flashing

Flashing OpenWrt

Target: ath79
Subtarget: generic
Package architecture: mips_24kc
Supported Since Commit
Support started version: 21.02.0
Current supported version: 25.12.5
LAN Comment: Atheros AR8035 GbE Phy
WLAN Hardware: Atheros AR9344, Atheros AR9382
WLAN Comment: 2.4Ghz 2x2:2 MIMO, 5Ghz 2x2:2 MIMO
Installation method(s):
U-Boot TFTP recovery, see git-commit
Recovery method(s):
U-Boot TFTP recovery, see git-commit
git • >>
ath79: Add support for OpenMesh MR600 v2
Device specifications:
======================

* Qualcomm/Atheros AR9344 rev 2
* 560/450/225 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
* 2T2R 2.4 GHz Wi-Fi
* 2T2R 5 GHz Wi-Fi
* 8x GPIO-LEDs (6x wifi, 1x wps, 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