Netgear WNR2000V2

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 00:06, 24 January 2020 (edit)
Jeremywh7 (Talk | contribs)
m (Bad Flash Recovery - typo)
← Previous diff
Current revision (02:40, 6 January 2024) (edit) (undo)
Kernel-panic69 (Talk | contribs)
m (Upgrade Flash - (add note about 54652 working))
 
(10 intermediate revisions not shown.)
Line 1: Line 1:
-[[Image:WNR2000-product.jpg | right | 200px]]+[[Image:WNR2000-product.jpg | right | 350px]]
=Hardware= =Hardware=
-===[http://en.techinfodepot.shoutwiki.com/wiki/Netgear_WNR2000v2 Specifications]===+==[http://en.techinfodepot.shoutwiki.com/wiki/Netgear_WNR2000v2 Specifications]==
{| border="1" cellspacing="0" {| border="1" cellspacing="0"
|- |-
Line 33: Line 33:
|} |}
-===MTD Partitions===+==MTD Partitions==
From a `dmesg` output: From a `dmesg` output:
-=====[https://www.dd-wrt.com/phpBB2/viewtopic.php?p=444262#444262 CFE log]=====+===[https://www.dd-wrt.com/phpBB2/viewtopic.php?p=444262#444262 CFE log]===
CFE for WNR2000v2 version: v1.0.18 CFE for WNR2000v2 version: v1.0.18
Build Date: Wed Sep 9 14:33:22 CST 2009 Build Date: Wed Sep 9 14:33:22 CST 2009
Line 51: Line 51:
0x003f0000-0x00400000 : "nvram" 0x003f0000-0x00400000 : "nvram"
-=====[http://www.linksysinfo.org/index.php?threads/wnr2000v2-file-is-too-big-to-fit-in-mtd-not-wrong-file.71257/#post-260485 Running DD-WRT]=====+===[http://www.linksysinfo.org/index.php?threads/wnr2000v2-file-is-too-big-to-fit-in-mtd-not-wrong-file.71257/#post-260485 Running DD-WRT]===
Creating 5 MTD partitions on "sflash": Creating 5 MTD partitions on "sflash":
0x00000000-0x00040000 : "cfe" 0x00000000-0x00040000 : "cfe"
Line 59: Line 59:
0x00390000-0x003e0000 : "ddwrt" 0x00390000-0x003e0000 : "ddwrt"
-=Flash Size=+==Flash Size==
DD-WRT replaces the ''linux'' partition and adds ''ddwrt'', but '''''board_data'' and ''nvram'' must be preserved.''' DD-WRT replaces the ''linux'' partition and adds ''ddwrt'', but '''''board_data'' and ''nvram'' must be preserved.'''
*Thus the size limit is: 0x3E0000-0x40000='''3712 KB''' *Thus the size limit is: 0x3E0000-0x40000='''3712 KB'''
*The CFE vmlinuz loader times out when loading linux, so full build size may not be achievable. *The CFE vmlinuz loader times out when loading linux, so full build size may not be achievable.
-===Initial Flash Instructions===+=Initial Flash Instructions=
'''THESE INSTRUCTIONS ARE FOR THE [https://wikidevi.com/wiki/Netgear_WNR2000v2 VERSION 2] MODEL ONLY!''' For V3 see [[Netgear_WNR2000V3|HERE]]. '''THESE INSTRUCTIONS ARE FOR THE [https://wikidevi.com/wiki/Netgear_WNR2000v2 VERSION 2] MODEL ONLY!''' For V3 see [[Netgear_WNR2000V3|HERE]].
*Also: V1, V4, and V5 are [[Known_incompatible_devices#List_of_Incompatible_Devices|incompatible devices]] without u-boot mods (search the forums). *Also: V1, V4, and V5 are [[Known_incompatible_devices#List_of_Incompatible_Devices|incompatible devices]] without u-boot mods (search the forums).
Line 70: Line 70:
#Read the [[Firmware_FAQ|Firmware FAQ]] and [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=51486 Peacock announcement] #Read the [[Firmware_FAQ|Firmware FAQ]] and [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=51486 Peacock announcement]
#Find build links [[Firmware_FAQ#Where_do_I_download_firmware.3F|here]]. #Find build links [[Firmware_FAQ#Where_do_I_download_firmware.3F|here]].
-#A known good initial flash trailed build is 15962: [ftp://ftp.dd-wrt.com/betas/2010/12-24-10-r15962/broadcom_K26/dd-wrt.v24-15962_NEWD-2_K2.6_mini-WNR2000v2.chk ''K2.6_mini-WNR2000v2.chk''] in the ''broadcom_K26'' directory.+#A known good initial flash trailed build is 15962: [https://ftp.dd-wrt.com/betas/2010/12-24-10-r15962/broadcom_K26/dd-wrt.v24-15962_NEWD-2_K2.6_mini-WNR2000v2.chk ''K2.6_mini-WNR2000v2.chk''] in the ''broadcom_K26'' directory.
-#*All trailed builds tested from 21061 and newer fail initial flash+#*All trailed builds tested from 21061 and newer fail initial flash.
-#*The broadcom_K3X build directory may list the WNR2000v2, but it '''is too big to flash'''!+#*[https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1295467#1257781 There may be exceptions depending on user experience or procedure used].
 +#*'''<span style="color:#ffffff; background:#ff0000">&nbsp;**WARNING**:&nbsp;</span>'''The broadcom_K3X build directory may list the WNR2000v2, but it '''is too big to flash'''!
#Push the reset button on the back of the router until the lights flash (or 30s), then release. #Push the reset button on the back of the router until the lights flash (or 30s), then release.
#Attach an Ethernet cable to a router LAN port, and disable wireless on the computer. #Attach an Ethernet cable to a router LAN port, and disable wireless on the computer.
Line 86: Line 87:
#*Remember to change the browser IP address if it was changed in the router configuration #*Remember to change the browser IP address if it was changed in the router configuration
-===Upgrade Flash===+=Upgrade Flash=
Flash a K2.6_mini.bin file ('''not nv60k, nv64k, nor trailed builds''') via GUI or CLI: [[Installation]] Flash a K2.6_mini.bin file ('''not nv60k, nv64k, nor trailed builds''') via GUI or CLI: [[Installation]]
-*40723 is the last build that will flash, and test build r40733 is the first to fail (tested through 41418)+*Builds ''after'' 40723 fail to flash through at least 41418 (test build r40733 is the first to fail)
 +**NOTE: The reset button code was broken in 40571 and fixed in build 40750.
 +*Build 42602 flashed from GUI, but required a power off and on
 +*Build 50218 (test build) is the last working (through 06-06-2023-r52894 so far)
 +*Build [https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1295467#1257781 54652 is the newest working as of Jan 05 2024].
=Overclocking= =Overclocking=
-'''Attempt at your own risk''' - it is recommended to add a heatsink and/or improve cooling.<br>+'''Attempt at your own risk''' - it is recommended to add a heatsink to the BCM4716 and/or improve cooling.<br>
The BCM4716 uses the pll20mhz_table from [http://svn.dd-wrt.com/browser/src/linux/brcm/linux-2.6.23/brcm/shared/hndmips.c hndmips.c], and the CFE allows overclocking. The BCM4716 uses the pll20mhz_table from [http://svn.dd-wrt.com/browser/src/linux/brcm/linux-2.6.23/brcm/shared/hndmips.c hndmips.c], and the CFE allows overclocking.
-*Use the GUI, or (for more options) set clkfreq based on the pll20mhz_table's ''{cpu,ddr,axi}'' settings.+*Use the GUI (if possible), or for more options set clkfreq based on the pll20mhz_table's ''{cpu,ddr,axi}'' settings.
-*If manually setting, also set the nvram "overclocking" parameter to the ''{cpu}'' speed (or DD will reset it):+*If manually setting, the nvram "overclocking" parameter must also be set to the ''{cpu}'' speed (or DD will revert it):
nvram set clkfreq=''{cpu,ddr,axi}'' nvram set clkfreq=''{cpu,ddr,axi}''
nvram set overclocking=''{cpu}'' nvram set overclocking=''{cpu}''
nvram commit && reboot nvram commit && reboot
*The Samsung K4H561638''?''-LCCC RAM (where ''?'' is 'J' or 'N') is DDR400 CL3: 200 MHz 'ddr' speed from hndmips.c. *The Samsung K4H561638''?''-LCCC RAM (where ''?'' is 'J' or 'N') is DDR400 CL3: 200 MHz 'ddr' speed from hndmips.c.
-*In one test, an overclock at 400,200,100 without a heatsink produced a max SoC surface temperature of only 53.8degC (128degF) after several speedtest runs. Eventually, 373,186,93 was selected and stable with ''overclocking=373''.+*Depending on long-term stability, 400,200,100, 373,186,93 or 353,176,88 are good options (with ''overclocking'' set appropriately).
=Bad Flash Recovery= =Bad Flash Recovery=
-This defaults to boot_wait=0, and the CFE for this model has fewer commands available than typical. Avoid using `nvram erase` if the TFTP is not working, as this can make things worse. There are three options for [[Serial_Recovery#Break_CFE_Boot|serial recovery]] with TFTP:+This defaults to boot_wait=0, and the CFE for this model has fewer commands available than typical. Avoid using `nvram erase` if the TFTP is not working, as this can make things worse. There are three options for [[Serial_Recovery#Break_CFE_Boot|serial recovery]] with TFTP (see [[Serial_port_pinouts#Netgear_WNR2000_v2.2Fv3|pinouts]]):
flash : flash1.trx flash : flash1.trx
*This replaces the `-ctheader` option, to flash trailed builds (OEM or ''mini-WNR2000v2.chk''). *This replaces the `-ctheader` option, to flash trailed builds (OEM or ''mini-WNR2000v2.chk'').
flash -noheader : flash1.trx flash -noheader : flash1.trx
*This works for a bad DD-WRT flash with non-trailed builds so long as `nvram erase` is not used. *This works for a bad DD-WRT flash with non-trailed builds so long as `nvram erase` is not used.
- tftpd [running this will put the CFE into a wait state to receive a file via TFTP]+ tftpd
-*This is the only to recover to OEM firmware, if nothing else works.+*This puts the CFE into a wait state to receive a file via TFTP. It is the only way to recover to OEM firmware, if nothing else works.
If normal TFTP does not work and serial is unavailable, recovering a brick (e.g. from flashing an oversize image) is possible via pin-short to enter TFTP mode. '''This is not without risk!''' Read [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=81013 this thread] as timing is very important. If normal TFTP does not work and serial is unavailable, recovering a brick (e.g. from flashing an oversize image) is possible via pin-short to enter TFTP mode. '''This is not without risk!''' Read [http://www.dd-wrt.com/phpBB2/viewtopic.php?t=81013 this thread] as timing is very important.
Line 115: Line 120:
[https://www.dd-wrt.com/phpBB2/viewtopic.php?t=72269 Forum device thread] [https://www.dd-wrt.com/phpBB2/viewtopic.php?t=72269 Forum device thread]
-WNR2000v2 has a known bug with firmware up through 18777 (and 26490):<br>+It has [https://www.linksysinfo.org/index.php?threads/wnr2000v2-and-tomato.71918/#post-270271 been reported] that Tomato firmware must be flashed from DD-WRT. [https://exotic.se/freshtomato/ Freshtomato] Mini builds (no-USB K2.6 MIPSr2) might fit (unsupported by DD-WRT, and untested), e.g.:
-LAN1, LAN2, LAN3 and LAN4 port work properly (10M/100M half/full duplex) but the LED displays incorrectly:+*freshtomato-K26-NVRAM32K_RT-MIPSR2-{version}-''Mini''
-*LAN1 and LAN2 always amber+*freshtomato-K26-NVRAM32K_RT-MIPSR2-{version}-''MiniIPv6''
-*LAN 3 always green+*[https://bitbucket.org/pedro311/freshtomato-mips/src/mips-master/release/src/Makefile Differences]: Versus ''Mini'', ''MiniIPv6'' adds IPv6 but removes JFFS and HTTPS
-*LAN4 LED is correct: amber for 10M connection and green for 100M networking+*''Mini''(Open)''VPN'' and ''Mini''(PPTD)''VPN2'' builds have size optimizations and lose JFFS, but may be oversized
 + 
 +WNR2000v2 has a known LED bug with firmware through 18777 (and 26490):<br>
 +LAN ports work properly but the LED (10/100Mb/s) color displays incorrectly:
 +*LAN1 and LAN2: always amber
 +*LAN3: always green
 +*LAN4: displays correctly (amber for 10Mb/s connection, green for 100Mb/s)
 + 
[[Category:Netgear guides]] [[Category:Netgear guides]]

Current revision

Contents

[edit] Hardware

[edit] Specifications

FCC ID PY309100105
Power 12 VDC, 1 A
CPU Broadcom BCM4716B0 (300 MHz)
Flash/RAM 4 /32 MiB
Wireless chip1 Broadcom BCM4716B0
Wireless protocols bgn
Wireless MIMO config 2x2:2
Antenna connector U.FL
WAN / LAN ports 1 / 4 @ 10/100 Mb/s

[edit] MTD Partitions

From a `dmesg` output:

[edit] CFE log

CFE for WNR2000v2 version: v1.0.18
Build Date: Wed Sep  9 14:33:22 CST 2009
[...]
Creating 10 MTD partitions on "sflash":
0x00000000-0x00040000 : "boot"
0x00040000-0x00390000 : "linux"
0x000c0e78-0x00390000 : "rootfs"
0x00390000-0x003a0000 : "ML1"
0x003a0000-0x003b0000 : "ML2"
0x003b0000-0x003c0000 : "T_Meter1"
0x003c0000-0x003d0000 : "T_Meter2"
0x003d0000-0x003e0000 : "POT"
0x003e0000-0x003f0000 : "board_data"
0x003f0000-0x00400000 : "nvram"

[edit] Running DD-WRT

Creating 5 MTD partitions on "sflash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x003e0000 : "linux"
0x0018bc00-0x00390000 : "rootfs"
0x003f0000-0x00400000 : "nvram"
0x00390000-0x003e0000 : "ddwrt"

[edit] Flash Size

DD-WRT replaces the linux partition and adds ddwrt, but board_data and nvram must be preserved.

  • Thus the size limit is: 0x3E0000-0x40000=3712 KB
  • The CFE vmlinuz loader times out when loading linux, so full build size may not be achievable.

[edit] Initial Flash Instructions

THESE INSTRUCTIONS ARE FOR THE VERSION 2 MODEL ONLY! For V3 see HERE.

  1. Read the Firmware FAQ and Peacock announcement
  2. Find build links here.
  3. A known good initial flash trailed build is 15962: K2.6_mini-WNR2000v2.chk in the broadcom_K26 directory.
  4. Push the reset button on the back of the router until the lights flash (or 30s), then release.
  5. Attach an Ethernet cable to a router LAN port, and disable wireless on the computer.
  6. Wait until you have a connection with the router then login to the router at http://192.168.1.1/
  7. At the password prompt, put admin/admin or admin/password for the username/password
  8. Go to the Router Upgrade link on the left side of the router gui and click on it
  9. Navigate to and Choose the mini-WNR2000v2.chk file and confirm to upgrade to a different version
  10. Wait FIVE full minutes after the upgrade appears to have finished. You can watch the lights on the front if you need something to do. As long as they are changing, you need to sit quietly and wait! If you screw this up you WILL brick your router. When the green and blue lights, and the connected port light have all stopped blinking, it should be ready as long as you have waited FIVE FULL MINUTES!
  11. Log onto the router at http://192.168.1.1/
  12. Set the username and password by TYPING in the boxes and hitting enter.
  13. Reset the router as outlined in note 1 of the peacock announcement. THIS STEP IS IMPORTANT!
  14. Set the password again then configure the router. Click Save on each tab, then when done click Apply
    • Remember to change the browser IP address if it was changed in the router configuration

[edit] Upgrade Flash

Flash a K2.6_mini.bin file (not nv60k, nv64k, nor trailed builds) via GUI or CLI: Installation

  • Builds after 40723 fail to flash through at least 41418 (test build r40733 is the first to fail)
    • NOTE: The reset button code was broken in 40571 and fixed in build 40750.
  • Build 42602 flashed from GUI, but required a power off and on
  • Build 50218 (test build) is the last working (through 06-06-2023-r52894 so far)
  • Build 54652 is the newest working as of Jan 05 2024.

[edit] Overclocking

Attempt at your own risk - it is recommended to add a heatsink to the BCM4716 and/or improve cooling.
The BCM4716 uses the pll20mhz_table from hndmips.c, and the CFE allows overclocking.

  • Use the GUI (if possible), or for more options set clkfreq based on the pll20mhz_table's {cpu,ddr,axi} settings.
  • If manually setting, the nvram "overclocking" parameter must also be set to the {cpu} speed (or DD will revert it):
nvram set clkfreq={cpu,ddr,axi}
nvram set overclocking={cpu}
nvram commit && reboot
  • The Samsung K4H561638?-LCCC RAM (where ? is 'J' or 'N') is DDR400 CL3: 200 MHz 'ddr' speed from hndmips.c.
  • Depending on long-term stability, 400,200,100, 373,186,93 or 353,176,88 are good options (with overclocking set appropriately).

[edit] Bad Flash Recovery

This defaults to boot_wait=0, and the CFE for this model has fewer commands available than typical. Avoid using `nvram erase` if the TFTP is not working, as this can make things worse. There are three options for serial recovery with TFTP (see pinouts):

flash : flash1.trx
  • This replaces the `-ctheader` option, to flash trailed builds (OEM or mini-WNR2000v2.chk).
flash -noheader : flash1.trx
  • This works for a bad DD-WRT flash with non-trailed builds so long as `nvram erase` is not used.
tftpd
  • This puts the CFE into a wait state to receive a file via TFTP. It is the only way to recover to OEM firmware, if nothing else works.

If normal TFTP does not work and serial is unavailable, recovering a brick (e.g. from flashing an oversize image) is possible via pin-short to enter TFTP mode. This is not without risk! Read this thread as timing is very important.

[edit] Notes

Forum device thread

It has been reported that Tomato firmware must be flashed from DD-WRT. Freshtomato Mini builds (no-USB K2.6 MIPSr2) might fit (unsupported by DD-WRT, and untested), e.g.:

  • freshtomato-K26-NVRAM32K_RT-MIPSR2-{version}-Mini
  • freshtomato-K26-NVRAM32K_RT-MIPSR2-{version}-MiniIPv6
  • Differences: Versus Mini, MiniIPv6 adds IPv6 but removes JFFS and HTTPS
  • Mini(Open)VPN and Mini(PPTD)VPN2 builds have size optimizations and lose JFFS, but may be oversized

WNR2000v2 has a known LED bug with firmware through 18777 (and 26490):
LAN ports work properly but the LED (10/100Mb/s) color displays incorrectly:

  • LAN1 and LAN2: always amber
  • LAN3: always green
  • LAN4: displays correctly (amber for 10Mb/s connection, green for 100Mb/s)