Topic: Is the RE450 now supported?

The content of this topic has been archived between 31 Mar 2018 and 7 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Page 4 of 4

Post #76

americadragons

6 Feb 2017, 19:09

Does anybody knows if i can use this device as a root ap i mean i have a modem and i want to use the rj45 in wan mode to dial the conection PPPOE and then setup a wireless network like a wireless router

(Last edited by americadragons on 6 Feb 2017, 19:10)

Post #77

radekdostal

11 Feb 2017, 13:17

americadragons wrote:

Does anybody knows if i can use this device as a root ap i mean i have a modem and i want to use the rj45 in wan mode to dial the conection PPPOE and then setup a wireless network like a wireless router

I never tried it, but do not see any technical reason, why it would not be possible. Only annoying thing is that you will have no LANs ports than.

Post #78

diegomanas

25 May 2017, 17:44

Heinz wrote:

@brandst check my file: ftp://tplink-forum.pl/temp/re450_back_to_stock.bin
or use LEDE sysupgrade image.

Does anyone has this file by any chance? I was looking into getting back to stock

Post #79

Heinz

25 May 2017, 17:54

diegomanas wrote:

Heinz wrote:
@brandst check my file: ftp://tplink-forum.pl/temp/re450_back_to_stock.bin
or use LEDE sysupgrade image.
Does anyone has this file by any chance? I was looking into getting back to stock

Check this: https://mega.nz/#!yBg1Ub5K!phRB6wnEJbGx … IbYdIHx-Jk

Post #80

diegomanas

26 May 2017, 02:43

Heinz wrote:

diegomanas wrote:
Heinz wrote:
@brandst check my file: ftp://tplink-forum.pl/temp/re450_back_to_stock.bin
or use LEDE sysupgrade image.
Does anyone has this file by any chance? I was looking into getting back to stock
Check this: https://mega.nz/#!yBg1Ub5K!phRB6wnEJbGx … IbYdIHx-Jk

Many thanks @Heinz, it worked like a charm!

Most of what you need is in page 2, but I'll leave here what I did to recover mine to stock for reference:

Renamed file to "re450bs.bin" for convenience but it is not required
Set my PC's IP to fixed (In my case 192.168.1.3)
Bring up a tftp server, in my case tftp64 but anyone will do.
Add file to the root that is visible through tftp
Connect by serial and do the following:

U-Boot 1.1.4 (Jul 27 2016 - 17:23:50)

ap135 - Scorpion 1.0

DRAM:  128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 133k for U-Boot at: 87fdc000
Reserving 192k for malloc() at: 87fac000
Reserving 44 Bytes for Board Info at: 87fabfd4
Reserving 36 Bytes for Global Data at: 87fabfb0
Reserving 128k for boot params() at: 87f8bfb0
Stack Pointer at: 87f8bf98
Now running in RAM - U-Boot at: 87fdc000
Flash Manuf Id 0xc2, DeviceId0 0x20, DeviceId1 0x17
flash size 16MB, sector count = 256
Flash: 16 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ath_gmac_enet_initialize...
athrs_sgmii_res_cal: cal value = 0xe
No valid address in Flash. Using fixed address
Scorpion  ----> AR8033 PHY *
AR8033 PHY init
eth0: 00:03:7f:09:0b:ad
eth0 up
eth0
Setting 0x18116290 to 0x58b0214f
Autobooting in 1 seconds
scorpion> setenv ipaddr 192.168.1.1
scorpion> setenv serverip 192.168.1.3
scorpion> ping ${serverip}
Trying eth0
Checking Link: Up
Checking Duplex: Full
Checking Speed 100BaseT
dup 1 speed 100
Using eth0 device
host 192.168.1.3 is alive
scorpion> tftp 0x80060000 re450bs.bin&&erase 0x9f020000 +$filesize&&cp.b $fileaddr 0x9f020000 $filesize
Trying eth0
Checking Link: Up
Checking Duplex: Full
Checking Speed 100BaseT
Using eth0 device
TFTP from server 192.168.1.3; our IP address is 192.168.1.1
Filename 're450bs.bin'.
Load address: 0x80060000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##################################
done
Bytes transferred = 6160384 (5e0000 hex)
Erase Flash from 0x9f020000 to 0x9f5fffff in Bank # 1
First 0x2 last 0x5f sector size 0x10000                                                                                             95
Erased 94 sectors
Copy to Flash... write addr: 9f020000
done
scorpion> boot
## Booting image at 9f020000 ...
   Uncompressing Kernel Image ... OK
...

After this you should have the stock firmware back in your device. If you cannot connect or login, please use the reset to restore default values and configure from the scratch.

As a side note, did anyone find out the method to trigger tftp recovery without serial console? Many tp-link devices have this and it's enabled by pressing a key during boot but I couldn't see the way to get it done

Post #81

radekdostal

12 Nov 2017, 19:54

diegomanas wrote:

As a side note, did anyone find out the method to trigger tftp recovery without serial console? Many tp-link devices have this and it's enabled by pressing a key during boot but I couldn't see the way to get it done

sorry - have not noticed anything like this when just briefly looking at the published u-boot source code.

Post #82

radekdostal

12 Nov 2017, 19:57

alxscott wrote:

FROM: https://github.com/lede-project/source/pull/519
Apologies to re-open this thread, but it seems best placed... I just bough 2 x TP-Link RE450 and it is hardware variant V2.. The LEDE image fails checksum check for install. Device Wiki ( https://wikidevi.com/wiki/TP-LINK_RE450 shows same CPU and Wireless chips, so I'm hoping it is a simple code tweak @dasty ?

I am sorry, but I do not have the v2 so hard to test anything. It may be as simple as adding more lines into this array in tools/firmware-utils/src/tplink-safeloader.c

    /** Firmware layout for the RE450 */
    {
        .id = "RE450",
        .vendor = "",
        .support_list =
            "SupportList:\r\n"
            "{product_name:RE450,product_ver:1.0.0,special_id:00000000}\r\n"
            "{product_name:RE450,product_ver:1.0.0,special_id:55530000}\r\n"
            "{product_name:RE450,product_ver:1.0.0,special_id:45550000}\r\n"
            "{product_name:RE450,product_ver:1.0.0,special_id:4A500000}\r\n"
            "{product_name:RE450,product_ver:1.0.0,special_id:43410000}\r\n"
            "{product_name:RE450,product_ver:1.0.0,special_id:41550000}\r\n"
            "{product_name:RE450,product_ver:1.0.0,special_id:4B520000}\r\n"
            "{product_name:RE450,product_ver:1.0.0,special_id:55534100}\r\n"
            "\x00",

but it may requires some extra modifications to who knows what. Without having HW it is hard to tell.

Thanks,
Radek

(Last edited by radekdostal on 12 Nov 2017, 20:00)

Post #83

alxscott

12 Nov 2017, 20:05

Radek, thanks for your reply,

I'm certainly willing to try a simple code change and see if I can flash the device... My pretty ( semi..) confident there is no significant hardware changes. My only question is regarding the special_id tag / field... does this relate to official TP-Link Release numbers? For example my official firmware states "1.0.2 Build 20170626 Rel. 60833".

Thanks in advance

Alex

Post #84

radekdostal

12 Nov 2017, 20:26

alxscott wrote:

Radek, thanks for your reply,
I'm certainly willing to try a simple code change and see if I can flash the device... My pretty ( semi..) confident there is no significant hardware changes. My only question is regarding the special_id tag / field... does this relate to official TP-Link Release numbers? For example my official firmware states "1.0.2 Build 20170626 Rel. 60833".
Thanks in advance
Alex

Hi Alex,

I originally extracted content of this field by running strings on the official TP-Link firmware. When I do the same on the firmware for the V2, I get the following list:

{product_name:RE450,product_ver:2.0.0,special_id:00000000}
{product_name:RE450,product_ver:2.0.0,special_id:55530000}
{product_name:RE450,product_ver:2.0.0,special_id:45550000}
{product_name:RE450,product_ver:2.0.0,special_id:4A500000}
{product_name:RE450,product_ver:2.0.0,special_id:43410000}
{product_name:RE450,product_ver:2.0.0,special_id:41550000}
{product_name:RE450,product_ver:2.0.0,special_id:41530000}
{product_name:RE450,product_ver:2.0.0,special_id:4B520000}
{product_name:RE450,product_ver:2.0.0,special_id:42520000}

as no device v1 is mentioned there I am not sure, that v2 version of firmware would run on v1 device and vice versa. So there is a chance, that if you do this modification, it will accept it for flashing, but it will brick the device.

Post #85

alxscott

13 Nov 2017, 18:25

Thanks for that info Radek;

I'll see if I can source chipset etc info for the V2 device and make a decision to try the existing LEDE Firmware, or compile fresh or simply return the routers!

Thanks again!

Post #86

tmo26

14 Nov 2017, 00:40

https://wikidevi.com/wiki/TP-LINK_RE450_v2.x

A new forum thread for the v2 version would be a good idea.

Post #87

robimarko

14 Nov 2017, 23:41

You cant use v1 image as SoC was changed.
Anybody got bootlog?

The discussion might have continued from here.

Page 4 of 4