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 | ||
| inbox:toh:google:onhub_tp-link_tgr1900 [2023/05/31 09:05] – [Photos] developer screw on the Asus linus | inbox:toh:google:onhub_tp-link_tgr1900 [2024/09/21 04:15] – [Asus / TP-LINK TGR1900 (Google OnHub)] Power jack details. ryanrs | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== TP-LINK TGR1900 (Google OnHub) ====== | + | ====== |
| ~~NOTOC~~ | ~~NOTOC~~ | ||
| + | |||
| + | {{ media: | ||
| + | |||
| + | {{ media: | ||
| /* This template is intended to be used via https:// | /* This template is intended to be used via https:// | ||
| - | {{page> | + | Asus / TP-LINK OnHub TGR1900 is a 3x3 802.11ac AP with a quad-core Qualcomm IPQ8064 SoC, 1 GiB RAM, and 4 GiB eMMC storage. Its stock firmware is based on ChromeOS, including a bootloader based on [[https:// |
| - | + | ||
| - | TP-LINK OnHub TGR1900 is a 3x3 802.11ac AP with a quad-core Qualcomm IPQ8064 SoC, 1 GiB RAM, and 4 GiB eMMC storage. Its stock firmware is based on ChromeOS, including a bootloader based on [[https:// | + | |
| ASUS OnHub SRT-AC1900 is a nearly-identical AP, with almost identical hardware specifications, | ASUS OnHub SRT-AC1900 is a nearly-identical AP, with almost identical hardware specifications, | ||
| - | /*****/ | + | The TP-Link uses a standard 12V barrel jack. The ASUS has a weird connector for 19V. Keep this in mind if you're buying on eBay, since many listings won't include the power supply. |
| - | /* How to add images ========> | + | |
| - | /*****/ | + | |
| - | + | ||
| - | {{ media: | + | |
| - | + | ||
| - | {{ media: | + | |
| ===== Supported Versions ===== | ===== Supported Versions ===== | ||
| - | ---- datatable ---- | + | <!-- ToH: { |
| - | cols | + | " |
| - | headers | + | " |
| - | align : c,c,c,c,c,c,c | + | " |
| - | filter | + | " |
| - | filter | + | " |
| - | ---- | + | |
| + | } --> | ||
| - | ---- datatable ---- | + | <!-- ToH: { |
| - | cols | + | " |
| - | headers | + | " |
| - | align : c,c,c,c,c,c,c | + | " |
| - | filter | + | " |
| - | filter | + | |
| - | ---- | + | } --> |
| ===== Hardware Highlights ===== | ===== Hardware Highlights ===== | ||
| - | ---- datatable ---- | + | <!-- ToH: { |
| - | cols | + | " |
| - | header | + | " |
| - | align : c,c,c,c,c,c,c,c,c,c,c,c,c | + | " |
| - | filter | + | |
| - | filter | + | " |
| - | ---- | + | |
| + | } --> | ||
| - | ---- datatable ---- | + | <!-- ToH: { |
| - | cols | + | " |
| - | header | + | " |
| - | align : c,c,c,c,c,c,c,c,c,c,c,c,c | + | |
| - | filter | + | " |
| - | filter | + | |
| - | ---- | + | } --> |
| ===== Installation ===== | ===== 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 | ||
| - | filter | ||
| - | ---- | ||
| - | |||
| - | ---- 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 | ||
| - | filter | ||
| - | ---- | ||
| - | |||
| - | {{page> | ||
| + | Download OpenWRT firmware: [[https:// | ||
| + | For explanation of the different types of images, see [[docs: | ||
| /*** if info available: uncomment and fill in | /*** if info available: uncomment and fill in | ||
| Line 111: | Line 93: | ||
| ==== Installing OpenWrt ==== | ==== Installing OpenWrt ==== | ||
| - | In the following steps, you will configure Google OnHub for Developer Mode, and boot from a USB image containing OpenWrt. You will again need: | + | In the following steps, you will configure Google OnHub for Developer Mode, and boot from a USB image containing OpenWrt. You will need: |
| - | * USB drive (flash OpenWrt '' | + | * USB drive that is **4GB or bigger** notice that this size if **not optional**, |
| - | * 1.5mm hex key | + | * 1.5mm hex key (TP-LINK variant) or an ordinary Philips screwdriver (ASUS variant) |
| * Pin to press reset button | * Pin to press reset button | ||
| Procedure: | Procedure: | ||
| - | - Peel off the rubber feet at the bottom of the device to reveal the hidden switch screw (see location on picture [[# | + | - Write the right factory image to the USB drive with **dd**. This done by writing the whole squashfs factory image to the entire device, i.e. **dd if=openwrt-ipq806x-chromium-[asus|tplink]_onhub-squashfs-factory.bin of=/ |
| - | | + | - TP-LINK variant: |
| - | - Plug in USB stick containing OpenWrt | + | * Write the OpenWrt image '' |
| - | - Hold the Reset button (Near the power jack) | + | * Peel off the rubber feet at the bottom of the device to reveal the hidden switch screw on the TP-LINK variant |
| + | | ||
| + | - ASUS variant: | ||
| + | * Write the OpenWrt image '' | ||
| + | * Peel off the rubber feet at the bottom of the device | ||
| + | * Remove all four screws breaking the warranty seal | ||
| + | * Remove the bottom plate | ||
| + | * Remove the three screws holding the speaker in place | ||
| + | * Lift up and fold the speaker to the side | ||
| + | * Unscrew the developer mode screw as illustrated in the [[# | ||
| + | - Plug in the USB stick containing OpenWrt | ||
| + | - Hold the Reset button (Near the power jack on the TP-LINK variant, right above the USB port on the ASUS variant) | ||
| - Connect power to the device while holding Reset button | - Connect power to the device while holding Reset button | ||
| - The LED will be white and after a few seconds should blink orange; After a few more seconds, the LED should blink red: you may now release the Reset button | - The LED will be white and after a few seconds should blink orange; After a few more seconds, the LED should blink red: you may now release the Reset button | ||
| - | - Press the developer mode switch at the bottom of the device: | + | - Press the developer mode switch at the bottom of the device |
| - | * Insert | + | * On the TP-LINK variant: insert |
| + | * On the ASUS variant: the developer mode switch is the small white pushbutton underneath the device, next to the developer mode screw | ||
| * The LEDs should blink purple and the device will restart. | * The LEDs should blink purple and the device will restart. | ||
| - Wait a few seconds for the device to finish booting: it will start blinking purple again and possibly beep twice. | - Wait a few seconds for the device to finish booting: it will start blinking purple again and possibly beep twice. | ||
| Line 165: | Line 159: | ||
| === Expanding storage (optional) === | === Expanding storage (optional) === | ||
| + | |||
| + | <WRAP center round info 650px> | ||
| + | OpenWrt 23.05 automatically resizes storage to full 4GB, so it's not necessary to run the commands below manually. Instructions below are for reference only. | ||
| + | </ | ||
| + | |||
| + | < | ||
| You can expand your storage to the full 4GB this device has by executing the following through SSH:\\ | You can expand your storage to the full 4GB this device has by executing the following through SSH:\\ | ||
| <code bash> | <code bash> | ||
| Line 185: | Line 185: | ||
| More information about expanding for squashfs and ext4 is provided here: [[: | More information about expanding for squashfs and ext4 is provided here: [[: | ||
| + | |||
| + | </ | ||
| /*** if info available: uncomment and fill in | /*** if info available: uncomment and fill in | ||
| Line 248: | Line 250: | ||
| ***/ | ***/ | ||
| + | ===== Basic configuration ===== | ||
| + | -> [[docs: | ||
| + | Set up your Internet connection, configure wireless, configure USB port, etc. | ||
| + | |||
| + | ===== Specific Configuration ===== | ||
| + | ==== Network interfaces ==== | ||
| + | The default network configuration is: | ||
| + | ^ Interface Name ^ Description | ||
| + | | br-lan (eth1.1) | LAN & WiFi bridge | ||
| + | | br-wan (eth0.2) | WAN bridge | ||
| + | | vlan1 (eth1.1) | ||
| + | | vlan2 (eth0.2) | ||
| + | | radio0 | ||
| + | | radio1 | ||
| + | | radio2 | ||
| + | |||
| + | Note transfer speeds are slow on '' | ||
| + | |||
| + | ==== Switch Ports (for VLANs) | ||
| + | |||
| + | OpenWrt Switch port number 1 is the LAN Ethernet port labeled ''< | ||
| + | |||
| + | By default, '' | ||
| + | ^ Port ^ Switch port ^ | ||
| + | | CPU (eth0) | ||
| + | | LAN | 1 | | ||
| + | | WAN | 2 | | ||
| + | | CPU (eth1) | ||
| ===== Hardware ===== | ===== Hardware ===== | ||
| ==== Info ==== | ==== Info ==== | ||
| Line 265: | Line 295: | ||
| ^ Serial | ^ Serial | ||
| ^ JTAG | | | ^ JTAG | | | ||
| + | |||
| Line 297: | Line 328: | ||
| [{{: | [{{: | ||
| {{: | {{: | ||
| + | |||
| + | To unscrew the developer screw on the ASUS variant, it is necessary to remove the bottom plate (four screws under the feet of the device) then remove the speaker (three screws around the speaker) and then you can use a long-ish screwdriver to unscrew the developer mode screw. | ||
| ==== Opening the case ==== | ==== Opening the case ==== | ||
| Line 304: | Line 337: | ||
| ==== Serial ==== | ==== Serial ==== | ||
| - | -> [[docs: | ||
| - | How to connect to the Serial Port of this specific device:\\ | + | {{ :media: |
| - | **Insert photo of PCB with markings for serial port** | + | |
| - | <WRAP BOX> | + | OnHub devices share the [[https://chromium.googlesource.com/chromiumos/third_party/ |
| - | FIXME //Replace EXAMPLE by real values.// | + | |
| - | </WRAP> | + | However, you may not be out of luck; it's technically possible to wire up your own connector, as the debug pads are still available on production systems, as highlighted on the board photo. The pinout is well documented in the [[https:// |
| + | |||
| + | 15 = GND | ||
| + | 16 = 1P8_UART2_RX | ||
| + | 17 = 1P8_UART2_TX | ||
| + | 18 = PP1800 | ||
| - | ^ Serial connection parameters\\ for Google Onhub TP-LINK TGR1900 | EXAMPLE 115200, 8N1, 3.3V | | + | Skillful soldering could theoretically attach wires to these pins to bring out the 1.8V TTL UART port. |
| + | UART console is available in default software for both the stock ChromeOS firmware (once the device is in Developer Mode) and in OpenWrt. | ||
| + | ^ Serial connection parameters\\ for TP-LINK and ASUS OnHub | 115200, 8N1, 1.8V | | ||
| ===== Bootlogs ===== | ===== Bootlogs ===== | ||
| ==== OEM bootlog ==== | ==== OEM bootlog ==== | ||
| Line 1476: | Line 1514: | ||
| Technical information: | Technical information: | ||
| - | Information about bootloader: https:// | + | Information about bootloader: https://www.chromium.org/chromium-os/developer-library/guides/device/ |
| ===== Tags ===== | ===== Tags ===== | ||
| [[meta: | [[meta: | ||
| {{tag> | {{tag> | ||