All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Stile <john@stilen.com>
To: buildroot@busybox.net
Subject: [Buildroot] can I build two copies of uboot in buildroot?
Date: Fri, 25 Jan 2013 16:01:47 -0800	[thread overview]
Message-ID: <1359158507.7974.86.camel@genx> (raw)
In-Reply-To: <1359148418.7974.65.camel@genx>

On Fri, 2013-01-25 at 13:13 -0800, John Stile wrote:
> I have hacked at91bootstrap to select and boot one of two copies of
> uboot+env on a NAND flash, but I had to compile the second uboot my
> self, since the environment address is set at compile time, and
> buildroot only builds one copy of uboot.  
> 
> How might I hack uboot to build two different copies of uboot?  I'm just
> changing the address location of the uboot environment, and saving the
> image as a different name.
> 
> I wasn't able to figure out how to make the uboot environment address a
> parameter to uboot, so I also haven't tried to have at91bootstrap call
> uboot with this parameter, but that might be easier.
> 

As this seems to be difficult to do, maybe it is the wrong approach.

From at91bootstrap, it is easy to also load uboots env area into another
RAM address.

Is it possible to have uboot read it's environment from a RAM address,
rather than NAND?
OR
Can uboot's scripting support load variables from a RAM address?

Maybe I could build one uboot, and one env, write it to two places,
have at91bootstrap copy the proper uboot to RAM, copy the proper
environment to RAM, and have uboot (via hack or script) acquire the
proper parameters from RAM.  This would allow for 2 NAND areas, and a
one fall back NOR image.

  reply	other threads:[~2013-01-26  0:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 21:13 [Buildroot] can I build two copies of uboot in buildroot? John Stile
2013-01-26  0:01 ` John Stile [this message]
2013-01-26  9:45 ` Peter Korsgaard

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=1359158507.7974.86.camel@genx \
    --to=john@stilen.com \
    --cc=buildroot@busybox.net \
    /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.