You are here: OpenWrt Wiki » Table of Hardware » Netgear » Netgear WNDR3700 and WNDR37AV

Differences

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

--- toh:netgear:wndr3700 [2012/07/29 10:52]
orca
+++ toh:netgear:wndr3700 [2013/05/03 19:19] (current)
rab attitude adjustment fix for stupid US wireless restriction
@@ Line 3: / Line 3: @@
 ====== Netgear WNDR3700 and WNDR37AV ======
-Netgear has sold a number of these units in boxes marked WNDR37AV.  This was done for marketing purposes solely, the hardware is exactly identical (even to the point of many users finding a router physically labeled "WNDR3700 or WNDR3700v2" inside of a box labeled "WNDR37AV").
+===== Device Info and Specifics =====
-===== Supported Versions =====
+**NOTE:** Netgear has sold a number of these units in boxes marked WNDR37AV.  This was done for marketing purposes solely, the hardware is exactly identical (even to the point of many users finding a router physically labeled "WNDR3700 or WNDR3700v2" inside of a box labeled "WNDR37AV").
+==== Hardware Highlights ====
+^ Version ^ CPU ^ Ram ^ Flash ^ Network ^ USB ^ Serial ^ JTag ^ FCC ^
+| V1 | Atheros AR7161 rev 2 680 MHz | 64MiB | 8MiB | 4 x 1 | Yes | Yes | Yes | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=278475&fcc_id='PY308300092'|here]] |
+| V2 | Atheros AR7161 rev 2 680 MHz | 64MiB | 16MiB | 4 x 1 | Yes | Yes | Yes | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=290558&fcc_id='PY308300092'|here]] |
+| V3 | Broadcom BCM4718A1  | 64MiB | 8MiB | 4 x 1 | Yes | ? | ? | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=651807&fcc_id=%27PY311200166%27|here]] |
+| V4 | Atheros AR9344 @ 560 MHz | 128MiB | 128MiB | 4x1 | Yes | Yes | Yes | [[https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=847398&fcc_id=%27PY312100186%27|here]] |
+==== Supported Versions ====
 ^ Version/Model ^ Launchdate ^ S/N ^ OpenWrt Version Supported ^ Model Specific Notes ^
 | v1 |         |  | Backfire | aka WNDR37AV-100PES, WNDR3700-100PES  |
-| v2 | 2011-01 |  | Backfire 10.03.1 | Box side panel lists WNDR3700**v2**, aka WNDRMAC-100PES  |
+| v2 | 2011-01 |  | Backfire 10.03.1 | Box side panel lists WNDR3700**v2**, aka WNDRMAC-100PES, WNDR3700-100prs  |
-|  -  | 2011-03 |  | Backfire 10.03.1  | the [[toh:netgear:WNDR3800]] is the actual successor board  |
+| wndr3800 | 2011-03 |  | Backfire 10.03.1  | the [[toh:netgear:WNDR3800]] is the actual successor board  |
 | v3 | 2011-09? |  | ? | WNDR3700**v3** is based on a Broadcom chip, so **completely different architecture than v1 or v2** |
+| V4 | ? | | WIP? | WNDR3700**v4** is again Atheros-based, now AR9344 with 128MiB RAM and 128MiB NAND flash. Same PCB as [[toh:netgear:WNDR4300]], but only 2T2R. [[https://forum.openwrt.org/viewtopic.php?id=41094|OpenWrt Forum thread]] |
 If you want to know what version you have after installing OpenWrt you can run <code>dmesg | grep m25p80</code> and then take a look in the hardware table (ver1 has 8 MiB , ver2 has 16 MiB).
@@ Line 22: / Line 32: @@
 **NOTE:** There are rumors that a certain batch of version 1 routers have problems with the 2.4GHz radio suddenly dying. The ones came in boxes marked as -01R14 or -01R15 on the barcode label. It is also said that -01R21 or -02R01 are expected to be working o.k. According to "board verion" Ver4 is said to be reliable. If you look at the pictures you may see at least 3 places with some kind of "version" numbering.  See [[http://spreadsheets.google.com/pub?key=0AjNDNODfzgytdEJvZ0N0SkFLejFJZzBHcnFaaUg4OGc&hl=en&output=html]].
+Added Notice:
+A thread on netgears forum telling how to see firmware and version of a router.
+http://forum1.netgear.com/showthread.php?t=63234
-===== Hardware Highlights =====
+===== Basic Operation =====
-^ Version ^ CPU ^ Ram ^ Flash ^ Network ^ USB ^ Serial ^ JTag ^ FCC ^
-| V1 | Atheros AR7161 rev 2 680 MHz | 64MiB |  8MiB | 4 x 1 | Yes | Yes | Yes | [[https://fjallfoss.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=278475&fcc_id='PY308300092'|here]] |
-| V2 | Atheros AR7161 rev 2 680 MHz | 64MiB | 16MiB | 4 x 1 | Yes | Yes | Yes | [[https://fjallfoss.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=290558&fcc_id='PY308300092'|here]] |
-| V3 | Broadcom BCM4718A1  | 64MiB | 8MiB | 4 x 1 | Yes | ? | ? | [[https://fjallfoss.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=651807&fcc_id=%27PY311200166%27|here]] |
-===== Installation =====
+==== Installation ====
-Please consult ->[[doc:howto:generic.flashing|Installing OpenWrt (generic)]] and additionally read on here for WNDR3700 specifics:
+=== Support for the different versions of WNDR3700 ===
-  * Version 1 of this device is supported in Backfire 10.03 and above. Manually building OpenWrt is not required. Quickest way is to download a precompiled [[http://downloads.openwrt.org/backfire/10.03/ar71xx/|stable image]], look for wndr3700 factory (SquashFS is recommended):
+  * Version 1 of this device is supported in Backfire 10.03 and above (Attitude Adjustment and trunk). Manually building OpenWrt is not required. Quickest way is to download a precompiled [[http://downloads.openwrt.org/backfire/10.03.1/ar71xx/|stable image]], look for wndr3700 factory (SquashFS is recommended):
-    * openwrt-ar71xx-wndr3700-squashfs-factory.img       06-Apr-2010 2424965
+    * openwrt-ar71xx-wndr3700-squashfs-factory.img
-    * openwrt-ar71xx-wndr3700-jffs2-factory.img          06-Apr-2010 3211397
+    * openwrt-ar71xx-wndr3700-jffs2-factory.img
-  * Version 2 is supported by 10.03.1 (released as of 2011-12-21):
+  * Version 2 is supported since 10.03.1:
     * [[http://downloads.openwrt.org/backfire/10.03.1/ar71xx/]]
   * Version 3 is not yet supported by OpenWrt.
-  * Alternative is a precompiled image from the trunk (bleeding edge): [[http://downloads.openwrt.org/snapshots/trunk/ar71xx/]].
+  * [[WNDR3800]] is supported since 10.03.1.
-  * To create your own firmware, see this HowTo here: [[doc:howtobuild:build.wndr3700]].
+  * There are separate images for wndr3700, wndr3700v2 and wndr3800 (due to the firmware having to be tagged a different way). The wndr3700v2 will reject the version 1 images.
-  * There are separate images for wndr3700 and wndr3700v2 (due to the firmware having to be tagged a different way).  The wndr3700v2 will reject the version 1 images. The version 2 images are available starting from Backfire 10.03.1-RC5.
+=== Where to get firmware? ===
+  * You can get generic OpenWRT firmware of the [[about:history#stable.releases|stable branch]] from the [[http://downloads.openwrt.org/|official repository]]. This firmware covers most basic needs of an average user.
+  * Alternative is a precompiled image from the [[about:history#bleeding.edge.trunk|trunk (bleeding edge) branch]]: [[http://downloads.openwrt.org/snapshots/trunk/ar71xx/]].
+  * An easy way to get a custom firmware with extended functionality is to use a [[toh:netgear:wndr3700#pre-built.customized.firmware|pre-built customized firmware]] based on either [[about:history#bleeding.edge.trunk|trunk]] or [[about:history#stable.releases|stable]] branch.
+  * To create your own customized firmware, see this HowTo here: [[doc:howtobuild:build.wndr3700]].
 :!: Developers recommend the SquashFS versions! Read about differences here: [[doc:techref:filesystems]]. And if you are interested, you can read about the differences between img and bin here: .
-==== Flash Layout ====
+=== How to flash the firmware to device? ===
-->[[doc:techref:flash.layout]]
+Please consult ->[[doc:howto:generic.flashing|Installing OpenWrt (generic)]] and additionally read on here for WNDR3700 specifics.
+There are two different images available for the wndr3700 series:
+  * **sysupgrade.bin** images are meant for flashing from an existing Openwrt system, either by using LuCI and the sysupgrade script.
+  * **factory.img** images are otherwise identical, but a short header has been added to the image enabling the original Netgear OEM firmware and the TFTP recovery mode to accept the images.
-==== OEM easy installation ====
+== OEM easy installation ==
-FIXME
-To install simply use stock WNDR3700 GUI to upload and install OpenWrt. Non North American users will get an warning regarding that OpenWrt identifies itself an NA, don't worry. You can just simple ignore this.
+To install simply use the stock WNDR3700 GUI to upload and install OpenWrt. Remember to use a **factory.img** image. Non North American users will get an warning regarding that OpenWrt identifies itself an NA, don't worry. You can just simple ignore this.
 [[https://forum.openwrt.org/viewtopic.php?id=24993|Netgear WNDR3700 - OpenWrt New User(s)]]
-==== OEM installation using the TFTP method ====
+== OEM installation using the TFTP method (recommended) ==
 Hold the 'System Restore' button on the underside of the router while powering it on, and hold the button until the power led blinks **green**. Then, upload the .img firmware as described in [[doc/howto/generic.flashing.tftp|Installing OpenWrt via TFTP]] (see the section titled Bootloader contains TFTP server). However, note that the router will not accept the firmware when the filename is too long! Using firmware.img as filename should work.  After upload, the power led is turned off and flashing starts, after that is finished the router will restart and the power led will eventually become stable green (it will be stable orange for quite some time first).
-==== OEM installation via serial console and TFTP ====
+== OEM installation via serial console and TFTP ==
-  * Connect via serial console
+  * Connect via serial console (also accounts for [[wndr3700#usb.serial.console|USB Serial Console]])
   * Interrupt U-Boot by pressing any key
   * You may need to enable writes to the flash by issuing "protect off all"
@@ Line 74: / Line 92: @@
 </code>
-==== Upgrading OpenWrt ====
+=== Upgrading OpenWrt ===
 ->[[doc:howto:generic.sysupgrade]]
-===== Basic configuration =====
+==== Basic configuration ====
 ->[[doc:howto:basic.config|Basic configuration]].
-==== Enabling wireless ====
+=== Enabling wireless ===
+**NOTE:** For information on possible wireless regulatory issues, please refer to [[toh:netgear:wndr3700#Wireless Regulatory Issues?|this section]].
 At least the Backfire 10.03 image (openwrt-ar71xx-wndr3700-squashfs-factory.img 06-Apr-2010 2424965) does not have working wireless out of the box as some kernel modules are missing for the wireless chipset, however this is easy to remedy.  SSH to your router (you will first need to telnet in and set a password, as described in [[doc/howto/firstlogin|First Login]], and then run the following commands (assumes the router has Internet access):
@@ Line 91: / Line 110: @@
 Now, restart the router.
-==== Wireless Regulatory Issues? ====
+===== Advanced Operation =====
-Unless you are American, BOTH 2.4GHz and 5GHz will likely not be fully available on OpenWrt 10.03 Backfire (you will experience loss of channels 12, 13 and 14 if these are available where you are, as well as potentially incorrect 5GHz channel availability. Power output levels may be incorrect for your country as well).
-To sum up the background for this:
+==== Pre-built Customized firmware ====
+Besides generic OpenWRT firmware distribution, there are customized builds based on it and managed by individuals in the community.
-  * Netgear ships the WNDR3700 with [[wp>EEPROM]] chip stating that the router should restrict to US settings. Outside America, they ship software that ignores this chip. This is a bad thing as it means that your OpenWrt can't work properly for the next two reasons.
+[[https://forum.openwrt.org/viewforum.php?id=16|Announcements and updates]] can be found on the OpenWRT users forum.
-  * In the USA, it is illegal to ship router firmware that can (through incorrect settings) bypass radio regulations.
-  * Atheros (the wireless chip maker in the WNDR3700) asks open source folks not to ship compiled builds that bypass radio restrictions, even though their hardware vendors do this. This means if you bought hardware from one of the manufacturers (and you're one of the 95% of the world's population that doesn't live in the USA) that doesn't set the value in the EEPROM correctly, you're kinda screwed if you want to use OpenWrt...
-Personally, I think this is a ridiculous situation, but there seem to be issues with fixing it. You can do the job yourself as follows:
+Typically, these builds are intended to extend functionality and/or to improve performance of the firmware, as well as provide the end-user with a preconfigured setup.
-You may partially fix this by compiling a custom image with CONFIG_ATH_USER_REGD set in the Ath9k driver. This will, however, take a significant time to compile and result in a restriction to 20dBm max power output across all channels (this is apparently due to a bug according to my reading, but it's not fixed yet as far as I can tell). A much better option that will allow you to use the full legal power output in your country would be to follow the instructions here:
+**Warning**: As custom builds are mostly based on the [[about:history#bleeding.edge.trunk|trunk (bleeding edge) branch]], they are much more prone to bugs and regressions.
-http://smorgasbord.gavagai.nl/2010/09/wifi-regulatory-compliance-and-how-to-fix-it/
+In order to address this, some members also release builds based on the [[about:history#stable.releases|stable branch]], thus reducing the potential of regressions, yet providing the advantages of customization (check out the link to hnyman's build below).
-They're a little complex, so I've uploaded my fixed regulatory.bin to RapidShare to save you all the hassle of learning to compile one yourself. Hopefully someone will move it somewhere more permanent and update this. Anyhow, this is me doing my bit to make this whole process better and usable for more people...what you need to do is as follows:
+Specifically for WNDR3700, these are the longer maintained and the more frequently updated builds (as of September, 24 / 2012):
-  - If you're living in the USA, congratulations. You don't need to do any of this as you live in the only country anyone seems to care about making things easy for.
-  - Set up your router so that it is able to access the internet or the later step involving wget will fail (unless you host the file on your local network).
-  - Enter the following:
-<code>
+[[https://forum.openwrt.org/viewtopic.php?id=27722|Fully featured OpenWrt build for the WNDR3700]] (managed by arokh; trunk-only builds)
-cd /etc/config
-vi wireless
-</code>;
-Add the following to each radio for your router (this will prevent you exceeding the regulatory limits in your country when you do the next bits):
+[[https://forum.openwrt.org/viewtopic.php?id=28392|IPv6 oriented Openwrt build for WNDR3700]] (managed by hnyman; trunk and stable builds)
-|''option 'country' 'XX'
-''|
-(Where XX is the two letter country code for your country. For example, Australia is AU).
-(if those are ISO 2 letter country codes, a list is available here: http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 If not, then someone please clarify what codes are those.)
-. Download the following file: https://rapidshare.com/files/458836427/regulatory.bin. Put it on a web server (sorry I can't give you a direct link, or you'd be able to do without this step (RapidShare doesn't allow direct downloads without looking at their page, so don't try to skip putting it on a web server or server on your network - hopefully someone can improve this process using their private server as the file's only tiny)).
-NEW: Instead of your own webserver, you can also use http://datatomb.de/mirror/stuff/regulatory.bin
-Enter the following:
-<;code>
-cd /usr/lib/crda/
-rm regulatory.bin
-wget <web server URL>/regulatory.bin
-reboot
-</code>
-. When your router comes up again, log in with SSH as you did before. Check the available channels and power outputs are as desired by entering:
-<code>
-iw list
-</code>
-. If you want to see what settings I put in the regulatory DB (they're as per the article I linked at the beginning) you can get them here: https://rapidshare.com/files/458836748/db.txt . If for some reason you want to use this to set the proper regulatory settings for the USA, you need to use UX as the country code...otherwise all country codes are still correct.
+==== Flash Layout ====
+->[[doc:techref:flash.layout]]
-===== Specific Configuration =====
+==== Specific Configuration ====
-==== Interfaces ====
+=== Interfaces ===
 The default network configuration is:
 ^ Interface Name ^ Description ^ Default configuration ^
@@ Line 156: / Line 142: @@
 | wlan1 | WiFi | Disabled |
-==== Switch Ports (for VLANs) ====
+=== Switch Ports (for VLANs) ===
 Numbers 0-3 are Ports 4 to 1 as labeled on the unit, 5 is the internal connection to the router itself. Don't be fooled: Port 1 on the unit is number 3 when configuring VLANs. vlan0 = eth0.0, vlan1 = eth0.1 and so on.
 ^ Port ^ Switch port ^
@@ Line 231: / Line 217: @@
-==== Switch LED configuration ====
+=== Switch LED configuration ===
 The switch on wndr3700 supports following led groups:
   * Group 1: green leds for all ports on the switch
@@ Line 263: / Line 249: @@
 <code>swconfig dev rtl8366s set blinkrate 2</code>
-Note: The default LED config built into Backfire 10.03.1-rc4 (and earlier) does not match the explanation printed on the router's bottom. To make the LED behaviour match the printed explanation (green LED for 1000Mb/s), use mode 6 for port 1, mode 9 for port 2 and mode 2 for port 5. This has later been patched to trunk and Backfire branch. You can either use the swconfig command or directly edit the file '/etc/config/network'. Reference: https://dev.openwrt.org/ticket/8103
+Note: The default LED config built into Backfire 10.03.1-rc4 (and earlier) does not match the explanation printed on the router's bottom. To make the LED behaviour match the printed explanation (green LED for 1000Mb/s), use mode 6 for port 1, mode 9 for port 2 and mode 2 for port 5. This has later been patched to [[about:history#bleeding.edge.trunk|trunk (bleeding edge)]] and Backfire branch. You can either use the swconfig command or directly edit the file '/etc/config/network'. Reference: https://dev.openwrt.org/ticket/8103
-==== Activate USB LED in Backfire ====
+=== Activate USB LED in Backfire ===
 Install the package 'kmod-leds-wndr3700-usb'.
@@ Line 299: / Line 285: @@
 Note: Reference to original info: https://forum.openwrt.org/viewtopic.php?pid=105502#p105502
-===== Hardware Buttons =====
+==== Hardware Buttons ====
 ->[[doc:howto:hardware.buttons]]
-==== Monitor button actions ====
+=== Monitor button actions ===
-WNDR3700 buttons have currently (r25360) different names in Backfire and in trunk:
+WNDR3700 buttons have currently (r25360) different names in Backfire and in [[about:history#bleeding.edge.trunk|trunk]] :
 ^          ^ Reset ^ WPS   ^ WiFi  ^
 ^ Backfire | BTN_0 | BTN_1 | BTN_2 |
 ^ Trunk    | reset | wps   | BTN_2 |
-==== Activate the buttons ====
+=== Activate the buttons ===
-=== WiFi button ===
+== WiFi button ==
 The button automatics is done with the ''wifitoggle'' package. It only requires hotplugging the button event to the '/sbin/wifi' script.
@@ Line 330: / Line 316: @@
 </code>
-=== WPS button ===
+== WPS button ==
 There is support for the WPS button removing the ''wpad-mini'' package and installing the full version of ''wpad'' & ''hostapd-utils'' packages.
+FIXME Apparently changeset 33393 enables WPS support also for wpad-mini, but that is still unverified.  //hnyman 14-09-2012//
 If you have a WPS enabled network device (like a modern USB dongle), you can negotiate joining the routers wireless network without manually entering SSID & passkey. You just initiate "WPS authentication" by pushing the similar WPS button on the device (or launching the process by its driver/control software). After the device has initiated the authentication process, you can accept the transaction by using the WPS button on WNDR3700. The connection should then get negotiated, and in most cases in future your PC should remember the received network settings from then on.
@@ Line 364: / Line 352: @@
 </code> If everything goes ok, you should see in Syslog not only the button events, but also succesful WPS authentication.
-=== Reset button ===
+== Reset button ==
 If you just want a straightforward simple reset button functionality, you can install the ''restorefactory'' package and configure it:
@@ Line 380: / Line 368: @@
 After you reset to the factory defaults you have to reinstall and reconfigure the ''restorefactory'' package. You can skip this step if you build your own image which contains a preconfigured ''restorefactory'' configuration.
 ==== USB serial console ====
@@ Line 387: / Line 376: @@
 ''miniterm -b9600 -d/dev/ttyS0''
-===== Hardware =====
+===== Hardware Modding =====
-==== Info ====
+==== Hardware Specifics ====
+=== Info ===
 | **[[wp>Instruction set|Architecture]]:**    | [[wp>MIPS architecture|MIPS]] |
 | **Vendor:**          | [[wp>Qualcomm Atheros]]  |
 | **[[doc:techref:Bootloader]]:**     | crippled [[doc:techref:bootloader:uboot|U-Boot]] |
-| **[[doc:hardware:soc|System-On-Chip]]:**  | AR7161  |
+| **[[doc:hardware:soc|System-On-Chip]]:**  | [[http://www.qca.qualcomm.com/networking/brand.php?brand=4&product=68|AR7161 ]] |
-| **[[doc:hardware:cpu|CPU]]/Speed**        | 24Kc V7.4 680 MHz  |
+| **[[doc:hardware:cpu|CPU]]/Speed**        | [[http://www.mips.com/products/processor-cores/mips32-24k/|MIPS32 24Kc]] V7.4 680 MHz   (([[http://www.mips.com/secure-download/index.dot?product_name=/auth/MD00346%2D2B%2D24K%2DDTS%2D04.00.pdf|Datasheet specific to the 24Kc CPU core (free registration required)]])) |
 | **Flash-Chip:**  | v1: [[http://www.spansion.com/Support/Datasheets/S25FL064P_00_03_e.pdf|Spansion S25FL064P (FL064PIF)]] or [[http://www.macronix.com/QuickPlace/hq/PageLibrary4825740B00298A3B.nsf/$defaultview/3F21BAC2E121E17848257639003A3146/$File/MX25L6405D%2C%203V%2C%2064Mb%2C%20v1.5.pdf?OpenElement|Macronix MX25L6405DMI-12G]], v2: [[http://www.macronix.com/QuickPlace/hq/PageLibrary4825740B00298A3B.nsf/$defaultview/3F21BAC2E121E17848257639003A3146/$File/MX25L12845E%2C%203V%2C%20128Mb%2C%20v1.7.pdf|Macronix MX25L12845EWI-10G]] |
 | **Flash size:**      | v1 has 8192 KiB, v2 has 16384 KiB |
@@ Line 404: / Line 396: @@
 | **Serial:**          | [[#Serial|Yes]]   |
 | **JTAG:**            | [[#JTAG|Yes]]  |
+| **Voltage Reg:**     | [[#VReg|Yes]]  |
-==== Photos ====
+=== Photos ===
 {{:toh:netgear:s_wndr3700c.jpg?700|}}
 {{:toh:netgear:s_wndr3700s.jpg?700|}}
-==== Opening the case ====
+=== Opening the case ===
 **Note:** This will void your warranty!
@@ Line 416: / Line 410: @@
   *There are four more screws under the rubber feet. The feet are not glued to the plastic and can easily be removed and pushed back into place once reassembled. The feet have rubber tethers, but you can slide them out gently without damaging them, and later you can reinsert them just as easily. Don't forget to put them in a plastic baggie so you don't lose them!
-==== Serial ====
+=== Serial ===
 Internal J1 4-pin connector
@@ Line 431: / Line 425: @@
 COM port settings: Speed:115200, Data bits:8, Stop bits:1, Parity:none, Flow control:none
-==== JTAG ====
+=== JTAG ===
 Internal J3 connector
@@ Line 446: / Line 440: @@
 See [[doc:hardware:port.jtag]] for more JTAG details.
+=== VReg ===
+Onboard Voltage Regulator is a STMicroelectronics ST1S10 which is described by ST as a
-===== Recovery flash in failsafe mode =====
+A, 900 kHz, monolithic synchronous step-down regulator IC
-If you happen to brick your router, do not fear. You can use TFTP file transfer to flash the router with a new firmware.
+Full details of the onboard ST1S10 Voltage Regulator are here
-You need:
+http://www.st.com/stonline/stappl/st/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/DATASHEET/CD00169322.pdf
-  * A TFTP client for your computer. There are both command-line tools and GUI versions available.
-  * Your computer must have an IP address from the 192.168.1.x network, as the router failsafe mode defaults to 192.168.1.1.
-  * A new firmware to flash in. Either an original Netgear firmware or an Openwrt "factory.img" firmware. "Sysupgrade" version will not work.
-  * Access to router's reset button
-Steps needed in the flashing process:
+There are three total ST1S10 chips near the capacitors on the upper right of the board.
-  - configure and connect PC
-  - power on the router
-  - press and hold the RESET button as soon as the switch LEDs light up.
-  - keep holding RESET until the power LED begins to flash orange and then green.
-  - once the power LED is flashing green, release RESET
-  - start the TFTP transfer to router at 192.168.1.1.
-  - wait a few minutes for the router to complete flash. It should reboot automatically.
-Please note that the TFTP transfer is quick, as the file is stored in RAM. However, **the flashing process itself will take several minutes**, after which the router should reboot automatically. Be patient -- it will eventually come up as a brand new factory-fresh router with NETGEAR firmware (or Openwrt if you used the Openwrt 'factory' firmware version for debricking).
+{{:toh:netgear:wndr3700-4.jpg?700|}}
-Original source: https://forum.openwrt.org/viewtopic.php?pid=103295#p103295
-**Alternative advice**
-Forum user **ole.h** previously posted a method for unbricking the router easily with a TFTP client. Further to his post, if you use the factory reset button method, you don't need to worry about building a serial cable, trying to tap into any crazy boot timing sequence, or do anything else particularly tricky. It is simple and the following step-by-step process (cribbed from the ole.h's earlier notes, as well as from http://cyberstorm.altervista.org/wag354g/guides/howto_unbricking_wag354g_en.txt) will get you going. This assumes that you have a copy of the stock NETGEAR firmware in the current directory.
-  - Configure your ethernet connection (on the client machine you're using to configure the WNDR3700) using a static IP as 192.168.1.2, netmask 255.255.255.0. (The WNDR3700 in factory reset mode is going to come up as 192.168.1.1.)
-  - Connect your computer to one of the LAN (not WAN) ports on the router.
-  - Start a continuous ping from your client computer to 192.168.1.1 (Linux and Mac OS ping will continue until stopped by default; Windows ping by default sends 4 pings and then stops, so use "ping -t" under Windows); probably nothing will answer these pings yet, but you can use the output to tell you when the router is ready in the next couple steps.
-  - Power the router off.
-  - Hold down the factory reset button on the bottom of the case. Now turn the router back on while continuing to hold the factory reset button...
-  - Wait until the router is listening on 192.168.1.1 (this takes 45-60 seconds; to confirm, you can ping 192.168.1.1, and see if it responds; it's best to start a sequence of ping requests above, before your hands get busy with the factory reset button).
-  - Release the factory reset button. (If you happen to have a serial cable connected, you'll see that the system is in firmware recovery mode and that it will be waiting for you to upload firmware. But you don't need the serial cable at all.)
-  - Run a tftp CLIENT on your computer (enter no hostname on the command line) and enter the following:<code bash>
-verbose
-trace
-rexmt 1
-binary
-connect 192.168.1.1
-put WNDR3700-V1.0.4.35NA.img (or whatever the filename is that you are trying to flash)
-</code>
-Once done, the router will flash itself to the stock NETGEAR firmware file that you provided and reboot automatically.
-===== Serial cables (optional) =====
+==== Serial cables (optional) ====
-==== Construction ====
+=== Construction ===
 If you have a basic familiarity with RS232 signals and putting together basic electronic components, you should be able to follow these instructions to create a cable to attach to the WNDR3700's serial port.
@@ Line 524: / Line 486: @@
-==== U-Boot Mods ====
+=== Flashing over serial ===
-According to the release notes in the NETGEAR-supplied GPL firmware, U-Boot can be upgraded using the following procedure. Note that you do not need to update U-Boot in order to install OpenWrt. Additionally, this has not yet been tested by the author of this wiki page, and you can permanently brick your router (with little hope of recovery, other than possibly finding a JTAG interface) if your U-boot image becomes corrupted:
-<code>
-Please burn u-boot-wndr3700-dni6-V1.7.bin
-Set up a tftp server on your PC, its ip address is 192.168.1.12.
-Entering into boot loader
-ag7100> set serverip 192.168.1.12
-ag7100> tftp 0x80010000 u-boot-wndr3700-dni6-V1.7.bin
-ag7100> erase 0xbf000000 +0x70000
-ag7100> cp.b 0x80010000 0xbf000000 0x50000
-ag7100> reset
-Entering into boot loader again
-ag7100>bootm
-Then the device should be in tftp recovery mode. Please run the command
-"tftp -i 192.168.1.1 put WNDR3700U-V1.0.4.49.img" on MS-DOS of your PC.
-</code>
-==== Flashing over serial ====
 If, for whatever reason, you would prefer to avoid tftp flashing, it's possible to load a new image with ymodem (//loady//) or kermit (//loadb//).  It's a good idea to use //iminfo// to verify the image's checksum before copying it to flash with //cp.b//.  Remember to use the sysupgrade .bin file even if this is your initial flash from the factory firmware; the extra header in the factory .img is NOT required when flashing from U-Boot.
@@ Line 575: / Line 519: @@
 Note that the size value (0x004d0004 in this case) will vary from one image to another.  Don't omit the "+" in the erase command as it's part of the command's syntax.
-===== Hardware Mods =====
+==== U-Boot Mods ====
-==== 128 MiB RAM Mod ====
+According to the release notes in the NETGEAR-supplied GPL firmware, U-Boot can be upgraded using the following procedure. Note that you do not need to update U-Boot in order to install OpenWrt. Additionally, this has not yet been tested by the author of this wiki page, and you can permanently brick your router (with little hope of recovery, other than possibly finding a JTAG interface) if your U-boot image becomes corrupted:
+<code>
+Please burn u-boot-wndr3700-dni6-V1.7.bin
+Set up a tftp server on your PC, its ip address is 192.168.1.12.
+Entering into boot loader
+ag7100> set serverip 192.168.1.12
+ag7100> tftp 0x80010000 u-boot-wndr3700-dni6-V1.7.bin
+ag7100> erase 0xbf000000 +0x70000
+ag7100> cp.b 0x80010000 0xbf000000 0x50000
+ag7100> reset
+Entering into boot loader again
+ag7100>bootm
+Then the device should be in tftp recovery mode. Please run the command
+"tftp -i 192.168.1.1 put WNDR3700U-V1.0.4.49.img" on MS-DOS of your PC.
+</code>
+==== Hardware Mods ====
+=== 128 MiB RAM Mod ===
 **NEW: More and More people reports serious issues after correctly replace ram chips on WNDR3700V2. For now users are advised to stay away from extending RAM on WNDR 3700V2 untill we will have positive feedback on this procedure.**
@@ Line 600: / Line 564: @@
 |infineon|HYB25D512160BE|
 |Micron|MT46V32M16TG|
-|Micron|MT46V32M16TGЗ|
+|Micron|MT46V32M16TG?|
 |Elixir|N2DS51216BT-5T|
 |Elixir|N2DS51216CS-5T|
@@ Line 610: / Line 574: @@
 **U-Boot report after adding memory**\\
+<code>
 ''U-Boot 1.1.4DNI1.6 (May 22 2009 - 16:37:44)
@@ Line 629: / Line 594: @@
 Out:   serial
 Err:   serial
-Net:   ag7100_enet_initialize...''
+Net:   ag7100_enet_initialize...
 ''
-----
+</code>
+=== Antenna Mod ===
+The procedure below covers hardware revision 1. Revision 2 only has U.FL connectors for the 5 GHz antennas (PJ2 and PJ4), while the 2.4 GHz connectors are replaced with dummy connectors (presumably a Hirose testing connectors used in production). So for revision 2 the PJ5 and PJ6 connectors will have to bypassed and the coax cable soldered directly to the PCB.
-==== Antenna Mod ====
+You will need:
-Need 4 U.FL connector, 4 cable UFL-F/RPSMA-F 13 centimeters long, 4 Antenna Level One (OAN-0501).
+  * 4 cable U.FL-F (female) to RPSMA-F (female) app. 13 centimeters long
+  * 4 Antenna (preferably 2 2.4 GHz and 2 5 GHz antenna), e.g. Level One (OAN-0501).
 On board removes:
@@ Line 662: / Line 632: @@
 {{:toh:netgear:img_1205.jpg?243x162|Netgear WNDR3700 v1 Antenn Mod}}
 {{:toh:netgear:img_1209.jpg?243x162|Netgear WNDR3700 v1 Antenn Mod}}
+===== Troubleshooting and Recovery =====
+==== Wireless Regulatory Issues? ====
+Unless you are American, BOTH 2.4GHz and 5GHz will likely not be fully available on OpenWrt 10.03 Backfire (you will experience loss of channels 12, 13 and 14 if these are available where you are, as well as potentially incorrect 5GHz channel availability. Power output levels may be incorrect for your country as well).
+To sum up the background for this:
+  * Netgear ships the WNDR3700 with [[wp>EEPROM]] chip stating that the router should restrict to US settings. Outside America, they ship software that ignores this chip. This is a bad thing as it means that your OpenWrt can't work properly for the next two reasons.
+  * In the USA, it is illegal to ship router firmware that can (through incorrect settings) bypass radio regulations.
+  * Atheros (the wireless chip maker in the WNDR3700) asks open source folks not to ship compiled builds that bypass radio restrictions, even though their hardware vendors do this. This means if you bought hardware from one of the manufacturers (and you're one of the 95% of the world's population that doesn't live in the USA) that doesn't set the value in the EEPROM correctly, you're kinda screwed if you want to use OpenWrt...
+Personally, I think this is a ridiculous situation, but there seem to be issues with fixing it. You can do the job yourself as follows:
+=== Backfire ===
+You may partially fix this by compiling a custom image with CONFIG_ATH_USER_REGD set in the Ath9k driver. This will, however, take a significant time to compile and result in a restriction to 20dBm max power output across all channels (this is apparently due to a bug according to my reading, but it's not fixed yet as far as I can tell). A much better option that will allow you to use the full legal power output in your country would be to follow the instructions here:
+http://smorgasbord.gavagai.nl/2010/09/wifi-regulatory-compliance-and-how-to-fix-it/
+They're a little complex, so I've uploaded my fixed regulatory.bin to RapidShare to save you all the hassle of learning to compile one yourself. Hopefully someone will move it somewhere more permanent and update this. Anyhow, this is me doing my bit to make this whole process better and usable for more people...what you need to do is as follows:
+  - If you're living in the USA, congratulations. You don't need to do any of this as you live in the only country anyone seems to care about making things easy for.
+  - Set up your router so that it is able to access the internet or the later step involving wget will fail (unless you host the file on your local network).
+  - Enter the following:
+<code>
+cd /etc/config
+vi wireless
+</code>
+Add the following to each radio for your router (this will prevent you exceeding the regulatory limits in your country when you do the next bits):
+|''option 'country' 'XX'
+''|
+(Where XX is the two letter country code for your country. For example, Australia is AU).
+(if those are ISO 2 letter country codes, a list is available here: http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 If not, then someone please clarify what codes are those.)
+. Download the following file: https://rapidshare.com/files/458836427/regulatory.bin. Put it on a web server (sorry I can't give you a direct link, or you'd be able to do without this step (RapidShare doesn't allow direct downloads without looking at their page, so don't try to skip putting it on a web server or server on your network - hopefully someone can improve this process using their private server as the file's only tiny)).
+NEW: Instead of your own webserver, you can also use http://datatomb.de/mirror/stuff/regulatory.bin
+Enter the following:
+<code>
+cd /usr/lib/crda/
+rm regulatory.bin
+wget <web server URL>/regulatory.bin
+reboot
+</code>
+. When your router comes up again, log in with SSH as you did before. Check the available channels and power outputs are as desired by entering:
+<code>
+iw list
+</code>
+. If you want to see what settings I put in the regulatory DB (they're as per the article I linked at the beginning) you can get them here: https://rapidshare.com/files/458836748/db.txt . If for some reason you want to use this to set the proper regulatory settings for the USA, you need to use UX as the country code...otherwise all country codes are still correct.
+=== Attitude Adjustment ===
+SSH to the router and run the following:
+<code>
+cd /tmp/
+wget http://luci.subsignal.org/~jow/reghack/reghack.elf
+chmod +x reghack.elf
+cp /lib/modules/*/ath.ko .
+cp /lib/modules/*/cfg80211.ko .
+./reghack.elf ath.ko
+./reghack.elf cfg80211.ko
+mv *.ko /lib/modules/*/
+reboot
+</code>
+==== Recovery flash in failsafe mode ====
+If you happen to brick your router, do not fear. You can use TFTP file transfer to flash the router with a new firmware. Note that this TFTP recovery mode is separate from Openwrt's own "[[doc:howto:generic.failsafe|failsafe mode]]" and is offered by the original u-boot boot manager by Netgear, so it should be enabled with either an original Netgear firmware, a working Openwrt firmware or a bricked Openwrt firmware.
+Note:  WNDR3700 may also automatically enter the TFTP recovery mode, if you have flashed a bad firmware image. That is indicated by the power led blinking slowly and steadily, much slower that during a normal Openwrt boot.
+For TFTP recovery you need:
+  * A TFTP client for your computer. There are both command-line tools and GUI versions available.
+  * Your computer must have an IP address from the 192.168.1.x network, as the router failsafe mode defaults to 192.168.1.1. You might need to manually config the address, as some operating systems change the IP to a link-local 196.254.x.x address after a while if there is no DHCP server.
+  * A new firmware to flash in. Either an original Netgear firmware or an Openwrt "factory.img" firmware. "Sysupgrade" version will not work.
+  * Access to router's reset button
+Steps needed in the flashing process:
+  - configure and connect PC
+  - power on the router
+  - press and hold the RESET button as soon as the switch LEDs light up.
+  - keep holding RESET until the power LED begins to flash orange and then green.
+  - once the power LED is flashing green, release RESET
+  - start the TFTP transfer to router at 192.168.1.1.
+  - wait a few minutes for the router to complete flash. It should reboot automatically.
+Please note that the TFTP transfer is quick, as the file is stored in RAM. However, **the flashing process itself will take several minutes**, after which the router should reboot automatically. Be patient -- it will eventually come up as a brand new factory-fresh router with NETGEAR firmware (or Openwrt if you used the Openwrt 'factory' firmware version for debricking).
+Original source: https://forum.openwrt.org/viewtopic.php?pid=103295#p103295
+**Alternative advice**
+Forum user **ole.h** previously posted a method for unbricking the router easily with a TFTP client. Further to his post, if you use the factory reset button method, you don't need to worry about building a serial cable, trying to tap into any crazy boot timing sequence, or do anything else particularly tricky. It is simple and the following step-by-step process (cribbed from the ole.h's earlier notes, as well as from http://cyberstorm.altervista.org/wag354g/guides/howto_unbricking_wag354g_en.txt) will get you going. This assumes that you have a copy of the stock NETGEAR firmware in the current directory.
+  - Configure your ethernet connection (on the client machine you're using to configure the WNDR3700) using a static IP as 192.168.1.2, netmask 255.255.255.0. (The WNDR3700 in factory reset mode is going to come up as 192.168.1.1.)
+  - Connect your computer to one of the LAN (not WAN) ports on the router.
+  - Start a continuous ping from your client computer to 192.168.1.1 (Linux and Mac OS ping will continue until stopped by default; Windows ping by default sends 4 pings and then stops, so use "ping -t" under Windows); probably nothing will answer these pings yet, but you can use the output to tell you when the router is ready in the next couple steps.
+  - Power the router off.
+  - Hold down the factory reset button on the bottom of the case. Now turn the router back on while continuing to hold the factory reset button...
+  - Wait until the router is listening on 192.168.1.1 (this takes 45-60 seconds; to confirm, you can ping 192.168.1.1, and see if it responds; it's best to start a sequence of ping requests above, before your hands get busy with the factory reset button).
+  - Release the factory reset button. (If you happen to have a serial cable connected, you'll see that the system is in firmware recovery mode and that it will be waiting for you to upload firmware. But you don't need the serial cable at all.)
+  - Run a tftp CLIENT on your computer (enter no hostname on the command line) and enter the following:<code bash>
+verbose
+trace
+rexmt 1
+binary
+connect 192.168.1.1
+put WNDR3700-V1.0.4.35NA.img (or whatever the filename is that you are trying to flash)
+</code>
+Once done, the router will flash itself to the stock NETGEAR firmware file that you provided and reboot automatically.
+==== Entering Openwrt failsafe mode ====
+Openwrt offers a generic [[doc:howto:generic.failsafe|failsafe mode]], which can be launched during a few seconds early in the boot process. With WNDR3700 the correct moment is **when the power LED changes from steady orange to blinking green**. If you at that moment **press any button** (WPS, Wifi or reset) during the next two seconds, you enter the failsafe mode, in which you can access the console with telnet. Successful entrance to the failsafe mode is indicated by a rapidly blinking power LED.
+WNDR3700 provides the failsafe waiting moment indication messages both to the serial console and to the network, just like described in the [[doc:howto:generic.failsafe|failsafe mode]] article.
 ----
 ===== Tags =====
 [[meta:tags]]
 {{tag>GigabitEthernet 5Port 2PHY USB 1USB JTAG 802.11abgn 802.11abgn_simultan ath9k 4Ant DetachableAntenna 64RAM 16Flash MIPS MIPS32 24Kc}}

toh/netgear/wndr3700.1343551954.txt.bz2 · Last modified: 2012/07/29 10:52 by orca

OpenWrt

Wiki Search

Actions

Donate

Translations

Differences