From: Sagar Heroorkar <sagar.heroorkar@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] (imp) uboot image size
Date: Wed, 14 Jul 2010 15:25:25 -0400 [thread overview]
Message-ID: <AANLkTikU-szcraLAd6kmsYneZWPQH2uQnFmFcTyyugZl@mail.gmail.com> (raw)
In-Reply-To: <4C3E0E3D.7060305@free.fr>
I changed the TEXT_BASE to implement the uboot redundancy. I got in to
problem of having image size.
See this:
I am planning to implement uboot redundancy.
This means having the following idea which we thought.
Golden-Uboot which is flashed in the NOR-FLASH. This is not field
upgradable.
This golden uboot is going to have logic to pick the other uboot based on
certain flags or env vriables
As i mentioned i wanted the uboot to be redundant.
So i will have 2 copies of uboot now.
Uboot1
Uboot2
Golden uboot will pick either of one uboots mentioned above. If the uboot1
which is picked fails to boot, then we will have uboot2 as back up to boot.
vice versa.
Golden uboot recides in the address fffa0000 (start.s).
There is a relocation code which copies the code from flash to ram. if the
uboot which i have picked addressess will change , hence how can i do the
relocation?
Any pointers will help me if any one already did this kind of approach
making uboot redundant.
next prev parent reply other threads:[~2010-07-14 19:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 18:38 [U-Boot] (imp) uboot image size Sagar Heroorkar
2010-07-13 18:46 ` Albert ARIBAUD
2010-07-14 6:10 ` Wolfgang Denk
2010-07-14 19:10 ` Sagar Heroorkar
[not found] ` <4C3E0E3D.7060305@free.fr>
2010-07-14 19:25 ` Sagar Heroorkar [this message]
2010-07-14 19:43 ` Albert ARIBAUD
2010-07-14 20:53 ` Wolfgang Denk
[not found] ` <4C3E2808.5040509@free.fr>
[not found] ` <20100714214943.4BFB6160691@gemini.denx.de>
2010-07-14 22:35 ` Albert ARIBAUD
2010-07-14 22:37 ` Albert ARIBAUD
2010-07-15 14:38 ` Sagar Heroorkar
2010-07-14 20:37 ` Wolfgang Denk
2010-07-14 20:29 ` Wolfgang Denk
2010-07-14 20:40 ` Albert ARIBAUD
2010-07-14 20:59 ` 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=AANLkTikU-szcraLAd6kmsYneZWPQH2uQnFmFcTyyugZl@mail.gmail.com \
--to=sagar.heroorkar@gmail.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 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.