All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul van Gool <paul.vangool@rinconnetworks.com>
To: linux-mtd@lists.infradead.org
Subject: problem writing to /dev/mtd0
Date: Fri, 14 Nov 2003 16:25:33 -0800	[thread overview]
Message-ID: <20031115002533.GA15967@rinconnetworks.com> (raw)

Hi,

I'm trying to read and write from/to a flash partition using its char
device. Reading seems to work fine but I can't seem to get writing  to
work.

I'm using a SolutionEngine7751 dev board, Linux 2.4.20 and the MTD release
that was part of that kernel. The error I get is:

Last[3] is cba4cda6, datum is 34333231

Looking at Last[4] during the 10000 write attempts, it seems its value
seems to alternate between cba4cda6 and cbe4cde6.

The errno I get back is 5, and is EIO.

Boottime info regarding the chips is:

Amd/Fujitsu Extended Query Table v1.0 at 0x0040
Solution Engine FLASH: JEDEC Device ID is 0xC4. Assuming broken CFI table.
Solution Engine FLASH: Swapping erase regions for broken CFI table.
number of CFI chips: 1
Solution Engine: Flash at 0x00000000, EPROM at 0x01000000
Using configured partition at 0x00020000.
Creating 4 MTD partitions on "Solution Engine FLASH":
0x00000000-0x00020000 : "Boot loader"
0x00020000-0x000e0000 : "Kernel"
0x000e0000-0x00300000 : "Root filesystem"
0x00300000-0x00400000 : "JFFS segment"

I use this flash chip through its block device all the time and writing
through that device (/dev/mtdblock0) hasn't been an issue.

Any ideas?

Thanks.

Paul
-- 
Paul van Gool                                               Rincon Networks
paul.vangool@rinconnetworks.com                              (805)-705-1442

             reply	other threads:[~2003-11-15  0:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15  0:25 Paul van Gool [this message]
2003-11-15  8:31 ` problem writing to /dev/mtd0 David Woodhouse
2003-11-17 16:53   ` Paul van Gool

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=20031115002533.GA15967@rinconnetworks.com \
    --to=paul.vangool@rinconnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.