On 02/20/2014 07:19 AM, 孙钰 wrote: > The Uboot in Factory (u-boot 2014.01) works for RevB3, > But the kernal fails.... > > Here follows the message: > U-Boot SPL 2014.01 (Feb 05 2014 - 15:07:29) > OMAP4460 ES1.1 > > > U-Boot 2014.01 (Feb 05 2014 - 15:07:29) > > CPU : OMAP4460 ES1.1 > Board: OMAP4 Panda > I2C: ready > DRAM: 1 GiB > MMC: OMAP SD/MMC: 0 > Using default environment > > Net: No ethernet found. > Hit any key to stop autoboot: 0 > mmc0 is current device > SD/MMC found on device 0 > 2113 bytes read in 3 ms (687.5 KiB/s) > Running bootscript from mmc0 ... > ## Executing script at 82000000 > mmc0 is current device > 4690280 bytes read in 215 ms (20.8 MiB/s) > 68363617 bytes read in 3077 ms (21.2 MiB/s) > 23288 bytes read in 8 ms (2.8 MiB/s) > Kernel image @ 0x80000000 [ 0x000000 - 0x479168 ] > ## Loading init Ramdisk from Legacy Image at 82000000 ... > Image Name: Initrd > Image Type: ARM Linux RAMDisk Image (uncompressed) > Data Size: 68363553 Bytes = 65.2 MiB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > ## Flattened Device Tree blob at 80f80000 > Booting using the fdt blob at 0x80f80000 > Using Device Tree in place at 80f80000, end 80f88af7 > > Starting kernel ...
on my non B3 board: http://slexy.org/view/s2YhugU4oW (3.13) http://slexy.org/view/s2mU9djKVq (3.14-rc3) Looking at the dts, I guessed there are cs1 is being attempted, could someone with a B3 board try http://slexy.org/raw/s20dkh58XR out (not an official patch, just to get an idea). I am trying to get my hands to a B3 board to verify as well, but might take a few days. -- Regards, Nishanth Menon -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
