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 [2018/03/31 23:23] – ↷ Links adapted because of a move operation bobafetthotmailtoh:netgear:wnr2200 [2019/11/05 13:06] – tftp method can work on 16M model sefralgon
Line 2: Line 2:
  
 ===== Supported Versions ===== ===== Supported Versions =====
-^ Version/Model   ^ Launch Date   ^ S/N   ^ OpenWrt Version Supported           ^ Model Specific Notes   ^ +---- datatable ---- 
-| v1              |             |     |  Barrier Breaker (14.07) and newer  |                      |+cols    : Brand, Model, Versions, Supported Current Rel, OEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid 
 +headers : Brand, Model, Version, Current Release, OEM Info, Forum Topic, Technical Data 
 +align   : c,c,c,c,c,c,
 +filter  : Model=WNR2200 
 +sort    : ^Flash MB 
 +---
  
 ===== Hardware Highlights ===== ===== Hardware Highlights =====
-^ Ver ^ CPU ^ Ram ^ Flash ^ Network ^ Wireless ^ USB ^ Serial ^ JTag ^ Wiki ^ FCC ^ +---- datatable ---- 
-| v1 | Atheros AR7241 360 MHz | 64MiB | 8MiB | 1 WAN + 4x LAN (100 Mbit) | AR9287 [bgn 2x2:2] | 1x USB 2.0 | Yes | Yes(EJTAGNot soldered) | [[https://wikidevi.com/wiki/Netgear_WNR2200|here]] | [[https://fcc.io/PY3/10200131|here]] | +cols    : Model, Versions, CPU, CPU MHz, Flash MB_mbflashs, RAM MB_mbram, WLAN Hardware, WLAN 2.4GHz, WLAN 5.0GHz, Ethernet 100M ports_, Ethernet Gbit ports_, Modem, USB ports_ 
- +header  Model, Version,SoC,CPU MHz,Flash MB,RAM MB,WLAN Hardware,WLAN2.4,WLAN5.0,100M ports,Gbit ports,Modem,USB 
-[[http://www.netgear.com/home/products/networking/wifi-routers/wnr2200.aspx|Manufacturer's site]]+align   c,c,c,c,c,c,c,c,c,c,c,c,
 +filter  Model=WNR2200 
 +sort    ^Flash MB 
 +----
  
  
 ===== Installation ===== ===== Installation =====
-OpenWrt provides officialnearly working (USB missing) Barrier Breaker images. USB works in images created after [[https://dev.openwrt.org/changeset/47236|r47236]].+---- datatable ---- 
 +cols    : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_urlFirmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url 
 +headers : Model, Version, Current Release, Firmware OpenWrt Install, Firmware OpenWrt Upgrade, Firmware OEM Stock 
 +align   : c,c,c 
 +filter  : Model=WNR2200 
 +sort    : ^Flash MB 
 +---- 
 + 
 +-> [[docs:guide-user:installation:generic.flashing|Install OpenWrt (generic explanation)]] 
  
 ==== Selecting a Firmware Image ==== ==== Selecting a Firmware Image ====
  
-Always use the one with //factory// in its name.+When flashing from the official firmware, always use the one with //factory// in its name.
 Note, however, that there are two factory images created for the WNR2200. One has 'NA' on the end, and the other doesn't. From my research, the 'NA' stands for 'North America'. However, it also seems that Netgear did not make a different firmware for North Americans. Not being from North America, I didn't care about this and just flashed the one without 'NA' in its name. If you are from North America, then you should probably contact someone on IRC, the mailing lists or the forums to get a more definite answer. I also saw that Netgear listed on their website that there are firmware differences between the worldwide versions and the Russian and Chinese versions, so if you're from Russia or China, you might want to ask someone before flashing as well. Note, however, that there are two factory images created for the WNR2200. One has 'NA' on the end, and the other doesn't. From my research, the 'NA' stands for 'North America'. However, it also seems that Netgear did not make a different firmware for North Americans. Not being from North America, I didn't care about this and just flashed the one without 'NA' in its name. If you are from North America, then you should probably contact someone on IRC, the mailing lists or the forums to get a more definite answer. I also saw that Netgear listed on their website that there are firmware differences between the worldwide versions and the Russian and Chinese versions, so if you're from Russia or China, you might want to ask someone before flashing as well.
 +
 +Factory firmware, as well as firmware distributed from the official site has 128 byte header, which consists of 3-4 lines of plain text padded with 0x00 bytes. The official web interface checks for correct device identifier (in this case wnr2200) and when it's present, compares the version and shows a warning when you try to downgrade it. Firmware named factory-NA has line "region:NA" in it. Example header from an official firmware image:
 +
 +  device:wnr2200
 +  version:V1.0.2.24
 +  region:
 +
 +Other than that, the last byte of the image contains a checksum. A program tools/firmware-utils/src/mkdniimg.c from OpenWRT source tree contains code which can create images of this format. 
 +
 +The difference between routers sold in Russia and China and other version is flash size. Russian router has MX25L12845EMI-10G which is 16 legged SPI chip with 16M of NOR flash. It is sometimes marketed as WNR2200-100RUS, but router label just says WNR2200.
 +
 +However, as far as I can see, there is difference between labels on 100RUS and WW versions: Russian (16M) version has three fields with adhesive stickers: SECURITY PIN, SERIAL, MAC; While version sold elsewhere (8M) has four: WiFi Network Name (SSID), Network Key (Password), SERIAL, MAC.
 +It could be used as a clue, but this observation is based on only couple of routers and only definitive ways to determine fw size are via terminal or by looking at the chip itself.
  
 //If you are unsure of which version to flash, do not flash. You could end up bricking your router if you flash the wrong version.// //If you are unsure of which version to flash, do not flash. You could end up bricking your router if you flash the wrong version.//
Line 27: Line 58:
 ==== Flashing from OpenWrt ==== ==== Flashing from OpenWrt ====
  
-The OpenWrt web interface has an option to flash new firmware over it, but I did not get it working yet+The OpenWrt web interface has an option to flash new firmware over it. If it doesn't work, //sysupgrade// script can be used from terminal. 
-So to flash OpenWrt manually over tftp (without a serial console), you'll have to boot into recovery mode. Solet's get started.+ 
 +Update can also be done manually by flashing **sysupgrade.bin** image onto "firmware" partition with //mtd write// command. Please make sure, first four bytes of image you are about flash are 2200 (32 32 30 30 in hex). 
 + 
 +If you want to flash official firmware from OpenWRT you need to strip 128 byte-long header first. 
 + 
 +==== Flashing from Bootloader ==== 
 + 
 +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 mandatoryprobably 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 57: 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 602: Line 640:
 serial   80000003 SIO stdin stdout stderr</nowiki> serial   80000003 SIO stdin stdout stderr</nowiki>
 </WRAP>\\ </WRAP>\\
 +
 +=== Flashing 16M RU/CN model via bootloader ===
 +
 +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 616: 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 633: 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 649: 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 ===
Line 680: Line 717:
  gpio-59  (reset               ) in  hi      gpio-59  (reset               ) 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.
  
 ===== Bootlogs ===== ===== Bootlogs =====
Line 873: Line 915:
   root@WNR2200:/#   root@WNR2200:/#
 </code> | </code> |
 +
 +===== Tags =====
 +[[meta:tags|How to add tags]]
 +{{tag>AR7241 8flash 16flash 64ram}}
  • Last modified: 2024/02/12 08:58
  • by 127.0.0.1