From: David Anders <dave123_aml@yahoo.com>
To: "Jörn" Engel <joern@logfs.org>, John Klonatos <megaklon@gmail.com>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: Direct Access to flash chips
Date: Wed, 29 Aug 2007 06:37:02 -0700 (PDT) [thread overview]
Message-ID: <154983.97140.qm@web54402.mail.yahoo.com> (raw)
In-Reply-To: <20070829103108.GD23020@lazybastard.org>
Jörn,
the alauda based card readers are getting pretty hard to find. although they work, they aren't a
long term solution for accessing raw NAND flash. by far the best solution i've run across is to
use the FTDI FT2232 chip to bit bang NAND flash access. there are both an opensource library and
proprietary library for the FT2232 usage under linux.(see projects like OpenOCD for example
usage).
chip information:
http://www.ftdichip.com/Products/FT2232C.htm
prototype modules:
http://www.dlpdesign.com/usb/2232m.shtml
there are some other products that would work as well including the EZ-Usb products, however they
do require custom firmware to properly access the NAND flash.
http://moin.elinux.org/wiki/EzUsb
there are several NAND flash vendors that have NAND flash evaluation kits that include a device
for accessing NAND flash, but these are generally beyond the cost of most developers.
Dave Anders
> On Wed, 29 August 2007 11:30:46 +0300, John Klonatos wrote:
> >
> > I am new to flash technology. From what i understand so far
> > in order to use the mtd layer, one must have direct access to the
> > flash chip.
> > If this is correct in the first place, i would like to know
> > how one can achieve this kind of direct connection. I have searched
> > through the web and so far nothing. I know there are card flash
> > readers (SmartMedia and Xd-Picture) but what the host system see is
> > the usb interface.
> > So, is there a (free) platform available to make possible this
> > type of direct connection. Or it is enough to use the usb
> > interface/protocol.
>
> Olympus MAUSB-10 and Fijufilm DPC-R1 allow raw access. You can use this
> driver:
> http://logfs.org/~joern/patches/alauda_mtd.patch.26
>
> David, any reason not to merge it?
>
> Jörn
>
> --
> In America you can have either a flimsy box banged together out of two
> by fours and drywall, or a McMansion -- a flimsy box banged together
> out of two by fours and drywall, but larger, more dramatic-looking,
> and full of expensive fittings.
> -- Paul Graham
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
____________________________________________________________________________________
Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545469
next prev parent reply other threads:[~2007-08-29 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 8:30 Direct Access to flash chips John Klonatos
2007-08-29 10:31 ` Jörn Engel
2007-08-29 13:37 ` David Anders [this message]
2007-08-29 13:46 ` David Woodhouse
2007-08-29 15:57 ` Jörn Engel
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=154983.97140.qm@web54402.mail.yahoo.com \
--to=dave123_aml@yahoo.com \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-mtd@lists.infradead.org \
--cc=megaklon@gmail.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