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 ... 2014-02-20 19:04 GMT+08:00 Alexander Graf <[email protected]>: > > On 18.02.2014, at 16:05, Guillaume Gardet <[email protected]> wrote: > >> >> Le 18/02/2014 15:22, Nishanth Menon a écrit : >>> On 02/18/2014 03:15 AM, Alexander Graf wrote: >>>> >>>>> Am 18.02.2014 um 09:57 schrieb Guillaume Gardet >>>>> <[email protected]>: >>>>> >>>>> Hi, >>>>> >>>>> Le 16/02/2014 15:31, 孙钰 a écrit : >>>>>> Hi all, >>>>>> >>>>>> Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because >>>>>> the Modification of Elpida DDR2 RAM >>>>>> >>>>>> Here follows the serial port messages: >>>>>> U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM: >>>>>> identified size not same as expected size identified: 0 expected: >>>>>> 40000000 >>>>> It seems to be a known problem. See: >>>>> http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-FAQ >>>>> >>>>> Not sure how it will affect other board revision if we rebuild u-boot >>>>> without CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS. >>>>> >>>>> And why upstream u-boot keep things like that if it is known to be broken? >>>> Could we convert this into a runtime check against some easily accessible >>>> version register? >>> >>> Commit 675cc77a3ae45e8b0ec17128563264d4a509f628 in upstream >>> also for the very latest, consider: >>> http://patchwork.ozlabs.org/patch/320811/ >>> >> >> So ,we could upgrade to latest u-boot (2014.01) from Base:System project to >> 13.1:Ports. >> >> Dirk or Alex, could you do that, please? > > Do you really think it's a good idea to update to the latest u-boot for 13.1? > There's a good chance other boards break, no? > > > Alex > > -- > To unsubscribe, e-mail: [email protected] > To contact the owner, e-mail: [email protected] > -- 孙钰 Address:北航新主楼F1015 -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
