public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] fw_setenv device not accessible
Date: Tue, 29 Oct 2013 11:51:24 +0100	[thread overview]
Message-ID: <20131029105124.F417838061F@gemini.denx.de> (raw)
In-Reply-To: <1383039837672-166275.post@n7.nabble.com>

Dear pshambhu,

In message <1383039837672-166275.post@n7.nabble.com> you wrote:
>  
>     I am unable to change the u-boot environment variables from the Linux
> environment using fw_setenv and fw_printenv. 
> I am able to list out the variables from the particular partition, but i am
> unable to change the variable value using fw_setenv.
> 
> [Linux promp]# fw_setenv Status 0
> Can't open /dev/mtd4: Permission denied
> Error: can't write fw_env to flash
> 
> i tried to change the permission of /dev/mtd4 as well, but i am getting the
> same problem.

Obviously partition mtd4 is mapped as read-only.  You need read-write
mode instead.  This has nothing to do with the permissions on the
/dev/mtd4 special file, but with the mapping of the MTD device in the
device tree or the mtdargs boot argument or however you pass that
information to Linux on your system.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A Perl script is correct if it's halfway readable and  gets  the  job
done before your boss fires you.
                       - L. Wall & R. L. Schwartz, _Programming Perl_

  reply	other threads:[~2013-10-29 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29  9:43 [U-Boot] fw_setenv device not accessible pshambhu
2013-10-29 10:51 ` Wolfgang Denk [this message]
2013-11-08  7:15   ` pshambhu
2013-11-08  7:24     ` Wolfgang Denk

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=20131029105124.F417838061F@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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