From: llandre <r&d2@dave-tech.it>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Variable bootfile can't be modified [SOLVED]
Date: Mon, 16 Jul 2007 10:26:44 +0200 [thread overview]
Message-ID: <469B2BC4.20907@dave-tech.it> (raw)
In-Reply-To: <466FF29A.2080606@dave-tech.it>
CONFIG_EXTRA_ENV_SETTINGS erroneously defined bootfile twice.
Regards,
llandre
DAVE Electronics System House - R&D Department
web: http://www.dave-tech.it
email: r&d2 at dave-tech.it
> Hi all,
>
> I'm experiencing a weird problem with current U-Boot sources.
> Variable bootfile can't be modified as expected.
> When the board boots, bootfile looks like this:
>
> bootfile=parsy/prelk/uImage
>
> If I change it, the new value is appended to the env but old value in
> not deleted:
>
> parsy> setenv bootfile abc
> parsy> print bootfile
> bootfile=parsy/prelk/uImage
> parsy> print
> bootdelay=3
> baudrate=115200
> ...
> bootfile=parsy/prelk/uImage
> ...
> stdin=serial
> stdout=serial
> stderr=serial
> bootfile=abc
>
> Environment size: 1381/131067 bytes
> parsy>
>
> Then If I issue manually
> setenv bootfile
> the first occurrence is deleted.
> If I issue the same command again the second occurrence (abc) is deleted.
>
> Anybody experienced similar problems?
>
>
>
> TIA
> llandre
>
> DAVE Electronics System House - R&D Department
> web: http://www.dave-tech.it
> email: r&d2 at dave-tech.it
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
>
prev parent reply other threads:[~2007-07-16 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 13:35 [U-Boot-Users] Variable bootfile can't be modified llandre
2007-07-16 8:26 ` llandre [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=469B2BC4.20907@dave-tech.it \
--to=r&d2@dave-tech.it \
--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 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.