Hi Stefan, Freescale provides some patches (kernel 2.6.31) 0093-ENGR00117951-2-MX25-Change-default-config-to-enable.patch 0095-ENGR00117392-MX25-Camera-enhancement-to-support-enc.patch 0129-ENGR00118562-MX25-Fix-audio-cannot-work-with-sgtl50.patch 0140-ENGR00118701-MX25-Fix-headphone-plug-in-caused-syste.patch * 0201-ENGR00119504-MX25-Change-nand-partition-for-bootloa.patch 0228-ENGR00120539-MX25-Fix-GPIO3_BASE_ADDR-definition-in.patch 0265-ENGR00120850-MX25-Enable-Active-Well-biased-on-STOP.patch 0277-ENGR00120880-2-MX25-Disable-Enable-HSYNC-bit-per-LC.patch 0294-ENGR00119078-MX25-Fix-a-USB-remote-wakeup-issue.patch * 0523-ENGR00122852-2-MX25-pass-mem-and-irq-via-resources.patch 0551-ENGR00123072-2-MX25-Add-Keypad-mem-resource.patch 0572--ENGR00123128-MX25-wifi-small-data-transfer-error-in.patch 0702-ENGR00124740-4-MX25-35-ALSA-Changes-due-to-ESAI-as.patch
I dunno if they can help you, but if you want to try them let me know, I can pack them up and send to you. []'s Hamilton Vera On Thu, Dec 2, 2010 at 8:18 AM, Stefan <[email protected]> wrote: > Hi, > > concerning my vm_flags failed -1 issue I found > http://groups.google.com/group/android-porting/browse_thread/thread/778134e31311aed5/b7e17f2c33310aa7?hl=de&q=bad+vm_flags#b7e17f2c33310aa7 > and changed (VM_WRITE | VM_EXEC) to (VM_WRITE). > > Now, I have new errors > > Look at this: > > $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' > sh: can't access tty; job control turned off > # warning: `rild' uses 32-bit capabilities (legacy support in use) > Unable to handle kernel NULL pointer dereference at virtual address > 00000102 > pgd = c00fc000 > [00000102] *pgd=00000000 > Unable to handle kernel NULL pointer dereference at virtual address > 000000c0 > pgd = c00fc000 > [000000c0] *pgd=00000000 > Internal error: Oops: 17 [#1] PREEMPT > last sysfs file: /sys/devices/platform/mxsdhci.1/mmc_host/mmc0/ > mmc0:0007/block/m > mcblk0/mmcblk0p1/uevent > Modules linked in: > CPU: 0 Tainted: G W (2.6.33-guf-ptx1Android #37) > PC is at account_system_time+0xa4/0x1f0 > LR is at update_process_times+0x28/0x4c > pc : [<c0131974>] lr : [<c0145d9c>] psr: 60000093 > sp : c7041b78 ip : c7041ba0 fp : c7041b9c > r10: c7041c20 r9 : 7fffffff r8 : 00010000 > r7 : 00000001 r6 : c7040000 r5 : 00000000 r4 : 00000000 > r3 : 00000001 r2 : 00000001 r1 : 00000000 r0 : 00000001 > Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user > Control: 0005317f Table: 87050000 DAC: 00000015 > Process (pid: 0, stack limit = 0xc7040270) > Stack: (0xc7041b78 to 0xc05734bc) > [<c0131974>] (account_system_time+0xa4/0x1f0) from [<c0145d9c>] > (update_process_ > times+0x28/0x4c) > [<c0145d9c>] (update_process_times+0x28/0x4c) from [<c015e430>] > (tick_sched_time > r+0x70/0xb4) > [<c015e430>] (tick_sched_timer+0x70/0xb4) from [<c0154698>] > (__run_hrtimer+0x44/ > 0x13c) > [<c0154698>] (__run_hrtimer+0x44/0x13c) from [<c0154a3c>] > (hrtimer_interrupt+0x1 > 10/0x400) > [<c0154a3c>] (hrtimer_interrupt+0x110/0x400) from [<c012a2ec>] > (mxc_timer_interr > upt+0x28/0x38) > [<c012a2ec>] (mxc_timer_interrupt+0x28/0x38) from [<c016c4bc>] > (handle_IRQ_event > +0x5c/0x134) > [<c016c4bc>] (handle_IRQ_event+0x5c/0x134) from [<c016e3c4>] > (handle_level_irq+0 > x90/0x12c) > [<c016e3c4>] (handle_level_irq+0x90/0x12c) from [<c011f03c>] > (asm_do_IRQ+0x3c/0x > 8c) > [<c011f03c>] (asm_do_IRQ+0x3c/0x8c) from [<c011fb6c>] (__irq_svc+0x4c/ > 0x8c) > Exception stack(0xc7041c98 to 0xc7041ce0) > 1c80: 00000001 > 20000013 > 1ca0: c0529cd4 c0529cd4 c0529d70 00000000 c0570327 c7041d5c c0529d70 > 00000000 > 1cc0: 0000001e c7041cf6 c7041cb8 c7041ce0 c013b038 c013b5dc 60000013 > ffffffff > [<c011fb6c>] (__irq_svc+0x4c/0x8c) from [<c013b5dc>] (vprintk > +0x238/0x49c) > [<c013b5dc>] (vprintk+0x238/0x49c) from [<c042763c>] (printk > +0x18/0x28) > [<c042763c>] (printk+0x18/0x28) from [<c01259c8>] (show_pte+0x40/0xc8) > [<c01259c8>] (show_pte+0x40/0xc8) from [<c0125ab0>] (__do_kernel_fault > +0x60/0x80 > ) > [<c0125ab0>] (__do_kernel_fault+0x60/0x80) from [<c0125c18>] > (do_page_fault+0x14 > 8/0x21c) > [<c0125c18>] (do_page_fault+0x148/0x21c) from [<c011f2c8>] > (do_DataAbort+0x38/0x > 9c) > [<c011f2c8>] (do_DataAbort+0x38/0x9c) from [<c011fb0c>] (__dabt_svc > +0x4c/0x60) > Exception stack(0xc7041ee0 to 0xc7041f28) > 1ee0: acfcc7b2 c7b2b720 00000002 00000102 00000102 c05708a0 c7041f30 > c0403cac > 1f00: c7a82000 c052ab98 c05710bc c05712bc c7041f28 c7041f28 c0145450 > c0403cc4 > 1f20: 20000013 ffffffff > [<c011fb0c>] (__dabt_svc+0x4c/0x60) from [<c0403cc4>] (can_stat_update > +0x18/0x1e > 0) > [<c0403cc4>] (can_stat_update+0x18/0x1e0) from [<00000004>] (0x4) > Code: e0a55003 e1c142f0 e89dabf0 e595535c (e59530c0) > ---[ end trace 17edc5f3bf1e45a8 ]--- > Kernel panic - not syncing: Fatal exception in interrupt > [<c0124ddc>] (unwind_backtrace+0x0/0xe4) from [<c0427524>] (panic > +0x40/0x140) > [<c0427524>] (panic+0x40/0x140) from [<c0123724>] (die+0xac/0xc8) > [<c0123724>] (die+0xac/0xc8) from [<c0125ac0>] (__do_kernel_fault > +0x70/0x80) > [<c0125ac0>] (__do_kernel_fault+0x70/0x80) from [<c0125c18>] > (do_page_fault+0x14 > 8/0x21c) > [<c0125c18>] (do_page_fault+0x148/0x21c) from [<c011f2c8>] > (do_DataAbort+0x38/0x > 9c) > [<c011f2c8>] (do_DataAbort+0x38/0x9c) from [<c011fb0c>] (__dabt_svc > +0x4c/0x60) > Exception stack(0xc7041b30 to 0xc7041b78) > 1b20: 00000001 00000000 00000001 > 00000001 > 1b40: 00000000 00000000 c7040000 00000001 00010000 7fffffff c7041c20 > c7041b9c > 1b60: c7041ba0 c7041b78 c0145d9c c0131974 60000093 ffffffff > [<c011fb0c>] (__dabt_svc+0x4c/0x60) from [<c0131974>] > (account_system_time+0xa4/ > 0x1f0) > [<c0131974>] (account_system_time+0xa4/0x1f0) from [<c0145d9c>] > (update_process_ > times+0x28/0x4c) > [<c0145d9c>] (update_process_times+0x28/0x4c) from [<c015e430>] > (tick_sched_time > r+0x70/0xb4) > [<c015e430>] (tick_sched_timer+0x70/0xb4) from [<c0154698>] > (__run_hrtimer+0x44/ > 0x13c) > [<c0154698>] (__run_hrtimer+0x44/0x13c) from [<c0154a3c>] > (hrtimer_interrupt+0x1 > 10/0x400) > [<c0154a3c>] (hrtimer_interrupt+0x110/0x400) from [<c012a2ec>] > (mxc_timer_interr > upt+0x28/0x38) > [<c012a2ec>] (mxc_timer_interrupt+0x28/0x38) from [<c016c4bc>] > (handle_IRQ_event > +0x5c/0x134) > [<c016c4bc>] (handle_IRQ_event+0x5c/0x134) from [<c016e3c4>] > (handle_level_irq+0 > x90/0x12c) > [<c016e3c4>] (handle_level_irq+0x90/0x12c) from [<c011f03c>] > (asm_do_IRQ+0x3c/0x > 8c) > [<c011f03c>] (asm_do_IRQ+0x3c/0x8c) from [<c011fb6c>] (__irq_svc+0x4c/ > 0x8c) > Exception stack(0xc7041c98 to 0xc7041ce0) > 1c80: 00000001 > 20000013 > 1ca0: c0529cd4 c0529cd4 c0529d70 00000000 c0570327 c7041d5c c0529d70 > 00000000 > 1cc0: 0000001e c7041cf6 c7041cb8 c7041ce0 c013b038 c013b5dc 60000013 > ffffffff > [<c011fb6c>] (__irq_svc+0x4c/0x8c) from [<c013b5dc>] (vprintk > +0x238/0x49c) > [<c013b5dc>] (vprintk+0x238/0x49c) from [<c042763c>] (printk > +0x18/0x28) > [<c042763c>] (printk+0x18/0x28) from [<c01259c8>] (show_pte+0x40/0xc8) > [<c01259c8>] (show_pte+0x40/0xc8) from [<c0125ab0>] (__do_kernel_fault > +0x60/0x80 > ) > [<c0125ab0>] (__do_kernel_fault+0x60/0x80) from [<c0125c18>] > (do_page_fault+0x14 > 8/0x21c) > [<c0125c18>] (do_page_fault+0x148/0x21c) from [<c011f2c8>] > (do_DataAbort+0x38/0x > 9c) > [<c011f2c8>] (do_DataAbort+0x38/0x9c) from [<c011fb0c>] (__dabt_svc > +0x4c/0x60) > Exception stack(0xc7041ee0 to 0xc7041f28) > 1ee0: acfcc7b2 c7b2b720 00000002 00000102 00000102 c05708a0 c7041f30 > c0403cac > 1f00: c7a82000 c052ab98 c05710bc c05712bc c7041f28 c7041f28 c0145450 > c0403cc4 > 1f20: 20000013 ffffffff > [<c011fb0c>] (__dabt_svc+0x4c/0x60) from [<c0403cc4>] (can_stat_update > +0x18/0x1e > 0) > [<c0403cc4>] (can_stat_update+0x18/0x1e0) from [<00000004>] (0x4) > > > And here it stucks. Maybe one of you experts knows this error > I hope this isn't because of my 2.6.33 kernel, but I am really > not sure. > > Thank you > > Stefan > > On 2 Dez., 07:32, Stefan <[email protected]> wrote: >> 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_OMAPfromthe 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 > -- Hamilton Vera int Administrator (char Network[],char ComputationalSystems[]) http://hvera.wordpress.com -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
