public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx53loco: Fix boot hang during reboot stress test
Date: Mon, 09 Feb 2015 18:52:15 +0100	[thread overview]
Message-ID: <54D8F3CF.4020102@denx.de> (raw)
In-Reply-To: <1423474173-3749-1-git-send-email-festevam@gmail.com>

Hi Fabio,

On 09/02/2015 10:29, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
> 
> Currently by running the following test:
> 
> => setenv bootcmd reset
> => save
> => reset
> 
> , we observe a hang after approximately 20-30 minutes of stress reboot test.
> 
> Investigation of this issue revealed that when a single DDR chip select is used,
> the hang does not happen. It only happens when the two chip selects are active.
> 
> MX53 reference manual states at "28.6.2 Memory ZQ calibration sequence":
> 
> "The controller must keep the memory lines quiet (except for CK) for the ZQ
> calibration time as defined in the Jedec (512 cycles for ZQCL after reset, 256
> for other ZQCL and 64 for ZQCS)."
> 
> According to the SDE_0 and SDE_1 bit descriptions from register ESDCTL_ESDCTL:
> 
> "Writing 1 to SDE0 or SDE1 will initiate power up delays as JEDEC defines.
> Power up delays are a function of the configured memory type (DDR2/DDR3/LPDDR2)"
> 
> So make sure to activate one chip select at time (CS0 first and then CS1 later),
> so that the required JEDEC delay is respected for each chip select.
> 
> With this change applied the board has gone through three days of reboot stress
> test without any hang.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  board/freescale/mx53loco/imximage.cfg | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/board/freescale/mx53loco/imximage.cfg b/board/freescale/mx53loco/imximage.cfg
> index d1c1931..a5f1d98 100644
> --- a/board/freescale/mx53loco/imximage.cfg
> +++ b/board/freescale/mx53loco/imximage.cfg
> @@ -59,7 +59,7 @@ DATA 4 0x63fd9090 0x4d444c44
>  DATA 4 0x63fd907c 0x01370138
>  DATA 4 0x63fd9080 0x013b013c
>  DATA 4 0x63fd9018 0x00011740
> -DATA 4 0x63fd9000 0xc3190000
> +DATA 4 0x63fd9000 0x83190000
>  DATA 4 0x63fd900c 0x9f5152e3
>  DATA 4 0x63fd9010 0xb68e8a63
>  DATA 4 0x63fd9014 0x01ff00db
> @@ -72,6 +72,7 @@ DATA 4 0x63fd901c 0x00008033
>  DATA 4 0x63fd901c 0x00028031
>  DATA 4 0x63fd901c 0x052080b0
>  DATA 4 0x63fd901c 0x04008040
> +DATA 4 0x63fd9000 0xc3190000
>  DATA 4 0x63fd901c 0x0000803a
>  DATA 4 0x63fd901c 0x0000803b
>  DATA 4 0x63fd901c 0x00028039
> 

Good catch !

Acked-by: Stefano Babic <sbabic@denx.de>

Best regards,
Stefano Babic

-- 
=====================================================================
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 at denx.de
=====================================================================

      reply	other threads:[~2015-02-09 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09  9:29 [U-Boot] [PATCH] mx53loco: Fix boot hang during reboot stress test Fabio Estevam
2015-02-09 17:52 ` Stefano Babic [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=54D8F3CF.4020102@denx.de \
    --to=sbabic@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox