I think it would be much easier for you to check with elinux people. They have already made Android run on beagle board. Take a look at http://elinux.org/Android_on_OMAP Yi On Mon, 2009-06-15 at 06:13 -0700, Sreehari wrote: > > My output log is like this > > > > > > > Texas Instruments X-Loader 1.41 > > Starting OS Bootloader... > > > > > > U-Boot 1.3.3-00035-gab55ae5-dirty (Jun 16 2008 - 17:35:22) > > > > OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz > > OMAP3 Beagle Board + LPDDR/NAND > > DRAM: 128 MB > > NAND: 256 MiB > > In: serial > > Out: serial > > Err: serial > > Audio Tone on Speakers ... complete > > OMAP3 beagleboard.org # setenv bootargs console=ttyS2,115200n8 > noinitrd root=/dev/mmcblk0p2 video=omapfb.mode=dvi:1280x720mr...@50 > init=/init rootfstype=ext3 rw rootdelay=5 nohz=off > androidboot.console=ttyS2 > > > OMAP3 beagleboard.org # mmcinit > > > OMAP3 beagleboard.org # fatload mmc 0 0x80300000 uImage > > > reading uImage > > > > 1850248 bytes read > > OMAP3 beagleboard.org # bootm 0x80300000 > > > ## Booting kernel from Legacy Image at 80300000 ... > > Image Name: Linux-2.6.29-omap1-07176-g57a557 > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 1850184 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.29-omap1-07176-g57a5578 (a...@anu-desktop) (gcc > version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)) #1 Mon Jun > 15 12:27:19 IST 2009 > > CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=10c5387f > > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache > > Machine: OMAP3 Beagle Board > > Memory policy: ECC disabled, Data cache writeback > > OMAP3430 ES2.1 > > SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000 > > Reserving 12582912 bytes SDRAM for VRAM > > Built 1 zonelists in Zone order, mobility grouping on. Total pages: > 32512 > > Kernel command line: console=ttyS2,115200n8 noinitrd root=/dev/ > mmcblk0p2 video=omapfb.mode=dvi:1280x720mr...@50 init=/init > rootfstype=ext3 rw rootdelay=5 nohz=off androidboot.console=ttyS2 > > Unknown boot option `androidboot.console=ttyS2': ignoring > > Clocking rate (Crystal/DPLL/ARM core): 26.0/332/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: 113280KB available (3368K code, 680K data, 132K init) > > Calibrating delay loop... 504.17 BogoMIPS (lpj=1970176) > > Mount-cache hash table entries: 512 > > CPU: Testing write buffer coherency: ok > > net_namespace: 520 bytes > > regulator: core version 0.5 > > NET: Registered protocol family 16 > > Found NAND on CS0 > > Registering NAND on CS0 > > OMAP DMA hardware revision 4.0 > > bio: create slab <bio-0> at 0 > > OMAP DSS rev 2.0 > > OMAP DISPC rev 3.0 > > OMAP VENC rev 2 > > 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 > > regulator: VMMC1: 1850 <--> 3150 mV normal standby > > regulator: VDAC: 1800 mV normal standby > > regulator: VUSB1V5: 1500 <--> 0 mV normal standby > > regulator: VUSB1V8: 1800 <--> 0 mV normal standby > > regulator: VUSB3V1: 3100 <--> 0 mV normal standby > > regulator: VPLL2: 1800 mV normal standby > > regulator: VSIM: 1800 <--> 3000 mV normal standby > > i2c_omap i2c_omap.3: bus 3 rev3.12 at 100 kHz > > SCSI subsystem initialized > > twl4030_usb twl4030_usb: Initialized TWL4030 USB module > > 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.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 221 > > 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.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 > > i2c /dev entries driver > > Driver 'sd' needs updating - please use bus_type methods > > omap2-nand driver initializing > > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB > 1,8V 16-bit) > > cmdlinepart partition parsing not available > > Creating 5 MTD partitions on "omap2-nand": > > 0x000000000000-0x000000080000 : "X-Loader" > > 0x000000080000-0x000000260000 : "U-Boot" > > 0x000000260000-0x000000280000 : "U-Boot Env" > > 0x000000280000-0x000000680000 : "Kernel" > > 0x000000680000-0x000010000000 : "File System" > > Initializing USB Mass Storage driver... > > usbcore: registered new interface driver usb-storage > > USB Mass Storage support registered. > > twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0 > > mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock > > 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' > > 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 > > clock: clksel_round_rate_div: dpll4_m4_ck target_rate 36000000 > > clock: new_div = 12, new_rate = 36000000 > > omapdss: Could not find exact pixel clock. Requested 23500 kHz, got > 24000 kHz > > twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:04:34 > UTC (946685074) > > Waiting 5sec before mounting root device... > > mmc0: card lacks mandatory switch function, performance might suffer. > > mmc0: new SD card at address b368 > > mmcblk0: mmc0:b368 ADATA 59.8 MiB > > 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) on device 179:2. > > Freeing init memory: 132K > > Warning: unable to open an initial console. > > Failed to execute /init. Attempting defaults... > > Kernel panic - not syncing: No init found. Try passing init= option > to kernel. > > > Thanks, > > On Jun 15, 6:11 pm, Sreehari <[email protected]> wrote: > > Hi Experts, > > > > I am fresher in android porting. I got the android sources from > > git repositories.I build the sources and got the required images.After > > that i copied that images into the SD card in dual partition > > method .One partition(kernel) is in the form of FAT32 and other(file > > system images) in the form of ext3 format. When i tried to bring up my > > board(beagle board -rev B) using this images, i got following errors. > > > > Could anybody please help me? > > > > Thanks , > > Hari > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-porting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-porting?hl=en -~----------~----~----~----~------~----~------~--~---
