From: Pink Boy <dasfoo@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problem building fw_printenv un u-boot 1.3.4
Date: Wed, 3 Dec 2008 13:08:02 -0800 (PST) [thread overview]
Message-ID: <499688.4597.qm@web31814.mail.mud.yahoo.com> (raw)
In-Reply-To: <20081203114512.4803C834B020@gemini.denx.de>
Dear Wolfgang,
> In message pink sez,
>> So still doing some hacking trying to build this and
>> wondering if either u-boot-1.3.4 is busted, or the
>> instructions are wrong.
>
> v1.3.4 is old. Why don't you use current code?
Far as I can tell v1.3.4 is from Sept this year. Is it older
than that?
>> Note sure it it works or not. When I run it I get the
>> following error.
> >
> > Cannot parse config file: No such file or directory
>
> Obviously you have to create a config file in your target
> file system...
I'm sorry I should have done a little more poking about before I
posted that. I put fw_env.config in /etc and changed the entry
to and at least
/dev/mtd1 0xe000 0x2000 0x2000
#/dev/mtd1 0xe000 0x2000 0x2000
Then created device nodes.
mknod /dev/mtd0 c 90 0
mknod /dev/mtd1 c 90 1
After that fw_printenv works. However fw_setenv returns an error.
# ./fw_setenv beets are_good
Can't open /dev/mtd1: Permission denied
Error: can't write fw_env to flash
It's probably something stupid on my part. But at least I got this
far.
Would using the latest tree be better? It appears at least that
make at91rm9200dk_config
make env
doesn't work because fw_printenv needs some kernel headers to
build correctly.
Mr Foo
prev parent reply other threads:[~2008-12-03 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 0:20 [U-Boot] pci booting 460ex seems to hang at tlb entries Ayman M. El-Khashab
2008-12-02 3:03 ` [U-Boot] Problem building fw_printenv un u-boot 1.3.4 Pink Boy
2008-12-03 1:38 ` Pink Boy
2008-12-03 11:45 ` Wolfgang Denk
2008-12-03 21:08 ` Pink Boy [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=499688.4597.qm@web31814.mail.mud.yahoo.com \
--to=dasfoo@yahoo.com \
--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