Dependency loop with kernel-fitimage class

Dependency loop with kernel-fitimage class

[Olivier Dufour]

[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]

Hi,

I'm trying to build a trusted boot image on ARM64 platform using u-boot.
I've added kernel-fitimage to KERNEL_CLASSES, and set UBOOT_SIGN_ENABLE to
"1".

I get the following dependency loop:

> Dependency loop #1 found:
>   Task
> /build/firmware/v3/build/../meta-marvell/recipes-bsp/u-boot/u-boot-marvell_2017.03.bb:do_concat_dtb
> (dependent Tasks ['linux-marvell_4.4.52.bb:do_assemble_fitimage'])
>   Task
> /build/firmware/v3/build/../meta-marvell/recipes-bsp/u-boot/u-boot-marvell_2017.03.bb:do_install
> (dependent Tasks ['pseudo_1.8.2.bb:do_populate_sysroot',
> 'u-boot-marvell_2017.03.bb:do_compile', 'u-boot-marvell_2017.03.bb:
> do_concat_dtb'])
>   Task
> /build/firmware/v3/build/../meta-marvell/recipes-bsp/u-boot/u-boot-marvell_2017.03.bb:do_deploy
> (dependent Tasks ['u-boot-marvell_2017.03.bb:do_install',
> 'u-boot-marvell_2017.03.bb:do_deploy_dtb'])
>   Task
> /build/firmware/v3/build/../meta-marvell/recipes-kernel/linux/linux-marvell_4.4.52.bb:do_assemble_fitimage
> (dependent Tasks ['u-boot-marvell_2017.03.bb:do_deploy',
> 'linux-marvell_4.4.52.bb:do_compile'])


From my understanding, do_assemble_fitimage should only depend on
do_deploy_dtb, since it doesn't require the whole u-boot binary, but only
the dtb.

I did a few patches to get it work eventually, but I wonder if that's the
right way to go. Maybe I'm missing a step in my configuration ?

Regards,

-- 
Olivier Dufour

[-- Attachment #2: Type: text/html, Size: 1946 bytes --]

Re: [poky] Dependency loop with kernel-fitimage class

[Nandor Han]

[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]

On 2018-05-16 13:17, Olivier Dufour wrote:
> Hi,
>
> I'm trying to build a trusted boot image on ARM64 platform using u-boot.
> I've added kernel-fitimage to KERNEL_CLASSES, and set 
> UBOOT_SIGN_ENABLE to "1".
>
> I get the following dependency loop:
>
>     Dependency loop #1 found:
>       Task
>     /build/firmware/v3/build/../meta-marvell/recipes-bsp/u-boot/u-boot-marvell_2017.03.bb:do_concat_dtb
>     (dependent Tasks ['linux-marvell_4.4.52.bb:do_assemble_fitimage'])
>       Task
>     /build/firmware/v3/build/../meta-marvell/recipes-bsp/u-boot/u-boot-marvell_2017.03.bb:do_install
>     (dependent Tasks ['pseudo_1.8.2.bb:do_populate_sysroot',
>     'u-boot-marvell_2017.03.bb:do_compile',
>     'u-boot-marvell_2017.03.bb:do_concat_dtb'])
>       Task
>     /build/firmware/v3/build/../meta-marvell/recipes-bsp/u-boot/u-boot-marvell_2017.03.bb:do_deploy
>     (dependent Tasks ['u-boot-marvell_2017.03.bb:do_install',
>     'u-boot-marvell_2017.03.bb:do_deploy_dtb'])
>       Task
>     /build/firmware/v3/build/../meta-marvell/recipes-kernel/linux/linux-marvell_4.4.52.bb:do_assemble_fitimage
>     (dependent Tasks ['u-boot-marvell_2017.03.bb:do_deploy',
>     'linux-marvell_4.4.52.bb:do_compile'])
>
>
> From my understanding, do_assemble_fitimage should only depend on 
> do_deploy_dtb, since it doesn't require the whole u-boot binary, but 
> only the dtb.
>
> I did a few patches to get it work eventually, but I wonder if that's 
> the right way to go. Maybe I'm missing a step in my configuration ?
>
Hi,

The keys are injected in DTB, however the newly created DTB needs to be 
recombined with U-Boot, resulting in `u-boot-dtb.bin` (IIRC).

Just to have this in mind :)

Nandor

[-- Attachment #2: Type: text/html, Size: 2842 bytes --]