Open-Mesh OM2P-HS v1

From TechInfoDepot
Jump to navigationJump to search
multiple revisions of this device, use caution
bgn (N300)
OM2P-HS 300Mbps Access Point
WikiDevi.wi-cat.ru Open-Mesh OM2P-HS
3rd Party Firmware
dd-wrt Status Unknown
OpenWrt Supported
Tomato any flavor Incompatible
Gargoyle Status Unknown
Platform
BrandModelRev Open-Mesh OM2P-HS
FCC ID (fcc.io) WT8OM2PHS
FCC ID (fcc.report) WT8OM2PHS
IC ID 10103A-OM2PHS
Type mesh node, access point
CPU1 checkY Atheros AR9341
CPU1 Type MIPS 74Kc
CPU1 Speed 520 MHz
Flash1 Chip Spansion FL128PIFL
Flash1 Size 16 MiB 16,777,216 B <br />131,072 Kib <br />16,384 KiB <br />128 Mib <br />0.0156 GiB <br /> (SPI NOR)
RAM1 Size 64 MiB 67,108,864 B <br />524,288 Kib <br />65,536 KiB <br />512 Mib <br />0.0625 GiB <br />
RAM1 Chip Nanya NT5DS32M16DS-5T
ETH chip1 Atheros AR9341
Switch Atheros AR9341
Ethernet Port Count 1-100MbE-WAN
1-100MbE-LAN
Wired Standard IEEE 802.3i/3u

802dot11 OUI: AC:86:74 (5 E, 3 W)
Ethernet OUI: AC:86:74 (5 E, 3 W)

Stock bootloader U-Boot
Expansion IF types none specified
PoE non-standard (otherwise unspecified)
Power 12 VDC, 1 A
Connector type barrel
5.5 mm (OD)
2.1 mm (ID)
9.5 mm (LEN)
Serial Port (UART) yes
Other

Default SSID: open-mesh (5 addl. devices)
Default login user: root
Default login password: 0p3nm35h
root:0p3nm35h credentials used by 5 additional devices
of which 5 are Open-Mesh devices

Manuf/OEM/ODM Senao
3rd Party Firmware Support OpenWrt • (List | Dev | DLs)
Retail
FCC approval date 09 October 2012
UPC 552160054408
(UPC DB, On eBay)
Country of manuf Taiwan
Radio 1
Chip1 Atheros AR9341
Wireless interface OUI AC:86:74
Antenna Connector Type U.FL
MIMO status 2x2:1
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
 CPU1 brandRadio1 chip1 brandRadio1 chip2 brand
Open-Mesh OM2P v1AtherosAtheros
Open-Mesh OM2P v2AtherosAtheros
Open-Mesh OM2P v4Qualcomm AtherosQualcomm Atheros
Open-Mesh OM2P-HS v1AtherosAtheros
Open-Mesh OM2P-HS v2AtherosAtheros
Open-Mesh OM2P-HS v3AtherosAtheros
Open-Mesh OM2P-HS v4Qualcomm AtherosQualcomm Atheros
Open-Mesh OM2P-LCAtherosAtheros

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.) = N300 class

Overview

"7016A0608004 Ver:1.00" is silkscreened on the board in the FCC photos.

The device uses two Lynwave ALA120-052022 antennas.

The PoE implementation in this device consists of a Passive PoE feed with pins +4,5 and -7,8 at 18 VDC.

Links of Interest

On Open-Mesh's store

Datasheet

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.2
LAN Hardware: Atheros AR9341
WLAN Hardware: Atheros AR9341
WLAN Comment: MIMO 2x2:2
Installation method(s):
U-Boot TFTP + serial recovery, see git-commit
git • >>
ath79: add support for OpenMesh OM2P-HS v1
Device specifications:
======================

* Qualcomm/Atheros AR9341 rev 1
* 535/400/200 MHz (CPU/DDR/AHB)
* 64 MB of RAM
* 16 MB of SPI NOR flash
  - 2x 7 MB available; but one of the 7 MB regions is the recovery image
* 2x 10/100 Mbps Ethernet
* 2T2R 2.4 GHz Wi-Fi
* 6x GPIO-LEDs (3x wifi, 2x ethernet, 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)
* 2x fast ethernet
  - eth0
    + 802.3af POE
    + builtin switch port 1
    + used as LAN interface
  - eth1
    + 18-24V passive POE (mode B)
    + used as WAN 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