Skip to content
Snippets Groups Projects
Commit e0abce03 authored by Sven Eckelmann's avatar Sven Eckelmann
Browse files

ath79-generic: Add support for OpenMesh OM5P

Device specifications:
======================

* Qualcomm/Atheros AR9344 rev 2
* 560/450/225 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 5 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
    + 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

WAN/LAN LEDs appear to be wrong in ar71xx and have been swapped here.

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
parent d427c94e
No related branches found
No related tags found
No related merge requests found
...@@ -43,6 +43,7 @@ ath79-generic ...@@ -43,6 +43,7 @@ ath79-generic
- OM2P (v1, v2, v4) - OM2P (v1, v2, v4)
- OM2P-HS (v1, v2, v3, v4) - OM2P-HS (v1, v2, v3, v4)
- OM2P-LC - OM2P-LC
- OM5P
* Plasma Cloud * Plasma Cloud
......
...@@ -189,6 +189,10 @@ device('openmesh-om2p-lc', 'openmesh_om2p-lc', { ...@@ -189,6 +189,10 @@ device('openmesh-om2p-lc', 'openmesh_om2p-lc', {
factory = false, factory = false,
}) })
device('openmesh-om5p', 'openmesh_om5p', {
factory = false,
})
-- Plasma Cloud -- Plasma Cloud
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment