[U-Boot] 2017.05-RC3 hanging on DM3730

[Adam Ford]

On Thu, May 4, 2017 at 6:08 PM, Tom Rini <trini at konsulko.com> wrote:
> On Thu, May 04, 2017 at 05:58:47PM -0500, Adam Ford wrote:
>> On Thu, May 4, 2017 at 4:27 PM, Tom Rini <trini at konsulko.com> wrote:
>> > On Thu, May 04, 2017 at 04:06:33PM -0500, Adam Ford wrote:
>> >
>> >> Tom,
>> >>
>> >> I re-synced my U-boot trunk today and did a clean build and found that
>> >> SPL isn't able to load U-Boot.
>> >>
>> >> U-Boot SPL 2017.05-rc3 (May 04 2017 - 15:48:21)
>> >>
>> >>
>> >> I haven't had a chance yet to bisect the issue.  Do you know when you
>> >> plan to do the 2017.05 release?  I'd like to try and locate the issue
>> >> before the final release.
>> >
>> > I'd like to do the release on Monday.  Can you please start bisecting?
>>
>> I bisected it since I won't have time tomorrow or this weekend.
>>
>> Commit 7584f2e0fb0f ("arm: omap3: Compile clock.c with -marm option to
>> unbreak OMAP3530") seems to break the OMAP3630 (DM3730) in that
>> nothing boots at all:
>>
>>    (dead)
>>
>>
>> Commit 19a75b8cf8d1("arm: omap3: Bring back ARM errata workaround
>> 725233") at least shows some activity, but not enough to do anything:
>>
>>    U-Boot SPL 2017.03-00007-g19a75b8 (May 04 2017 - 17:53:10)
>>
>>    (dead)
>>
>> I am wondering if other OMAP36/37 devices have had any issues?
>
> My bbXM is working.  Can you try and see which of the errata is breaking
> your particular setup?  Thanks!

It appears to be a toolchain issue.  I use Buildroot which builds
everything from scratch. I specify some items like glibc, gcc version,
binutils, etc.

I am not sure why the removal of "CFLAGS_clock.o += -marm" causes an issue.

When I built it with Linaro 2016.11 it worked, but that version is
tuned for a corex-A9, but it proves the code is ok.  Sorry for the
noise.

adam
>
> --
> Tom