Porting froyo on Zoom2

35 views
Skip to first unread message

kapilddit

unread,
Jan 12, 2011, 4:13:25 AM1/12/11
to omapzoom
Hi
m trying to port froyo on omap zoom2 board. It is working with linux
2.6.29 kernel, m facing problem with linux omap kernel 2.6.32.9.....
I am getting error : kernel penic...

Can u pls give me the link to download the correct kernel with android
pathes...

logs:
OMAP34XX ZOOM2 # setenv ipaddr 172.17.44.54
OMAP34XX ZOOM2 # setenv ipaddr 172.17.44.54
OMAP34XX ZOOM2 # setenv serverip 172.17.44.59
OMAP34XX ZOOM2 # setenv gatewayip 172.17.44.1
OMAP34XX ZOOM2 # setenv netmask 255.255.255.0
OMAP34XX ZOOM2 # setenv bootcmd 'tftpboot 81c00000 uImage ; bootm
81c00000'
OMAP34XX ZOOM2 # setenv bootargs 'console=ttyS3,115200n8 root=/dev/nfs
rw rootdelay=1 ip=dhcp nfsroot=172.17.44.59:/home/Prashant/
target,nolock
mem=256M init=/init videoout=omap24xxvout
omap_vout.video1_numbuffers=4 omap_vout.vid1_static_vrfb_alloc=y
omapfb.vram="0:4M"'
OMAP34XX ZOOM2 # boot
LAN9x18 (0x92210000) detected.
Read mac address: 00:08:EE:03:8C:63
start Auto negotiation... (take ~2sec)
Auto negotiation complete, 100BaseTX, full duplex
TFTP from server 172.17.44.59; our IP address is 172.17.44.54
Filename 'uImage'.
Load address: 0x81c00000
Loading:
#################################################################

#################################################################

#################################################################

#################################################################

#################################################################

#################################################################
#####
done
Bytes transferred = 2021304 (1ed7b8 hex)
## Booting image at 81c00000 ...
Image Name: Linux-2.6.32.27
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2021240 Bytes = 1.9 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
OK

Starting kernel ...

Linux version 2.6.32.27 (root@alok) (gcc version 4.4.1 (Sourcery G++
Lite 2009q3-67) ) #4 Wed Jan 12 17:05:26 IST 2011
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP Zoom2 board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 ES3.1
SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on. Total pages:
65024
Kernel command line: console=ttyS3,115200n8 root=/dev/nfs rw
rootdelay=1 ip=dhcp nfsroot=172.17.44.59:/home/Prashant/target,nolock
mem=256M ini
t=/init videoout=omap24xxvout omap_vout.video1_numbuffers=4
omap_vout.vid1_static_vrfb_alloc=y omapfb.vram="0:4M"
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 255616KB available (3464K code, 303K data, 136K init, 0K
highmem)
Hierarchical RCU implementation.
NR_IRQS:402
clock: init parent: could not find regval 0 for clock dpll2_fck
clock: Could not find fieldval 0 for clock dpll2_fck parent core_ck
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
clock: Could not find fieldval 0 for clock dpll2_fck parent core_ck
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
MUX: setup N28_3430_MMC1_CLK (0xd8002144): 0x0000 -> 0x0118
MUX: setup AE2_3430_MMC2_CLK (0xd8002158): 0x0101 -> 0x0118
MUX: setup AG5_3430_MMC2_CMD (0xd800215a): 0x0101 -> 0x0118
MUX: setup AH5_3430_MMC2_DAT0 (0xd800215c): 0x0101 -> 0x0118
MUX: setup AH4_3430_MMC2_DAT1 (0xd800215e): 0x011c -> 0x0118
MUX: setup AG4_3430_MMC2_DAT2 (0xd8002160): 0x0009 -> 0x0118
MUX: setup AF4_3430_MMC2_DAT3 (0xd8002162): 0x0109 -> 0x0118
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850 <--> 3150 mV normal standby
regulator: VMMC2: 1850 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV normal standby
i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at d80ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
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.
NetWinder Floating Point Emulator V0.97 (double precision)
ashmem: initialized
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.
yaffs Jan 11 2011 18:49:04 Installing.
msgmni has been set to 499
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
serial8250.3: ttyS3 at MMIO 0x10000000 (irq = 262) is a ST16654
console [ttyS3] enabled
brd: module loaded
loop: module loaded
smsc911x: Driver version 2008-10-21.
smsc911x-mdio: probed
eth0: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=ffffffff:
01, irq=-1)
net eth0: MAC Address: 00:08:ee:03:8c:63
usbmon: debugfs is not available
i2c /dev entries driver
Driver for 1-wire Dallas network protocol.
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB .., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 172.17.44.54
IP-Config: Complete:
device=eth0, addr=172.17.44.54, mask=255.255.255.0,
gw=172.17.44.1,
host=172.17.44.54, domain=, nis-domain=(none),
bootserver=0.0.0.0, rootserver=172.17.44.59, rootpath=
Waiting 1sec before mounting root device...
Looking up port of RPC 100003/2 on 172.17.44.59
Looking up port of RPC 100005/1 on 172.17.44.59
VFS: Mounted root (nfs filesystem) on device 0:11.
Freeing init memory: 136K
Warning: unable to open an initial console.
Kernel panic - not syncing: Attempted to kill init!

Thondar, Geetha

unread,
Jan 19, 2011, 1:32:34 PM1/19/11
to omap...@googlegroups.com
You could try the tags "L25.Inc3.4P3 Froyo Release" on Zoom2. They are validated on Zoom3630, but supposedly would work on Zoom2 too.

http://git.omapzoom.org/?p=kernel/omap.git;a=summary

Starting kernel ...

JFFS2 version 2.2. (NAND) (c) 2001-2006 Red Hat, Inc.

Deva R

unread,
Jan 20, 2011, 12:27:32 PM1/20/11
to omap...@googlegroups.com
> m trying to port froyo on omap zoom2 board. It is working with linux
> 2.6.29 kernel, m facing problem with linux omap kernel 2.6.32.9.....
why not K32 as released with froyo for zoom2?? link -
http://git.omapzoom.org/?p=kernel/omap.git;a=tree;hb=refs/heads/p-android-omap-2.6.32

btw, when u meant linux-omap kernel, did u added all android kernel patches?
android requires mandatory set of features on top of linux kernel -
http://git.omapzoom.org/?p=kernel/omap.git;a=blob;f=Documentation/android.txt;hb=refs/heads/p-android-omap-2.6.32

if its taken care, you can start debugging android init program, why its failing
http://elinux.org/Android_Debugging#init_logging

--
Regards,
Deva
www.bittoggler.com

Reply all
Reply to author
Forward
0 new messages