Hello all, I'm trying to get Android booting on custom hardware (that appears to be based heavily on BeagleBoard/xM design). I'm having problems with the device resetting, as shown in the trace below. I'm guessing it's not a kernel problem because I'd expect to see a "kernel panic", rather than a spontaneous reset? Comparing this trace to a known good boot (on BeagleBoard-xM), there wasn't much left to do anyway trace-wise...
Anybody have any ideas? Regards, Richard. <SNIP> Waiting 1sec before mounting root device... mmc0: host reports active read-only switch, but ignoring. mmc0: new high speed SDHC card at address 0007 mmcblk0: mmc0:0007 SD16G 14.6 GiB mmcblk0: p1 p2 p3 EXT4-fs (mmcblk0p2): recovery complete EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext4 filesystem) on device 179:2. Freeing init memory: 216K init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead. init: cannot open '/initlogo.rle' init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' enabling adb adb_open root@android:/ # init: untracked pid 1040 exited warning: `zygote' uses 32-bit capabilities (legacy support in use) request_suspend_state: wakeup (3->0) at 21261627199 (2000-01-01 00:00:17.357543946 UTC) <<<RESET OCCURS HERE>>> Texas Instruments X-Loader 1.51 (Mar 31 2014 - 15:45:22) Beagle unknown 0x04 Starting X-loader on MMC Reading boot sector 213264 Bytes Read from MMC Starting OS Bootloader from MMC... Starting OS Bootloader... U-Boot 2010.06-svn102 (Mar 31 2014 - 15:48:32) <SNIP> -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
