Differences

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

toh:netgear:dg834gt [2012/10/08 16:30]
apbarrett Add some sub-sub-headings to the linux instructions.
toh:netgear:dg834gt [2014/01/18 18:27] (current)
dllud Corrected internal links.
Line 1: Line 1:
====== Netgear DG834GT ====== ====== Netgear DG834GT ======
-| {{:meta:icons:tango:48px-dialog-warning.svg.png?nolink&24x24}} | **WARNING:** Do not confuse the DG834**GT** with the [[oldwiki:openwrtdocs:hardware:netgear:DG834G]]! +| {{:meta:icons:tango:48px-dialog-warning.svg.png}} | **WARNING:** Do not confuse the DG834**GT** with the [[/toh/netgear/dg834.v4|DG834G V4]]!\\ Also note that the **Wifi** chip for this router is the **Atheros** AR2414 chip and //not// the Broadcom.
-Also note that the **Wifi** chip for this router is the **atheros** AR2414 chip and //not// the broadcom.+
===== Hardware Highlights ===== ===== Hardware Highlights =====
-^ CPU ^ Ram ^ Flash ^ LAN ^ USB ^ Serial ^ JTag ^ +^ SoC ^ Ram ^ Flash ^ LAN ^ USB ^ Serial ^ JTag ^ 
-|Broadcom BCM6348@255MHz | 16MiB | 4MiB | 4 x 1| USB 1.1 Host | Yes | Yes |+|Broadcom BCM6348@256MHz | 16MiB | 4MiB | 4 x 1| USB 1.1 Host | Yes | Yes |
===== Installation ===== ===== Installation =====
Line 12: Line 12:
The DG834GT became supported in  OpenWrt release 10.03 'Backfire'. The DG834GT became supported in  OpenWrt release 10.03 'Backfire'.
-The image needed to flash onto a Broadcom 63xx-series board depends on the board, method you are using to flash, and, for web-based flash, on the version of the Broadcom code your router uses. The board name is 96348GW-10 and it has CFE codeversion 3.02. However, the quickest way to get OpenWRT on the device is using a precompiled image - the image file will be named openwrt-DG834GT_DG834PN-squashfs-cfe.bin. Take a look in [[http://downloads.openwrt.org/backfire/10.03.1-rc5/brcm63xx/|Backfire 10.03.1-rc5]]+The image needed to flash onto a Broadcom 63xx-series board depends on the board, method you are using to flash, and, for web-based flash, on the version of the Broadcom code your router uses. The board name is 96348GW-10 and it has CFE codeversion 3.02. However, the quickest way to get OpenWRT on the device is using a precompiled image - the image file will be named openwrt-DG834GT_DG834PN-<file_system>-cfe.bin. Take a look in [[http://downloads.openwrt.org/backfire/10.03.1/brcm63xx/|Backfire 10.03.1]]
  * There is **NO** support for the ADSL modem currently!   * There is **NO** support for the ADSL modem currently!
-  * The image file does NOT have support for WiFi, so you'll have to add it with <code>opkg update</code> then <code>opkg install kmod-ath9k</code>+  * The image file does NOT have support for WiFi, so you'll have to add it with <code>opkg update</code> then <code> 
 +  opkg install kmod-ath 
 +  opkg install kmod-ath5k</code>
There are three known methods to install OpenWRT on the DG834GT: There are three known methods to install OpenWRT on the DG834GT:
Line 24: Line 26:
=== Create the image === === Create the image ===
-  - Download latest build image ( .bin ) from OpenWrt eg like [[http://downloads.openwrt.org/backfire/10.03.1-rc4/brcm63xx/]] then either openwrt-DG834GT_DG834PN-jffs2-128k-cfe.bin OR openwrt-DG834GT_DG834PN-jffs2-64k-cfe.bin OR openwrt-DG834GT_DG834PN-squashfs-cfe.bin +  - Download the build image (.bin) from OpenWrt, e.g.: [[http://downloads.openwrt.org/backfire/10.03.1/brcm63xx/openwrt-DG834GT_DG834PN-squashfs-cfe.bin|openwrt-DG834GT_DG834PN-squashfs-cfe.bin]] (recommended) OR [[http://downloads.openwrt.org/backfire/10.03.1/brcm63xx/openwrt-DG834GT_DG834PN-jffs2-128k-cfe.bin|openwrt-DG834GT_DG834PN-jffs2-128k-cfe.bin]] OR [[http://downloads.openwrt.org/backfire/10.03.1/brcm63xx/openwrt-DG834GT_DG834PN-jffs2-64k-cfe.bin|openwrt-DG834GT_DG834PN-jffs2-64k-cfe.bin]]. 
-  - Get whole directory named DG834GT_V1.02.16_NA_src from [[ftp://downloads.netgear.com/files/GPL/DG834GT_V1.02.16_NA_src.zip]] unzip all etc+  - Get [[ftp://downloads.netgear.com/files/GPL/DG834GT_V1.02.16_NA_src.zip]] and unzip the  directory DG834GT_V1.02.16_NA_src
-  - Get code for mkimage.sh file from post 424 on [[https://forum.openwrt.org/viewtopic.php?pid=89333#p89333]] and compile etc. and put mkimage.sh in DG834GT_V1.02.16_NA_src directory +  - In DG834GT_V1.02.16_NA_src directory create an empty file named mkimage.sh and insert the code from post 424 on [[https://forum.openwrt.org/viewtopic.php?pid=89333#p89333]]. 
-  - put the openwrt image ( .bin ) named say,openwrt-DG834GT_DG834PN-squashfs-cfe.bin, in the DG834GT_V1.02.16_NA_src directory +  - Put the OpenWrt image (.bin) in the DG834GT_V1.02.16_NA_src directory. 
-  - Execute something like &quot;./mkimage.sh DG834GT_V1.02.16.img openwrt-96348gw-10-squashfs-cfe.bin openwrt-DG834GT-2.6.27.11.img&quot; where first file is old netgear supplied image. second file is openwrt downloaded one and third file is whatever you wanna name the new image+  - In a terminal cd into DG834GT_V1.02.16_NA_src and execute something like &lt;code>;./mkimage.sh DG834GT_V1.02.16.img openwrt-96348gw-10-squashfs-cfe.bin openwrt-DG834GT-2.6.27.11.img&lt;/code> Where first file is the Netgear supplied image, second file is OpenWrt downloaded one and third file is whatever you want to name the new image.
-=== Install using NFTF ===+=== Install using NFTP ===
-  - Get code for patched nftp program from here [[http://forum.kitz.co.uk/index.php/topic,5842.msg148308.html#msg1483088]] then compile nftp to get a binary  +  - Get code for patched NFTP program from here [[http://forum.kitz.co.uk/index.php/topic,5842.msg148308.html#msg1483088]] then compile NFTP to get a binary. 
-  - Put the newly created image eg named "openwrt-DG834GT-2.6.27.11.img" in this example in the same folder as the binary nftp file +  - Put the newly created image e.g. named "openwrt-DG834GT-2.6.27.11.img" in this example in the same folder as the binary NFTP file. 
-  - Put router in flashing mode by pull out plug and press reset button then insert power until leds flash alternatively then execute something like &quot;sudo ./ntfp -u eth0 openwrt-DG834GT-2.6.27.11.img&quot; where the last file is the new image created by mkimage.sh file earlier on etc.  +  - Put router in flashing mode by pulling out the power plug, start pressing the reset button, inserting power and then keep pressing reset until LEDs flash alternatively. Then execute something like &lt;code>;sudo ./ntfp -u eth0 openwrt-DG834GT-2.6.27.11.img&lt;/code>; where the last file is the new image created by mkimage.sh file earlier on. 
-  - Reboot router again and say for like 3 times on and off by taking out plug to make sure it has initialized everything properly  +  - Power cycle the router around 3 times, making sure everything has initialized properly before going for the next cycle.
- +
-ENJOY !!! This took me 3 hours to figure out.+
=== Install using web interface === === Install using web interface ===
-  - For an easier upload method than messing around with nftp (constant fail for me, probably user error), once you have made the "openwrt-DG834GT-2.6.27.11.img" file, it can be uploaded thru the original web interface / flash upgrade router procedure. Wish I had known THAT 2 hours ago! +For an easier upload method than messing around with NFTP, once you have made the ''openwrt-DG834GT-2.6.27.11.img'' file, it can be uploaded through the original web interface / flash upgrade router procedure.
-  - I used the instructions above and loaded "Backfire (10.03.1-RC6, r28680)" (am posting this before going further)+
-NOTE : for users of a SKY DG834GT with the locked bootloader you still need to use NFTP to flash because the web interface will not work as the bootloader checks the image and it does not allow flashing. You still need to use NFTP and recovery mode to flash !+I used the instructions above and loaded Backfire 10.03.1 successfully.
-==== OEM installation on Windows using the Firmware recovery tool ====+NOTE: for users of a SKY DG834GT with the locked bootloader you still need to use NFTP to flash because the web interface will not work. The bootloader checks the image and it does not allow flashing. 
 + 
 +==== OEM installation on Windows using the Firmware Recovery Tool ====
On Windows you can use Netgear's supplied firmware recovery tool, but you need to make some alterations to the image file before it will be acceptable to the tool. You need to prepend the second stage bootloader to the image, then pad the image out to make it a multiple of 1024 bytes, and then ensure that the Netgear model and version information is present. On Windows you can use Netgear's supplied firmware recovery tool, but you need to make some alterations to the image file before it will be acceptable to the tool. You need to prepend the second stage bootloader to the image, then pad the image out to make it a multiple of 1024 bytes, and then ensure that the Netgear model and version information is present.
The first few parts of this are done based around the instructions found in [[https://forum.openwrt.org/viewtopic.php?pid=144111#p144111|this forum post]]. Roughly speaking the steps you'll need to follow are: The first few parts of this are done based around the instructions found in [[https://forum.openwrt.org/viewtopic.php?pid=144111#p144111|this forum post]]. Roughly speaking the steps you'll need to follow are:
-  * Start with an official firmware, and extract the first 65536 bytes. // head -c 65536 <netgear-firmware.img> > 2bl.bin // +  - Start with an official firmware, and extract the first 65536 bytes. // head -c 65536 <netgear-firmware.img> > 2bl.bin // 
-  * Figure out how much padding is needed to make the file length a multiple of 1024 bytes. // dd if=/dev/zero of=padding.bin bs=<bytesneeded> count=1// +  - Figure out how much padding is needed to make the file length a multiple of 1024 bytes. // dd if=/dev/zero of=padding.bin bs=<bytesneeded> count=1// 
-  * Prepend the extracted data to the beginning of the openwrt firmware and append the padding to the end. // cat 2bl.bin openwrt.bin padding.bin >file_to_flash.img // +  - Prepend the extracted data to the beginning of the openwrt firmware and append the padding to the end. // cat 2bl.bin openwrt.bin padding.bin >file_to_flash.img // 
-  * Use the [[http://www.ph-mb.com/downloads/brcm_firmware_tool/Broadcom_Firmware_Tool_v1.0_Beta1_standalone.rar|Broadcom Firmware Tool]] found from [[http://www.skyuser.co.uk/forum/technical-discussion/32854-firmware-image-editing-tool-dg834gt-sagem-f-st-broadcom-based-routers.html#post235918|SkyUser Forum]] to add the Netgear information to the firmware file. This is done by loading the firmware image (file_to_flash.img) into the tool, selecting the Netgear/Sercomm tab, then adding "DG834GT" as the target platform and a version number as the "version ID". You can then "Save As", ensuring the file is saved as a "Netgear Firmware Image" rather than the default Broadcom Firmware Image". +  - Use the [[http://www.ph-mb.com/downloads/brcm_firmware_tool/Broadcom_Firmware_Tool_v1.0_Beta1_standalone.rar|Broadcom Firmware Tool]] found from [[http://www.skyuser.co.uk/forum/technical-discussion/32854-firmware-image-editing-tool-dg834gt-sagem-f-st-broadcom-based-routers.html#post235918|SkyUser Forum]] to add the Netgear information to the firmware file. This is done by loading the firmware image (file_to_flash.img) into the tool, selecting the Netgear/Sercomm tab, then adding "DG834GT" as the target platform and a version number as the "version ID". You can then "Save As", ensuring the file is saved as a "Netgear Firmware Image" rather than the default Broadcom Firmware Image". 
-  * Boot the DG834GT into recovery mode by holding the reset button down whilst powering it up. The power and status lights should flash alternately. +  - Boot the DG834GT into recovery mode by holding the reset button down whilst powering it up. The power and status lights should flash alternately. 
-  * Ensure the new firmware file is in the same directory as the Netgear Firmware Recovery Tool (remove the existing firmware file to avoid confusion). +  - Ensure the new firmware file is in the same directory as the Netgear Firmware Recovery Tool (remove the existing firmware file to avoid confusion). 
-  * Use the Recovery Tool to flash the firmware on a 32bit Windows system. +  - Use the Recovery Tool to flash the firmware on a 32bit Windows system.
-If you are working on Windows, this author would strongly suggest having unix tools at your disposal to make life a little easier. This could be as simple as [[http://sourceforge.net/projects/unxutils/|UnxUtils]] or as complex as [[http://www.cygwin.com/|Cygwin]]. Note that if you're using UnxUtils, you can't point dd at /dev/zero. Instead, point it at a real file, on the understanding that first few bytes (up to 1023) of the real file will turn up at the end of the image.+If you are working on Windows, this author would strongly suggest having UNIX tools at your disposal to make life a little easier. This could be as simple as [[http://sourceforge.net/projects/unxutils/|UnxUtils]] or as complex as [[http://www.cygwin.com/|Cygwin]]. Note that if you're using UnxUtils, you can't point dd at /dev/zero. Instead, point it at a real file, on the understanding that first few bytes (up to 1023) of the real file will turn up at the end of the image.
If you don't get the padding right, then the Firmware Recovery Tool will hang at 99%, and the power and status lights will flash quickly. Don't panic - the chances are that the firmware has flashed ok, but you'll need to power cycle the router. If you don't get the padding right, then the Firmware Recovery Tool will hang at 99%, and the power and status lights will flash quickly. Don't panic - the chances are that the firmware has flashed ok, but you'll need to power cycle the router.
Line 68: Line 69:
| {{:meta:icons:tango:48px-dialog-warning.svg.png?nolink&24x24}} | **WARNING:** Some DG834GT devices appear to have problems with the bootloader and serial port. This may make the device's serial port effectively inaccessible! | | {{:meta:icons:tango:48px-dialog-warning.svg.png?nolink&24x24}} | **WARNING:** Some DG834GT devices appear to have problems with the bootloader and serial port. This may make the device's serial port effectively inaccessible! |
-The second method needs access to the device serial port. You will need a level shifter to connect an RS232 port, or alternatively you may be able to use one of the older USB to mobile phone serial connection cable, or even something like the BusPirate. The DG834GT operates at 3.3V, so whatever you use must be able to interface at this voltage. The UART connection is a row of four pads below the WiFi card connector, see below for pinout. You will need to solder either pins or wires to the pads.  +The second method needs access to the device serial port. You will need a level shifter to connect an RS232 port, or alternatively you may be able to use one of the older USB to mobile phone serial connection cable, or even something like the BusPirate. The DG834GT operates at 3.3V, so whatever you use must be able to interface at this voltage. The UART connection is a row of four pads below the WiFi card connector, see below for pinout. You will need to solder either pins or wires to the pads. 
-  * Connect to the serial port on the DG834GT with the power off on the device. +  - Connect to the serial port on the DG834GT with the power off on the device. 
-  * Set your PC to have a static IP address in the 192.168.1.xxx/24 range. +  - Set your PC to have a static IP address in the 192.168.1.xxx/24 range. 
-  * Start a TFTP server on your PC, and put the OpenWrt firmware file in it's root directory. (E.G. openwrt-DG834GT_DG834PN-squashfs-cfe.bin) +  - Start a TFTP server on your PC, and put the OpenWrt firmware file in it's root directory. (E.G. openwrt-DG834GT_DG834PN-squashfs-cfe.bin) 
-  * Ensure you have your terminal software set to 115200 baud, 8N1. +  - Ensure you have your terminal software set to 115200 baud, 8N1. 
-  * Power the DG834GT up, and quickly hit any key on your terminal. +  - Power the DG834GT up, and quickly hit any key on your terminal. 
-  * This should get you the CFE> prompt. If you just got random rubbish on the screen, you have a DG834GT that has problems with the serial port and bootloader. You may have to try using NFTP or the Netgear Firmware Recovery tool instead. +  - This should get you the CFE> prompt. If you just got random rubbish on the screen, you have a DG834GT that has problems with the serial port and bootloader. You may have to try using NFTP or the Netgear Firmware Recovery tool instead. 
-  * In the serial terminal, type <code>flashimage [your_pc_ip_address]:openwrt-DG834GT_DG834PN-squashfs-cfe.bin</code>+  - In the serial terminal, type <code>flashimage [your_pc_ip_address]:openwrt-DG834GT_DG834PN-squashfs-cfe.bin</code>
 +==== Enjoy OpenWrt ====
 +After the flashing has finished your router reboots. Wait for about two minutes until OpenWrt has booted, get a static IP address in ''192.168.1.xxx/24'' range and then connect to the router at ''192.168.1.1'' via telnet. This is the default address for a fresh OpenWrt installation.  Set the password with ''passwd'' and log out using ''exit''. Telnet will not work anymore from this point on, but SSH will.
 +
 +Beside SSH you can now access the web interface on ''http://192.168.1.1'' to complete basic configuration of your new router.
 +
 +==== WiFi ====
 +
 +The OpenWrt image file does NOT have support for WiFi, so you'll have to install the necessary kernel modules. To do so the router needs internet access, which you can get in two ways:
 +  * Connect the router to a wired network (easiest). Most probably you will have to [[toh:netgear:dg834gt#assigning.a.wan.port.with.dhcp|assign a port from the switch to WAN and use DHCP]] to get a valid IP address.
 +  * If there is only a wireless network available you can [[toh:netgear:dg834gt#using.a.gnu/linux.pc.to.forward.internet|use a GNU/Linux PC with two network interfaces (wireless and ethernet) to forward internet]] to the DG834GT.
 + 
 +=== Assigning a WAN port with DHCP ===
 +
 +The OpenWrt image has a static IP address (''192.168.1.1'') which may not be in the subnet of the network the DG834GT is plugged into. To circumvent this you can use the VLAN functionality to separate one of the switch ports for usage as WAN port with DHCP. To do so replace the ''/etc/config/network'' with the following:
 +<code>
 +config 'switch' 'eth1'
 + option 'enable' '1'
 + option 'enable_vlan' '1'
 + option 'reset' '1'
 +
 +config 'switch_vlan' 'vlan0'
 + option 'vlan' '0'
 + option 'device' 'eth1'
 + option 'ports' '1 2 3 5*'
 +
 +config 'switch_vlan' 'vlan1'
 + option 'vlan' '1'
 + option 'device' 'eth1'
 + option 'ports' '0 5t'
 +
 +config 'interface' 'loopback'
 + option 'ifname' 'lo'
 + option 'proto' 'static'
 + option 'ipaddr' '127.0.0.1'
 + option 'netmask' '255.0.0.0'
 +
 +config 'interface' 'lan'
 + option 'type' 'bridge'
 + option 'ifname' 'eth1.0'
 + option 'proto' 'static'
 + option 'ipaddr' '192.168.1.1'
 + option 'netmask' '255.255.255.0'
 + option 'nat' '1'
 + option 'mtu' '1500'
 +
 +config 'interface' 'wan'
 + option 'ifname' 'eth1.1'
 + option 'mtu' '1492'
 + option 'proto' 'dhcp'
 +</code>
 +This [[http://www.hwupgrade.it/forum/showpost.php?p=34766046&postcount=130|configuration by misteroX]] separates port number 4 of the switch to be used as a WAN interface. It will try to automatically get an IP address using DHCP.
 +
 +Connect the router to your wired network using port 4 and use one of the remaining ports to connect to your PC. Reboot the router and use ''ifconfig'' to check if you have an IP assigned for ''eth1.1''. If so you can proceed to [[toh:netgear:dg834gt#installing.the.driver|Installing the driver]].
 +
 +=== Using a GNU/Linux PC to forward internet ===
 +
 +During the Installation of the wireless driver the device self-reboots. This works around that. The following assumes that you have left the default IP address on the DG834GT.
 +
 +On the GNU/Linux PC configure the ethernet controller to the DG834GT with a static IP so you can telnet then SSH to it.
 +<code>
 +sudo ifconfig eth0 192.168.1.3 netmask 255.255.255.0
 +</code>
 +
 +== Configure DG834GT to use PC as internet provider ==
 +
 +Modify ''/etc/config/network'' so the gateway is the laptop. Add the following gateway line to the ''config interface lan'' section.
 +<code>
 +config interface lan
 + option type    bridge
 + option ifname  eth1
 + option gateway  192.168.1.3
 +</code>
 +
 +Add to the ''System;Startup;Local Startup'' post boot script (via web interface) so it appends an external nameserver to resolve.conf. Alternatively you could edit ''/etc/rc.local''. ''8.8.8.8'' is a valid name server. 
 +<code>
 +echo search lan > /etc/resolv.conf
 +echo nameserver 8.8.8.8 >> /etc/resolv.conf
 +exit 0
 +</code>
 +
 +== PC forwarding ==
 +
 +Configure the GNU/Linux PC to forward traffic from the ethernet to the internet with the following script. Tailor the interfaces to your environment.
 +<code>
 +#!/bin/bash
 +#assumes PC eth0 is connected to DG834GT and will have IP 192.168.1.3
 +#allow the netgear to get info from the inet via this laptop.
 +
 +function verbose
 +{
 +    echo $*
 +    $*
 +}
 +
 +echo 1 > /proc/sys/net/ipv4/ip_forward
 +
 +IP=192.168.1.3
 +#internal
 +INT=eth0
 +EXT=wlan0
 +
 +#setup static IP on interface to the netgear
 +verbose ifconfig eth0 $IP netmask 255.255.255.0
 +
 +#set up routing
 +verbose iptables -t nat -A POSTROUTING -o $EXT -j MASQUERADE
 +#allow router to connect out and remote servers to respond
 +verbose iptables -A FORWARD -i $INT -o $EXT -j ACCEPT
 +verbose iptables -A FORWARD -i $EXT -o $INT -m state    --state RELATED,ESTABLISHED -j ACCEPT
 +exit
 +</code>
 +
 +== PC looses internet ==
 +Occasionally the PC may loose the internet. It might prioritize routing traffic through the DG834GT rather than the interface to the internet. In the following replace 10.0.2.1 with your router's IP.
 +<code>
 +sudo route del default
 +sudo route add default gw 10.0.2.1
 +</code>
 +
 +=== Installing the driver ===
 +
 +At the shell:
 +<code>
 +opkg update
 +opkg install kmod-ath
 +opkg install kmod-ath5k
 +</code>
 +The DG834GT can appear to hang, as the files being downloaded and configured are large.  Downloading the dependencies separately is unnecessary, but gives more feedback. Note that the device may reboot between drivers.
 +
 +After the installation has finished edit ''/etc/config/wireless'' and comment out or delete the line:
 +<code>
 +option disabled 1
 +</code>
 +
 +Enter command ''wifi''. You should now see a wireless network with SSID "OpenWrt" (if you did not change the default settings). The web interface will now have ''Network;Wifi'' available.
 +
 +If you used the internet forwarding method with a PC undo the changes to ''/etc/config/network'' and ''System;Startup;Local Startup''.
===== Hardware ===== ===== Hardware =====
==== Info ==== ==== Info ====
- +| **[[wp>Instruction set|Architecture]]:**   | [[wp>MIPS architecture|MIPS]] big endian | 
-| **Architecture:** MIPS big endian|  +| **Vendor:**         | [[wp>Broadcom]]
-| **Vendor:** Broadcom |  +| **[[doc:techref:Bootloader]]:**     | [[doc:techref:bootloader:CFE|CFE]]
-| **Bootloader:** CFE |  +| **Board Id:**      | 96348GW-10 | 
-| **System-On-Chip:** Broadcom 6348KPBG |  +| **[[doc:hardware:soc|System-On-Chip]]:** | BCM6348KPBG
-| **CPU Speed:** 255 Mhz |  +| **[[doc:hardware:cpu|CPU]]/Speed**       | BMIPS3300 V0.7 / 256 MHz
-| **Flash-Chip:** MX 29LV320BTC-70G |  +| **Flash-Chip:**     | MX 29LV320BTC-70G | 
-| **Flash size:** 4 MiB |  +| **Flash size:**     | 4 MiB | 
-| **RAM:** IC42S32400 16 MiB or W9812G2DH-7 16 MiB both (1Mx4x32bit) |  +| **RAM:**             | IC42S32400\\ W9812G2DH-7
-| **Wireless:** Atheros AR2414 MiniPCI (802.11bg) |  +| **RAM size:**            | 16 MiB (1Mx4x32bit) | 
-| **Ethernet:** BCM5325EKQMG +| **Wireless:**       | Atheros AR2414 MiniPCI (802.11bg) | 
-| **USB:** Yes USB 1.1 unpopulated |  +| **Ethernet:**       | BCM5325 w/ vlan support [[doc:techref:swconfig]] | 
-| **Serial:** [[:inbox#Serial|Yes]] |  +| **Internet:**        | ADSL2+ 
-| **JTAG:** [[:inbox#JTAG|Yes]] |+| **USB:**             | Yes USB 1.1 unpopulated
 +| **[[doc:hardware:port.serial|Serial]]:** | [[#Serial|Yes]] | 
 +| **[[doc:hardware:port.jtag|JTAG]]:**     | [[#JTAG|Yes]] |
==== Serial ==== ==== Serial ====
Line 206: Line 346:
^GPIO ^ BGA pad ^connected ^ ^GPIO ^ BGA pad ^connected ^
-|GPIO_0| AB5 |_ | +|GPIO_0| AB5 |_ (Power LED)
-|GPIO_1| AC5 |LED 2| +|GPIO_1| AC5 |LED 2 (Orange Tick LED)
-|GPIO_2| AD1 |connected| +|GPIO_2| AD1 |connected (Orange ADSL LED)
-|GPIO_3| AD2 |LED 4| +|GPIO_3| AD2 |LED 4 (Wireless LED)
-|GPIO_4| AD4 |connected| +|GPIO_4| AD4 |connected reset
-|GPIO_5| AD3 |LED 3| +|GPIO_5| AD3 |LED 3 (Hidden LED)
-|GPIO_6| AE3 |connected reset+|GPIO_6| AE3 |connected | 
-|GPIO_7| AD5 |connected via left from the R514 label|+|GPIO_7| AD5 |connected via left from the R514 label (Green ADSL LED)|
|GPIO_8| AE5 |connected| |GPIO_8| AE5 |connected|
|GPIO_9| AE4 |connected| |GPIO_9| AE4 |connected|

Back to top

toh/netgear/dg834gt.1349706649.txt.bz2 · Last modified: 2012/10/08 16:30 by apbarrett