If you have killed the flash chip there you will have to replace it to fix the router. A last resort, if the bootloader is messed up, JTAG can be used to flash a new bootloader, then a firmware image can be sent via TFTP.Īll the above methods are mentioned on the Troubleshooting page
DEBRICK ROUTER WITH TTL 232R RPI SERIAL
If you already have a pin header installed and have serial access I would use this before TFTP or Failsafe.Ĥ) JTAG. Again, this can allow you to see what went wrong, and fix it. Open the case up and connect to the serial console, either to connect to OpenWrt once it has booted, or directly to the bootloader. This allows you to get back into OpenWrt, mount the writable partition and correct your mistake.Ģ) TFTP'ing a new image (since you should have boot_wait enabled.)ģ) Serial Console. The standard order for attempting to connect to an "unconnectable" router - I hate the term "bricked," most of the time it can be recovered - are as follows:ġ) Failsafe. The reason that pin shorting can work has been discussed previously so I'm not going to go into it. One of the primary issues with shorting pins is exactly what has occured here: "Oh pins x and y don't work, lets try shorting random pins to see if that makes it better." In reality it is quite possible you've ruined the flash chip.
Shorting pins is never a good solution, there is always a better way to recover. I guess I could try the other side, but it began to ping before on pins 1-2. I tried to short pins 1-2 again, but I can not get it to ping, I tried all the pins on that same side and no ping. I changed the ip of the lan config to static 192.168.0.4 and wan to static 192.168.0.7, which are valid IPs on my network.
3.5mm Audio Jack 2 core and spiral, 24 AWG diam5mm TTL-232R-3V3-2mm USB to UART cable with +3.3V TTL level UART signals. TTL-232R-3V3-AJ USB to UART cable with +3.3V TTL level UART signals. It looked like everything was restored to original. Ttl 232r 3v3 cable pinout TTL-232R-3V3 - Buy TTL-232R-3V. However,all of my configurations were gone. I thought if I am pinging it I should be able to connect. So what I did next, while ping was still occurring, was to telnet in. However, this one is hard than the first. Since I was lock out of another different (wrt54gs) router before and was able to fix it by shorting pins 5-6 and tftping image, I thought I could fix this one. In the script there was only wireless related code. Since wireless does not work with kernel 2.6, I thought I could disable this script. I did a "chmod 644" on the file /etc/init.d/network.
0 kommentar(er)
