Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:openmesh:om2p [2016/03/12 03:01] – Request for confirmation of OpenWrt support added tmomas | toh:openmesh:om2p [2022/02/04 05:32] – [Notes] teppo | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Open-Mesh.com OM2P ====== | ||
| + | High Power 802.11n Mini Router including hardware watchdog, passive 12-18v (NON 802.3af) POE support, dual Ethernet Ports | ||
| + | ===== Supported Versions ===== | ||
| + | ---- datatable ---- | ||
| + | cols : Brand, Model, Versions, Supported Current Rel, OEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid | ||
| + | headers : Brand, Model, Version, Current Release, OEM Info, Forum Topic, Technical Data | ||
| + | align : c, | ||
| + | filter | ||
| + | ---- | ||
| + | |||
| + | ===== Hardware Highlights ===== | ||
| + | ---- datatable ---- | ||
| + | cols : Model, CPU, CPU MHz, Flash MB_mbflashs, | ||
| + | header | ||
| + | align : c, | ||
| + | filter | ||
| + | ---- | ||
| + | |||
| + | ===== Installation ===== | ||
| + | ---- datatable ---- | ||
| + | cols : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url | ||
| + | headers : Model, Version, Current Release, Firmware OpenWrt Install, Firmware OpenWrt Upgrade, Firmware OEM Stock | ||
| + | align : c,c,c | ||
| + | filter | ||
| + | ---- | ||
| + | |||
| + | -> [[docs: | ||
| + | |||
| + | ==== Flash Layout ==== | ||
| + | For now I only have the mtd layout: | ||
| + | dev: size | ||
| + | mtd0: 00040000 00040000 " | ||
| + | mtd1: 00040000 00040000 " | ||
| + | mtd2: 00140000 00040000 " | ||
| + | mtd3: 00100000 00040000 " | ||
| + | mtd4: 00600000 00040000 " | ||
| + | mtd5: 003c0000 00040000 " | ||
| + | mtd6: 00700000 00040000 " | ||
| + | mtd7: 00040000 00040000 " | ||
| + | |||
| + | ==== OEM installation using the TFTP method ==== | ||
| + | |||
| + | After building your firmware your firmware will be the following: | ||
| + | trunk/ | ||
| + | Use the ap51-flash utility built in step 9 above and run: | ||
| + | ./ | ||
| + | Then plugin the OM2P in eth0 and power it up. | ||
| + | |||
| + | The output of the flash tool should look like this: | ||
| + | |||
| + | [MA: | ||
| + | [MA: | ||
| + | [MA: | ||
| + | [MA: | ||
| + | [MA: | ||
| + | [MA: | ||
| + | |||
| + | ==== Upgrading OpenWrt ==== | ||
| + | The recommended way to upgrade is via the " | ||
| + | |||
| + | sysupgrade / | ||
| + | |||
| + | === Manually === | ||
| + | In order to manually flash a new version of the firmware and kernel from within the device itself, you can download the following files to the device /tmp folder: | ||
| + | OM2P: | ||
| + | trunk/ | ||
| + | trunk/ | ||
| + | |||
| + | Then ssh to the device to update and perform the following: | ||
| + | cd /tmp | ||
| + | mtd -e kernel write vmlinux-om2p.uImage kernel | ||
| + | mtd -e rootfs write root.squashfs rootfs | ||
| + | reboot ; exit | ||
| + | Again, the recommended way is to use the sysupgrade script. | ||
| + | |||
| + | === LuCI Web Upgrade Process === | ||
| + | |||
| + | There is a bug in LuCI which currently prevents us to upgrade via the web interface, but a fix is on its way. | ||
| + | |||
| + | ===== Debricking ===== | ||
| + | TODO | ||
| + | |||
| + | ===== Basic configuration ===== | ||
| + | |||
| + | Plug a lan cable to the left connector, telnet 192.168.1.1 and set new password. For more details | ||
| + | follow instructions on [[: | ||
| + | Afterwards you can use the web interface at '' | ||
| + | |||
| + | ===== Specific Configuration ===== | ||
| + | ==== Interfaces ==== | ||
| + | |||
| + | By default, the lan interface is mapped to eth0 and the wan interface to eth1, which works but doesn' | ||
| + | |||
| + | ==== Switch Ports (for VLANs) ==== | ||
| + | TODO | ||
| + | |||
| + | ==== Failsafe mode ==== | ||
| + | |||
| + | Pushing the button for factory reset does not switch the device to failsafe mode. | ||
| + | |||
| + | ==== Buttons ==== | ||
| + | |||
| + | There is only one tiny button for factory reset, but it doesn' | ||
| + | |||
| + | ===== Build Image ===== | ||
| + | The following are the steps required to build an OM2P build environment. Fortunately openmesh.com/ | ||
| + | |||
| + | 1. Install and update CentOS (optional) | ||
| + | |||
| + | 2. Create openwrt user (optional) | ||
| + | useradd -m openwrt | ||
| + | 3. Add password for user openwrt (optional) | ||
| + | passwd openwrt | ||
| + | 4. Install any missing packages: (optional) | ||
| + | yum -y install minicom lrzsz gawk flex ncurses-devel subversion expect git zlib-devel gcc-c++ gmp gmp-devel unzip wget | ||
| + | 5. Switch to the openwrt user (optional) | ||
| + | su -l openwrt | ||
| + | 6. Checkout OpenWRT (trunk): | ||
| + | svn co svn:// | ||
| + | 7. Updated feeds | ||
| + | cd trunk ; scripts/ | ||
| + | 8. Install required feeds: | ||
| + | scripts/ | ||
| + | 9. Downloading and building the ap51-flash flashing utility | ||
| + | git clone https:// | ||
| + | (which currently redirects to) | ||
| + | (https:// | ||
| + | cd ap51-flash | ||
| + | make | ||
| + | 10. Make the config for the required device: make menuconfig | ||
| + | Target System -> Atheros AR71xx/ | ||
| + | Target Profile -> OpenMesh OM2P | ||
| + | Base system -> <*> om-watchdog | ||
| + | LuCI -> Collections -> <*> luci | ||
| + | Server Interfaces -> <*> luci-sgi-uhttpd | ||
| + | 11. Start the make process and enjoy a few coffee... | ||
| + | make | ||
| + | |||
| + | |||
| + | ===== Hardware ===== | ||
| + | ==== Info ==== | ||
| + | |||
| + | CPU: MIPS 24Kc V7.4 | ||
| + | Memory: 61272k/ | ||
| + | eth0/eth1: Atheros AG71xx | ||
| + | AR7240/ | ||
| + | ieee80211 phy0: Atheros AR9285 Rev:2 | ||
| + | m25p80 spi0.0: s25sl12800 (16384 Kbytes) | ||
| + | serial8250.0: | ||
| + | |||
| + | ==== Photos ==== | ||
| + | Model Number: OM2P 802.11g/n 150mbps Access Point with External Antenna | ||
| + | |||
| + | {{: | ||
| + | {{: | ||
| + | |||
| + | ==== Opening the case ==== | ||
| + | **Note:** This will void your warranty! | ||
| + | |||
| + | 1. Gently remove the front 2 rubber feet (farthest from the rear ports). | ||
| + | |||
| + | 2. Remove the 2 screws. | ||
| + | |||
| + | 3. Carefully lift the front of the lid (not more than about 5 mm), then slide forward (away from the rear ports). | ||
| + | |||
| + | ==== Serial ==== | ||
| + | This is a 3.3v serial port | ||
| + | |||
| + | baudrate is : 115200 | ||
| + | flowcontrol | ||
| + | parity is : none | ||
| + | databits are : 8 | ||
| + | |||
| + | With the ethernet jacks in front of you, the pinout should look like this: | ||
| + | |||
| + | +---+ | ||
| + | |RXD| | ||
| + | +---+ | ||
| + | |TXD| | ||
| + | +---+ | ||
| + | |GND| | ||
| + | +---+ | ||
| + | |VCC| | ||
| + | +---+ | ||
| + | +-----+ +----+----+ +---+ | ||
| + | |Power| |LAN1|LAN2| |Ant| | ||
| + | +-----+ +----+----+ +---+ | ||
| + | |||
| + | ==== JTAG ==== | ||
| + | TODO | ||
| + | |||
| + | |||
| + | ===== Hardware mods ===== | ||
| + | It is possible to add an iBeacon bluetooth low energy module to add iBeacon functionality | ||
| + | to the OM2P, as is demonstrated | ||
| + | |||
| + | ===== Notes ===== | ||
| + | OM2Pv2 is also supported via these above install instructions, | ||
| + | |||
| + | ===== Tags ===== | ||
| + | [[meta: | ||
| + | {{tag> | ||