Differences

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

toh:netgear:wndr3400 [2013/03/24 15:54]
hauke
toh:netgear:wndr3400 [2014/07/21 00:53] (current)
bz files moved to the MIPS74k branch
Line 11: Line 11:
==== Hardware Highlights ==== ==== Hardware Highlights ====
-^ Version ^ CPU ^ Ram ^ Flash ^ Network ^ USB ^ Serial ^ JTag ^ FCC ^ +^ Version ^ CPU ^ Ram ^ Flash ^ Network ^ Switch ^ USB ^ Serial ^ JTag ^ FCC ^ 
-| V1 | Broadcom BCM4718  | 64MiB | 8MiB | 4 x 1 | Yes | Yes | ? | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=439394&fcc_id=PY309300116|here]] | +| V1 | Broadcom BCM4718  | 64MiB | 8MiB | 4 x 1 | BCM5325EKQMG  |Yes | Yes | ? | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=439394&fcc_id=PY309300116|here]] | 
-| V2 | Broadcom BCM5357 rev 2 @ 530 MHz  | 64MiB | 8MiB | 4 x 1 | Yes | Yes | ? | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=311124&fcc_id=PY311100155|here]] | +| V2 | Broadcom BCM5357 rev 2 @ 530 MHz  | 64MiB | 8MiB | 4 x 1 | |Yes | Yes | ? | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=311124&fcc_id=PY311100155|here]] | 
-| V3 |   | ? | ? | 4 x 1 | Yes | ? | ? | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=626496&fcc_id=PY312300210|confidential until 06/05/2013]] |+| V3 | Broadcom BCM5358 (all data taken from FCC) | 64MiB | ? | 4 x 1 | | Yes | ? | ? | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=626496&fcc_id=PY312300210|here]] |
| |
Line 36: Line 36:
  * Version 1 of this device is supported in trunk.   * Version 1 of this device is supported in trunk.
    * The precompiled image openwrt-wndr3400_v1-squashfs.chk can be uploaded in the original Web interface or via TFTP     * The precompiled image openwrt-wndr3400_v1-squashfs.chk can be uploaded in the original Web interface or via TFTP
 +    * Now should be the mips74k branch file:
 +            http://downloads.openwrt.org/snapshots/trunk/brcm47xx.mips74k/openwrt-wndr3400_v1-squashfs.chk
== Update the image == == Update the image ==
  * Version 1: Updating is done with the file named openwrt-brcm47xx-squashfs.trx .   * Version 1: Updating is done with the file named openwrt-brcm47xx-squashfs.trx .
 +  * Again, moved to:
 +          http://downloads.openwrt.org/snapshots/trunk/brcm47xx.mips74k/openwrt-brcm47xx-mips74k-squashfs.trx
== Wireless support == == Wireless support ==
Line 45: Line 49:
There are at least 4 different wireless drivers available: **b43** , **broadcom-wl** , **brcmsmac** and **brcmfmac**. There are at least 4 different wireless drivers available: **b43** , **broadcom-wl** , **brcmsmac** and **brcmfmac**.
-  * b43 : 2 wireless radios detected, both radios don't work (no scanning)+  * b43 : 2 wireless radios detected, both radios don't work (no scanning)(as of trunk r37307)
-  * broadcom-wl : 1 wireless radio detected ( 2.4GHz b/g speed only ), AP Mode works+  * broadcom-wl : 1 wireless radio detected ( 2.4GHz b/g speed only ), AP Mode works (as of trunk Feb-2013)
-  * brcmsmac: 2 wireless radios detected, both work with N speed, no AP (Master) mode yet, client only, P2P status unknown (ad-hoc networking)+  * brcmsmac: 2 wireless radios detected, both work with N speed, AP Mode on bgn radio[1], 802.11a+n client mode only, P2P status unknown (ad-hoc networking)(as of trunk r37307)
  * brcmfmac: unknown   * brcmfmac: unknown
-AP Mode for brcmsmac is WIP ([[http://marc.info/?l=linux-wireless&m=136060952425786&w=2 | linux-wireless ]] )+[1]AP Mode for brcmsmac is WIP ([[http://marc.info/?l=linux-wireless&m=136060952425786&w=2 | linux-wireless ]] ), AP mode has errors 
== Hardware tinkering == == Hardware tinkering ==
Line 64: Line 69:
Serial Headers aren't populated. Serial Headers aren't populated.
<code> <code>
-<--- to BCM5358U                  JP1+<--- to main chip                JP1
                    (  ) (Rx) (  )  (  )  (Tx)  ( GND )                     (  ) (Rx) (  )  (  )  (Tx)  ( GND )
</code> </code>
Line 78: Line 83:
  * Upload file via TFTP - example: tftp -4 -v -m binary 192.168.1.1 -c put WNDR3400-V1.0.0.50_20.0.59-OFW.chk   * Upload file via TFTP - example: tftp -4 -v -m binary 192.168.1.1 -c put WNDR3400-V1.0.0.50_20.0.59-OFW.chk
  * Wait until device reboots   * Wait until device reboots
 +
 +==== WNDR3400v1 Restore Netgear Factory Image ====
 +
 +  * Connect with serial console
 +  * Interrupt CFE Bootloader by pressing CTRL+C
 +  *prepare a TFTP client from 192.168.1.x to send the .CHK firmware to the router with IP 192.168.1.1
 +  * on router run "tftpd" command in CFE - starts TFTPD on router
 +
===== WNDR3400v2 ===== ===== WNDR3400v2 =====
Line 89: Line 102:
The unit has 3 buttons: 2 Back (Reset, Wireless), 1 Top (WPS "dome") The unit has 3 buttons: 2 Back (Reset, Wireless), 1 Top (WPS "dome")
 +WLAN support of BCM43236 : no full mac driver
 +<code>
 +[  16.880000] brcmfmac: brcmf_usb_fw_download: unsupported chip 43236 rev 2
 +</code>
== Serial console == == Serial console ==
Line 2053: Line 2070:
other working commands: nvram other working commands: nvram
 +
 +===== WNDR3400v3 =====
 +
 +According to FCC photos a BCM5358 CPU with a BCM43236KMLG radio.
 +
 +Like with the WNDR3400v2 support of the radio might be depending on the used chip revision.
 +There is no driver for BCM43236 rev1 + rev2 - see comment at [http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91453 linux-wireless] (May 2012)
 +
 +
 +===== Restore factory settings / bricked device =====
 +
 +If you damage some partitions with configuration data you might see the following
 +even if you have flashed the original firmware back to the device
 +
 +  * CFE bootloader with MAC 00:00:00:00:00:00
 +  * no settings matching the sticker on the unit
 +
 +To restore those settings Netgear provides several "burn-in" tools.
 +These tools write certain nvram data (nvram set/commit does not remember after reboots)
 +<code>
 +burn_hw_rev
 +burn5gpass
 +burn5gssid
 +burnboardid
 +burnethermac
 +burnpass
 +burnpin
 +burnrf
 +burnsku
 +burnsn
 +burnssid
 +</code>
===== Tags ===== ===== Tags =====

Back to top

toh/netgear/wndr3400.1364136866.txt.bz2 · Last modified: 2013/03/24 15:54 by hauke