Posted: Fri Feb 13, 2009 22:36 Post subject: Flashed my WG302 and now it seems bricked
Hi Everyone, I have a WG302V1 and I used the wg302.rmt file via TFTP to flash my unit and after the reboot it just seems to spit out garbage via console then immediately reboot.
It does try to TFTP to the 0.36 address and look for a config.bin file so it seems like this could be recoverable. I've tried renaming the .rmt and .bin files to config.bin to see if those would do the trick but no joy there. I've read through the wikis and searched the site and didn't find anything.
I do see that flashing a WAP is on my own luck but it seems like if you guys got it running on your V1, I should be able to to as well. As long as this thing asks for a flash image I think we're still in business, it is just a matter of making it take a bin file, install it and configure it to work.
Anyway, any advice is certainly appreciated.
thanks in advance!
NOTE: I did use the WG302v1 v24 preSP2 - build 11522 file as per the current instructions.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sun Feb 15, 2009 12:54 Post subject:
it was not me who got it running. one of our users helped me and tested it. but he had problems with the rmt file. so he did manually install it with redboot, since the tftp recovery did not work at all.
so he used the linux.bin file to install it manually with redboot. the procedure is simply the same as for gateworks and other xscale based boards with redboot only installations _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Posted: Thu Feb 26, 2009 13:41 Post subject: Re: i have get a running dd-wrt on wg302 v2
Sash wrote:
dianc wrote:
yesterday i read this topic,and i tryed today,it's run.
my pc ip addesss:192.168.0.250
pc run Tftpd32 : linux.bin in the current directory
connect wg302 v2 with console: 9600-8-N-1-N
reboot wg302 v2
enter the RedBoot console by pressing CTRL+C
this is the command in the console.
--------------
fis init -f
ip_address -l 192.168.0.228/24 -h 192.168.0.250
load -r -b %{FREEMEMLO} linux.bin
fis create linux
fconfig
fis load linux
exec -c "console=ttyS0,9600 root=/dev/mtdblock2"
reset
-------------
for standadrd install its
Code:
fis load linux
exec
I tried your recommendation of "exec" command, but the machine to start the implementation of the 'exec', my console appeared garbled. So I switch to 'exec -c "console=ttyS0,9600 root=/dev/mtdblock2"'
I also own a WG302v2, but unfortunately i don't have a Serial (RS232) wire, so I can't use the console.
I noticed there is also the "wg302v2-webflash-firmware.bin" available. Is it working ? If I flash my router from the web interface with this file, is there any risk of brick ?
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Tue Mar 03, 2009 9:27 Post subject:
consider that dd-wrt uses 115200 baudrate. this is why you saw garbage. but do not use any parameter for exec since the parameters for /dev/mtdblock2 is not enough. rootfstype=squashfs noinitrd is important too
the default dd-wrt commandline which is used without parameters is
"console=ttyS0,115200 panic=10 root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd"
i dont know why your redboot wont support "load". the only one i know who tested this device (and he surelly knows also the installation instructions) is Eko here in this forum _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Just got my hands on one of these AP's. Found some stuff that might help others. To answer pic.micro23 you need to find the start of your free memory address. When you CTRL-C into the console look for
Code:
RAM: 0x00000000-0x10000000, 0x0001f9b8-0x0ffd1000 available
Whatever is in the spot '0x0001f9b8' you need to use as your starting memory address. That was mine.
Now my setup in using this firmware - I have a WG302v1.
Before continuing be sure to reset your AP to default settings
The Setup:
First you will need a Null modem cable to connect to the console. DB9 Female on both ends. Google it.
Connect a Ethernet cable to the ap from your computer and set your IP address as 192.168.0.36
Download the latest version of v24 pre sp2 from brainslayers directory. Here
Install a TFTP client and place linux.bin in its default download directory. Download
Start up hyper terminal and set it to default settings. Connect to the ap with the null modem cable and start listening.
Unplug the ap and plug back. Once plugged back in hit ctrl+c until you get the redboot console.
Make sure your tftp server is started before proceeding.
In the terminal:
1. fis init -f
1a. Answer 'y'
NOTE: 0x01600000 is what I found netgear to be using when installing there own firmware.
2. load -b 0x01600000 -m tftp -h 192.168.0.36 -r linux.bin
3. fis create linux
4. fconfig
4a.When prompted to type a script for bootup type:
fis load -b 0x01600000 linux <press enter>
exec 0x0160004c <press enter, then enter again to finish>
4b. press enter to the rest of the options
5. reset
Disconnect from hyper terminal and setup a new session with a 115 baud rate so the text is readable.
Now you should see it started a wifi connection. Connect to it. Go to 192.168.1.1. What a trial? All things don't come free.
So we made it. From standard crappy netgear firmware to all out pro dd-wrt firmware. You can now upgrade with the web based firmware you probably saw earlier.
Back to the original:
I haven't tried going back to the original firmware but I found this over at dslreports by lemonadesoda:
Quote:
1./ Download WinAgents TFTP Server (demo for 30 days)
2./ Download netgear firmware and save to, e.g. c:\netgear\wg302.rmt
3./ Edit settings in WinAgents so the default virtual directory is now c:\netgear\. Important note, do not set up a second virtual directory
4./ Set PC to 192.168.0.36
5./ Run WinAgents TFTP Server with "local" default settings
6./ Connect ethernet cable
7./ Power off the netgear. Hold down the reset button. Power on the netgear. Wait 5-10 secs before releasing the rest button
8./ Patiently wait about 2 minutes. Watch the "Transfers" console in WinAgents. You should get a log of the downloading process after 1 minute or so.
9./ The device will reboot itself and you will be back online at 192.168.0.228
10./ Phew. Get a drink.
I would recommend setting up hyper terminal so you can see what is happening when reverting back.
Bugs/Problems:
-I have noticed that the WAN port won't get a DHCP address. So a workaround is to just setup a Static Address.
-When wireless channel is set to auto the security set will not be recognized right by clients trying to connect. Be sure to choose a specific channel.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Sun May 03, 2009 15:08 Post subject:
i will take care about the auto channel selection problem. _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s