mirror of
https://github.com/openwrt/openwrt.git
synced 2026-10-18 22:26:28 +04:00
Hardware: - SoC: Broadcom BCM4708A0, 2x Cortex-A9 at 800 MHz - RAM: 256 MiB - Flash: 128 MiB NAND (BCH-8) - Ethernet: 4x LAN + 1x WAN, gigabit (switch port 0 = WAN, 1-4 = LAN) - Wi-Fi: BCM4331 2.4 GHz (b43), BCM4360 5 GHz - USB: 1x USB 3.0, 1x USB 2.0 - LEDs: power (white/amber), WAN (white/amber), 2.4 GHz, 5 GHz, WPS, WiFi, USB 1, USB 2 - Buttons: WPS, WiFi (rfkill), Reset - Serial: 115200 8N1 on the SoC UART (ttyS0); the on-board header was not used for this port, netconsole served as the console - Power: 12 V DC, 2.5 A (barrel jack, included adapter) - Board ID: U12H332T00_NETGEAR MAC addresses (NVRAM): - LAN: et0macaddr - WAN: et1macaddr - 2.4 GHz: pci/1/1/macaddr - 5 GHz: pci/2/1/macaddr The LED and button GPIOs were mapped by driving each line by hand on a unit (egc112, GitHub review of the pull request). All LEDs are active low except the WPS and WiFi button LEDs, which are active high as on the R7000. The LEDs use the color/function bindings (white:power, amber:power, white:wan, amber:wan, white:wlan-2ghz, white:wlan-5ghz, white:wps, white:wlan, white:usb-1, white:usb-2); diag.sh, with the preceding commit, picks white:power as the status LED, so boot goes amber (bootloader), blinking white (preinit), solid white. egc112 re-tested the LEDs, buttons, board check and USB on a v1 and a v2. The 2.4 GHz LED is driven as a netdev trigger on phy0-ap0: b43 has no phy0tpt trigger and the phy0radio/assoc/tx/rx ones stay dark in AP mode. sysupgrade accepts only a CHK image with this board ID. The USB VBUS regulator is left off at registration, as on the sibling boards, so VBUS is power-cycled after CFE. Not yet supported: 5 GHz Wi-Fi (the BCM4360 AC-PHY needs the b43 AC-PHY series, a separate pull request). Installation from stock firmware: 1. Connect a computer to a LAN port and open http://192.168.1.1 (factory login admin / password). 2. ADVANCED > Administration > Router Update, select the factory image (openwrt-bcm53xx-generic-netgear_r6400-v1-squashfs.chk), Upload. 3. Wait for the router to restart into OpenWrt. Recovery: Netgear's bootloader accepts a firmware image over TFTP/NMRP (e.g. nmrpflash) when the image does not boot. Signed-off-by: Russell Ballestrini <russell@unturf.com> Link: https://github.com/openwrt/openwrt/pull/25786 Signed-off-by: Jonas Jelonek <jonas@jonasjelonek.de>