Differences
This shows you the differences between two versions of the page.
|
toh:tp-link:tl-wdr4900 [2013/02/06 04:14] qasdfdsaq |
toh:tp-link:tl-wdr4900 [2013/11/09 21:50] (current) nbd remove more obsolete crap |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======TP-Link TL-WDR4900====== | ======TP-Link TL-WDR4900====== | ||
| - | Dual Band (concurrent) and Gigabit Ethernet. | + | {{:media:toh:tp-link:tl-wdr4900.jpg?400|TP-Link TL-WDR4900 V2.x}} |
| - | Advertised as 900 Mbps it has simultaneous Triple-Stream (3x3) radios on both 2.4Ghz and 5 Ghz Bands. | + | |
| - | **There are two very different revisions:** | + | Dual Band (concurrent) and Gigabit Ethernet. Advertised as 900 Mbps it has simultaneous Triple-Stream (3x3) radios on both 2.4GHz and 5 GHz Bands. |
| - | V1.0 World-wide: 3 internal antennas (2.4Ghz) and 3 external antennas (5Ghz), 800Mhz Freescale PPC CPU | + | **<color red>There are two very different revisions</color>** |
| - | V2.0 China: 6 external antennas, 720Mhz Qualcomm/Atheros SoC | + | * V1.x: target: ''mpcC85xx'' 800Mhz Freescale PPC P1014 CPU 3 internal antennas (2.4Ghz) and 3 external antennas (5Ghz), available world-wide |
| + | * V2.x: target: ''ar71xx'' 720Mhz Qualcomm/Atheros SoC and 6 external antennas, available in PRC only | ||
| - | Qualcomm SoC QCA9558-AT4A w/ 3x3 MIMO for 2.4Ghz | + | Manufacturer's website: |
| - | Atheros AR9580-AR1A w/ 3x3 MIMO for 5Ghz | + | * [[http://www.tp-link.com/en/products/details/?model=TL-WDR4900]] (V1.x) |
| - | Atheros AR8327N-AL1A switch with "900Mbps+" hardware NAT | + | * [[http://www.tp-link.com.cn/product_double_292.html]] (V2.x) |
| - | 8M Flash | + | |
| - | 128M RAM | + | * Price: AliExpress - [[http://www.aliexpress.com/item/-/997429375.html|about 100 USD]] |
| + | |||
| + | * Forum https://forum.openwrt.org/viewtopic.php?id=42062 | ||
| ===== Supported Versions ===== | ===== Supported Versions ===== | ||
| ^ Version/Model ^ S/N ^ Release Date ^ OpenWrt Version Supported ^ Model Specific Notes ^ | ^ Version/Model ^ S/N ^ Release Date ^ OpenWrt Version Supported ^ Model Specific Notes ^ | ||
| - | | v1.0 | - | 2013 | WIP | Freescale PPC w/2 Atheros radio chips | | + | | v1.0 world-wide | - | 2013-01-22 | trunk [[https://dev.openwrt.org/changeset/36051|r36051]] | Freescale PPC w/2 Atheros radio chips 3 internal antennas (2.4Ghz) and 3 external antennas (5Ghz) | |
| - | | v2.0 | - | 2013 | ??? | ap135 - should be supportable | | + | | v1.3 world-wide | - | 2013 | trunk | http://downloads.openwrt.org/snapshots/trunk/mpc85xx/ | |
| + | | v2.0 PRC only | - | 2013-01-22 | ??? | ap135 - should be supportable, 6 external antennas, available in PRC only | | ||
| + | |||
| + | ===== Hardware ===== | ||
| + | ==== Info ==== | ||
| + | |||
| + | ^ ^ Version 1.x ^ Versions 2.x ^ | ||
| + | | **[[wp>Instruction set|Instruction set]]:** | [[wp>PowerPC]] | [[wp>MIPS architecture|MIPS]] | | ||
| + | | **Vendor:** | [[wp>Freescale Semiconductor]] | [[wp>Qualcomm Atheros]] | | ||
| + | | **[[doc:techref:Bootloader]]:** | [[doc:techref:bootloader:uboot|U-Boot]] 2010.12-svn15934 for PowerPC | [[doc:techref:bootloader:uboot|U-Boot]] ? fork of mainline U-Boot version 1.1.4 (2005-12-17) for MIPS ? | | ||
| + | | **[[doc:hardware:soc|System-On-Chip]]:** | [[wp>PowerQUICC#PowerQUICC_III|Freescale MPC85xx]] | QCA9558-AT4A | | ||
| + | | **[[doc:hardware:cpu|CPU]]/Speed** | PPC P1014@800MHz | MIPS 74Kc Vers. ?.? 720 MHz | | ||
| + | | **Flash-Chip:** | [[http://www.spansion.com/Support/Datasheets/S25FL064P_00.pdf|ST 25P64V6P]] | | | ||
| + | | **Flash size:** | 16384 KiB | 8192 KiB | | ||
| + | | **RAM-Chip:** | [[http://www.skhynix.com/inc/pdfDownload.jsp?path=/datasheet/pdf/graphics/H5TQ1G63DFR(Rev1.1).pdf|H5TQ1G63DFR]] | | | ||
| + | | **RAM size:** | 128 MiB | 128 MiB | | ||
| + | | **Wireless1:** | Chip: AR9381-AL1A for 2.4GHz | SoC: QCA9558-AT4A w/ 3x3 MIMO for 2.4Ghz | | ||
| + | | **Wireless2:** | Chip: AR9580-AR1A w/ 3x3 MIMO for 5Ghz | Chip: AR9580-AR1A w/ 3x3 MIMO for 5Ghz | | ||
| + | | **[[doc:techref:swconfig|Switch]]:** | AR8327N-AL1A | AR8327N-AL1A | | ||
| + | | **USB:** | 2 (USB 2.0) | 2 (USB 2.0) | | ||
| + | | **[[doc:hardware:port.serial|Serial]]:** | [[#Serial|Yes]] | [[#Serial|Yes]] | | ||
| + | | **[[doc:hardware:port.jtag|JTAG]]:** | Yes | [[#JTAG|Yes]] | | ||
| + | |||
| + | ==== Photos ==== | ||
| + | |||
| + | {{:media:tplinkwdr4900v1serial.jpg?400|wdr4900v1}} | ||
| + | {{:media:tplinkwdr4900v1.jpg?400|wdr4900v1}} | ||
| + | |||
| + | ===== Serial console ===== | ||
| + | |||
| + | Serial console is available on JP2 connector (look at the picture of PCB).\\ | ||
| + | Setting: 115200 8N1\\ | ||
| + | Login to factory firmware: root/5up\\ | ||
| + | |||
| + | ''note:'' be extremely careful when soldering a serial console on TP-Link TL-WDR4900 - the design of the PCB is somehow not suited for soldering and important connection/parts are near the soldering points. We have now 3 Routers which are dead, just because we used too much soldering-water... | ||
| + | |||
| + | ===== De-brick or OEM installation using the TFTP and RS232 (serial) method ===== | ||
| + | |||
| + | If you want to de-brick/upgrade your router using TFTP you follow these steps: | ||
| + | |||
| + | |||
| + | ==== Pre-requisits ==== | ||
| + | |||
| + | * Serial RS232 connected from your machine to TL-WDR4900 & a terminal program (e.g. minicom, screen) set to **115200 8N1**, no flow control, 3,3V. | ||
| + | * Copy a working & full OpenWrt firmware image into your TFTP server folder (e.g: openwrt-mpc85xx-generic-tl-wdr4900-v1-squashfs-factory.bin). | ||
| + | * A TFTP server started on your local machine on LAN address 192.168.1.x/24. | ||
| + | * Connect your LAN-port to one of the routers LAN ports. | ||
| + | |||
| + | |||
| + | ==== Written Flash Procedure ==== | ||
| + | |||
| + | - Router should be unplugged (power off), your serial line connected, terminal open and TFTP server installed not yet running. | ||
| + | - Copy your desired openwrt image for the TPlink-WDR4900 into your TFTP server folder and rename it into ''openwrt.bin'' (to save some typing within the flash procedure). | ||
| + | - First goal is to get the command prompt from the U-Boot bootloader on your router. | ||
| + | - Plug in your router and be ready to type "''vl''" just after you see the line ''Autobooting in 1 seconds'': | ||
| + | |||
| + | <code> | ||
| + | U-Boot 2010.12-svn15934 (Dec 11 2012 - 16:23:49) | ||
| + | |||
| + | CPU: P1014, Version: 1.0, (0x80f10110) | ||
| + | Core: E500, Version: 5.1, (0x80212151) | ||
| + | Clock Configuration: | ||
| + | CPU0:800 MHz, | ||
| + | CCB:400 MHz, | ||
| + | DDR:333.333 MHz (666.667 MT/s data rate) (Asynchronous), IFC:100 MHz | ||
| + | L1: D-cache 32 kB enabled | ||
| + | I-cache 32 kB enabled | ||
| + | Board: P1014RDB | ||
| + | SPI: ready | ||
| + | DRAM: 128 MiB | ||
| + | L2: 256 KB enabled | ||
| + | Using default environment | ||
| + | |||
| + | PCIe1: Root Complex of mini PCIe Slot, x1, regs @ 0xffe0a000 | ||
| + | 01:00.0 - 168c:abcd - Network controller | ||
| + | PCIe1: Bus 00 - 01 | ||
| + | PCIe2: Root Complex of PCIe Slot, x1, regs @ 0xffe09000 | ||
| + | 03:00.0 - 168c:0033 - Network controller | ||
| + | PCIe2: Bus 02 - 03 | ||
| + | In: serial | ||
| + | Out: serial | ||
| + | Err: serial | ||
| + | Net: initialization for Atheros AR8327/AR8328 | ||
| + | AR8327/AR8328 v1.1 is found! | ||
| + | eTSEC1 | ||
| + | Autobooting in 1 seconds | ||
| + | </code> | ||
| + | |||
| + | In case you failed the right timing just reboot again until the prompt appears | ||
| + | <code>=></code> | ||
| + | |||
| + | - (//optional//) Now lets check what kind of parameters the u-boot loader expects (e.g file name of firmware, IP via TFTP & load address). | ||
| + | Type ''tftpboot'' & press ENTER … | ||
| + | <code> | ||
| + | => tftpboot | ||
| + | Check for phy link status | ||
| + | Speed: 1000, full duplex | ||
| + | Using eTSEC1 device | ||
| + | TFTP from server 192.168.0.104; our IP address is 192.168.0.136 | ||
| + | Filename 'uImage'. | ||
| + | Load address: 0x1000000 | ||
| + | Loading: T T T T T T T T T T | ||
| + | Retry count exceeded; starting again | ||
| + | </code> | ||
| + | |||
| + | - As you can see, uboot expects a firmware image file name "''uImage''" at TFTP server address ''192.168.1.104'', | ||
| + | then, just change you local ip into ''192.168.1.104'' and start your TFTP server. | ||
| + | - Start the uBoot's TFTP client to download the image from your local machine by typing: ''tftpboot 0x1000000 openwrt.bin'' + ENTER | ||
| + | |||
| + | <code> | ||
| + | => tftpboot 0x1000000 openwrt.bin | ||
| + | Check for phy link status | ||
| + | Speed: 1000, full duplex | ||
| + | Using eTSEC1 device | ||
| + | TFTP from server 192.168.0.104; our IP address is 192.168.0.136 | ||
| + | Filename 'openwrt.bin'. | ||
| + | Load address: 0x1000000 | ||
| + | Loading: ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ################################################################# | ||
| + | ### | ||
| + | done | ||
| + | Bytes transferred = 16252928 (f80000 hex) | ||
| + | </code> | ||
| + | |||
| + | - The last line needs to show a size of f80000 hex, otherwise your image is unsuitable. | ||
| + | - To select the SPI flash memory type: sf probe 0 | ||
| + | <code> | ||
| + | => sf probe 0 | ||
| + | SF: Detected S25FL128S_65k with page size 256, total 16 MiB | ||
| + | 16384 KiB S25FL128S_64K at 0:0 is now current device | ||
| + | </code> | ||
| + | - Now we need to erase parts of the flash memory to be able to copy your fresh loaded firmware into it, | ||
| + | just type in the prompt ''sf erase 0x60000 0xf80000'': | ||
| + | <code> | ||
| + | => sf erase 0x60000 0xf80000 | ||
| + | SPI flash erase successful | ||
| + | </code> | ||
| + | |||
| + | - Now just copy the image to the right place by typing ''sf write 0x1000000 0x60000 0xf80000'' | ||
| + | <code> | ||
| + | => sf write 0x1000000 0x60000 0xf80000 | ||
| + | SPI flash write successful | ||
| + | </code> | ||
| + | |||
| + | - So, in case your image is the correct one, you should do just a single reboot to have a working TL-WRD4900 back on your desk. | ||
| + | Type ''reset'' or just un-plug and re-plug the power of your router and watch the boot process. | ||
| + | <code> | ||
| + | => reset | ||
| + | </code> | ||
| + | |||
| + | ==== Failsafe / reset ==== | ||
| + | After all else failed, I found [[http://www.binaryfriend.ru/2012/10/how-to-hard-reset-openwrt-on-tp-link-1043nd]]. Extremely simple. Please see the original page for more info. Summary: | ||
| + | |||
| + | - Power the router up; | ||
| + | - After powering up track the SYS light when it starts to blink, when it does press and hold the QSS button till SYS lights starts to blink faster – router goes to recovery mode; | ||
| + | - Telnet to the router on 192.168.1.1 – no password needed (if your computer doesn’t gets IP address from DHCP assign it manually for i.e. 192.168.1.200 with netmask of 255.255.255.0); | ||
| + | - In telnet terminal type `mtd -r erase rootfs_data` to reset OpenWRT to it’s defaults. | ||
| + | |||
| + | ===== Reverting to stock firmware ===== | ||
| + | |||
| + | You can revert to stock firmware by following these steps: | ||
| + | |||
| + | * Download / copy with SCP or wget this firmware to the /tmp folder of the router: [[ftp://everbest.ftpserver.biz/Share/TP-Link/TL-WDR4900%20Firmware/wdr4900nv1_en_3_14_1_up(130304)_beta.bin]] | ||
| + | * Open a SSH session to the router, cd to /tmp | ||
| + | * Execute the following command: mtd -r write wdr4900nv1_en_3_14_1_up(130304)_beta.bin firmware | ||
| + | * Wait until the router reboots | ||
| + | Note: You can only flash this firmware version because it has no BOOT in the filename. This image and OpenWRT images are the exact same size. Other images from TP-Link do have BOOT in the filename and these files are also | ||
| + | more bytes than this one. | ||
| + | {{tag>GigabitEthernet internalantenna 2usb 3x3 450mbps usb2.0 5ghz 5port 16flash 802.11abgn ath9k detachableantenna 6ant 3ant 128ram 802.11abgn_simultan 2WNIC}} | ||
toh/tp-link/tl-wdr4900.1360120467.txt.bz2 · Last modified: 2013/02/06 04:14 by qasdfdsaq
This text is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.