Compare with my boot log, it seems the next step will boot ipu and display... it's hard to say where is the exactly problem....
Currently if I were you, I would 1. burn the freescale official code with SD and see if it can boot the system 2. go ahead or go back to try other official freescale code like R9.1 or R8 3. if any official code could work on your board, then it means the hardware is ok and you have to go back to check your configuration/build/setting 4. by the way, be careful with your bootloader parameters which saved in the SD, even you burn new code, these parameters never change... hope this help, good luck.. 2010/12/14 Liu Qingwei <lqw1...@gmail.com> > I'm using BBG 3.0 too. > > And I'm facing another problem: can't enable BOARD_LATE_INIT in u-boot, or > the system will halt (function: setup_core_voltage_spi, file: mx51_bbg.c): > -------------- /* Enable VGEN3, VCAM, VAUDIO, VVIDEO, VSD regulators */ > -------------- val = 0x49249; > ----halt---> pmic_reg(slave, 33, val, 1); <halt in this line > > I've been puzzled for a long time. > > Best regards, > Qingwei > > 2010/12/14 Matt Shao <low...@gmail.com> > > Which board are you using? With EVK BBG V3 Board, I can >> successfully boot it... >> >> 2010/12/13, Qingwei <lqw1...@gmail.com>: >> > I'm trying to porting android to i.MX51 board, and exactly follow the >> > R9 user guide, but the board always hangs at particular point, the log >> > is as below, please help. >> > >> > Starting kernel ... >> > >> > Linux version 2.6.31-00839-gb094e97 (l...@inspiron-1420) (gcc version >> > 4.1.2) #7 P >> > REEMPT Mon Dec 13 14:36:55 CST 2010 >> > 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=ttymx >> > c0 di1_primary calibration ip=dhcp >> > 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 new >> > =0x3 >> > 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 0.0 FinVer 0 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) >> > >> > thanks in advance, >> > Qingwei >> > >> > -- >> > 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
