Good day to all.
I also decided to share my experience of resuscitation TP-LINK 3020.
The story in my opinion is quite useful. It all started with the fact that I decided to play around with the firmware from the forced idleness and got fucked up in full. Not only did I do this via WiFi, but also WiFi was heard in the same modem with factory firmware and default settings. Apparently the IPs were in conflict somewhere during the flashing, and I got a beautiful brick that blinked merrily with all the LEDs in a cyclic reboot.
Don't do that.Grieved and climbed into Google.
The disadvantages in my position were: I was at work in the wild wilderness, no shops nearby, no USB to UART adapters, no phone cord.
Pros: on the router has already been wired UART. Unsolder it, by the way, two minutes under a standard comb 2.54. And I was in the presence of Freeduino board with a USB port. Only here's the example of its use as a USB-UART bridge in the internet I have not met. Basically, they pressed forward on the board with a few hardware UART, and then alone. Well, I'm not such a big special. However, the time was free, the modem is already semi-corpses - virtually nothing to lose. There was a risk to kill the modem completely, there was an option to wait to return home (in a month) and take the modem out there searching the normal adapter. But a month without this modem meant the loss of waste heaps of time for me, which I had planned to spend just on the gutting of the modem. The second torture was sorry and scared.
Well, go. He took freeduin, prisobachil to the computer. Found a tricky sketch on the internet:
void setup () {
pinMode (0, INPUT);
pinMode (1, INPUT);
}
void loop () {
} And that's all. What is there input, where input is not clear. Vaguely imagining the upcoming torment with a software serial or with something else that was incomprehensible, he began to connect a modem. RX-TX, TX-RX. Somewhere they advised a resistor for matching the voltages, I did not have it. Someone advised to short the RESET to the ground, which also seemed to me suspicious. I decided that a half volt difference does not matter. The modem hooked it up to the network card and foolishly turned it on ... And I saw flashing LEDs repeating to the beat every two seconds:
U-Boot 1.1.4 (Nov 28 2011 - 09:34:00)
AP121 (ar9330) U-boot
DRAM: 32 MB
..........
.......
..
eth0, eth1
Autobooting in 1 seconds ... And where did I see it? In the window of the Arduinov serial monitor. And at the top of the window an unobtrusively loomed input field and a button with a purely Russian “Send”. I thought, doubted, scored there "
tpl ", waited for the appearance of" Autobooting in 1 seconds "and sent. Without any additional terminals there, Putty and the like. And it stopped!
It simply could not be true.
Scored "
printenv " - works!
I was shocked. Then everything goes like clockwork:
- downloaded tftpd32, stuck the firmware into its folder.
- Established IP network card laptop 192.168.1.100.
- launch tftpd32, IP - 192.168.1.100, Show Dir - the path to the firmware - Copy.
-
tftpboot 0x80000000 CyberWrt-v1.4.bin - done
-
erase 0x9f020000 + 0x3c0000 - done
-
cp.b 0x80000000 0x9f020000 0x3c0000 - done
-
bootm 0x9f020000 - done!
- returned to the network card the receipt of the IP machine ...
And all this from the serial monitor from Arduino ...
And that's it! The result is a live modem! And what is interesting - I even forgot to connect the “land” between the modem and the freeduin. I noticed it after the firmware. It was just that the modem was receiving power from the USB of the same laptop as the Freeduino, apparently it connected somewhere there :).
ZY: I soldered this Fiduin from the assembly kit, before that I didn’t solder anything smaller than the iron wire. Somehow I had a bigger picture when I ordered. In the middle of the process was already completely sure -
this will never work. Earned infection.
So - the eyes are afraid, and the hands do. Good luck to all who will repeat.
Post has been editedojw - 19.02.14, 03:13