|
Hello,
I went through the steps published on Android4SAM to successfully build bootstrap, kernel, and android rootfs, but cannot seem to boot on the SAM9M10-G45-EK board using SD Card. I get the linux penguin followed by the Atmel logo splash screen and then nothing. Examining DBGU output reveals the system hangs on repeated "init: untracked pid xxx exited" errors where xxx are incremental pids. Please see tail-end of DBGU capture below (note: UBIFS errors are consistent with sample output exhibited on Android4SAM). I'm using Ubuntu 11.10 Oneiric as build platform.
Has anyone encountered this? I appreciate any help as internet searches don't seem to yield useful information so far.
DBGU Output
==========
...
rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
atmel_mci atmel_mci.0: Atmel MCI controller at 0xfff80000 irq 11, 1 slots
atmel_mci atmel_mci.1: Atmel MCI controller at 0xfffd0000 irq 29, 1 slots
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
mmcblk0:
p1 p2 p3
VFS: Mounted root (ext2 filesystem) on device 179:2.
Freeing init memory: 144K
EXT2-fs (mmcblk0p2): error: ext2_valid_block_bitmap:
Invalid block bitmap - block_group = 0, block = 129
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0_0", error -19
UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi1_0", error -19
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
# enabling adb
adb_open
request_suspend_state: wakeup (3->0) at 54637678748 (1970-01-01 00:00:54.637476)
init: untracked pid 824 exited
init: untracked pid 828 exited
request_suspend_state: wakeup (0->0) at 57503387874 (1970-01-01 00:00:57.503187)
init: untracked pid 866 exited
init: untracked pid 867 exited
request_suspend_state: wakeup (0->0) at 61474522272 (1970-01-01 00:01:01.474321)
init: untracked pid 875 exited
init: untracked pid 876 exited
...
Thanks,
eustace
|
Forum
