From: Denys Dmytriyenko <denis@denix.org>
To: anshuld@ti.com
Cc: meta-ti@lists.yoctoproject.org, vigneshr@ti.com
Subject: Re: [meta-ti] [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs
Date: Tue, 15 Apr 2025 20:11:39 -0400 [thread overview]
Message-ID: <20250416001139.GS13634@denix.org> (raw)
In-Reply-To: <20250415093645.435281-3-anshuld@ti.com>
On Tue, Apr 15, 2025 at 03:06:44PM +0530, Anshul Dalal via lists.yoctoproject.org wrote:
> 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_INSTALL when
> ti-falcon is enabled which allows us to deploy the required files to
> rootfs.
>
> Signed-off-by: Anshul Dalal <anshuld@ti.com>
> ---
> 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(+)
>
> diff --git a/meta-ti-bsp/conf/machine/include/ti-falcon.inc b/meta-ti-bsp/conf/machine/include/ti-falcon.inc
> index b571c04d..9f93c683 100644
> --- a/meta-ti-bsp/conf/machine/include/ti-falcon.inc
> +++ b/meta-ti-bsp/conf/machine/include/ti-falcon.inc
> @@ -1,3 +1,4 @@
> +IMAGE_INSTALL:append = " u-boot-ti-staging-falcon"
Why += cannot be used here?
> KERNEL_CLASSES:remove = "kernel-fitimage"
> KERNEL_CLASSES += "kernel-fitimage-legacyhs"
> UBOOT_DTB_LOADADDRESS = "0x82000000"
> diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> index 41d4abdd..76803ae3 100644
> --- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> +++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> @@ -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 "
Shouldn't these be specific to ti-falcon only?
> +
> TOOLCHAIN = "gcc"
next prev parent reply other threads:[~2025-04-16 0:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 9:36 [master/scarthgap][PATCH v1 1/3] am62: apply u-boot config fragment on ti-falcon Anshul Dalal
2025-04-15 9:36 ` [master/scarthgap][PATCH v1 2/3] bsp: conf: machine: add ti-falcon.inc Anshul Dalal
2025-04-16 0:13 ` [meta-ti] " Denys Dmytriyenko
2025-04-16 3:01 ` Anshul Dalal
2025-04-15 9:36 ` [master/scarthgap][PATCH v1 3/3] bsp: u-boot: deploy tispl_falcon.bin to rootfs Anshul Dalal
2025-04-16 0:11 ` Denys Dmytriyenko [this message]
2025-04-16 2:59 ` [meta-ti] " Anshul Dalal
2025-04-16 14:33 ` Denys Dmytriyenko
2025-04-17 9:48 ` Anshul Dalal
2025-04-17 18:37 ` Denys Dmytriyenko
2025-04-21 9:01 ` Anshul Dalal
2025-04-22 19:53 ` Denys Dmytriyenko
2025-04-23 8:12 ` Anshul Dalal
2025-04-23 16:17 ` Denys Dmytriyenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250416001139.GS13634@denix.org \
--to=denis@denix.org \
--cc=anshuld@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.