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
toh:tp-link:re200 [2020/07/09 11:59] – [Serial] idarektoh:tp-link:re200 [2024/09/20 22:23] (current) – Add notes to flash OpenWrt on official Web UI for v3 ivzhh
Line 1: Line 1:
 ====== TP-Link RE200 ====== ====== TP-Link RE200 ======
  
-The [[toh:tp-link:start|TP-Link]] RE200 is a wall-pluggable dual-band wireless range extender (802.11b/g/n and 802.11a/n/ac) based on the MediaTek SoCs with an Ethernet port. The RE200v1 is based on a MT7620A SoC, while the RE200v2 and RE200v3 are based on a MT7628A SoC.+The [[toh:tp-link:start|TP-Link]] RE200 is a wall-pluggable dual-band wireless range extender (802.11b/g/n and 802.11a/n/ac) based on the MediaTek SoCs with an Ethernet port. The RE200v1 is based on a MT7620A SoC, while the RE200v2, RE200v3 and RE200v4 are based on a MT7628A SoC. 
 + 
 +<WRAP round important> 
 +**The latest RE200 v5 is not supported by OpenWrt! The device only has 4MB of flash and runs VxWorks by default.** 
 +</WRAP> 
 + 
 +<WRAP round important> 
 +The latest OpenWrt release (23.05.3, 23.05.4 and 22.03.7) are broken on the RE200v1! \\ 
 +**Do not flash these images, you will brick your device!** 
 +</WRAP>
  
 ===== Supported Versions ===== ===== Supported Versions =====
----- datatable ---- +<!-- ToH: { 
-cols    : Brand, Model, Versions, Supported Current Rel, OEM device homepage URL_url, OWrt Forum Topic URL_url, Device Techdata_pageid +  "source": "json", 
-headers : Brand, Model, Version, Current Release, OEM Info, Forum Topic, Technical Data +  "dom": "t", 
-align   : c,c,c,c,c,c,c +  "paging": false, 
-filter  : Model=RE200 +  "rotate": true, 
-----+  "shownColumns": ["brand", "model", "version", "supportedcurrentrel", "oemdevicehomepageurl", "owrt_forum_topic_url", "deviceid"], 
 +  "filterColumns": {"model": "^RE200$"} 
 +} -->
  
  
 ===== Hardware Highlights ===== ===== Hardware Highlights =====
----- datatable ---- +<!-- ToH: { 
-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_ +  "source": "json", 
-header  : Model, Version,SoC,CPU MHz,Flash MB,RAM MB,WLAN Hardware,WLAN2.4,WLAN5.0,100M ports,Gbit ports,Modem,USB +  "dom": "t", 
-align   : c,c,c,c,c,c,c,c,c,c,c,c,c +  "paging": false, 
-filter  : Model=RE200 +  "rotate": true, 
-----+  "shownColumns": ["model", "version", "cpu", "cpumhz", "flashmb", "rammb", "wlanhardware", "wlan24ghz", "wlan50ghz", "ethernet100mports", "ethernet1gports", "modem", "usbports"], 
 +  "filterColumns": {"model": "^RE200$"} 
 +} -->
  
  
 ===== Installation ===== ===== Installation =====
  
-/* **Release** */ +<!-- ToH: { 
-/* uncomment when release is available; at the same time, remove the snapshot datatables below */ +  "source": "json", 
-/* +  "dom": "t", 
----- datatable ---- +  "paging": false, 
-cols    : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url +  "rotate": true, 
-headers : Model, Version, Current Release, Firmware OpenWrt Install, Firmware OpenWrt Upgrade, Firmware OEM Stock +  "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareopenwrtupgradeurl", "firmwareoemstockurl"], 
-align   : c,c,c +  "filterColumns": {"model": "^RE200$"} 
-filter  : Model=RE200 +} -->
----- +
-*/ +
- +
----- datatable ---- +
-cols    : Model, Versions, Supported Current Rel, Firmware OpenWrt snapshot Install URL_url, Firmware OpenWrt snapshot Upgrade URL_url, Firmware OEM Stock URL_url +
-headers : Model, Version, Current Release, Firmware OpenWrt snapshot Install, Firmware OpenWrt snapshot Upgrade, Firmware OEM Stock +
-align   : c,c,c +
-filter  : Model=RE200 +
-----+
  
 -> [[docs:guide-user:installation:generic.flashing|Install OpenWrt (generic explanation)]] -> [[docs:guide-user:installation:generic.flashing|Install OpenWrt (generic explanation)]]
  
 +Note that the time for an initial flash is very long for these devices. Users should expect 20 minutes before being able to access it, V4 can be 10 minutes, V1 is slower. Further sysupgrades may be a little faster at around 8 minutes.
 ==== Web Interface Method (v1) ==== ==== Web Interface Method (v1) ====
 +
 +<WRAP round important>
 +The latest OpenWrt release (23.05.3, 23.05.4 and 22.03.7) are broken on the RE200v1! \\
 +**Do not flash these images, you will brick your device!**
 +</WRAP>
  
 It is possible to install OpenWrt via the TP-Link web interface, but you need to prepare the image first. It is possible to install OpenWrt via the TP-Link web interface, but you need to prepare the image first.
Line 49: Line 59:
 === Automatic image preparation === === Automatic image preparation ===
  
-A GUI tool for creating a web-flashable image based on an original TP-Link firmware image and an OpenWrt image is available at [[https://www.aboehler.at/doku/doku.php/projects:re200]]. Follow the instructions there or in the software. The software basically automates the below steps.+The [[https://www.aboehler.at/doku/doku.php/projects:re200|GUI tool (openwrt-imagetool)]] for creating a web-flashable image based on an original TP-Link firmware image and an OpenWrt image is available [[https://www.aboehler.at/hg/openwrt-imagetool/archive/tip.tar.bz2 | in this mercurial repo]]. Follow the instructions there or in the software. The software basically automates the below steps.
  
 === Manual image preparation === === Manual image preparation ===
Line 62: Line 72:
 Then, the Header MD5sum1 needs to be fixed. You can use ''%%mktplinkfw -i stock_upgrade.bin%%'' to find out the correct MD5 sum and a hex editor to change the bytes of the header sum. The web interface now happily accepts the image. Then, the Header MD5sum1 needs to be fixed. You can use ''%%mktplinkfw -i stock_upgrade.bin%%'' to find out the correct MD5 sum and a hex editor to change the bytes of the header sum. The web interface now happily accepts the image.
  
-==== Web Interface Method (v2) ====+==== Web Interface Method (v2, v3, v4) ====
  
-Simply install the -factory.bin image via the stock web interface. This procedure does not overwrite U-Boot, hence you have higher chances of being able to recover from a bad flash.+Simply install the -factory.bin image via the stock web interface. This procedure does not overwrite U-Boot, hence you have higher chances of being able to recover from a bad flash. (note: for v3 running TP-Link firmware > 1.1.0, Web UI rejects OpenWrt factory bin. You need to [[https://forum.openwrt.org/t/tp-link-re200-v3-refuses-to-install-openwrt/108388/8?u=ivzhh|downgrade to 1.1.0 first]]. The TP-Link US website doesn't have the 1.1.0 firmware link, you need to stay on the EU site and download the 2019 version)
  
 ==== Serial (v1 and v2) ==== ==== Serial (v1 and v2) ====
  
-You need to configure a TFTP server at 192.168.0.10 and put the -factory.bin image as "test.bin". Then, interrupt the boot loader by pressing '2', accept the defaults and OpenWrt will be installed to flash.+You need to configure a TFTP server at 192.168.0.10 and PUT the -factory.bin image as "test.bin". Then, interrupt the boot loader by pressing '2', accept the defaults and OpenWrt will be installed to flash. RE200 will look for test.bin at 192.168.0.10 having its own IP set as 192.168.0.254.
  
-===== Back to Stock (v1) =====+==== Serial (v4) ==== 
 + 
 +You need to configure a TFTP server at 192.168.0.184 and PUT the -factory.bin image as "test.bin". Then, interrupt the boot loader by pressing '2', accept the defaults and OpenWrt will be installed to flash. RE200 will look for test.bin at 192.168.0.184 having its own IP set as 192.168.0.254. 
 + 
 + 
 +===== Back to Stock ===== 
 + 
 +==== Back to Stock (v1) ====
  
 Download an OEM firmware from TP-Link and prepare it as follows (we need to strip the first 0x200 bytes TP-Link header and the next 0x20000 bytes U-Boot): Download an OEM firmware from TP-Link and prepare it as follows (we need to strip the first 0x200 bytes TP-Link header and the next 0x20000 bytes U-Boot):
Line 76: Line 93:
 <code>dd if=re200v1_eu_3_14_2_up_boot\(160329\).bin of=re200v1_tftp.bin bs=1 skip=131584</code> <code>dd if=re200v1_eu_3_14_2_up_boot\(160329\).bin of=re200v1_tftp.bin bs=1 skip=131584</code>
  
-Put the resulting re200v1_tftp.bin image as "test.bin" to your TFTP server. Install via Serial as you would install OpenWrt.+Transfer this file to your RE200 running OpenWrt: 
 + 
 +<code>scp -O re200v1_tftp.bin root@192.168.1.1:/tmp</code> 
 + 
 +Install it by forcing a ''%%sysupgrade%%'': 
 + 
 +<code>sysupgrade -F -n /tmp/re200v1_tftp.bin</code> 
 + 
 +Flashing this relatively big file takes some time, so be patient. Afterwards, you should be back to stock. 
 + 
 +<WRAP round important> 
 +**If you flash the wrong file or mess up the preparation, you will have to disassemble your device and attach serial console!** 
 +</WRAP>
  
-In theory, you could also you ''%%sysupgrade%%'' to flash back to stock, but this is untested.+As an alternative, you can use serial console: Put the resulting re200v1_tftp.bin image as "test.bin" to your TFTP server. Install via Serial as you would install OpenWrt.
  
-===== Back to Stock (v2) =====+==== Back to Stock (v2, v3, v4) ====
  
 Download an OEM firmware from TP-Link and prepare it using the tool ''%%tplink-safeloader%%'' from the OpenWrt development environment (should be included in the Image Builder): Download an OEM firmware from TP-Link and prepare it using the tool ''%%tplink-safeloader%%'' from the OpenWrt development environment (should be included in the Image Builder):
  
-<code>build_dir/host/firmware-utils/bin/tplink-safeloader -z oem-firmware.bin -d oem-sysupgrade.bin</code>+<code>build_dir/host/firmware-utils/bin/tplink-safeloader -z oem-firmware.bin -o oem-sysupgrade.bin</code>
  
 Transfer the resulting file to /tmp on the device, then run ''%%sysupgrade /tmp/sysupgrade.bin -F%%'' on the device. ''%%-F%%'' is necessary because the firmware does not have the upgrade metadata appended. Transfer the resulting file to /tmp on the device, then run ''%%sysupgrade /tmp/sysupgrade.bin -F%%'' on the device. ''%%-F%%'' is necessary because the firmware does not have the upgrade metadata appended.
  
 **Attention:** After the first reboot, it is advisable to flash an OEM firmware upgrade. Otherwise, the software version is displayed as 0.0.0. **Attention:** After the first reboot, it is advisable to flash an OEM firmware upgrade. Otherwise, the software version is displayed as 0.0.0.
 +
 +**Note:** RE200v4 OEM firmware requires a ''%%soft_ver%%'' HIGHER than its own. This means (for the time being until a solution is found):
 +
 +If you
 +
 +  - Upgrade from stock to OpenWrt or
 +  - Upgrade stock to newer stock version
 +
 +it will require the firmware image to contain a later firmware version than the one currently installed. However, if OpenWrt is always $STOCK+1, you cannot simply flash OpenWrt and revert to stock. Doing so would leave you with the OpenWrt-supplied FW version stored in the soft-version partition. Stock will then refuse any FW with a version lower or equal to this; which simply might not exist.
 +
 +This also makes the following impossible:
 +
 +  - flash OpenWrt
 +  - revert to stock
 +  - flash OpenWrt again (fails because the firmware already has the version used by this image)
 +
 +If the obove mentioned serial recovery should fail because of this, one could do the following:
 +  - place openwrt-ramips-mt76x8-tplink_re200-v4-initramfs-kernel.bin as test.bin at the tftp server (if you compile that target it will drop in bin/targets along with the other images)
 +  - press 4 to enter console mode (write help for available commands)
 +  - tftp to load image into ram
 +  - bootm to start the kernel
 +  - you now have a running openwrt kernel and may bring a working image to /tmp (wget)
 +  - sysupgrade with your image
 +
 +This however will not overwrite ''%%soft_ver%%''!
 +
  
 ===== Hardware ===== ===== Hardware =====
 ==== Info ==== ==== Info ====
-^ ^ RE200v1 ^ RE200v2/v3 ^+^ ^ RE200v1 ^ RE200v2/v3/v4 ^
 ^ [[wp>Instruction set]]           | [[wp>MIPS architecture|MIPS]]   || ^ [[wp>Instruction set]]           | [[wp>MIPS architecture|MIPS]]   ||
 ^ Vendor                           | [[wp>MediaTek]] || ^ Vendor                           | [[wp>MediaTek]] ||
Line 106: Line 161:
 ^ [[docs:techref:hardware:port.serial|Serial]]   | [[#Serial|Yes]] || ^ [[docs:techref:hardware:port.serial|Serial]]   | [[#Serial|Yes]] ||
  
-==== Photos ====+==== Photos v1 ====
 /* =====>>>>> Standard size for photos: add ?400 to the medialink                                */ /* =====>>>>> Standard size for photos: add ?400 to the medialink                                */
 /* When uploading photos, **name them** intelligently. Nobody knows what 20100930_000602.jpg is! */ /* When uploading photos, **name them** intelligently. Nobody knows what 20100930_000602.jpg is! */
Line 125: Line 180:
 **Note:** This will void your warranty! **Note:** This will void your warranty!
  
-<WRAP BOX> 
 The case is welded together and you can't open it easily. I used a swivel vise to crack open the case. If done carefully, it only leaves a few small marks. I super-glued mine back together after porting OpenWrt. The case is welded together and you can't open it easily. I used a swivel vise to crack open the case. If done carefully, it only leaves a few small marks. I super-glued mine back together after porting OpenWrt.
-</WRAP> 
  
-4 pins from on the right (on picture) starting with top square shape not connected and following with GND, RX and TX. As noticed in version 1.1, RX and TX may be switched with places. If no output in TTL on boot, try to switch them.+{{page>meta:infobox:high_voltage&noheader&nofooter&noeditbtn}} 
 ==== Serial ==== ==== Serial ====
  
-Serial port:  TTL voltage, 57600 bps, 8N1.\\ +Serial port:  3.3V voltage (measured on RE200v1), 57600 baud, 8N1.\\ 
 {{media:tplink:re200:re200_serial.jpg?300|}} {{media:tplink:re200:re200_serial.jpg?300|}}
  
Line 138: Line 192:
  
 4 pins from on the right (on the picture) starting with a top square shape not connected and following with GND, RX and TX. As noticed in version 1.1, RX and TX may be switched with places. If no output in TTL on boot, try to switch them. 4 pins from on the right (on the picture) starting with a top square shape not connected and following with GND, RX and TX. As noticed in version 1.1, RX and TX may be switched with places. If no output in TTL on boot, try to switch them.
 +
 +
 +RE200-V4 mainboard view.\\
 +{{media:tplink:re200:re200-v4-mb.jpg?300|}}
 +
 +
 ===== U-Boot ====== ===== U-Boot ======
  
Line 218: Line 278:
 </code> </code>
  
 +===== U-Boot from RE200 Ver. 4.0 ======
 +
 +
 +<code>
 +U-Boot 1.1.3 (Jul  8 2020 - 12:47:21)
 +
 +Board: Ralink APSoC DRAM:  64 MB
 +relocate_code Pointer at: 83fb8000
 +Use New Uboot
 +Use New Uboot patch lock_dcache addiu $12, 0x1000
 +flash manufacture id: ef, device id 40 17
 +find flash: W25Q64BV
 +*** Warning - bad CRC, using default environment
 +
 +============================================ 
 +Ralink UBoot Version: 5.0.0.0
 +-------------------------------------------- 
 +ASIC 7628_MP (Port5<->None)
 +DRAM component: 512 Mbits DDR, width 16
 +DRAM bus: 16 bit
 +Total memory: 64 MBytes
 +Flash component: SPI Flash
 +Date:Jul  8 2020  Time:12:47:21
 +============================================ 
 +icache: sets:512, ways:4, linesz:32 ,total:65536
 +dcache: sets:256, ways:4, linesz:32 ,total:32768 
 +
 + ##### The CPU freq = 580 MHZ #### 
 + estimate memory size =64 Mbytes
 +RESET MT7628 PHY!!!!!!
 +
 +Please choose the operation: 
 +   1: Load system code to SDRAM via TFTP. 
 +   2: Load system code then write to Flash via TFTP. 
 +   3: Boot system code via Flash (default).
 +   4: Entr boot command line interface.
 +   7: Load Boot Loader code then write to Flash via Serial. 
 +   9: Load Boot Loader code then write to Flash via TFTP. 
 +default: 3
 + 0 
 +   
 +3: System Boot system code via Flash.
 +gpioMode1 Reg: 0x571504c4
 +gpioMode2 Reg: 0x5550555
 +tplink_turn_off_led
 +## Booting image at bc020000 ...
 +text base: 80000000
 +entry point: 8000c150
 +   Uncompressing Kernel Image ... OK
 +No initrd
 +## Transferring control to Linux (at address 8000c150) ...
 +## Giving linux memsize in MB, 64
 +
 +Starting kernel ...
 +
 +
 +LINUX started...
 +</code>
  
 ===== Tags ===== ===== Tags =====
 [[meta:tags|How to add tags]] [[meta:tags|How to add tags]]
-{{tag>mt7620a mt7620 mt7610E 8Flash 64RAM}}+{{tag>ramips mt7620 mt7628 8flash 64RAM 1port fastethernet 802.11bgn 802.11ac mt7610E 0usb mips32 wall_plug mains_powered}}
  • Last modified: 2020/07/09 11:59
  • by idarek