WZR-HP-G300NH bricked after a successful DD-WRT installation

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware
Author Message
smacker
DD-WRT Novice


Joined: 09 May 2010
Posts: 7
Location: Japan

PostPosted: Sat May 15, 2010 19:07    Post subject: WZR-HP-G300NH bricked after a successful DD-WRT installation Reply with quote
Hi everyone,

I used to use my WZR-HP-G300NH with Japanese firmware until last week.

Then, tried the wzrg300nh-firmware_MULTI.bin to install ddwrt from web interface of stock firmware. It worked fine. I started to use it and tried for 1 week.

Yesterday, tried to revert the stock firmware (English one - Brainslayer's) from ddwrt web interface. After installation, router went into an infinite loop with "double blinking" red led (dunno the name, the one like a gear) on every 3 seconds. (not reboots itself, just led double blinks) I have checked other topics but those seem to me different.

It's not 'ping'able now.
I can reach the device over tftp and could install the below mentioned firmwares. But any of them differs.

    wzrg300nh-firmware_MULTI.bin (Brainslayer's)
    wzrg300nh_original.bin (Brainslayer's)
    buffalo_to_ddwrt_webflash-MULTI.bin (Brainslayer's)
    openwrt-ar71xx-wzr-hp-g300nh-squashfs-tftp.bin
    wzrhpg300nh-172 (Original Buffalo Firmware - English)
    wzrhpg300nh-174 (Original Buffalo Firmware - English)
    wzrhpg300nh-165 (Original Buffalo Firmware - Japanese)
    wzrhpg300nh-174 (Original Buffalo Firmware - Japanese)


TFTP log is attached.

As a result, it seems like bricked. It's a Japanese one and has the A0 A1 serial number on it. (Hope this makes some sense)

Is there someone who has the same issue or knows a way to overcome please?

Thanks
Sponsor
nareshseep
DD-WRT Novice


Joined: 06 Apr 2010
Posts: 7

PostPosted: Sun May 23, 2010 0:07    Post subject: Reply with quote
you can still resuscitate your wireless router, my router came DOA from AMAZON and after 10hrs of continuous research I got it up and running.

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

What you have to be quick about is that when you have plugged in the power to the router, you need to run the arp command at the same time, so that the pc can find the router via mac address. This window is about 2-3 seconds by my estimates for the router to accept a tftp connection. BTW I have the A0 D0 revision of the Buffalo WZR-HP-300NH .
smacker
DD-WRT Novice


Joined: 09 May 2010
Posts: 7
Location: Japan

PostPosted: Sun May 23, 2010 7:07    Post subject: Reply with quote
But the problem is I can do tftp and it works, but nothing was changed.
I did the procedures and catch the correct timing to tftp the firmware. it was ok, but then nothing happened. You can see the tftp log from the first post.
Do you still recommend me to do the same thing again and again?
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7631

PostPosted: Sun May 23, 2010 9:54    Post subject: Reply with quote
smacker wrote:
But the problem is I can do tftp and it works, but nothing was changed.


The problem is that you have not connected a serial terminal to the router so you can see what happens on that side.

The long log you provided is basically worthless, it only shows that the file was transferred ok but you have no idea of what happened on the other side.

_________________
Kernel panic: Aiee, killing interrupt handler!
smacker
DD-WRT Novice


Joined: 09 May 2010
Posts: 7
Location: Japan

PostPosted: Sun May 23, 2010 10:09    Post subject: Reply with quote
So, keep trying again and again?
buddee
DD-WRT Guru


Joined: 06 Feb 2010
Posts: 7401
Location: Little Rock

PostPosted: Sun May 23, 2010 10:20    Post subject: Reply with quote
you can keep trying again and again, but what LOM is saying is if you dont ttl to your unit and find out whats going on, you probably wasting your time, thus will end in the same result, however if you get a serial connection into your unit, then post that here, then maybe could better know whats up with it.
_________________
Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ

Having problems with port forwarding? Check out Port Forward Troubleshooting for more info.
smacker
DD-WRT Novice


Joined: 09 May 2010
Posts: 7
Location: Japan

PostPosted: Wed May 26, 2010 9:00    Post subject: Reply with quote
Thanks for the comments.

I made the serial connection with a simple max232. And here is the log when i tftp the image. It gives a Bad Data CRC error.

Code:


BUFFALO U-BOOT Ver 1.02
AP83--539 (ar9100) U-boot 0.0.12
64 MB
Memory Test (address line)
Memory Test start(0x00000000) end(0x04000000) size(67108864)
Data line test start:0x00000000 pattern 0x00000001 0x00000003 0x00000007 0x0000000F 0x00000005 0x00000015 0x00000055 0xAAAAAAAA
Address line test start:0x00000000 len:0x4000000 pattern 0xAAAAAAAA 0x55555555 
Fill test patnum:5
fill Pattern 5555AAAA  Writing...             \0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08Reading...
fill Pattern AAAA5555  Writing...             \0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08Reading...
fill Pattern 0000FFFF  Writing...             \0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08Reading...
fill Pattern FFFF0000  Writing...             \0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08Reading...
fill Pattern AAAAAAAA  Writing...             \0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08Reading...
Top of RAM usable for U-Boot at: 84000000
Reserving 250k for U-Boot at: 83fc0000
Reserving 256k for malloc() at: 83f80000
Reserving 44 Bytes for Board Info at: 83f7ffd4
Reserving 36 Bytes for Global Data at: 83f7ffb0
Reserving 128k for boot params() at: 83f5ffb0
Stack Pointer at: 83f5ff98
Now running in RAM - U-Boot at: 83fc0000
Dev ID2:2222
Name: AMD-SPANSION Flash id: 0x1227E, Size: 33554432 bytes.
Flash: 32 MB
In:    serial
Out:   serial
Err:   serial
Memory Test
uboot use  83F5FFB0 - 84000000
Memory Test start(80000000) end(83F00000) size(03F00000)
Pattern 55555555  Writing...            \0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08Reading...Pattern AAAAAAAA  Writing...            \0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08Reading...Pattern 00000000  Writing...            \0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08\0x08Reading...
Memory Test OK
### buf_ver=[1.02] U-Boot Ver.=[1.02]
### build_date(env)=[Feb 16 2009 - 10:47:08] build_date(bin)=[Feb 16 2009 - 10:47:08]
ag7100_enet_initialize...
: cfg1 0xf cfg2 0x7114
rtl8366sr_phy_setup  ethUnit=0
Realtek 8366SR switch ID 0x8366
Realtek Greeen Ethernet Setup
eth0: 02:aa:bb:cc:dd:1a
eth0 up
: cfg1 0xf cfg2 0x7114
eth1: 02:aa:bb:cc:dd:1a
eth1 up
eth0  02:AA:BB:CC:DD:1A
, eth1  02:AA:BB:CC:DD:1A

Trying eth0
eth0 is duplex
ag7100_check_link: _100BASET
dup 1 speed 100
CFG_PLL_FREQ=5
CFG_HZ=bebc200
cpu pll=1050
eth pll=1032
eth0 clk pll=13000a44
eth0 mii=12
eth0 cfg1=f
eth0 cfg2=7115
eth0 fcfg_0=1f1f00
eth0 fcfg_1=7ff0000
eth0 fcfg_2=fff
eth0 fcfg_3=780008
eth0 fcfg_4=3ffff
eth0 fcfg_5=3ffff

tftp server(receive) go, waiting:4[sec]
Trying eth1
eth1 link down
FAIL
Trying eth0
eth0 is duplex
ag7100_check_link: _100BASET
Load address: 0x81f00000
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
\0x09 $$$$$$$$$$$
tftp server done
Bytes transferred = 20685004 (13ba0cc hex)
## Booting image at be060000 ...
   Image Name:   Linux Kernel Image
   Created:      2009-09-25  12:49:22 UTC
   Image Type:   MIPS Linux Kernel Image (gzip compressed)
   Data Size:    21168064 Bytes = 20.2 MB
   Load Address: 80002000
   Entry Point:  80200000
   Verifying Checksum ... Bad Data CRC
 # LED(0x2) Blink[2] (Please press 'Ctrl+c' to stop)


Here is where the led double blinks. When I press ctrl+c here, it continues like this;

Code:

OK
   Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 80200000) ...
## Giving linux memsize in bytes, 67108864

Starting kernel ...

Linux version 2.6.15 (vc03021@mkitec-xen) (gcc version 3.4.4) #1 Fri Sep 25 21:22:43 JST 2009
flash_size passed from bootloader = 32
arg 1: console=ttyS0,115200
arg 2: root=31:03
arg 3: rootfstype=jffs2
arg 4: init=/sbin/init
arg 5: mtdparts=ar9100-nor0:256k(u-boot),128k(u-boot-env),1024k(uImage),31104k(rootfs),128k@32640k(ART),128k@32512k(properties)
arg 6: mem=64M
use [CONFIG_CMDLINE] = console=ttyS0,115200 root=31:03 rootfstype=squashfs init=/sbin/init mtdparts=ar9100-nor0:256k(uboot),128k(uboot_environ),1024k(linux),31104k(rootfs),128k@32640k(ART),128k@32512k(user_property),32128k@384k(firmware) mem=64M
CPU revision is: 00019374
Determined physical RAM map:
 memory: 02000000 @ 00000000 (usable)
User-defined physical RAM map:
 memory: 04000000 @ 00000000 (usable)
Built 1 zonelists
Kernel command line: console=ttyS0,115200 root=31:03 rootfstype=squashfs init=/sbin/init mtdparts=ar9100-nor0:256k(uboot),128k(uboot_environ),1024k(linux),31104k(rootfs),128k@32640k(ART),128k@32512k(user_property),32128k@384k(firmware) mem=64M
Primary instruction cache 64kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
Cache parity protection disabled
PID hash table entries: 512 (order: 9, 8192 bytes)
Using 200.000 MHz high precision timer.
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 62536k/65536k available (1698k kernel code, 2940k reserved, 337k data, 108k init, 0k highmem)
Mount-cache hash table entries: 512
Checking for 'wait' instruction...  available.
NET: Registered protocol family 16
SCSI subsystem initialized
AR7100 GPIOC major 0
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
squashfs: LZMA suppport for slax.org by jro
Initializing Cryptographic API
io scheduler noop registered
io scheduler deadline registered
HDLC line discipline: version $Revision: #1 $, maxframe=4096
N_HDLC line discipline registered.
mel_initsw initialized.
Serial: 8250/16550 driver $Revision: #1 $ 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x0 (irq = 19) is a 16550A
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE compression module registered
NET: Registered protocol family 24
AR9100 FLASH DRIVER found device
  vendor 0x1   device-id 0x227e, 0x2222, 0x2201
FLASH ID: S29GL256N SIZE: (32 MB)
7 cmdlinepart partitions found on MTD device ar9100-nor0
Creating 7 MTD partitions on "ar9100-nor0":
0x00000000-0x00040000 : "uboot"
0x00040000-0x00060000 : "uboot_environ"
0x00060000-0x00160000 : "linux"
0x00160000-0x01fc0000 : "rootfs"
0x01fe0000-0x02000000 : "ART"
0x01fc0000-0x01fe0000 : "user_property"
0x00060000-0x01fc0000 : "firmware"
u32 classifier
    OLD policer on
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
ip_conntrack version 2.4 (512 buckets, 4096 max) - 212 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_time loading
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
ar7100wdt_init: Registering WDT success
SQUASHFS error: sb_bread failed reading block 0x4c8e
SQUASHFS error: Unable to read cache block [1323b07:1025]
SQUASHFS error: Unable to read inode [1323b07:1025]
VFS: Cannot open root device "31:03" or unknown-block(31,3)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)


I have tried a couple of firmwares. Please give me some more advice.
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7631

PostPosted: Fri May 28, 2010 6:30    Post subject: Reply with quote
I don't think, by the look of your serial log, that the firmware you download by tftp gets written to the flash, it looks like it is booting the old corrupted firmware that it has in flash, the Linux kernel you have uploaded has a UTC time stamp but the kernel you are booting has JST time stamp.
There is normally, after a tftp transfer, a long row of symbols showing the write to the individual flash sectors, similar to the big block showing the tftp transfer.

Your U-Boot version is of an older kind which I don't have so I can not see if the tftp command was flawed in the old version or not implemented in the same way.
You can Ctrl-C at an earlier stage and get a U-Boot prompt, then type help to see the available boot and flash commands.

_________________
Kernel panic: Aiee, killing interrupt handler!
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7631

PostPosted: Fri May 28, 2010 19:38    Post subject: Reply with quote
See this link for a similar case, also U-Boot 1.02

http://scarygliders.net/?p=13

_________________
Kernel panic: Aiee, killing interrupt handler!
smacker
DD-WRT Novice


Joined: 09 May 2010
Posts: 7
Location: Japan

PostPosted: Sun May 30, 2010 16:32    Post subject: Reply with quote
Good news!

That method worked well. I'm on DD-WRT again.

Thank you all, for your help.

Here is the schematics I used :


And the one I made is attached below.

One more question I have. Just out of curiosity.
This magic number sequence exists at the almost beginning of DD-WRT image. So I deleted the first part of the image. Otherwise UBoot does not allow it to boot.

But, the original image file from buffalo does not have this magic number at the beginning. Besides, I searched for it but it doesn't exist in the original image file. How come this could be? Because at first I tried to get the original buffalo firmware back. But didn't work. Still gave me the same error. (Bad Data CRC)
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7631

PostPosted: Sun May 30, 2010 17:13    Post subject: Reply with quote
smacker wrote:


One more question I have. Just out of curiosity.
This magic number sequence exists at the almost beginning of DD-WRT image. So I deleted the first part of the image. Otherwise UBoot does not allow it to boot.

But, the original image file from buffalo does not have this magic number at the beginning. Besides, I searched for it but it doesn't exist in the original image file. How come this could be? Because at first I tried to get the original buffalo firmware back. But didn't work. Still gave me the same error. (Bad Data CRC)


The dd-wrt image is in Buffalo Open F/W format and later versions of the U-Boot understands that format, looks like your ver 1.02 does not have it implemented.

The header should be stripped off by the tftp client in U-Boot before the image is written to disk.
You have done that manually now. Smile

Buffalo's original firmware is in encrypted format so you will not see the 27 05 19 56 until it has been decrypted and later U-Boot versions does also accept the encrypted format via tftp.

_________________
Kernel panic: Aiee, killing interrupt handler!
smacker
DD-WRT Novice


Joined: 09 May 2010
Posts: 7
Location: Japan

PostPosted: Sun May 30, 2010 17:23    Post subject: Reply with quote
Got it.

Thank you so much.
steve1234
DD-WRT Novice


Joined: 24 Jan 2011
Posts: 1

PostPosted: Mon Jan 24, 2011 9:43    Post subject: Reply with quote
hello every....I am new to this forum and I really liked this whole post..... the particpation of the experts is really great and awesome one..... keep it up gud work u all
_________________
Test King , mcitp exam , mcpd dumps , mcp test
Display posts from previous:    Page 1 of 1
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