Hi jrey, What dev platform are you using. What does the display show? if there is no display then what makes you think it hanged.It's done freeing mem blocks. The log looks normal. The boot is completed and adb is available. Did you start using adb. what do your adb logs tell you? What you posted looks like a dmesg log and it won't change after the boot is completed, unless there is a state change. After this point, if you board has a usb port, plug in something and remove it. You should see new messages. I don't think demo images would fail for any platform. They may have bugs but usually never fail.If they do, just report to manufacturer or your retailer.
On Jan 18, 4:05 pm, jrey <[email protected]> wrote: > i am new in this linux embedded systems but im not totally new in > embedded systems, i have used PIC mcu from Microchip before but not > using a dev. board like iMX51 from freescale. Ive managed to boot the > included demo images of WinCE and Ubuntu but im having a hard time > booting the Android R9_1 Demo image which is also included in the > Evaluation Kit. This is the last dump from the serial port: > --------------------------------------------------------------------------- > ------------------------------------------------------- > 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" > MXC MTD nand Driver 3.0 > i.MX GPMI NFC > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller > fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1 > fsl-ehci fsl-ehci.0: irq 18, io base 0x73f80000 > fsl-ehci fsl-ehci.0: 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 > fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller > fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2 > fsl-ehci fsl-ehci.1: irq 14, io base 0x73f80200 > fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00 > usb usb2: configuration #1 chosen from 1 choice > hub 2-0:1.0: USB hub found > hub 2-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 > usbcore: registered new interface driver uvcvideo > USB Video Class driver (v0.1.0) > APM Battery Driver > usb 2-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- > [email protected] > Bluetooth: Virtual HCI driver ver 1.3 > Bluetooth: Generic Bluetooth USB driver ver 0.5 > usbcore: registered new interface driver btusb > pmic_battery: probe of pmic_battery.1 failed with error -1 > 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 2-1: configuration #1 chosen from 1 choice > logger: created 64K log 'log_main' > hub 2-1:1.0: USB hub found > hub 2-1:1.0: 7 ports detected > logger: created 256K log 'log_events' > 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 > 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 > mmc0: new SDHC card at address a0a2 > mmcblk0: mmc0:a0a2 SD04G 3.69 GiB > mmcblk0: > DMA Sound Buffers Allocated:UseIram=1 buf->addr=1fff6000 buf->area=db856000 > size=24576 > > DMA Sound Buffers Allocated:UseIram=1 buf->addr=a90c8000 buf->area=fa301000 > size=24576 > > asoc: SGTL5000 <-> imx-ssi-2-0 mapping ok > p1 p2 p3 < p5 p6 > p4 > 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 > hcd_bus_suspend > ehci_bus_suspend > OTG wakeup irq is enabled > OTG phy lowpower enable > USB Host suspended > RPC: Registered udp transport module. > RPC: Registered tcp transport module. > <6>DVI device plug-out > 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: c0686a80 > android_bind > mass_storage_function_add > android_usb gadget: Number of LUNs=3 > adb_function_add > android_usb gadget: android_usb ready > Suspend udc for OTG auto detect > OTG wakeup irq is enabled > udc resume > OTG wakeup irq disable > OTG phy lowpower disable > OTG wakeup irq is enabled > OTG phy lowpower enable > dr_controller_run: udc enter low power mode > USB Gadget resumed > 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-01-01 01:31:15 UTC > (5475) > Freeing init memory: 176K > init: cannot open '/initlogo.rle' > EXT4-fs (mmcblk0p2): barriers enabled > kjournald2 starting: pid 2068, dev mmcblk0p2:8, commit interval 5 > seconds > EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running > e2fsck is recommended > EXT4-fs (mmcblk0p2): internal journal on mmcblk0p2:8 > EXT4-fs (mmcblk0p2): delayed allocation enabled > EXT4-fs: mballoc enabled > EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode > EXT4-fs (mmcblk0p5): barriers enabled > kjournald2 starting: pid 2069, dev mmcblk0p5:8, commit interval 5 > seconds > EXT4-fs (mmcblk0p5): warning: maximal mount count reached, running > e2fsck is recommended > EXT4-fs (mmcblk0p5): internal journal on mmcblk0p5:8 > EXT4-fs (mmcblk0p5): delayed allocation enabled > EXT4-fs: mballoc enabled > EXT4-fs (mmcblk0p5): recovery complete > EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode > EXT4-fs (mmcblk0p6): barriers enabled > kjournald2 starting: pid 2070, dev mmcblk0p6:8, commit interval 5 > seconds > EXT4-fs (mmcblk0p6): warning: maximal mount count reached, running > e2fsck is recommended > EXT4-fs (mmcblk0p6): internal journal on mmcblk0p6:8 > EXT4-fs (mmcblk0p6): delayed allocation enabled > EXT4-fs: mballoc enabled > EXT4-fs (mmcblk0p6): recovery complete > EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode > init: cannot find '/system/etc/install-recovery.sh', disabling > 'flash_recovery' > enabling adb > adb_open > # usb 2-1.6: new high speed USB device using fsl-ehci and address 3 > usb 2-1.6: configuration #1 chosen from 1 choice > scsi0 : SCSI emulation for USB Mass Storage devices > warning: `wpa_supplicant' uses 32-bit capabilities (legacy support in > use) > otg is idle for some times,so we close the clock 9203120 > close otg clk ok > scsi 0:0:0:0: Direct-Access USB TO I DE/SATA Device 0009 PQ: 0 > ANSI: 0 > sd 0:0:0:0: [sda] Attached SCSI disk > pmem: request for physical address of pmem region from process 2156. > request_suspend_state: wakeup (3->0) at 23482776287 (1970-01-01 > 01:31:36.275807876 UTC) > Not all allocated memory blocks were freed. Doing it now. > Freeing list entry #0, gpuaddr=ab300000 > Freeing list entry #1, gpuaddr=ab301000 > Freeing list entry #2, gpuaddr=ab311000 > Freeing list entry #3, gpuaddr=ab343000 > Freeing list entry #6, gpuaddr=ab364000 > Freeing list entry #7, gpuaddr=ab366000 > Freeing list entry #8, gpuaddr=ab386000 > Freeing list entry #103, gpuaddr=ab976000 > ---------------------------------------------------------------------- > The system hangs at this point (or i assumed it hangs), or should i > wait a lot more? is it checking something from the board or busy > freeing mem blocks? Can someone pls. help me boot the demo image? im > actually studying linux embedded systems/device drivers but i can't > continue if i can't even boot the demo image. > > Thanks in advance guys, have a nice day and God bless always. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
