From: "Markus Wagner" <markus.wagner@wamasoft.de>
To: <vernoninhand@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: AW: Problems mounting jffs2 image on nor flash > Erase at 0x....failed immediately: -EROFS. Is the sector locked?
Date: Thu, 8 May 2008 08:59:50 +0200 [thread overview]
Message-ID: <200805080701.m4871jL8015834@wamasoft.de> (raw)
In-Reply-To: <48226D8F.3030603@gmail.com>
> Hello,
>
> i have some problems to mount my jffs2 image on my NOR-Flash.
> I ported UBoot and Linux to my new board.
> So far UBoot works well but Linux has some problems to mount the flash.
>
> I can read from my flash with the dd command.
> But when I mount the flash with 'mount -t jffs2 /dev/mtdblock4 /mnt/' I
get the error: 'Erase at 0x...... failed immediately: -EROFS. Is the sector
locked?'
>
> Some Infos:
> Its an Intel P33 Strataflash.
>
> <SNIP>
>
> It seems to me that the kernel doesn't know that the flash is protected
after power up.
>
> How can I get it to work?
> Where should I look at?
>
> Thanks for your help.
> Markus
>
>
>You did not mention exactly which device you are using. I just posted a
>patch to the list that added more StrataFlash devices to the fixup table
>so they are unlocked at power up.
>See [PATCH] mtd: add more StrataFlash chip ids that need powerup fixup
>Vern
It s a 28F256P33 Strataflash.
I have done a workaround in add_mtd_partitions()
If I detect the filesystem partition I fire a manually unlock to it.
Works so far.
But I will search your patch in the archive.
Seems to be the better solution.
Thx
Markus
prev parent reply other threads:[~2008-05-08 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 8:05 Problems mounting jffs2 image on nor flash > Erase at 0x.... failed immediately: -EROFS. Is the sector locked? Markus Wagner
2008-05-08 3:03 ` Vernon Sauder
2008-05-08 6:59 ` Markus Wagner [this message]
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=200805080701.m4871jL8015834@wamasoft.de \
--to=markus.wagner@wamasoft.de \
--cc=linux-mtd@lists.infradead.org \
--cc=vernoninhand@gmail.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