Dear experts,
I am currently trying to build and run the "Android port for OMAP3
with GStreamer integration" on my DevKit8000 board.
However I cannot boot up the Android and I got the following message:
Texas Instruments X-Loader 1.41
Starting on with MMC
Reading boot sector
1085088 Bytes Read from MMC
Starting OS Bootloader from MMC...
U-Boot 1.3.3 (Apr 20 2009 - 10:56:01)
OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 DevKit9000 Board + LPDDR/NAND
DRAM: 128 MB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading uImage
1877872 bytes read
## Booting kernel from Legacy Image at 80300000 ...
Image Name: Linux-2.6.27-omap1-svn260-dirty1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1877808 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing
Linux.........................................................................................................................
done, booting the kernel.
Linux version 2.6.27-omap1-svn260-dirty1 (luofc@LINUXSERVER) (gcc
version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)) #10 Tue May
5 08:55:19 CST 2009
CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=00c5387f
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 Unknown revision
SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
CPU0: L1 I VIPT cache. Caches unified at level 2, coherent at level 3
CPU0: Level 1 cache is separate instruction and data
CPU0: I cache: 16384 bytes, associativity 4, 64 byte lines, 64 sets,
supports RA
CPU0: D cache: 16384 bytes, associativity 4, 64 byte lines, 64 sets,
supports RA WB WT
CPU0: Level 2 cache is unified
CPU0: unified cache: 262144 bytes, associativity 8, 64 byte lines, 512
sets,
supports WA RA WB WT
Built 1 zonelists in Zone order, mobility grouping on. Total pages:
32512
Kernel command line: console=ttyS2,115200n8 noinitrd root=/dev/
mmcblk0p2 init=/init rootdelay=1
clock: virt_vdd1_prcm_set: missing clockdomain<3>clock:
virt_vdd2_prcm_set: missing clockdomain<6>Clocking rate (Crystal/DPLL/
ARM core): 26.0/266/500 MHz
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
PID hash table entries: 512 (order: 9, 2048 bytes)
OMAP clockevent source: GPTIMER12 at 32768 Hz
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 125496KB available (3460K code, 651K data, 136K init)
Calibrating delay loop... 507.32 BogoMIPS (lpj=1982464)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 288 bytes
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
Switched to new clocking rate (Crystal/DPLL3/MPU): 26.0/266/133 MHz
OMAP DMA hardware revision 4.0
USB: No board-specific platform config found
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
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, host, debug=0
musb_hdrc: USB Host mode controller at d80ab000 using DMA, IRQ 92
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
ashmem: initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) Ac 2001-2006 Red Hat, Inc.
msgmni has been set to 245
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
def_mode =
omapfb: using mode 4.3inch_LCD
omap3beagle_panel_init was invoked
omapfb: configured for panel omap3beagle
omapfb omapfb: timeout waiting for FRAME DONE
pixclock in set_lcd_timings is 10 MHz
DISPC_POL_FREQ = 0x3000
pixclock in set_lcd_timings is 9 MHz
omapfb: DISPC version 3.0 initialized
Console: switching to colour frame buffer device 60x34
omapfb: Framebuffer initialized. Total vram 262144 planes 1
omapfb: Pixclock 9600 kHz hfreq 18.2857 kHz vfreq 63.9 Hz
Serial: 8250/16550 driver4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
dm9000 Ethernet Driver, V1.31
eth0: dm9000a at c8850000,c8852400 IRQ 185 MAC: 00:11:22:33:44:55
(chip)
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
i2c /dev entries driver
Driver 'sd' needs updating - please use bus_type methods
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xb1 (Micron omap2-nand)
NAND bus width 8 instead 16 bit
No NAND device found!!!
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xb1 (Micron NAND 128MiB
1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand":
0x00000000-0x00080000 : "X-Loader"
0x00080000-0x00260000 : "U-Boot"
0x00260000-0x00280000 : "U-Boot Env"
0x00280000-0x00680000 : "Kernel"
0x00680000-0x08000000 : "File System"
usbmon: debugfs is not available
input: omap_twl4030keypad as /class/input/input0
input: gpio-keys as /class/input/input1
ads7846 spi2.0: touchscreen, irq 187
input: ADS784x Touchscreen as /class/input/input2
twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
twl4030_rtc twl4030_rtc: Power up reset detected.
twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
Registered led device: beagleboard::usr0
Registered led device: beagleboard::usr1
Registered led device: beagleboard::pmu_stat
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
Advanced Linux Sound Architecture Driver Version 1.0.17.
usbcore: registered new interface driver snd-usb-audio
ASoC version 0.13.2
OMAP3 Beagle SoC init
TWL4030 Audio Codec init
asoc: twl4030 <-> omap-mcbsp-dai mapping ok
ALSA device list:
#0: omap3beagle (twl4030)
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev
1
twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00
UTC (946684800)
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-
enable.
mmc0: new SD card at address 4fc7
mmcblk0: mmc0:4fc7 SD01G 1006080KiB
mmcblk0: p1 p2
kjournald starting. Commit interval 5 seconds
EXT3 FS on mmcblk0p2, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing init memory: 136K
Warning: unable to open an initial console.
Kernel panic - not syncing: Attempted to kill init!
It seems that it cannot start the init at the android's filesystem.
This have been puzzled me for period of time. Do anyone have any idea
which I can fix it?
Thanks,
James