All of lore.kernel.org
 help / color / mirror / Atom feed
From: Todd Poynor <tpoynor@mvista.com>
To: Sreecharan Sivadevuni <mailsreecharan@yahoo.co.uk>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Question regarding mounting CRAMFS and JFFS2 from a single flash chip on ucLinux
Date: Tue, 22 Nov 2005 14:12:08 -0800	[thread overview]
Message-ID: <438397B8.5060205@mvista.com> (raw)
In-Reply-To: <20051122151042.57202.qmail@web26306.mail.ukl.yahoo.com>

Sreecharan Sivadevuni wrote:
> I am using an arm processor based development board on
> which there is an Intel E28F320(NOR) flash chip which
> is of 4MB. ...
> my flash is getting detected on 'cfi_probe'. But when
> I am trying to mount JFFS2(or trying to write to )
> '/dev/mtdblock0'(at 0x00600000) I am getting an error
> that it is a readonly file system. The error as it is
> printed on console is "-EROFS. Is the Sector Locked ?"
> This is coming from file 'cfi_cmdset_0001.c' from
> function 'do_erase_one_block'. This is despite that I
> have made my JFFS2 partition as MTD_WRITEB_WRITEABLE
> in 'physmem.c' file.

Your flash chips probably power up with all blocks locked, and blocks to 
be written must be unlocked first.  Can use flash_unlock /dev/mtdX prior 
to mounting the writeable fs, or various ways of unlocking blocks at 
chip probe or maps setup time have been discussed in the archives.

-- 
Todd

      reply	other threads:[~2005-11-22 22:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 15:10 Question regarding mounting CRAMFS and JFFS2 from a single flash chip on ucLinux Sreecharan Sivadevuni
2005-11-22 22:12 ` Todd Poynor [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=438397B8.5060205@mvista.com \
    --to=tpoynor@mvista.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mailsreecharan@yahoo.co.uk \
    /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.