on Ali i purchased an MH-ET LIVE mini CH340E USB to TTL converter UART module for $ 1.68, that fixed the job.
only need pins 1, 2 and GND to connect and set the converter to 3V3.
then just follow the steps and done.
now to find the correct working DD-WRT version for hw1.8
Sorry if oot, i've wr1043nd and flash to dd-wrt Firmware 36104 and my router work normally but something bothered me, the globe/wan indicator is red but i'm still connected to my internet and don't have any problem to browsing/download and the wan status is LOCAL, this is a normal problem for WR1043nd ?? because i've tried with another router Tp-link WR841ND it's normal the indicator of wan is green .. any suggest or help??
thanks
LE: Sorted! Tried with a different serial converter, no success, and then changed the wires (from USB to router pins).
Hello all,
Like many of you, I've managed to brick a 1043nd V1.1 and so far unsuccessfully to recover it..
What I did so far:
-managed to solder GND,RX,TX to router's board.
-bought a USB to TTL Serial Converter (see img, red one)
-cannot send tpl command, tried with putty and termite.
This is what putty displays:
Code:
U-Boot 1.1.4 (Mar 31 2012 - 10:40:21)
AP83 (ar9100) U-boot 0.0.11
DRAM:
sri
32 MB
id read 0x100000ff
flash size 8MB, sector count = 128
Flash: 8 MB
Using default environment
In: serial
Out: serial
Err: serial
Net: ag7100_enet_initialize...
No valid address in Flash. Using fixed address
: cfg1 0xf cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
eth0 up
eth0
Autobooting in 1 seconds## Booting image at bf020000 ...
Uncompressing Kernel Image ... OK
It's very strage, but i have found the solution: I use a cheap USB-TTL 3.3V CP2102, looks like the orange one above. I always ends up with 4Mb. The solution is: Start Putty. Disconnect the Ground pin from CP2102 board. Power on the modem and after 1 second connect the Ground pin to the CP2102 board. Than you see the tekst scrolling en everything is working fine. You can enter commands. The Ground pin will hang the boot process, don't know why.
You are great. You save my lifie.
Everyfing works fine.
Thank you.
Hello i have bricked router 1043nd, with serial i receive this:
AP83 (ar9100) U-boot 0.0.11
DRAM:
sri
4 MB
and stop.
what is the problem?
I was getting a similar error while trying to unbrick my WR1043ND V2 router using a standard USB-TTL converter. However basis the recommendation given here https://forum.openwrt.org/viewtopic.php?id=55276 I tried using an Arduino Uno, at it worked perfectly for me.
You could try the unbrick process by using an Arduino instead of a standard USB-TTL converter if you are getting this error. Might just work out for you
I am having limited success with a Raspberry Pi 2 connecting to the serial port on the HAT. I can read the output from the Tp_link as it tries to boot but I cannot get tpl into the device as it carries on its reboot loop into infinity. Which pins did you connect to the TP-Link? TX / RX and ground?
Hello i have bricked router 1043nd, with serial i receive this:
AP83 (ar9100) U-boot 0.0.11
DRAM:
sri
4 MB
and stop.
what is the problem?
I was getting a similar error while trying to unbrick my WR1043ND V2 router using a standard USB-TTL converter. However basis the recommendation given here https://forum.openwrt.org/viewtopic.php?id=55276 I tried using an Arduino Uno, at it worked perfectly for me.
You could try the unbrick process by using an Arduino instead of a standard USB-TTL converter if you are getting this error. Might just work out for you
I am having limited success with a Raspberry Pi 2 connecting to the serial port on the HAT. I can read the output from the Tp_link as it tries to boot but I cannot get tpl into the device as it carries on its reboot loop into infinity. Which pins did you connect to the TP-Link? TX / RX and ground?
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Tue Mar 10, 2020 17:38 Post subject:
jason_a69 wrote:
I am having limited success with a Raspberry Pi 2 connecting to the serial port on the HAT. I can read the output from the Tp_link as it tries to boot but I cannot get tpl into the device as it carries on its reboot loop into infinity. Which pins did you connect to the TP-Link? TX / RX and ground?
I am having limited success with a Raspberry Pi 2 connecting to the serial port on the HAT. I can read the output from the Tp_link as it tries to boot but I cannot get tpl into the device as it carries on its reboot loop into infinity. Which pins did you connect to the TP-Link? TX / RX and ground?
Yes, all you should need to connect is TX, RX, and GND.
I've tried that but no joy, I'll get another USB to TTL adapter tomorrow and give that a go. I'm in Taiwan so there's loads of choice about Thanks for responding.
I am having limited success with a Raspberry Pi 2 connecting to the serial port on the HAT. I can read the output from the Tp_link as it tries to boot but I cannot get tpl into the device as it carries on its reboot loop into infinity. Which pins did you connect to the TP-Link? TX / RX and ground?
Yes, all you should need to connect is TX, RX, and GND.
I've tried that but no joy, I'll get another USB to TTL adapter tomorrow and give that a go. I'm in Taiwan so there's loads of choice about Thanks for responding.
So I managed to get 2 UBS TTY devices that work, a PL2303 and a CP2101. I am using the CP2102 connected to the same Raspberry Pi and I am getting the boot sequence correctly but I still cannot for the life of me get the device to stop at tpl. I have even written a minicom script that should send the information for me, it is quite simple
Code:
expect "Autobooting in 1 seconds"
send tpl
Is there any way I can test the RX pin on the motherboard? I am getting to the point where Mr Fist will make sure that the TP Link never works again.
I am having limited success with a Raspberry Pi 2 connecting to the serial port on the HAT. I can read the output from the Tp_link as it tries to boot but I cannot get tpl into the device as it carries on its reboot loop into infinity. Which pins did you connect to the TP-Link? TX / RX and ground?
Yes, all you should need to connect is TX, RX, and GND.
I've tried that but no joy, I'll get another USB to TTL adapter tomorrow and give that a go. I'm in Taiwan so there's loads of choice about Thanks for responding.
So I managed to get 2 UBS TTY devices that work, a PL2303 and a CP2101. I am using the CP2102 connected to the same Raspberry Pi and I am getting the boot sequence correctly but I still cannot for the life of me get the device to stop at tpl. I have even written a minicom script that should send the information for me, it is quite simple
Code:
expect "Autobooting in 1 seconds"
send tpl
Is there any way I can test the RX pin on the motherboard? I am getting to the point where Mr Fist will make sure that the TP Link never works again.
Any ideas are very welcome.
There is no need to reply to this, it's really fried now, only the power light is on.
