I use an i.MX25 (ARM926EJ-S) from freescale. It runs with 400 MHz. I use 128MB DDR RAM and 256 MB NANDFLASH.
To start up I use following commands: First I mount the android file system from sd card $mount /dev/mmcblk0p1 /media/ then I unmount the proc and sys and mount proc and sys form android $umount proc $umount sys $mount -t proc proc /media/android/proc $mount -t sysfs sysfs /media/android/sys $umask 000 And now change root $chroot /media/android After exporting some paths I start $./app_process -Xzygote /system/bin --zygote then I want to start the runtime, but no runtime there When I try so start with the init following error messages occurs and the system reboots. $root:/ ./init at24 0-0050: uevent rtc-pcf8563 0-0051: uevent init: cannot open '/initlogo.rle' init: cannot find '/system/bin/playmp3', disabling 'bootsound' init: cannot find '/system/bin/dbus-daemon', disabling 'dbus' init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' binder_mmap: 530 40008000-40028000 bad vm_flags failed -1 sh: can't access tty; job control turned off # init: untracked pid 534 exited init: untracked pid 535 exited warning: `rild' uses 32-bit capabilities (legacy support in use) binder_mmap: 541 40009000-40107000 bad vm_flags failed -1 binder_mmap: 544 40008000-40028000 bad vm_flags failed -1 init: untracked pid 540 exited init: untracked pid 545 exited binder_mmap: 547 40009000-40107000 bad vm_flags failed -1 binder_mmap: 548 40008000-40028000 bad vm_flags failed -1 init: untracked pid 549 exited init: untracked pid 546 exited binder_mmap: 551 40009000-40107000 bad vm_flags failed -1 binder_mmap: 552 40008000-40028000 bad vm_flags failed -1 init: untracked pid 550 exited init: untracked pid 553 exited binder_mmap: 555 40009000-40107000 bad vm_flags failed -1 binder_mmap: 556 40008000-40028000 bad vm_flags failed -1 init: critical process 'servicemanager' exited 4 times in 4 minutes; rebooting i nto recovery mode On 1 Dez., 19:08, Hamilton Vera <[email protected]> wrote: > Give more information about the iMX that you are using. > > []'s > > Hamilton Vera > > > > On Tue, Nov 30, 2010 at 12:15 PM, Stefan <[email protected]> wrote: > > Hi alltogether, > > > I use a 2.6.33 Kernel for a i.mx cpu. I've patched the files and > > drivers described > > in :http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Porting... > > > Afterwards I set the kernel config as recommended in > >http://android.git.kernel.org/?p=kernel/common.git;a=blob_plain;f=Doc... > > > Then I got the system.img, ramdisk.img and userdata.img as described > > here: > >http://elinux.org/Android_on_OMAPfrom the emulator > > > Now I want get Android started but some files are missing: > > > device/system/bin/dbus-daemon is missung > > device/system/bin/runtime is missing > > device/system/bin/logd is missing > > > and last but not least > > > device/system/bin/usbd is missing. > > > When I tried to follow the instructions > > formhttp://elinux.org/Android_on_OMAP > > the problem is: dbus-daemon and runtime is unknown. > > > Now my question: > > May I use the dbus-daemon from my standart system? > > Where do I get / How can I build the runtime routine? > > > These questions may seem for you experienced developers > > maybe a bit stupid but I hope some of you can help me. > > > With best regards, > > > Stefan > > > -- > > unsubscribe: [email protected] > > website:http://groups.google.com/group/android-porting > > -- > Hamilton Vera > int Administrator (char Network[],char > ComputationalSystems[])http://hvera.wordpress.com -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
