From: "Jasper Jackson" <jasper@vidicode.nl>
To: "MTD Mailinglist" <linux-mtd@lists.infradead.org>
Subject: EDB9312 Flash chips
Date: Fri, 9 Jan 2004 10:54:14 +0100 [thread overview]
Message-ID: <002e01c3d696$8a421190$1800a8c0@inetrjasper> (raw)
Hi All,
We've been working around for a while with the EDB9312 developmentboard from
Cirrus Logic,
Now the time has come that we want a filesystem on our flashchips, the
problem is, that the flash chips don't seem
to respond to a CFI probe. There is a memory map written by David for the
edb7312 (the little brother).
It seems that the only thing that has to be done is ajust the WINDOW_START
and the WINDOW_SIZE,
but that doesn't work.
CFI Flash device in physical memory map, seems to work
when set to:
Physical start: 0x60000000
Physical length: 0x2000000
But reading from those adresses results in crep,
Almost everything I read is 'R' or 'U' and some dots, no binary data from ie
redboot which resides at adress 0x60000000 is found.
When lowlevel writing to those adresses (from a homebrew kernel module), the
data written can be read back that goes OK, but after a reboot it's gone,
not exactly what you expect from flash memory.
According to the Cirrus Documentation those are the right adresses, it is
also said that there is no difference between the
physical and the virual adress (not that I believe that, but ok).
Before I go ahead with JFFS I think that it's important that my flashchips
are detected.
Ok, ready for that part,
My question however, is, are there people familiar with MTD and the EDB9312,
i've been working for a week now on it,
I think i'm doing something terribly stupid wrong, I should be ashamed for
that, I know, but I don't see it at the moment.
Some extra information:
Kernel: 2.4.21-rmk1
Config:
MTD Support ON
Direct char device access ON
Caching block device access ON
ROM/Flashchip drivers -> Detect flash by CFI
ROM/Flashchip drivers -> Intel/sharp support
Thanks in advance,
Jasper Jackson
reply other threads:[~2004-01-09 9:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='002e01c3d696$8a421190$1800a8c0@inetrjasper' \
--to=jasper@vidicode.nl \
--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