On Fri, Dec 4, 2015 at 10:23 AM, Hannes Schmelzer Hannes.Schmelzer@br-automation.com wrote:
Hi Hannes,
Hi
it is not a problem in my case as I'm booting from mmc0 and according to the SPL, it could find u-boot.img. There seems to be something u-boot.img starting code, that makes problems.
Just in case I've tried reverting the patch, but the issue remains.
Okay ... maybe you could do some git bisect if you have a known working revision to find out which commit introduced failure.
c7b9686d5d482c8e952598841ea467e6ec0ec0de is the first bad commit commit c7b9686d5d482c8e952598841ea467e6ec0ec0de Author: Thomas Chou thomas@wytron.com.tw Date: Thu Nov 19 21:48:12 2015 +0800
ns16550: unify serial_omap
Unify serial_omap, and use the generic binding.
Signed-off-by: Thomas Chou thomas@wytron.com.tw Reviewed-by: Tom Rini trini@konsulko.com Acked-by: Simon Glass sjg@chromium.org
:040000 040000 a7f81b05b55c059f564705661d4b1365bac66a41 113024998957dbdaf844d4c13d081f0364c1a030 M board :040000 040000 5213aea092fb657216f97666289defd572c6dc0f 2795213aa40831ee4b60d27aba7c8b3fb356662b M drivers :040000 040000 e727eb53a5f60c0376355d27c39b6636121f1827 a8cc2d9a8580ccffe4b2d11c898dde27a9c47065 M include
On Fri, Dec 4, 2015 at 9:39 AM, Hannes Schmelzer
hannes@schmelzer.or.at wrote:
Hi,
Does your board boot from MMC1 ? I had similar problem on my b&r boards ... i haven't solved it at all neither walked deep to find out hat the root cause is.
just try to revert locally the commit
a1e56cf6d430d78db3a4dc08a422311145e32315 spl: mmc: add support for BOOT_DEVICE_MMC2
this works for me ... but i didn't have time yet to debug this fully. Maybe next week.
let me know what happens on your board.
best regards, Hannes
On 12/04/2015 09:26 AM, Yegor Yefremov wrote:
git master fails to start u-boot.img on at least am335x_evm_defconfig some other similar boards:
U-Boot SPL 2016.01-rc1-00373-gbe30dfb (Dec 04 2015 - 08:51:13) Trying to boot from MMC reading args spl_load_image_fat_os: error reading image args, err - -1 reading u-boot.img reading u-boot.img
Compiler used:
arm-linux-gnueabihf-gcc -v Using built-in specs. COLLECT_GCC=arm-linux-gnueabihf-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../src/configure -v --with-pkgversion=' 4.9.2-10' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,go,fortran,objc --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --disable-libquadmath --enable-plugin --with-system-zlib --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=arm-linux-gnueabihf --program-prefix=arm-linux- gnueabihf- Thread model: posix gcc version 4.9.2 ( 4.9.2-10)
Any idea?
Regards, Yegor _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot