LOL I connect my router via Arduino Due R3 to PC and got terminal

Message from terminal after router power on:

What it mean?

This does not seem ok:

m25p80 spi0.0: unrecognized JEDEC id 1c3016

what flash is onboard? Take a macro picture or note here every code you read on it...

Also What hw.ver is on the label?

TL-WR851N VER. 8.2

Cannot make enough good photo of my board... Onboard flash? U mean the biggest "chip" on board?

wow congratulations!

Do they have same mac addresses?

I bricked my router to, i have a  8.2version.

It powers on, all the led light simultaneas and go off. There is nothing i can do to it to change it, 30/30/30 doesn't work.
It doesn't responds to ping, it repeatly conects for a second on lan, but the lan cable doesn't link.
It only lights up once and then it's over.

Any solutions?

you mean wr841 right??

flash it's this:

http://4.bp.blogspot.com/-ume9kTJ4fBs/U … bottom.jpg

omg another brick, there is something BAD going on..

Yes, wr841N v8.2 i see on the back of the router.

I am to blame for this, i was pushing the flashing over the limits.
I am not familiar with this procedure, can you please direct me to the right procedure?

Thanks!

@uqadwe what image you flashed (post specific link) and how? why you say that you are to blame???

Not sure, but my flash is: "cfeon q32b-104hip"

that same problem!

yeah...

I originally flashed an OpenWrt firmware(lucy)

and then tried to return to stock, it seemed blocked after an half an hour so i unpluged it.
I don't have the link anymore, i flashed it from the LUCY web interface

(Last edited by uqadwe on 25 Nov 2012, 22:25)

ok, uqadwe you have to connect to serial console, and your problem seems the usual "flashed an image including uboot in the WRONG way"..

search info in wiki for serial port, you need a ttl serial adapter, not a classic rs232 serial port.. and some soldering skills..

quorce, wiki said that wr841nd v8 has spansion FL032PIF (dunno if it's right), while your flash seems different...

you can try to flash back stock firmware with tftp method..

Ok understand... Is this possible only with USB TTL Serial adapter?

PS. wr841n not wr841nd - if this is any difference

(Last edited by quorce on 25 Nov 2012, 22:37)

Wouldn't be more likely to resolv the problem to send it to warranty?
Do you think they will easily find out what really happened? Considering it will be probably get analysed by the retailer service, which is a big online shop.

Thanks for your guidance!

uqadwe, they can find out if they connect to serial.. it will be more useful and fun if you manage to unbrick by yourself ^^

quorce, you already got a serial terminal, you're good to go (you have mail!)!

(Last edited by nebbia88 on 25 Nov 2012, 22:41)

Yes!! So some more research needs to be done, and from my previos experience, doing the wrong thing here will disable
uboot and not only os loading, but I would love to save config or art , edit, and write back

Does uboot support setting mac? Does it subbort saveenv ?? I tried to get the source, to have a look at uboot, but GPL
kit is not a tar.gz.

I think maybe there is something to analyse from this, which is the crash that happened on router #2, after flashing tplink firmware (without boot, 120552). This is the crash footprint, form tplink linux.

insmod: cannot open module `/lib/modules/2.6.31/kernel/flashid.ko': No such file or directory
PPPoL2TP kernel driver, V1.0
PPTP driver version 0.8.3
insmod: cannot open module `/lib/modules/2.6.31/kernel/harmony.ko': No such file or directory

unlzma/peek_old_byte: position 9413459 out of range
unlzma/peek_old_byte: position 41992320 out of range
SQUASHFS error: crypto_decompress_update returned -85522, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x1e4431
SQUASHFS error: Unable to read data cache entry [1e4431]
SQUASHFS error: Unable to read page, block 1e4431, size 8457
SQUASHFS error: Unable to read data cache entry [1e4431]
SQUASHFS error: Unable to read page, block 1e4431, size 8457
SQUASHFS error: Unable to read data cache entry [1e4431]

I think I get the insmod : harmony error on a working board, but it seems the next operation is trying to unpack the rest as LZMA, what if kernel command string is wrong, or FS type is something else? It is clear what Openwrt does, and how it views flash disk, but maybe THAT is something that changed in the tplink f/w and is a reason they have concatenated boot + firmware in the last two firmwares. But, it does not explain why I succeeded to reflash router #1, but bricked router #2, but I am not 100% sure both routers were at same f/w before I installed Openwrt on them, so there IS a small chance/risk that one router had an updated Uboot, and the other one not. Anyway this is possibly a footprint....

Also: My understanding of the boot procedure is that the cpu reads the spi-connected serial flash int ram before starting. How much it reads, and if there are any checks to the content I dont know, but if there is, it is most probably limited to something extremely simple, since we have not started executing instructions yet. Also, this "prologue" surely can handle many different flash roms,  but there IS some check on the contents that could explain why not even uboot started when I bricked my router.
Does anyone have access to the ar9341 data sheet, and could explain this, or even e-mail a copy?

(Last edited by gulweb on 25 Nov 2012, 23:56)

hmm...

got next problem... im "in" router via serial and got problem with tftp...

which version is correct for wr841n? tftp 0x80000000 tplink.bin or 0x81000000? in both version i got checksum bad...

Try to do a printenv, that is at least what Uboot thinks of the situation.

in my version it printed out some command abbreviations, and the addresses it wanted to use.

But I want to point out that I DO NOT know or understand this full out.

If you do print out, please post result, so we have something to discuss.

printenv said tftp=0x81000000 so i think it's right, and different from the wr841nd v7 (wiki says 0x80000000), but equal to the wr703nd (same chipset family?)

http://wiki.openwrt.org/toh/tp-link/tl- … inal.image

we try to setenv ipaddr and setenv serverip, because the wifi NIC has same subnet, so conflict, but then it says "checksum bad" when tftpboot...

someone can verify if using setenv cause this problem??

we not had time to try WHITOUT USING SETENV, but adjusting ip of NIC accordingly...

(Last edited by nebbia88 on 26 Nov 2012, 09:17)

on pc ethernet set on 192.168.1.2, router to pc via WAN port, than try:

wasp> tftpboot 0x80000000 tplink.bin
enet1 port0 up
dup 1 speed 1000
Using eth1 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'tplink.bin'.
Load address: 0x80000000
Loading: T T T T T T T

wasp> tftpboot 0x81000000 tplink.bin
Using eth1 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'tplink.bin'.
Load address: 0x81000000
Loading: T T T T T T T T T T

and printenv:

wasp> printenv
bootargs=console=ttyS0,115200 root=31:02 rootfstype=squashfs init=/sbin/init mtdparts=ath-nor0:128k(u-boot),1024k(kernel),2816k(rootfs),64k(config),64k(art)
bootcmd=bootm 0x9f020000
bootdelay=1
baudrate=115200
ethaddr=0xba:0xbe:0xfa:0xce:0x08:0x41
dir=
bc=ap123
lu=tftp 0x81000000 ${dir}u-boot.bin&&erase 0x9f000000 +$filesize;cp.b $fileaddr 0x9f000000 $filesize
lf=tftp 0x81000000 ${dir}${bc}-squashfs&&erase 0x9f120000 +$filesize;cp.b $fileaddr 0x9f120000 $filesize
stdin=serial
stdout=serial
stderr=serial
ethact=eth0
ipaddr=192.168.1.1
serverip=192.168.1.2

Environment size: 561/65532 bytes

ps. tftpboot via LAN port

wasp> tftpboot 0x81000000 tplink.bin
enet1 port0 down
enet1 port1 up
Using eth1 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'tplink.bin'.
Load address: 0x81000000
Loading: checksum bad
T checksum bad
checksum bad
T checksum bad
checksum bad
T checksum bad

(Last edited by quorce on 26 Nov 2012, 10:20)

try WITHOUT USING setenv, leave all default settings after bootup, so set PC NIC to 192.168.1.100

that same...

wasp> tftpboot 0x81000000 tplink.bin
enet1 port1 up
dup 1 speed 1000
Using eth1 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.111
Filename 'tplink.bin'.
Load address: 0x81000000
Loading: checksum bad
T checksum bad
T checksum bad
T checksum bad
T checksum bad

I retire myself from this topic xD

only thing i have in mind is "try a different pc and different cable" (but i'm not hoping it makes a difference..)

(Last edited by nebbia88 on 26 Nov 2012, 10:38)

without effect... today got 3 other cables + other pc... still that same