(sorry for all the posts, I'm about to call it a day on this)
At the u-boot prompt this is interesting:
After the kernel boots, the Pocket Edge logo appears on the LCD. Nice, since it's just displayed "entourage Edge" backwards for a few weeks. But it doesn't get very far. But it does fire up adb for a short time. You have 10 seconds to press a key to drop to a prompt, but keyboard entry on the serial console isn't being heard. I tried passing bootargs of console=ttyS1,etc,etc.... but didn't seem to help. I'm thinking we can figure out a bootarg to to suspend it or drop to a shell, then we can adb the device to death.
Dump with lots removed, see full dump attached
Quote:
Edge>> run boot_recover
Hostname : ESIedge
Filesystem : v1.0.0
Kernel release : Linux 2.6.29
Kernel version : #1 PREEMPT Wed Sep 29 13:04:47 EDT 2010
Mounting /proc : [SUCCESS]
Mounting /sys : [SUCCESS]
Mounting /dev : [SUCCESS]
Mounting /dev/pts : [SUCCESS]
Enabling hot-plug : [SUCCESS]
Populating /dev : [SUCCESS]
Mounting other filesystems : [SUCCESS]
Starting syslogd : Oct 9 22:03:11 ESIedge syslog.info syslogd started: BusyBox v1.9.1
[SUCCESS]
Starting telnetd : [SUCCESS]
System initialization complete.
Archive: /usr/esi/images.zip
inflating: /tmp/img-splash-flip.raw
inflating: /tmp/img-splash.raw
inflating: /tmp/migrate-1.raw
inflating: /tmp/migrate-2.raw
inflating: /tmp/migrate-3.raw
inflating: /tmp/migrate-4.raw
inflating: /tmp/migrate-flip-1.raw
inflating: /tmp/migrate-flip-2.raw
inflating: /tmp/migrate-flip-3.raw
inflating: /tmp/migrate-flip-4.raw
show splash screen...
starting adbd...
[ 8.438872] enabling adb
UBI device number 0, total 7864 LEBs (4058578944 bytes, 3.8 GiB), available 1 LEBs (516096 bytes, 504.0 KiB), LEB size 516096 bytes (504.0 KiB)
/etc/init.d/edge_start: No valid command specified for Maintenance Mode...
*** Press any key within 10 seconds to start shell...^J
starting pid 691, tty '': '/bin/umount'
umount: mdev busy - remounted read-only
starting pid 693, tty '': '/sbin/swapoff'
The system is going down NOW!
|
You can see a BUNCH of boot options with printenv. "run" just runs the env variable on the commandline. So you can run them directly. I experimented with different parts of various boot arguments from the different environment variables.
For people that are new to u-boot like me:
Actually looks up the env variable $boot_recover and runs it so it runs:
Quote:
nand read 0x01000000 0x01300000 0x01800000
setenv esiboot sf read 0x500000 0x400000 0x300000
setenv bootargs $(bootargs_maint)
setenv autoboot boot
bootz 0x500000
|