1 (edited by dl3daz 2010-04-09 15:06:26)

Topic: Help needed with U-Boot - Bricked wr841nd-v5

EDIT 3:

Problem solved!

For the records:

tftpboot 0x80000000

...

Bytes transferred = 2367492 (242004 hex)
ar7240> erase 0x9f020000 +0x242004
...
ar7240> cp.b 0x80000000 0x9f020000 0x242004

ar7240> bootm 0x9f020000

Hello,
as this is my first post to this forum, I hope that this is the right place for my question:

Played with the wr841nd-v5, installed openwrt-ar71xx-tl-wr841nd-v5-squashfs-factory.bin via the original WEB-GUI, tried to re-install the original FW and failed:

U-Boot 1.1.4 (Aug  4 2009 - 14:30:25)

AP93 (ar7240) U-boot
DRAM:  
sri
#### TAP VALUE 1 = 7, 2 = 8
32 MB
id read 0x100000ff
flash size 4194304, sector count = 64
Flash:  4 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7240_enet_initialize...
No valid address in Flash. Using fixed address
: cfg1 0xf cfg2 0x7014
eth0: 00:03:7f:09:0b:ad
eth0 up
No valid address in Flash. Using fixed address
: cfg1 0xf cfg2 0x7214
eth1: 00:03:7f:09:0b:ad
ATHRS26: resetting s26
ATHRS26: s26 reset done
eth1 up
eth0, eth1
Autobooting in 1 seconds

I managed to access U-Boot and do "tftpboot", "loady" etc but nothing worked.

Is there any HowTo describing in detail what I have to do to install a FW image? Addresses? Erase flash? Copy Image?

EDIT:
tftp and "bootm 0x81000000" starts a kernel but ends in tons of

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001cb024: 0xf59c instead

and finally

Further such events for this erase block will not be printed
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 195, bad_blocks 0, c->nr_blocks 656
VFS: Cannot open root device "<NULL>" or unknown-block(31,2)
Please append a correct "root=" boot option; here are the available partitions:
1f00             128 mtdblock0 (driver?)
1f01            1280 mtdblock1 (driver?)
1f02            2624 mtdblock2 (driver?)
1f03              64 mtdblock3 (driver?)
1f04            3904 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)

EDIT 2:
Ok, I think, I am getting closer:

ar7240> erase 0x9f020000 +01E0000

First 0x2 last 0x1f sector size 0x10000
  31
Erased 30 sectors
ar7240> tftp
*** Warning: no boot file name; using '7B01A8C0.img'
Using eth1 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.123
Filename '7B01A8C0.img'.
Load address: 0x81000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ########
done
Bytes transferred = 2367492 (242004 hex)

ar7240> cp.b 0x81000000 0x9f020000 0x1E0000
Copy to Flash... write addr: 9f020000
done

ar7240> bootm 0x9f020000
## Booting image at 9f020000 ...
   Uncompressing Kernel Image ... OK

Starting kernel ...

Linux version 2.6.32.10 (buildbot@tksite) (gcc version 4.3.3 (GCC) ) #1 Thu Apr 1 17:26:32 CDT 0
bootconsole [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)
Atheros AR7240 rev 2, CPU:400.000 MHz, AHB:200.000 MHz, DDR:400.000 MHz
Determined physical RAM map:
 memory: 02000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd

until

Distributed Switch Architecture driver version 0.1
eth0[0]: detected a Atheros AR7240 built-in switch
dsa slave smi: probed
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
SQUASHFS error: squashfs_read_data failed to read block 0xe2c4d
SQUASHFS error: Unable to read metadata cache entry [e2c4d]
SQUASHFS error: Unable to read inode 0xd9405ff
------------[ cut here ]------------
WARNING: at fs/inode.c:712 0x800ebbac()
Modules linked in:
Call Trace:[<8007da34>] 0x8007da34
[<800683c4>] 0x800683c4

....

[<8006c8e0>] 0x8006c8e0

---[ end trace a4411e8f35b28b5b ]---
VFS: Cannot open root device "<NULL>" or unknown-block(31,2)
Please append a correct "root=" boot option; here are the available partitions:
1f00             128 mtdblock0 (driver?)
1f01            1280 mtdblock1 (driver?)
1f02            2624 mtdblock2 (driver?)
1f03            1708 mtdblock3 (driver?)
1f04              64 mtdblock4 (driver?)
1f05            3904 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)

Regards,
Falk

Re: Help needed with U-Boot - Bricked wr841nd-v5

Thanks for the info, that was really helpful just now (had to reflash a hosed router smile ).

For the record: I documented this in a bit more detail in the wiki:
http://nuwiki.openwrt.org/toh/tp-link/tl-wr841nd

Re: Help needed with U-Boot - Bricked wr841nd-v5

Hello,

kread wrote:

Thanks for the info, that was really helpful just now (had to reflash a hosed router smile ).

For the record: I documented this in a bit more detail in the wiki:
http://nuwiki.openwrt.org/toh/tp-link/tl-wr841nd

might I suggest to change the cited voltage levels in the serial port section to 3.3V? They are a little bit misleading and perhaps they are wrong for some devices.

Thanks
hmw

Re: Help needed with U-Boot - Bricked wr841nd-v5

Hello everyone,
I have WR841 Router, and meanwhile I updating the firmware the electricity got cut off and then when I accessed the RS232 with the cable it booted, I tried to write a flash on the address of the firmware but ever since it didn’t boot and I bought a WR1043 instead and I tried to write a firmware on the WR841 flash but I don’t know exactly its address, and this is what I got:
erase 0xbf020000 +7c0000
tftpboot 0x81000000 code.bin
cp.b 0x81000000 0xbf020000 0x7c0000
So I thought of doing this, while it was working or on function, I dispatched the flash for the WR1043 and I’ve installed it on the WR841, I managed to write the WR841 and the file on the flash (wr841n_en_3_4_5_up_boot(090226) but it doesn’t boot because I wrote it on the wrong address, the file includes the boot sector (U-BOOT 1.1.4 feb 6 2009). So on what kind of address do I have to write it, can anyone help me out?

Re: Help needed with U-Boot - Bricked wr841nd-v5

Hi!!!! I am a newbie here, I am not getting the solution, please explain me I wanna know that.