am62: apply u-boot config fragment on ti-falcon
PATCH 1/3 am62: apply u-boot config fragment on ti-falcon
The am62x_r5_falcon.config fragment in u-boot enables falcon boot support for R5 SPL, this patch enables the config fragment for am62a, 62p, 62x and 62lp evms based on ti-falcon distro override.
--- meta-ti-bsp/conf/machine/am62axx-evm-k3r5.conf | 2 ++ meta-ti-bsp/conf/machine/am62pxx-evm-k3r5.conf | 2 ++ meta-ti-bsp/conf/machine/am62xx-evm-k3r5.conf | 2 ++ meta-ti-bsp/conf/machine/am62xx-lp-evm-k3r5.conf | 2 ++ 4 files changed, 8 insertions(+)
meta-ti-bsp/conf/machine/am62axx-evm-k3r5.conf +2 -0
@@ -9,3 +9,5 @@ SYSFW_CONFIG = "evm" SYSFW_SUFFIX = "hs-fs" UBOOT_MACHINE = "am62ax_evm_r5_defconfig" + +UBOOT_CONFIG_FRAGMENTS:ti-falcon = "am62x_r5_falcon.config"
meta-ti-bsp/conf/machine/am62pxx-evm-k3r5.conf +2 -0
@@ -10,3 +10,5 @@ SYSFW_CONFIG = "evm" SYSFW_SUFFIX = "hs-fs" UBOOT_MACHINE = "am62px_evm_r5_defconfig" + +UBOOT_CONFIG_FRAGMENTS:ti-falcon = "am62x_r5_falcon.config"
meta-ti-bsp/conf/machine/am62xx-evm-k3r5.conf +2 -0
@@ -10,3 +10,5 @@ SYSFW_CONFIG = "evm" SYSFW_SUFFIX = "hs-fs" UBOOT_MACHINE = "am62x_evm_r5_defconfig" + +UBOOT_CONFIG_FRAGMENTS:ti-falcon = "am62x_r5_falcon.config"
meta-ti-bsp/conf/machine/am62xx-lp-evm-k3r5.conf +2 -0
@@ -10,3 +10,5 @@ SYSFW_CONFIG = "evm" SYSFW_SUFFIX = "hs-fs" UBOOT_MACHINE = "am62x_lpsk_r5_defconfig" + +UBOOT_CONFIG_FRAGMENTS:ti-falcon = "am62x_r5_falcon.config"
PATCH 2/3 bsp: conf: machine: add ti-falcon.inc
ti-falcon.inc configures the following things for enabling falcon boot:
1. Change fitImage class to kernel-fitimage-legacyhs
2. Update kernel and dtb address for falcon boot
3. Disable kernel compression
--- meta-ti-bsp/conf/machine/include/k3.inc | 4 ++++ meta-ti-bsp/conf/machine/include/ti-falcon.inc | 5 +++++ 2 files changed, 9 insertions(+) create mode 100644 meta-ti-bsp/conf/machine/include/ti-falcon.inc
meta-ti-bsp/conf/machine/include/k3.inc +4 -0
@@ -56,3 +56,7 @@ TI_WKS_BOOTLOADER_APPEND ?= "" do_image_wic[depends] += "virtual/bootloader:do_deploy" SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS2" + +FALCON_INCLUDE:ti-falcon = "conf/machine/include/ti-falcon.inc" + +require ${FALCON_INCLUDE}
meta-ti-bsp/conf/machine/include/ti-falcon.inc new file +5 -0
@@ -0,0 +1,5 @@ +KERNEL_CLASSES:remove = "kernel-fitimage" +KERNEL_CLASSES += "kernel-fitimage-legacyhs" +UBOOT_DTB_LOADADDRESS = "0x82000000" +UBOOT_LOADADDRESS = "0x82200000" +FIT_KERNEL_COMP_ALG = "none"
Re: [meta-ti] [master/scarthgap][PATCH v1 2/3] bsp: conf: machine: add ti-falcon.inc
Quoted 18 lines · Anshul Dalal via lists.yoctoproject.org
ti-falcon.inc configures the following things for enabling falcon boot:
1. Change fitImage class to kernel-fitimage-legacyhs
2. Update kernel and dtb address for falcon boot
3. Disable kernel compressionSigned-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/k3.inc | 4 ++++ meta-ti-bsp/conf/machine/include/ti-falcon.inc | 5 +++++ 2 files changed, 9 insertions(+) create mode 100644 meta-ti-bsp/conf/machine/include/ti-falcon.incmeta-ti-bsp/conf/machine/include/k3.inc +0
-0
meta-ti-bsp/conf/machine/include/k3.inc TI_WKS_BOOTLOADER_APPEND ?= "" · line 60
Quoted 5 lines
meta-ti-bsp/conf/machine/include/k3.inc +2
-0@@ -56,3 +56,7 @@ TI_WKS_BOOTLOADER_APPEND ?= "" do_image_wic[depends] += "virtual/bootloader:do_deploy" SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS2" + +FALCON_INCLUDE:ti-falcon = "conf/machine/include/ti-falcon.inc"
Where and how ti-falcon override is being defined/set?
Quoted 12 lines
meta-ti-bsp/conf/machine/include/k3.inc +1
-0+require ${FALCON_INCLUDE}meta-ti-bsp/conf/machine/include/ti-falcon.inc new file +5
-0@@ -0,0 +1,5 @@ +KERNEL_CLASSES:remove = "kernel-fitimage" +KERNEL_CLASSES += "kernel-fitimage-legacyhs" +UBOOT_DTB_LOADADDRESS = "0x82000000" +UBOOT_LOADADDRESS = "0x82200000" +FIT_KERNEL_COMP_ALG = "none"
Re: [meta-ti] [master/scarthgap][PATCH v1 2/3] bsp: conf: machine: add ti-falcon.inc
Quoted 21 lines · Denys Dmytriyenko
Quoted 20 lines · Anshul Dalal via lists.yoctoproject.org
ti-falcon.inc configures the following things for enabling falcon boot:
1. Change fitImage class to kernel-fitimage-legacyhs
2. Update kernel and dtb address for falcon boot
3. Disable kernel compressionSigned-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/k3.inc | 4 ++++ meta-ti-bsp/conf/machine/include/ti-falcon.inc | 5 +++++ 2 files changed, 9 insertions(+) create mode 100644 meta-ti-bsp/conf/machine/include/ti-falcon.incmeta-ti-bsp/conf/machine/include/k3.inc +0
-0@@ -56,3 +56,7 @@ TI_WKS_BOOTLOADER_APPEND ?= "" do_image_wic[depends] += "virtual/bootloader:do_deploy"
Quoted 6 lines
meta-ti-bsp/conf/machine/include/k3.inc TI_WKS_BOOTLOADER_APPEND ?= "" · line 60
Quoted 3 lines
meta-ti-bsp/conf/machine/include/k3.inc +2
-0SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS2" + +FALCON_INCLUDE:ti-falcon = "conf/machine/include/ti-falcon.inc"Where and how ti-falcon override is being defined/set?
It's a DISTROOVERRIDE set in local.conf as follows:
DISTROOVERRIDES:append = ":ti-falcon"
Quoted 13 lines
Quoted 13 lines
meta-ti-bsp/conf/machine/include/k3.inc +1
-0+require ${FALCON_INCLUDE}meta-ti-bsp/conf/machine/include/ti-falcon.inc new file +5
-0@@ -0,0 +1,5 @@ +KERNEL_CLASSES:remove = "kernel-fitimage" +KERNEL_CLASSES += "kernel-fitimage-legacyhs" +UBOOT_DTB_LOADADDRESS = "0x82000000" +UBOOT_LOADADDRESS = "0x82200000" +FIT_KERNEL_COMP_ALG = "none"
PATCH 3/3 bsp: u-boot: deploy tispl_falcon.bin to rootfs
In reply to Anshul DalalFalcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in IMAGE_INSTALL when ti-falcon is enabled which allows us to deploy the required files to rootfs.
--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1 -0
@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon" KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +11 -0
@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"
@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} } +do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon " + TOOLCHAIN = "gcc"
Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Quoted 19 lines · Anshul Dalal via lists.yoctoproject.org
Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in
IMAGE_INSTALLwhen ti-falcon is enabled which allows us to deploy the required files to rootfs.Signed-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0
meta-ti-bsp/conf/machine/include/ti-falcon.inc line 1
Quoted 1 line
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1
-0@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"
Why += cannot be used here?
Quoted 18 lines
meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +2
-0@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR}
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc do_deploy:append:am62pxx() { · line 385
Quoted 10 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +8
-0} +do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon "
Shouldn't these be specific to ti-falcon only?
Quoted 2 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +1
-0+ TOOLCHAIN = "gcc"
Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Quoted 45 lines · Denys Dmytriyenko
Quoted 19 lines · Anshul Dalal via lists.yoctoproject.org
Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in
IMAGE_INSTALLwhen ti-falcon is enabled which allows us to deploy the required files to rootfs.Signed-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0meta-ti-bsp/conf/machine/include/ti-falcon.inc line 1
Quoted 1 line
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1
-0@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"Why += cannot be used here?
Quoted 20 lines
meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +2
-0@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} }
Quoted 12 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc do_deploy:append:am62pxx() { · line 385
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +8
-0+do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon "Shouldn't these be specific to ti-falcon only?
These are the only supported platforms at the moment, depending on machine specific overrides allows us to throw an error at the recipe parsing stage instead of having to wait till the do_install task fails to copy the non-existent tispl_falcon.bin in case of unsupported platforms.
As support for more platforms is added, the list can be expanded until all platforms are supported when we can just have a ti-falcon override.
Quoted 2 lines
Quoted 2 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +1
-0+ TOOLCHAIN = "gcc"
Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Quoted 59 lines · Anshul Dalal
Quoted 45 lines · Denys Dmytriyenko
Quoted 19 lines · Anshul Dalal via lists.yoctoproject.org
Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in
IMAGE_INSTALLwhen ti-falcon is enabled which allows us to deploy the required files to rootfs.Signed-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0meta-ti-bsp/conf/machine/include/ti-falcon.inc line 1
Quoted 1 line
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1
-0@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"Why += cannot be used here?
Quoted 20 lines
meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +2
-0@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} }Quoted 12 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc do_deploy:append:am62pxx() { · line 385
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +8
-0+do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon "Shouldn't these be specific to ti-falcon only?
Quoted 5 lines
These are the only supported platforms at the moment, depending on machine specific overrides allows us to throw an error at the recipe parsing stage instead of having to wait till the
do_installtask fails to copy the non-existent tispl_falcon.bin in case of unsupported platforms.
What happens when you build for am62xx-evm and ti-falcon is not enabled?
Quoted 2 lines
As support for more platforms is added, the list can be expanded until all platforms are supported when we can just have a ti-falcon override.
Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Quoted 60 lines · Denys Dmytriyenko
Quoted 59 lines · Anshul Dalal
Quoted 57 lines · Denys Dmytriyenko
Quoted 19 lines · Anshul Dalal via lists.yoctoproject.org
Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in
IMAGE_INSTALLwhen ti-falcon is enabled which allows us to deploy the required files to rootfs.Signed-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0meta-ti-bsp/conf/machine/include/ti-falcon.inc line 1
Quoted 1 line
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1
-0@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"Why += cannot be used here?
Quoted 18 lines
meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +2
-0@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR}meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc do_deploy:append:am62pxx() { · line 385
Quoted 10 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +8
-0} +do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon "Shouldn't these be specific to ti-falcon only?
Quoted 8 lines
Quoted 5 lines
These are the only supported platforms at the moment, depending on machine specific overrides allows us to throw an error at the recipe parsing stage instead of having to wait till the
do_installtask fails to copy the non-existent tispl_falcon.bin in case of unsupported platforms.What happens when you build for am62xx-evm and ti-falcon is not enabled?
The ${PN}-falcon package is added to the list of packages but the do_package task is never run for u-boot since it's not in IMAGES_INSTALL.
So, the net effect is no change to the u-boot's working directory during the build process. It's only with ti-falcon that the respective packages-split directory is created with u-boot-ti-staging-falcon sub-directory.
Quoted 3 lines
Quoted 3 lines
As support for more platforms is added, the list can be expanded until all platforms are supported when we can just have a ti-falcon override.
Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Quoted 67 lines · Anshul Dalal
Quoted 66 lines · Denys Dmytriyenko
Quoted 64 lines · Anshul Dalal
Quoted 45 lines · Denys Dmytriyenko
Quoted 19 lines · Anshul Dalal via lists.yoctoproject.org
Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in
IMAGE_INSTALLwhen ti-falcon is enabled which allows us to deploy the required files to rootfs.Signed-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0meta-ti-bsp/conf/machine/include/ti-falcon.inc line 1
Quoted 1 line
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1
-0@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"Why += cannot be used here?
Quoted 20 lines
meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +2
-0@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} }Quoted 12 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc do_deploy:append:am62pxx() { · line 385
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +8
-0+do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon "Shouldn't these be specific to ti-falcon only?
These are the only supported platforms at the moment, depending on machine specific overrides allows us to throw an error at the recipe parsing stage instead of having to wait till the
do_installtask fails to copy the non-existent tispl_falcon.bin in case of unsupported platforms.
Quoted 6 lines
Quoted 2 lines
What happens when you build for am62xx-evm and ti-falcon is not enabled?
The ${PN}-falcon package is added to the list of packages but the
do_packagetask is never run for u-boot since it's not inIMAGES_INSTALL.
All our platforms have u-boot in EXTRA_IMAGEDEPENDS, which means u-boot gets built and packaged all the time. Moreover, it's common to "bitbake u-boot"
Quoted 8 lines
So, the net effect is no change to the u-boot's working directory during the build process. It's only with ti-falcon that the respective packages-split directory is created with u-boot-ti-staging-falcon sub-directory.
Quoted 3 lines
Quoted 3 lines
As support for more platforms is added, the list can be expanded until all platforms are supported when we can just have a ti-falcon override.
Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Quoted 71 lines · Denys Dmytriyenko
Quoted 70 lines · Anshul Dalal
Quoted 68 lines · Denys Dmytriyenko
Quoted 59 lines · Anshul Dalal
Quoted 45 lines · Denys Dmytriyenko
Quoted 19 lines · Anshul Dalal via lists.yoctoproject.org
Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in
IMAGE_INSTALLwhen ti-falcon is enabled which allows us to deploy the required files to rootfs.Signed-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0meta-ti-bsp/conf/machine/include/ti-falcon.inc line 1
Quoted 1 line
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1
-0@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"Why += cannot be used here?
Quoted 20 lines
meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +2
-0@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} }Quoted 12 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc do_deploy:append:am62pxx() { · line 385
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +8
-0+do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon "Shouldn't these be specific to ti-falcon only?
Quoted 5 lines
These are the only supported platforms at the moment, depending on machine specific overrides allows us to throw an error at the recipe parsing stage instead of having to wait till the
do_installtask fails to copy the non-existent tispl_falcon.bin in case of unsupported platforms.What happens when you build for am62xx-evm and ti-falcon is not enabled?
Quoted 7 lines
Quoted 3 lines
The ${PN}-falcon package is added to the list of packages but the
do_packagetask is never run for u-boot since it's not inIMAGES_INSTALL.All our platforms have u-boot in
EXTRA_IMAGEDEPENDS, which means u-boot gets built and packaged all the time. Moreover, it's common to "bitbake u-boot"
Recipes in EXTRA_IMAGEDEPENDS don't provide any packages to rootfs[1], hence why u-boot has no package directory when ti-falcon is not set or even before this patch set.
Therefore having the falcon u-boot package in PACKAGES does not change the build time behaviour until it's added to IMAGES_INSTALL (which is only done when ti-falcon is set).
In my testing, there is no difference between the work directory for u-boot with ti-falcon unset vs the work directory before this patch set[2].
[1]:
https://docs.yoctoproject.org/ref-manual/variables.html#term-EXTRA_IMAGEDEPENDS
[2]:
U-boot's work directories:
# before patch set: build image recipe-sysroot-native temp deploy-source-date-epoch license-destdir source-date-epoch deploy-u-boot-ti-staging pseudo srcipk-staging git recipe-sysroot sysroot-destdir
# without ti-falcon: build image recipe-sysroot-native temp deploy-source-date-epoch license-destdir source-date-epoch deploy-u-boot-ti-staging pseudo srcipk-staging git recipe-sysroot sysroot-destdir
# with ti-falcon: build package recipe-sysroot-native deploy-ipks packages-split source-date-epoch deploy-source-date-epoch pkgdata spdx deploy-u-boot-ti-staging pkgdata-pdata-input srcipk-staging git pkgdata-sysroot sysroot-destdir image pseudo temp license-destdir recipe-sysroot
---
Regards,
Anshul
Quoted 9 lines
Quoted 9 lines
So, the net effect is no change to the u-boot's working directory during the build process. It's only with ti-falcon that the respective packages-split directory is created with u-boot-ti-staging-falcon sub-directory.
Quoted 3 lines
Quoted 3 lines
As support for more platforms is added, the list can be expanded until all platforms are supported when we can just have a ti-falcon override.
Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Quoted 110 lines · Anshul Dalal
Quoted 71 lines · Denys Dmytriyenko
Quoted 70 lines · Anshul Dalal
Quoted 68 lines · Denys Dmytriyenko
Quoted 59 lines · Anshul Dalal
Quoted 45 lines · Denys Dmytriyenko
Quoted 19 lines · Anshul Dalal via lists.yoctoproject.org
Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in
IMAGE_INSTALLwhen ti-falcon is enabled which allows us to deploy the required files to rootfs.Signed-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0meta-ti-bsp/conf/machine/include/ti-falcon.inc line 1
Quoted 1 line
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1
-0@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"Why += cannot be used here?
Quoted 20 lines
meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +2
-0@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} }Quoted 12 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc do_deploy:append:am62pxx() { · line 385
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +8
-0+do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon "Shouldn't these be specific to ti-falcon only?
Quoted 5 lines
These are the only supported platforms at the moment, depending on machine specific overrides allows us to throw an error at the recipe parsing stage instead of having to wait till the
do_installtask fails to copy the non-existent tispl_falcon.bin in case of unsupported platforms.What happens when you build for am62xx-evm and ti-falcon is not enabled?
Quoted 7 lines
Quoted 3 lines
The ${PN}-falcon package is added to the list of packages but the
do_packagetask is never run for u-boot since it's not inIMAGES_INSTALL.All our platforms have u-boot in
EXTRA_IMAGEDEPENDS, which means u-boot gets built and packaged all the time. Moreover, it's common to "bitbake u-boot"Recipes in
EXTRA_IMAGEDEPENDSdon't provide any packages to rootfs[1], hence why u-boot has nopackagedirectory when ti-falcon is not set or even before this patch set.Therefore having the falcon u-boot package in PACKAGES does not change the build time behaviour until it's added to
IMAGES_INSTALL(which is only done when ti-falcon is set).In my testing, there is no difference between the work directory for u-boot with ti-falcon unset vs the work directory before this patch set[2].
[1]:
https://docs.yoctoproject.org/ref-manual/variables.html#term-EXTRA_IMAGEDEPENDS[2]:
U-boot's work directories:# before patch set: build image recipe-sysroot-native temp deploy-source-date-epoch license-destdir source-date-epoch deploy-u-boot-ti-staging pseudo srcipk-staging git recipe-sysroot sysroot-destdir# without ti-falcon: build image recipe-sysroot-native temp deploy-source-date-epoch license-destdir source-date-epoch deploy-u-boot-ti-staging pseudo srcipk-staging git recipe-sysroot sysroot-destdir
Quoted 8 lines
# with ti-falcon: build package recipe-sysroot-native deploy-ipks packages-split source-date-epoch deploy-source-date-epoch pkgdata spdx deploy-u-boot-ti-staging pkgdata-pdata-input srcipk-staging git pkgdata-sysroot sysroot-destdir image pseudo temp license-destdir recipe-sysroot
You should not rely on this behavior expecting that U-boot will be built, but not packaged!
In scarthgap, this may be true:
$ MACHINE=am62xx-evm bitbake tisdk-base-image -g $ grep '\-> "u-boot-ti-staging.do_package' task-depends.dot $
But in walnascar/master, SPDX 3.x functionality for SW Bill of Materials is enabled by default and operates on packages, hence do_package() task will be called for U-boot:
$ MACHINE=am62xx-evm bitbake tisdk-base-image -g $ grep u-boot-ti-staging.do_package task-depends.dot "u-boot-ti-staging.do_create_spdx" -> "u-boot-ti-staging.do_package" "u-boot-ti-staging.do_create_spdx" -> "u-boot-ti-staging.do_packagedata" "u-boot-ti-staging.do_packagedata" -> "u-boot-ti-staging.do_package" $
And indeed, the work directory contains both package and packages-split directories:
$ ls -1 arago-tmp-default/work/am62xx_evm-oe-linux/u-boot-ti-staging/2025.01+git/ build deploy-source-date-epoch deploy-u-boot-ti-staging git image license-destdir package packages-split pkgdata pkgdata-pdata-input pkgdata-sysroot pseudo recipe-sysroot recipe-sysroot-native source-date-epoch sources-unpack spdx sysroot-destdir temp
$ ls -1 arago-tmp-default/work/am62xx_evm-oe-linux/u-boot-ti-staging/2025.01+git/packages-split/ u-boot-ti-staging u-boot-ti-staging-dbg u-boot-ti-staging-dev u-boot-ti-staging-doc u-boot-ti-staging-env u-boot-ti-staging-extlinux u-boot-ti-staging-locale u-boot-ti-staging-src u-boot-ti-staging-staticdev
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
So, the net effect is no change to the u-boot's working directory during the build process. It's only with ti-falcon that the respective packages-split directory is created with u-boot-ti-staging-falcon sub-directory.
Quoted 3 lines
Quoted 3 lines
As support for more platforms is added, the list can be expanded until all platforms are supported when we can just have a ti-falcon override.
Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Quoted 93 lines · Denys Dmytriyenko
Quoted 92 lines · Anshul Dalal
Quoted 71 lines · Denys Dmytriyenko
Quoted 70 lines · Anshul Dalal
Quoted 68 lines · Denys Dmytriyenko
Quoted 59 lines · Anshul Dalal
Quoted 45 lines · Denys Dmytriyenko
Quoted 19 lines · Anshul Dalal via lists.yoctoproject.org
Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in
IMAGE_INSTALLwhen ti-falcon is enabled which allows us to deploy the required files to rootfs.Signed-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0meta-ti-bsp/conf/machine/include/ti-falcon.inc line 1
Quoted 1 line
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1
-0@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"Why += cannot be used here?
Quoted 20 lines
meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +2
-0@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} }Quoted 12 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc do_deploy:append:am62pxx() { · line 385
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +8
-0+do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon "Shouldn't these be specific to ti-falcon only?
Quoted 5 lines
These are the only supported platforms at the moment, depending on machine specific overrides allows us to throw an error at the recipe parsing stage instead of having to wait till the
do_installtask fails to copy the non-existent tispl_falcon.bin in case of unsupported platforms.What happens when you build for am62xx-evm and ti-falcon is not enabled?
Quoted 7 lines
Quoted 3 lines
The ${PN}-falcon package is added to the list of packages but the
do_packagetask is never run for u-boot since it's not inIMAGES_INSTALL.All our platforms have u-boot in
EXTRA_IMAGEDEPENDS, which means u-boot gets built and packaged all the time. Moreover, it's common to "bitbake u-boot"Recipes in
EXTRA_IMAGEDEPENDSdon't provide any packages to rootfs[1], hence why u-boot has nopackagedirectory when ti-falcon is not set or even before this patch set.Therefore having the falcon u-boot package in PACKAGES does not change the build time behaviour until it's added to
IMAGES_INSTALL(which is only done when ti-falcon is set).In my testing, there is no difference between the work directory for u-boot with ti-falcon unset vs the work directory before this patch set[2].
[snip]
Quoted 6 lines
You should not rely on this behavior expecting that U-boot will be built, but not packaged!
In scarthgap, this may be true:
Quoted 8 lines
$ MACHINE=am62xx-evm bitbake tisdk-base-image -g $ grep '\-> "u-boot-ti-staging.do_package' task-depends.dot $But in walnascar/master, SPDX 3.x functionality for SW Bill of Materials is enabled by default and operates on packages, hence
do_package()task will be called for U-boot:
Well in that case, we can use nested overrides using ti-falcon as well as the machine specific config. Like below:
PACKAGES:prepend:ti-append:am62xx-evm = "${PN}-falcon " PACKAGES:prepend:ti-append:am62axx-evm = "${PN}-falcon " PACKAGES:prepend:ti-append:am62pxx-evm = "${PN}-falcon " PACKAGES:prepend:ti-append:am62xx-lp-evm = "${PN}-falcon "
[snip]
Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Quoted 110 lines · Anshul Dalal
Quoted 93 lines · Denys Dmytriyenko
Quoted 92 lines · Anshul Dalal
Quoted 71 lines · Denys Dmytriyenko
Quoted 70 lines · Anshul Dalal
Quoted 68 lines · Denys Dmytriyenko
Quoted 59 lines · Anshul Dalal
Quoted 45 lines · Denys Dmytriyenko
Quoted 19 lines · Anshul Dalal via lists.yoctoproject.org
Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage.
This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in
IMAGE_INSTALLwhen ti-falcon is enabled which allows us to deploy the required files to rootfs.Signed-off-by Anshul Dalal <[email protected]>--- meta-ti-bsp/conf/machine/include/ti-falcon.inc | 1 + meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 11 +++++++++++ 2 files changed, 12 insertions(+)meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0meta-ti-bsp/conf/machine/include/ti-falcon.inc line 1
Quoted 1 line
meta-ti-bsp/conf/machine/include/ti-falcon.inc +1
-0@@ -1,3 +1,4 @@ +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"Why += cannot be used here?
Quoted 20 lines
meta-ti-bsp/conf/machine/include/ti-falcon.inc +0
-0KERNEL_CLASSES:remove = "kernel-fitimage" KERNEL_CLASSES += "kernel-fitimage-legacyhs" UBOOT_DTB_LOADADDRESS = "0x82000000"meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +2
-0@@ -14,6 +14,8 @@ require u-boot-mergeconfig.inc FILESEXTRAPATHS:prepend := "${THISDIR}/u-boot:" +FILES:${PN}-falcon = "boot/tispl_falcon.bin" + SUMMARY = "u-boot bootloader for TI devices" LICENSE = "GPL-2.0-or-later"@@ -373,4 +375,13 @@ do_deploy:append:am62pxx() { install -m 0644 ${S}/tools/logos/ti_logo_414x97_32bpp.bmp.gz ${DEPLOYDIR} }Quoted 12 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc do_deploy:append:am62pxx() { · line 385
Quoted 8 lines
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc +8
-0+do_install:append:ti-falcon() { + install -m 0644 ${B}/tispl_falcon.bin ${D}/boot +} + +PACKAGES:prepend:am62xx-evm = "${PN}-falcon " +PACKAGES:prepend:am62axx-evm = "${PN}-falcon " +PACKAGES:prepend:am62pxx-evm = "${PN}-falcon " +PACKAGES:prepend:am62xx-lp-evm = "${PN}-falcon "Shouldn't these be specific to ti-falcon only?
Quoted 5 lines
These are the only supported platforms at the moment, depending on machine specific overrides allows us to throw an error at the recipe parsing stage instead of having to wait till the
do_installtask fails to copy the non-existent tispl_falcon.bin in case of unsupported platforms.What happens when you build for am62xx-evm and ti-falcon is not enabled?
Quoted 7 lines
Quoted 3 lines
The ${PN}-falcon package is added to the list of packages but the
do_packagetask is never run for u-boot since it's not inIMAGES_INSTALL.All our platforms have u-boot in
EXTRA_IMAGEDEPENDS, which means u-boot gets built and packaged all the time. Moreover, it's common to "bitbake u-boot"Recipes in
EXTRA_IMAGEDEPENDSdon't provide any packages to rootfs[1], hence why u-boot has nopackagedirectory when ti-falcon is not set or even before this patch set.Therefore having the falcon u-boot package in PACKAGES does not change the build time behaviour until it's added to
IMAGES_INSTALL(which is only done when ti-falcon is set).In my testing, there is no difference between the work directory for u-boot with ti-falcon unset vs the work directory before this patch set[2].
[snip]
Quoted 6 lines
You should not rely on this behavior expecting that U-boot will be built, but not packaged!
In scarthgap, this may be true:
Quoted 8 lines
$ MACHINE=am62xx-evm bitbake tisdk-base-image -g $ grep '\-> "u-boot-ti-staging.do_package' task-depends.dot $But in walnascar/master, SPDX 3.x functionality for SW Bill of Materials is enabled by default and operates on packages, hence
do_package()task will be called for U-boot:
Quoted 7 lines
Well in that case, we can use nested overrides using ti-falcon as well as the machine specific config. Like below:
PACKAGES:prepend:ti-append:am62xx-evm = "${PN}-falcon " PACKAGES:prepend:ti-append:am62axx-evm = "${PN}-falcon " PACKAGES:prepend:ti-append:am62pxx-evm = "${PN}-falcon " PACKAGES:prepend:ti-append:am62xx-lp-evm = "${PN}-falcon "
First of all, there's a typo there in the overrides ^^^
Second, consider making it more obvious and deterministic by splitting overrides:
FALCON_PKG = ""
FALCON_PKG:ti-falcon = "${PN}-falcon"
PACKAGES:prepend:am62xx-evm = "${FALCON_PKG} "
...