All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Flash not Erased
Date: Thu, 20 Jun 2013 08:00:21 +0200	[thread overview]
Message-ID: <51C29A75.20000@denx.de> (raw)
In-Reply-To: <51C1CFB0.2040705@shf.de>

Hi Jan,

On 19.06.2013 17:35, Jan Schunke wrote:
> I am trying to compile my own U-Boot for microblaze.
> Version:
> U-Boot 2013.01-dirty (Jun 19 2013 - 16:26:51)
> microblazeel-xilinx-linux-gnu-gcc (crosstool-NG 1.15.3) 4.6.4 20120924
> (prerelease)
> GNU ld (crosstool-NG 1.15.3) 2.22.90.20121010
> 
> I have demo where Flash access works fine.
> Verion:
> U-Boot 2012.10 (Feb 13 2013 - 20:16:43)
> microblazeel-xilinx-linux-gnu-gcc (crosstool-NG 1.15.3) 4.6.2 20111018
> (prerelease)
> GNU ld (crosstool-NG 1.15.3) 2.21.53.20110813
> 
> 
> When I use my own u-boot and try to write to flash I always get
> 
> "Flash not erased"
> 
> it seems to be a problem that my flash is x16 but recognized as x8.
> 
> Are there any Config variables to set the mode to x16?

This is a known problem. Those chips connected in x8 mode are known to
currently not work correctly with the common CFI NOR flash driver. Could
you please try the following patch:

http://patchwork.ozlabs.org/patch/249707/

And let us know if this fixes the problem?

Thanks,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2013-06-20  6:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 15:35 [U-Boot] Flash not Erased Jan Schunke
2013-06-20  6:00 ` Stefan Roese [this message]
2013-06-20  7:50   ` Jan Schunke

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=51C29A75.20000@denx.de \
    --to=sr@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 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.