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:wnr2200 [2019/11/01 15:25] – [Tags] +16flash sefralgontoh:netgear:wnr2200 [2019/11/05 13:06] – tftp method can work on 16M model sefralgon
Line 7: Line 7:
 align   : c,c,c,c,c,c,c align   : c,c,c,c,c,c,c
 filter  : Model=WNR2200 filter  : Model=WNR2200
 +sort    : ^Flash MB
 ---- ----
  
Line 16: Line 17:
 align   : c,c,c,c,c,c,c,c,c,c,c,c,c align   : c,c,c,c,c,c,c,c,c,c,c,c,c
 filter  : Model=WNR2200 filter  : Model=WNR2200
 +sort    : ^Flash MB
 ---- ----
  
Line 25: Line 27:
 align   : c,c,c align   : c,c,c
 filter  : Model=WNR2200 filter  : Model=WNR2200
 +sort    : ^Flash MB
 ---- ----
  
Line 63: Line 66:
 ==== Flashing from Bootloader ==== ==== Flashing from Bootloader ====
  
-So to flash OpenWrt manually over tftp (without a serial console), you'll have to boot into recovery mode. This method seems to work only for 8M version.+So to flash OpenWrt manually over tftp (without a serial console), you'll have to boot into recovery mode. (Using Reset button is not necessarily mandatory, probably other hardware buttons will work as well).
   - Turn the router off   - Turn the router off
   - Use a long, thin object (e.g. a toothpick) to hold down the button marked "Restore Factory Settings" (or something similar).   - Use a long, thin object (e.g. a toothpick) to hold down the button marked "Restore Factory Settings" (or something similar).
Line 92: Line 95:
 Make sure, that tftp.exe doesn't throws any errors. If so, retry the command until tftp executes successfully. Make sure, that tftp.exe doesn't throws any errors. If so, retry the command until tftp executes successfully.
  
-**Final steps**+=== Final steps===
  
 Once you've done all of this, wait around 3 to 7 minutes (you can see that the update is in progress, when a pairs of yellow leds goes on; its finished, when the power led turns solid green) and then reconnect to your router. If all goes well, you should be able to access your router using telnet on 192.168.1.1:23. Once you've done all of this, wait around 3 to 7 minutes (you can see that the update is in progress, when a pairs of yellow leds goes on; its finished, when the power led turns solid green) and then reconnect to your router. If all goes well, you should be able to access your router using telnet on 192.168.1.1:23.
Line 640: Line 643:
 === Flashing 16M RU/CN model via bootloader === === Flashing 16M RU/CN model via bootloader ===
  
-Unfortunately this version does not seem to support tftp recovery, however there are indications that NMRP protocol can be used to flash it.+There are indications that NMRP protocol can be used to flash it. TFTP recovery method might also work, but can be tricky. Try to watch for power LED, if it starts flashing dimly it is indication, that router is in recovery/upgrade mode.
  
 ==== Serial ==== ==== Serial ====
Line 655: Line 658:
 ==== GPIO ==== ==== GPIO ====
  
-GPIO LEDs and buttons on this device are connected to either AR7241 SoC or AR9287 wireless chip, so not all of them are accessible to stock version of OpenWrt 15.05 (on SoC some are masked by JTAG, also ath9k driver does not register AR9287 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 AR7241 SoC and AR9287 wireless chip.
  
 Controlled by **AR7241** SoC (20 GPIOs total, some shared with JTAG or built-in Ethernet switch) : Controlled by **AR7241** SoC (20 GPIOs total, some shared with JTAG or built-in Ethernet switch) :
Line 672: Line 675:
 |   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 **AR9287** wireless chip (11 GPIOs total, unaccessible with default ath9k driver, see __Patches__ section below) :+Controlled by **AR9287** wireless chip (11 GPIOs total) :
 ^   Type       Function         GPIO      ^   Polarity    ^   Notes   ^ ^   Type       Function         GPIO      ^   Polarity    ^   Notes   ^
 |   LED    |  WLAN  BLUE      |  53  (1, 0)    active low    not all triggers work - see note [2]  | |   LED    |  WLAN  BLUE      |  53  (1, 0)    active low    not all triggers work - see note [2]  |
-|   LED    |  TEST  AMBER     |  54  (1, 1)    active low    aka POWER AMBER  - see note [3]  |+|   LED    |  POWER  AMBER    |  54  (1, 1)    active low    aka TEST AMBER  - see note [3]  |
 |   LED    |  POWER GREEN      55  (1, 2)    active low    | |   LED    |  POWER GREEN      55  (1, 2)    active low    |
 |  Button  |     RFKILL        56  (1, 3)    active low    | |  Button  |     RFKILL        56  (1, 3)    active low    |
Line 688: Line 691:
   *//[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 WNR2200 have been submitted to trunk ([[https://patchwork.ozlabs.org/project/openwrt/list/?submitter=68145]]). They are included in OpenWrt starting from version r49102.\\ 
-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 ===
  • Last modified: 2024/02/12 08:58
  • by 127.0.0.1