[U-Boot] Please pull u-boot-dm

[Simon Glass]

Hi Stephen,

On 10 July 2018 at 13:53, Stephen Warren <swarren at wwwdotorg.org> wrote:
> On 07/10/2018 12:47 PM, Tom Rini wrote:
>>
>> On Mon, Jul 09, 2018 at 01:53:43PM -0600, Simon Glass wrote:
>>
>>> Hi Tom.
>>>
>>> Here are some test-coverage and DM core enhancements. Also it adds a
>>> way to access the binman definition from U-Boot.
>>>
>>>
>>> The following changes since commit
>>> 8c5d4fd0ec222701598a27b26ab7265d4cee45a3:
>>>
>>>    Prepare v2018.07 (2018-07-09 10:24:14 -0400)
>>>
>>> are available in the Git repository at:
>>>
>>>    git://git.denx.de/u-boot-dm.git
>>>
>>> for you to fetch changes up to 16b8d6b76992690c65c58dc8b0591496cc5e46ef:
>>>
>>>    binman: Support updating the device tree with calc'd info
>>> (2018-07-09 09:11:00 -0600)
>
>
> This pull has caused intermittent/random build errors on my Jenkins system.
> The log shows:
>
>>   LD      spl/u-boot-spl
>>   OBJCOPY spl/u-boot-spl-nodtb.bin
>>   COPY    spl/u-boot-spl.bin
>>   BINMAN  u-boot-tegra.bin
>>   BINMAN  u-boot-nodtb-tegra.bin
>>   BINMAN  u-boot-dtb-tegra.bin
>> binman: pylibfdt error -9: FDT_ERR_BADMAGIC
>>
>> /var/lib/jenkins/workspace/u-boot-denx_uboot-master-build/src/u-boot/Makefile:1244:
>> recipe for target 'u-boot-tegra.bin' failed
>> make[1]: *** [u-boot-tegra.bin] Error 1
>> make[1]: *** Waiting for unfinished jobs....
>> make[1]: Leaving directory
>> '/var/lib/jenkins/workspace/u-boot-denx_uboot-master-build/build/u-boot/beaver'
>> Makefile:148: recipe for target 'sub-make' failed
>> make: *** [sub-make] Error 2
>> make: Leaving directory
>> '/var/lib/jenkins/workspace/u-boot-denx_uboot-master-build/src/u-boot'
>
>
> This doesn't happen every time; my Jenkins system builds 25 Tegra/sandbox
> boards, yet a varying set of boards fail each time I trigger the build: Just
> beaver the first time, then just colibri_t20 and ventana, then just
> medcom-wide. Note that the system performs incremental builds, if that
> matters.

That might be the fdt_resize() problem which David Gibson has just
sorted out upstream. If you can run binman -D (to get a stack trace)
that might help. I should be able to do a patch if that is the
problem.

That said, I'm working on getting the real pylibffdt applied upstream,
hopefully will not be too much longer.

Regards,
Simon