OpenWrt Forum Archive

Topic: [Solved] Unbrick a TP-WR1043ND v2.1

The content of this topic has been archived on 24 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi everybody smile

I had brick this router and when i try to unbrick with serial port i never saw that :

No valid address in Flash. Using fixed address
: cfg1 0xf cfg2 0x7114
eth0 up
eth0
Autobooting in 1 seconds..

That's what i saw :

y¦?U?!¦¦¦¦¦¦¦¦k#¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦?¦¦¦O?V¦+¦¦¦!¦¦¦w[}e¦¦¦y¦¦T*¦Y9!¦¦¦¦?/A77-#--=' A9!#3-1¦¦¦¦k¦{¦;-¦¦77¦¦¦¦¦Q¦¦¦¦¦¦¦?¦¦W=¦¦'!¦¦/-¦¦¦¦¦¦¦¦¦¦¦¦¦7¦¦¦W=¦¦¦5¦¦¦¦¦5¦¦¦¦ M¦¦5¦¦¦5¦¦¦¦¦+¦¦¦RJ¦¦e=#3¦m7¦¦53¦¦¦5-95m7¦¦¦¦¦¦¦w5-95m7¦¦¦¦¦¦¦3'=/¦- ...

- I can't wrote tpl.
- When i connect the rx pin converter to the tx pin router & connect via putty/termite nothing happened

So, i think i had overwrite u-boot...
How can i rewrite uboot ?

Thanks for your answer.

(Last edited by icstl23 on 7 Aug 2015, 09:44)

Looks more like a problem with the serial connection. What chipset are you using? Maybe try a different one.

Hi,
Thanks for your answer !

Sorry but i'm not sure to understand your answer:

@MBS: The chipset of my motherboard or my router ?
@nebbia88:  what's a standar or good RS232 port ?

I'm using this converter :

http://www.ebay.fr/itm/PL2303HX-Cable-A … 48724b50cc

For the converter I try the prolific driver and the generic driver from microsoft, nothing change..
I try the connection with 2 different computers but nothing change, always this :

y¦?U?!¦¦¦¦¦¦¦¦k#¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦?¦¦¦O?V¦+¦¦¦!¦¦¦w[}e¦¦¦y¦¦T*¦Y9!¦¦¦¦?/A77-#--=' A9!#3-1¦¦¦¦k¦{¦;-¦¦77¦¦¦¦¦Q¦¦¦¦¦¦¦?¦¦W=¦¦'!¦¦/-¦¦¦¦¦¦¦¦¦¦¦¦¦7¦¦¦W=¦¦¦5¦¦¦¦¦5¦¦¦¦ M¦¦5¦¦¦5¦¦¦¦¦+¦¦¦RJ¦¦e=#3¦m7¦¦53¦¦¦5-95m7¦¦¦¦¦¦¦w5-95m7¦¦¦¦¦¦¦3'=/¦- ...

that should work fine! are you sure about tx/rx order? baud rate 115200?

Yes, i'm sure smile

just connect gnd to gnd tx to rx  and rx to tx and be sure u use 3v

Freeneter wrote:

just connect gnd to gnd tx to rx  and rx to tx and be sure u use 3v

That's what i did exept for the 3v

In this tutorial, it's writing not use VCC connection :

https://forum.openwrt.org/viewtopic.php?id=38424

On the item description of my converter it's writing Red cable ---- VCC (5V)

Do you think it's the problem ?

And if it's not how rewrite u-boot ?

(Last edited by icstl23 on 25 Jul 2015, 22:03)

Hi smile
I had test other connection that's what i found : in my hardware (V2.1) i receive correct message when i connect like this :

http://i.imgur.com/Y90akOs.jpg


I receive that :

U-Boot 1.1.4 (Jun 13 2014 - 15:14:01)

ap135 - Scorpion 1.0DRAM:
sri
Scorpion 1.0
ath_ddr_initial_config(178): (16bit) ddr2 init
tap = 0x00000003
Tap (low, high) = (0x0, 0x1d)
Tap values = (0xe, 0xe, 0xe, 0xe)
64 MB
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x17
flash size 8MB, sector count = 128
Flash:  8 MB
Using default environment

*** Warning *** : PCIe WLAN Module not found !!!
*** Warning *** : PCIe WLAN Module not found !!!
In:    serial
Out:   serial
Err:   serial
Net:   ath_gmac_enet_initialize...
athrs_sgmii_res_cal: cal value = 0x1
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
ath_gmac_enet_initialize: reset mask:c02200
Scorpion  ----> S17 PHY *
athrs17_reg_init: complete
: cfg1 0x80000000 cfg2 0x7114
eth0: ba:be:fa:ce:08:41
eth0 up
athrs17_reg_init_wan done
SGMII in forced mode
athr_gmac_sgmii_setup SGMII done
: cfg1 0x800c0000 cfg2 0x7214
eth1: ba:be:fa:ce:08:41
eth1 up
eth0, eth1
Setting 0x18116290 to 0x58b1a14f
Autobooting in 1 seconds
## Booting image at 9f020000 ...
   Uncompressing Kernel Image ... Too big uncompressed streamLZMA ERROR 1 - must                                                                                                                                                              RESET board to recover

U-Boot 1.1.4 (Jun 13 2014 - 15:14:01)
...

I was able to wrote tpl and hit, but nothing happened.
I test with position the gnd in the other pin, it's the same

Have you got an idea for resolve ?

(Last edited by icstl23 on 26 Jul 2015, 16:09)

have u tried to reserve the tx pin also? (after the pin beside tx?)
Also u have type tpl really fast, just copy tpl in your clipboard (ctrl+c) and spam ctrl+v

Freeneter wrote:

have u tried to reserve the tx pin also? (after the pin beside tx?)
Also u have type tpl really fast, just copy tpl in your clipboard (ctrl+c) and spam ctrl+v

Yes i test that, thanks for the idea : copy tpl in your clipboard (ctrl+c) and spam !

It's more effective (with right clic for paste at home)

But the tpl not stop the reboot & reboot again..

http://www.loggn.de/wp-content/uploads/2012/05/wr1043nd_brick_gnd_tx_rx.jpg

try this order of your cable but if u had a device like a arduino or raspberry pi u could also use this devices to connect them to the router with ttl

This connection did the same message of my first post:

y¦?U?!¦¦¦¦¦¦¦¦k#¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦¦?¦¦¦O?V¦+¦¦¦!¦¦¦w[}e¦¦¦y¦¦T*¦Y9!¦¦¦¦?/A77-#--=' A9!#3-1¦¦¦¦k¦{¦;-¦¦77¦¦¦¦¦Q¦¦¦¦¦¦¦?¦¦W=¦¦'!¦¦/-¦¦¦¦¦¦¦¦¦¦¦¦¦7¦¦¦W=¦¦¦5¦¦¦¦¦5¦¦¦¦ M¦¦5¦¦¦5¦¦¦¦¦+¦¦¦RJ¦¦e=#3¦m7¦¦53¦¦¦5-95m7¦¦¦¦¦¦¦w5-95m7¦¦¦¦¦¦¦3'=/¦- ...

I have no arduino or rasberry...
Thanks for your help, it's very considerable

i´m very sorry i couldnt help u, i have no clue whats wrong sad maybe someone else got a idea?

Looks like you may have the wrong data rate.  Have you tried using 57600?  Perhaps the u-boot parameter was changed to a different data rate.

Check if your cables RX is actually able to receive its TX. So, only connect (according to the ebay page) the green wire to the white wire. Nothing else (no GND, no Vcc, no router)! Then start your terminal program, disable local echo and type something. You should read exactly what you type in. Enable local echo, now you should read every character twice, which you type in. If this doesn't work, your TX has got a problem (maybe also wrong labeled cable).
Otherwise, some TP-Link routers (or revisions) kind of disable their RX pins by default. See the following articles:
http://wiki.openwrt.org/toh/tp-link/tl- … x_disabled
http://wiki.openwrt.org/toh/tp-link/tl- … al_console

Hi smile
To begin I would like to thank every one who try to help me, It's very pleasant smile
I'm sorry for this period of silence, I got a head full of shit about this brick..


After many days i try your recommendation :
           
        - I try other data rate but nothing change
        - I try to connect only the Tx cable to the Rx pin but i can't read what i whrote
        - I try another adapter (FT232RL) but nothing change


So i decided to resolder all the pin (Tx, Rx, Gnd)

And That's the solution !

The Wiki about the V2 is right, when i connect like it's explain on, i have the good message and i can stop the reboot with tpl.

Now when i try to send the firmware.bin with :

setenv ipaddr 192.168.0.3
setenv serverip 192.168.0.5
erase 0x9f020000 +0x7c0000
tftp 0x80060000 firmware.bin


i have a message like this:

Try to..
T T T T T T T T T T

eth0: link down

Configuration:

I'm using TFTPD64, he is authorize in my firewall
My Ip adress is 192.168.0.5
The TFTPD64 is configure with this Ip
The firmware.bin is on the good folder
and the Router is connect with the LAN cable to my computer

If someone have an idea, it's will be very kind smile

(Last edited by icstl23 on 5 Aug 2015, 10:15)

You don't need to overwrite uboot in uboot.
You can flash a openwrt with unlocked uboot partition and use mtd to overwrite uboot.
Btw you should correct the wiki if it is wrong.

(Last edited by alphasparc on 5 Aug 2015, 13:22)

icstl23 wrote:

Sorry alphasparc but I don't understand your answer,
For unbrick a tl-wr1043nd
There is nothing about unlock uboot partition in the how to here : https://forum.openwrt.org/viewtopic.php?id=38424
and nothing in the wiki here : http://wiki.openwrt.org/toh/tp-link/tl-wr1043nd

Can you explain what i must do ?

TP-Link should have a TFTP unbrick mode if you upgraded to the latest tp-link firmware before.
Was documented a few month back.

I never upgraded to the latest tp-link firmware before

You should really check the firewall and IP/Subnet mask of the PC

The discussion might have continued from here.