On Wed, Apr 9, 2014 at 4:37 PM, Olof Johansson olof@lixom.net wrote:
On Wed, Apr 9, 2014 at 8:33 AM, Kevin Hilman khilman@linaro.org wrote:
On Wed, Apr 9, 2014 at 6:33 AM, Fabio Estevam festevam@gmail.com wrote:
On Wed, Apr 9, 2014 at 5:31 AM, Russell King - ARM Linux linux@arm.linux.org.uk wrote:
On Wed, Apr 09, 2014 at 01:14:51AM -0700, Olof's autobooter wrote:
Failed boards:
cubie2 sunxi_defconfig : FAILED 1:20.72 hummingboard multi_v7_defconfig : FAILED 1:04.66 panda multi_v7_defconfig : FAILED 1:36.13 snowball multi_v7_defconfig : FAILED 1:13.33 wandboard multi_v7_defconfig : FAILED 1:03.73Well, it looks like the Dove fix isn't the full story, and boards are still broken even with the PJ4 fix in place.
mx6 is booting fine with multi_v7_defconfig here (and also in Kevin's boot system).
As Kevin pointed out, the issue Olof is seeing is probably due to dtb and zImage overlap, so he needs to properly adjust the loadaddr/fdt_addr.
Yes. I suspect it's load addr related since I ran into similar failures.
I've moved loadaddrs around, and the i.MX platforms and panda all boot now (1 out of 1 try).
Snowball still has an issue with multi_v7 and cubie2 with sunxi_defconfig due to out-of-date u-boot (don't get me started on that....). I'll bisect snowball shortly.
snowball with multi_v7_defconfig is probably the uImage load addr and entry point.
Recently, _text has a 2M offset since adding qcom platforms to multi_v7, so the snowball uImage has to be created accordingly.
I added a feature to pyboot to get the uImage loadaddr/entrypoint from _text in System.map.
Kevin