From: Stefano Babic <sbabic@denx.de>
To: Lukasz Majewski <lukma@denx.de>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>,
Marek Vasut <marex@denx.de>
Cc: Tom Rini <trini@konsulko.com>, Stefan Agner <stefan.agner@toradex.com>
Subject: Re: [PATCH] u-boot: Add {gen|deploy}_default_envs tasks to generate environment images
Date: Thu, 3 May 2018 18:24:32 +0200 [thread overview]
Message-ID: <05497147-e45a-1b11-e6d0-387de8fdee26@denx.de> (raw)
In-Reply-To: <20180427145139.30732-1-lukma@denx.de>
Hi Lukasz,
On 27/04/2018 16:51, Lukasz Majewski wrote:
> This commit provides the ability to generate u-boot environment(s) as
> images, which afterwards can be used to produce image (with wic) for
> flashing (eMMC or SPI-NOR).
>
> This change removes the need to run "env default" during production phase,
> as proper environment (including redundant one) is already stored on
> persistent memory (the CRC is also correct).
>
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
>
> ---
> This patch depends on "u-boot: Upgrade to 2018.03 release"
> https://patchwork.openembedded.org/patch/149998/
> ---
> meta/recipes-bsp/u-boot/u-boot.inc | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u-boot/u-boot.inc
> index c2bcf99840..2796e503cf 100644
> --- a/meta/recipes-bsp/u-boot/u-boot.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot.inc
> @@ -305,3 +305,38 @@ do_deploy () {
> }
>
> addtask deploy before do_build after do_compile
> +
> +# Create new rules to extract default envs
> +UBOOT_ENVS_DEFAULT ?= "uboot-envs-default"
> +DEFAULT_ENVS ?= "u-boot-env-default.txt"
> +DEFAULT_ENVS_SIZE ?= "65536"
> +
> +# Generate default environment
> +do_gen_default_envs[doc] = "Generate image with default U-Boot environment(s)"
> +do_gen_default_envs () {
> + ${B}/source/scripts/get_default_envs.sh ${B} > ${B}/${DEFAULT_ENVS}
> +
> + # Generate env image
> + ${B}/tools/mkenvimage -s ${DEFAULT_ENVS_SIZE} -o ${B}/${UBOOT_ENVS_DEFAULT} ${B}/${DEFAULT_ENVS}
> +
> + # Generate redundant env image
> + ${B}/tools/mkenvimage -r -s ${DEFAULT_ENVS_SIZE} -o ${B}/${UBOOT_ENVS_DEFAULT}_r ${B}/${DEFAULT_ENVS}
> +
> + rm ${B}/${DEFAULT_ENVS}
> +}
> +
Why do we need a separate task ? Is it not part of do_compile ?
> +addtask gen_default_envs before do_deploy_default_envs after do_compile
> +
> +# Deploy default environment
> +do_deploy_default_envs[doc] = "Copy images with default U-Boot environment to deployment directory"
> +do_deploy_default_envs () {
> + install -d ${DEPLOYDIR}
> +
> + install ${B}/${UBOOT_ENVS_DEFAULT} ${DEPLOYDIR}/${UBOOT_ENVS_DEFAULT}
> + install ${B}/${UBOOT_ENVS_DEFAULT}_r ${DEPLOYDIR}/${UBOOT_ENVS_DEFAULT}_r
> +
> + rm ${B}/${UBOOT_ENVS_DEFAULT}
> + rm ${B}/${UBOOT_ENVS_DEFAULT}_r
> +}
> +
> +addtask deploy_default_envs before do_deploy after do_gen_default_envs
>
I would like to see that the default environment is installed and
delivered as (additional) package. I could then add it to my rootfs and
use it to set up the environment in user space in case a CRC error is
reported by the env tools.
Regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next prev parent reply other threads:[~2018-05-03 16:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 14:51 [PATCH] u-boot: Add {gen|deploy}_default_envs tasks to generate environment images Lukasz Majewski
2018-04-27 15:07 ` Marek Vasut
2018-04-27 16:15 ` Lukasz Majewski
2018-04-27 17:37 ` Marek Vasut
2018-04-29 13:53 ` Lukasz Majewski
2018-04-29 14:07 ` Marek Vasut
2018-04-30 14:03 ` Otavio Salvador
2018-04-30 17:32 ` Marek Vasut
2018-05-03 16:28 ` Stefano Babic
2018-05-03 16:36 ` Marek Vasut
2018-05-03 16:50 ` Stefano Babic
2018-05-03 16:59 ` Marek Vasut
2018-05-03 18:15 ` Lukasz Majewski
2018-05-03 19:02 ` Marek Vasut
2018-05-09 11:45 ` Lukasz Majewski
2018-05-09 11:57 ` Marek Vasut
2018-05-03 20:58 ` Stefano Babic
2018-05-03 23:04 ` Marek Vasut
2018-04-30 6:50 ` Martin Hundebøll
2018-04-30 8:18 ` Lukasz Majewski
2018-04-30 13:23 ` Martin Jansa
2018-04-30 13:26 ` Martin Jansa
2018-04-30 14:22 ` Lukasz Majewski
2018-05-03 16:24 ` Stefano Babic [this message]
2018-05-03 18:17 ` Lukasz Majewski
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=05497147-e45a-1b11-e6d0-387de8fdee26@denx.de \
--to=sbabic@denx.de \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefan.agner@toradex.com \
--cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox