From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: Denys Dmytriyenko <denys@konsulko.com>,
Ryan Eatmon <reatmon@ti.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master/kirkstone][PATCH 1/8] ti-rtos-firmware: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 not defined
Date: Fri, 10 Feb 2023 16:02:03 -0500 [thread overview]
Message-ID: <20230210210203.GC22689@denix.org> (raw)
In-Reply-To: <20230207234239.30720-1-afd@ti.com>
On Tue, Feb 07, 2023 at 05:42:32PM -0600, Andrew Davis via lists.yoctoproject.org wrote:
> Use ti-k3-secdev native package to provide secure-binary-image.sh script
> when it is not passed on as an environment variable. This fixes and issue
Fixes *an* issue
> with AM64xx which is always HS but should not require TI_SECURE_DEV_PKG
> when building for HS-FS platforms.
And GP?
>
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
> meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
> index 9a6da088..6c59b8ab 100644
> --- a/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
> +++ b/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
> @@ -31,9 +31,11 @@ CLEANBROKEN = "1"
> PR = "${INC_PR}.0"
>
> # Secure Build
> +include recipes-ti/includes/ti-paths.inc
Set TI_K3_SECDEV_INSTALL_DIR here instead of including ti-paths.inc?
> DEPENDS += "openssl-native"
> -
> -TI_SECURE_DEV_PKG ?= ""
> +DEPENDS:append = "${@ '' if d.getVar('TI_SECURE_DEV_PKG_K3') else ' ti-k3-secdev-native' }"
Should probably use DEPENDS += here instead of a generic :append override.
As :append and :remove are almost impossible to fight/override downstream,
it is recommended to use += whenever possible, like in this case...
> +TI_SECURE_DEV_PKG = "${@ d.getVar('TI_SECURE_DEV_PKG_K3') or d.getVar('TI_K3_SECDEV_INSTALL_DIR') }"
> +export TI_SECURE_DEV_PKG
>
> RTOS_ETH_FW_DIR = "${S}/ti-eth/${PLAT_SFX}"
> RTOS_DM_FW_DIR = "${S}/ti-dm/${PLAT_SFX}"
> @@ -49,7 +51,6 @@ DM_FIRMWARE = "ipc_echo_testb_mcu1_0_release_strip.xer5f"
>
> # J721e HS support
> do_install:prepend:j721e-hs-evm() {
> - export TI_SECURE_DEV_PKG=${TI_SECURE_DEV_PKG}
> ( cd ${RTOS_DM_FW_DIR}; \
> mv ${DM_FIRMWARE} ${DM_FIRMWARE}.unsigned; \
> ${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh ${DM_FIRMWARE}.unsigned ${DM_FIRMWARE}; \
> @@ -80,7 +81,6 @@ do_install:prepend:j721e-hs-evm() {
>
> # J7200 HS support
> do_install:prepend:j7200-hs-evm() {
> - export TI_SECURE_DEV_PKG=${TI_SECURE_DEV_PKG}
> ( cd ${RTOS_DM_FW_DIR}; \
> mv ${DM_FIRMWARE} ${DM_FIRMWARE}.unsigned; \
> ${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh ${DM_FIRMWARE}.unsigned ${DM_FIRMWARE}; \
> @@ -101,7 +101,6 @@ do_install:prepend:j7200-hs-evm() {
>
> # J721s2 HS support
> do_install:prepend:j721s2-hs-evm() {
> - export TI_SECURE_DEV_PKG=${TI_SECURE_DEV_PKG}
> ( cd ${RTOS_DM_FW_DIR}; \
> mv ${DM_FIRMWARE} ${DM_FIRMWARE}.unsigned; \
> ${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh ${DM_FIRMWARE}.unsigned ${DM_FIRMWARE}; \
> --
> 2.39.1
next prev parent reply other threads:[~2023-02-10 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 23:42 [meta-ti][master/kirkstone][PATCH 1/8] ti-rtos-firmware: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 not defined Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 2/8] ti-rtos-firmware: Remove unneeded per-machine TARGET defines Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 3/8] ti-rtos-firmware: Fix name for AM64x and AM62x firmware Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 4/8] ti-rtos-firmware: Do not break the source directory by renaming files Andrew Davis
2023-02-10 21:07 ` Denys Dmytriyenko
2023-02-10 21:14 ` Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 5/8] ti-rtos-firmware: Use defines to set firmware names Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 6/8] ti-rtos-firmware: Use a table instead of a list of copy commands Andrew Davis
2023-02-09 13:29 ` Ryan Eatmon
2023-02-09 18:11 ` Andrew Davis
2023-02-10 1:46 ` Ryan Eatmon
2023-02-10 21:23 ` Denys Dmytriyenko
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 7/8] ti-rtos-firmware: Fix use of base_libdir with nonarch_base_libdir Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 8/8] ti-rtos-firmware: Deploy secure firmware unconditionally Andrew Davis
2023-02-10 21:02 ` Denys Dmytriyenko [this message]
2023-02-10 21:13 ` [meta-ti][master/kirkstone][PATCH 1/8] ti-rtos-firmware: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 not defined Andrew Davis
2023-02-10 21:50 ` Denys Dmytriyenko
2023-02-14 9:45 ` Jose Quaresma
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=20230210210203.GC22689@denix.org \
--to=denis@denix.org \
--cc=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.