On 05/04/2018 20:46, Bryan O'Donoghue wrote:
> Working with HAB on the i.MX7 we've encountered a case where a board that
> successfully authenticates u-boot when booting Linux via OPTEE subsequently
> fails to properly bring up the RTC.
>
> The RTC registers live in the low-power block of the
On Fri, Apr 6, 2018 at 6:41 AM, Bryan O'Donoghue
wrote:
> No, I don't think so.
>
> HAB can hand off to u-boot with the bit unset and you don't have to have
> CONFIG_SECURE_BOOT set in u-boot to install or chain-load a TEE.
>
> There's no technical requirement that I
On 05/04/18 20:29, Fabio Estevam wrote:
Hi Bryan,
On Thu, Apr 5, 2018 at 3:46 PM, Bryan O'Donoghue
wrote:
--- a/arch/arm/mach-imx/mx7/soc.c
+++ b/arch/arm/mach-imx/mx7/soc.c
@@ -180,6 +180,8 @@ int arch_cpu_init(void)
isolate_resource();
#endif
+
Hi Bryan,
On Thu, Apr 5, 2018 at 3:46 PM, Bryan O'Donoghue
wrote:
> --- a/arch/arm/mach-imx/mx7/soc.c
> +++ b/arch/arm/mach-imx/mx7/soc.c
> @@ -180,6 +180,8 @@ int arch_cpu_init(void)
> isolate_resource();
> #endif
>
> + init_snvs();
Shouldn't this be
+ Stefano
On 05/04/18 19:46, Bryan O'Donoghue wrote:
Working with HAB on the i.MX7 we've encountered a case where a board that
successfully authenticates u-boot when booting Linux via OPTEE subsequently
fails to properly bring up the RTC.
The RTC registers live in the low-power block of the
Working with HAB on the i.MX7 we've encountered a case where a board that
successfully authenticates u-boot when booting Linux via OPTEE subsequently
fails to properly bring up the RTC.
The RTC registers live in the low-power block of the Secure Non-Volatile
Storage (SNVS) block.
The root cause
6 matches
Mail list logo