From mboxrd@z Thu Jan  1 00:00:00 1970
From: York Sun <yorksun@freescale.com>
Date: Tue, 10 Mar 2015 09:15:19 -0700
Subject: [U-Boot] [PATCH] Add bootscript support to esbc_validate.
In-Reply-To: <1425976730-14526-1-git-send-email-gaurav.rana@freescale.com>
References: <1425976730-14526-1-git-send-email-gaurav.rana@freescale.com>
Message-ID: <54FF1897.3030602@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de



On 03/10/2015 01:38 AM, Gaurav Rana wrote:
> 1. Default environment will be used for secure boot flow
>  which can't be edited or saved.
> 2. Command for secure boot is predefined in the default
>  environment which will run on autoboot (and autoboot is
>  the only option allowed in case of secure boot) and it
>  looks like this:
>  #define CONFIG_SECBOOT \
>  "setenv bs_hdraddr 0xe8e00000;"                 \
>  "esbc_validate $bs_hdraddr;"                    \
>  "source $img_addr;"                             \
>  "esbc_halt;"
>  #endif
> 3. Boot Script can contain esbc_validate commands and bootm command.
>  Uboot source command used in default secure boot command will
>  run the bootscript.
> 4. Command esbc_halt added to ensure either bootm executes
>  after validation of images or core should just spin.
>
What's the purpose of "esbc_halt"? Once it enters the spin, how to get it out?

York