From: "Brock Denson" <bdenson@wa-ventures.com>
To: <linux-mtd@lists.infradead.org>
Subject: problems with mtd on atmel dk
Date: Fri, 23 Jul 2004 15:31:13 -0500 [thread overview]
Message-ID: <011d01c470f4$012c7b40$6400a8c0@BDENSONLAPTOP> (raw)
I am having problems with the flash on my at91rm9200dk board with
linux-2.4.26-vrs1 and the at91-03052004 patch. The dk has two flash chips,
an 8M dataflash (serial) at54db642, and a 2M parallel at49bv1614a. In the
boot log I get the following:
For the parallel flash:
...
physmap flash device: 200000 at 10000000
CFI: Found no Physically mapped flash device at location zero
Search for id:(1f c0) interleave(1) type(2)
Found: Atmel AT49BV16X
Physically mapped flash:
Found 1 x16 devices at 0x0 in 16-bit mode
kmod: failed to exec /sbin/modprobe -s -k cfi_cmdset_0002, errno = 2
Support for command set 0002 not present
gen_probe: No supported Vendor Command Set found
kmod: failed to exec /sbin/modprobe -s -k map_rom, errno = 2
...
For the serial flash:
...
Found AT91 i2c
AT91 SPI driver loaded
at91_dataflash: Atmel AT45DB642 detected [spi0] (8650752 bytes)
Creating 3 MTD partitions on "Atmel AT45DB642":
0x00000000-0x00010000 : "bootloader"
0x00010000-0x000d0000 : "kernel"
mtd: partition "kernel" doesn't start on an erase block boundary -- force
read-only
0x000d0000-0x00840000 : "filesystem"
mtd: partition "filesystem" doesn't start on an erase block boundary --
force read-only
...
If I do a ls dev/mtdblock I see:
0 1 2
Which I assume are the three partitions on the dataflash device, but I can
not mount them with mount -t jffs2 /dev/mtdblock/0 /mnt. I get a permission
denied error.
I don't see any listing at all for the parallel flash. Can someone point me
in the right direction on how to solve this problem?
Thanks,
Brock Denson
WAIV
bdenson@wa-ventures.com
210 849-1988
next reply other threads:[~2004-07-23 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 20:31 Brock Denson [this message]
2004-07-26 1:26 ` problems with mtd on atmel dk Aras Vaichas
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='011d01c470f4$012c7b40$6400a8c0@BDENSONLAPTOP' \
--to=bdenson@wa-ventures.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.