From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: Ryan Eatmon <reatmon@ti.com>, meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master/kirkstone][PATCH v2 03/15] optee-os: Use new ti-secdev class to sign the images
Date: Wed, 22 Feb 2023 14:38:10 -0500 [thread overview]
Message-ID: <20230222193810.GU22689@denix.org> (raw)
In-Reply-To: <20230215193355.9676-4-afd@ti.com>
On Wed, Feb 15, 2023 at 01:33:43PM -0600, Andrew Davis via lists.yoctoproject.org wrote:
> Use the new ti-k3-secdev package to pull in the signing tools if they are
> not provided by the environment. This allows us to use these tools
> unconditionally. Remove the checks for the script and do the signing
> for all K3 machines. The signature is automatically stripped from
> the binaries on non-HS devices at boot time as needed so this change
> is harmless for GP devices.
>
> Signed-off-by: Andrew Davis <afd@ti.com>
Tested-by: Denys Dmytriyenko <denys@konsulko.com>
> ---
> .../optee/optee-os_3.16%.bbappend | 43 +++----------------
> 1 file changed, 7 insertions(+), 36 deletions(-)
>
> diff --git a/meta-ti-bsp/recipes-security/optee/optee-os_3.16%.bbappend b/meta-ti-bsp/recipes-security/optee/optee-os_3.16%.bbappend
> index 6913851b..1e0072ef 100644
> --- a/meta-ti-bsp/recipes-security/optee/optee-os_3.16%.bbappend
> +++ b/meta-ti-bsp/recipes-security/optee/optee-os_3.16%.bbappend
> @@ -1,14 +1,13 @@
> PV:ti-soc = "3.19.0+git${SRCPV}"
> SRCREV:ti-soc = "afacf356f9593a7f83cae9f96026824ec242ff52"
>
> +# Use TI SECDEV for signing
> +inherit ti-secdev
> +
> EXTRA_OEMAKE:append:k3 = "${@ ' CFG_CONSOLE_UART='+ d.getVar('OPTEE_K3_USART') if d.getVar('OPTEE_K3_USART') else ''}"
>
> EXTRA_OEMAKE:append:am62xx = " CFG_WITH_SOFTWARE_PRNG=y CFG_TEE_CORE_LOG_LEVEL=1"
>
> -do_compile:prepend:ti-soc() {
> - export TI_SECURE_DEV_PKG=${TI_SECURE_DEV_PKG}
> -}
> -
> do_compile:append:k3() {
> ( cd ${B}/core/; \
> cp tee-pager_v2.bin ${B}/bl32.bin; \
> @@ -35,20 +34,6 @@ optee_sign_legacyhs() {
> fi
> }
>
> -# Signing procedure for K3 HS devices
> -optee_sign_k3hs() {
> - ( cd ${B}/core/; \
> - if [ -f ${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh ]; then \
> - ${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh tee-pager_v2.bin tee-pager.bin.signed; \
> - else \
> - echo "Warning: TI_SECURE_DEV_PKG not set, OP-TEE not signed."; \
> - cp tee-pager_v2.bin tee-pager.bin.signed; \
> - fi; \
> - mv tee-pager.bin.signed ${B}/bl32.bin; \
> - cp tee.elf ${B}/bl32.elf; \
> - )
> -}
> -
> do_compile:append:ti43x() {
> optee_sign_legacyhs
> }
> @@ -57,24 +42,10 @@ do_compile:append:dra7xx() {
> optee_sign_legacyhs
> }
>
> -do_compile:append:am65xx-hs-evm() {
> - optee_sign_k3hs
> -}
> -
> -do_compile:append:am64xx-evm() {
> - optee_sign_k3hs
> -}
> -
> -do_compile:append:j721e-hs-evm() {
> - optee_sign_k3hs
> -}
> -
> -do_compile:append:j7200-hs-evm() {
> - optee_sign_k3hs
> -}
> -
> -do_compile:append:j721s2-hs-evm() {
> - optee_sign_k3hs
> +# Signing procedure for K3 devices
> +do_compile:append:k3() {
> + ${TI_SECURE_DEV_PKG}/scripts/secure-binary-image.sh ${B}/core/tee-pager_v2.bin ${B}/bl32.bin
> + cp ${B}/core/tee.elf ${B}/bl32.elf
> }
>
> do_install:append:ti-soc() {
> --
> 2.39.1
next prev parent reply other threads:[~2023-02-22 19:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 19:33 [meta-ti][master/kirkstone][PATCH v2 00/15] ti-rtos-firmware and secdev Andrew Davis
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 01/15] meta-ti-bsp: Add helper class for TI Security Development Tools Andrew Davis
2023-02-22 19:36 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 02/15] trusted-firmware-a: Use new ti-secdev class to sign the images Andrew Davis
2023-02-22 19:37 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 03/15] optee-os: " Andrew Davis
2023-02-22 19:38 ` Denys Dmytriyenko [this message]
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 04/15] u-boot-ti: " Andrew Davis
2023-02-22 19:38 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 05/15] ti-rtos-firmware: " Andrew Davis
2023-02-22 19:39 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 06/15] ti-sci-fw: " Andrew Davis
2023-02-22 19:39 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 07/15] conf: machine: k3: Remove unneeded TI_SECURE_DEV_PKG_K3 assignments Andrew Davis
2023-02-22 19:40 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 08/15] ti-k3-secdev: Remove inclusion of ti-paths.inc Andrew Davis
2023-02-22 19:41 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 09/15] ti-rtos-firmware: Remove unneeded per-machine TARGET defines Andrew Davis
2023-02-22 19:41 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 10/15] ti-rtos-firmware: Fix name for AM64x and AM62x firmware Andrew Davis
2023-02-22 19:42 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 11/15] ti-rtos-firmware: Do not break the source directory by renaming files Andrew Davis
2023-02-22 19:42 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 12/15] ti-rtos-firmware: Use defines to set firmware names Andrew Davis
2023-02-22 19:43 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 13/15] ti-rtos-firmware: Use a table instead of a list of copy commands Andrew Davis
2023-02-22 19:43 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 14/15] ti-rtos-firmware: Fix use of base_libdir with nonarch_base_libdir Andrew Davis
2023-02-22 19:44 ` Denys Dmytriyenko
2023-02-15 19:33 ` [meta-ti][master/kirkstone][PATCH v2 15/15] ti-rtos-firmware: Deploy secure firmware unconditionally Andrew Davis
2023-02-22 19:44 ` Denys Dmytriyenko
2023-02-17 7:09 ` [meta-ti][master/kirkstone][PATCH v2 00/15] ti-rtos-firmware and secdev Denys Dmytriyenko
2023-02-18 4:09 ` Ryan Eatmon
2023-02-21 20:51 ` Denys Dmytriyenko
2023-02-21 21:12 ` 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=20230222193810.GU22689@denix.org \
--to=denis@denix.org \
--cc=afd@ti.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.