OpenWrt Forum Archive

Topic: Failed to flash! (Code 512) ALSO HERE!

The content of this topic has been archived on 3 Feb 2015. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,
I can not flash any firmware to my WRT54GL, even the original firmware of the linksys! The Kamikaze installed was working well. After first try for firmware flashing, it stopped letting me to telnet to it, from my windows xp. Please help! at least if it is possible to telnet to it ! I tried with tftp to flash the image, also failed (I did not set boot_waite on, I receive "timeout occurred"). Is there any easier way before going for a JTAG firmware flashing?

thank you!

hi

i found a solution how to flash another firmware. i had the same problem.

use putty.exe to login to your router.

then on the command line use following commands.

nvram set boot_wait=on
nvram commit
nvram set wait_time="20"
nvram commit

this will give you enough time to upload the image.

open up two terminal windows on your client (this is only windows sample should work with any client you just have to adjust tftp and ping commands)
this assumes that the router has ip address 192.168.1.1

in one window you enter

ping -t -w 10 192.168.1.1

in the other you prepare your tftp

tftp -i 192.168.1.1 PUT <imagename.bin or trx>

go back to your web interface of the router and reboot

as soon as there is no more ping being returned by the router hit enter in the second terminal window and upload the image.

worked for me.

cheers

ced

I installed KAMIKAZE 8.09rc2, then downloaded the latest svn.

When I try to upgrade the firmware I get the same error message.

I tried the nvram command but it is not part of the default image for rc2. 

I have a Netgear-WGT634U router, what can I do to resolve this problem??

Code 512 is in most cases caused by an invalid firmware image. Please male sure you always upload TRX-files on broadcom.

reaperxtc wrote:

I installed KAMIKAZE 8.09rc2, then downloaded the latest svn.

When I try to upgrade the firmware I get the same error message.

I tried the nvram command but it is not part of the default image for rc2. 

I have a Netgear-WGT634U router, what can I do to resolve this problem??

You cannot flash a wgt634u with tftp put from outside.
Either use luci to flash it (I never tried that myself) or use a serial console (see http://wiki.openwrt.org/OpenWrtDocs/Hardware/Netgear/WGT634U )

I tried using luci and it gives me the 512 error message.

The two options I changed were 2.6 kernel and netgear wireless; than I ran a make; everything compiled fine.

Before I purchase a serial cable, is there anything else I can do?

I winded up compiling a new firmware with the 2.4 kernel for wgt634u router and it took it without giving me an error.

The nvram command is now available and I will try to recompile 2.6 with netgear wireless driver.

I also ordered a cable from Amazon “AUTHENTIC MYBAT BRAND CHARGING USB DATA CABLE + CD DRIVER for SAMSUNG SGH-D807 / SYNC SGH-A707��  in hopes to make a usb to serial adapter.


----------------------------------------------------------------------------------------------------------------------------------
TO DEVELOPERS:

I'm not really sure of the internal workings of openwrt, but I believe there is a signature check for what firmware it will accept and give an error 512 if the signature does not match.

Personally I feel since this router can handle the 2.4 and 2.6 kernel, this signature should be added to both so users are not forced to use the nvram trick to upgrade from a 2.4 kernel to a 2.6 or a usb to serial cable.

I have not tried the nvram trick yet, but hopefully it will work.

(Last edited by reaperxtc on 10 Feb 2009, 00:16)

O well it is stuck in bootwait and I cannot tftp an image to it.

It does have an ip address of 192.168.1.1, hopefully the cable I purchased allows me to fix it.....=(

(Last edited by reaperxtc on 10 Feb 2009, 04:14)

reaperxtc wrote:

O well it is stuck in bootwait and I cannot tftp an image to it.

It does have an ip address of 192.168.1.1, hopefully the cable I purchased allows me to fix it.....=(

I repeat, you cannot flash the wgt634u with tftp put from the outside, you will have to use a serial console cable and do that manually via the console, as described in the wiki. There is no bootwait option on the wgt634u.
Using a 2.4 kernel does not make any sense, nvram variables can be changed in CFE via the serial console, and kamikaze does not use nvram for linux configuration anymore.
Just for info: I am using a Nokia DLR-3P for access to the serial console on various devices (wgt634u, fonera, asus wl-500gd, ...).

I'm wondering at this point if the firmware for 8.02 available in the downloads is based on the 2.4 kernel since when I compiled the 2.6 firmware the router would not accept it. Also the netgear firmware that I downloaded did not have wireless working.


What I should have done was use a tftpd and download the firmware to the netgear router.

(Last edited by reaperxtc on 10 Feb 2009, 22:03)

I think, to get wifi running on the wgt634u, you have to install kmod-madwifi manually, because it's not included in the firmware images.
FYI: the 2.4 kernel images are only for routers with broadcom wifi, because the b43 drivers are not ready for production yet.

The discussion might have continued from here.