OpenWrt Forum Archive

Topic: Please help can not access uboot

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

Dear all

I flash openwrt ap147 to my access point.
Now it can not boot. I connect usb ttl to check boot log it show below.
I try to access uboot to reflash  device factory firmware.
Now I can not access the device. please advice me.

[    0.680000] console [ttyS0] enabled, bootconsole disabled
[    0.690000] m25p80 spi0.0: found w25q128, expected m25p80
[    0.700000] m25p80 spi0.0: w25q128 (16384 Kbytes)
[    0.700000] 6 cmdlinepart partitions found on MTD device spi0.0
[    0.710000] Creating 6 MTD partitions on "spi0.0":
[    0.710000] 0x000000000000-0x000000040000 : "u-boot"
[    0.720000] 0x000000040000-0x000000050000 : "u-boot-env"
[    0.720000] 0x000000050000-0x000000e80000 : "rootfs"
[    0.730000] mtd: partition "rootfs" set to be root filesystem
[    0.740000] mtd: partition "rootfs_data" created automatically, ofs=240000, len=C40000
[    0.750000] 0x000000240000-0x000000e80000 : "rootfs_data"
[    0.750000] 0x000000e80000-0x000000ff0000 : "kernel"
[    0.760000] 0x000000ff0000-0x000001000000 : "art"
[    0.770000] 0x000000050000-0x000000ff0000 : "firmware"
[    0.790000] ag71xx_mdio: probed
[    0.930000] ag71xx_mdio: probed
[    0.930000] eth0: Atheros AG71xx at 0xb9000000, irq 4
[    1.490000] ag71xx ag71xx.0: eth0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd042, driver=Generic PHY]
[    1.500000] eth1: Atheros AG71xx at 0xba000000, irq 5
[    2.060000] eth1: Found an AR934X built-in switch
[    3.090000] GACT probability on
[    3.090000] Mirror/redirect action on
[    3.090000] netem: version 1.3
[    3.100000] u32 classifier
[    3.100000]     Performance counters on
[    3.100000]     input device check on
[    3.110000]     Actions configured
[    3.110000] Netfilter messages via NETLINK v0.30.
[    3.120000] nf_conntrack version 0.5.0 (1962 buckets, 7848 max)
[    3.120000] ctnetlink v0.93: registering with nfnetlink.
[    3.130000] ip_tables: (C) 2000-2006 Netfilter Core Team
[    3.140000] TCP cubic registered
[    3.140000] NET: Registered protocol family 17
[    3.140000] Bridge firewalling registered
[    3.150000] Ebtables v2.0 registered
[    3.150000] 8021q: 802.1Q VLAN Support v1.8
[    3.160000] ### of_selftest(): No testcase data in device tree; not running tests
[    3.160000] SQUASHFS error: Failed to initialise xz decompressor
[    3.170000] VFS: Cannot open root device "(null)" or unknown-block(31,2)
[    3.180000] Please append a correct "root=" boot option; here are the available partitions:
[    3.190000] 1f00             256 mtdblock0  (driver?)
[    3.190000] 1f01              64 mtdblock1  (driver?)
[    3.200000] 1f02           14528 mtdblock2  (driver?)
[    3.200000] 1f03           12544 mtdblock3  (driver?)
[    3.210000] 1f04            1472 mtdblock4  (driver?)
[    3.210000] 1f05              64 mtdblock5  (driver?)
[    3.220000] 1f06           16000 mtdblock6  (driver?)
[    3.220000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)

What happened between the moment it worked and when it stopped?

It 's not work and LED is red.

i had a similar problem and error while flashing a easybox 803 with uboot, this happened when i sent openwrt via xmodem or writeuboot.py, sending the file via tftp solved it

tftp not work for me because device can not run on safemode.

The discussion might have continued from here.