Duplicated dtb files issue for multiple confiugrations

[yi liu]

Hi all,

I am trying to make use of isar image installer to create the installer for some distro based on meta-iot2050 (https://github.com/siemens/meta-iot2050). During the build process, I got error below:

|ERROR: mc:isar-installer:isar-image-installer-1.0-r0 do_copy_boot_files: The recipe isar-|image-installer is trying to install files into a shared area when those files already exist. |Those files and their manifest location are:
|  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-m2.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6528-iot2050-basic.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-pg2.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6528-iot2050-basic-pg2.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|  /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advanced-sm.dtb
|    (matched in manifest-arm64-img-jupiter-base-dev.copy_boot_files)
|Please verify which recipe should provide the above files.

It looks like the isar image installer utilizes multiple configurations to build the installer image and the target image at the same time. After searching from the mail list, I found this issue has been reported in other threads with similar cases (building multiple images for the same machine):
- https://groups.google.com/g/isar-users/c/qAnjahjjfsw
- https://groups.google.com/g/isar-users/c/Va0Ue-ISYeA
- https://groups.google.com/g/isar-users/c/ZMD4XY4dKWQ
- https://groups.google.com/g/isar-users/c/PSGU_AcdPZ8

Is anyone still working on this issue?

Best Regards,
Liu Yi

[Uladzimir Bely]

> --
> You received this message because you are subscribed to the Google
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to isar-users+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/c426ad86-5cc5-42e6-8223-e7a7e5b3424en%40googlegroups.com
> .

Hello.

Have you tried the patch from
"https://groups.google.com/g/isar-users/c/qAnjahjjfsw discussion? Does
it work for you case with installer?

It's still not merged to Isar since it may break some downstreams that
could expect DTB files in their current location in deploy directory.

--
Best regards,
Uladzimir.

[Jan Kiszka]

The patch wasn't merge as we agreed that it is not the best way forward.
We should rather look into avoiding deploy dir for the DTB distribution
(and only come back to it if that turns out to be impossible).

Jan

--
Siemens AG, Technology
Linux Expert Center

[Yi Liu]

Thanks for the suggestion. This patch has been verified that can solve the issue for my case.

I will keep it as a temporary solution until the better one is found.

 

Best Regards,

Liu Yi

[Baurzhan Ismagulov]

On 2024-06-06 00:24, 'Yi Liu' via isar-users wrote:
> Thanks for the suggestion. This patch has been verified that can solve the
> issue for my case.
>
> I will keep it as a temporary solution until the better one is found.

Thanks Liu Yi for the feedback,

To summarize the topics, we're experiencing two different issues:

1. Two images, same machine: Same dtb overwritten in deploy by image.bbclass --
this thread.

Proposals:

- Split by image
- Possibly with on/off switch
- Deploy in kernel recipe

2. Different dtbs overwritten in deploy.

Addressed by splitting by machine-distro:
https://patchwork.isar-build.org/project/isar/patch/20240131144459.23...@ilbers.de/

Deploying in the kernel recipe would solve #1 without splitting the deploy dir.
We'll be sharing our progress on this.

We've checked the use case of rebuilding into a dirty deploy dir with a
different config for the same machine/distro and didn't encounter any issues.
If this is still relevant, we'd like to have the steps to reproduce.

With kind regards,
Baurzhan