From: Calvin Johnson <calvin.johnson@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] armv8/ls1043a: Add the OCRAM initialization
Date: Thu, 27 Oct 2016 09:47:03 +0000 [thread overview]
Message-ID: <AMSPR04MB407D669CE991B3D90C4924A93AA0@AMSPR04MB407.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM4PR0401MB17329A6E993C58BD922449559AAB0@AM4PR0401MB1732.eurprd04.prod.outlook.com>
Hi York,
>-----Original Message-----
>From: york sun
>Sent: Wednesday, October 26, 2016 10:09 PM
>To: Calvin Johnson <calvin.johnson@nxp.com>; Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>; Pratiyush
>Srivastava <pratiyush.srivastava@nxp.com>; u-boot at lists.denx.de; Mingkai Hu <mingkai.hu@nxp.com>
>Cc: Hou Zhiqiang <Zhiqiang.Hou@freescale.com>
>Subject: Re: [PATCH] armv8/ls1043a: Add the OCRAM initialization
>
>On 10/24/2016 09:30 PM, Calvin Johnson wrote:
>
>>>>> I wonder why we don't see ECC errors before this patch. We have
>>>>> LS1043A boots on NAND, SD.
>>>>>
>>>>
>>>> OCRAM has a requirement of initializing before first time "read".
>>>> If user reads OCRAM before **initializing**; ECC error will come. (u-boot is not handling this error for now).
>>>>
>>>> I can only guess the reason of not seeing this error as OCRAM never read before any write.
>>>> Even in case of Stack, data is first written and then read.
>>>>
>>>
>>> Is there a case you want to read from OCRAM before writing anything to it? Why don't we need to do so for SPL or
>LSCH3?
>>
>> This issue will be seen ONLY in secure boot. It was reproduced on LS1043A also.
>>
>
>How about LSCH3? We have LS2080A secure boot.
I don't know about LS2080A. Prabhakar or Ruchika(copied) may be able to comment on this.
Regards
Calvin
next prev parent reply other threads:[~2016-10-27 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 12:15 [U-Boot] [PATCH] armv8/ls1043a: Add the OCRAM initialization Pratiyush Srivastava
2016-10-12 16:37 ` york sun
2016-10-17 3:35 ` Prabhakar Kushwaha
2016-10-21 20:08 ` york sun
2016-10-23 13:59 ` Prabhakar Kushwaha
2016-10-24 16:15 ` york sun
2016-10-25 1:43 ` Mingkai Hu
2016-10-25 4:30 ` Calvin Johnson
2016-10-26 16:39 ` york sun
2016-10-27 9:47 ` Calvin Johnson [this message]
2016-11-07 18:36 ` york sun
[not found] ` <1ff50edd-3948-c861-6ac9-9a0618ea3584@nxp.com>
2016-11-14 17:32 ` york sun
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=AMSPR04MB407D669CE991B3D90C4924A93AA0@AMSPR04MB407.eurprd04.prod.outlook.com \
--to=calvin.johnson@nxp.com \
--cc=u-boot@lists.denx.de \
/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.