From: tglx@linutronix.de (Thomas Gleixner)
To: Shen Aaron-r62966 <Aaron.Shen@motorola.com>,
linux-mtd@lists.infradead.org
Subject: Re: Write function for 16 bit NAND Flash
Date: Fri, 23 Apr 2004 11:12:54 +0200 [thread overview]
Message-ID: <200404231112.54873.tglx@linutronix.de> (raw)
In-Reply-To: <01139FC052A0D411900B00508B9535FC13AC4057@ZCH07EXM04.corp.mot.com>
On Friday 23 April 2004 05:43, Shen Aaron-r62966 wrote:
> Hi,
>
> I'm investigating to write boot code into an empty 16 bit NAND Flash. I
> met some problem, and if you have some experience, please be kindly to
> share with me.
>
> The current write program is for 8 bit NAND Flash(Samsung K9F5608Q0C) and
> is loaded by AXD. The flash is 32 page per block and 528(512+16) byte per
> page. I use int type pointer to copy the boot data into the main area
> buffer of the flash. It's successful as I read back the data from the flash
> to verify.
int type pointer ? Surprise, surprise. Is the buswitdh set to 32 bit ?
> As the 16 bit NAND Flash(Samsung K9F5616Q0C) is also 32 page per block
> but 264(256+8) word per page, I try to use short int type pointer to copy.
> The data has truly been copied into the main area buffer of the flash. But
> after I read back it from the flash, it seems to be all 0xFFFF. Seems the
> data are not writen into the flash at all.
Hmm. How do you apply the commands to the chip ?
--
Thomas
________________________________________________________________________
"Free software" is a matter of liberty, not price. To understand the concept,
you should think of "free" as in "free speech,'' not as in "free beer".
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2004-04-23 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 3:43 Write function for 16 bit NAND Flash Shen Aaron-r62966
2004-04-23 9:12 ` Thomas Gleixner [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=200404231112.54873.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=Aaron.Shen@motorola.com \
--cc=linux-mtd@lists.infradead.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