Does OpenWRT Support the new TP-LINK device RE200 ?
Or is it in the Pipeline ?

regrads
Klaus

My idea:
Build a Firmware with this options:
Target System Ralink RT288x/RT3xxx
Subtarget MT7620 based boardes
Target Profile Default Profile

Board information is here: http://wiki.openwrt.org/toh/tp-link/re200

Should a try to flash the RE200 or is it to dangerous ?
What can i do, to make the RE200 available to openwrt ?

(Last edited by Rampler on 15 Apr 2015, 08:02)

I have a RE200 and am willing to try to get it working on if anyone has a good guide on how to get started.  To get past the factory flash, is there any magic number information that needs to be packaged so that it is accepted by the device?  The device page says rampis as the target but that link is broken.

OK, I have been spending a little time each night trying to get this device supported, with very little understanding of what I am doing.

I found the mktplinkfw in the imagebuilder and was able to view that the factory firmware uses the TP-Link v1 header information:

File name              : /home/matt/re200-firmware.bin
File size              : 0x007e0200 /  8258048 bytes
Version 1 Header size  : 0x00000200 /      512 bytes
Header MD5Sum1         : 74 74 2b 2f 81 09 31 77 af 17 e1 e6 ea 1b 8e f7 (ok)
Header MD5Sum2         : 5f 9c ca 34 1b f9 af 92 99 ee 03 26 15 cb 6c 85 (purpose yet unknown, unchecked here)

Vendor name            : TP-LINK Technologies
Firmware version       : ver. 1.0
Hardware ID            : 0x02000001
Hardware Revision      : 0x00000001
Region code            : 0x00000000

Kernel data offset     : 0x00000200 /      512 bytes
Kernel data length     : 0x000d8375 /   885621 bytes
Kernel load address    : 0x00000080
Kernel entry point     : 0x10c30080
Rootfs data offset     : 0x00100000 /  1048576 bytes
Rootfs data length     : 0x006c0000 /  7077888 bytes
Boot loader data offset: 0x00000000 /        0 bytes
Boot loader data length: 0x00019424 /   103460 bytes
Total firmware length  : 0x007e0200 /  8258048 bytes

I understand what it means, but I don't know what good the information does me.  I am guessing that there is something I can do to create an image definition that would let me strip the uboot information out so that I could put it in an openWRT image.  Anybody know how to use the mktplinkfw utility?

I think the mktplinkfw tool should be one of your last concerns, for the moment you should focus on gathering information about the device: open it up, take pictures, document it in the wiki (look at other device pages for reference - some of the TP-Link devices are well documented), find serial port (read the wiki on this subject, first!), connect to it, get a boot log, backup your entire flash.
After that, you should get comfortable with the build environment, add your device configuration, build basic images, load kernel images into RAM and check how they boot up. Then you will need the mktplinkfw tool to build an image that you can flash to the device.