Dear Fabio Estevam, > On Fri, Apr 26, 2013 at 11:20 AM, Fabio Estevam <[email protected]> wrote: > > On Fri, Apr 26, 2013 at 11:15 AM, Marek Vasut <[email protected]> wrote: > >> Did you apply that patch of mine ? > > > > Yes, but does not help on this particular issue. > > Well, actually it helped in some way. The reset pattern is different > now and after several attempts the kernel booted: > > U-Boot 2013.04-dirty (Apr 26 2013 - 11:24:08) > > CPU: Freescale i.MX23 rev1.3 at 454 MHz > BOOT: SSP SD/MMC #0 > DRAM: 128 MiB > MMC: MXS MMC: 0 > In: serial > Out: serial > Err: serial > Hit any key to stop autoboot: 0 > mmc0 is current device > reading boot.scr > ** Unable to read file boot.scr ** > reading uImage > 3258040 bytes read in 1113 ms (2.8 MiB/s) > Booting from mmc ... > reading imx23-evk.dtb > 20944 bytes read in 33 ms (619.1 KiB/s) > ## Booting kernel from Legacy Image at 42000000 ... > Image Name: Linux-3.8.8-fslc+g7fd77a4 > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 3257976 Bytes = 3.1 MiB > Load Address: 40008000 > Entry Point: 40008000 > Verifying Checksum ... OK > ## Flattened Device Tree blob at 41000000 > Booting using the fdt blob at 0x41000000 > Loading Kernel Image ... OK > OK > Loading Device Tree to 47b72000, end 47b7a1cf ... OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > HTLLCLC
This is a DRAM issue for sure. What compression algo do you use to compress the kernel btw ? _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
