Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
toh:netgear:wnr1000 [2018/04/28 19:22] – v3 moved to separate page tmomastoh:netgear:wnr1000_v2 [2020/09/15 21:36] – [Netgear WNR1000 v2] jlpapple
Line 1: Line 1:
 ====== Netgear WNR1000 v2 ====== ====== Netgear WNR1000 v2 ======
  
-WNR1000-100PES - very similar to [[toh:netgear:wnr2000|WNR2000v3]] / [[toh:netgear:wnr612v2|WNR612v2]] |+{{section>meta:infobox:432_warning#infobox_for_dataentries&noheader&nofooter&noeditbutton}}
  
 +**Note:** Official images are too large as of 17.XX. Use the Community Builds in the forum topic URL below for the latest 17.XX, 18.XX, and 19.XX images. https://forum.openwrt.org/t/builds-for-netgear-wnr1000v2-wnr1000v2-vc-wnr612v2-wpn824n-wnr2000v3/39360
  
 +WNR1000-100PES - very similar to [[toh:netgear:wnr2000|WNR2000v3]] / [[toh:netgear:wnr612v2|WNR612v2]]
 +
 +WNR1000v2 also exists as WNR1000v2h2 - instructions for WNR1000v2 also work for WNR1000v2h2 without modification.
 ===== Supported Versions ===== ===== Supported Versions =====
 ---- datatable ---- ---- datatable ----
Line 38: Line 42:
 -> [[docs:guide-user:installation:generic.flashing|Install OpenWrt (generic explanation)]] -> [[docs:guide-user:installation:generic.flashing|Install OpenWrt (generic explanation)]]
  
-FIXME Please add the installation procedure here.+**Note:**  Ready-to-install firmware images for OpenWrt 17.01.7 and 18.06.8 and 19.07.3 are available as of June 2020 [[https://forum.openwrt.org/t/wnr1000v2-builds-for-netgear/39360|via OpenWrt Community Builds]]. These are customized builds that do include opkg due to inadequate flash size that cause stock, official OpenWrt builds to bootloop or not retain settings upon reboot.
  
 +[[https://forum.openwrt.org/t/wnr1000v2-builds-for-netgear/39360|Updated Installation Instructions]]
  
 +- - -
 +
 +I tried web-interface upload of v2.img linked above, router complained 2x about image, using ambiguous language about cause of failure; filename pattern violation, or image content, or checksum..
 +
 + 1. alert/modal/popup "Firmware upload failed, please check your file"
 + I dismiss that, and click ok/yes
 + 2. another error, now inserted into web-page <div>, text refreshes away before I can copy-paste it
 +
 +Upgrade WNR1000v2 to the latest factory firmware: 1.1.2.60. Otherwise, the power LED may not behave properly.
 +
 +You need to place the device into failsafe mode. For booting into failsafe mode, you need to power up the device while holding the reset button with a pin. The power LED should have an amber colour. Hold the button until it is starting to flash green. It starts to flash green after it flashes the amber LED for six times. After that, the device is in failsafe mode, accepting a firmware via its TFTP server. The device should respond to pings at 192.168.1.1, although the responses may be malformed.
 +
 +Configure your ethernet interface with a 192.168.1.0/24 IP address. I use 192.168.1.2 with netmask 255.255.255.0 but it should work with any free address from that block.
 +
 +You need a TFTP client for this purpose. You may check the OpenWrt wiki for more information if you aren't familiar with the procedure.
 +You need openwrt-ar71xx-generic-wnr1000v2-squashfs-factory-barrier-breaker-r44095.img, download can be found at https://gist.github.com/SaltwaterC/ef49c8a4df81c8896153. 
 +It's only image what can be flashed sucseesfuly, later images stuck at bootloop.
 +
 +> tftp 192.168.1.1
 +> binary
 +> trace
 +> put openwrt-ar71xx-generic-wnr1000v2-squashfs-factory-barrier-breaker-r44095.img
 +
 +After boot you can upgrade openwrt to a newer version with sysupgrade.
 ===== Telnet enable ===== ===== Telnet enable =====
  
Line 60: Line 89:
 ==== GPIO ==== ==== GPIO ====
  
-GPIO LEDs and buttons on this device are connected to either AR7240 SoC or AR9285 wireless chip, so not all of them are accessible to stock version of OpenWrt 15.05 (generic ath9k driver does not register AR9285 GPIOs in kernel). Please read more in __Patches__ section below about current status of addressing these issues.+GPIO LEDs and buttons on this device are connected to GPIO controllers on AR7240 SoC and AR9285 wireless chip.
  
 Controlled by **AR7240** SoC (18 GPIOs total, LAN LEDs shared with built-in Ethernet switch) : Controlled by **AR7240** SoC (18 GPIOs total, LAN LEDs shared with built-in Ethernet switch) :
 ^  Type  ^   Function    ^     GPIO      ^   Polarity                 Notes               ^ ^  Type  ^   Function    ^     GPIO      ^   Polarity                 Notes               ^
 |  LED    WAN  AMBER      (0, 0)    active low  |                                   | |  LED    WAN  AMBER      (0, 0)    active low  |                                   |
-|  LED   |  TEST AMBER   |    (0, 1)    active low  |  aka POWER AMBER  - see note [3]  |+|  LED   |  POWER AMBER  |    (0, 1)    active low  |  aka TEST AMBER  - see note [3]   |
 |  LED    LAN1 AMBER      (0, 6)    active low  |  shared with JTAG - see note [0]  | |  LED    LAN1 AMBER      (0, 6)    active low  |  shared with JTAG - see note [0]  |
 |  LED    LAN2 AMBER      (0, 7)    active low  |  shared with JTAG - see note [0]  | |  LED    LAN2 AMBER      (0, 7)    active low  |  shared with JTAG - see note [0]  |
Line 77: Line 106:
 |  LED    WAN  GREEN    17  (0, 17)  |  active low  |   link activity - see note [1]    | |  LED    WAN  GREEN    17  (0, 17)  |  active low  |   link activity - see note [1]    |
  
-Controlled by **AR9285** wireless chip (12 GPIOs total, unaccessible with default ath9k driver, see __Patches__ section below) :+Controlled by **AR9285** wireless chip (12 GPIOs total) :
 ^   Type     Function       GPIO       Polarity                   Notes                  ^ ^   Type     Function       GPIO       Polarity                   Notes                  ^
 |   LED    |  WLAN  BLUE  |  53  (1, 1)  |  active low  |  not all triggers work - see note [2]  | |   LED    |  WLAN  BLUE  |  53  (1, 1)  |  active low  |  not all triggers work - see note [2]  |
Line 91: Line 120:
   *//[2] - 'phy0radio' trigger does not work, use default 'phy0tpt' or 'wlan0' netdevice instead//   *//[2] - 'phy0radio' trigger does not work, use default 'phy0tpt' or 'wlan0' netdevice instead//
   *//[3] - this is amber light on power LED (labelled TEST in u-boot sources)//   *//[3] - this is amber light on power LED (labelled TEST in u-boot sources)//
- 
-=== Patches === 
- 
-Patches providing full GPIO support on WNR2000v3 / WNR612v2 / WNR1000v2 have been submitted to trunk ([[https://patchwork.ozlabs.org/project/openwrt/list/?submitter=68145]]). They are included in OpenWrt starting from version r49077.\\ 
-All above patches and their versions backported to Chaos Chalmer (15.05) are available at [[https://micu.webserwer.pl/pmwiki/pmwiki.php?n=OpenWRT.Patches]]. 
  
 === GPIO in OpenWrt === === GPIO in OpenWrt ===
Line 121: Line 145:
  gpio-60  (rfkill              ) in  hi      gpio-60  (rfkill              ) in  hi    
 </code> </code>
 +
 +===== Custom u-boot =====
 +
 +There is a project allowing to build custom u-boot image https://github.com/realmicu/uboot-wnrmod2k
 +It could be used if flash memory chip was replaced or to obtain additional functionality.
  
 ===== Tags ===== ===== Tags =====
 [[meta:tags|How to add tags]] [[meta:tags|How to add tags]]
 {{tag>4flash 32ram AR7240}} {{tag>4flash 32ram AR7240}}
  • Last modified: 2024/02/12 08:58
  • by 127.0.0.1