From: Denys Dmytriyenko <denis@denix.org>
To: Aparna M <a-m1@ti.com>
Cc: meta-ti@lists.yoctoproject.org, nm@ti.com, praneeth@ti.com,
reatmon@ti.com, devarsht@ti.com, s-adivi@ti.com
Subject: Re: [meta-ti][dunfell][PATCH] ti-tros-firmware: Add DM firmware binary to deploy directory for am62xx-evm
Date: Fri, 13 May 2022 17:53:53 -0400 [thread overview]
Message-ID: <20220513215353.GF9834@denix.org> (raw)
In-Reply-To: <20220513073848.13539-1-a-m1@ti.com>
On Fri, May 13, 2022 at 01:08:48PM +0530, Aparna M wrote:
> The DM firmware binary is required for building uboot binaries for
> am62xx-evm using toplevel makefile in SDK. Add this file to deploy
> directory so it can be included in prebuilt-images directory of SDK
> for am62xx-evm.
>
> Signed-off-by: Aparna M <a-m1@ti.com>
> ---
>
> I have had to include a dummy do_deplo without which yocto build fails
> with a "Task do_deploy is empty" error. Any suggestions as to why this
> could be happening?
You could have an empty do_deploy with a single colon symbol (NOP) in it:
https://git.openembedded.org/openembedded-core/tree/meta/recipes-support/user-creation/xuser-account_0.1.bb?h=dunfell
> recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
> index 56a74899..0f2ba9af 100644
> --- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
> +++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
> @@ -169,6 +169,16 @@ do_install_am62xx() {
> install -m 0644 ${RTOS_DM_FW_DIR}/ipc_echo_testb_mcu1_0_release_strip.xer5f ${LEGACY_DM_FW_DIR}
> }
>
> +
> +do_deploy() {
> + install -d ${DEPLOYDIR}
> +}
> +
> +do_deploy_am62xx() {
> + install -d ${DEPLOYDIR}
> + install -m 0644 ${RTOS_DM_FW_DIR}/ipc_echo_testb_mcu1_0_release_strip.xer5f ${DEPLOYDIR}
> +}
> +
> # Set up names for the firmwares
> ALTERNATIVE_${PN}_am65xx = "\
> am65x-mcu-r5f0_0-fw \
> @@ -357,3 +367,5 @@ INSANE_SKIP_${PN} += "arch"
> # we don't want to configure and build the source code
> do_compile[noexec] = "1"
> do_configure[noexec] = "1"
> +
> +addtask deploy after do_install
> --
> 2.17.1
>
prev parent reply other threads:[~2022-05-13 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 7:38 [meta-ti][dunfell][PATCH] ti-tros-firmware: Add DM firmware binary to deploy directory for am62xx-evm Aparna M
2022-05-13 21:53 ` Denys Dmytriyenko [this message]
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=20220513215353.GF9834@denix.org \
--to=denis@denix.org \
--cc=a-m1@ti.com \
--cc=devarsht@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=s-adivi@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.