[OpenWrt-Devel] Get to RedBoot prompt in Atheros-based router

[Nguyễn Hồng Quân]

Hello all

I'm trying to flash OpenWrt to an old D-Link DIR-300 router. The router
has contained DD-WRT already (not stock firmware), so I assume that its
RedBoot listens at 192.168.1.1 when booting.

However, I tried many times with "telnet 192.168.1.1 9000" and cannot
get in. The error is always: No route to host (though the wired
connection - eth0 - is OK).

I tried both when NetworkManager is active and when NetworkManager is
disable.

Anyone has experience in this?

P/S: I also tried with IP 192.168.20.81 and failed.

[Bastian Bittorf]

Post by Nguyễn Hồng Quân
I'm trying to flash OpenWrt to an old D-Link DIR-300 router. The

please use
http://wiki.openwrt.org/toh/d-link/dir-300#with.dir300-flash.sh.shell.script

the link is dead, but it's in the feed:
package/feeds/packages/dir300-flash

bye, bastian

[Nguyễn Hồng Quân]

Hi Bastian,

I tried that script but failed at "Waiting for the wireless router…"
(infinite waiting).
The scripted start from "looking for factory bootloader" step but as I
told, the router has had DD-WRT already. This means factory bootloader
was replaced.

I wonder if the time for RedBoot to wait for telnet was set to 0 by
someone before.

Post by Bastian Bittorf

Post by Nguyễn Hồng Quân
I'm trying to flash OpenWrt to an old D-Link DIR-300 router. The

please use
http://wiki.openwrt.org/toh/d-link/dir-300#with.dir300-flash.sh.shell.script
package/feeds/packages/dir300-flash

--
Regards,
Quân

Y!IM: ng_hquan_vn
GTalk: ng.hong.quan

[Bastian Bittorf]

Post by Nguyễn Hồng Quân
I wonder if the time for RedBoot to wait for telnet was set to 0 by
someone before.

it should be possible from DD-WRT/openwrt to alter variables from
redboot. look out for fconfig:

http://wiki.openwrt.org/doc/techref/bootloader/redboot

bye, bastian

[Nguyễn Hồng Quân]

Hello,

Post by Bastian Bittorf
it should be possible from DD-WRT/openwrt to alter variables from
http://wiki.openwrt.org/doc/techref/bootloader/redboot

Unfortunately, because I cannot get access to RedBoot, I cannot reset
that variable.
I'm trying the last option: serial port. But what I got in Terminal is
all non-printable characters. Do you have experience in this? Maybe one
of signal lines is erroneous?

--
Regards,
Quân

Y!IM: ng_hquan_vn
GTalk: ng.hong.quan

[Bastian Bittorf]

Post by Nguyễn Hồng Quân
I'm trying the last option: serial port. But what I got in Terminal
is all non-printable characters. Do you have experience in this?
Maybe one of signal lines is erroneous?

http://wiki.openwrt.org/doc/hardware/port.serial#finding.serial.console

you are lucky! i'am ill at the moment and have time to
debrick an old dir300 via serial today. will post my experience.

bye, bastian

[Nguyễn Hồng Quân]

Hello

Post by Bastian Bittorf
http://wiki.openwrt.org/doc/hardware/port.serial#finding.serial.console
you are lucky! i'am ill at the moment and have time to
debrick an old dir300 via serial today. will post my experience.

Thanks in advance.
I determined serial pins based on
http://wiki.openwrt.org/toh/d-link/dir-300#serial.port.jp1

--
Regards,
Quân

Y!IM: ng_hquan_vn
GTalk: ng.hong.quan

[Bastian Bittorf]

Post by Nguyễn Hồng Quân
I determined serial pins based on
http://wiki.openwrt.org/toh/d-link/dir-300#serial.port.jp1

here it is working out of the box:

screen /dev/ttyS0 9600

the board needs some time to boot the bootloader,
really slow 8-)

what wondered me: if a DHCP is running in
your ethernet network it fetches and uses an IP
from there, so 192.168.1.1 is ofcourse not reachable.

bye, bastian

[Nguyễn Hồng Quân]

Hello Bastian,

Post by Bastian Bittorf

Post by Nguyễn Hồng Quân
I determined serial pins based on
http://wiki.openwrt.org/toh/d-link/dir-300#serial.port.jp1

screen /dev/ttyS0 9600
the board needs some time to boot the bootloader,
really slow 8-)

On my side, it is fast (I was checking it until the wireless LED is
on). During that time, only weird characters (not readable) show in
console.

To make the serial connection, I use a TTL-to-RS232 converter circuit,
which works well with La Fonera route before.

Post by Bastian Bittorf
what wondered me: if a DHCP is running in
your ethernet network it fetches and uses an IP
from there, so 192.168.1.1 is ofcourse not reachable.
bye, bastian

I disconnected all my other network interfaces. Use only eth0 between
my PC and router (no 3rd machine).

--
Regards,
Quân

Y!IM: ng_hquan_vn
GTalk: ng.hong.quan

[Bastian Bittorf]

Post by Nguyễn Hồng Quân
To make the serial connection, I use a TTL-to-RS232 converter
circuit, which works well with La Fonera route before.

are you really on 9600 baud 8,N,1? if yes, resolder it.

bye, bastian

[Nguyễn Hồng Quân]

Thank for your care, Bastian.
I found the cause of the problem.

[Bastian Bittorf]

tried increasing the baudrate and found that my router use 115200

good! write a sentence on the wiki:
http://wiki.openwrt.org/toh/d-link/dir-300

bye, bastian