From: Marcus Mikolaiczyk <m.mikolaiczyk@rac.de>
To: linux-mtd@lists.infradead.org
Subject: partition doesn't end on an erase block -> eraseall - permission denied
Date: Tue, 10 May 2005 13:15:23 +0200 [thread overview]
Message-ID: <428097CB.3010801@rac.de> (raw)
Hi all,
Our board uses a NOR Flash (mtd0,1) and a NAND flash 2Gbit Samsung
(256MByte). The NAND is now beeing recognised by the kernel but has some
problems with finding an eraseblock on the NAND.
Pagesize (2K + 64)Bytes
Blocksize(128K + 4K)Bytes (=eraseblocksize 0x21000)
Maybe to make a partition which ends up on an eraseblock could be a
solution?
nanddump is working.
dmesg:
...
devfs: v1.12a (20020514) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
Dummy keyboard driver installed.
pty: 256 Unix98 ptys configured
12:34:56:78:99:9A
12:34:56:78:99:9A
physmap flash device: 2000000 at a8000000
Triboard Flash: Found 2 x16 devices at 0x0 in 32-bit mode
Intel/Sharp Extended Query Table at 0x0031
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
Creating 2 MTD partitions on "Triboard Flash":
0x00000000-0x00500000 : "Kernel + BOLO"
mtd: Giving out device 0 to Kernel + BOLO
0x00500000-0x02000000 : "User_Flash"
mtd: Giving out device 1 to User_Flash
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB
3,3V 8-bit)
Creating 1 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x00000000-0x10000000 : "BTU NAND flash partition 1"
mtd: partition "BTU NAND flash partition 1" doesn't end on an erase
block -- force read-only
mtd: Giving out device 2 to BTU NAND flash partition 1
...
nanddump /dev/mtd/2 test_mtd2_dump_02 0x0 0x400
Jan 1 00:08:21 10 daemon.info klogd: MTD_open
Jan 1 00:08:21 10 daemon.info klogd: MTD_ioctl
Jan 1 00:08:23 10 daemon.info klogd: MTD_read
Jan 1 00:08:23 10 daemon.info klogd: nand_read_ecc: from = 0x00000000,
len = 512
Jan 1 00:08:23 10 daemon.warn klogd: Reading data from NAND FLASH
without ECC is not recommended
Jan 1 00:08:24 10 daemon.info klogd: MTD_ioctl
Jan 1 00:08:24 10 daemon.info klogd: nand_read_oob: from = 0x00000000,
len = 16
Jan 1 00:08:24 10 daemon.info klogd: MTD_read
Jan 1 00:08:24 10 daemon.info klogd: nand_read_ecc: from = 0x00000200,
len = 512
Jan 1 00:08:24 10 daemon.warn klogd: Reading data from NAND FLASH
without ECC is not recommended
Jan 1 00:08:24 10 daemon.info klogd: MTD_ioctl
Jan 1 00:08:24 10 daemon.info klogd: nand_read_oob: from = 0x00000200,
len = 16
Jan 1 00:08:24 10 daemon.info klogd: MTD_close
Jan 1 00:08:24 10 daemon.info klogd: nand_sync: called
bash-2.05a# eraseall -j /dev/mtd/2
eraseall: /dev/mtd/2: Permission denied
Jan 1 00:10:31 10 daemon.info klogd: MTD_open
bash-2.05a# unlock /dev/mtd/2
Could not open mtd device: /dev/mtd/2
next reply other threads:[~2005-05-10 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 11:15 Marcus Mikolaiczyk [this message]
2005-05-11 7:42 ` partition doesn't end on an erase block -> eraseall - permission denied Marcus Mikolaiczyk
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=428097CB.3010801@rac.de \
--to=m.mikolaiczyk@rac.de \
--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