New Code to add Support for USR5465

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3
Author Message
stanleyt
DD-WRT Novice


Joined: 09 Feb 2010
Posts: 6

PostPosted: Wed Feb 10, 2010 15:44    Post subject: Reply with quote
modervador wrote:
stanleyt wrote:
Hi modervador,
Glad to hear good news that there is a suitable DD-WRT image for USR5455.
I downloaded the binary file for my USR5455, but failed to upload image neither by TFTP nor command line.(shown at http://www.dd-wrt.com/wiki/index.php/Installation#Method_2:_Flashing_with_TFTP. )
I run the upgrade utility under WinXP SP3.

Would you please show me the installation procedures?

And just in case if I need to restore AP back to factory binary, how should I do with it?
Appreciated!


What is the static IP of your USR5455?

I assigned 192.168.9.191 as its IP address.
It connects under local network.
Sponsor
modervador
DD-WRT User


Joined: 07 Sep 2009
Posts: 270

PostPosted: Wed Feb 10, 2010 17:34    Post subject: Reply with quote
stanleyt wrote:
I assigned 192.168.9.191 as its IP address.
It connects under local network.

OK, I noted you're using WinXPsp3. Set an appropriate static IP address on your PC. Connect the USR5455 directly to the PC, but do not power up the router yet. Open a cmd box and issue the command

ping -t -w 10 192.168.9.191

then power up the router. Copy and post the ping response output beginning with the few seconds before power-up through 10-15 seconds after, when you should be getting responses all with TTL=64.
modervador
DD-WRT User


Joined: 07 Sep 2009
Posts: 270

PostPosted: Wed Feb 10, 2010 18:23    Post subject: Reply with quote
Friends,

The other week I recompiled the firmware for the USR5465/USR5455, which I now make available at this earlier post:

http://www.dd-wrt.com/phpBB2/viewtopic.php?p=387319#387319

It is still at svn13525, but I thought a recompile was worthwhile anyway because as it turns out, I had not put everything needed for CIFS automount into the previous versions. I removed that feature rather than unravel the maze of config and makefiles needed to make it work. I am shifting focus onto how to make DD-WRT reliably detect these routers without requiring my custom builds.

For those who have already flashed the earlier custom version 13525 (2009-12-30), this newer one (2010-01-16) offers no functional advantage except that the "orphaned" parts of CIFS no longer take up space in RAM. For those flashing DD-WRT onto a USR5465/USR5455 for the first time, please use my newest build.
stanleyt
DD-WRT Novice


Joined: 09 Feb 2010
Posts: 6

PostPosted: Thu Feb 11, 2010 13:49    Post subject: Reply with quote
modervador wrote:
Connect the USR5455 directly to the PC, but do not power up the router yet. Open a cmd box and issue the command

ping -t -w 10 192.168.9.191

then power up the router. Copy and post the ping response output beginning with the few seconds before power-up through 10-15 seconds after, when you should be getting responses all with TTL=64.

I've done the first step, below is the output
Quote:

C:\>ping -t -w 10 192.168.9.191

Pinging 192.168.9.191 with 32 bytes of data:

Hardware error.
Hardware error.
Hardware error.
Hardware error.
Hardware error.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.9.191: bytes=32 time=3ms TTL=64
Reply from 192.168.9.191: bytes=32 time<1ms TTL=64
Reply from 192.168.9.191: bytes=32 time<1ms TTL=64
Reply from 192.168.9.191: bytes=32 time<1ms TTL=64
Reply from 192.168.9.191: bytes=32 time<1ms TTL=64
Reply from 192.168.9.191: bytes=32 time<1ms TTL=64
Reply from 192.168.9.191: bytes=32 time<1ms TTL=64
Reply from 192.168.9.191: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.9.191:
Packets: Sent = 19, Received = 8, Lost = 11 (57% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3ms, Average = 0ms
Control-C
^C
modervador
DD-WRT User


Joined: 07 Sep 2009
Posts: 270

PostPosted: Thu Feb 11, 2010 15:35    Post subject: Reply with quote
OK, tftp will not push a firmware onto that IP in the router's current state. Just to verify, you can still access the USRobotics factory firmware web interface of this device at http://192.168.9.191 correct?

Time for the next test.

1. on your PC, set a static IP of 192.168.1.3 / 255.255.255.0

2. now in a cmd box on the PC, issue command

ping -t -w 10 192.168.1.64

3. do the power-on test and post results as before.

This experimentation will help us understand not only the peculiarities of the USR5455, but also how to restore factory firmware or flash a working DD-WRT if the device becomes corrupted. Thanks for your efforts.
stanleyt
DD-WRT Novice


Joined: 09 Feb 2010
Posts: 6

PostPosted: Thu Feb 11, 2010 16:36    Post subject: Reply with quote
modervador wrote:
Time for the next test.

1. on your PC, set a static IP of 192.168.1.3 / 255.255.255.0

2. now in a cmd box on the PC, issue command

ping -t -w 10 192.168.1.64

Hmmm...,I can realize the purpose of test now, although still have no idea why are these steps.

Anyway, I set my IP to 192.168.1.3, then repeat procedures above. Here is the log.
Quote:

C:\>ping -t -w 10 192.168.1.64

Pinging 192.168.1.64 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
.
.
.
.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.64:
Packets: Sent = 32, Received = 0, Lost = 32 (100% loss),
Control-C
^C
JarGer
DD-WRT Novice


Joined: 22 Jan 2010
Posts: 4
Location: Hamburg, Germany

PostPosted: Thu Feb 11, 2010 21:32    Post subject: Reply with quote
hi stanleyt,

try short reset (push reset button for 8 seconds) while ping loop.
stanleyt
DD-WRT Novice


Joined: 09 Feb 2010
Posts: 6

PostPosted: Fri Feb 12, 2010 0:06    Post subject: Reply with quote
JarGer wrote:
hi stanleyt,

try short reset (push reset button for 8 seconds) while ping loop.

Thanks to JarGer.
Maybe I did something wrong at previous test, seems USR5455 responses as expectation this time.
My procedures:
(1)"ping -t -w 10 192.168.1.64" on PC
(2)power on USR5455
(3)(about 10 seconds after,) push USR5455 reset button
The logs are as shown below.
Quote:

C:\>ping -t -w 10 192.168.1.64

Pinging 192.168.1.64 with 32 bytes of data:

Hardware error.
Hardware error.
Hardware error.
Hardware error.
Hardware error.
Hardware error.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.64: bytes=32 time=2ms TTL=100
Reply from 192.168.1.64: bytes=32 time<1ms TTL=100
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Request timed out.
Hardware error.
Hardware error.
Hardware error.
Hardware error.
Hardware error.
Hardware error.
Reply from 192.168.1.64: bytes=32 time=1ms TTL=100
Reply from 192.168.1.64: bytes=32 time<1ms TTL=100
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64
Reply from 192.168.1.64: bytes=32 time=1ms TTL=64
Reply from 192.168.1.64: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.64:
Packets: Sent = 43, Received = 20, Lost = 23 (53% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3ms, Average = 0ms
Control-C
^C
modervador
DD-WRT User


Joined: 07 Sep 2009
Posts: 270

PostPosted: Fri Feb 12, 2010 1:56    Post subject: Reply with quote
JarGer's advice was timely. The reason I didn't recommend the reset button earlier is that if the firmware is in some undefined state, it is foreseeable that you can get locked out from this "single port" router. I was waiting for you to confirm that the USR factory firmware was still working, but you never did.

The tests were to confirm that you can connect to the USR5455 while it is able to accept a firmware flash. You're getting very close now. I believe you had two cycles of

Request timed out. -OR- Hardware error.
...
Reply from 192.168.1.64: bytes=32 time=2ms TTL=100
...
Request timed out.
...
Reply from 192.168.1.64: bytes=32 time=3ms TTL=64
...

The first was from the power-up, then the second from the reset push.

Now, if you want to push the DD-WRT via tftp, you need to start it just before the TTL=100 ping responses begin, certainly no later than they end. Next post will detail how to do this for your USR5455, which I am adapting the procedure from an earlier post of mine regarding the USR5465,

http://www.dd-wrt.com/phpBB2/viewtopic.php?p=345877#345877

Alternatively, if you would rather use the US Robotics factory firmware web interface to install DD-WRT, we could try it that way. In my opinion, it trades one type of complication for another, but some folks might be more comfortable with it anyway.
modervador
DD-WRT User


Joined: 07 Sep 2009
Posts: 270

PostPosted: Fri Feb 12, 2010 2:51    Post subject: Reply with quote
Flashing DD-WRT onto a USR5455 by the "manual TFTP" method.

In this procedure, "router" refers to the USR5455. This router has 4 MB of flash, so DD-WRT mini builds are a good fit. It is assumed that your router is running the latest version of the USRobotics factory firmware which defaults to an IP of 192.168.1.64 / 255.255.255.0, and that your PC is running Windows XP.


PART A. Establish reliable communication with the CFE.

1. power up router and PC, connect router LAN port to PC LAN port.

2. disable all network interfaces on the PC except the one connected to the router. Disable any firewall on that interface.

3. set PC's LAN interface to static IP 192.168.1.3, netmask 255.255.255.0, gateway 192.168.1.64.

4. in a cmd prompt window, ping -t -w 10 192.168.1.64 (i.e. ping the factory default address of the router); response will probably be "Request timed out". Leave the ping running.

5. press and HOLD router's reset button while LEDs cycle through a pattern, finally leaving all LEDs unchanging except for one LAN port LED blinking. Expect it to take 5-10 seconds. Then release the button. (Alternative method: unplug the router's power, wait 5 seconds, then power-up again.)

6. a few seconds after you release the reset button (or power-up) you'll see a few responses like the following:

Reply from 192.168.1.64: bytes=32 time=2ms TTL=100

This means the CFE is able to receive a firmware image via tftp. Yay. After a few more seconds, the ping responses change to TTL=64, indicating the firmware has booted.

7. repeat steps A.5 and A.6 to be sure you get the hang of it and understand the timing of things.


PART B. Do the flash.

1. open a 2nd cmd prompt window into the subdirectory where you saved your DD-WRT firmware .bin file.

2. without hitting <enter>, type

tftp -i 192.168.1.64 PUT dd-wrt.v24_13525-2010-01-16_mini_usb_USR54x5.bin

Maybe you'll substitute a different firmware filename, but remember, don't hit <enter> yet.

3. Just like step A.5, do the 10-second (or power cycle).

4. IMMEDIATELY after you release the reset button (or power-up) hit the <enter> key in the 2nd cmd window to start the tftp command running. In the first cmd prompt window, several ping responses will be seen with TTL=100 while the tftp is active. When the tftp signals a sucessful finish, these ping responses will stop.

5. now that the firmware image is transfered, walk away and do something else for 5 minutes while it is written from RAM to the flash chip.

6. cycle the router power.

7. Since the PC's LAN interface is already a static IP 192.168.1.3, you can browse to http://192.168.1.1 now and you'll see the DD-WRT setup pages. You know what to do next.

8. You'll probably return the PC's LAN interface to DHCP mode after confirming your configuration is good.
stanleyt
DD-WRT Novice


Joined: 09 Feb 2010
Posts: 6

PostPosted: Fri Feb 12, 2010 6:23    Post subject: Reply with quote
Hi modervador,
Thanks for your provided procedures.
Now I am enjoying all new USR5455.
modervador
DD-WRT User


Joined: 07 Sep 2009
Posts: 270

PostPosted: Fri Feb 12, 2010 12:32    Post subject: Reply with quote
You are very welcome. Thank you for your efforts confirming a few things so a written procedure could be possible.
kccoyote
DD-WRT Novice


Joined: 07 Jul 2009
Posts: 12

PostPosted: Sun Apr 11, 2010 22:04    Post subject: Reply with quote
I also successfully tftp-flashed my stock USR5465 with the firmware on these pages, so that's fantastic, but what is the current status on this model?

Is it supported by the standard broadcom builds that are make by Eko now? Or do we need to wait until modervador makes a new build? or?
nrosier
DD-WRT Novice


Joined: 07 Nov 2012
Posts: 1

PostPosted: Wed Nov 07, 2012 15:14    Post subject: Reply with quote
Hi modervador,

any chance on a new build (or some information on how to build my own firmware). I'd like to add IPv6 support which does not seem to be included in your FW.

Rgds,
N.
vismak
DD-WRT Novice


Joined: 28 Jun 2013
Posts: 1

PostPosted: Fri Jun 28, 2013 15:23    Post subject: Reply with quote
Hi, greetings from Greece
Just flashed my 5455 with dd-wrt.v24_13525-2010-01-16_mini_usb_USR54x5.bin but i have no lan access.
From wlan a can login to access point and check that the firmware has been up and running , also lan ip is 192.168.1.1 but cannot access from any class c in the lan.It is not even pingable.The lan led lights up when i connect a lan cable.
I reflashed and made a 30-30-30 reset but the problem remains.
Any sugestions ?

Thank you for your work

update
Finaly worked as repeater , and by clicking wan to switch option
Goto page Previous  1, 2, 3 Display posts from previous:    Page 3 of 3
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum