From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7376257954614345728 Date: Thu, 6 Jun 2024 00:24:26 -0700 (PDT) From: Yi Liu To: isar-users Message-Id: In-Reply-To: References: Subject: Re: Duplicated dtb files issue for multiple confiugrations MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_56548_1456320808.1717658666694" X-TUID: 6unAA1VXRQyL ------=_Part_56548_1456320808.1717658666694 Content-Type: multipart/alternative; boundary="----=_Part_56549_882267057.1717658666694" ------=_Part_56549_882267057.1717658666694 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks for the suggestion. This patch has been verified that can solve the= =20 issue for my case.=20 I will keep it as a temporary solution until the better one is found. =20 Best Regards, Liu Yi On Wednesday, June 5, 2024 at 2:07:54=E2=80=AFAM UTC+8 Uladzimir Bely wrote= : > On Mon, 2024-06-03 at 05:46 -0700, 'yi liu' via isar-users wrote: > > Hi all, > >=20 > > 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: > >=20 > > |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. > >=20 > > 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 > >=20 > > Is anyone still working on this issue?=20 > >=20 > > Best Regards, > > Liu Yi > > --=20 > > 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 > >=20 > https://groups.google.com/d/msgid/isar-users/c426ad86-5cc5-42e6-8223-e7a7= e5b3424en%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. > > --=20 > Best regards, > Uladzimir. > ------=_Part_56549_882267057.1717658666694 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

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.

=C2=A0

Best Regards,

Liu Yi


<= div dir=3D"auto" class=3D"gmail_attr">On Wednesday, June 5, 2024 at 2:07:54= =E2=80=AFAM UTC+8 Uladzimir Bely wrote:
On Mon, 2024-06-03 at 05:46 -0700, 'yi liu&#= 39; via isar-users wrote:
> Hi all,
>=20
> I am trying to make use of isar image installer to create the
> installer for some distro based on meta-iot2050
> (https://gi= thub.com/siemens/meta-iot2050). During the build process,
> I got error below:
>=20
> |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:
> |=C2=A0 /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advance= d-m2.dtb
> |=C2=A0 =C2=A0 (matched in manifest-arm64-img-jupiter-base-dev.cop= y_boot_files)
> |=C2=A0 /build/tmp/deploy/images/iot2050/k3-am6528-iot2050-basic.d= tb
> |=C2=A0 =C2=A0 (matched in manifest-arm64-img-jupiter-base-dev.cop= y_boot_files)
> |=C2=A0 /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advance= d-
> pg2.dtb
> |=C2=A0 =C2=A0 (matched in manifest-arm64-img-jupiter-base-dev.cop= y_boot_files)
> |=C2=A0 /build/tmp/deploy/images/iot2050/k3-am6528-iot2050-basic-p= g2.dtb
> |=C2=A0 =C2=A0 (matched in manifest-arm64-img-jupiter-base-dev.cop= y_boot_files)
> |=C2=A0 /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advance= d.dtb
> |=C2=A0 =C2=A0 (matched in manifest-arm64-img-jupiter-base-dev.cop= y_boot_files)
> |=C2=A0 /build/tmp/deploy/images/iot2050/k3-am6548-iot2050-advance= d-sm.dtb
> |=C2=A0 =C2=A0 (matched in manifest-arm64-img-jupiter-base-dev.cop= y_boot_files)
> |Please verify which recipe should provide the above files.
>=20
> It looks like the isar image installer utilizes multiple
> configurations to build the installer image and the target image a= t
> the same time. After searching from the mail list, I found this is= sue
> 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
>=20
> Is anyone still working on this issue?=20
>=20
> Best Regards,
> Liu Yi
> --=20
> 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-u= sers+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/i= sar-users/c426ad86-5cc5-42e6-8223-e7a7e5b3424en%40googlegroups.com
> .

Hello.

Have you tried the patch from
"https://groups.google.com/g/isar-users/c/qAnjahjjfsw di= scussion? Does
it work for you case with installer?
=20
It's still not merged to Isar since it may break some downstreams t= hat
could expect DTB files in their current location in deploy directory.

--=20
Best regards,
Uladzimir.
------=_Part_56549_882267057.1717658666694-- ------=_Part_56548_1456320808.1717658666694--