From: Andrew Davis <afd@ti.com>
To: Denys Dmytriyenko <denys@konsulko.com>,
Ryan Eatmon <reatmon@ti.com>, <meta-ti@lists.yoctoproject.org>
Cc: Andrew Davis <afd@ti.com>
Subject: [meta-ti][dunfell][RFC 4/6] ti-sci-fw: Use SYSFW_TIBOOT3 to point to the SYSFW image
Date: Fri, 1 Jul 2022 17:02:26 -0500 [thread overview]
Message-ID: <20220701220228.5449-5-afd@ti.com> (raw)
In-Reply-To: <20220701220228.5449-1-afd@ti.com>
Currently we reuse UBOOT_* names which usually are the same we
want to give to the name of the SYSFW binary. This isn't always
correct, we should use a SYSFW specific variable in case the
UBOOT names are changed.
Signed-off-by: Andrew Davis <afd@ti.com>
---
recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
index 1bb4fd3e..1b2ea184 100644
--- a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
+++ b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
@@ -37,6 +37,8 @@ SYSFW_PREFIX_am62xx-evm-k3r5 = "fs"
SYSFW_TISCI = "${S}/ti-sysfw/ti-${SYSFW_PREFIX}-firmware-${SYSFW_SOC}-*.bin"
+SYSFW_TIBOOT3 = "tiboot3-${SYSFW_SOC}-${SYSFW_SUFFIX}-${SYSFW_CONFIG}.bin"
+
SYSFW_BINARY = "sysfw-${SYSFW_SOC}-${SYSFW_CONFIG}.itb"
SYSFW_VBINARY = "sysfw-${PV}-${SYSFW_SOC}-${SYSFW_CONFIG}.itb"
SYSFW_IMAGE = "sysfw-${SYSFW_SOC}-${SYSFW_CONFIG}.itb"
@@ -78,10 +80,9 @@ do_install() {
fi
fi
- if [ -f "${WORKDIR}/imggen/${UBOOT_BINARY}" ]; then
- install -m 644 ${WORKDIR}/imggen/${UBOOT_BINARY} ${D}/boot/${UBOOT_IMAGE}
- ln -sf ${UBOOT_IMAGE} ${D}/boot/${UBOOT_SYMLINK}
- ln -sf ${UBOOT_IMAGE} ${D}/boot/${UBOOT_BINARY}
+ if [ -f "${WORKDIR}/imggen/${SYSFW_TIBOOT3}" ]; then
+ install -m 644 ${WORKDIR}/imggen/${SYSFW_TIBOOT3} ${D}/boot/${SYSFW_TIBOOT3}
+ ln -sf ${SYSFW_TIBOOT3} ${D}/boot/tiboot3.bin
fi
}
@@ -100,10 +101,9 @@ do_deploy () {
fi
fi
- if [ -f "${WORKDIR}/imggen/${UBOOT_BINARY}" ]; then
- install -m 644 ${WORKDIR}/imggen/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE}
- ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_SYMLINK}
- ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_BINARY}
+ if [ -f "${WORKDIR}/imggen/${SYSFW_TIBOOT3}" ]; then
+ install -m 644 ${WORKDIR}/imggen/${SYSFW_TIBOOT3} ${DEPLOYDIR}/${SYSFW_TIBOOT3}
+ ln -sf ${SYSFW_TIBOOT3} ${DEPLOYDIR}/tiboot3.bin
fi
install -m 644 ${SYSFW_TISCI} ${DEPLOYDIR}/
--
2.36.1
next prev parent reply other threads:[~2022-07-01 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 22:02 [meta-ti][dunfell][RFC 0/6] HS SDK on GP EVM support Andrew Davis
2022-07-01 22:02 ` [meta-ti][dunfell][RFC 1/6] conf: machine: Make multi-certificate image the default Andrew Davis
2022-07-01 22:02 ` [meta-ti][dunfell][RFC 2/6] ti-sci-fw: Use new SOC_TYPE and SYSFW_DIR to simplify recipe Andrew Davis
2022-07-02 22:30 ` Denys Dmytriyenko
2022-07-05 15:04 ` Andrew Davis
2022-07-01 22:02 ` [meta-ti][dunfell][RFC 3/6] ti-sci-fw: Deploy all SYSFW firmware types Andrew Davis
2022-07-01 22:02 ` Andrew Davis [this message]
2022-07-01 22:02 ` [meta-ti][dunfell][RFC 5/6] machine: am64xx-k3r5: The output of u-boot is not used Andrew Davis
2022-07-01 22:02 ` [meta-ti][dunfell][RFC 6/6] ti-sci-fw: Deploy GP version of tiboot3.bin with HS SDK Andrew Davis
2022-07-02 22:43 ` [meta-ti][dunfell][RFC 0/6] HS SDK on GP EVM support Denys Dmytriyenko
2022-07-05 15:28 ` Andrew Davis
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=20220701220228.5449-5-afd@ti.com \
--to=afd@ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@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.