When I boot from TFTP/NFS servers,I can access the Android shell! Someone know why I can't when booting from nand? and is there another way to acces the android shell?
2010/5/7 hadhami riahi <[email protected]> > Hi Ashwin, > Thanks for reply. > I tried to acces Android's shell through adb : > > export ADBHOST=192.168.1.25 > android_google/out/host/linux-x86/bin/adb kill-server > android_google/out/host/linux-x86/bin/adb shell > * daemon not running. starting it now * > * daemon started successfully * > error: device not found > > It seems that I can't reach my target! > Regards > > 2010/5/7 Ashwin Bihari <[email protected]> > > Run "logcat" to see what's happening with Android which is causing >> this..without that information, it's hard to debug.. >> >> Regards >> -- Ashwin >> >> >> >> On Fri, May 7, 2010 at 6:20 AM, hadhami riahi <[email protected]> >> wrote: >> > Hello, >> > I'm porting Android on imx51 target.I was able to boot it from TFTP/ >> > NFS servers and from a SD card but I'm facing problems while trying to >> > boot from internal NAND. >> > I've created a jffs2 for the file system >> > My u-boot commands are: >> > bootcmd_nand=nand unlock;nand read 0x90800000 0x700000 0x232800;bootm >> > 0x90800000 >> > bootargs=console=ttymxc0,115200 androidboot.console=ttymxc0 wvga >> > calibration init=/init noinitrd root=/dev/mtdblock3 rw >> > rootfstype=jffs2 >> > >> > The end of the log is: >> > >> > JFFS2 doesn't use OOB. >> > Empty flash at 0x03bef5a8 ends at 0x03bef800 >> > VFS: Mounted root (jffs2 filesystem). >> > Freeing init memory: 132K >> > Warning: unable to open an initial console. >> > JFFS2 notice: (1035) check_node_data: wrong data CRC in data node at >> > 0x0f49bf6c: read 0xef2d0e46, calculated 0xd5e1ae35. >> > init: cannot open '/initlogo.rle' >> > init: cannot find '/system/etc/install-recovery.sh', disabling >> > 'flash_recovery' >> > # gpu_z430: module license 'Proprietary' taints kernel. >> > warning: `rild' uses 32-bit capabilities (legacy support in use) >> > request_suspend_state: wakeup (3->0) at 29417136653 (1970-01-01 >> > 00:00:29.417130028 UTC) >> > init: untracked pid 1773 exited >> > request_suspend_state: wakeup (0->0) at 41428491778 (1970-01-01 >> > 00:00:41.428484653 UTC) >> > init: untracked pid 1797 exited >> > >> > and it keeps printing the same message with increasing pid number! >> > What can be the problem? >> > Has anyone already faced the same issue? >> > Thanks! >> > >> > -- >> > unsubscribe: >> > [email protected]<android-porting%[email protected]> >> > website: http://groups.google.com/group/android-porting >> > >> > > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
