Hello all,
Thank you sincerely for all your inputs. I've solved the
problem. Now am able to bring up Android 2.2 on omap2430 board.
I had to enable ASHMEM and WAKELOCK support in the kernel
configuration. Since the kernel I'm using did not have ASHMEM and
WAKELOCK support, I had to copy the
Hi,
Thank you for your inputs. I've tried removing the number of
applications from init.rc file. Still there's no progress. I keep
getting the same kernel panic.
I've booted Devkit8000 board with Android 2.1 successfully. Devkit8000
also has only 128MB of RAM. So I don't think this can be
The root file system is mounted via NFS.
Not sure if android init starting executed at this point.
if you have a lauterbach, put a while loop spin lock in android init.c and
see if we hit that.
In the kernel I'm using there is no
configuration item for ASHMEM, WAKELOCK, etc. do they have to be
This usually happens when the init script exit with an error status.
Try to echo status of each command in the init script and see where
the error occur.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
I remember seeing something similar when I was changing the memory
split from 2G/2G to 3G/1G. If you have changed the memory map, it
might be something to take a look at. My init was exiting during
execve, which kinda explains the Attempted to kill init message.
On Dec 14, 1:02 am, Deva R
Hi,
Thank u for your inputs. The board has only 128MB RAM. I have
also changed the RAM size to 128MB and checked. But still I have the
same problem.
Regards,
Vadi.
On Dec 2, 10:59 pm, Ashwin Bihari abih...@gmail.com wrote:
You're going to have a REAL hard time getting Android 2.2 up on a
You still have to reduce the amount of applications (number or size)
running. Standard Android really needs 192meg to run the standard
image.
On Dec 6, 12:43 am, Vivek vivekgulat...@gmail.com wrote:
Hi,
Thank u for your inputs. The board has only 128MB RAM. I have
also changed the RAM
