Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
inbox:toh:google:onhub_tp-link_tgr1900 [2024/02/12 21:22] – [TP-LINK TGR1900 (Google OnHub)] justanotherenduserinbox: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:
 ====== Asus / TP-LINK TGR1900 (Google OnHub) ====== ====== Asus / TP-LINK TGR1900 (Google OnHub) ======
 ~~NOTOC~~ ~~NOTOC~~
 +
 +{{ media:google_onhub_image.jpg?400|TP-LINK OnHub TGR1900}}
 +
 +{{ media:asus:asus_onhub.jpg?150|ASUS Onhub SRT-AC1900}}
  
 /* This template is intended to be used via https://openwrt.org/meta/create_new_device_page . */ /* This template is intended to be used via https://openwrt.org/meta/create_new_device_page . */
- 
-{{page>meta:infobox:construction&noheader&nofooter&noeditbtn}} 
  
 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://coreboot.org/|Coreboot]] and [[https://libreboot.org/docs/depthcharge/|Depthcharge]], and can be convinced to run non-Google-signed software (such as OpenWrt) by entering Developer Mode. 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://coreboot.org/|Coreboot]] and [[https://libreboot.org/docs/depthcharge/|Depthcharge]], and can be convinced to run non-Google-signed software (such as OpenWrt) by entering Developer Mode.
Line 10: Line 12:
 ASUS OnHub SRT-AC1900 is a nearly-identical AP, with almost identical hardware specifications, and nearly identical stock firmware. Thus, much of this page applies to it as well. ASUS OnHub SRT-AC1900 is a nearly-identical AP, with almost identical hardware specifications, and nearly identical stock firmware. Thus, much of this page applies to it as well.
  
-/*****/ +The TP-Link uses a standard 12V barrel jackThe 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 ========> https://openwrt.org/meta/adding_images_to_openwrt_wiki */ +
-/*****/ +
- +
-{{ media:google_onhub_image.jpg?400|TP-LINK OnHub TGR1900}} +
- +
-{{ media:asus:asus_onhub.jpg?150|ASUS Onhub SRT-AC1900}} +
 ===== Supported Versions ===== ===== Supported Versions =====
 <!-- ToH: { <!-- ToH: {
Line 342: Line 337:
  
 ==== Serial ==== ==== Serial ====
--> [[docs:techref:hardware:port.serial]] general information about the serial port, serial port cable, etc. 
  
-How to connect to the Serial Port of this specific device:\\ +{{ :media:tplink:tgr1900_servo_header.jpg?400|}}
-**Insert photo of PCB with markings for serial port**+
  
-<WRAP BOX> +OnHub devices share the [[https://chromium.googlesource.com/chromiumos/third_party/hdctools/+/HEAD/docs/servo_v2.md|Servo debug header]] used on many ChromeOS systems. The debug header has a 50-pin footprint, and provides access to UART pins among many other debug-related signals. Unfortunately, this header is typically populated with a proper connector only for Google-internal boards, and the companion Servo board is only available to Google engineers. 
-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://www.chromium.org/chromium-os/servo/chromium_os_yoshi_flex.tar.gz|"Yoshi" flex cable schematic]], and particularly its contained ''Schematic/810-10062-00_20130625_yoshi_flex_SCH_0.pdf''. In short, the relevant pins are: 
 + 
 +  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 1514: Line 1514:
 Technical information: [[hwinfo>TP-LINK_TGR1900_(Google_OnHub)]]  Technical information: [[hwinfo>TP-LINK_TGR1900_(Google_OnHub)]] 
  
-Information about bootloader: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_mode.md+Information about bootloader: https://www.chromium.org/chromium-os/developer-library/guides/device/developer-mode/
  
 ===== Tags ===== ===== Tags =====
 [[meta:tags|How to add tags]] [[meta:tags|How to add tags]]
 {{tag>ipq806x ipq8064 4096emmc 1024ram 2port gigabitethernet 802.11abgnac 2core arm armv7}} {{tag>ipq806x ipq8064 4096emmc 1024ram 2port gigabitethernet 802.11abgnac 2core arm armv7}}
  • Last modified: 2024/09/25 18:42
  • by ryanrs