All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norman Cheung <brjerome.1@gmail.com>
To: Radha Mohan <radhamohan_ch@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Write to NOR flash garbled
Date: Mon, 24 Aug 2009 22:49:46 -0700	[thread overview]
Message-ID: <4A937B7A.4070609@gmail.com> (raw)
In-Reply-To: <231717.78385.qm@web94806.mail.in2.yahoo.com>

There was no error.  However, reading the content after the write shows 
that the data was corrupted. Putting a delay after the write seems to 
solve the problem. 

It seems that the chip_ready() in do_write_buffer() is returning 
prematurely.  According to Spansion's spec. chip_ready() should check 
DQ7.  But chip_ready() read the same location and if they are the same, 
it assumes that chip is ready.

Norman

Radha Mohan wrote:
> hi,
>
> Can you list out the errors that you are getting? 
> I also faced some problem with Spansion S29GL064M90TAIR4NOR flash. In my case the
> sector erase was not happening immediately after giving the command. So with that I saw
> some Data CRC and Node CRC errors.
> So I put a retry in the code where erase was failing (cfi_cmdset0002.c). And also I disabled
> the buffered write.
>
> -- Mohan
>
>
>
> ----- Original Message ----
> From: N Cheung <brjerome.1@gmail.com>
> To: linux-mtd@lists.infradead.org
> Sent: Tuesday, 25 August, 2009 12:28:28 AM
> Subject: Write to NOR flash garbled
>
> This device, a Micrel KS8695 based system with Linux 2.6.18 with AMD
> Am29LV641DH.  Device running find for 2 years until switch to a
> compatible Spansion NOR flash S29GL064N.
>
> flashcp failed with error: File does not seem to match flash data.
> First mismatch at 0x00000000-0x00002800
>
> Use dd to copy a one line text file, we can read it back OK.  But with
> a bigger (200 lines) text file, the data get garbled.
>
> However, if MTD debug is set to verbosity=3, flashcp copied big files
> without problem.
>
> Any pointers will be greatly appreciated.
>
> Thanks in advance,
> Norman
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
>
>       Looking for local information? Find it on Yahoo! Local http://in.local.yahoo.com/
>
>
>   

      reply	other threads:[~2009-08-25  5:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 18:58 Write to NOR flash garbled N Cheung
2009-08-25  4:51 ` Radha Mohan
2009-08-25  5:49   ` Norman Cheung [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=4A937B7A.4070609@gmail.com \
    --to=brjerome.1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=radhamohan_ch@yahoo.com \
    /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.