DaBigMac wrote:I've managed to flash a bad image to my router from inside the uboot console using instructions from a previous post made about half a year ago. I still have serial access, HOWEVER there no longer seems to be a boot wait time. I am using a USB to serial adapter and previously I could manage to catch the boot process in time to stop it, but for some reason, since the flash, no matter how fast I am, I cannot seem to catch the the uboot startup process fast enough to interrupt the boot process..
Is there any possibility that any of the instructions in previous posts could have removed an argument similar to the boot_wait argument in uboot? If so, can you think of any way to change it back??
Here's the log..
=~=~=~=~=~=~=~=~=~=~=~=
............................................................ done, booting the kernel.
Linux version 2.6.28.9 (emmanuel@debian) (gcc version 4.1.2) #2 Sat Apr 11 21:26:37 CST 2009
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Linksys WRT350N v2
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: root=/dev/mtdblock1 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200 init=/etc/preinit
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 30408KB available (1812K code, 136K data, 92K init)
Calibrating delay loop... 332.59 BogoMIPS (lpj=1662976)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 476 bytes
NET: Registered protocol family 16
Orion ID: MV88F5181L-Rev-A1. TCLK=166666667.
Applying Orion-1/Orion-NAS PCIe config read transaction workaround
PCI: bus0: Fast back to back transfers disabled
pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot
pci 0000:01:00.0: PME# disabled
PCI: bus1: Fast back to back transfers enabled
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 59
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:00:00:00:51:81
physmap platform flash device: 00800000 at f4000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
Searching for RedBoot partition table in physmap-flash.0 at offset 0x7f0000
No RedBoot partition table detected in physmap-flash.0
Using physmap partition information
Creating 3 MTD partitions on "physmap-flash.0":
0x00000000-0x00100000 : "kernel"
0x00100000-0x00750000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=260000, len=4F0000
0x00260000-0x00750000 : "rootfs_data"
0x007c0000-0x00800000 : "u-boot"
i2c /dev entries driver
TCP westwood registered
NET: Registered protocol family 17
Distributed Switch Architecture driver version 0.1
eth0: detected a Marvell 88E6131 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>
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
SQUASHFS error: lzma returned unexpected result 0x1
SQUASHFS error: Unable to read cache block [1563c8:316]
SQUASHFS error: Unable to read inode [1563c8:316]
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0x7368 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004: 0x021e instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008: 0x13f7 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c: 0x13f2 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010: 0x13f6 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014: 0xf000 instead
etc etc etc ad nausem until it finally kernel panics several pages later..
I can assure you, boot wait is GONE 
, there is no way that any human being could be pressing the enter key more furiously than I already was..
I was wondering if you could give me more information on JTAG. I'm utterly without any previous experience in using JTAG, but hey, I can't brick it any worse than it already is, right?
If you can give me some suggestions for parts and software that would be great, I remember wiring diagrams in earlier posts as well as some (very confusing) instructions..
The soldering/wiring won't be an issue, but I fear the software side greatly..
Many thanks for the effort to date guys, for those following the path of flashing inside uboot, use the more recent posts rather than the older one, as, trust me, it WILL bring you grief, I followed the instructions very closely..
Cheers,
DaBigMac
P.S. The instructions I used were in post #298
(Last edited by DaBigMac on 13 Jul 2009, 16:59)
