linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Nicholson <paul@eisusa.com>
To: "Rick Hunnicutt" <rhunnicutt@getntds.com>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MVME 5100 flash programming
Date: Wed, 19 Dec 2001 13:56:07 -0800	[thread overview]
Message-ID: <p04330106b846bc64c18f@[216.244.24.248]> (raw)
In-Reply-To: <000201c188cc$b6a5a720$8df859c7@get.com>


I don't know what a 5100 is or how the FLASH chip select is generated. Embedded chip select logic usually has a write enable bit. I would suggest that you verify that you can generate a chip select for a write operation.

Paul

At 12:35 PM -0800 12/19/01, Rick Hunnicutt wrote:
>Hello all,
>
>I have a 5100 running the 2.4.2 kernel and want to use the onboard flash.
>With PPC_Bug, we are able to program the 16M area with a kernel and RAM disk
>image and boot. At the very least, I'd like to use some of the remaining
>flash area as a read/write area for configuration data. Ideally, I'd like
>the whole flash area to be a JFFS file system using MTD and the CFI
>interface.
>
>Problem is, I am unable to get the flash to respond to any type of query.
>The MTD code fails to get a response to the CFI query. Other code that tries
>to perform a simple query of the chips Manufacture ID fails as well. I can
>read the data in the flash that was written by pflash but can't seem to get
>writes to occur.
>
>Anyone using the flash on a 5100 at all? Any ideas, code samples, help at
>all would be appreciated!
>
>Thanks,
>Rick
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-12-19 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 20:35 MVME 5100 flash programming Rick Hunnicutt
2001-12-19 21:56 ` Paul Nicholson [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='p04330106b846bc64c18f@[216.244.24.248]' \
    --to=paul@eisusa.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rhunnicutt@getntds.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).