linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: flash writing with Linux
Date: Fri, 16 Mar 2001 11:37:05 +0100	[thread overview]
Message-ID: <20010316103710.64844281DB@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 16 Mar 2001 10:57:20 +0100." <3AB1E380.7E88EC47@esd-electronics.com>


In message <3AB1E380.7E88EC47@esd-electronics.com> you wrote:
>
> does anybody know if a flash writing tool for Linux is available ?

Which architecture, what type of flash?

> I want to update a flash image from a running Linux. The Linux is
> running from a ramdisk, so the flash can be erased and rewritten.

Yepp, that's what we do all the time.

> I think what I need are two thing: A device driver for accessing the
> flash and a command line tool for erasing and writing to the flash.

Please check the Patch "patch.drivers" (against PPC 2.4.3-pre3  tree)
in  ftp://ftp.denx.de/pub/LinuxPPC/usr/src/patches/ or have a look at
our source snapshot at
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/linux-2.4.3-pre3-2001-03-11.tar.bz2

It includes a character device driver for CFI (AMD chips)  and  JEDEC
(Intel  chips) compliant flash types. So far, this has been tested on
big-endian systems (PowerPC only),  but  I  would  be  interested  in
receiving feedback for other architectures as well.

Of course there are also user  utilities  to  erase  the  flash.  For
writing no special tool is needed - just copy to the device (in fact,
if your write block size is a multiple of the erase block size of the
chips  the  driver  performs  an  auto-erase,  so  you don't need the
flash_erase command either).

Hope this helps - feel free to ask  if  there  are  any  question  or
problems.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
If in any problem you find yourself doing an immense amount of  work,
the answer can be obtained by simple inspection.

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

  reply	other threads:[~2001-03-16 10:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-16  9:57 flash writing with Linux Matthias Fuchs
2001-03-16 10:37 ` Wolfgang Denk [this message]
2001-03-16 15:25 ` Subodh Nijsure
2001-03-19 17:16   ` Matthias Fuchs
2001-03-19 17:35     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2001-03-19 17:31 Kári Davíðsson
2001-03-19 17:45 Julia Elbert

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=20010316103710.64844281DB@denx.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=matthias.fuchs@esd-electronics.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).