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 respective files from other kernel
which had this source and compiled the same for omap2430 board.
Regards,
Vadi.
On Dec 13, 10:03 pm, Hemanth <hemanth....@gmail.com> wrote:
> 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. Myinitwas exiting during
> execve, which kinda explains the "Attempted to killinit" message.
>
> On Dec 14, 1:02 am, Deva R <r.deva...@gmail.com> wrote:
>
>
>
>
>
>
>
> > > The root file system is mounted via NFS.
>
> > Not sure if androidinitstarting executed at this point.
> > if you have a lauterbach, put a while loop spin lock in androidinit.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
> > >enabled? Am I using the right Android kernel?
>
> > This will be a problem,.
> > how about other essential options? (as listed
> > underhttp://git.omapzoom.org/?p=kernel/common.git;a=blob_plain;f=Documenta...<http://android.git.kernel.org/?p=kernel/common.git;a=blob_plain;f=Doc...>
> > )
>
> > >I've also tried the omap android kernel from the following link.
> > >git://android.git.kernel.org/kernel/omap.git using branch named
> > >"android-omap-2.6.32".
> > >This is even worse. I don't get any kernel messages output on the
> > >screen.
>
> > did u used 2430-sdp defconfig? probably this's simple to fix - like debug
> > console mismatch.,
>
> > from the mail, i guess the .config you are using have all the mandatory
> > configs present, but disabled (config file attachment is missing ).
> > can you enable them and try?
>
> > On Mon, Dec 13, 2010 at 8:21 PM, Vivek <vivekgulat...@gmail.com> wrote:
> > > Hi,
> > > Thank you for your inputs. I've tried removing the number of
> > > applications frominit.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 an issue. May
> > > be I'm missing something in kernel configuration or wrong kernel
> > > arguments for frame buffer support, etc.
>
> > > Regards,
> > > Vadi.
>
> > > On Dec 6, 11:02 pm, Brad Davis <bda...@cove-mtn.com> wrote:
> > > > 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 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
> > > > > > system with only 64MB RAM. You'll need a minimum of 128MB for Eclair
> > > > > > (2.1), I imagine the same for FroYo (2.2) or even more..
>
> > > > > > Regards
> > > > > > -- Ashwin
>
> > > > > > On Thu, Dec 2, 2010 at 9:12 AM, Vivek <vivekgulat...@gmail.com>
> > > wrote:
> > > > > > > Dear all,
> > > > > > > I wanted to boot my omap 2430 SDP board with Android 2.2
> > > using
> > > > > > > kernel 2.6.32. I've done the following to bring the board up.
> > > > > > > 1) I've downloaded the kernel from the following link.
> > > > > > > git://android.git.kernel.org/kernel/common.git
> > > > > > > 2) I checkout the tag named "v2.6.32"
> > > > > > > 3) Configured the kernel for omap2430 using the default
> > > configuration
> > > > > > > file named "omap_2430sdp_defconfig"
> > > > > > > 4) Configured again for Android. Please find the attached
> > > > > > > configuration file for your reference.
> > > > > > > 5) My omap2430 board does not have a touchscreen. It only has a
> > > > > > > LCD
> > > > > > > display.
> > > > > > > 6) The root file system is mounted via NFS.
> > > > > > > 7) The kernel messages are shown below.
>
> > > ===========================================================================
> > > =
> > > > > > > Linux version 2.6.32-00000-v2.6.32-dirty
> > > (r...@localhost.localdomain)
> > > > > > > (gcc versi
> > > > > > > on 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #18 PREEMPT Thu Dec 2
> > > > > > > 14:50:38 IST 2010
> > > > > > > CPU: ARMv6-compatible processor [4107b366] revision 6 (ARMv6TEJ),
> > > > > > > cr=00c5387f
> > > > > > > CPU: VIPT aliasing data cache, VIPT aliasing instruction cache
> > > > > > > Machine: OMAP2430 sdp2430 board
> > > > > > > Memory policy: ECC disabled, Data cache writeback
> > > > > > > OMAP2430
>
> > > > > > > SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
> > > > > > > Built 1 zonelists in Zone order, mobility grouping on. Total
> > > pages:
> > > > > > > 16256
> > > > > > > Kernel command line: console=ttyS0,115200n8=noinitrd
> > > ip=192.168.8.203
> > > > > > > root=/dev/
> > > > > > > nfs rw nfsroot=192.168.8.83:
> > > /home/vivek/omap2430/Android2.2/RFS,nolock
> > > > > > > mem=64M v
> > > > > > > ideo=omapfb.mode=dvi:240x320init=/init
> > > > > > > PID hash table entries: 256 (order: -2, 1024 bytes)
> > > > > > > Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
> > > > > > > Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
> > > > > > > Memory: 64MB = 64MB total
> > > > > > > Memory: 60876KB available (3340K code, 445K data, 116Kinit, 0K
> > > > > > > highmem)
> > > > > > > Hierarchical RCU implementation.
> > > > > > > NR_IRQS:384
> > > > > > > Clocking rate (Crystal/DPLL/MPU): 13.0/660/330 MHz
> > > > > > > GPMC revision 3.0
> > > > > > > IRQ: Found an INTC at 0xd80fe000 (revision 3.0) with 96 interrupts
> > > > > > > Total of 96 interrupts on 1 active controller
> > > > > > > OMAP243x GPIO hardware version 2.4
> > > > > > > OMAP clockevent source: GPTIMER1 at 13000000 Hz
> > > > > > > Console: colour dummy device 80x30
> > > > > > > Calibrating delay loop... 329.31 BogoMIPS (lpj=1646592)
> > > > > > > Mount-cache hash table entries: 512
> > > > > > > CPU: Testing write buffer coherency: ok
> > > > > > > NET: Registered protocol family 16
> > > > > > > OMAP DMA hardware revision 4.0
> > > > > > > bio: create slab <bio-0> at 0
> > > > > > > i2c_omap i2c_omap.1: bus 1 rev3.7 at 400 kHz
> > > > > > > i2c_omap i2c_omap.2: bus 2 rev3.7 at 2600 kHz
> > > > > > > twl4030: PIH (irq 7) chaining IRQs 368..375
> > > > > > > twl4030: power (irq 373) chaining IRQs 376..383
> > > > > > > Switching to clocksource gp timer
> > > > > > > NET: Registered protocol family 2
> > > > > > > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> > > > > > > TCP established hash table entries: 2048 (order: 2, 16384 bytes)
> > > > > > > TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
> > > > > > > TCP: Hash tables configured (established 2048 bind 2048)
> > > > > > > TCP reno registered
> > > > > > > NET: Registered protocol family 1
> > > > > > > RPC: Registered udp transport module.
> > > > > > > RPC: Registered tcp transport module.
> > > > > > > RPC: Registered tcp NFSv4.1 backchannel transport module.
> > > > > > > VFS: Disk quotas dquot_6.5.2
> > > > > > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > > > > > > JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
> > > > > > > msgmni has been set to 119
> > > > > > > alg: No test for stdrng (krng)
> > > > > > > io scheduler noop registered
> > > > > > > io scheduler anticipatory registered (default)
> > > > > > > io scheduler deadline registered
> > > > > > > io scheduler cfq registered
> > > > > > > omapfb: configured for panel sdp2430
> > > > > > > omapfb omapfb: timeout waiting for FRAME DONE
> > > > > > > omapfb: DISPC version 3.0 initialized
> > > > > > > Console: switching to colour frame buffer device 30x40
> > > > > > > omapfb: Framebuffer initialized. Total vram 155648 planes 1
> > > > > > > omapfb: Pixclock 5156 kHz hfreq 18.2 kHz vfreq 54.8 Hz
> > > > > > > omap_rng omap_rng: OMAP Random Number Generator ver. 50
> > > > > > > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> > > > > > > serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
> > > > > > > console [ttyS0] enabled
> > > > > > > serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
> > > > > > > serial8250.2: ttyS2 at MMIO 0x4806e000 (irq = 74) is a ST16654
> > > > > > > brd: module loaded
> > > > > > > loop: module loaded
> > > > > > > omapflash.0: Found 1 x16 devices at 0x0 in 16-bit bank
> > > > > > > omapflash.0: Found 1 x16 devices at 0x2000000 in 16-bit bank
> > > > > > > Intel/Sharp Extended Query Table at 0x010A
> > > > > > > Intel/Sharp Extended Query Table at 0x010A
> > > > > > > Intel/Sharp Extended Query Table at 0x010A
> > > > > > > Intel/Sharp Extended Query Table at 0x010A
> > > > > > > Intel/Sharp Extended Query Table at 0x010A
> > > > > > > Intel/Sharp Extended Query Table at 0x010A
> > > > > > > Using buffer write method
> > > > > > > Using auto-unlock on power-up/resume
> > > > > > > cfi_cmdset_0001: Erase suspend on write enabled
> > > > > > > Creating 4 MTD partitions on "omapflash.0":
> > > > > > > 0x000000000000-0x000000040000 : "bootloader"
> > > > > > > 0x000000040000-0x000000060000 : "params"
> > > > > > > 0x000000060000-0x000000260000 : "kernel"
> > > > > > > 0x000000260000-0x000004000000 : "filesystem"
> > > > > > > OneNAND driver initializing
> > > > > > > smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <n...@fluxnic.net>
> > > > > > > eth0: SMC91C94 (rev 9) at c48ae300 IRQ 309 [nowait]
> > > > > > > eth0: Ethernet addr: 08:00:28:01:1b:92
> > > > > > > OMAP Keypad Driver
> > > > > > > i2c /dev entries driver
> > > > > > > OMAP Watchdog Timer Rev 0x22: initial timeout 60 sec
> > > > > > > TCP cubic registered
> > > > > > > NET: Registered protocol family 17
> > > > > > > NET: Registered protocol family 15
> > > > > > > Power Management for OMAP2 initializing
> > > > > > > PRCM revision 1.0
> > > > > > > eth0: link up
> > > > > > > IP-Config: Guessing netmask 255.255.255.0
> > > > > > > IP-Config: Complete:
> > > > > > > device=eth0, addr=192.168.8.203, mask=255.255.255.0,
> > > > > > > gw=255.255.255.255,
> > > > > > >
>
> ...
>
> read more »
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
