[U-Boot] am3517: segmentation fault in Linux after upgrading from arago src to mainline u-boot

Måns Rullgård mans at mansr.com
Thu Nov 28 19:00:13 CET 2013


Tom Rini <trini at ti.com> writes:

> On Thu, Nov 28, 2013 at 05:39:09PM +0100, Yegor Yefremov wrote:
>
>> I'm having problems with the new u-boot (November 2013) and am3517
>> SoC. When I start Debian 7.0 armhf I get lots of Segmentation faults,
>> I can't even perform apt-get udpate. With the older u-boot (arago
>> sources from 2010) everything seems to work properly.
>> 
>> I've checked ATAG_MEM and both u-boot versions deliver same RAM start
>> address and size. I've compared EMIF4 settings
>> (arch/arm/cpu/armv7/omap3/emif4.c) and PINMUX and everything is the
>> same.

Misconfigured memory would have been my first guess.

>> Where else can I look for differences?
>
> Can you bisect the arago tree from what it's based on, to what the top
> of tree is there?  Some errata or another being patched up I guess..

Which A8 revision does this chip use?  Is it the same r1p3 as the 3530?

-- 
Måns Rullgård
mans at mansr.com


More information about the U-Boot mailing list