Hi,all!
I choosed Prebuilt_Images of AM3517 in TI_Android_GingerBread_2_3_4Sources.tar.gz for porting android, SD boot。My platform is Zoom AM3517 eXperimenter Kit.The system could boot well until I tried to format my SD(2GB)as usual with mkmmc-android.sh. And then I failed to boot android, the boot information was as follows:
waiting 1sec before mounting root device...
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 212K
init: cannot find '/sbin/ueventd', disabling 'ueventd'
init: Timed out waiting for /dev/.coldboot_done
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
init: Unable to open persistent property directory /data/property errno: 5
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: service 'console' requires console
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
init: cannot find '/sbin/adbd', disabling 'adbd'
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
init: untracked pid 661 exited
init: untracked pid 660 exited
request_suspend_state: wakeup (3->0) at 13116882326 (2000-01-01 00:01:00.915374758 UTC)
init: untracked pid 717 exited
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted inode referenced: 29953
.......
or like this:
waiting 1sec before mounting root device...
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 212K
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
enabling adb
adb_open
# tlv320aic23_write cannot write 043 to register R7
tlv320aic23_write cannot write 07f to register R8
tlv320aic23_write cannot write 043 to register R7
tlv320aic23_write cannot write 001 to register R9
tlv320aic23_write cannot write 047 to register R6
tlv320aic23_write cannot write 004 to register R5
tlv320aic23_write cannot write 00c to register R5
tlv320aic23_write cannot write 000 to register R9
omap_device: omap_i2c.2: new worst case activate latency 0: 61035
tlv320aic23_write cannot write 057 to register R6
tlv320aic23_write cannot write 05f to register R6
tlv320aic23_write cannot write 05f to register R6
warning: `zygote' uses 32-bit capabilities (legacy support in use)
request_suspend_state: wakeup (3->0) at 25517852783 (2000-01-01 00:00:22.321746828 UTC)
init: untracked pid 962 exited
OMAPLFBManualSync Not Supported
tlv320aic23_write cannot write 043 to register R7
tlv320aic23_write cannot write 07f to register R8
tlv320aic23_write cannot write 043 to register R7
tlv320aic23_write cannot write 001 to register R9
tlv320aic23_write cannot write 057 to register R6
tlv320aic23_write cannot write 047 to register R6
tlv320aic23_write cannot write 047 to register R6
tlv320aic23_write cannot write 004 to register R5
tlv320aic23_write cannot write 00c to register R5
tlv320aic23_write cannot write 000 to register R9
tlv320aic23_write cannot write 057 to register R6
tlv320aic23_write cannot write 05f to register R6
tlv320aic23_write cannot write 05f to register R6
request_suspend_state: wakeup (0->0) at 39850555420 (2000-01-01 00:00:36.654479982 UTC)
init: untracked pid 1093 exited
OMAPLFBManualSync Not Supported
tlv320aic23_write cannot write 043 to register R7
tlv320aic23_write cannot write 07f to register R8
tlv320aic23_write cannot write 043 to register R7
tlv320aic23_write cannot write 001 to register R9
tlv320aic23_write cannot write 057 to register R6
tlv320aic23_write cannot write 047 to register R6
tlv320aic23_write cannot write 047 to register R6
tlv320aic23_write cannot write 004 to register R5
tlv320aic23_write cannot write 00c to register R5
tlv320aic23_write cannot write 000 to register R9
tlv320aic23_write cannot write 043 to register R7
tlv320aic23_write cannot write 07f to register R8
tlv320aic23_write cannot write 043 to register R7... ...
my boot arguments was :
bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi
baudrate=115200
bootfile=uImage
loadaddr=0x82000000
console=ttyO2,115200n8
mmcargs=setenv bootargs console=${console} root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
nandargs=setenv bootargs console=${console} root=/dev/mtdblock4 rw rootfstype=jffs2
loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
loaduimage=fatload mmc 0 ${loadaddr} uImage
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr}
dieid#=20b00000000000000154417b0200d024
ethact=DaVinci EMAC
bootdelay=3
stdin=serial
stdout=serial
stderr=serial
Environment size: 858/131068 bytes
and I can't boot suceeful with the same SD card, the same configuration, the same platform. So could anyone tell what's the Possible reason?
2). the second question was : Could I use Uart in AM3517EVM as the communication port betwwen my PC and Am3517EVM? Is there any uart demos in Android for AM3517EVM?
