Airlink101 AR430W/DLINK DIR300 Installation Instructions

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3, 4, 5, 6  Next
Author Message
deaftone
DD-WRT Novice


Joined: 18 May 2007
Posts: 24

PostPosted: Thu Nov 20, 2008 2:35    Post subject: Reply with quote
Wow, thanks for the detailed help, I'll report back with a success story hopefully Smile
Sponsor
Sash
DD-WRT Guru


Joined: 20 Sep 2006
Posts: 17638
Location: Hesse/Germany

PostPosted: Thu Nov 20, 2008 12:28    Post subject: Reply with quote
captainK wrote:
I bailed DD-WRT firmware and went back to Airlink's original, primarily because my AR430W was using RC5 and I could not figure how to safely get to V24.


just follow the instruction in the dl folder and start at fis init and downloading linux kernel and root.fs

_________________
Forum Guidelines...How to get help
&
Forum Rules
&
RTFM/STFW
&
Throw some buzzwords into the WIKI search Exclamation
_________________
I'm NOT rude, just offer pure facts!
_________________
Atheros (TP-Link & Clones, etc ) debrick service in EU
_________________
Guide on HowTo be Safe, Secure and Protect Your Online Anonymity!
deaftone
DD-WRT Novice


Joined: 18 May 2007
Posts: 24

PostPosted: Fri Nov 21, 2008 10:11    Post subject: Reply with quote
Sash, once again you refer to the instructions in the dl folder, but have you read them? They don't contain any info on how to upgrade from an existing dd-wrt install. From my readings around the forums I have found that all you need to do is a web upgrade with the ar430w-firmware.bin from the dl folder, no need to modify redboot or any fis cmds unless you want to complicate things for no reason!!! If you look in the dl folder of either v24(which capitanK was talking about upgrading to from v24-RC5)/v24-sp1/v24-pre-sp2, THEY DO NOT CONTAIN the files you mentioned above (vmlinux.bin.l7 and root.fs), and have not been part of the install since v24-RC6.2!! For a guru you sure don't know much about what you're talking, seems like you just want more posts, how bout you at least get familiar with the contents of the dl folders or the model at hand before spitting out any more useless and misleading information.

Has anyone managed a Dual-WAN link with an ar430w?

Thanks for your info capitanK, worked as far as getting to the recovery page, tried to upload the stock firmware, but even then got errors, so i tried to reupload the v24-sp1 that initially worked.... same endless power cycling...

Code:
== Executing boot script in 1.880 seconds - enter ^C to abort
^C
DD-WRT> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xBFC00000  0x80080000  0x00030000  0xBFC00000
linux             0xBFC30000  0x80041000  0x0037A000  0x80041000
FIS directory     0xBFFE0000  0xBFFE0000  0x0000F000  0x00000000
RedBoot config    0xBFFEF000  0xBFFEF000  0x00001000  0x00000000
DD-WRT>
laserfan
DD-WRT Novice


Joined: 12 Nov 2008
Posts: 29

PostPosted: Fri Nov 21, 2008 14:54    Post subject: Reply with quote
deaftone wrote:
I have completed the steps countless number of times, all I ever get in the end is the box keeps restarting itself, responds _only_ from 192.168.1.1 on LAN and WAN ports

I did similar to you and tried a preSP2 build that didn't work (loaded & ran that is, but didn't function the way I wanted it to). But in my case following donn's instruction above from Step0 recovered me to v24sp1 (having put the matching ar430w-firmware.bin and linux.bin in the tftp directly and renaming all others).

The only departure/oddity is that unlike donn's Step 1, it worked when I was connected to the LAN port. AND I used 192.168.1.1 for the AR430W not 20.81 as stated for getting into RedBoot. Not sure why this worked but I never argue with success.

Make sure you type 'y' when asked, and compare your results detail-for-detail with donn's. If you still have the restarting problem after success with this procedure, then you are left to the mercy of the (much-dreaded, or should I say dreadful) DD-WRT support guys I'm afraid.

P.S. captainK's procedure didn't work for me. At least, I could not get the AR430W to display the Emergency Recovery page at the end. That's probably OK and I read this messes with the units MAC address. Maybe someday someone will figure-out how to recover to Airlink101 firmware perfectly...
deaftone
DD-WRT Novice


Joined: 18 May 2007
Posts: 24

PostPosted: Fri Nov 21, 2008 18:46    Post subject: Reply with quote
Well, all my router would show was the recovery page, tried uploading both 1.01 and 1.02 of the original ar430w firmware, waited the 10min, power cycled, then it would simply boot into recovery mode without having to hold down the reset button anymore. I'll try again and this time post logs. What could be causing this? The mac address did change after flashing the dir300redboot.rom, would that affect anything? What would be some debug cmds to see if the filesystem flashed correctly?

p.s. could it help to specify the base address in each load cmd? (-b?)
Sash
DD-WRT Guru


Joined: 20 Sep 2006
Posts: 17638
Location: Hesse/Germany

PostPosted: Fri Nov 21, 2008 18:51    Post subject: Reply with quote
@deaftone

and again for upgrade to v24 sp1
Sash wrote:
just follow the instruction in the dl folder and do a "fis init" and start at downloading linux kernel and root.fs

_________________
Forum Guidelines...How to get help
&
Forum Rules
&
RTFM/STFW
&
Throw some buzzwords into the WIKI search Exclamation
_________________
I'm NOT rude, just offer pure facts!
_________________
Atheros (TP-Link & Clones, etc ) debrick service in EU
_________________
Guide on HowTo be Safe, Secure and Protect Your Online Anonymity!


Last edited by Sash on Sat Dec 20, 2008 8:25; edited 1 time in total
deaftone
DD-WRT Novice


Joined: 18 May 2007
Posts: 24

PostPosted: Fri Nov 21, 2008 22:20    Post subject: Reply with quote
Sash, read my post and check the dl folders, should I make a file list for you? I'm not here to argue, judge, or favor, I'm just seeking help, and when a "guru" keeps making the same remark, as irrelevant and WRONG as it is, what am I left to do? I have been spending countless nrs of hours reading and reflashing, believe me I know the INSTRUCTIONS a.k.a flashing.txt by heart by now from rc5 to pre-sp2, and this would be what? you're third post on this thread referring to the "instructions"? It is you my friend who should read them and get familiar with what files are used for what versions, if you still don't understand what I'm talking about I can make you a nice little file list from the dl dir's of v24-rc5 up to v24-pre-sp2 and prove to you that 1. it's not a matter of not reading them or not applying correctly. and 2. as I said in my last post
deaftone wrote:
If you look in the dl folder of either v24(which capitanK was talking about upgrading to from v24-RC5)/v24-sp1/v24-pre-sp2, THEY DO NOT CONTAIN the files you mentioned above (vmlinux.bin.l7 and root.fs), and have not been part of the install since v24-RC6.2!!


So what are you even talking about when you say...
Sash wrote:
just follow the instruction in the dl folder and start at fis init and downloading linux kernel and root.fs


Those files are no longer being used... hence linux.bin, try being a little more specific if I'm wrong.

Anyways, I do appreciate all the work you probably put in throughout the yrs, and I'm not here to bash on people, I need a direct answer, short n simple. Don't keep telling me to read the instructions when that's not the problem, believe me, I'm not that slow, as to not being able to read some instructions, of course anyone in their right mind would read them before proceeding; and over n over again upon failing, but when they don't supply an answer to my question and you seem to keep pointing me back to them... wtf. So here's some debugs for ya, _this_ is what I need help with, _not_ reading.
deaftone
DD-WRT Novice


Joined: 18 May 2007
Posts: 24

PostPosted: Fri Nov 21, 2008 22:23    Post subject: Reply with quote
Started recovery process as captainK mentioned...

Code:
DD-WRT> ^C
DD-WRT> ip_address -h 192.168.1.23
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.23
DD-WRT> fconfig -i
Initialize non-volatile configuration - continue (y/n)? y
Run script at boot: false
Use BOOTP for network configuration: true
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)?
DD-WRT> ip_address
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.23
DD-WRT> fconfig -i
Initialize non-volatile configuration - continue (y/n)? y
Run script at boot: false
Use BOOTP for network configuration: true
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> ip_address
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.23
DD-WRT> fconfig bootp false
bootp: Setting to false
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fis init
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> load -r -b %{FREEMEMLO} dir300redboot.rom
Using default protocol (TFTP)
Raw file loaded 0x80040800-0x800607ff, assumed entry at 0x80040800
DD-WRT> fis create -l 0x30000 -e 0xbfc00000 RedBoot
An image named 'RedBoot' exists - continue (y/n)? y
... Erase from 0xbfc00000-0xbfc30000: ...
... Program from 0x80040800-0x80060800 at 0xbfc00000: ..
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> reset



*
All ram/flash addresses above match to captainK's and everything worked fine so far...
Then I waited for the router to reboot and opened a telnet session on 192.168.20.81:9000
next I pulled up http://192.168.20.81 and the emergency web server was already running but it won't accept an
uploads unless you hold down the reset button for ~30s on boot first, so why is it even running?
Not that it really matters, I just wanted to get the RedBoot version output before starting to upload the firmware.
*

Code:
== Executing boot script in 0.980 seconds - enter ^C to abort
^C
RedBoot> version
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Version: "RedBoot v2.3"
RAM: 0x80000000-0x80800000, [0x80036350-0x807ed000] available
FLASH: 0xbfc00000 - 0xbfff0000, 64 blocks of 0x00010000 bytes each.
RedBoot>


*
I unplugged the router and started the recovery process holding the reset button, on boot I sniffed this out before
I started uploading with wireshark:
*

Code:
6842   2291.489952   D-Link_40:81:82   Broadcast   ARP   Who has 192.168.20.80?  Tell 192.168.20.81
6843   2291.489969   QuantaCo_91:3c:5b   D-Link_40:81:82   ARP   192.168.20.80 is at 00:1e:68:91:3c:5b
6844   2291.490722   192.168.20.81   192.168.20.80   TFTP   Read Request, File: COBRAART.SYS\000, Transfer type: OCTET\000
6845   2291.497680   192.168.20.80   192.168.20.81   TFTP   Error Code, Code: File not found, Message: File not found\000


*
Is COBRAART.SYS something I should worry about?
then...
- loaded http://192.168.20.81 and let go of the reset button
- began uploading ar430w_v1_02_8949.bin which is the latest firmware release (v1.02) by airlink for the ar430w
- ~ ten min later, browser forwarded to http://192.168.20.81/OK.html when the upload was complete saying the update
was successful, or at least it seemed to think so.

So then I, set local ip to 192.168.1.2/255.255.255.0, unplugged power cord/plugged back in after about 10-15s

On boot:
- LAN ports don't even work at this point... "Cable unplugged"
- It does not respond to 192.168.1.1 on WAN port, it sticks to 192.168.20.81 and "looks for .20.80"
- Tries to request COBRAART.SYS from .20.80 once again and fails. (tftp)
- Emergency Web Server is running once again.
- Port 9000 is open and taking connections so I started a session.
*

Code:
^C
RedBoot> version
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Version: "RedBoot v2.3"
RAM: 0x80000000-0x80800000, [0x80036350-0x807ed000] available
FLASH: 0xbfc00000 - 0xbfff0000, 64 blocks of 0x00010000 bytes each.
RedBoot>


If I ping 192.168.20.81 then errors appear in the telnet session.

Code:
RedBoot> /releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send

AHB ERROR: AR531X_DEBUG_ERROR = 0000c34f
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR

status_4 = 00000145

RedBoot>


=========================================================================
At this point I repeated the recovery method with the other official airlink
firmware release wrgg23_airlink_ar430w_v1.01_77ak (v1.01) and got the same results.

The telnet session while pinging box after another supposed "successful flash" through the recovery method using the web server and firmware v1.01

{code]^C
RedBoot> version
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Version: "RedBoot v2.3"
RAM: 0x80000000-0x80800000, [0x80036350-0x807ed000] available
FLASH: 0xbfc00000 - 0xbfff0000, 64 blocks of 0x00010000 bytes each.
RedBoot>
RedBoot> /releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB

ERROR: AR531X_DEBUG_ERROR = 0000c34f
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR

status_4 = 00000555
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR:

AR531X_DEBUG_ERROR = 00000555
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR

status_4 = 00000145

RedBoot> /releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB

ERROR: AR531X_DEBUG_ERROR = 0000c34f
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR

status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR:

AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR

status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR:

AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR

status_4 = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR:

AR531X_DEBUG_ERROR = 00000145
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR

status_4 = 00000145

RedBoot>[/code]
===================================================================

What the hell is going on!?@&^#% This has been driving me nuts for the past week and a half!*&@^# Is this a bootloader prob or flash prob? When it seems like it simply won't flash/load a given firmware.
Does anyone know what that tftp request for COBRAART.SYS is about?
Once again, thanks in advance and any help would be greatly appreciated!

Now I'm off to a nice quiet cigarette break, later tonight I'll post some logs from trying to flash v24-sp1, and from what I caught there was an address mismatch, which is what I was asking about earlier.
captainK
DD-WRT Novice


Joined: 16 Jan 2008
Posts: 17

PostPosted: Sat Nov 22, 2008 3:12    Post subject: AR430W original firmware Reply with quote
When you get to the Emergency Recovery screen, you browse for the Airlink firmware that you dled from their website,(in my case v1.02) and click upload, mine said uploading or flashing or something like that and told me to wait ~ 510 seconds.....then said complete. I pulled the power. I reset my NIC to 192.168.1.2 / 255.255.255.0 and moved the Cat5 cable to the LAN port and opened my browser to 192.168.1.1 and presto, I was in the Airlink setup utility. Perfect, and tested for two days on my network, and even with an AR431W repeater doing wireless and Perfect....no hiccups....perfect. That recycling of power/connection you speak of reminds me of the stock AR431W repeaters acknowledged problems that are fixed with Airlink's firmware upgrade. Remember:
AR430W = Router with 4 port switch
AR431W = Repeater/Bridge/AP with ONE LAN port
Sash
DD-WRT Guru


Joined: 20 Sep 2006
Posts: 17638
Location: Hesse/Germany

PostPosted: Sat Nov 22, 2008 8:46    Post subject: Reply with quote
Sash wrote:
@deaftone

and again for upgrade to v24 sp1
Sash wrote:
just follow the instruction in the dl folder and start at fis init and downloading linux kernel and root.fs


Code:
connect to the bootloader with telnet on port 9000 and ip 192.168.1.1

now do the following: (consider that fis create operations are taking sometimes several minutes to finish)
[b]fis init[/b]
load -r -b 0x80041000 linux.bin
fis create linux

now type reset again. the unit should now boot dd-wrt and work as known from other atheros based platforms

-------------------------------------------------------------------------------------------------------------------
Appendix:
download putty.exe to c:\
create a file an c:\ called redboot.bat with the following content:

rem echo off
:start
rem ------------------------------------------------
ping 192.168.20.81 -n 1 -w 1 > NULL
IF ERRORLEVEL 1 goto start

rem putty
rem ------------------------------------------------
break
putty.exe telnet://192.168.20.81:9000 -m redboot.txt
exit


create a file on c:\ called redboot.txt with the following content:

^C


start the bat file and power on the router.....here comes redboot

_________________
Forum Guidelines...How to get help
&
Forum Rules
&
RTFM/STFW
&
Throw some buzzwords into the WIKI search Exclamation
_________________
I'm NOT rude, just offer pure facts!
_________________
Atheros (TP-Link & Clones, etc ) debrick service in EU
_________________
Guide on HowTo be Safe, Secure and Protect Your Online Anonymity!
deaftone
DD-WRT Novice


Joined: 18 May 2007
Posts: 24

PostPosted: Wed Nov 26, 2008 8:32    Post subject: Reply with quote
I am not trying to upgrade Sash, I am simply trying to get something running on this box. Either stock or dd-wrt, doesn't matter because at this point there's noting running on it and it won't take a flash! Haven't messed with it in days because I was about to crush the damn thing having taken me a week to try and figure out what went wrong from a perfectly fine v24-sp1 being upgraded to v24-pre-sp2 and on first boot, kaput!, followed all available and applicable instructions off the forum step by step, and honestly, I can't figure it out! How would I simply format everything and start fresh? Does dd-wrt replace the redboot bootloader or mod it and expect that it was already in a working stage? What could be stopping it from loading the filesystem on boot considering all went well? How should I set static ip's in the last "fconfig" after entering the boot script? Is there a 3x1000ms delay between the filesystem being loaded and executed or if not, what for? Could it be increased to 5 be on the safe side? Tried flashing from Vista and XP, successfully flashed v24-sp1 on it initially, ran stable for 3 days, upgraded to v24-pre-sp2, loaded fine on first boot, moded settings, rebooted fine, then I went to reset to defaults, and would not boot ever since.

Do I need to format flash? Clear any type of cache in ram? Delete nvram? How can I completely wipe it and start fresh really?

Does anyone know where to find the original redboot bootloader for the ar430w, I know it's the same chipset and all as the dir-300, but maybe that could be a reason for fault in my case since I could not even revert using capitanK's instructions and on boot after I load that dir300redboot.rom it tries to request that COBRAART.SYS file from the tftp server on .20.80, what is that all about?
deaftone
DD-WRT Novice


Joined: 18 May 2007
Posts: 24

PostPosted: Wed Nov 26, 2008 17:27    Post subject: Reply with quote
How do I restore from this point?
Looks like somehow the whole router config got deleted... no radio or board config after that 'reset to defaults' in v24-pre-sp2, what should I do?


Code:

DD-WRT> version

RedBoot(tm) bootstrap and debug environment [ROMRAM]
production release, version "2.1.3" - built 18:43:19, Sep 20 2007

Platform: ap61 (Atheros WiSOC)
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
Copyright (C) 2007, NewMedia-NET GmbH.

Board: DLINK DIR-300
RAM: 0x80000000-0x81000000, [0x80040580-0x80fe1000] available
FLASH: 0xbfc00000 - 0xbfff0000, 64 blocks of 0x00010000 bytes each.
DD-WRT> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xBFC00000  0x80080000  0x00030000  0xBFC00000
linux             0xBFC30000  0x80041000  0x00395000  0x80041000
FIS directory     0xBFFE0000  0xBFFE0000  0x0000F000  0x00000000
RedBoot config    0xBFFEF000  0xBFFEF000  0x00001000  0x00000000
DD-WRT> fis list -d
Name              FLASH addr  Mem addr    Datalen     Entry point
RedBoot           0xBFC00000  0x80080000  0x00028718  0xBFC00000
linux             0xBFC30000  0x80041000  0x00395000  0x80041000
FIS directory     0xBFFE0000  0xBFFE0000  0x00000000  0x00000000
RedBoot config    0xBFFEF000  0xBFFEF000  0x00000000  0x00000000
DD-WRT> bdrestore
Board config  found at 0xbff90000
No board config data found!
DD-WRT>

Code:
DD-WRT> x -b 0x80041000 -l 0x00000100
80041000: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
80041010: 00 08 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
80041020: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
80041030: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
80041040: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
80041050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
80041060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
80041070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
80041080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
80041090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
800410A0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
800410B0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
800410C0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
800410D0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
800410E0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
800410F0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
DD-WRT> x -b 0xbfc30000 -l 0x00000100
BFC30000: 6D 00 00 80 00 3C 15 29  00 00 00 00 00 00 04 02  |m....<.)........|
BFC30010: 96 00 0E 0F F8 3F D5 D1  50 C7 E1 D5 37 C0 34 84  |.....?..P...7.4.|
BFC30020: 0C 61 30 4C 79 46 3F B8  56 DA CF 30 74 25 6E F7  |.a0LyF?.V..0t%n.|
BFC30030: 2A F8 AF 2D B3 41 30 3B  58 C6 85 3A F2 41 23 D9  |*..-.A0;X..:.A#.|
BFC30040: 92 03 8C 99 9A B9 4C CF  A7 82 7D 66 C1 A0 7B 28  |......L...}f..{(|
BFC30050: 84 4F 08 B5 19 DD F3 5B  5D F6 F4 E5 3F 38 05 C4  |.O.....[]...?8..|
BFC30060: 3D E1 6B B1 FF 1F 96 53  68 92 98 2E B9 24 9C 31  |=.k....Sh....$.1|
BFC30070: 68 B7 0A 0D 1D 64 E7 78  9A 76 09 20 FB B2 2E 8D  |h....d.x.v. ....|
BFC30080: 83 A6 09 3A 46 09 37 6C  44 0A D6 DE E5 0C 38 9C  |...:F.7lD.....8.|
BFC30090: AF 21 BC 98 04 2F 06 90  D0 6A CC 7C F6 DA 64 4A  |.!.../...j.|..dJ|
BFC300A0: 6C 4C AA 03 16 8B EC 8D  AB 04 28 DA C5 B1 08 9D  |lL........(.....|
BFC300B0: 83 EA 6C DB 72 02 98 FF  6E 43 05 75 6E 11 06 18  |..l.r...nC.un...|
BFC300C0: DC 88 C5 18 ED FD 0A DC  95 B4 2C 62 E5 99 EF 12  |..........,b....|
BFC300D0: 2D 8D BB B4 7A 86 03 2C  07 9F 8D 7D 4C 94 E4 82  |-...z..,...}L...|
BFC300E0: 5E 5A 59 76 33 A8 89 98  C3 64 C5 07 5C BB 66 FC  |^ZYv3....d..\.f.|
BFC300F0: F3 13 51 DC 1D EC C5 57  1B F8 D1 E5 78 9C D2 3B  |..Q....W....x..;|
DD-WRT>


board info:
Code:

== Executing boot script in 0.250 seconds - enter ^C to abort
^C
DD-WRT> dump -b 0xbfff0000 -l 0x7f
BFFF0000: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0010: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0020: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0030: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0040: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0050: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0060: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0070: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF     |............... |
DD-WRT> dump -b 0xbfff0000 -l 0xf8
BFFF0000: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0010: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0020: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0030: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0040: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0050: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0060: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0070: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0080: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0090: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF00A0: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF00B0: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF00C0: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF00D0: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF00E0: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF00F0: FF FF FF FF FF FF FF FF                           |........        |

radio config:
Code:
DD-WRT> dump -b 0xbfff00f8 -l 0x200
BFFF00F8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0108: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0118: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0128: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0138: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0148: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0158: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0168: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0178: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0188: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0198: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF01A8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF01B8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF01C8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF01D8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF01E8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF01F8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0208: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0218: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0228: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0238: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0248: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0258: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0268: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0278: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0288: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF0298: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF02A8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF02B8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF02C8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF02D8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
BFFF02E8: FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF  |................|
DD-WRT>


boot script:
Code:

DD-WRT> dump -b 0xBFFEF000 -l 0x60
BFFEF000: 00 00 10 00 0B AD FA CE  01 0C 01 00 62 6F 6F 74  |............boot|
BFFEF010: 5F 73 63 72 69 70 74 00  00 00 00 01 04 11 01 0C  |_script.........|
BFFEF020: 62 6F 6F 74 5F 73 63 72  69 70 74 5F 64 61 74 61  |boot_script_data|
BFFEF030: 00 62 6F 6F 74 5F 73 63  72 69 70 74 00 66 69 73  |.boot_script.fis|
BFFEF040: 20 6C 6F 61 64 20 2D 6C  20 6C 69 6E 75 78 0A 65  | load -l linux.e|
BFFEF050: 78 65 63 0A 00 00 00 00  00 00 00 00 00 00 00 00  |xec.............|
DD-WRT>

These logs were made after completing all the flashing steps for v24-sp1 as stated in flashing.txt. The memory addresses are just what I managed to pull up from an openwrt thread but should still apply, correct me if I'm wrong. What do I need to do at this point in order to restore? See Sash, it had nothing to do with "following the instructions in the dl folder", but I would still greatly appreciate your help or anyone elses! At least after a week of bullshittin I finally know what the problem is, *phew*, now for the solution Very Happy
Sash
DD-WRT Guru


Joined: 20 Sep 2006
Posts: 17638
Location: Hesse/Germany

PostPosted: Mon Dec 22, 2008 9:53    Post subject: Reply with quote
i flash about 20 dir300 and never run into such problems. so there must be gone something wrong on your side.

what is happening when u try to flash ddwrt again with my instruction above? ddwrt reboot is running ok so far?

_________________
Forum Guidelines...How to get help
&
Forum Rules
&
RTFM/STFW
&
Throw some buzzwords into the WIKI search Exclamation
_________________
I'm NOT rude, just offer pure facts!
_________________
Atheros (TP-Link & Clones, etc ) debrick service in EU
_________________
Guide on HowTo be Safe, Secure and Protect Your Online Anonymity!
ftusa2
DD-WRT Novice


Joined: 12 Feb 2009
Posts: 8

PostPosted: Thu Feb 12, 2009 1:57    Post subject: Urgent SOS ! Reply with quote
I was using this post http://micront.com/howto/routers/airlink101-ar430w/flashing-ar430w-with-dd-wrt.html, which is so clear and easy to follow, everything is fine, but now the PuttyTel died out at bellow step.

DD-WRT> load -r -v -h 192.168.1.23 -b 0x80041000 linux.binÅ

--------------------------------------------------------------------------------

Raw file loaded 0x80041000-0x803cffff, assumed entry at 0x80041000--------------

DD-WRT> ------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------


Because after I run the command, I found it need to set a 5 sec keep alive option, however, I tried, but the pannel does NOT have "Apply" botton, but still is "Open" instead.....

Now the router is a brick ? How can I get it back on track?
oldbud
DD-WRT Novice


Joined: 06 Feb 2009
Posts: 1

PostPosted: Thu Feb 12, 2009 9:28    Post subject: Reply with quote
thisisunsane wrote:

The ones that I found didn't have the current file names and didn't discuss how to get Tftp running in a clear manner. As I said, my instructions were just updates and clarifications. That thread did come up in my google search.

What are the two versions of the AR430W? I have run across two, myself, one that comes with a 5v power supply and has a little button on the side and one that has a 12v power supply and doesn't have that button. I was able to install DD-WRT on both with the same procedure. I'd like to know what other versions I may run into and what differences in procedure would be required as I have six more of these sitting, unopened, awaiting DD-WRT.

Thank you.
AFAIK the button is available on both, from opening my older/newer boxes, but the ones shipped with a 5v source have a newer case with access to the button.

Both motherboards have 5v printed on it, and according to Airlink Support:
Quote:
Q) Does it matter which power supply can be connected to which router (AR430W)???

A) It does not matter which power supply the router came with 5v or 12v. The router was built to auto sense a 12v input or a 5v input. So regardless 12v or 5v the router will still work and won't burn. We just started to use the 5v to save on shipping cost due to weight.
Goto page Previous  1, 2, 3, 4, 5, 6  Next Display posts from previous:    Page 4 of 6
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC 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 cannot attach files in this forum
You cannot download files in this forum