From: James <jamessteward@optusnet.com.au>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
Alessandro Rubini <rubini-list@gnudd.com>,
michael <trimarchi@gandalf.sssup.it>
Subject: Re: Help needed with MTD on AT91SAM9263-EK please.
Date: Fri, 30 May 2008 12:05:27 +1000 [thread overview]
Message-ID: <1212113127.6315.34.camel@Ubuntu-Desktop> (raw)
In-Reply-To: <1212043611.12909.8.camel@Ubuntu-Desktop>
On Thu, 2008-05-29 at 16:46 +1000, James wrote:
> On Thu, 2008-05-29 at 08:41 +0200, Richard Genoud wrote:
> > ok, so this must be a hardware problem...
>
> I've emailed Atmel. I suspect a chip has undergone a dies shrink and
> now there's a timing spec that's violated, unless I've got 2-3 boards
> all with the same hardware problem.
No response yet from Atmel.
> I'll look through the EBI timing setup and the chip requirements when I
> get another moment.
I made the chip timing excessively long/slow and the problems seem to
have disappeared!
At the moment I have..
(arch/arm/mach-at91/at91sam9263_devices.c)
/* set the bus interface characteristics */
at91_sys_write(AT91_SMC_SETUP(3),
AT91_SMC_NWESETUP_(0x1f)
| AT91_SMC_NCS_WRSETUP_(0x10)
| AT91_SMC_NRDSETUP_(0x1f)
| AT91_SMC_NCS_RDSETUP_(0x10));
at91_sys_write(AT91_SMC_PULSE(3),
AT91_SMC_NWEPULSE_(0x1f)
| AT91_SMC_NCS_WRPULSE_(0x3f)
| AT91_SMC_NRDPULSE_(0x1f)
| AT91_SMC_NCS_RDPULSE_(0x3f));
at91_sys_write(AT91_SMC_CYCLE(3),
AT91_SMC_NWECYCLE_(0x7f)
| AT91_SMC_NRDCYCLE_(0x7f));
if (data->bus_width_16)
mode = AT91_SMC_DBW_16;
else
mode = AT91_SMC_DBW_8;
at91_sys_write(AT91_SMC_MODE(3),
mode | AT91_SMC_READMODE
| AT91_SMC_WRITEMODE
| AT91_SMC_EXNWMODE_DISABLE
| AT91_SMC_TDF_(15));
which makes access times pretty slow - but seems reliable. I'll need to
learn more about the NAND chip timing requirements before refining these
to something more sensible.
Regards,
James.
next prev parent reply other threads:[~2008-05-30 2:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 6:20 Help needed with MTD on AT91SAM9263-EK please James
2008-05-23 6:26 ` Richard Genoud
2008-05-23 6:38 ` James
2008-05-23 6:48 ` michael
2008-05-23 7:02 ` James
2008-05-23 7:12 ` michael
2008-05-23 7:13 ` michael
2008-05-23 7:19 ` michael
2008-05-23 7:28 ` James
2008-05-23 6:52 ` Richard Genoud
2008-05-23 7:05 ` James
2008-05-23 7:27 ` Richard Genoud
2008-05-23 7:32 ` James
2008-05-23 7:41 ` michael
2008-05-25 22:50 ` James
2008-05-27 7:42 ` Richard Genoud
2008-05-27 21:46 ` James
2008-05-28 6:24 ` Richard Genoud
2008-05-28 22:52 ` James
2008-05-28 22:59 ` James
2008-05-29 6:41 ` Richard Genoud
2008-05-29 6:46 ` James
2008-05-30 2:05 ` James [this message]
2008-05-23 7:03 ` Alessandro Rubini
2008-05-23 7:08 ` James
2008-05-23 7:09 ` James
2008-05-23 7:39 ` Alessandro Rubini
2008-05-23 7:42 ` James
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=1212113127.6315.34.camel@Ubuntu-Desktop \
--to=jamessteward@optusnet.com.au \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.genoud@gmail.com \
--cc=rubini-list@gnudd.com \
--cc=trimarchi@gandalf.sssup.it \
/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