Hi Vinay, do you get any tux image when the kernel goes up? Or any touchscreen calibration procedure?
[]'s Hamilton Vera On Mon, Dec 6, 2010 at 1:30 PM, Vinay <vinayku...@gmail.com> wrote: > Hi Matt and Hamilton, > > I'm so sorry. I have made a mistake in my post. I have actually used > "R9". Not R7. > And I'm using imx51 BBG EVK. > > I did refer to the iMx android R9 user guide. The log which I have > posted was when I used R9. > Kindly excuse for the mistake. Please let me know how I can go about > it further. > > Thanks a lot > > Vinay. > > On Dec 6, 2:01 pm, Vinay <vinayku...@gmail.com> wrote: >> Hi, >> >> I'm trying to port froyo to imx 51 board. I have followed the >> instructions given in the document: iMx Android R7 User guide. I have >> not encountered any error while building the u-boot, kernel and >> android images. >> >> However the board does not boot and hangs at a particular point. The >> log gathered using minicom is as below. I'm a new to this, please let >> me know what is going wrong. >> >> Starting >> kernel ... >> >> Linux version 2.6.31-00839-gb0f5b7f (ic012...@blrkapt0675pc) (gcc >> version 4.1.20 >> CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), >> cr=10c53c7f >> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction >> cache >> Machine: Freescale MX51 Babbage >> Board >> Memory policy: ECC disabled, Data cache >> writeback >> Built 1 zonelists in Zone order, mobility grouping on. Total pages: >> 109728 >> Kernel command line: console=ttymxc0,115200 init=/init >> androidboot.console=ttymp >> Unknown boot option `androidboot.console=ttymxc0': >> ignoring >> PID hash table entries: 2048 (order: 11, 8192 >> bytes) >> Dentry cache hash table entries: 65536 (order: 6, 262144 >> bytes) >> Inode-cache hash table entries: 32768 (order: 5, 131072 >> bytes) >> Memory: 432MB = 432MB >> total >> Memory: 431664KB available (5188K code, 922K data, 168K init, 0K >> highmem) >> SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, >> Nodes=1 >> NR_IRQS: >> 368 >> MXC IRQ >> initialized >> MXC_Early serial console at MMIO 0x73fbc000 (options >> '115200') >> console [ttymxc0] >> enabled >> Console: colour dummy device >> 80x30 >> Calibrating delay loop... 799.53 BogoMIPS >> (lpj=3997696) >> Mount-cache hash table entries: >> 512 >> CPU: Testing write buffer coherency: >> ok >> regulator: core version >> 0.5 >> NET: Registered protocol family >> 16 >> i.MX IRAM pool: 128 >> k...@0xdb840000 >> IRAM >> READY >> CPU is i.MX51 Revision >> 3.0 >> MXC GPIO >> hardware >> iomux_config_mux: Warning: iomux pin config changed, reg=f7ea8134, >> prev=0x1 ne3 >> Using SDMA >> I.API >> MXC DMA API >> initialized >> bio: create slab <bio-0> at >> 0 >> SCSI subsystem >> initialized >> CSPI: mxc_spi-0 >> probed >> usbcore: registered new interface driver >> usbfs >> usbcore: registered new interface driver >> hub >> usbcore: registered new device driver >> usb >> MXC I2C >> driver >> MXC I2C >> driver >> MXC HS I2C >> driver >> IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), >> 5F(6,7) >> Bluetooth: Core ver >> 2.15 >> NET: Registered protocol family >> 31 >> Bluetooth: HCI device and connection manager >> initialized >> Bluetooth: HCI socket layer >> initialized >> mc13892 Rev 2.0 FinVer 2 >> detected >> Initializing regulators for >> Babbage. >> regulator: SW1: 600 <--> 1375 >> mV >> regulator: SW2: 900 <--> 1850 >> mV >> regulator: SW3: 1100 <--> 1850 >> mV >> regulator: SW4: 1100 <--> 1850 >> mV >> regulator: SWBST: 0 >> mV >> regulator: VIOHI: 0 >> mV >> regulator: VPLL: 1050 <--> 1800 >> mV >> regulator: VDIG: 1650 >> mV >> regulator: VSD: 1800 <--> 3150 >> mV >> regulator: VUSB2: 2400 <--> 2775 >> mV >> regulator: VVIDEO: 2775 >> mV >> regulator: VAUDIO: 2300 <--> 3000 >> mV >> regulator: VCAM: 2500 <--> 3000 mV fast >> normal >> regulator: VGEN1: 1200 >> mV >> regulator: VGEN2: 1200 <--> 3150 >> mV >> regulator: VGEN3: 1800 <--> 2900 >> mV >> regulator: VUSB: 0 >> mV >> regulator: GPO1: 0 >> mV >> regulator: GPO2: 0 >> mV >> regulator: GPO3: 0 >> mV >> regulator: GPO4: 0 >> mV >> Device spi1.0 >> probed >> NET: Registered protocol family >> 2 >> IP route cache hash table entries: 4096 (order: 2, 16384 >> bytes) >> TCP established hash table entries: 16384 (order: 5, 131072 >> bytes) >> TCP bind hash table entries: 16384 (order: 4, 65536 >> bytes) >> TCP: Hash tables configured (established 16384 bind >> 16384) >> TCP reno >> registered >> NET: Registered protocol family >> 1 >> Trying to unpack rootfs image as >> initramfs... >> Freeing initrd memory: >> 208K >> LPMode driver module >> loaded >> Static Power Management for Freescale >> i.MX51 >> PM driver module >> loaded >> sdram autogating driver module >> loaded >> Bus freq driver module >> loaded >> DI1 is >> primary >> mxc_dvfs_core_probe >> DVFS driver module >> loaded >> i.MXC CPU frequency >> driver >> DVFS PER driver module >> loaded >> ashmem: >> initialized >> msgmni has been set to >> 843 >> alg: No test for stdrng >> (krng) >> io scheduler noop >> registered >> io scheduler anticipatory >> registered >> io scheduler deadline >> registered >> io scheduler cfq registered >> (default) >> mxc_ipu mxc_ipu: Channel already disabled >> 9 >> mxc_ipu mxc_ipu: Channel already uninitialized >> 9 >> Console: switching to colour frame buffer device >> 100x30 >> fbcvt: 1024x...@60: CVT Name - . >> 786M3 >> regulator: get() with no >> identifier >> regulator: get() with no >> identifier >> regulator: get() with no >> identifier >> mxci2c_wait_writefifo:wait >> error >> Serial: MXC Internal UART >> driver >> mxcintuart.0: ttymxc0 at MMIO 0x73fbc000 (irq = 31) is a Freescale >> i.MX >> console handover: boot [ttymxc0] -> real >> [ttymxc0] >> mxcintuart.1: ttymxc1 at MMIO 0x73fc0000 (irq = 32) is a Freescale >> i.MX >> mxcintuart.2: ttymxc2 at MMIO 0x7000c000 (irq = 33) is a Freescale >> i.MX >> brd: module >> loaded >> loop: module >> loaded >> pmem_adsp: 1 >> init >> pmem_gpu: 3 >> init >> FEC Ethernet >> Driver >> fec_enet_mii_bus: >> probed >> IEEE1588: ptp-timer is >> unavailable >> PPP generic driver version >> 2.4.2 >> mxc_dataflash spi1.1: at45db321d (1000 KBytes) pagesize 512 bytes >> (OTP) >> Creating 2 MTD partitions on >> "mxc_dataflash": >> 0x000000000000-0x000000100000 : >> "bootloader" >> 0x000000100000-0x000000400000 : >> "kernel" >> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) >> Driver >> fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host >> Controller >> fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number >> 1 >> fsl-ehci fsl-ehci.1: irq 14, io base >> 0x73f80200 >> fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI >> 1.00 >> usb usb1: configuration #1 chosen from 1 >> choice >> hub 1-0:1.0: USB hub >> found >> hub 1-0:1.0: 1 port >> detected >> Initializing USB Mass Storage >> driver... >> usbcore: registered new interface driver usb- >> storage >> USB Mass Storage support >> registered. >> usbcore: registered new interface driver >> usbserial >> USB Serial support registered for >> generic >> usbcore: registered new interface driver >> usbserial_generic >> usbserial: USB Serial Driver >> core >> USB Serial support registered for GSM modem (1- >> port) >> usbcore: registered new interface driver >> option >> option: v0.7.2:USB Driver for GSM >> modems >> ARC USBOTG Device Controller driver (1 August >> 2005) >> mice: could not register psaux device, error: >> -16 >> mice: PS/2 mouse device common for all >> mice >> MXC keypad >> loaded >> clk: Unable to get requested clock: >> kpp_clk >> input: mxckpd as /devices/virtual/input/ >> input0 >> mc13892 rtc probe >> start >> pmic_rtc pmic_rtc.1: rtc core: registered pmic_rtc as >> rtc0 >> mc13892 rtc probe >> succeed >> i2c /dev entries >> driver >> Linux video capture interface: >> v2.00 >> i2c-adapter i2c-0: ACK not >> received >> ov3640_write_reg:write reg >> error:reg=3012,val=80 >> mxc_v4l2_output mxc_v4l2_output.0: Registered device >> video1 >> usb 1-1: new high speed USB device using fsl-ehci and address >> 2 >> i2c-adapter i2c-1: ACK not >> received >> MXC WatchDog Driver >> 2.0 >> clk: Unable to get requested clock: >> wdog_clk >> MXC Watchdog # 0 Timer: initial timeout 60 >> sec >> device-mapper: uevent: version >> 1.0.3 >> device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm- >> de...@redhat.com >> Bluetooth: Virtual HCI driver ver >> 1.3 >> Bluetooth: Generic Bluetooth USB driver ver >> 0.5 >> usbcore: registered new interface driver >> btusb >> VPU >> initialized >> mxsdhci: MXC Secure Digital Host Controller Interface >> driver >> mxsdhci: MXC SDHCI Controller >> Driver. >> mmc0: SDHCI detect irq 128 irq 1 INTERNAL >> DMA >> mxsdhci: MXC SDHCI Controller >> Driver. >> mmc1: SDHCI detect irq 134 irq 2 INTERNAL >> DMA >> Registered led device: >> pmic_ledsr >> Registered led device: >> pmic_ledsg >> Registered led device: >> pmic_ledsb >> usbcore: registered new interface driver >> usbhid >> usbhid: v2.6:USB HID core >> driver >> usb 1-1: configuration #1 chosen from 1 >> choice >> logger: created 64K log >> 'log_main' >> logger: created 256K log >> 'log_events' >> hub 1-1:1.0: USB hub >> found >> hub 1-1:1.0: 7 ports >> detected >> logger: created 64K log >> 'log_radio' >> logger: created 64K log >> 'log_system' >> Advanced Linux Sound Architecture Driver Version >> 1.0.20. >> regulator: Unable to get requested regulator: >> VDDD >> sgtl5000-i2c 1-000a: SGTL5000 revision >> 17 >> mmc0: new high speed SD card at address >> 1234 >> mmcblk0: mmc0:1234 SA02G 1.83 >> GiB >> mmcblk0: p1 p2 p3 < p5 p6 > >> p4 >> No device for DAI imx- >> ssi-1-0 >> No device for DAI imx- >> ssi-1-1 >> No device for DAI imx- >> ssi-2-0 >> No device for DAI imx- >> ssi-2-1 >> DMA Sound Buffers Allocated:UseIram=1 buf->addr=1fff6000 buf->area=db856000 >> siz6 >> >> DMA Sound Buffers Allocated:UseIram=1 buf->addr=a9298000 buf->area=fa31d000 >> siz6 >> >> asoc: SGTL5000 <-> imx-ssi-2-0 mapping >> ok >> ALSA device >> list: >> #0: imx-3stack >> (SGTL5000) >> TCP cubic >> registered >> NET: Registered protocol family >> 10 >> IPv6 over IPv4 tunneling >> driver >> NET: Registered protocol family >> 17 >> Bluetooth: L2CAP ver >> 2.13 >> Bluetooth: L2CAP socket layer >> initialized >> Bluetooth: SCO (Voice Link) ver >> 0.6 >> Bluetooth: SCO socket layer >> initialized >> Bluetooth: RFCOMM TTY layer >> initialized >> Bluetooth: RFCOMM socket layer >> initialized >> Bluetooth: RFCOMM ver >> 1.11 >> Bluetooth: BNEP (Ethernet Emulation) ver >> 1.3 >> Bluetooth: BNEP filters: protocol >> multicast >> Bluetooth: HIDP (Human Interface Emulation) ver >> 1.2 >> usb 1-1.2: new low speed USB device using fsl-ehci and address >> 3 >> RPC: Registered udp transport >> module. >> RPC: Registered tcp transport >> module. >> <6>DVI device plug- >> in >> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev >> 2 >> regulator_init_complete: disabling >> GPO4 >> regulator_init_complete: disabling >> GPO3 >> regulator_init_complete: disabling >> GPO2 >> regulator_init_complete: disabling >> GPO1 >> regulator_init_complete: disabling >> VGEN1 >> regulator_init_complete: disabling >> VCAM >> regulator_init_complete: disabling >> VAUDIO >> regulator_init_complete: disabling >> VSD >> regulator_init_complete: disabling >> SWBST >> android >> init >> android_probe pdata: >> c0574054 >> android_bind >> mass_storage_function_add >> android_usb gadget: Number of >> LUNs=3 >> adb_function_add >> android_usb gadget: android_usb >> ready >> udc >> run >> fsl-usb2-udc: bind to driver >> android_usb >> input: mxc_ts as /devices/virtual/input/ >> input1 >> mxc input touchscreen >> loaded >> pmic_rtc pmic_rtc.1: setting system clock to 1970-02-23 21:14:41 UTC >> (4655681) >> usb 1-1.2: configuration #1 chosen from 1 >> choice >> input: Dell Dell USB Keyboard as /devices/platform/fsl-ehci.1/ >> usb1/1-1/1-1.2/1-2 >> generic-usb 0003:413C:2003.0001: input: USB HID v1.10 Keyboard [Dell >> Dell USB K0 >> IP-Config: Failed to open >> eth0 >> IP-Config: No network devices >> available. >> Freeing init memory: >> 168K >> init: cannot open '/ >> initlogo.rle' >> kjournald starting. Commit interval 5 >> seconds >> EXT3 FS on mmcblk0p2, internal >> journal >> EXT3-fs: mounted filesystem with writeback data >> mode. >> usb 1-1.6: new high speed USB device using fsl-ehci and address >> 4 >> usb 1-1.6: configuration #1 chosen from 1 >> choice >> scsi0 : SCSI emulation for USB Mass Storage >> devices >> kjournald starting. Commit interval 5 >> seconds >> EXT3 FS on mmcblk0p5, internal >> journal >> EXT3-fs: recovery >> complete. >> EXT3-fs: mounted filesystem with writeback data >> mode. >> kjournald starting. Commit interval 5 >> seconds >> EXT3 FS on mmcblk0p6, internal >> journal >> EXT3-fs: recovery >> complete. >> EXT3-fs: mounted filesystem with writeback data >> mode. >> scsi 0:0:0:0: Direct-Access USB TO I DE/SATA Device 0041 PQ: 0 >> ANSI: 0 >> sd 0:0:0:0: [sda] Attached SCSI disk >> >> (This is where, nothing happens further) >> >> Thanks in advance, >> Vinay. > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- Hamilton Vera int Administrator (char Network[],char ComputationalSystems[]) http://hvera.wordpress.com -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
