mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Christian Hemp <c.hemp@phytec.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] mtd: nand_mxs: fix NAND error when change clk rate
Date: Thu, 22 Dec 2016 09:50:40 +0100	[thread overview]
Message-ID: <8e786abe-cd51-63a4-9dd6-b83360b3f928@phytec.de> (raw)
In-Reply-To: <20161221222923.GB24177@ravnborg.org>

Hello Sam,


On 21.12.2016 23:29, Sam Ravnborg wrote:
> Hi Christian.
>
> On Wed, Dec 21, 2016 at 10:38:41PM +0100, Christian Hemp wrote:
>> The function "nand_enable_edo_mode" changed the NAND clk rate, without turning
>> it off. In this case it is posible to get the following errors:
>>      MXS NAND: Error sending command
>>      MXS NAND: Error sending command
>>      MXS NAND: DMA read error
>>
>> This can be fixed if the NAND clk is disabled before we change the clk
>> rate.
> Very interesting.
> I have ~50 targets and a few of these are used for power cycle tests.
> On one of these targets I have seen this exact same pattern - once...
>
> Can you give any hints that makes it simpler to verify your fix or anything?
To reproduce the issue and test the fix I reseted the board in a loop.
For this I added 'reset' to /env/bin/init. With 'reset" in /env/bin/init I
saw the issue after 1 - 2 Minutes.
Also I have done 1000 power cuts and resets without any error in our 
test rack.

power cut:
1. start barebox to prompt
2. power cut

soft reset:
1. start barebox to prompt
2. reset

     Christian

>
>
> This is a board with i.MX6 SoloCore - where we have 2 GiB FLASH + 512 MB RAM.
>
> Anyway - it saved my day to see this landing on the mailing list!
>
> 	Sam


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-12-22  8:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 21:38 Christian Hemp
2016-12-21 22:29 ` Sam Ravnborg
2016-12-22  8:50   ` Christian Hemp [this message]
2016-12-22 17:55     ` Sam Ravnborg
2016-12-23 10:39 ` Sam Ravnborg
2016-12-27 17:07 ` Fabio Estevam
2017-01-09 10:21 ` Sascha Hauer
2017-08-21 16:26   ` Uwe Kleine-König
2017-08-21 16:31     ` Fabio Estevam

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=8e786abe-cd51-63a4-9dd6-b83360b3f928@phytec.de \
    --to=c.hemp@phytec.de \
    --cc=barebox@lists.infradead.org \
    --cc=sam@ravnborg.org \
    /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