LCD is attached, but there's no display, just appears "#" prompt.
maybe android has been not loaded yet, just kernel is started. 2011/1/7 Tiago Maluta <tiago.mal...@gmail.com> > On Wed, Jan 5, 2011 at 4:49 AM, Qingwei <lqw1...@gmail.com> wrote: > > I'm developing with mx51 board (BBG 3.0), and facing a strange > > problem, system always halts, the log as follow: > > > > U-Boot 2009.08-00177-g0928c00-dirty (Dec 18 2010 - 18:05:02) > > > > CPU: Freescale i.MX51 family 3.0V at 800 MHz > > mx51 pll1: 800MHz > > mx51 pll2: 665MHz > > mx51 pll3: 216MHz > > ipg clock : 66500000Hz > > ipg per clock : 665000000Hz > > uart clock : 54000000Hz > > cspi clock : 54000000Hz > > axi_a clock : 166250000Hz > > axi_b clock : 133000000Hz > > emi_slow clock: 83125000Hz > > ddr clock : 166250000Hz > > esdhc clock : 216000000Hz > > Board: MX51 BABBAGE 3.0 [POR] > > Boot Device: MMC > > I2C: ready > > DRAM: 512 MB > > > > ......[OMITTED] > > > > Starting kernel ... > > > > Linux version 2.6.31-01021-g97fca14-dirty (l...@inspiron-1420) (gcc > > version 4.1.2 > > ) #42 PREEMPT Wed Jan 5 13:18:40 CST 2011 > > CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f > > CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache > > > > ......[OMITTED] > > > > 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 > > 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 00:29:03 UTC > > (1743) > > Freeing init memory: 176K > > init: cannot open '/initlogo.rle' > > EXT4-fs (mmcblk0p2): barriers enabled > > kjournald2 starting: pid 2026, dev mmcblk0p2:8, commit interval 5 > > seconds > > 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 2027, dev mmcblk0p5:8, commit interval 5 > > seconds > > EXT4-fs (mmcblk0p5): warning: maximal mount count reached, running > > e2fsck is rec > > ommended > > 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 2028, dev mmcblk0p6:8, commit interval 5 > > seconds > > EXT4-fs (mmcblk0p6): warning: maximal mount count reached, running > > e2fsck is rec > > ommended > > 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 > > hcd_bus_suspend > > ehci_bus_suspend > > OTG wakeup irq is enabled > > OTG phy lowpower enable > > otg is idle for some times,so we close the clock 1202c20 > > close otg clk ok > > [STOP HERE] > > > > Can anybody give some hint? > > > > Thanks. > > Is the LCD attached to the board? When Android boots for the first > time you be prompted to configure touch before the system release the > android shell (on serial), so maybe your system isn't halted but > waiting. > > --tm > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
